Git migration next steps

Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Git migration next steps

Hervé BOUTEMY
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)
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Git migration next steps

Hervé BOUTEMY
yes, and 83 maven-box CI jobs [1]

some CI failures are not really expected, but in general, the result is good

it's time for everybody to check his favorite plugin or shared component and
do the little fixes: the global migration is done

and it's time also to start reviewing PRs and merging: this was the big
objective with Git migration

Regards,

Hervé

[1] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/

Le samedi 9 décembre 2017, 17:06:09 CET Stephen Connolly a écrit :

> I see we have a large number of repos now on gitbox ;-)
>
> On Thu 7 Dec 2017 at 07:00, Hervé BOUTEMY <[hidden email]> 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 <[hidden email]> 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: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > > >
> > > > --
> > >
> > > Sent from my phone
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> > --
>
> Sent from my phone



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Git migration next steps

stephenconnolly
On Sun 10 Dec 2017 at 09:59, Hervé BOUTEMY <[hidden email]> wrote:

> here is a list of strange issues in CI jobs:
>
> - Doxia Sitetools is failing at checkout [1]
>
> - Maven core branches fail in maven-wip [2] while the multi-branch does not
> fail [3]: AFAIK, same Jenkins files are used, isn't it?


Ubuntu-4 was having issues


>
> Regards,
>
> Hervé
>
> [1]
> https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-doxia-sitetools/job/master/4/console
>
> [2] https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/job/maven/
>
> [3]
> https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/
>
> Le dimanche 10 décembre 2017, 06:29:20 CET Hervé BOUTEMY a écrit :
> > yes, and 83 maven-box CI jobs [1]
> >
> > some CI failures are not really expected, but in general, the result is
> good
> >
> > it's time for everybody to check his favorite plugin or shared component
> and
> > do the little fixes: the global migration is done
> >
> > and it's time also to start reviewing PRs and merging: this was the big
> > objective with Git migration
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/
> >
> > Le samedi 9 décembre 2017, 17:06:09 CET Stephen Connolly a écrit :
> > > I see we have a large number of repos now on gitbox ;-)
> > >
> > > On Thu 7 Dec 2017 at 07:00, Hervé BOUTEMY <[hidden email]>
> 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 <[hidden email]>
> 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: [hidden email]
> > > > > > For additional commands, e-mail: [hidden email]
> > > > > >
> > > > > > --
> > > > >
> > > > > Sent from my phone
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > > >
> > > > --
> > >
> > > Sent from my phone
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
> --
Sent from my phone
Reply | Threaded
Open this post in threaded view
|

Re: Git migration next steps

Hervé BOUTEMY
thank you: one less issue

a new finding: the Jira message points to the Jenkins build, why not
But it does not point to Git commit [1]

the link to the git commit is very useful to track how the fix was done, and
remains valid on a long period (which is not the case of the Jenkins build)

Is it possible to have this in our standard build, please?

Regards,

Hervé

[1] https://issues.apache.org/jira/browse/DOXIASITETOOLS-182

Le lundi 11 décembre 2017, 21:29:15 CET Stephen Connolly a écrit :

> On Sun 10 Dec 2017 at 09:59, Hervé BOUTEMY <[hidden email]> wrote:
> > here is a list of strange issues in CI jobs:
> >
> > - Doxia Sitetools is failing at checkout [1]
> >
> > - Maven core branches fail in maven-wip [2] while the multi-branch does
> > not
> > fail [3]: AFAIK, same Jenkins files are used, isn't it?
>
> Ubuntu-4 was having issues
>
> > Regards,
> >
> > Hervé
> >
> > [1]
> > https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-doxi
> > a-sitetools/job/master/4/console
> >
> > [2] https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/job/maven/
> >
> > [3]
> > https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/
> >
> > Le dimanche 10 décembre 2017, 06:29:20 CET Hervé BOUTEMY a écrit :
> > > yes, and 83 maven-box CI jobs [1]
> > >
> > > some CI failures are not really expected, but in general, the result is
> >
> > good
> >
> > > it's time for everybody to check his favorite plugin or shared component
> >
> > and
> >
> > > do the little fixes: the global migration is done
> > >
> > > and it's time also to start reviewing PRs and merging: this was the big
> > > objective with Git migration
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/
> > >
> > > Le samedi 9 décembre 2017, 17:06:09 CET Stephen Connolly a écrit :
> > > > I see we have a large number of repos now on gitbox ;-)
> > > >
> > > > On Thu 7 Dec 2017 at 07:00, Hervé BOUTEMY <[hidden email]>
> >
> > 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 <[hidden email]>
> >
> > 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: [hidden email]
> > > > > > > For additional commands, e-mail: [hidden email]
> > > > > > >
> > > > > > > --
> > > > > >
> > > > > > Sent from my phone
> > > > >
> > > > > --------------------------------------------------------------------
> > > > > -
> > > > > To unsubscribe, e-mail: [hidden email]
> > > > > For additional commands, e-mail: [hidden email]
> > > > >
> > > > > --
> > > >
> > > > Sent from my phone
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> > --
>
> Sent from my phone



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]