• Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • downstream-ext-plugin
    • None

      Hi,

      In my use-case I'd like to pass parameters to downstream builds but only trigger if there are changes. The use-case is described in more detail on the mailing list: here.

      I logged a feature request on the Parameterized Trigger Plugin - to support SCM checks for downstream builds, but it's not clear what the best, most practical path is:

      • Parameterized plugin extended support SCM checks
      • Downstream-Ext plugin extended to support parameters
      • These plugins merged as they seem to cover similar functionality

      Would it make sense to add the parameter functionality to this plugin if there is no movement on the parameterized plugin?

      Ta
      Andy

          [JENKINS-11455] Support Parameters for Downstream Projects

          kutzi added a comment -

          I'm not sure what the best action would be.
          I don't think, however, that replicating parameterized trigger support in this plugin would be a good idea.
          Probably the best way would be to merge the plugins, but then again having small focused plugins is also a good goal.

          kutzi added a comment - I'm not sure what the best action would be. I don't think, however, that replicating parameterized trigger support in this plugin would be a good idea. Probably the best way would be to merge the plugins, but then again having small focused plugins is also a good goal.

          Andy Bigos added a comment -


          I think from a Software Engineering point of view having a small focused plugin is good - however if you can't use it with other plugins you are limiting functionality. It would be great to be able to chain the plugins together but I suspect that's not possible in this case (but not sure?). Otherwise, from a user's point of view it's not ideal to say you can't have that functionality because it's more elegant to have smaller more focused plugins! What do you think?

          Andy Bigos added a comment - I think from a Software Engineering point of view having a small focused plugin is good - however if you can't use it with other plugins you are limiting functionality. It would be great to be able to chain the plugins together but I suspect that's not possible in this case (but not sure?). Otherwise, from a user's point of view it's not ideal to say you can't have that functionality because it's more elegant to have smaller more focused plugins! What do you think?

          Currently I am not able to find a way to stop triggering parameterized downstreams of rebuilding matrix subjobs via matrix-reloaded plugin.
          I hoped that the Downstream-Ext Plugin would support me there, but unfortunately it is not possible to set up parameters here.

          From my Point of View these plugins are related so closely that merging these would provide more benefits than doubling code to cover all possible use cases.

          Julian Junghans added a comment - Currently I am not able to find a way to stop triggering parameterized downstreams of rebuilding matrix subjobs via matrix-reloaded plugin. I hoped that the Downstream-Ext Plugin would support me there, but unfortunately it is not possible to set up parameters here. From my Point of View these plugins are related so closely that merging these would provide more benefits than doubling code to cover all possible use cases.

            kutzi kutzi
            abigos Andy Bigos
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: