Declarative should provide an easy way to disable/enable some steps in an PR context or not

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      When writing a Jenkinsfile, if you have email notifications, or notifications in general, this probably does not make sense to send those when building a PR. Same goes for actual deployments or touching real environments by any mean.

      PR are reviewed through GitHub, have a build status there, and so on. So by default, sending emails to maintainers creates unnecessary noise.

      Maybe this be globally enabled/disabled by default though the new options block.

      Like:

      options {
         notifyOnChangeRequest = true // I would argue that we should be opinionated and put it with a default of false
      }
      

      And possibly be overridable per step, like:

      notOnChangeRequest { // PR on GitHub & Bitbucket, patchset on Gerrit, Review Request in ReviewBoard...
         sh "deploy-to-production.sh"
      }
      

      For when and usual stage deactivations:

      when {
          branch CHANGE_REQUEST
      }
      

      WDYT?

      Thanks!

            Assignee:
            Andrew Bayer
            Reporter:
            Baptiste Mathus
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: