You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2016/11/11 04:13:01 UTC
svn commit: r1769244 - /maven/trunks/
Author: hboutemy
Date: Fri Nov 11 04:13:01 2016
New Revision: 1769244
URL: http://svn.apache.org/viewvc?rev=1769244&view=rev
Log:
added jenkins-seeding
Modified:
maven/trunks/ (props changed)
Propchange: maven/trunks/
------------------------------------------------------------------------------
--- svn:externals (original)
+++ svn:externals Fri Nov 11 04:13:01 2016
@@ -1,6 +1,7 @@
archetypes https://svn.apache.org/repos/asf/maven/archetypes/trunk
doxia https://svn.apache.org/repos/asf/maven/doxia/trunks
enforcer https://svn.apache.org/repos/asf/maven/enforcer/trunk
+jenkins-seeding https://svn.apache.org/repos/asf/maven/jenkins-seeding
jxr https://svn.apache.org/repos/asf/maven/jxr/trunk
plugin-tools https://svn.apache.org/repos/asf/maven/plugin-tools/trunk
plugins https://svn.apache.org/repos/asf/maven/plugins/trunk
Re: svn commit: r1769244 - /maven/trunks/
Posted by Hervé BOUTEMY <he...@free.fr>.
ok, say me how you want to merge things...
I think we can create some experiments on skins and Doxia for svn,
archetype(s) for git
then we'll review before doing the job for master pieces like plugins or
shared, which are the 2 big beasts that would benefit the most from the DSL
IMHO: but we need to be confident enough before doing these...
Regards,
Hervé
Le vendredi 11 novembre 2016, 17:20:44 CET Karl Heinz Marbaise a écrit :
> Hi Hervé,
>
> I think I have neglected that...
>
> but it would be a good idea to improve this ...
>
> I can help here if you like...
>
>
> Kind regards
> Karl Heinz
>
> On 11/11/16 09:54, Hervé BOUTEMY wrote:
> > I'm having a look at Karl Heinz job done on Jenkins + Docker at the
> > beginning of the year
> > And I'm comparing with the solution done by Sling [1] [2]
> >
> > Are the 2 approaches complementary or competing?
> > What would be the best fit for us?
> >
> > Currently, I understand the Sling's create_jobs.groovy job since it look
> > much simplistic (I suppose the Docker part is provided by ASF Jenkins
> > now...): the features we would miss would be git support in addition to
> > svn, and Windows node job creation in addition to Ubuntu
> >
> > And in fact, what's the status of maven-jenkins-seeding? The corresponding
> > Jenkins job [3] does not seem to really prepare any Jenkins job yet
> >
> >
> > Notice: having this Jenkins DSL work would have multiple benefits:
> > - the general usual benefit from this DSL of keeping config in SCM
> > - would be an enabler to migrate some svn roots to many separate git repos
> > [4] The only feature that would still be missing to me would be the svn
> > trunks approach = the way I can checkout the whole svn content in 1
> > command: I'd like to have such equivalent in git. But I could live
> > without it, if necessary: Jenkins integration is the real show stopper
> > for me until now...
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup
> >
> > [2] https://svn.apache.org/viewvc/sling/trunk/tooling/jenkins/
> > create_jobs.groovy?view=markup
> >
> > [3]
> > https://builds.apache.org/view/M-R/view/Maven/job/maven-jenkins-seeding/
> >
> > [4] https://cwiki.apache.org/confluence/display/MAVEN/Git
> > +Migration#GitMigration-Migratinganaggregatortreeintoacollectionofgitrepos
> >
> > Le vendredi 11 novembre 2016, 04:13:01 CET hboutemy@apache.org a écrit :
> >> Author: hboutemy
> >> Date: Fri Nov 11 04:13:01 2016
> >> New Revision: 1769244
> >>
> >> URL: http://svn.apache.org/viewvc?rev=1769244&view=rev
> >> Log:
> >> added jenkins-seeding
> >>
> >> Modified:
> >> maven/trunks/ (props changed)
> >>
> >> Propchange: maven/trunks/
> >> -------------------------------------------------------------------------
> >> --- -- --- svn:externals (original)
> >> +++ svn:externals Fri Nov 11 04:13:01 2016
> >> @@ -1,6 +1,7 @@
> >>
> >> archetypes
> >>
> >> https://svn.apache.org/repos/asf/maven/archetypes/trunk doxia
> >>
> >> https://svn.apache.org/repos/asf/maven/doxia/trunks enforcer
> >>
> >> https://svn.apache.org/repos/asf/maven/enforcer/trunk
> >>
> >> +jenkins-seeding
> >> https://svn.apache.org/repos/asf/maven/jenkins-seeding jxr
> >>
> >> https://svn.apache.org/repos/asf/maven/jxr/trunk plugin-tools
> >>
> >> https://svn.apache.org/repos/asf/maven/plugin-tools/trunk
> >>
> >> plugins
> >> https://svn.apache.org/repos/asf/maven/plugins/trunk
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: svn commit: r1769244 - /maven/trunks/
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Herv�,
I think I have neglected that...
but it would be a good idea to improve this ...
I can help here if you like...
Kind regards
Karl Heinz
On 11/11/16 09:54, Herv� BOUTEMY wrote:
> I'm having a look at Karl Heinz job done on Jenkins + Docker at the beginning
> of the year
> And I'm comparing with the solution done by Sling [1] [2]
>
> Are the 2 approaches complementary or competing?
> What would be the best fit for us?
>
> Currently, I understand the Sling's create_jobs.groovy job since it look much
> simplistic (I suppose the Docker part is provided by ASF Jenkins now...): the
> features we would miss would be git support in addition to svn, and Windows
> node job creation in addition to Ubuntu
>
> And in fact, what's the status of maven-jenkins-seeding? The corresponding
> Jenkins job [3] does not seem to really prepare any Jenkins job yet
>
>
> Notice: having this Jenkins DSL work would have multiple benefits:
> - the general usual benefit from this DSL of keeping config in SCM
> - would be an enabler to migrate some svn roots to many separate git repos [4]
> The only feature that would still be missing to me would be the svn trunks
> approach = the way I can checkout the whole svn content in 1 command: I'd like
> to have such equivalent in git. But I could live without it, if necessary:
> Jenkins integration is the real show stopper for me until now...
>
> Regards,
>
> Herv�
>
> [1] https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup
>
> [2] https://svn.apache.org/viewvc/sling/trunk/tooling/jenkins/
> create_jobs.groovy?view=markup
>
> [3] https://builds.apache.org/view/M-R/view/Maven/job/maven-jenkins-seeding/
>
> [4] https://cwiki.apache.org/confluence/display/MAVEN/Git
> +Migration#GitMigration-Migratinganaggregatortreeintoacollectionofgitrepos
>
>
> Le vendredi 11 novembre 2016, 04:13:01 CET hboutemy@apache.org a �crit :
>> Author: hboutemy
>> Date: Fri Nov 11 04:13:01 2016
>> New Revision: 1769244
>>
>> URL: http://svn.apache.org/viewvc?rev=1769244&view=rev
>> Log:
>> added jenkins-seeding
>>
>> Modified:
>> maven/trunks/ (props changed)
>>
>> Propchange: maven/trunks/
>> ----------------------------------------------------------------------------
>> -- --- svn:externals (original)
>> +++ svn:externals Fri Nov 11 04:13:01 2016
>> @@ -1,6 +1,7 @@
>> archetypes
>> https://svn.apache.org/repos/asf/maven/archetypes/trunk doxia
>> https://svn.apache.org/repos/asf/maven/doxia/trunks enforcer
>> https://svn.apache.org/repos/asf/maven/enforcer/trunk
>> +jenkins-seeding
>> https://svn.apache.org/repos/asf/maven/jenkins-seeding jxr
>> https://svn.apache.org/repos/asf/maven/jxr/trunk plugin-tools
>> https://svn.apache.org/repos/asf/maven/plugin-tools/trunk
>> plugins
>> https://svn.apache.org/repos/asf/maven/plugins/trunk
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: svn commit: r1769244 - /maven/trunks/
Posted by Hervé BOUTEMY <he...@free.fr>.
I'm having a look at Karl Heinz job done on Jenkins + Docker at the beginning
of the year
And I'm comparing with the solution done by Sling [1] [2]
Are the 2 approaches complementary or competing?
What would be the best fit for us?
Currently, I understand the Sling's create_jobs.groovy job since it look much
simplistic (I suppose the Docker part is provided by ASF Jenkins now...): the
features we would miss would be git support in addition to svn, and Windows
node job creation in addition to Ubuntu
And in fact, what's the status of maven-jenkins-seeding? The corresponding
Jenkins job [3] does not seem to really prepare any Jenkins job yet
Notice: having this Jenkins DSL work would have multiple benefits:
- the general usual benefit from this DSL of keeping config in SCM
- would be an enabler to migrate some svn roots to many separate git repos [4]
The only feature that would still be missing to me would be the svn trunks
approach = the way I can checkout the whole svn content in 1 command: I'd like
to have such equivalent in git. But I could live without it, if necessary:
Jenkins integration is the real show stopper for me until now...
Regards,
Hervé
[1] https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup
[2] https://svn.apache.org/viewvc/sling/trunk/tooling/jenkins/
create_jobs.groovy?view=markup
[3] https://builds.apache.org/view/M-R/view/Maven/job/maven-jenkins-seeding/
[4] https://cwiki.apache.org/confluence/display/MAVEN/Git
+Migration#GitMigration-Migratinganaggregatortreeintoacollectionofgitrepos
Le vendredi 11 novembre 2016, 04:13:01 CET hboutemy@apache.org a écrit :
> Author: hboutemy
> Date: Fri Nov 11 04:13:01 2016
> New Revision: 1769244
>
> URL: http://svn.apache.org/viewvc?rev=1769244&view=rev
> Log:
> added jenkins-seeding
>
> Modified:
> maven/trunks/ (props changed)
>
> Propchange: maven/trunks/
> ----------------------------------------------------------------------------
> -- --- svn:externals (original)
> +++ svn:externals Fri Nov 11 04:13:01 2016
> @@ -1,6 +1,7 @@
> archetypes
> https://svn.apache.org/repos/asf/maven/archetypes/trunk doxia
> https://svn.apache.org/repos/asf/maven/doxia/trunks enforcer
> https://svn.apache.org/repos/asf/maven/enforcer/trunk
> +jenkins-seeding
> https://svn.apache.org/repos/asf/maven/jenkins-seeding jxr
> https://svn.apache.org/repos/asf/maven/jxr/trunk plugin-tools
> https://svn.apache.org/repos/asf/maven/plugin-tools/trunk
> plugins
> https://svn.apache.org/repos/asf/maven/plugins/trunk
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org