[JIRA] (JENKINS-61825) P4 - Additional build occurs

[s3037560@gmail.com (JIRA)]

Kevin Park updated an issue

Jenkins / JENKINS-61825 P4 - Additional build occurs Change By: Kevin Park Summary: P4 - Additional build occurs Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[s3037560@gmail.com (JIRA)]

Kevin Park updated an issue

Jenkins / JENKINS-61825 P4 - Additional build occurs Change By: Kevin Park

p4 plugin: 10.10.12   It is a multibranch pipeline project with Helix Streams as its source. See the attached screen shot (multi_pipeline.png).   I have the following trigger, so the trigger will be fired only when there is a submit to //stream/Dev-A/…   $ p4 triggers -o | grep -v “^#” Triggers:      jenkins change-commit //stream/Dev-A/... “%//depot/jdepot.sh% %change%”   jdepot.sh is attached.   However, in the following steps, a Jenkins job for another stream path, //stream/Dev-B/… is also fired.  * A submit is made to //stream/Dev-B/… * No Jenkins job is fired since the submit was not for //stream/Dev-A/…, which is expected. * A submit is made to //stream/Dev-A/… * A Jenkins job for //stream/Dev-A/… is fired, which is expected. * However, a Jenkins job for //stream/Dev-B/… which was previously submitted is also fired.   Jenkinsfile for //stream/Dev-A/… and //stream/Dev-B/… are attached. See Jenkins_Dev-A and Jenkins_Dev-B.

Add Comment

[s3037560@gmail.com (JIRA)]

Kevin Park updated an issue

Jenkins / JENKINS-61825 P4 - Additional build occurs

Change By: Kevin Park Labels: p4-plugin p4plugin

Add Comment

[s3037560@gmail.com (JIRA)]

Kevin Park updated an issue

Jenkins / JENKINS-61825 P4 - Additional build occurs Change By: Kevin Park Labels: p4-plugin

Add Comment

[s3037560@gmail.com (JIRA)]

Kevin Park updated an issue

Jenkins / JENKINS-61825 P4 - Additional build occurs Change By: Kevin Park

p4 plugin: 10 1 .10.12

It is a multibranch pipeline project with Helix Streams as its source. See the attached screen shot (multi_pipeline.png).   I have the following trigger, so the trigger will be fired only when there is a submit to //stream/Dev-A/…   $ p4 triggers -o | grep -v “^#” Triggers:      jenkins change-commit //stream/Dev-A/... “%//depot/jdepot.sh% %change%”   jdepot.sh is attached.   However, in the following steps, a Jenkins job for another stream path, //stream/Dev-B/… is also fired.  * A submit is made to //stream/Dev-B/… * No Jenkins job is fired since the submit was not for //stream/Dev-A/…, which is expected. * A submit is made to //stream/Dev-A/… * A Jenkins job for //stream/Dev-A/… is fired, which is expected. * However, a Jenkins job for //stream/Dev-B/… which was previously submitted is also fired.   Jenkinsfile for //stream/Dev-A/… and //stream/Dev-B/… are attached. See Jenkins_Dev-A and Jenkins_Dev-B.

Add Comment

[kwirth@perforce.com (JIRA)]

Karl Wirth commented on JENKINS-61825

Re: P4 - Additional build occurs Hi Kevin Park The Perforce trigger you are using tells all jobs to wake up and check if they need to be built. Therefore any job that has: triggers { p4Trigger() } will wake up and check if it needs to be built. In your case there are new changes so it will run the build. If you are after a more targeted build you need to remove the 'triggers' line above from your pipeline script and call the direct URL for the job in your Perforce trigger. For example: http://MyJenkinsServer:8080/job/MyJobName/job/MyBranchName/build?delay=0sec

Add Comment

[kwirth@perforce.com (JIRA)]

Karl Wirth updated an issue

Jenkins / JENKINS-61825

P4 - Additional build occurs

Change By: Karl Wirth Labels: P4_SUPPORT p4plugin

Add Comment

[kwirth@perforce.com (JIRA)]

Karl Wirth assigned an issue to Karl Wirth

Jenkins / JENKINS-61825 P4 - Additional build occurs

Change By: Karl Wirth Assignee: Karl Wirth

Add Comment