• Type: Bug
• Resolution: Duplicate
• Priority: Critical
• Component/s: build-token-root-plugin
• Labels:

  None

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

Daniel Wilmer created issue - 2016-12-09 13:11

Daniel Wilmer made changes - 2016-12-09 13:11

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 - 2016-12-09 23:48

Link

New: This issue duplicates JENKINS-37412 [ JENKINS-37412 ]

Jesse Glick made changes - 2016-12-21 20:42

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]