[ 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