Failed to generate build summary - Jenkins Plugin

[jack.lunn]

I’m using the Jenkins plugin and it’s working fairly well. However, i’m getting repeated errors involving the build summary. They don’t fail the pipeline but they do take a lot of time waiting for the summary and then timing out. So this takes a < 60 second pipeline process and extends it to more than 5 minutes.

The log is attached below:

Creating release…
Release 1.0.45 created successfully!
INFO: Octopus CLI exit code: 0
ERROR: Failed to generate build summary: Connection timed out (Connection timed out)
java.net.ConnectException: Connection timed out (Connection timed out)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:607)
at java.net.Socket.connect(Socket.java:556)
at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
at sun.net.www.http.HttpClient.(HttpClient.java:242)
at sun.net.www.http.HttpClient.New(HttpClient.java:339)
at sun.net.www.http.HttpClient.New(HttpClient.java:357)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1226)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:990)
at com.octopusdeploy.api.AuthenticatedWebClient.getResponse(AuthenticatedWebClient.java:154)
at com.octopusdeploy.api.AuthenticatedWebClient.get(AuthenticatedWebClient.java:85)
at com.octopusdeploy.api.AuthenticatedWebClient.get(AuthenticatedWebClient.java:72)
at com.octopusdeploy.api.ProjectsApi.getAllProjects(ProjectsApi.java:29)
at com.octopusdeploy.api.ProjectsApi.getProjectByName(ProjectsApi.java:64)
at hudson.plugins.octopusdeploy.OctopusDeployReleaseRecorder.AddBuildSummary(OctopusDeployReleaseRecorder.java:394)
at hudson.plugins.octopusdeploy.OctopusDeployReleaseRecorder.perform(OctopusDeployReleaseRecorder.java:374)
at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:99)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69)
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

[garrett.dass]

Hi @jack.lunn,

Thanks for reaching out and I’m sorry you’re running into that slowdown.

I’m not immediately clear on what the issue is but it does look network-related. I am wondering if I could get a copy of your Octopus Server log and potentially the general time of when this build/error occurred?

Looking forward to hearing back.

Regards,

[garrett.dass]

Hi @jack.lunn,

I am not seeing anything too obvious, either. Just a few more questions from the team if you don’t mind:

• What type of Endpoint/AV are you running on the Octopus Server machine? I am wondering if the process Octodiff.exe is being killed prematurely.
• Would it be possible to get a screenshot of your Push build information screen in Jenkins?
• What version of Jenkins and Octopus Deploy are you running?

Looking forward to hearing back.

Regards,
Garrett

[jack.lunn]

Garrett,

We are using the Jenkins pipeline dsl to configure our pipelines. You can see below the pack, package, and create release steps.

octopusPack additionalArgs: ‘’, includePaths: ‘’, outputPath: ‘’,

overwriteExisting: true, packageFormat: ‘zip’, packageId: “${env.PROJECT_NAME}”,

packageVersion: “1.0.${BUILD_NUMBER}”, sourcePath: ‘’,

toolId: ‘Default’, verboseLogging: false

octopusPushPackage additionalArgs: ‘’, overwriteMode: ‘OverwriteExisting’,

packagePaths: “${env.PROJECT_NAME}.1.0.${BUILD_NUMBER}.zip”,

serverId: “${env.SERVER_ID}”, spaceId: “${env.SPACE_ID}”, toolId: ‘Default’

octopusCreateRelease additionalArgs: ‘’, cancelOnTimeout: false, channel: ‘’,

defaultPackageVersion: “1.0.${BUILD_NUMBER}”, deployThisRelease: false,

deploymentTimeout: ‘’, environment: ‘development’,

jenkinsUrlLinkback: false, project: “${env.PROJECT_NAME}”, releaseNotes: false,

releaseNotesFile: ‘’, releaseVersion: “1.0.${BUILD_NUMBER}”,

serverId: “${env.SERVER_ID}”, spaceId: “${env.SPACE_ID}”,

tenant: ‘’, tenantTag: ‘’, toolId: ‘Default’, verboseLogging: false,

waitForDeployment: false

I will have to get back to you on the AV for the endpoint.

We are running Jenkins 2.235.5 and Octopus 2019.1.1 (yes I know that’s old. We are working on updating the servers)

Can you tell me what’s going on behind the scenes when it’s trying to update the build summary? Is octopus trying to send data back to Jenkins? What is the data flow there?

[garrett.dass]

Hi @jack.lunn,

Thanks for sending over that information.

It looks like full Jenkins Pipelines integration is a new(er) feature than 2019.1.1, it could be a case of a minimum Octopus Version requirement or a case of incompatibility between the older versions you’re running. I apologize I don’t have a more definitive answer, but it does seem likely this is what you’re running into.

Regarding what’s going on with the Build Summary, we have a few documents here and here that will explain a bit more on what that step is doing.

Please let me know if you have any more questions.

Regards,
Garrett