Quite a nice read! This might be a step in the right direction!
One question though: currently I control the whole build with a single Perl script. It doesn't matter if I'm on Windows or Linux (eg it reads env-vars I set on the nodes)... So how would I write that with literate builds? Add another environment above the three you mentioned? Or is there another way to describe the build without having to reference the environments?
On 03.10.2013 19:55, Stephen Connolly wrote:
http://jenkins-ci.org/content/literate-builds-wtf On Thursday, 3 October 2013, Roland Asmann wrote: I'm not quite sure what you mean with 'literate builds'... Do you mean splitting them in multiple jobs? On Thursday, October 3, 2013 6:27:10 PM UTC+2, Stephen Connolly wrote: Of course with literate builds you get a much easier way: Here's the markdown you'd have # Environments * `debian` * `i386` * `x64` * `redhat` * `i386` * `x64` * `windows` # Build * `debian` whatever command you use to make the deb * `redhat` rpmbuild blah blah blah * `windows` whatever command you use to make the exe On 3 October 2013 17:11, Roland Asmann <[email protected]> wrote: Hi guys, I need some help with a matrix-build. Until now, I had the build configured to run on all nodes that have a label 'deb' and 'rpm' as axis 'distro' combined with axis 'arch' which checks on 'i386' and 'x64'. This is because we are building some binaries that are specific for i386 and x64 and packaging the builds depending in either RPM or DEB. So in all, we had 4 artifacts resulting. Now, I need to add another distro-type, namely a Windows EXE. The thing is that this doesn't have to be built on both architectures, since the project will only create a 32-bit binary. I know I can set the matrix to invalidate the combination 'exe' and 'x64', but that is not exactly doing what I want. If I would do this, it would never build my EXE on a 64-bit node, but I would like to have these nodes included in the build-pool as well! The nodes will need to have the label 'x64' set for some other builds I have, so changing them to 'i386' is also not an option. So, the question is, how can I setup the build to run the following 'combinations': - deb x i386 - deb x x64 - rpm x i386 - rpm x x64 - exe and have the 'exe' run on any available machine that has the label 'exe', no matter if it has the label 'i386' or 'x64'? Any help is greatly appreciated! Roland -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@__googlegroups.com. For more options, visit https://groups.google.com/__groups/opt_out <https://groups.google.com/groups/opt_out>. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <javascript:_e({}, 'cvml', 'jenkinsci-users%[email protected]');>. For more options, visit https://groups.google.com/groups/opt_out. -- Sent from my phone -- You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/0ujfEFyJ5Xs/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
