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

Multibranch pipelines not allowing trigger from script

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • pipeline
    • None

      I am trying to to allow my multibranch Jenkins Pipeline to be triggered from a script. However each time I check the box and enter my token name and hit save, it does not save the configuration. When I hit edit configuration after saving, the box remains unchecked. Is this feature not supported from Jenkins Pipeline or is this a bug? If it's not supported, should we remove the checkbox option?

      Jenkins ver. 2.16

          [JENKINS-37412] Multibranch pipelines not allowing trigger from script

          Neil Hunt created issue -
          Daniel Wilmer made changes -
          Link New: This issue is duplicated by JENKINS-40335 [ JENKINS-40335 ]

          Daniel Wilmer added a comment - - edited

          As I descried in ticket JENKINS-40335 we are having the same issue here and it is a real issue for us.

          It is reproducible on a clean new jenkins installation (Version: 2.36).

          Daniel Wilmer added a comment - - edited As I descried in ticket JENKINS-40335 we are having the same issue here and it is a real issue for us. It is reproducible on a clean new jenkins installation (Version: 2.36).
          Jesse Glick made changes -
          Link New: This issue duplicates JENKINS-33020 [ JENKINS-33020 ]
          Jesse Glick made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            oleg_nenashev Oleg Nenashev
            neilhunt1 Neil Hunt
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: