|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-15515) Provide environm... [email protected] (JIRA)
- [JIRA] (JENKINS-15515) Provide env... [email protected] (JIRA)
- [JIRA] (JENKINS-15515) Provide env... [email protected] (JIRA)
- [JIRA] (JENKINS-15515) Provide env... [email protected] (JIRA)
- [JIRA] (JENKINS-15515) Provide env... [email protected] (JIRA)
- [JIRA] (JENKINS-15515) Provide env... [email protected] (JIRA)
- [JIRA] (JENKINS-15515) Provide env... [email protected] (JIRA)
- [JIRA] (JENKINS-15515) Provide env... [email protected] (JIRA)
- [JIRA] (JENKINS-15515) Provide env... [email protected] (JIRA)

Sorry for that, maybe this example might make things a little clearer.
Given the depot layout
Which contains the history
If I'd set up a project in jenkins using the view map
Which is simply a job that calls;
Building this job after changeset 1 is submitted (before changeset 2 is submitted) I get the expected output
Then if I submit changeset 2 and build the project again I get the response
Am I misconstruing what P4_CHANGELIST represents? I'd expect it to be the changeset id of the last changeset associated with a project, but under all the projects I've used it with it seems to be the last sync'd changeset regardless of the workspace.