[JIRA] (JENKINS-38401) Jekinsfile Changelist nr doesn't get updated when using pipeline Script from SCM.
Title: Message Title Karl Wirth started work on JENKINS-38401 Change By: Karl Wirth Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38401) Jekinsfile Changelist nr doesn't get updated when using pipeline Script from SCM.
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-38401 Jekinsfile Changelist nr doesn't get updated when using pipeline Script from SCM. Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38401) Jekinsfile Changelist nr doesn't get updated when using pipeline Script from SCM.
Title: Message Title Jason Davis commented on JENKINS-38401 Re: Jekinsfile Changelist nr doesn't get updated when using pipeline Script from SCM. Also running into this - the changes list for the build is never reset to only include the changes in that build, so it continually grows - making the list impractical for users to follow. Ideally - show only the Perforce changes in the build, and if there are no changes in the build, show "No Changes" rather than using the successful changes list from the previous build. Another problem side effect, when using the JIRA issue updater plugin to update JIRA tickets, the plugin is repeatedly marking JIRA issues, it looks like because the changes list is not being reset per build. So every build - even though there were no Perforce changes in that build - is marking the same JIRA issues in that list. I've had to avoid using my pipeline job, to avoid frustrating and confusing users. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38401) Jekinsfile Changelist nr doesn't get updated when using pipeline Script from SCM.
Title: Message Title Kevin Sim updated an issue Jenkins / JENKINS-38401 Jekinsfile Changelist nr doesn't get updated when using pipeline Script from SCM. Change By: Kevin Sim Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38401) Jekinsfile Changelist nr doesn't get updated when using pipeline Script from SCM.
Title: Message Title p v created an issue Jenkins / JENKINS-38401 Jekinsfile Changelist nr doesn't get updated when using pipeline Script from SCM. Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Sep/21 7:51 AM Environment: Jenkins 2.22 Priority: Minor Reporter: p v Jekinsfile Changelist nr doesn't get updated when using pipeline Script from SCM. Perforce Software Polling Log Started on 21.09.2016 08:47:00 P4: Polling on: master with:file-master-8.40_JenkinsFile ... p4 client -o file-master-8.40_JenkinsFile + ... p4 info + P4 Task: establishing connection. ... server: wessslx4:1666 ... node: WEW P4: Polling with range: 50845,now ... p4 changes -m100 //file-master-8.40_JenkinsFile/...@50845,now + P4: Polling on: master with:master-8.40_JenkinsFile ... p4 client -o master-8.40_JenkinsFile + ... p4 info + P4 Task: establishing connection. ... server: wessslx4:1666 ... node: WEW P4: Polling with range: 50845,now ... p4 changes -m100 //master-8.40_JenkinsFile/...@50845,now + ... p4 change -o 50871 + ... p4 describe -s 50871 + ... found change: 50871 next change: 50871 Done. Took 0,29 Sekunden Changes found
