[Buildbot] #3550: Feature: Implement renderables on locks property

Buildbot trac trac at buildbot.net
Tue May 10 16:59:37 UTC 2016

#3550: Feature: Implement renderables on locks property
Reporter:  mattiasr     |      Owner:
    Type:  enhancement  |     Status:  new
Priority:  minor        |  Milestone:  undecided
 Version:  0.8.12       |   Keywords:
 As a developer i would like to generate locks based on the current branch
 i'm building using AnyScheduler.

 We have a publish step that takes our rpm artifact and genereates metadata
 in our yum repositories based on several criterias.

 stability of package (eg. head, stage)
 namespace of yum repo to deploy to (eg. application, internal)
 type of package (eg. debuginfo, srpm, updates)
 branch (eg. master, bugfix/something, feature/something)

 We need an exclusive lock on this step due to the metadata would be
 corrupt if we build on the same area on several builders at the same time.

 But if we can distinguish by namespace, stability, type of package and
 branch as an renderable we could allow several publish to be run working
 on different areas.

 head/centos/6/x86_64/application/master/updates would not affect

 or head/centos/6/x86_64/application/master/SRPM would not affect

 or head/centos/6/x86_64/internal/bugfix/INFRA-123/updates would not affect

 and so on.

 This would mean that we can scale out in number of slaves and cut the
 feedback loop for developers by a great deal.

 This would also mean that when we come to release/tagging, we would save
 even more time and doesn't block developers as we do today ("It's
 codefreeze, stop pushing code so i can get on with my tagging")

 Best would be if this can be implemented on eight, but a fix in nine and
 we might be able to backport it to eight might be ok.

 Setting priority to minor, but for us it's a blocker right now.

Ticket URL: <http://trac.buildbot.net/ticket/3550>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation

More information about the bugs mailing list