re-reading our migration process documentation [1], I see "check especially
behaviour on checking out tag"
I suppose that we could compare content between git checkout and svn checkout
for HEAD and every past release
did somebody prepare a shell script for that?
Regards,
Hervé
[1]
There are 6 svn locations without any special complexity that are waiting for
a volunteer for git migration for a few years but nobody does anything about:
I started 3 days ago to ask for help about it and got pretty no feedback [1]
then there are the 4 complex svn locations (plugins, shared,
On Fri 6 Oct 2017 at 16:47, Arnaud Héritier wrote:
> I agree that we should use pipeline nowdays
> perhaps a shared lib if we want to standardize some stuffs and a set of
> multi-branches jobs (or org folder but it requires GitHub :( )
Nah I can give us org folder on top
But did we completely abandoned the idea of moving everything to git ?
The CI setup was the main stop for it ?
On Fri, Oct 6, 2017 at 8:05 PM, Hervé BOUTEMY wrote:
> I was expecting the usual litany
>
> what I'm not confident currently with pipeline on Maven core is that
I was expecting the usual litany
what I'm not confident currently with pipeline on Maven core is that we have
for example the "maven-3.x-jenkinsfile/MNG-6242 - build #1 - null" message,
with this "null" part that makes me wonder if we are using it as expected.
And for large multi-module svn
I agree that we should use pipeline nowdays
perhaps a shared lib if we want to standardize some stuffs and a set of
multi-branches jobs (or org folder but it requires GitHub :( )
On Fri, Oct 6, 2017 at 9:16 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On Fri 6 Oct 2017 at
GitHub user sgarelle opened a pull request:
https://github.com/apache/maven-plugins/pull/132
MPDF-48: Update site documentation & non supported report plugins.
Ready for 1.4 release.
You can merge this pull request into a Git repository by running:
$ git pull
On Fri 6 Oct 2017 at 06:32, Hervé BOUTEMY wrote:
> I just fixed a few failing jobs [1] to have again a usable Jenkins.
>
> Now I'm facing some issues, I suppose caused by newer Jenkins versions:
> - Maven 3.0.5 causes NoSuchMethodError: o.c.plexus.util.xml.pull.MXParser
>