CI build fails (general problem?)

25 views
Skip to first unread message

Robin Jansohn

unread,
Aug 1, 2019, 5:44:31 AM8/1/19
to Jenkins Developers
My pull request fails to build (https://github.com/jenkinsci/deploy-plugin/pull/40) and it does not seem to have anything to do with my changes. Is there a general problem at the moment? Anything else I can do to solve the problem?

[2019-08-01T09:26:16.690Z] java.lang.NoClassDefFoundError: Could not initialize class org.jvnet.hudson.test.TestPluginManager
[2019-08-01T09:26:16.690Z] at org.jvnet.hudson.test.JenkinsRule.<init>(JenkinsRule.java:321)
[2019-08-01T09:26:16.690Z] at hudson.plugins.deploy.PipelineSyntaxTest.<init>(PipelineSyntaxTest.java:22)



Locally I can build it without a problem...

Daniel Beck

unread,
Aug 1, 2019, 6:33:27 AM8/1/19
to Jenkins Developers
Looks like an infra problem. From the build log:

[2019-08-01T09:39:50.355Z] Java HotSpot(TM) 64-Bit Server VM warning: Insufficient space for shared memory file:

[2019-08-01T09:40:06.604Z] Caused by: java.io.IOException: Failed to create a new directory /tmp/hudson1385458821293755070tmp

Builds run on ephemeral agents, so I'd wait a bit and try again.
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/408bbf70-0935-4a1f-bdec-953506563529%40googlegroups.com.

Jesse Glick

unread,
Aug 1, 2019, 12:39:51 PM8/1/19
to Jenkins Dev
On Thu, Aug 1, 2019 at 6:33 AM Daniel Beck <m...@beckweb.net> wrote:
> [2019-08-01T09:40:06.604Z] Caused by: java.io.IOException: Failed to create a new directory /tmp/hudson1385458821293755070tmp

There were disk space errors recently. I would try using the new `useAci` option

buildPlugin(useAci: true)

which is probably immune to such issues.

Mark Waite

unread,
Aug 1, 2019, 1:36:35 PM8/1/19
to jenkinsci-dev
I wasn't aware of the useAci switch.  The  https://github.com/jenkins-infra/pipeline-library/blob/master/README.adoc#optional-arguments says that it means "Use Azure container instances" instead of Azure VM instances.

Does useAci: true work with jobs that are configured for Windows, or is it limited to Linux containers?

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.


--
Thanks!
Mark Waite

Slide

unread,
Aug 1, 2019, 1:58:58 PM8/1/19
to jenkin...@googlegroups.com
It is new (two days ago or so). It currently will not use ACI for Windows builds, only Linux builds. I am working on getting Windows Docker Agent images in place so that it will work for Windows builds in the future.



--

Robin Jansohn

unread,
Aug 1, 2019, 3:36:12 PM8/1/19
to Jenkins Developers
Did the trick for me, thanks!
Reply all
Reply to author
Forward
0 new messages