[
https://issues.apache.org/jira/browse/HBASE-21427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16675250#comment-16675250
]
Sean Busbey commented on HBASE-21427:
-------------------------------------
IIRC it was not easy to do this because of how multi-branch pipelines work in
jenkins.
What if we moved this stuff into its own repo, something like {{hbase-ci}}? we
could probably remove most of {{dev-support}}. we'd need to refactor things a
bit since the job would have to manage what branches are tested itself, but
we'd gain the ability to throttle ourselves project wide as opposed to now
where it's per-branch.
I went the per-branch route originally because it's what the jenkins docs
encourage and it means we automagically have an equivalent amount of testing of
new feature branches as the main branch. But I don't think folks are aware of
the amount of testing done by default when they make a branch. Centralizing
things would flip this around and make folks opt-in to it. We'd need to
document that as a part of docs about "how to make a feature branch".
> Make it so flakie's and nightlies build rates are configurable from jenkins
> Config page
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-21427
> URL: https://issues.apache.org/jira/browse/HBASE-21427
> Project: HBase
> Issue Type: Improvement
> Components: test
> Reporter: stack
> Priority: Major
>
> Request is that rather than have to change code whenever we want to change
> build rates, would be easier doing change in jenkins Config screen.
> My guess is easy enough to do... .
> ^^
> [~busbey] Lets chat.... (or I could bang my head)
> See HBASE-21424 for a bit of background.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
