Damn, I found it
I had to rename $JENKINS_HOME/plugins/ruby-runtime.api to
$JENKINS_HOME/plugins/ruby-runtime.api.disabled.
Chris
On Wednesday, December 7, 2022 at 3:48:25 PM UTC-5 zil...@gmail.com wrote:
> More logs, this is the first log I see. Again I renamed the
> $HOME_JENKINS/plugins
More logs, this is the first log I see. Again I renamed the
$HOME_JENKINS/plugins dir.
2022-12-07 20:46:03.252+ [id=33]INFO
jenkins.InitReactorRunner$1#onAttained: Listed all plugins
2022-12-07 20:46:09.644+ [id=30]INFO
ruby.RubyRuntimePlugin#start: Injecting JRuby into
I updated Java to no avail
$ java -version
openjdk version "11.0.16" 2022-07-19 LTS
OpenJDK Runtime Environment (Red_Hat-11.0.16.0.8-1.amzn2.0.1) (build
11.0.16+8-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-11.0.16.0.8-1.amzn2.0.1) (build
11.0.16+8-LTS, mixed mode, sharing)
On Wednesday,
I have
$ java -version
openjdk version "1.8.0_342"
OpenJDK Runtime Environment (build 1.8.0_342-b07)
OpenJDK 64-Bit Server VM (build 25.342-b07, mixed mode)
On Wednesday, December 7, 2022 at 3:26:06 PM UTC-5 zil...@gmail.com wrote:
> Also I see this in the logs, and looking for info on
>
Also I see this in the logs, and looking for info on
Jenkins.getInstanceOrNull provides nothing.
2022-12-07 20:24:26.772+ [id=190]WARNING
o.e.jetty.server.HttpChannel#handleException: /login
java.lang.IllegalStateException: Jenkins.instance is missing. Read the
documentation of
I'm attempting to update from 2.263.1 to 2.375.1 (huge gap I know), and I'm
getting this on the Jenkins page. It just shows 2 Jenkins butler pics, a
large black circle, and a large blue circle with a question mark in the
middle.
I've even renamed my $JENKINS_HOME/plugins and
Ok, good to see. Then you might not need the xunit plugin at all, since the
JUnit plugin supports this XML format out-of-the-box.
> Am 07.12.2022 um 16:13 schrieb Fabian Cenedese :
>
> At 13:16 07.12.2022, Ullrich Hafner wrote:
>
>> The best way would be to clone the xunit plugin and feed
At 13:16 07.12.2022, Ullrich Hafner wrote:
>The best way would be to clone the xunit plugin and feed your file as a new
>test case. Then you can directly see what is broken.
I found that pytest generates a JUnit format file. With JUnit as parser
insteap of CppUnit it works. So it was a user
The best way would be to clone the xunit plugin and feed your file as a new
test case. Then you can directly see what is broken.
> Am 07.12.2022 um 06:50 schrieb Fabian Cenedese :
>
> Hello
>
> I'm using pytest for testing and have it generate a unittest
> xml file that can be read by Jenkins.
