-
Bug
-
Resolution: Fixed
-
Major
-
Pipeline: Multibranch 1.3
Jenkins ver. 1.647
It's not possible to enable Trigger builds remotely. The setting will not be persisted even if the option can be set. (The other Build Triggers can be set and are honored)
- is duplicated by
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JENKINS-30519 Declarative job properties in multibranch
-
- Resolved
-
- links to
[JENKINS-33020] ComputedFolder shows BuildAuthorizationToken configuration but does not actually support it
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
Quentin Dufour
added a comment - - edited 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.
Is there another way to trigger Branch Indexing remotely then?
.../notifyCommit never finds the project to trigger it...
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
Daniel Wilmer
added a comment - - edited 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
Screenshot multibranch pipeline setup dialog with the "Trigger Remote Build" as visible within Jenkins ver. 1.642.2 and Pipeline plugin version 1.13