Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-23861

Parameterized remote trigger should allow setting parent build status based on downstream build status

      Basically it should have the same functionality as you get from the parameterized trigger plugin when blocking on the downstream build.

          [JENKINS-23861] Parameterized remote trigger should allow setting parent build status based on downstream build status

          Dima Spivak added a comment - - edited

          It would also be useful for the parameterized remote trigger plugin to set the same environmental variables that the parameterized plugin sets:

          • LAST_TRIGGERED_JOB_NAME="Last project started"
          • TRIGGERED_JOB_NAMES="Comma separated list of all triggered projects"
          • TRIGGERED_BUILD_NUMBER_<project name>="Last build number triggered"
          • TRIGGERED_BUILD_NUMBERS_<project name>="Comma separated list of build numbers triggered"
          • TRIGGERED_BUILD_RESULT_<project name>="Last triggered build result of project"
          • TRIGGERED_BUILD_RESULT_<project name>RUN<build number>= "Result of triggered build for build number"
          • TRIGGERED_BUILD_RUN_COUNT_<project name>= "Number of builds triggered for the project"

          (Realized this has already filed as JENKINS-22384.)

          Dima Spivak added a comment - - edited It would also be useful for the parameterized remote trigger plugin to set the same environmental variables that the parameterized plugin sets: LAST_TRIGGERED_JOB_NAME="Last project started" TRIGGERED_JOB_NAMES="Comma separated list of all triggered projects" TRIGGERED_BUILD_NUMBER_<project name>="Last build number triggered" TRIGGERED_BUILD_NUMBERS_<project name>="Comma separated list of build numbers triggered" TRIGGERED_BUILD_RESULT_<project name>="Last triggered build result of project" TRIGGERED_BUILD_RESULT_<project name> RUN <build number>= "Result of triggered build for build number" TRIGGERED_BUILD_RUN_COUNT_<project name>= "Number of builds triggered for the project" (Realized this has already filed as JENKINS-22384 .)

          This would be nice, because right now if the build it triggers is unstable, it will just fail this build.. when you may not want that

          Lorelei McCollum added a comment - This would be nice, because right now if the build it triggers is unstable, it will just fail this build.. when you may not want that

          For me, the UNSTABLE remote build does not change the caller build result and it is finished as a SUCCESS.
          When the remote job executes tests, this makes the UNSTABLE stats useless.

          Alexander Vorobiev added a comment - For me, the UNSTABLE remote build does not change the caller build result and it is finished as a SUCCESS. When the remote job executes tests, this makes the UNSTABLE stats useless.

            Unassigned Unassigned
            abayer Andrew Bayer
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: