Is this a standalone project (thus, bug), or a branch project (thus, possibly duplicate of JENKINS-34005)? Steps to reproduce from scratch? Exact plugin versions?

I just tried to do the same thing on Jenkins 2.5 but there the remote trigger option is gone...
Use the LTS Jenkins Version with the actual Pipeline plugins and create a new Pipeline-Multibranch item using the Pipeline script from SCM definition with the URL https://github.com/reinhapa/junit-compat.git

Set the Trigger builds remotely (e.g., from scripts) option under Build Triggers

After saving and re-open the build trigger setting for remote triggering is no longer active.

Used Versions:
Jenkins 1.642.2
Pipeline-Multibranch: 1.13

I'm affected by this as well (both in Jenkins 2.0 and 2.6, multibranch plugin 2.4) using a github source but even if I specify no source at all the trigger setting doesn't persist.

Set the Trigger builds remotely (e.g., from scripts) option under Build Triggers

Sorry, where? There is no such option for multibranch projects.

Hmm, it must be another plugin that causes the option to be there then, because I definitely have the option.

Could be the "Build Token Root Plugin"

Screenshot multibranch pipeline setup dialog with the "Trigger Remote Build" as visible within Jenkins ver. 1.642.2 and Pipeline plugin version 1.13

I've the same problem. I can check the box and enter a token, but when I click on save, this field is reset.
I'm on Jenkins 2.9 (and also had this problem on previous versions).
Seems to be the same bug as JENKINS-35310

Accidentally edited duplicate, so see explanation there. Summary: a bug only in that the option is even displayed.

cobexer

Is there another way to trigger Branch Indexing remotely then?

POST to …/build.

.../notifyCommit never finds the project to trigger it...

If true, that is a bug, or more likely a misconfiguration.

BTW an alternate misinterpretation of the checkbox which should not be here is to set a build token on each branch project inside the folder, i.e. to schedule actually project builds rather than indexing. This is not currently possible; one bullet point in JENKINS-30519 proposes a possible implementation, but really BuildAuthorizationToken is a deprecated system that is fundamentally insecure, and probably ultimately better solved by allowing users to create limited-access tokens.

jglick Thanks for clarification.

I just wanted to verify that /notifyCommit works fine.
Jenkins Users, just be sure to use exactly the same repository urls in the job configuration and notification url.

• works:
  • Multibranch pipeline repository url: git@gitlab:some/project.git
  • Multibranch pipeline notification url: https://jenkins/git/notifyCommit?url=git@gitlab:some/project.git
• works:
  • Multibranch pipeline repository url: git@gitlab.intranet:some/project.git
  • Multibranch pipeline notification url: https://jenkins/git/notifyCommit?url=git@gitlab.intranet:some/project.git
• does not work (misconfiguration):
  • Multibranch pipeline repository url: git@gitlab.intranet:some/project.git
  • Multibranch pipeline notification url: https://jenkins/git/notifyCommit?url=git@gitlab:some/project.git

Code changed in jenkins
User: Stephen Connolly
Path:
src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java
src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/configure-details.jelly
src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/configure-details.properties
src/main/resources/com/cloudbees/hudson/plugins/folder/computed/Messages.properties
http://jenkins-ci.org/commit/cloudbees-folder-plugin/9c378bea8901a0fddd0bdcea0783b98dae7d1078
Log:
[FIXED JENKINS-40921][FIXED JENKINS-33020] Only display triggers that make sense for a folder computation

Code changed in jenkins
User: Stephen Connolly
Path:
src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java
src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/configure-details.jelly
src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/configure-details.properties
src/main/resources/com/cloudbees/hudson/plugins/folder/computed/Messages.properties
src/test/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolderTest.java
http://jenkins-ci.org/commit/cloudbees-folder-plugin/0d35973205f9bf79eee02ba36dc380f02b6ecc0a
Log:
Merge pull request #89 from stephenc/jenkins-40921

[FIXED JENKINS-40921][FIXED JENKINS-33020] Only display triggers that make sense for a folder computation

Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/ea44cb643427...0d35973205f9

cloudbees-folders 6.0.0