• Type: Bug
• Resolution: Duplicate
• Priority: Blocker
• Component/s: build-pipeline-plugin
• Labels:

  None
• Environment:

  Jenkins Version: 1.653
  Build Pipeline Plugin Version: 1.5.1

[JENKINS-33686] Build triggered via "Build other projects (manual step)" has no connection to upstream job

Angelo Veltens created issue - 2016-03-21 10:59

Angelo Veltens made changes - 2016-03-21 10:59

Summary

Original: Build triggerd via "Build other projects (manual step)" has no connection to upstream job

New: Build triggered via "Build other projects (manual step)" has no connection to upstream job

Angelo Veltens made changes - 2016-03-21 11:51

Description

Original: h3. Setup: Simple Build Pipeline "Build A -> Build B" *Build A*: Build: Shell execution 'echo "Hello"' Post Build Action: Build other projects (manual step): "Build B" *Build B*: Build: Shell execution 'echo "World"' h3. Problem / Steps to reproduce # Pressing "Run" in Build Pipeline View triggers "Build A" (/) # Build A goes green >(/) # Trigger "Build B" in Build Pipeline View (/) # Build B runs and and finishes with succes (/) # Build B does not get green in the Pipeline (x) # Build B has no connection to the upstrem job (x) h3. Additional information * The problem did not occur in Jenkins versions 1.642.2 and 1.642.3 * In the working versions we can see the following env variables: {code} BUILD_CAUSE MANUALTRIGGER,UPSTREAMTRIGGER BUILD_CAUSE_MANUALTRIGGER true BUILD_CAUSE_UPSTREAMTRIGGER true {code} * In the new version the env variables only state the following: {code} BUILD_CAUSE MANUALTRIGGER BUILD_CAUSE_MANUALTRIGGER true {code} * When Build B tries to copy an artifact from upstream build, it fails * The information "Started by upstream project "Build A" build number x" is missing in the console output of Build B

New: h3. Setup: Simple Build Pipeline "Build A -> Build B" *Build A*: Build: Shell execution 'echo "Hello"' Post Build Action: Build other projects (manual step): "Build B" *Build B*: Build: Shell execution 'echo "World"' h3. Problem / Steps to reproduce # Pressing "Run" in Build Pipeline View triggers "Build A" (/) # Build A goes green >(/) # Trigger "Build B" in Build Pipeline View (/) # Build B runs and and finishes with succes (/) # Build B does not get green in the Pipeline (x) # Build B has no connection to the upstrem job (x) h3. Additional information * The problem did not occur in Jenkins versions 1.642.2, 1.642.3 and also not in *1.652* * In the working versions we can see the following env variables: {code} BUILD_CAUSE MANUALTRIGGER,UPSTREAMTRIGGER BUILD_CAUSE_MANUALTRIGGER true BUILD_CAUSE_UPSTREAMTRIGGER true {code} * In the new version the env variables only state the following: {code} BUILD_CAUSE MANUALTRIGGER BUILD_CAUSE_MANUALTRIGGER true {code} * When Build B tries to copy an artifact from upstream build, it fails * The information "Started by upstream project "Build A" build number x" is missing in the console output of Build B

Angelo Veltens made changes - 2016-03-21 11:52

Description

Original: h3. Setup: Simple Build Pipeline "Build A -> Build B" *Build A*: Build: Shell execution 'echo "Hello"' Post Build Action: Build other projects (manual step): "Build B" *Build B*: Build: Shell execution 'echo "World"' h3. Problem / Steps to reproduce # Pressing "Run" in Build Pipeline View triggers "Build A" (/) # Build A goes green >(/) # Trigger "Build B" in Build Pipeline View (/) # Build B runs and and finishes with succes (/) # Build B does not get green in the Pipeline (x) # Build B has no connection to the upstrem job (x) h3. Additional information * The problem did not occur in Jenkins versions 1.642.2, 1.642.3 and also not in *1.652* * In the working versions we can see the following env variables: {code} BUILD_CAUSE MANUALTRIGGER,UPSTREAMTRIGGER BUILD_CAUSE_MANUALTRIGGER true BUILD_CAUSE_UPSTREAMTRIGGER true {code} * In the new version the env variables only state the following: {code} BUILD_CAUSE MANUALTRIGGER BUILD_CAUSE_MANUALTRIGGER true {code} * When Build B tries to copy an artifact from upstream build, it fails * The information "Started by upstream project "Build A" build number x" is missing in the console output of Build B

New: h3. Setup: Simple Build Pipeline "Build A -> Build B" *Build A*: Build: Shell execution 'echo "Hello"' Post Build Action: Build other projects (manual step): "Build B" *Build B*: Build: Shell execution 'echo "World"' h3. Problem / Steps to reproduce # Pressing "Run" in Build Pipeline View triggers "Build A" (/) # Build A goes green >(/) # Trigger "Build B" in Build Pipeline View (/) # Build B runs and and finishes with succes (/) # Build B does not get green in the Pipeline (x) # Build B has no connection to the upstream job (x) h3. Additional information * The problem did not occur in Jenkins versions 1.642.2, 1.642.3 and also not in *1.652* * In the working versions we can see the following env variables: {code} BUILD_CAUSE MANUALTRIGGER,UPSTREAMTRIGGER BUILD_CAUSE_MANUALTRIGGER true BUILD_CAUSE_UPSTREAMTRIGGER true {code} * In the new version the env variables only state the following: {code} BUILD_CAUSE MANUALTRIGGER BUILD_CAUSE_MANUALTRIGGER true {code} * When Build B tries to copy an artifact from upstream build, it fails * The information "Started by upstream project "Build A" build number x" is missing in the console output of Build B

Angelo Veltens made changes - 2016-03-22 09:14

Link

New: This issue duplicates JENKINS-33591 [ JENKINS-33591 ]

Dan Alvizu made changes - 2016-03-25 19:41

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Dan Alvizu made changes - 2016-03-25 19:41

Assignee

New: Dan Alvizu [ dalvizu ]

Dan Alvizu made changes - 2016-03-25 19:41

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]

R. Tyler Croy made changes - 2016-07-26 00:01

Workflow

Original: JNJira [ 169650 ]

New: JNJira + In-Review [ 209858 ]