"Trigger builds remotely" not saved in Project Pipeline Configuration

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

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".

            Assignee:
            Unassigned
            Reporter:
            Daniel Wilmer
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: