Jenkins CI Windows node failed on release - should I be concerned?

[Mez Pahlan]

Hi again. I'm probably worrying about nothing but this looked strange to me.

https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fappcenter-plugin/activity/

During a release:prepare release:perform maven will request two builds from the CI server due to two commits to master. The first commit is the actual release the second is preparing for the next development cycle but contains no changes apart from a snapshot version number bump in the POM file. Should I be concerned that the actual release build failed on the CI server but the snapshot build did not? Is my plugin going to be published in this state? I know from past experience that if this happens for PR builds you can simply close and reopen the PR to trigger another build but what am I supposed to do here? Create a new release?

Again..... I might be worrying about nothing but I thought I should ask :)

Thanks!

[Daniel Beck]

You're the one doing the release, builds on CI mean nothing. ci.jenkins.io is actually only CI, it does not publish (unless you count incremental, which you shouldn't, as they are just a development tool).

> --
> 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/a685c8ac-e178-44c1-aaaa-1242347c2f17%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Gavin Mogan]

If its failing because of a system error, Then probably ignorable.

If its failing due to test breaking. It might be worth looking into.

Do daniel's point, If you just feel like ignoring it, ignore it.

In this case however, the error seems to be an issue between master talking to agent, so not likely your code.

14:35:58  [Pipeline] }
14:35:58  Terminated
14:37:45  win2012-e11d91 was marked offline: Connection was broken: java.util.concurrent.TimeoutException: Ping started at 1563399225815 hasn't completed by 1563399465816
14:37:45   at hudson.remoting.PingThread.ping(PingThread.java:134)
14:37:45   at hudson.remoting.PingThread.run(PingThread.java:90)

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/B0B70C6B-8D09-48D9-89C2-E630C6060418%40beckweb.net.

[Mez Pahlan]

Thanks Gavin, great explanation and insight. I'm likely worrying about nothing.