Hi devs,
I hope you have spent a nice weekend ;-)
Integrated new Surefire feature [1] in the core-its branch [2] which fixed
the first issue (see point 1.) and the build is successful [3].
After making an analysis, with a help of the logs, we can see that there
are 3 known issues at least:
1. S
Well, the Maven project is not the only one who wants to ensure repeatable
builds and may be surprises by things like that. It certainly would be a
safeguard for anybody interested in explizit configurations for CI jobs.
--
http://bernd.eckenfels.net
Von: Rober
No, there's no need for that and it would over-complicate the scripts.
mavenrc can be handy, but only at INFRA level.
As said, we were able to fix it on the project-level. The project simply
wasn't aware of
- side effects and impact of creating this file on Jenkins
- the existence of .mvn/jvm.
Do we need a Maven Option to turn of processing of implicit configurations,
just like you can turn of shellrc Files?
--
http://bernd.eckenfels.net
Von: Robert Scholte
Gesendet: Samstag, August 3, 2019 9:12 PM
An: Maven Developers List
Betreff: [SUMMARY] 3 ITs p
On Sun, 04 Aug 2019 13:06:31 +0200, Elliotte Rusty Harold
wrote:
This investigation and resolution of this mystery has been quite
informative. I suspect there are general principles and lessons here
about separating infrastructure for different projects that extend
well beyond Maven itself an
This investigation and resolution of this mystery has been quite
informative. I suspect there are general principles and lessons here
about separating infrastructure for different projects that extend
well beyond Maven itself and probably beyond Jenkins. Containers might
play a role.
Perhaps someo
