The last run looks better. It failed, but after the maven run completed successfully. I think it's a jenkins issue now.
Regards Julian On Wed, Dec 7, 2016 at 2:33 PM, Julian Sedding <[email protected]> wrote: > Hi Robert > > It looks like it is a timing issue again. The repository gets used, > before all whitelist configurations are available. The repo was > registered synchronously in this case, which prevented any additional > services from being registered until the repo was made available. The > stack-traces actually happened during repository initialization and > thus could not be successful. > > I made the repository initialization async for all cases now. > Hopefully this helps. We'll see shortly... > > > Regards > Julian > > > On Wed, Dec 7, 2016 at 1:33 PM, Robert Munteanu <[email protected]> wrote: >> On Wed, 2016-12-07 at 11:33 +0000, Apache Jenkins Server wrote: >>> See <https://builds.apache.org/job/sling-launchpad-builder-1.8/345/> >>> >> >> The launchpad has started failing with the latest changes from >> jcr.base, which are related to SLING-6357. >> >> http://svn.apache.org/viewvc?view=revision&revision=1773046 >> >> Julian, can you please double-check why the launchpad fails to start? >> >> Thanks, >> >> Robert >> >>
