Re: Moving redback-components to git

you can write a separate Jenkinsfile (call it Jenkinsfile-webui-test) and we can create a separate job for that (not part of the main job) On 18 April 2018 at 15:25, Martin Stockhammer wrote: > about the webui tests: > Parallel might be the wrong term. I would like to run

Re: Moving redback-components to git

about the webui tests: Parallel might be the wrong term. I would like to run these tests more or less indepentently that does not affect the normal build job of archiva if it fails. Currently its a separate job with its own configuration and report. I cannot have multiple jenkinsfiles in a

Re: Moving redback-components to git

On 18 April 2018 at 05:21, Martin wrote: > Hi Olivier, > > Ah great! Haven't used the multibranch pipelines yet, but this indeed > makes it a lot simpler. > > The Jenkinsfile in the archiva project is not complete, right? As I see > there is no deploy > stage there. Is there

Re: Moving redback-components to git

Hi Olivier, Ah great! Haven't used the multibranch pipelines yet, but this indeed makes it a lot simpler. The Jenkinsfile in the archiva project is not complete, right? As I see there is no deploy stage there. Is there a difference between the deploy from maven and the deploy from Jenkins