Trying to make multibranch support with not messed buildhistory by reusing
my flexible github triggering code and experience. Have some questions
after first scm/branch/freestyle API reading impression:
- Why uncategorized view is primary
jenkins.branch.MultiBranchProjectViewHolder#getViews and how to set own
primary view?
- Why uncategorized DEFAULT view (category) is named "Branch" by default?
- Freestyle-multibranch uses
observer jenkins.branch.MultiBranchProject.SCMHeadObserverImpl#observe is
it possible to replace it with custom logic?
This observer is not flexible and not extendable, it can do only simple
case comparison this vs that by revision. How to run the same build if it
was already built? Revision+Head are not enough information.
(Probably this is an answer why there is still no smart messages for
rebuilds.
if (rebuild) {
listener.getLogger().format(
"%s reopened: %s (%s)%n",) < why API expects defined
behavior? Again, what if i want rebuild by comment, date, other ifluence?
One more place of decision making is SCMSourceCriteria... Oh, and
Trait(?)... And BranchPropertyStrategy... How much places are designed for
decision making and influence on final result?
Can i decide in one (my) place and just return to multibranch my decision:
"this head, branch, etc should be built, please create views by
corresponding SCMHeadCategory, etc" Or just not call observe and bypass it?
- Is State.class expected to be used as persistent storage of data for
plugins? If yes, then how to control exceptions during xmlread to exclude
data clearing?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/5e646943-4151-4084-9f92-89788467a5ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
