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

flexible publish - Parametrized trigger does not work

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • None
    • 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

      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.

          [JENKINS-12418] flexible publish - Parametrized trigger does not work

          cjo9900 created issue -
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          cjo9900 made changes -
          Description Original: 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 '/nokia/fa_nmp/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.





          New: 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.





          bap made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          bap made changes -
          Status Original: Reopened [ 4 ] New: Open [ 1 ]
          bap made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          bap made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          ikedam made changes -
          Link New: This issue is related to JENKINS-19146 [ JENKINS-19146 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 142784 ] New: JNJira + In-Review [ 205609 ]

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

              Created:
              Updated:
              Resolved: