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

Option to disallow `properties` step on specific pipeline job

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      So I just really discovered the the `properties` step... I can see a bunch of reasons to use it in multibranch and regular pipelines... but wow... that can really wreck a job configuration that you don't want people to mess with, huh?

      For example, we're using the gitlab-plugin. The setup for that isn't the most painful thing, but it also isn't super simple – either way, its pretty important.

      It's actually really bad that a developer can, without realizing what they are doing, add a properties step to a jenkinsfile and break the integration point.  Sure, we have code review to catch that sort of thing. But that doesn't really help if:

      • Naive developer adds `properties` step
      • Sets up merge request
      • Build automatically triggered
      • Build removes gitlab integration
      • All other merge requests blocked until project is reconfigured
      • (ノಥ,_」ಥ)ノ彡┻━┻

      It would be really great if there was a way to say that the properties step is not allowed for a given job. This feature would need to exist for all pipeline jobs and not just multibranch pipeline.

        Attachments

          Activity

            People

            Assignee:
            owenmehegan Owen Mehegan
            Reporter:
            crussell52 Chris Russell
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: