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

flexible publish - Parametrized trigger does not work

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Labels:
      None
    • Environment:
      Jenkins 1.446 on RHEL 6
      Plugin:run-condition, 0.7,
      Plugin:flexible-publish, 0.7
      Plugin:token-macro, 1.5.1,
      Plugin:conditional-buildstep,
      Plugin:any-buildstep, 0.1,
      Plugin:parameterized-trigger, 2.12
    • Similar Issues:

      Description

      Enable flexible publish and set any condition and add the Parametrized Trigger plugin, set the next job and some parameters.

      Log shows that it should have been called.

      Run condition [Always] enabling perform for step [Trigger parameterized build on other projects]
      Strings match run condition: string 1=[], string 2=[]
      Run condition [Not] preventing perform for step [Trigger parameterized build on other projects]
      [ArtifactDeployer] - Starting deployment from the post-action ...
      [ArtifactDeployer] - 2 file(s) have been copied from the workspace to '/company/site/groups/jenkins_wp/fahud022/property_files/CHAIN1_MCL_0_Start_2012-01-16_09-58-38'.
      [ArtifactDeployer] - Stopping deployment from the post-action...

      Next job is not called and they do not show up as Downstream Projects on the project page

      possible solutions:

      1. Flex publish Plugin should implement DependecyDeclarer and call any other publishers that require it, if this is possible and makes sense.

      2. Add use of run condition plugin to parametrized trigger plugin. and prevent flexible publish from using parametrized trigger plugin.

        Attachments

          Issue Links

            Activity

            Hide
            bap bap added a comment -

            Don't bother!
            Unfortunately, when using the change above, the conditions are ignored and the downstream builds will always be triggered.

            I will add the parameterized trigger to the list of excluded publishers.

            Show
            bap bap added a comment - Don't bother! Unfortunately, when using the change above, the conditions are ignored and the downstream builds will always be triggered. I will add the parameterized trigger to the list of excluded publishers.
            Hide
            cjo9900 cjo9900 added a comment -

            Ok, I expected this,
            I will work on the parameterized trigger to add run condition support replacing existing job result only.

            Show
            cjo9900 cjo9900 added a comment - Ok, I expected this, I will work on the parameterized trigger to add run condition support replacing existing job result only.
            Hide
            thoudayer T. Houdayer added a comment -

            cjo9900, do you fix this issue ? If yes, when do you plan to re-add the parameterized trigger into the Flexible plugin list of available publishers ?

            Show
            thoudayer T. Houdayer added a comment - cjo9900, do you fix this issue ? If yes, when do you plan to re-add the parameterized trigger into the Flexible plugin list of available publishers ?
            Hide
            cjo9900 cjo9900 added a comment -

            The fix was to add the functionality to the parameterized trigger, as there is no way that the flexible publish can affect the Dependancies that are created.

            See Pull request for it.
            https://github.com/jenkinsci/parameterized-trigger-plugin/pull/17

            Show
            cjo9900 cjo9900 added a comment - The fix was to add the functionality to the parameterized trigger, as there is no way that the flexible publish can affect the Dependancies that are created. See Pull request for it. https://github.com/jenkinsci/parameterized-trigger-plugin/pull/17
            Hide
            emszpak Marcin Zajączkowski added a comment -

            @cjo9900, from the comments I thought that fixing issue is waiting for merge of pull request 17 in parameterized-trigger-plugin, but when I asked there the reply was that it rather seems to be already fixed here. How does it really look like?

            Show
            emszpak Marcin Zajączkowski added a comment - @cjo9900, from the comments I thought that fixing issue is waiting for merge of pull request 17 in parameterized-trigger-plugin, but when I asked there the reply was that it rather seems to be already fixed here. How does it really look like?

              People

              • Assignee:
                bap bap
                Reporter:
                cjo9900 cjo9900
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: