Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Ubuntu 14.04 x86_61
Jenkins 2.12
Open JDK 7
Multi-Branch Project Plugin 0.5
Description
According to the plugin wiki (https://wiki.jenkins-ci.org/display/JENKINS/Multi-Branch+Project+Plugin):
Sub-projects appear to be configurable, but they will be overwritten by branch indexing if you manually modify them.
But after I made changes to sub-branch project and run branch-indexing,
the sub-branch project configuration is not overwritten,
and further changes from Multi-branch configuration is not sync over to sub-branch project anymore.
Symptom:
You will see Detected unsupported subitem f.q.ClassName@hash[my-multibranch-project/my-branch], skipping in the indexing log.
Attachments
Activity
I'm using SVN plugin in Branch sources.
so I have tried to change sub-branch project SCM to:
1
"none".
2.
Change SVN Repository URL to use one of input parameter variable.
After the change,
the branch index is not sync anymore.
Rick Liu
added a comment - - edited I'm using SVN plugin in Branch sources.
so I have tried to change sub-branch project SCM to:
1
"none".
2.
Change SVN Repository URL to use one of input parameter variable.
After the change,
the branch index is not sync anymore.
Rick Liu
added a comment - Another place to easily reproduce is "Discard old build".
At Multibranch-Multiconfiguration,
I keep max 5 of build,
and then do branch indexing to have all sub-branch jobs created.
Then go to one of sub-branch jobs and change to keep max 10 of builds.
After the change,
the further branch indexing won't sync over.
Rick Liu
added a comment - Another place to easily reproduce is "Discard old build".
At Multibranch-Multiconfiguration,
I keep max 5 of build,
and then do branch indexing to have all sub-branch jobs created.
Then go to one of sub-branch jobs and change to keep max 10 of builds.
After the change,
the further branch indexing won't sync over. Added symptom to issue description. Also, this applies to all multibranch job types in this plugin.
It's because config submission removes the BranchProjectProperty, whose existence is checked before syncing.
This one will be tricky to fix, because without that property during sync, there are bound to be a lot of NPEs. Need to investigate further.
Which fields are you changing?
There is an outstanding issue
JENKINS-21017which causes configuration to not be updated when updating by XML. This is the mechanism multi-branch-project-plugin uses to apply changes to the sub-projects. I have workarounds in place for a couple fields https://github.com/jenkinsci/multi-branch-project-plugin/blob/multi-branch-project-plugin-0.5/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/TemplateDrivenBranchProjectFactory.java#L128