Working on Fortress Docker Images / Builds / Jenkins tests

2019-04-17 Thread Shawn McKinney
Hi, The docker images used by fortress to test openldap and apacheDS have been recently updated to support a minor change in the data schema, to support additional configuration params. https://hub.docker.com/r/apachedirectory/openldap-for-apache-fortress-tests/ https://hub.docker.com/r/apache

Re: Working on Fortress Docker Images / Builds / Jenkins tests

2019-04-18 Thread Shawn McKinney
> On Apr 17, 2019, at 2:31 PM, Shawn McKinney wrote: > > That is to say, that running the test on a local VM finishes in < 10 minutes, > while in a Jenkins pipeline much longer, > 1 hour. It feels like the tests are running inside a VM that’s underpowered. The adds, updates and deletes are

Re: Working on Fortress Docker Images / Builds / Jenkins tests

2019-04-18 Thread Stefan Seelmann
On 4/18/19 4:12 PM, Shawn McKinney wrote: > >> On Apr 17, 2019, at 2:31 PM, Shawn McKinney wrote: >> >> That is to say, that running the test on a local VM finishes in < 10 >> minutes, while in a Jenkins pipeline much longer, > 1 hour. > > It feels like the tests are running inside a VM that’s

Re: Working on Fortress Docker Images / Builds / Jenkins tests

2019-04-19 Thread Shawn McKinney
> On Apr 18, 2019, at 3:49 PM, Stefan Seelmann wrote: > > Yes, the Jenkins machines are rather slow, I agree. > > There is a bit info (memory and disk) in the Jenkins wiki [1], our jobs > use the "ubuntu" label. For further info we need ask builds@a.o list. > > What's also possible, if you de

Re: Working on Fortress Docker Images / Builds / Jenkins tests

2019-04-21 Thread Stefan Seelmann
On 4/19/19 2:42 PM, Shawn McKinney wrote: > >> On Apr 18, 2019, at 3:49 PM, Stefan Seelmann wrote: >> >> Yes, the Jenkins machines are rather slow, I agree. >> >> There is a bit info (memory and disk) in the Jenkins wiki [1], our jobs >> use the "ubuntu" label. For further info we need ask builds

Re: Working on Fortress Docker Images / Builds / Jenkins tests

2019-04-23 Thread Shawn McKinney
> On Apr 21, 2019, at 2:22 PM, Stefan Seelmann wrote: > > Some more observations when I run the ApacheDS pipeline: > > Some builds finish in only 15-20 minutes, those run on host ubuntu-eu2 > or ubuntu-eu3. However builds on one of the H2x or H3x nodes take 40-60 > minutes. Hi Stefan, Notice

Re: Working on Fortress Docker Images / Builds / Jenkins tests

2019-04-23 Thread Shawn McKinney
> On Apr 23, 2019, at 9:02 AM, Shawn McKinney wrote: > > Looking at the job config, can we try something like this? > > "Restrict where this project can be run” > > ubuntu && !(H2% || H3%) > > That is are wildcards supported? Couldn’t figure it out by reading the help > on the job website.

Re: Working on Fortress Docker Images / Builds / Jenkins tests

2019-04-23 Thread Stefan Seelmann
On 4/23/19 4:42 PM, Shawn McKinney wrote: > >> On Apr 23, 2019, at 9:02 AM, Shawn McKinney wrote: >> >> Looking at the job config, can we try something like this? >> >> "Restrict where this project can be run” >> >> ubuntu && !(H2% || H3%) >> >> That is are wildcards supported? Couldn’t figure i

Re: Working on Fortress Docker Images / Builds / Jenkins tests

2019-04-23 Thread Shawn McKinney
> On Apr 23, 2019, at 12:21 PM, Stefan Seelmann wrote: > > I got an error because between H33 and H34 there is only on |. after > fixing it saved. maybe try again? > > To get Jenkins access I only know [1], you can check yourself if you are > in that group ;) After correcting was able to save

Re: Working on Fortress Docker Images / Builds / Jenkins tests

2019-04-25 Thread Shawn McKinney
> On Apr 23, 2019, at 12:28 PM, Shawn McKinney wrote: > > Now running the job and it seems to be doing the right thing. Stay tuned, > will report back here where this ends up. Hello, A few more days, many successful test runs and we can say this issue has been resolved. A combination of