On 10/1/13 10:53 AM, "Ferenc Kovacs" <[email protected]> wrote:
Hi Ferenc,
> If you want, you can install ssh on your build nodes, then execute the
> shell script via ssh. That way you can stick to your original plan of using
one job and shell script.
Yes indeed. We have also consider this way to get builds
without Jenkins at all.
But then ... where is magic-help from Jenkins? :-)
> But if you want your build machines to be jenkins slaves, you can create a
> matrix/multi-configuration job where the platform/os is the axis and you
> can aggregate the resulting artifacts from a post-build action.
>
> If the mac step has to be executed first, that can be a problem, maybe
> somebody can answer that.
Yes, I have try to make matrix project ...
So far I did not see how this can help.
So war I really wondered ...
So many years old project as Hudson/Jenkins
85Mb archive .... What it do in such huge code-base?
and ... Where is magic? Where is easy of use?
If google shows that MANY developers needs sequential jobs,
why there is no simple solution?? Why people should break brain
to find a solution, build chains ... Strange for me ...
I very want to see this idea behind ...
May be this brings powerful flexibility ...
But still ,,, simple things should be simple.
> 2013.10.01. 8:52, "Ruslan Zasukhin" <[email protected]> ezt
> írta:
>
>> Hi Jenkins Gurus and Jenkins Team,
>>
>> I am very newbie to Jenkins, playing with it last 3 weeks.
>> With big fights (mainly with weak confusing docs, so googling googling)
>> we have got working configuration as:
>> * macmini - master of Jenkins
>> * VirtualBox - Win7 - slave
>> * VirtualBox - Ubuntu - slave
>> ** they use SHARED folder to put here few files to exchange.
>>
>> Before we have start try Jenkins, we have automate builds of allow products
>> into the next 7 scripts, which should go one by one:
>> 1) compile_mac
>> 2) compile_win
>> 3) compile_lin
>>
>> 4) package_mac -- must be first, because it builds
>> special REALbasic plugin
>> using DLLs from 3OS
>> RESULT file will go to Win and Linux
>>
>> 5) package_win
>> 6) package_lin
>>
>> 7) put_on_ftp_all_archives
>>
>>
>> Quite SIMPLE construction...
>>
>> ORIGINAL MY HOPE/DREAM was that I can make:
>> * ONE project in Jenkins
>> * Specify 7 Build Steps -- one step calls one bash script.
>> * DONE.
>>
>> But problem 1:
>> Build step cannot be restricted to some machine.
>> Only the whole project can be.
>> So hmm, I cannot have in ONE project
>> build step -- compile on mac
>> build step - compile on win
>>
>> PROBLEM 2:
>> Sequential execution -- inet has many enough HOW TO advices.
>>
>> YES, I was able to solve task, making 7(!!!) projects, which call in
>> post_build next in chain.
>> compile_mac
>> -> compile_win
>> -> compile_lin
>> -> package_mac -- very cool ??
>> ...
>>
>> Probably behind this are hidden some great ideas...
>> Which I do not understand yet.
>>
>> * I do not like that I need 7 projects instead one.
>> * I do not like that now I cannot reuse compile_mac as independent project,
>> which runs each 6 hours for example, because it will starts all following
>> projects. So I will need to make compile_mac_period.
>>
>>
>> ===========
>> I do not see any reason, why not allow us
>> do simple things in a simple way:
>>
>> FEATURE REQUEST:
>> A) Please allow me to specify where to run each Build Step
>> B) Please allow me tp specify by checkbox that I want steps to be
>> sequential
--
Best regards,
Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc
Valentina - Joining Worlds of Information
http://www.paradigmasoft.com
[I feel the need: the need for speed]
--
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.
