Brent,

Thanks for the lead. I will dig into it. It seems there is a light at the
end of my tunnel :)
Thanks a lot!

Jozo

On Fri, Apr 17, 2015 at 12:04 AM, Brent Atkinson <[email protected]>
wrote:

> Hi Jozo,
>
> Yes, you should be able to do something like that. However, your feeling
> isn't quite right: it is fairly common for people to provision hosts and
> tear-down them down part of the build. One reason this is advantageous is
> that your "cleanup" can fail and then your build environment is corrupt and
> builds start failing (or worse, don't fail but yield bad output silently).
>
> Just as an example, here's a group doing it with Vagrant and VMs:
> http://pivotallabs.com/spinning-useful-vms-quickly-vagrant-puppet-puppet-forge/
>
> Brent
>
> On Thu, Apr 16, 2015 at 5:51 PM, Jozef Vilcek <[email protected]>
> wrote:
>
>> Actually, Jenkins build environment I use does distributed builds (I do
>> not manage this). I have a feeling that agent setup is rather static.
>> Projects I need to build have native dependencies, which can change a lot.
>> There are many projects, they share build cluster and there dependencies
>> can be often in conflict.
>>
>> Can I do something like:
>> * setup an agent with desired OS and basic setup (libraries)
>> * project X build gets triggered
>> * project is assigned to the agent
>> * pre-build step is executed, which takes from workspace file list of
>> libraries specific to project X and install them
>> * maven build is executed -> everything is green
>> * cleanup
>> * ...
>> * project Y build gets triggered
>> * by chance, it is assigned to the same agent
>> * there is no trace of any library installed by project X
>> * pre-build step installs libraries specific to project Y
>> * ... etc
>>
>> On Thu, Apr 16, 2015 at 11:33 PM, Brent Atkinson <
>> [email protected]> wrote:
>>
>>> Hi Jozo,
>>>
>>> Yes, I was using the less incendiary term for the distributed build
>>> agents (or slaves), so you found the right docs.
>>>
>>> "Container" was referring to something like, but not necessarily Docker
>>> containers.
>>>
>>> When you use agents, you are typically do it to:
>>>
>>>   * unload the load from the build master
>>>   * need to build on different operating system or architecture from the
>>> master
>>>   * need to build in an isolated or preconfigured environment different
>>> from the master
>>>
>>> That last one would seem to align with your question, unless there's a
>>> reason you didn't want to use distributed builds.
>>>
>>> Hope that helps,
>>>
>>> Brent
>>>
>>> --
>>> 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/ZISjWJ48VNY/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GGSvDR29di81zROJn3A6d5G7vtK4mF7gZ7CWEwS%3D5GFw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GGSvDR29di81zROJn3A6d5G7vtK4mF7gZ7CWEwS%3D5GFw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> 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].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CAOUjMkwvAoOYTEt8s9d7rKu_GHMurugSHWsQV%3DfFtmZmfbra%3Dw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAOUjMkwvAoOYTEt8s9d7rKu_GHMurugSHWsQV%3DfFtmZmfbra%3Dw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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/ZISjWJ48VNY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0EzDORvkwntDYSMnK92iZ_nTocRU0Qfwt1cMmVfW-cVwA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0EzDORvkwntDYSMnK92iZ_nTocRU0Qfwt1cMmVfW-cVwA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAOUjMkwnWEXVdiMfHY61LH_dZ9uHTDmJ3vSAA3WY_f5RTR5pfw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to