Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-2012

Prevent publishing of plugins with duplicate (step) symbols

    Details

    • Similar Issues:

      Description

      Jenkins pipeline engine (scripted and declarative) has severe problems if a plugin defines a symbol that already has been used by a step of another plugin. Currently, such errors result in errors that are not easy to analyze by the users: NPE (see: JENKINS-55349) or unrelated parsing errors (see: JENKINS-55436).

      It would be helpful, if our build infrastructure would prevent such errors by checking the available list of steps for duplications before such a new step is published in the update center.

        Attachments

          Issue Links

            Activity

            Hide
            drulli Ulli Hafner added a comment -

            A similar problem will occur if we have two plugins that publish an action that uses the same URL.

            Show
            drulli Ulli Hafner added a comment - A similar problem will occur if we have two plugins that publish an action that uses the same URL.
            Hide
            teilo James Nord added a comment -

            I do not believe this is the correct place for this issue.

             

            People can (and do) develop plugins that are not published via Jenkins-ci and as such Jenkins itself should offer a way to disambiguate or otherwise handle the errors.

             

            You can not say this is an issue for the people developing these plugins as there is they could have thousands of jobs using their symbol when a new colliding symbol is introduced in open source.

            Show
            teilo James Nord added a comment - I do not believe this is the correct place for this issue.   People can (and do) develop plugins that are not published via Jenkins-ci and as such Jenkins itself should offer a way to disambiguate or otherwise handle the errors.   You can not say this is an issue for the people developing these plugins as there is they could have thousands of jobs using their symbol when a new colliding symbol is introduced in open source.
            Hide
            drulli Ulli Hafner added a comment -

            Checking these things in Jenkins Runtime should be done anyway, there is also an issue: JENKINS-55349.

            Show
            drulli Ulli Hafner added a comment - Checking these things in Jenkins Runtime should be done anyway, there is also an issue: JENKINS-55349 .

              People

              • Assignee:
                Unassigned
                Reporter:
                drulli Ulli Hafner
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: