Bootstrap latest does not work with buildbot-www.

[llloret]

As suggested by Dustin, I am trying to have a go at the nine branch, and when trying to setup the buildbot-www, it seems like the current bootstrap version (3.0.0) is not compatible with buildbot. Version 2.3.2 seems to be ok.

This patch makes sure that setup.py ask for 2.3.2 instead of latest.

[llloret]

I see that the usage of 3.0.0 was done very recently. So perhaps there are some things missing still in the repo?Perhaps I am trying to get into this while it is quite unstable.

Anyway, I am withdrawing the pull request, since I do not think it makes a lot of sense.

[llloret]

Sorry, I now have realized that I was working on an out of date nine branch.

[djmitche]

I did the same thing, and we only merged the 3.0.0 upgrade about 18h ago, so you weren't that out of date! Thank you for having a look, and please let us know what else you see. Do check out README.md too.

[llloret]

Hi,

I have had a look at this, and I have been able to successfully launch a
browser and see the mock of the new Web UI. But it is not very clear how I
could help with this. Is there somewhere to have a look at and see what
needs implementing on buildbot-www, with a bit more of detail (I have seen
the notes about Nine)?

I guess what I am asking for is for some initial information on how to best
start helping (or try at least) with this.

Thanks,
Luis

On Wed, Aug 14, 2013 at 2:20 PM, Dustin J. Mitchell <
notifications@github.com> wrote:

I did the same thing, and we only merged the 3.0.0 upgrade about 18h ago,
so you weren't that out of date! Thank you for having a look, and
please let us know what else you see. Do check out README.md too.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/828#issuecomment-22634593
.

[djmitche]

Well, that depends on what sort of thing you'd like to work on. It sounds
like you're interested in the frontend, in which case I'd point you to
@tardyp for guidance, although I'd suspect that anything you choose, and
any way you choose to do it, will be fine. Filling in some of the existing
but empty or fake views would be great. Most of the UI is table-based
right now, which is fine, but there may be better UI concepts that we could
use. We'll also need to implement some comprehensive views with strengths
similar to waterfall, grid, and console.

If you're more interested in the Python or backend-JS side, let me know.

[llloret]

Well, to be honest I do not have a lot of experience on JavaScript, but I
do would not mind having a stab at it. It seems like there is a lot top do
on this front.

Anyway, if you can think of something that is not in the frontend, I would
be happy to have a look and see if I could help.

Sent from mobile
On 14 Aug 2013 19:14, "Dustin J. Mitchell" notifications@github.com wrote:

Well, that depends on what sort of thing you'd like to work on. It sounds
like you're interested in the frontend, in which case I'd point you to
@tardyp for guidance, although I'd suspect that anything you choose, and
any way you choose to do it, will be fine. Filling in some of the existing
but empty or fake views would be great. Most of the UI is table-based
right now, which is fine, but there may be better UI concepts that we could
use. We'll also need to implement some comprehensive views with strengths
similar to waterfall, grid, and console.

If you're more interested in the Python or backend-JS side, let me know.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/828#issuecomment-22655152
.

[djmitche]

None of us are well-versed in JS, so certainly another person reading the
code and figuring out how to hack on it will help make sure that's logical,
and probably find some bugs or omissions or room for improvement.

One of the big un-attempted projects in the backend is to rewrite the IRC
bot to listen to 'mq' messages and translate those properly into IRC
messages. If that's interesting to you, have at it!

[tardyp]

Even if you are not well-versed to JS, I can say that angularJS is really
fun to work on, and pretty easy to start with, once you get the
fundamentals.

Especially now that the app is starting to work, so that you have a few
example to look at.

Here are a list of few short term tasks:

Create build page:
get the list of steps, which updates automatically
have a few tabs to get some more details (build properties, change
source details, artifact lists)

Create builder page:
show current builds(updated), pending buildrequest (updated), and
finished builds

Those last tasks are more design tasks, with a lot of jade templates to
write, and bootstrap css coding.

There are also JS intensive tasks:
Create the formular generator for forced builds. There is some nice
algorithm to find out in order to layout the form so that it looks better
than we currently have,

CC dev-buildbot
Pierre

On Wed, Aug 14, 2013 at 8:36 PM, Dustin J. Mitchell <
notifications@github.com> wrote:

None of us are well-versed in JS, so certainly another person reading the
code and figuring out how to hack on it will help make sure that's logical,
and probably find some bugs or omissions or room for improvement.

One of the big un-attempted projects in the backend is to rewrite the IRC
bot to listen to 'mq' messages and translate those properly into IRC
messages. If that's interesting to you, have at it!

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/828#issuecomment-22657096
.

[llloret]

Yes, I have been having a look at the angularjs tutorial and it was quite
exciting indeed.

One thing I would like to ask: is there some infrastructure in place
already to serve the data to the frontend. I think I saw some hard coded
values for some tables on the web, but I was wondering if it is now
possible to get the data dynamically from buildbot.

Thanks

Sent from mobile
On 14 Aug 2013 20:21, "Pierre Tardy" notifications@github.com wrote:

Even if you are not well-versed to JS, I can say that angularJS is really
fun to work on, and pretty easy to start with, once you get the
fundamentals.

Especially now that the app is starting to work, so that you have a few
example to look at.

Here are a list of few short term tasks:

Create build page:
get the list of steps, which updates automatically
have a few tabs to get some more details (build properties, change
source details, artifact lists)

Create builder page:
show current builds(updated), pending buildrequest (updated), and
finished builds

Those last tasks are more design tasks, with a lot of jade templates to
write, and bootstrap css coding.

There are also JS intensive tasks:
Create the formular generator for forced builds. There is some nice
algorithm to find out in order to layout the form so that it looks better
than we currently have,

CC dev-buildbot
Pierre

On Wed, Aug 14, 2013 at 8:36 PM, Dustin J. Mitchell <
notifications@github.com> wrote:

None of us are well-versed in JS, so certainly another person reading
the
code and figuring out how to hack on it will help make sure that's
logical,
and probably find some bugs or omissions or room for improvement.

One of the big un-attempted projects in the backend is to rewrite the
IRC
bot to listen to 'mq' messages and translate those properly into IRC
messages. If that's interesting to you, have at it!

—
Reply to this email directly or view it on GitHub<
https://github.com/buildbot/buildbot/pull/828#issuecomment-22657096>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/828#issuecomment-22659866
.

[djmitche]

Yes - there's a nice REST API to the data API - see
master/docs/developer/{data,www}.rst.

[tardyp]

And the data is not hardcoded. It s auto generated from spec. :)
Le 14 août 2013 23:24, "Dustin J. Mitchell" notifications@github.com a
écrit :

Yes - there's a nice REST API to the data API - see
master/docs/developer/{data,www}.rst.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/828#issuecomment-22668148
.

[llloret]

Thanks for the pointers. I will start having a look at it and see what I
can do.

On Wed, Aug 14, 2013 at 10:45 PM, Pierre Tardy notifications@github.comwrote:

And the data is not hardcoded. It s auto generated from spec. :)
Le 14 août 2013 23:24, "Dustin J. Mitchell" notifications@github.com a
écrit :

Yes - there's a nice REST API to the data API - see
master/docs/developer/{data,www}.rst.

—
Reply to this email directly or view it on GitHub<
https://github.com/buildbot/buildbot/pull/828#issuecomment-22668148>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/828#issuecomment-22669720
.

[llloret]

Hi,

I have been having a look at trying to start contributing to buildbot-www
and decided that the easiest way to start (and learn) was to create a new
page, something like the old Changesources one. So there I went, and this
is what I have seen and done so far:

• I made a simple jade template (with an ng-repeat, like the one in
  builders)
• I made a simple controller
• I added the new route to the angularjs route component
• ...

So, now I am at the point where I can see my new page, nicely rendered, but
the data that it shows in the table does not make any sense. I think it is
showing the methods that restangular objects get added when they are
restangularized. This is in the buildbotService component, I think.

I see that this happens as well in the builders page, so I am thinking: are
we sure that the buildbotService is returning the right data?

This is what I see it is returning (for changesources) (you can see that
the element 0 holds the 2 valid changesources I have configured, element 1
contains something else, and then there is a lot of things that I am not
sure what they are doing there):

---

{
changesources: {
0:
[ {
changesourceid: 1
link: http://localhost:8020/api/v2/changesource/1
master: {
active: true
last_active: 1376575201
link: http://localhost:8020/api/v2/master/1
masterid: 1
name: luis-minmate:/home/luis/buildbot/master9
}
name: http://myserver.com/svn/is/trunk/
} , {
changesourceid: 2
link: http://localhost:8020/api/v2/changesource/2
master: {
active: true
last_active: 1376575201
link: http://localhost:8020/api/v2/master/1
masterid: 1
name: luis-minmate:/home/luis/buildbot/master9
}
name: http://myserver.com/svn/is/branches/Virtua/
} ]
1: {
links:
[ {
href: http://localhost:8020/api/v2/changesource
rel: self
} ]
total: 2
route: changesource
getRestangularUrl: null
addRestangularMethod: null
one: null
all: null
parentResource: null
restangularCollection: false
get: null
getList: null
put: null
post: null
remove: null
head: null
trace: null
options: null
patch: null
customOperation: null
doPUT: null
customPUT: null
doPOST: null
customPOST: null
doGET: null
customGET: null
doDELETE: null
customDELETE: null
customGETLIST: null
doGETLIST: null
bind: null
unbind: null
on: null
}
changesources: {
$ref: $["0"]
}
meta: {
$ref: $["1"]
}
route: changesource
getRestangularUrl: null
addRestangularMethod: null
one: null
all: null
parentResource: null
restangularCollection: true
post: null
head: null
trace: null
putElement: null
options: null
patch: null
getList: null
customOperation: null
doPUT: null
customPUT: null
doPOST: null
customPOST: null
doGET: null
customGET: null
doDELETE: null
customDELETE: null
customGETLIST: null
doGETLIST: null
bind: null
unbind: null
on: null
}
}

---

Am I missing something in here? Let me know if you need any more info.
Thanks,
Luis

On Wed, Aug 14, 2013 at 10:45 PM, Pierre Tardy notifications@github.comwrote:

And the data is not hardcoded. It s auto generated from spec. :)
Le 14 août 2013 23:24, "Dustin J. Mitchell" notifications@github.com a
écrit :

Yes - there's a nice REST API to the data API - see
master/docs/developer/{data,www}.rst.

—
Reply to this email directly or view it on GitHub<
https://github.com/buildbot/buildbot/pull/828#issuecomment-22668148>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/828#issuecomment-22669720
.

[llloret]

An update: I can make this kind of work, by doing the follwoing on the
template:
tr(ng-repeat='changesource in changesources[0]')
td {{changesource.name}}

So I use changesources[0]... but I am not sure that's the right way to do
it. I guess it should be returned differently as part of the restangular
call.

BTW, by doing the equivalent change in the builders template, it gets the
right thing too: "tr(ng-repeat='builder in builders[0]')" instead of
"tr(ng-repeat='builder in builders')".

Another thought: I would expect that the return from restangular would be
very much like what you get on the REST itself, but it is not the case. Are
my expectations wrong. Keep in mind that I am pretty new to all this
technology, so I may be very very off-track.

Thanks,
Luis

On Thu, Aug 15, 2013 at 3:55 PM, Luis Lloret luislloret@gmail.com wrote:

Hi,

I have been having a look at trying to start contributing to buildbot-www
and decided that the easiest way to start (and learn) was to create a new
page, something like the old Changesources one. So there I went, and this
is what I have seen and done so far:

• I made a simple jade template (with an ng-repeat, like the one in
  builders)
• I made a simple controller
• I added the new route to the angularjs route component
• ...

So, now I am at the point where I can see my new page, nicely rendered,
but the data that it shows in the table does not make any sense. I think it
is showing the methods that restangular objects get added when they are
restangularized. This is in the buildbotService component, I think.

I see that this happens as well in the builders page, so I am thinking:
are we sure that the buildbotService is returning the right data?

This is what I see it is returning (for changesources) (you can see that
the element 0 holds the 2 valid changesources I have configured, element 1
contains something else, and then there is a lot of things that I am not
sure what they are doing there):

---

{
changesources: {
0:
[ {
changesourceid: 1
link: http://localhost:8020/api/v2/changesource/1
master: {
active: true
last_active: 1376575201
link: http://localhost:8020/api/v2/master/1
masterid: 1
name: luis-minmate:/home/luis/buildbot/master9
}
name: http://myserver.com/svn/is/trunk/
} , {
changesourceid: 2
link: http://localhost:8020/api/v2/changesource/2
master: {
active: true
last_active: 1376575201
link: http://localhost:8020/api/v2/master/1
masterid: 1
name: luis-minmate:/home/luis/buildbot/master9
}
name: http://myserver.com/svn/is/branches/Virtua/
} ]
1: {
links:
[ {
href: http://localhost:8020/api/v2/changesource
rel: self
} ]
total: 2
route: changesource
getRestangularUrl: null
addRestangularMethod: null
one: null
all: null
parentResource: null
restangularCollection: false
get: null
getList: null
put: null
post: null
remove: null
head: null
trace: null
options: null
patch: null
customOperation: null
doPUT: null
customPUT: null
doPOST: null
customPOST: null
doGET: null
customGET: null
doDELETE: null
customDELETE: null
customGETLIST: null
doGETLIST: null
bind: null
unbind: null
on: null
}
changesources: {
$ref: $["0"]
}
meta: {
$ref: $["1"]
}
route: changesource
getRestangularUrl: null
addRestangularMethod: null
one: null
all: null
parentResource: null
restangularCollection: true
post: null
head: null
trace: null
putElement: null
options: null
patch: null
getList: null
customOperation: null
doPUT: null
customPUT: null
doPOST: null
customPOST: null
doGET: null
customGET: null
doDELETE: null
customDELETE: null
customGETLIST: null
doGETLIST: null
bind: null
unbind: null
on: null
}
}

---

Am I missing something in here? Let me know if you need any more info.
Thanks,
Luis

On Wed, Aug 14, 2013 at 10:45 PM, Pierre Tardy notifications@github.comwrote:

And the data is not hardcoded. It s auto generated from spec. :)
Le 14 août 2013 23:24, "Dustin J. Mitchell" notifications@github.com a
écrit :

Yes - there's a nice REST API to the data API - see
master/docs/developer/{data,www}.rst.

—
Reply to this email directly or view it on GitHub<
https://github.com/buildbot/buildbot/pull/828#issuecomment-22668148>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/828#issuecomment-22669720
.

[llloret]

Ok, yet another update.

This seems to work too, if I remove the [0] from the views code (which I
think is the correct thing to do) and I add a [0] in the BuildbotService,
like below:
p.then((v) ->
$scope[scope_key] = v[0] # this was = v. before
elem.on("new", onEvent)
return v

Does that make sense? I reached this conclusion after seeing what v was in
the debugger. It had all the methods from Restangular, which I guess are
not necessary to pass the views.

If useful, I can update into my fork and someone can have a look at the
diffs to see if they make sense at all...
Luis

On Thu, Aug 15, 2013 at 4:31 PM, Luis Lloret luislloret@gmail.com wrote:

An update: I can make this kind of work, by doing the follwoing on the
template:
tr(ng-repeat='changesource in changesources[0]')
td {{changesource.name}}

So I use changesources[0]... but I am not sure that's the right way to do
it. I guess it should be returned differently as part of the restangular
call.

BTW, by doing the equivalent change in the builders template, it gets the
right thing too: "tr(ng-repeat='builder in builders[0]')" instead of
"tr(ng-repeat='builder in builders')".

Another thought: I would expect that the return from restangular would be
very much like what you get on the REST itself, but it is not the case. Are
my expectations wrong. Keep in mind that I am pretty new to all this
technology, so I may be very very off-track.

Thanks,
Luis

On Thu, Aug 15, 2013 at 3:55 PM, Luis Lloret luislloret@gmail.com wrote:

Hi,

I have been having a look at trying to start contributing to buildbot-www
and decided that the easiest way to start (and learn) was to create a new
page, something like the old Changesources one. So there I went, and this
is what I have seen and done so far:

• I made a simple jade template (with an ng-repeat, like the one in
  builders)
• I made a simple controller
• I added the new route to the angularjs route component
• ...

So, now I am at the point where I can see my new page, nicely rendered,
but the data that it shows in the table does not make any sense. I think it
is showing the methods that restangular objects get added when they are
restangularized. This is in the buildbotService component, I think.

I see that this happens as well in the builders page, so I am thinking:
are we sure that the buildbotService is returning the right data?

This is what I see it is returning (for changesources) (you can see that
the element 0 holds the 2 valid changesources I have configured, element 1
contains something else, and then there is a lot of things that I am not
sure what they are doing there):

---

{
changesources: {
0:
[ {
changesourceid: 1
link: http://localhost:8020/api/v2/changesource/1
master: {
active: true
last_active: 1376575201
link: http://localhost:8020/api/v2/master/1
masterid: 1
name: luis-minmate:/home/luis/buildbot/master9
}
name: http://myserver.com/svn/is/trunk/
} , {
changesourceid: 2
link: http://localhost:8020/api/v2/changesource/2
master: {
active: true
last_active: 1376575201
link: http://localhost:8020/api/v2/master/1
masterid: 1
name: luis-minmate:/home/luis/buildbot/master9
}
name: http://myserver.com/svn/is/branches/Virtua/
} ]
1: {
links:
[ {
href: http://localhost:8020/api/v2/changesource
rel: self
} ]
total: 2
route: changesource
getRestangularUrl: null
addRestangularMethod: null
one: null
all: null
parentResource: null
restangularCollection: false
get: null
getList: null
put: null
post: null
remove: null
head: null
trace: null
options: null
patch: null
customOperation: null
doPUT: null
customPUT: null
doPOST: null
customPOST: null
doGET: null
customGET: null
doDELETE: null
customDELETE: null
customGETLIST: null
doGETLIST: null
bind: null
unbind: null
on: null
}
changesources: {
$ref: $["0"]
}
meta: {
$ref: $["1"]
}
route: changesource
getRestangularUrl: null
addRestangularMethod: null
one: null
all: null
parentResource: null
restangularCollection: true
post: null
head: null
trace: null
putElement: null
options: null
patch: null
getList: null
customOperation: null
doPUT: null
customPUT: null
doPOST: null
customPOST: null
doGET: null
customGET: null
doDELETE: null
customDELETE: null
customGETLIST: null
doGETLIST: null
bind: null
unbind: null
on: null
}
}

---

Am I missing something in here? Let me know if you need any more info.
Thanks,
Luis

On Wed, Aug 14, 2013 at 10:45 PM, Pierre Tardy notifications@github.comwrote:

And the data is not hardcoded. It s auto generated from spec. :)
Le 14 août 2013 23:24, "Dustin J. Mitchell" notifications@github.com
a
écrit :

Yes - there's a nice REST API to the data API - see
master/docs/developer/{data,www}.rst.

—
Reply to this email directly or view it on GitHub<
https://github.com/buildbot/buildbot/pull/828#issuecomment-22668148>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/828#issuecomment-22669720
.

[llloret]

Can you show the code? Please just make anew PR and we all discuss it
there...
Le 15 août 2013 19:17, "Luis Lloret" luislloret@gmail.com a écrit :

Ok, yet another update.

This seems to work too, if I remove the [0] from the views code (which I
think is the correct thing to do) and I add a [0] in the BuildbotService,
like below:
p.then((v) ->
$scope[scope_key] = v[0] # this was = v.
before
elem.on("new", onEvent)
return v

Does that make sense? I reached this conclusion after seeing what v was in
the debugger. It had all the methods from Restangular, which I guess are
not necessary to pass the views.

If useful, I can update into my fork and someone can have a look at the
diffs to see if they make sense at all...
Luis

On Thu, Aug 15, 2013 at 4:31 PM, Luis Lloret luislloret@gmail.com wrote:

An update: I can make this kind of work, by doing the follwoing on the
template:
tr(ng-repeat='changesource in changesources[0]')
td {{changesource.name}}

So I use changesources[0]... but I am not sure that's the right way to do
it. I guess it should be returned differently as part of the restangular
call.

BTW, by doing the equivalent change in the builders template, it gets the
right thing too: "tr(ng-repeat='builder in builders[0]')" instead of
"tr(ng-repeat='builder in builders')".

Another thought: I would expect that the return from restangular would be
very much like what you get on the REST itself, but it is not the case. Are
my expectations wrong. Keep in mind that I am pretty new to all this
technology, so I may be very very off-track.

Thanks,
Luis

On Thu, Aug 15, 2013 at 3:55 PM, Luis Lloret luislloret@gmail.comwrote:

Hi,

I have been having a look at trying to start contributing to
buildbot-www and decided that the easiest way to start (and learn) was to
create a new page, something like the old Changesources one. So there I
went, and this is what I have seen and done so far:

• I made a simple jade template (with an ng-repeat, like the one in
  builders)
• I made a simple controller
• I added the new route to the angularjs route component
• ...

So, now I am at the point where I can see my new page, nicely rendered,
but the data that it shows in the table does not make any sense. I think it
is showing the methods that restangular objects get added when they are
restangularized. This is in the buildbotService component, I think.

I see that this happens as well in the builders page, so I am thinking:
are we sure that the buildbotService is returning the right data?

This is what I see it is returning (for changesources) (you can see that
the element 0 holds the 2 valid changesources I have configured, element 1
contains something else, and then there is a lot of things that I am not
sure what they are doing there):

---

{
changesources: {
0:
[ {
changesourceid: 1
link: http://localhost:8020/api/v2/changesource/1
master: {
active: true
last_active: 1376575201
link: http://localhost:8020/api/v2/master/1
masterid: 1
name: luis-minmate:/home/luis/buildbot/master9
}
name: http://myserver.com/svn/is/trunk/
} , {
changesourceid: 2
link: http://localhost:8020/api/v2/changesource/2
master: {
active: true
last_active: 1376575201
link: http://localhost:8020/api/v2/master/1
masterid: 1
name: luis-minmate:/home/luis/buildbot/master9
}
name: http://myserver.com/svn/is/branches/Virtua/
} ]
1: {
links:
[ {
href: http://localhost:8020/api/v2/changesource
rel: self
} ]
total: 2
route: changesource
getRestangularUrl: null
addRestangularMethod: null
one: null
all: null
parentResource: null
restangularCollection: false
get: null
getList: null
put: null
post: null
remove: null
head: null
trace: null
options: null
patch: null
customOperation: null
doPUT: null
customPUT: null
doPOST: null
customPOST: null
doGET: null
customGET: null
doDELETE: null
customDELETE: null
customGETLIST: null
doGETLIST: null
bind: null
unbind: null
on: null
}
changesources: {
$ref: $["0"]
}
meta: {
$ref: $["1"]
}
route: changesource
getRestangularUrl: null
addRestangularMethod: null
one: null
all: null
parentResource: null
restangularCollection: true
post: null
head: null
trace: null
putElement: null
options: null
patch: null
getList: null
customOperation: null
doPUT: null
customPUT: null
doPOST: null
customPOST: null
doGET: null
customGET: null
doDELETE: null
customDELETE: null
customGETLIST: null
doGETLIST: null
bind: null
unbind: null
on: null
}
}

---

Am I missing something in here? Let me know if you need any more info.
Thanks,
Luis

On Wed, Aug 14, 2013 at 10:45 PM, Pierre Tardy <notifications@github.com

wrote:

And the data is not hardcoded. It s auto generated from spec. :)
Le 14 août 2013 23:24, "Dustin J. Mitchell" notifications@github.com
a
écrit :

Yes - there's a nice REST API to the data API - see
master/docs/developer/{data,www}.rst.

—
Reply to this email directly or view it on GitHub<
https://github.com/buildbot/buildbot/pull/828#issuecomment-22668148>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/828#issuecomment-22669720
.

---

Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk

---

Buildbot-devel mailing list
Buildbot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/buildbot-devel