Since upgrading to from bamboo 4.4.2 to 5.8.1 builds sometimes fail to transfer artifacts from remote agent to bamboo server. One out of 20 builds or so seems to exhibit the problem and I see the errors in server/agents logs and worked with Atlassian support to change http.socket.timeout and client.timeout with not much impact.
anyone got a clue how to dig deeper and figure out a) what's going on? b) how to fix it?
Server Config Changes:
Agent Config Changes:
2015-05-12 05:40:07,277 ERROR [http-bio-8085-exec-60] [DeliverMessageServlet] Failed to deserialise message sent to /agentServer/message&fingerprint=-612195218561972921 : Artifact [Logs] for FEATURE-PLAT31487-JOB1-23 java.net.SocketTimeoutException: Read timed out
2015-05-12 05:39:40,288 INFO [0-BAM::linengbld36::Agent:pool-3-thread-1] [BuildArtifactPostProcessor] Copying the build artifacts for build: FEATURE-PLAT31487-JOB1-23 2015-05-12 05:39:47,091 INFO [0-BAM::linengbld36::Agent:pool-3-thread-1] [AbstractArtifactManager] Publishing [Logs] for FEATURE-PLAT31487-JOB1-23: 1343 file(s) matching [**/target/logs/**] in directory /opt/builds/build-dir/FEATURE-PLAT31487-JOB1/. 2015-05-12 05:39:47,316 INFO [0-BAM::linengbld36::Agent:pool-3-thread-1] [AbstractArtifactManager] Trying to publish the artifact with handler: com.atlassian.bamboo.build.artifact.BambooRemoteArtifactHandler 2015-05-12 05:41:16,382 ERROR [0-BAM::linengbld36::Agent:pool-3-thread-1] [HttpMessageSender] Failed to send message. java.io.IOException: Unexpected HTTP status code: HTTP/1.1 500 Internal Server Error at com.atlassian.bamboo.v2.build.agent.remote.sender.HttpMessageSender.send(HttpMessageSender.java:129)
I suggest you migrate to jenkins. We spent 4 months working with atlassian getting nowhere. They can't support bamboo. Switching to jenkins with the jenkins job builder helped us migrate in about a month. Jenkins has a community of 100k installations and any problem or question we had had an easily found answer.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot