maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte" <rfscho...@apache.org>
Subject [IMPORTANT] Re: Git migration next steps
Date Sat, 16 Dec 2017 10:56:31 GMT
For everybody just a warning I faced today:
If you switch to the git repos, please make sure all commits are migrated.
I noticed the latest commits of the maven-javadoc-plugin got lost.

thanks,
Robert

On Sat, 09 Dec 2017 17:06:09 +0100, Stephen Connolly  
<stephen.alan.connolly@gmail.com> wrote:

> I see we have a large number of repos now on gitbox ;-)
>
> On Thu 7 Dec 2017 at 07:00, Hervé BOUTEMY <herve.boutemy@free.fr> wrote:
>
>> ok, I didn't update my repo clone: now the run-its profile is activated
>>
>> then the plan should just confirm "it works!" :)
>>
>> and find which jobs are special, like maven-dist-tool (which has to be
>> scheduled daily instead of code change, and one platform only)
>>
>> Regards,
>>
>> Hervé
>>
>> Le mercredi 6 décembre 2017, 23:58:45 CET Stephen Connolly a écrit :
>> > On Wed 6 Dec 2017 at 22:38, Hervé BOUTEMY <herve.boutemy@free.fr>  
>> wrote:
>> > > Now that we have 2 ASF Organization Jenkins jobs (one for gitbox [1]
>> and
>> > > one
>> > > for git-wip: thank you Stephen) and that it looks quite successful,
>> let's
>> > > plan
>> > > the next steps.
>> > >
>> > > Here is what I see:
>> > > 1. removal of hand-defined Jenkins jobs that are now duplicates
>> > >
>> > > 2. preparation of the 60 new empty git repos for shared & plugins
>> > >
>> > > 3. migration of the 1 shared component and 1 plugin using  
>> migrate-*.sh
>> > > scripts
>> > > [3] to test and eventually rework the Jenkinsfile (I suppose it will
>> > > require
>> > > some little change, to run add "run-its" profile)
>> >
>> > As far as I recall, I added -P+run-its already
>> >
>> > For the plugin, I'd like to do the job for maven-site-plugin, since we
>> >
>> > > expect
>> > > to release it soon.
>> > > For the shared component, I don't know if there is a best candidate
>> > >
>> > > 4. once previous step is ok, do the full migration: if there are
>> > > volunteers
>> > > for helping, that would be great, since populating 60 git repos  
>> won't
>> be
>> > > really fun...
>> > >
>> > > And as part of 60 empty git repos creation, I propose to migrate the
>> > > "Google
>> > > repo manifest" maven-aggregator [4] to ASF: my personal use has been
>> quite
>> > > successful, I hope it's the same for others. Perhaps there are  
>> better
>> > > ideas
>> > > for its name: maven-aggregator
>> > >
>> > > Any other idea? any objection?
>> > >
>> > > Regards,
>> > >
>> > > Hervé
>> > >
>> > > [1] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/
>> > >
>> > > [2] https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/
>> > >
>> > > [3] https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/
>> > >
>> > > [4] https://github.com/hboutemy/maven-aggregator
>> > >
>> > >  
>> ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > > For additional commands, e-mail: dev-help@maven.apache.org
>> > >
>> > > --
>> >
>> > Sent from my phone
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> --
> Sent from my phone

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message