Re: Moving redback-components to git

2018-04-17 Thread Olivier Lamy
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

2018-04-17 Thread Martin Stockhammer
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

2018-04-17 Thread Olivier Lamy
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

2018-04-17 Thread Martin
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

Re: Moving redback-components to git

2018-04-16 Thread Olivier Lamy
look at https://builds.apache.org/view/A-D/view/Archiva/job/Archiva-TLP-Gitbox/ this would have make your life easier :-) no need of define pooling. the git repo is triggering the build If you don't like this one I would at least use the multibranch so we build branches and pr. On Tue, 17 Apr

Re: Moving redback-components to git

2018-04-16 Thread Olivier Lamy
Hi Martin, Awesome job! Thanks for your time! On Mon, 16 Apr 2018 at 01:42, Martin wrote: > Hi, > > split and move is done now. I'm still working on the Jenkins jobs (think > will use Jenkins pipelines now). > How do we handle the SVN repository? >

Re: Moving redback-components to git

2018-04-15 Thread Martin
Hi, split and move is done now. I'm still working on the Jenkins jobs (think will use Jenkins pipelines now). How do we handle the SVN repository? https://svn.apache.org/repos/asf/archiva/redback/redback-components I'm not sure, how this is handled for the archiva and redback repositories, if

Re: Moving redback-components to git

2018-04-08 Thread Olivier Lamy
Hi Martin I guess it's as you wish as you lead the move :-) Scripts are here http://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/ look at migrate-plugins.sh or migrate-shared.sh IMHO we don't really care about the history for aggregator. On Sun, 8 Apr 2018 at 23:34, Martin

Re: Moving redback-components to git

2018-04-08 Thread Martin
Hi Olivier, one repo per component would mean to create these repos: archiva-redback-components-site.git --> Mainly used for the site.xml, or should we name it '-docs.git' ? archiva-redback-components-parent.git --> The parent pom archiva-redback-components-expression-evaluator.git

Re: Moving redback-components to git

2018-04-08 Thread Olivier Lamy
Hi Martin Do you want to move to only one repo or a repo per component? * only one repo, you need to create the repo https://gitbox.apache.org/setup/newrepo.html (let me know if you don't have the kama to do it) then simply push the current git repo from github. * one repo per component this has