Skip to contentSkip to conversation

Toaster integration with Jenkins

RFC Barros Pena, Belen 3 participants 6 messages Mar 30, 2015 – Apr 1, 2015

lore
Share & tools
lore
#1 lore raw
Quoted 8 lines · Belen

We are considering working on integrating Toaster with Jenkins as part of the next Yocto Project release. Our thinking so far is collected in this Bugzilla feature:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=7527

Any thoughts? Are we missing something? Are we going about it in a completely wrong way?

I think is a great idea and will be really useful for some current infrastructures

Best regards

Victor Rodriguez

Quoted 12 lines

Let us know.

Thanks!

Belén

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#2 lore raw
In reply to Barros Pena, Belen

Hi,

Quoted 5 lines · Barros Pena, Belen

We are considering working on integrating Toaster with Jenkins as part of the next Yocto Project release. Our thinking so far is collected in this Bugzilla feature:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=7527

Ah, sounds really interesting. I've recently been thinking about how I should be able to benefit from toaster, as we're running out automated builds using Jenkins.

Quoted 2 lines

Any thoughts? Are we missing something? Are we going about it in a completely wrong way?

Sounds quite good to me.

If there's some project configuration that needs to be done in Toaster, I'd appreciate if as much as possible could be retrieved from our current Jenkins setup (i.e. exported from the Jenkins plugin to Toaster). (Not least as we're running a couple of scripts to source the environment and handling some extra configurations needed; thus I'd assume we couldn't just take the freestyle Jenkins project talked about in b) of Alexandru 's first comment in #YOCTO-7527.

I don't know if this is the right thread but a couple of other things that we really would need in order to fully be able to utilize this.

1) Some way of getting the built git branch shown in toaster. (As we discussed on YPDD in Düsseldorf together with Axis). We're building master and release branches for the same machine and image.

2) In the proposed bug, would toaser be able to recieve and handle toaster/build logs from different YP releases? Normally we've at least one active release branch, and possibly a master (or master-next) branch that's going to the next YP release. If possible, I'd like to visualize all this in the same Toaster instance.

Apart from that, I think this is really interesting!

Cheers,
Anders

Signature · 2 lines
Anders Darander
ChargeStorm AB / eStorm AB
#3 lore raw

Hi Anders,

Thanks for the comments. Some answers inline.

Cheers

Belén

Quoted 19 lines · Anders Darander

Hi,

Quoted 6 lines · Barros Pena, Belen

We are considering working on integrating Toaster with Jenkins as part of
the next Yocto Project release. Our thinking so far is collected in this Bugzilla feature:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=7527

Ah, sounds really interesting. I've recently been thinking about how I should be able to benefit from toaster, as we're running out automated builds using Jenkins.

Quoted 2 lines

Any thoughts? Are we missing something? Are we going about it in a completely wrong way?

Sounds quite good to me.

Quoted 7 lines

If there's some project configuration that needs to be done in Toaster, I'd appreciate if as much as possible could be retrieved from our current Jenkins setup (i.e. exported from the Jenkins plugin to Toaster). (Not least as we're running a couple of scripts to source the environment and handling some extra configurations needed; thus I'd assume we couldn't just take the freestyle Jenkins project talked about in b) of Alexandru 's first comment in #YOCTO-7527.

I will add this to the Bugzilla entry, so that we keep track of all possible issues.

Quoted 7 lines

I don't know if this is the right thread but a couple of other things that we really would need in order to fully be able to utilize this.

1) Some way of getting the built git branch shown in toaster. (As we discussed on YPDD in Düsseldorf together with Axis). We're building master and release branches for the same machine and image.

If you mean the name of the branch, Toaster currently shows this in several places. One of them is the configuration information for a finished build, which displays a list of the layers used, and for each of them the branch name and the commit used. I've uploaded an screenshot here

http://i.imgur.com/GPDwCh0.png

Quoted 3 lines

2) In the proposed bug, would toaser be able to recieve and handle toaster/build logs from different YP releases?

Yes, but you would need to create a Toaster project for each release. Currently, for each Toaster project, you must select the YP release you want to use. A project can only use a single release at any given time.

Quoted 13 lines

Normally we've at least
one active release branch, and possibly a master (or master-next) branch that's going to the next YP release. If possible, I'd like to visualize all this in the same Toaster instance.

Apart from that, I think this is really interesting!

Cheers,
Anders

Signature · 2 lines
Anders Darander
ChargeStorm AB / eStorm AB
#4 lore raw

Hi,

Quoted 9 lines · Barros Pena, Belen
Quoted 6 lines · Anders Darander

I don't know if this is the right thread but a couple of other things that we really would need in order to fully be able to utilize this.

1) Some way of getting the built git branch shown in toaster. (As we discussed on YPDD in Düsseldorf together with Axis). We're building master and release branches for the same machine and image.

Quoted 6 lines

If you mean the name of the branch, Toaster currently shows this in several places. One of them is the configuration information for a finished build, which displays a list of the layers used, and for each of them the branch name and the commit used. I've uploaded an screenshot here

http://i.imgur.com/GPDwCh0.png

Good to know. Just one question, is it possible to get the branch information for one layer on the "All build" page? To avoid having to go into each build to actually see what kind of build that was.

For instance, we're having a master layer, that checks out other layers as submodules. Being able to direclty see which branch of the master all builds originate from would be extremely useful (or another option would be if the Jenkins job name could be shown, as that would provide more or less the same information for us).

Hm, thinking more about that, being able to store the Jenkins job name and build number in the toaster database would likely be really usefull. That would allow Toaster to link back to the actual job and build in Jenkins. Those could be retrieved from the environmant variables BUILD_NUMBER and JOB_NAME in the Jenkins build.

Quoted 6 lines
Quoted 2 lines

2) In the proposed bug, would toaser be able to recieve and handle toaster/build logs from different YP releases?

Yes, but you would need to create a Toaster project for each release. Currently, for each Toaster project, you must select the YP release you want to use. A project can only use a single release at any given time.

I've just spent a couple of minutes looking for this (so excuse me if it's obvious).

A Toaster project in this case, would that equal to different toaster instances and databases, or would they still be able to be shown together in the same "All builds" page? If it's not the latter, it would be a nice feature for some upcoming release. (Though, it'll obviously make the implementation slightly harder as support for older YP releases would need to be kept).

Cheers,
Anders

Signature · 2 lines
Anders Darander
ChargeStorm AB / eStorm AB
#5 lore raw
Quoted 19 lines · Anders Darander

Hi,

Quoted 15 lines · Barros Pena, Belen
Quoted 6 lines · Anders Darander

I don't know if this is the right thread but a couple of other things that we really would need in order to fully be able to utilize this.

1) Some way of getting the built git branch shown in toaster. (As we discussed on YPDD in Düsseldorf together with Axis). We're building master and release branches for the same machine and image.

If you mean the name of the branch, Toaster currently shows this in several places. One of them is the configuration information for a finished build, which displays a list of the layers used, and for each of
them the branch name and the commit used. I've uploaded an screenshot here

Quoted 4 lines
Quoted 1 line

http://i.imgur.com/GPDwCh0.png

Good to know. Just one question, is it possible to get the branch information for one layer on the "All build" page?

Not right now, I'm afraid. Having said that, it is probably fairly easy to add that information to the table.

Quoted 9 lines

To avoid having to go
into each build to actually see what kind of build that was.

For instance, we're having a master layer, that checks out other layers as submodules.
Being able to direclty see which branch of the master all builds originate from would be extremely useful (or another option would be if the Jenkins job name could be shown, as that would provide more or less the same information for us).

This we could probably do, since builds connected to a Jenkins instance will need to be identifiable somehow in Toaster.

Quoted 3 lines

Hm, thinking more about that, being able to store the Jenkins job name and build number in the toaster database would likely be really useful.

Again, I'd say this is possible.

Quoted 3 lines

That would allow Toaster to link back to the actual job and build in Jenkins. Those could be retrieved from the environmant variables BUILD_NUMBER and JOB_NAME in the Jenkins build.

This sounds like a handy feature.

Quoted 8 lines
Quoted 7 lines
Quoted 3 lines

2) In the proposed bug, would toaser be able to recieve and handle toaster/build logs from different YP releases?

Yes, but you would need to create a Toaster project for each release. Currently, for each Toaster project, you must select the YP release you want to use. A project can only use a single release at any given time.

Quoted 6 lines

I've just spent a couple of minutes looking for this (so excuse me if it's obvious).

A Toaster project in this case, would that equal to different toaster instances and databases, or would they still be able to be shown together in the same "All builds" page?

Sorry, I should have explained better: in the same Toaster instance (and database). Each Toaster instance can have n projects. Each project is associated to a single release. So you can build on different releases within the same Toaster instance by using different projects, and access all the information through the 'all builds' page.

Quoted 11 lines

If it's not the latter, it would
be a nice feature for some upcoming release. (Though, it'll obviously make the implementation slightly harder as support for older YP releases would need to be kept).

Cheers,
Anders

Signature · 2 lines
Anders Darander
ChargeStorm AB / eStorm AB