[JIRA] (JENKINS-13263) Downstream jobs inherit same changeset

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13263) Downstream jobs inherit same changeset

JIRA noreply@jenkins-ci.org
nicholas blasingame created JENKINS-13263:
---------------------------------------------

             Summary: Downstream jobs inherit same changeset
                 Key: JENKINS-13263
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13263
             Project: Jenkins
          Issue Type: Improvement
          Components: perforce
         Environment: Jenkins ver. 1.456
Perforce 1.3.11
            Reporter: nicholas blasingame


I have an initial job that syncs to the depot and gets the most up to date changesets and then triggers the rest of the jobs through a daisy chain.

I know there are features that enable you to pass a changelist via parameters or counter, but I haven't found any solutions for the jobs posting the same changeset as the initial job.

It would be nice to have an option that allows downstream jobs to inherit the same changelog as their parents'.

This is more of a convenience since we can just use deduction to figure out which tests are using the most recent revisions, but it would be nice to just be able to see each job tell us what accurate changeset it is using.

Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13263) Downstream jobs inherit same changeset

JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nicholas blasingame updated JENKINS-13263:
------------------------------------------

      Labels: perforce polling scm  (was: )
    Assignee: Carl Quinn
   

> Downstream jobs inherit same changeset
> --------------------------------------
>
>                 Key: JENKINS-13263
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13263
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: perforce
>         Environment: Jenkins ver. 1.456
> Perforce 1.3.11
>            Reporter: nicholas blasingame
>            Assignee: Carl Quinn
>              Labels: perforce, polling, scm
>
> I have an initial job that syncs to the depot and gets the most up to date changesets and then triggers the rest of the jobs through a daisy chain.
> I know there are features that enable you to pass a changelist via parameters or counter, but I haven't found any solutions for the jobs posting the same changeset as the initial job.
> It would be nice to have an option that allows downstream jobs to inherit the same changelog as their parents'.
> This is more of a convenience since we can just use deduction to figure out which tests are using the most recent revisions, but it would be nice to just be able to see each job tell us what accurate changeset it is using.
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13263) Downstream jobs inherit same changeset

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160935#comment-160935 ]

Rob Petti commented on JENKINS-13263:
-------------------------------------

Wouldn't it get the same changelog anyways? Or is the client view different in every job?
               

> Downstream jobs inherit same changeset
> --------------------------------------
>
>                 Key: JENKINS-13263
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13263
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: perforce
>         Environment: Jenkins ver. 1.456
> Perforce 1.3.11
>            Reporter: nicholas blasingame
>            Assignee: Carl Quinn
>              Labels: perforce, polling, scm
>
> I have an initial job that syncs to the depot and gets the most up to date changesets and then triggers the rest of the jobs through a daisy chain.
> I know there are features that enable you to pass a changelist via parameters or counter, but I haven't found any solutions for the jobs posting the same changeset as the initial job.
> It would be nice to have an option that allows downstream jobs to inherit the same changelog as their parents'.
> This is more of a convenience since we can just use deduction to figure out which tests are using the most recent revisions, but it would be nice to just be able to see each job tell us what accurate changeset it is using.
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13263) Downstream jobs inherit same changeset

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160936#comment-160936 ]

Rob Petti commented on JENKINS-13263:
-------------------------------------

In any case, this sounds like it would be better suited as a separate plugin, so it can be used with other SCM plugins and in mixed environments.
               

> Downstream jobs inherit same changeset
> --------------------------------------
>
>                 Key: JENKINS-13263
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13263
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: perforce
>         Environment: Jenkins ver. 1.456
> Perforce 1.3.11
>            Reporter: nicholas blasingame
>            Assignee: Carl Quinn
>              Labels: perforce, polling, scm
>
> I have an initial job that syncs to the depot and gets the most up to date changesets and then triggers the rest of the jobs through a daisy chain.
> I know there are features that enable you to pass a changelist via parameters or counter, but I haven't found any solutions for the jobs posting the same changeset as the initial job.
> It would be nice to have an option that allows downstream jobs to inherit the same changelog as their parents'.
> This is more of a convenience since we can just use deduction to figure out which tests are using the most recent revisions, but it would be nice to just be able to see each job tell us what accurate changeset it is using.
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13263) Downstream jobs inherit same changeset

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Petti updated JENKINS-13263:
--------------------------------

    Priority: Minor  (was: Major)
   

> Downstream jobs inherit same changeset
> --------------------------------------
>
>                 Key: JENKINS-13263
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13263
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: perforce
>         Environment: Jenkins ver. 1.456
> Perforce 1.3.11
>            Reporter: nicholas blasingame
>            Assignee: Carl Quinn
>            Priority: Minor
>              Labels: perforce, polling, scm
>
> I have an initial job that syncs to the depot and gets the most up to date changesets and then triggers the rest of the jobs through a daisy chain.
> I know there are features that enable you to pass a changelist via parameters or counter, but I haven't found any solutions for the jobs posting the same changeset as the initial job.
> It would be nice to have an option that allows downstream jobs to inherit the same changelog as their parents'.
> This is more of a convenience since we can just use deduction to figure out which tests are using the most recent revisions, but it would be nice to just be able to see each job tell us what accurate changeset it is using.
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13263) Downstream jobs inherit same changeset

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160938#comment-160938 ]

Rob Petti commented on JENKINS-13263:
-------------------------------------

Speaking of...

https://github.com/rpetti/display-upstream-changes-plugin
               

> Downstream jobs inherit same changeset
> --------------------------------------
>
>                 Key: JENKINS-13263
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13263
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: perforce
>         Environment: Jenkins ver. 1.456
> Perforce 1.3.11
>            Reporter: nicholas blasingame
>            Assignee: Carl Quinn
>            Priority: Minor
>              Labels: perforce, polling, scm
>
> I have an initial job that syncs to the depot and gets the most up to date changesets and then triggers the rest of the jobs through a daisy chain.
> I know there are features that enable you to pass a changelist via parameters or counter, but I haven't found any solutions for the jobs posting the same changeset as the initial job.
> It would be nice to have an option that allows downstream jobs to inherit the same changelog as their parents'.
> This is more of a convenience since we can just use deduction to figure out which tests are using the most recent revisions, but it would be nice to just be able to see each job tell us what accurate changeset it is using.
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13263) Downstream jobs inherit same changeset

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Petti updated JENKINS-13263:
--------------------------------

    Component/s: display-upstream-changes
                     (was: perforce)
   

> Downstream jobs inherit same changeset
> --------------------------------------
>
>                 Key: JENKINS-13263
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13263
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: display-upstream-changes
>         Environment: Jenkins ver. 1.456
> Perforce 1.3.11
>            Reporter: nicholas blasingame
>            Assignee: Carl Quinn
>            Priority: Minor
>              Labels: perforce, polling, scm
>
> I have an initial job that syncs to the depot and gets the most up to date changesets and then triggers the rest of the jobs through a daisy chain.
> I know there are features that enable you to pass a changelist via parameters or counter, but I haven't found any solutions for the jobs posting the same changeset as the initial job.
> It would be nice to have an option that allows downstream jobs to inherit the same changelog as their parents'.
> This is more of a convenience since we can just use deduction to figure out which tests are using the most recent revisions, but it would be nice to just be able to see each job tell us what accurate changeset it is using.
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13263) Downstream jobs inherit same changeset

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Petti resolved JENKINS-13263.
---------------------------------

      Assignee: Rob Petti  (was: Carl Quinn)
    Resolution: Fixed

This information can now be obtained by using the Display Upstream Changes plugin, which will add the list of upstream changes to the build summary.
               

> Downstream jobs inherit same changeset
> --------------------------------------
>
>                 Key: JENKINS-13263
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13263
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: display-upstream-changes
>         Environment: Jenkins ver. 1.456
> Perforce 1.3.11
>            Reporter: nicholas blasingame
>            Assignee: Rob Petti
>            Priority: Minor
>              Labels: perforce, polling, scm
>
> I have an initial job that syncs to the depot and gets the most up to date changesets and then triggers the rest of the jobs through a daisy chain.
> I know there are features that enable you to pass a changelist via parameters or counter, but I haven't found any solutions for the jobs posting the same changeset as the initial job.
> It would be nice to have an option that allows downstream jobs to inherit the same changelog as their parents'.
> This is more of a convenience since we can just use deduction to figure out which tests are using the most recent revisions, but it would be nice to just be able to see each job tell us what accurate changeset it is using.
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13263) Downstream jobs inherit same changeset

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161115#comment-161115 ]

nicholas blasingame commented on JENKINS-13263:
-----------------------------------------------

Excellent thanks!
               

> Downstream jobs inherit same changeset
> --------------------------------------
>
>                 Key: JENKINS-13263
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13263
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: display-upstream-changes
>         Environment: Jenkins ver. 1.456
> Perforce 1.3.11
>            Reporter: nicholas blasingame
>            Assignee: Rob Petti
>            Priority: Minor
>              Labels: perforce, polling, scm
>
> I have an initial job that syncs to the depot and gets the most up to date changesets and then triggers the rest of the jobs through a daisy chain.
> I know there are features that enable you to pass a changelist via parameters or counter, but I haven't found any solutions for the jobs posting the same changeset as the initial job.
> It would be nice to have an option that allows downstream jobs to inherit the same changelog as their parents'.
> This is more of a convenience since we can just use deduction to figure out which tests are using the most recent revisions, but it would be nice to just be able to see each job tell us what accurate changeset it is using.
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira