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

"Trigger builds remotely" not saved in Project Pipeline Configuration

XMLWordPrintable

      The "Trigger builds remotely" Token is not saved (similar to JENKINS-36451).

      Steps to reproduce:

      • create an new Multibranch Pipeline Job.
      • Fill all required information.
      • Under "Build Triggers" select "Trigger builds remotely (e.g., from scripts)".
      • Enter a token.
      • Save.
      • Open the configuration again.
      • The "Trigger builds remotely" checkbox is not selected anymore.

      Luckily as a workaround we can use the Trigger "Periodically if not otherwise run".

          [JENKINS-40335] "Trigger builds remotely" not saved in Project Pipeline Configuration

          Daniel Wilmer created issue -
          Daniel Wilmer made changes -
          Description Original: The "Trigger builds remotely" Token is not saved (similar to JENKINS-36451).

          Steps to reproduce:
          * create an new Multibranch Pipeline Job
          * Fill all required information.
          * Under "Build Triggers" select "Trigger builds remotely (e.g., from scripts)"
          * Enter a token.
          * Save.
          * Open the configuration again.
          * The "Trigger builds remotely" checkbox is not selected anymore.

          Luckily as a workaround we can use the Trigger "Periodically if not otherwise run".
          		 New: The "Trigger builds remotely" Token is not saved (similar to JENKINS-36451).

          Steps to reproduce:
          * create an new Multibranch Pipeline Job.
          * Fill all required information.
          * Under "Build Triggers" select "Trigger builds remotely (e.g., from scripts)".
          * Enter a token.
          * Save.
          * Open the configuration again.
          * The "Trigger builds remotely" checkbox is not selected anymore.

          Luckily as a workaround we can use the Trigger "Periodically if not otherwise run".
          Daniel Wilmer made changes -
          Link New: This issue duplicates JENKINS-37412 [ JENKINS-37412 ]

          Adrien Lecharpentier added a comment -

          This is also true for any kind of jobs. In Jenkins 2.19.4, even a freestyle job won't save the token.

          Adrien Lecharpentier added a comment - This is also true for any kind of jobs. In Jenkins 2.19.4, even a freestyle job won't save the token.

          Jesse Glick added a comment -

          In Jenkins 2.19.4, even a freestyle job won't save the token.

          I just tried it and it is working for me. Anyway, if true, totally unrelated to this issue.

          Jesse Glick added a comment - In Jenkins 2.19.4, even a freestyle job won't save the token. I just tried it and it is working for me. Anyway, if true, totally unrelated to this issue.
          Jesse Glick made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Roy Shang added a comment -

          I have the same problem, my OS is Archlinux and Jenkins version is jenkins-2.47-1-any

          cannot find save button in the build triggers section of View Configuration

          Roy Shang added a comment - I have the same problem, my OS is Archlinux and Jenkins version is jenkins-2.47-1-any cannot find save button in the build triggers section of View Configuration

          Jesse Glick added a comment - - edited

          cannot find save button in the build triggers section of View Configuration

          Hence View Configuration, not Configure.

          Jesse Glick added a comment - - edited cannot find save button in the build triggers section of View Configuration Hence View Configuration , not Configure .

            Unassigned Unassigned
            dawi Daniel Wilmer
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: