|
||||||||
|
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-15653) Filter changes by view... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)
- [JIRA] (JENKINS-15653) Filter changes by... [email protected] (JIRA)

Thanks Rob.
#1: I validated this works OK in my Jenkins.
#3: This seems to work OK if one or more changes occurred since the last build. In that case P4_CHANGELIST matches the most recent entry on the /changes page. However when /changes shows 'no changes since last build' I would expect P4_CHANGELIST to be the same as the previous build, but it's not the case. I think this is a bug.