Hi,
builds with Maven (latest) are now failing with NoSuchFieldError:
DEFAULT_USER_SETTINGS_FILE.
Seems that Maven was updated to 3.5 although the installed Jenkins version
doesn't support it.
Bug report:
https://issues.jenkins-ci.org/browse/JENKINS-43446
Sample for failing builds:
https://b
> Is there a _more correct_ move option that will handle redirects from
the>
> old view?
Not implemented yet: https://issues.jenkins-ci.org/browse/JENKINS-6961
Regards
Dennis
Hi,
looks like someone tries to add JDK15.
https://builds.apache.org/view/A-D/view/CXF/job/CXF-Master-JDK11/ws/maven-plugins/codegen-plugin/target/it/jdk-cxf-with-toolchain/build.log
mentions "Misconfigured toolchains. Non-existing JDK home configuration
at /home/jenkins/tools/java/latest15"
Coul
Hi,
for Apache CXF we currently have multiple build jobs per branch and JDK
version, e.g.
- Master-JDK8
- Master-JDK11
- Master-JDK-latest
- 3.3-JDK8
- 3.3-JDK11
- 3.3-JDK-latest
As we have an increasing number of Java versions that we support, I thought
about simplying this with the move to t
> At Struts project I developed something like this, this runs
> sequentially (not sure why but there was a reason) and also supports
> PRs (but that needs a dedicated Github user with access to ASF)
>
> https://github.com/apache/struts/blob/master/Jenkinsfile
Thanks Łukasz, that's what I was loo
Hi,
currently the queue is again ~3500 builds long. I already experienced this
several times. Any update on a fix?
Best,
Dennis
Hi,
I still see that most executors are blocked by Maven builds. I'm trying to get
a job migration done but as in the past the queue is occupied by hundereds of
Maven builds. Please try to improve that!
Best,
Dennis
