|
||||||||
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... and...@keyboardcowboy.co.uk (JIRA)
- [JIRA] (JENKINS-15515) Provide env... rob.pe...@gmail.com (JIRA)
- [JIRA] (JENKINS-15515) Provide env... and...@keyboardcowboy.co.uk (JIRA)
- [JIRA] (JENKINS-15515) Provide env... and...@keyboardcowboy.co.uk (JIRA)
- [JIRA] (JENKINS-15515) Provide env... and...@keyboardcowboy.co.uk (JIRA)
- [JIRA] (JENKINS-15515) Provide env... and...@keyboardcowboy.co.uk (JIRA)
- [JIRA] (JENKINS-15515) Provide env... rob.pe...@gmail.com (JIRA)
- [JIRA] (JENKINS-15515) Provide env... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15515) Provide env... scm_issue_l...@java.net (JIRA)
I'm not sure I follow your first paragraph... P4_CHANGELIST is the last changeset id for the workspace, not the entire depot. On depots containing multiple projects, this will only be set to the last change that is synced for that specific project as defined by the workspace view. In this way, it already does exactly what you need it to do.
Are you just requesting that a variable be added that contains the changeset of the previous build?