Hi milki milk,
sorry for the very long delay... Currently trying to followup on all the stuff
that accumulated...
On 03 Sep 2015, at 16:32, milki milk wrote:
> On Thursday, September 3, 2015 at 4:03:50 AM UTC-7, Guenther, Marc(AWF) wrote:
>
>> On 01 Sep 2015, at 05:02, milki
Hi,
here is part 3 of the series, where I describe the actual implementation that
we came up with and are currently using:
http://www.technology-ebay.de/the-teams/mobile-de/blog/taming-the-hydra-part-3.html
Sorry for the long delay :)
Have fun,
Marc
On 28 Aug 2015, at 15:55, Patrick Hund wrot
Hi,
we had quite some severe memory problems with Job DSL Plugin, but then, we were
running it quite often (like, all the time...). In the end, it didn't even
survive one working day.
Using the JavaMelody Monitoring Plugin, we saw an ever increasing sawtooth in
the "Used non-heap memory" and t
On 01 Sep 2015, at 05:02, milki milk wrote:
> I'm not sure what you mean by "when a repo needs testing". So when there has
> been a commit in the repo, which changes the 'jenkins.yml' file, and that
> commit gets pushed, then that change will be applied to the existing jobs
> before they run.
Hi,
On 03 Sep 2015, at 01:36, milki milk wrote:
> So the article only mentions 2 methods - Cloudbees Template Plugin and
> Jenkins Job DSL. There are at least two other alternatives I know about -
> Jenkins Job Builder and Workflow. Were these and possibly other alternatives
> explored as wel
Hi all,
I think there has been a little bit of confusion here.
1. As described in my blog article, we are using Job-DSL-Plugin, not Jenkins
Job Builder (JJB). Both try to solve similar problems (automatically generate
jobs based on external descriptions) but there are two very important
differ
