Re: Moving redback-components to git

[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 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 single project, so this must be
> defined in the same file as the normal build job, right?
>
>
> Regards
>
> Martin
>
>
>
>
> Am 18. April 2018 06:39:16 MESZ schrieb 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 a difference between the deploy from maven and the
>>>  deploy from Jenkins used in the build jobs
>>>  before?
>>
>>
>>
>> might be a bit different from previously. Anyway I fixed it
>>
>>
>>
>>>  Do you know, how to create parallel jobs in the Jenkinsfile? I would like
>>>  to add the webui (selenium) tests too,
>>>  but don't know how to do this with one Jenkinsfile.
>>
>>
>> why in parallel?
>>
>>
>>  And this line: step([$class: 'JUnitResultArchiver', testResults:
>>>  '**/target/surefire-reports/TEST-*.xml']) creates the Test reports as on
>>>  the classic jobs?
>>
>>
>>
>> yes it is. But I switched to withMvn
>>
>>
>>
>>>  And I'm not sure, how the pull requests from github should be handled
>>>  here. But they are not very frequently for archiva and
>>>  I think I will try it out in the near future.
>>
>>
>> yup makes sense
>>
>>
>>>  And about the SVN projects:
>>>  - great to hear that we can abandon some old stuff ;-)
>>>  - I will move parent to gitbox next
>>>  - and I will create a ticket at INFRA for the svnpubsub to gitpubsub
>>>  migration, maybe we can publish the git content to a separate folder
>>>to test the process
>>
>>
>> the sub sites might be an issue (such http://archiva.apache.org/docs/2.2.3/
>> or http://archiva.apache.org/redback/ etc...)
>>
>>
>>>  Cheers
>>>
>>>  Martin
>>>
>>>  Am Dienstag, 17. April 2018, 07:43:49 CEST schrieb 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 2018 at 15:21, Olivier Lamy  wrote:

  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?
>>  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 I see it right,
>>  the directories are deleted (moved to attic), right?
>
>
>
>  yup we can delete those now
>
>
>
>>  So for unifying the infrastructure, it would be good to have all
>>
>  archiva
>>>
  projects on gitbox, that are possible to
>>  migrate without too much effort. So there are some parts remaining at
>>
>  the
>>>
  time:
>>  The archiva parent pom project:
>>  - Is there any restriction that prevents us from moving the parent to
>>  gitbox?
>>
>
>
>  no nothing prevent us.
>
>
>
>  The site publish:
>
>>  - I'm still not sure how these all fit together, and if it is
>>
>  possible to
>>>
  move to gitbox (svnpubsub is used?)
>>and what are the implications?
>
>
>
>  generated html is committed to svnpubsub (not sure how we can change
>
  that
>>>
  now...)
>
>
>  -> Olivier can you give some hints about this
>>
>>  The sandbox?
>>  - Do we still need this, or can we abandon it?
>
>
>
>  abandon
>
>
>
>>  The tools directory?
>>  - Contains maven-archiva-dev-plugin
>>  - What is this, do we need it?
>
>
>
>  remove
>
>
>
>>  The all directory?
>>  - Contains an aggregator pom with parent and archiva and activates
>>  redback  profile
>>  - Not sure, if this is used
>
>
>
>  can be remove as well
>
>
>
>>  docker-file and karaf-commands
>>  - I would delete 

Re: Moving redback-components to git

[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 single project, so this must be 
defined in the same file as the normal build job, right?


Regards

Martin



Am 18. April 2018 06:39:16 MESZ schrieb 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 a difference between the deploy from maven and
>the
>> deploy from Jenkins used in the build jobs
>> before?
>>
>
>might be a bit different from previously. Anyway I fixed it
>
>
>>
>> Do you know, how to create parallel jobs in the Jenkinsfile? I would
>like
>> to add the webui (selenium) tests too,
>> but don't know how to do this with one Jenkinsfile.
>>
>why in parallel?
>
>
>> And this line: step([$class: 'JUnitResultArchiver', testResults:
>> '**/target/surefire-reports/TEST-*.xml']) creates the Test reports as
>on
>> the classic jobs?
>>
>
>yes it is. But I switched to withMvn
>
>
>>
>> And I'm not sure, how the pull requests from github should be handled
>> here. But they are not very frequently for archiva and
>> I think I will try it out in the near future.
>>
>yup makes sense
>
>>
>> And about the SVN projects:
>> - great to hear that we can abandon some old stuff ;-)
>> - I will move parent to gitbox next
>> - and I will create a ticket at INFRA for the svnpubsub to gitpubsub
>> migration, maybe we can publish the git content to a separate folder
>>   to test the process
>>
>the sub sites might be an issue (such
>http://archiva.apache.org/docs/2.2.3/
>or http://archiva.apache.org/redback/ etc...)
>
>>
>> Cheers
>>
>> Martin
>>
>> Am Dienstag, 17. April 2018, 07:43:49 CEST schrieb 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 2018 at 15:21, Olivier Lamy 
>wrote:
>> >
>> > > 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?
>> > >>
>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 I see it right,
>> > >> the directories are deleted (moved to attic), right?
>> > >>
>> > >
>> > > yup we can delete those now
>> > >
>> > >
>> > >>
>> > >> So for unifying the infrastructure, it would be good to have all
>> archiva
>> > >> projects on gitbox, that are possible to
>> > >> migrate without too much effort. So there are some parts
>remaining at
>> the
>> > >> time:
>> > >> The archiva parent pom project:
>> > >> - Is there any restriction that prevents us from moving the
>parent to
>> > >> gitbox?
>> > >
>> > >
>> > > no nothing prevent us.
>> > >
>> > >
>> > >>
>> > >>
>> > > The site publish:
>> > >> - I'm still not sure how these all fit together, and if it is
>> possible to
>> > >> move to gitbox (svnpubsub is used?)
>> > >>   and what are the implications?
>> > >>
>> > >
>> > > generated html is committed to svnpubsub (not sure how we can
>change
>> that
>> > > now...)
>> > >
>> > >
>> > >> -> Olivier can you give some hints about this
>> > >>
>> > >> The sandbox?
>> > >> - Do we still need this, or can we abandon it?
>> > >>
>> > >
>> > > abandon
>> > >
>> > >
>> > >>
>> > >> The tools directory?
>> > >> - Contains maven-archiva-dev-plugin
>> > >> - What is this, do we need it?
>> > >>
>> > >
>> > > remove
>> > >
>> > >
>> > >>
>> > >> The all directory?
>> > >> - Contains an aggregator pom with parent and archiva and
>activates
>> > >> redback  profile
>> > >> - Not sure, if this is used
>> > >>
>> > >
>> > > can be remove as well
>> > >
>> > >
>> > >>
>> > >> docker-file and karaf-commands
>> > >> - I would delete them
>> > >>
>> > >
>> > > go for it
>> > >
>> > >
>> > >>
>> > >> Regards
>> > >>
>> > >> Martin
>> > >>
>> > >> Am Montag, 9. April 2018, 01:31:30 CEST schrieb 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 

Re: Moving redback-components to git

[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 a difference between the deploy from maven and the
> deploy from Jenkins used in the build jobs
> before?
>

might be a bit different from previously. Anyway I fixed it


>
> Do you know, how to create parallel jobs in the Jenkinsfile? I would like
> to add the webui (selenium) tests too,
> but don't know how to do this with one Jenkinsfile.
>
why in parallel?


> And this line: step([$class: 'JUnitResultArchiver', testResults:
> '**/target/surefire-reports/TEST-*.xml']) creates the Test reports as on
> the classic jobs?
>

yes it is. But I switched to withMvn


>
> And I'm not sure, how the pull requests from github should be handled
> here. But they are not very frequently for archiva and
> I think I will try it out in the near future.
>
yup makes sense

>
> And about the SVN projects:
> - great to hear that we can abandon some old stuff ;-)
> - I will move parent to gitbox next
> - and I will create a ticket at INFRA for the svnpubsub to gitpubsub
> migration, maybe we can publish the git content to a separate folder
>   to test the process
>
the sub sites might be an issue (such http://archiva.apache.org/docs/2.2.3/
or http://archiva.apache.org/redback/ etc...)

>
> Cheers
>
> Martin
>
> Am Dienstag, 17. April 2018, 07:43:49 CEST schrieb 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 2018 at 15:21, Olivier Lamy  wrote:
> >
> > > 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?
> > >> 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 I see it right,
> > >> the directories are deleted (moved to attic), right?
> > >>
> > >
> > > yup we can delete those now
> > >
> > >
> > >>
> > >> So for unifying the infrastructure, it would be good to have all
> archiva
> > >> projects on gitbox, that are possible to
> > >> migrate without too much effort. So there are some parts remaining at
> the
> > >> time:
> > >> The archiva parent pom project:
> > >> - Is there any restriction that prevents us from moving the parent to
> > >> gitbox?
> > >
> > >
> > > no nothing prevent us.
> > >
> > >
> > >>
> > >>
> > > The site publish:
> > >> - I'm still not sure how these all fit together, and if it is
> possible to
> > >> move to gitbox (svnpubsub is used?)
> > >>   and what are the implications?
> > >>
> > >
> > > generated html is committed to svnpubsub (not sure how we can change
> that
> > > now...)
> > >
> > >
> > >> -> Olivier can you give some hints about this
> > >>
> > >> The sandbox?
> > >> - Do we still need this, or can we abandon it?
> > >>
> > >
> > > abandon
> > >
> > >
> > >>
> > >> The tools directory?
> > >> - Contains maven-archiva-dev-plugin
> > >> - What is this, do we need it?
> > >>
> > >
> > > remove
> > >
> > >
> > >>
> > >> The all directory?
> > >> - Contains an aggregator pom with parent and archiva and activates
> > >> redback  profile
> > >> - Not sure, if this is used
> > >>
> > >
> > > can be remove as well
> > >
> > >
> > >>
> > >> docker-file and karaf-commands
> > >> - I would delete them
> > >>
> > >
> > > go for it
> > >
> > >
> > >>
> > >> Regards
> > >>
> > >> Martin
> > >>
> > >> Am Montag, 9. April 2018, 01:31:30 CEST schrieb 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  wrote:
> > >> >
> > >> > > 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
> > >> > > archiva-redback-components-modello-plugins.git
> > 

Re: Moving redback-components to git

[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 used in the build jobs 
before?

Do you know, how to create parallel jobs in the Jenkinsfile? I would like to 
add the webui (selenium) tests too,
but don't know how to do this with one Jenkinsfile.
And this line: step([$class: 'JUnitResultArchiver', testResults: 
'**/target/surefire-reports/TEST-*.xml']) creates the Test reports as on the 
classic jobs?

And I'm not sure, how the pull requests from github should be handled here. But 
they are not very frequently for archiva and 
I think I will try it out in the near future.

And about the SVN projects:
- great to hear that we can abandon some old stuff ;-)
- I will move parent to gitbox next
- and I will create a ticket at INFRA for the svnpubsub to gitpubsub migration, 
maybe we can publish the git content to a separate folder
  to test the process

Cheers

Martin

Am Dienstag, 17. April 2018, 07:43:49 CEST schrieb 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 2018 at 15:21, Olivier Lamy  wrote:
> 
> > 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?
> >> 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 I see it right,
> >> the directories are deleted (moved to attic), right?
> >>
> >
> > yup we can delete those now
> >
> >
> >>
> >> So for unifying the infrastructure, it would be good to have all archiva
> >> projects on gitbox, that are possible to
> >> migrate without too much effort. So there are some parts remaining at the
> >> time:
> >> The archiva parent pom project:
> >> - Is there any restriction that prevents us from moving the parent to
> >> gitbox?
> >
> >
> > no nothing prevent us.
> >
> >
> >>
> >>
> > The site publish:
> >> - I'm still not sure how these all fit together, and if it is possible to
> >> move to gitbox (svnpubsub is used?)
> >>   and what are the implications?
> >>
> >
> > generated html is committed to svnpubsub (not sure how we can change that
> > now...)
> >
> >
> >> -> Olivier can you give some hints about this
> >>
> >> The sandbox?
> >> - Do we still need this, or can we abandon it?
> >>
> >
> > abandon
> >
> >
> >>
> >> The tools directory?
> >> - Contains maven-archiva-dev-plugin
> >> - What is this, do we need it?
> >>
> >
> > remove
> >
> >
> >>
> >> The all directory?
> >> - Contains an aggregator pom with parent and archiva and activates
> >> redback  profile
> >> - Not sure, if this is used
> >>
> >
> > can be remove as well
> >
> >
> >>
> >> docker-file and karaf-commands
> >> - I would delete them
> >>
> >
> > go for it
> >
> >
> >>
> >> Regards
> >>
> >> Martin
> >>
> >> Am Montag, 9. April 2018, 01:31:30 CEST schrieb 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  wrote:
> >> >
> >> > > 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
> >> > > archiva-redback-components-modello-plugins.git
> >> > > archiva-redback-components-redback-features.git
> >> > > archiva-redback-components-spring-apacheds.git
> >> > > archiva-redback-components-spring-cache.git
> >> > > archiva-redback-components-spring-quartz.git
> >> > > archiva-redback-components-spring-registry.git
> >> > > archiva-redback-components-spring-taskqueue.git
> >> > > archiva-redback-components-spring-utils.git
> >> > >
> >> > > The current base directory is for redback-compontents-aggregator. I'm
> >> not
> >> > > sure, if we have to take care of this module.
> >> > > Our dependencies use all the specific component modules.
> >> > >
> >> > > I would use 

Re: Moving redback-components to git

[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 2018 at 15:21, Olivier Lamy  wrote:

> 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?
>> 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 I see it right,
>> the directories are deleted (moved to attic), right?
>>
>
> yup we can delete those now
>
>
>>
>> So for unifying the infrastructure, it would be good to have all archiva
>> projects on gitbox, that are possible to
>> migrate without too much effort. So there are some parts remaining at the
>> time:
>> The archiva parent pom project:
>> - Is there any restriction that prevents us from moving the parent to
>> gitbox?
>
>
> no nothing prevent us.
>
>
>>
>>
> The site publish:
>> - I'm still not sure how these all fit together, and if it is possible to
>> move to gitbox (svnpubsub is used?)
>>   and what are the implications?
>>
>
> generated html is committed to svnpubsub (not sure how we can change that
> now...)
>
>
>> -> Olivier can you give some hints about this
>>
>> The sandbox?
>> - Do we still need this, or can we abandon it?
>>
>
> abandon
>
>
>>
>> The tools directory?
>> - Contains maven-archiva-dev-plugin
>> - What is this, do we need it?
>>
>
> remove
>
>
>>
>> The all directory?
>> - Contains an aggregator pom with parent and archiva and activates
>> redback  profile
>> - Not sure, if this is used
>>
>
> can be remove as well
>
>
>>
>> docker-file and karaf-commands
>> - I would delete them
>>
>
> go for it
>
>
>>
>> Regards
>>
>> Martin
>>
>> Am Montag, 9. April 2018, 01:31:30 CEST schrieb 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  wrote:
>> >
>> > > 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
>> > > archiva-redback-components-modello-plugins.git
>> > > archiva-redback-components-redback-features.git
>> > > archiva-redback-components-spring-apacheds.git
>> > > archiva-redback-components-spring-cache.git
>> > > archiva-redback-components-spring-quartz.git
>> > > archiva-redback-components-spring-registry.git
>> > > archiva-redback-components-spring-taskqueue.git
>> > > archiva-redback-components-spring-utils.git
>> > >
>> > > The current base directory is for redback-compontents-aggregator. I'm
>> not
>> > > sure, if we have to take care of this module.
>> > > Our dependencies use all the specific component modules.
>> > >
>> > > I would use 'git subtree split' to divide the current git mirror into
>> > > these repositories, or you can show me the script
>> > > you mentioned.
>> > > There is a pom.xml in the base directory
>> (redback-components-aggregator)
>> > > and the README
>> > > and deploySite.sh script. The history of these will be lost, if we
>> get rid
>> > > of the aggregator module.
>> > >
>> > > What do you think? If it's OK, I can create the new repos.
>> > >
>> > > Regards
>> > >
>> > > Martin
>> > >
>> > > Am Sonntag, 8. April 2018, 13:40:08 CEST schrieb 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 been done in maven project so I
>> can
>> > > find
>> > > > the script for that.
>> > > >
>> > > > I would prefer one repo per component especially for release
>> process.
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > On Sun, 8 Apr 2018 at 02:55, Martin  wrote:
>> > > >
>> > > > > Hi Olivier,
>> > > > >
>> > > > > I would like to move the redback-components to git. Do you know
>> what
>> > > to do
>> > > > > for this?
>> > > > >
>> > > > > Regards
>> > > > >
>> > > > > Martin
>> > > > >
>> > > >
>> > > >
>> > > >

Re: Moving redback-components to git

[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?
> 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 I see it right,
> the directories are deleted (moved to attic), right?
>

yup we can delete those now


>
> So for unifying the infrastructure, it would be good to have all archiva
> projects on gitbox, that are possible to
> migrate without too much effort. So there are some parts remaining at the
> time:
> The archiva parent pom project:
> - Is there any restriction that prevents us from moving the parent to
> gitbox?


no nothing prevent us.


>
>
The site publish:
> - I'm still not sure how these all fit together, and if it is possible to
> move to gitbox (svnpubsub is used?)
>   and what are the implications?
>

generated html is committed to svnpubsub (not sure how we can change that
now...)


> -> Olivier can you give some hints about this
>
> The sandbox?
> - Do we still need this, or can we abandon it?
>

abandon


>
> The tools directory?
> - Contains maven-archiva-dev-plugin
> - What is this, do we need it?
>

remove


>
> The all directory?
> - Contains an aggregator pom with parent and archiva and activates
> redback  profile
> - Not sure, if this is used
>

can be remove as well


>
> docker-file and karaf-commands
> - I would delete them
>

go for it


>
> Regards
>
> Martin
>
> Am Montag, 9. April 2018, 01:31:30 CEST schrieb 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  wrote:
> >
> > > 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
> > > archiva-redback-components-modello-plugins.git
> > > archiva-redback-components-redback-features.git
> > > archiva-redback-components-spring-apacheds.git
> > > archiva-redback-components-spring-cache.git
> > > archiva-redback-components-spring-quartz.git
> > > archiva-redback-components-spring-registry.git
> > > archiva-redback-components-spring-taskqueue.git
> > > archiva-redback-components-spring-utils.git
> > >
> > > The current base directory is for redback-compontents-aggregator. I'm
> not
> > > sure, if we have to take care of this module.
> > > Our dependencies use all the specific component modules.
> > >
> > > I would use 'git subtree split' to divide the current git mirror into
> > > these repositories, or you can show me the script
> > > you mentioned.
> > > There is a pom.xml in the base directory
> (redback-components-aggregator)
> > > and the README
> > > and deploySite.sh script. The history of these will be lost, if we get
> rid
> > > of the aggregator module.
> > >
> > > What do you think? If it's OK, I can create the new repos.
> > >
> > > Regards
> > >
> > > Martin
> > >
> > > Am Sonntag, 8. April 2018, 13:40:08 CEST schrieb 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 been done in maven project so I can
> > > find
> > > > the script for that.
> > > >
> > > > I would prefer one repo per component especially for release process.
> > > >
> > > >
> > > >
> > > >
> > > > On Sun, 8 Apr 2018 at 02:55, Martin  wrote:
> > > >
> > > > > Hi Olivier,
> > > > >
> > > > > I would like to move the redback-components to git. Do you know
> what
> > > to do
> > > > > for this?
> > > > >
> > > > > Regards
> > > > >
> > > > > Martin
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>
>
>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Moving redback-components to git

[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 
I see it right,
the directories are deleted (moved to attic), right?

So for unifying the infrastructure, it would be good to have all archiva 
projects on gitbox, that are possible to
migrate without too much effort. So there are some parts remaining at the time:
The archiva parent pom project:
- Is there any restriction that prevents us from moving the parent to gitbox?

The site publish:
- I'm still not sure how these all fit together, and if it is possible to move 
to gitbox (svnpubsub is used?)
  and what are the implications?
-> Olivier can you give some hints about this

The sandbox?
- Do we still need this, or can we abandon it?

The tools directory?
- Contains maven-archiva-dev-plugin
- What is this, do we need it?

The all directory?
- Contains an aggregator pom with parent and archiva and activates redback  
profile
- Not sure, if this is used

docker-file and karaf-commands
- I would delete them

Regards

Martin

Am Montag, 9. April 2018, 01:31:30 CEST schrieb 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  wrote:
> 
> > 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
> > archiva-redback-components-modello-plugins.git
> > archiva-redback-components-redback-features.git
> > archiva-redback-components-spring-apacheds.git
> > archiva-redback-components-spring-cache.git
> > archiva-redback-components-spring-quartz.git
> > archiva-redback-components-spring-registry.git
> > archiva-redback-components-spring-taskqueue.git
> > archiva-redback-components-spring-utils.git
> >
> > The current base directory is for redback-compontents-aggregator. I'm not
> > sure, if we have to take care of this module.
> > Our dependencies use all the specific component modules.
> >
> > I would use 'git subtree split' to divide the current git mirror into
> > these repositories, or you can show me the script
> > you mentioned.
> > There is a pom.xml in the base directory (redback-components-aggregator)
> > and the README
> > and deploySite.sh script. The history of these will be lost, if we get rid
> > of the aggregator module.
> >
> > What do you think? If it's OK, I can create the new repos.
> >
> > Regards
> >
> > Martin
> >
> > Am Sonntag, 8. April 2018, 13:40:08 CEST schrieb 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 been done in maven project so I can
> > find
> > > the script for that.
> > >
> > > I would prefer one repo per component especially for release process.
> > >
> > >
> > >
> > >
> > > On Sun, 8 Apr 2018 at 02:55, Martin  wrote:
> > >
> > > > Hi Olivier,
> > > >
> > > > I would like to move the redback-components to git. Do you know what
> > to do
> > > > for this?
> > > >
> > > > Regards
> > > >
> > > > Martin
> > > >
> > >
> > >
> > >
> >
> >
> >
> 
> 

Re: Moving redback-components to git

[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  wrote:

> 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
> archiva-redback-components-modello-plugins.git
> archiva-redback-components-redback-features.git
> archiva-redback-components-spring-apacheds.git
> archiva-redback-components-spring-cache.git
> archiva-redback-components-spring-quartz.git
> archiva-redback-components-spring-registry.git
> archiva-redback-components-spring-taskqueue.git
> archiva-redback-components-spring-utils.git
>
> The current base directory is for redback-compontents-aggregator. I'm not
> sure, if we have to take care of this module.
> Our dependencies use all the specific component modules.
>
> I would use 'git subtree split' to divide the current git mirror into
> these repositories, or you can show me the script
> you mentioned.
> There is a pom.xml in the base directory (redback-components-aggregator)
> and the README
> and deploySite.sh script. The history of these will be lost, if we get rid
> of the aggregator module.
>
> What do you think? If it's OK, I can create the new repos.
>
> Regards
>
> Martin
>
> Am Sonntag, 8. April 2018, 13:40:08 CEST schrieb 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 been done in maven project so I can
> find
> > the script for that.
> >
> > I would prefer one repo per component especially for release process.
> >
> >
> >
> >
> > On Sun, 8 Apr 2018 at 02:55, Martin  wrote:
> >
> > > Hi Olivier,
> > >
> > > I would like to move the redback-components to git. Do you know what
> to do
> > > for this?
> > >
> > > Regards
> > >
> > > Martin
> > >
> >
> >
> >
>
>
>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Moving redback-components to git

[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
archiva-redback-components-modello-plugins.git
archiva-redback-components-redback-features.git
archiva-redback-components-spring-apacheds.git
archiva-redback-components-spring-cache.git
archiva-redback-components-spring-quartz.git
archiva-redback-components-spring-registry.git
archiva-redback-components-spring-taskqueue.git
archiva-redback-components-spring-utils.git

The current base directory is for redback-compontents-aggregator. I'm not sure, 
if we have to take care of this module.
Our dependencies use all the specific component modules.

I would use 'git subtree split' to divide the current git mirror into these 
repositories, or you can show me the script
you mentioned.
There is a pom.xml in the base directory (redback-components-aggregator) and 
the README
and deploySite.sh script. The history of these will be lost, if we get rid of 
the aggregator module. 

What do you think? If it's OK, I can create the new repos.

Regards 

Martin

Am Sonntag, 8. April 2018, 13:40:08 CEST schrieb 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 been done in maven project so I can find
> the script for that.
> 
> I would prefer one repo per component especially for release process.
> 
> 
> 
> 
> On Sun, 8 Apr 2018 at 02:55, Martin  wrote:
> 
> > Hi Olivier,
> >
> > I would like to move the redback-components to git. Do you know what to do
> > for this?
> >
> > Regards
> >
> > Martin
> >
> 
> 
>