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

Updates to a Choice Parameter are not synchronised

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • ez-templates-plugin
    • None
    • Jenkins ver. 2.7.1, EZ Templates 1.2.0

    Description

      My template job consist Choice parameter and when Choices are updated (e.g. I'm adding new choice items), the Choices in job which implements that template aren't updated (it says the same as it was). It works for other type of parameters, so it sounds like it's Choice parameter specific.

      Attachments

        Activity

          drekbour Marc Carter added a comment -

          I didn't implement any of the complex stuff - choices sync from template. Apologies for not mentioning it.

          I go through the cases in the next day or two to see if there is a deterministic rule that can be applied.

          drekbour Marc Carter added a comment - I didn't implement any of the complex stuff - choices sync from template. Apologies for not mentioning it. I go through the cases in the next day or two to see if there is a deterministic rule that can be applied.

          This would be awesome, thanks a lot.

          Should I submit a feature request in another ticket?

          dbalaganskiy Danila Balaganskiy added a comment - This would be awesome, thanks a lot. Should I submit a feature request in another ticket?
          drekbour Marc Carter added a comment -

          Go for it.

          drekbour Marc Carter added a comment - Go for it.
          emoshaya_cognitoiq Ebrahim Moshaya added a comment - - edited

          drekbour We have an ez template deploy job using the choice parameter "DEPLOY_ENVIRONMENT", that is available for developers, support and operations. The Choice parameter for some jobs implementing the template allow deploying artifacts to developer environments. However, I also have some jobs implementing the template that is hidden away and only available to support and operations that have production environments in the list of choice parameters. Ideally, we don't want every job inheriting the template to sync the choice parameters list or the order. Is there a way to exclude the choice parameters from syncing up with the parent template?

          emoshaya_cognitoiq Ebrahim Moshaya added a comment - - edited drekbour We have an ez template deploy job using the choice parameter "DEPLOY_ENVIRONMENT", that is available for developers, support and operations. The Choice parameter for some jobs implementing the template allow deploying artifacts to developer environments. However, I also have some jobs implementing the template that is hidden away and only available to support and operations that have production environments in the list of choice parameters. Ideally, we don't want every job inheriting the template to sync the choice parameters list or the order. Is there a way to exclude the choice parameters from syncing up with the parent template?

          @drekbour This change kind of broke all our configurations seeing as we had difference choices for different use cases in the implementing jobs. Could you please update to allow us to exclude the choice parameters all together from syncing the choices?

          emoshaya_cognitoiq Ebrahim Moshaya added a comment - @drekbour This change kind of broke all our configurations seeing as we had difference choices for different use cases in the implementing jobs. Could you please update to allow us to exclude the choice parameters all together from syncing the choices?

          People

            drekbour Marc Carter
            kenorb kenorb
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: