Hi Juan Pablo,

Thanks for the detailed explanation. It makes sense. Let's fix it
post-release. I´ll take a look after

Cheers,

Arturo


On Fri, Jun 14, 2024 at 10:54 PM Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi!
>
> I think everything is ok. The ci building is failing, not the one used
> to prepare the release (otherwise you wouldn't be able to do the tag).
>
> Haven't had the time to look at it closely, but it seems to me that
> the error is derived from several issues
> - the sonar scanner requires jdk-17 to run at sonarcloud
> - b/c of that, we had to split the ci build on 3 steps, mvn package,
> sq upload, snapshot deployment
> - that third stage skips tests in order to do it a bit faster
> - b/c of that, a test-jar dependency isn't built and uploaded, and
> when that test-jar is needed afterwards makes the build fail
>
> We haven't experienced this before b/c we had prior 2.12.2 snapshots
> at repository.a.o, and probably those were used on the ci builds. In
> the moment we switched to a new version (the commit you reference) the
> build doesn't find the required test-jar anywhere, so it fails. The
> release build hasn't failed b/c it doesn't skip the tests, so the
> test-jar does get built.
>
> I think it's ok to fix this post-release, especially if we switch to
> JDK-17, that would mean change the Jenkinsfile to one maven build
> instead of the 3 we have now.
>
> Hopefully this makes sense?
>
> cheers,
> juan pablo
>
> On Fri, Jun 14, 2024 at 10:15 PM Arturo Bernal <aber...@apache.org> wrote:
> >
> > Hi all
> >
> > I am having issues with the release. Some jobs failed, and I just noticed
> > it.
> > It has been failing since
> >
> https://github.com/apache/jspwiki/commit/71424cc587c43cd1418e56c99086db06a6b2fb46
> ,
> > which is basically to prepare the release. I also don't understand why it
> > is trying to use version 2.12.13-snapshot when the code has version
> > 2.12.2-snapshot.
> >
> > Any idea? Should I cancel and start over with another version RC2??
> >
> > Thanks.
> >
> > Arturo
>

Reply via email to