On Tue, Jun 19, 2012 at 8:50 PM, Sami Tikka wrote:
> So, you have a number of jobs that are mostly identical but there's a
> little bit that should work differently for them.
>
> To me this sounds like a perfect case of multi-configuration job.
> https://wiki.jenkins-ci.org/display/JENKINS/Buildin
ts own set of tests.
How can I set this up easily in jenkins without having to write those
first steps over and over again?
thx!
- bram
--
Bram de Jong - CTO
SampleSumo BVBA, Wiedauwkaai 23 G, B-9000 Ghent, Belgium
Web: http://www.samplesumo.com
Twitter: http://twitter.com/SampleSumo
Face
On Mon, Jun 4, 2012 at 6:18 PM, Les Mikesell wrote:
>> I suppose the gist of my question is:
>> If I have 50 different applications that are all sitting in the same
>> repository, and I want each of these applications to build separately
>> as a job, do I really need to do 50 different checkouts o
ive me an idea of how you set this up precisely?
- bram
--
Bram de Jong - CTO
SampleSumo BVBA, Wiedauwkaai 23 G, B-9000 Ghent, Belgium
Web: http://www.samplesumo.com
Twitter: http://twitter.com/SampleSumo
Facebook: http://facebook.com/SampleSumo
Phone: +32 9 3355925 - Mobile: +32 484 154730
On Mon, Jun 4, 2012 at 5:27 PM, Bram de Jong wrote:
>>> My initial guess on how to solve this:
>>> * put each of the repo's in a job that *only fetches* the repo into a
>>> shared directory and doesn't do anything else.
>>
>> I'd think in ter
>> My initial guess on how to solve this:
>> * put each of the repo's in a job that *only fetches* the repo into a
>> shared directory and doesn't do anything else.
>
> I'd think in terms of jobs that build components and applications, not
> so much in relationships to repositories.
The problem is
ructure. Will this get
me into as much trouble as I think it will - jenkins being built
around the idea of each app having a separate workspace?
A lot of questions, ...
- Bram
--
Bram de Jong - CTO
SampleSumo BVBA, Wiedauwkaai 23 G, B-9000 Ghent, Belgium
Web: http://www.samplesumo.com
Twitter: http:
