-
Bug
-
Resolution: Unresolved
-
Major
p4 plugin: 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.
[JENKINS-61825] P4 - Additional build occurs
Kevin Park
created issue -
Kevin Park
made changes -
| Summary | Original: Additional build occurs | New: P4 - Additional build occurs |
Kevin Park
made changes -
| Description |
Original:
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. |
New:
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. |
Kevin Park
made changes -
| Description |
Original:
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. |
New:
p4 plugin: 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. |
Kevin Park
made changes -
| Labels | New: p4-plugin |
Kevin Park
made changes -
| Labels | Original: p4-plugin | New: p4plugin |
Karl Wirth
made changes -
| Assignee | New: Karl Wirth [ p4karl ] |
Karl Wirth
made changes -
| Labels | Original: p4plugin | New: P4_SUPPORT p4plugin |
