-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
4
-
I have a build plan with artifact definition(s). Build passes even when no artifacts get attached to the build from (any of) artifact definition(s).
19-Apr-2015 16:53:44 Running post build plugin 'Artifact Copier' 19-Apr-2015 16:53:44 Publishing an artifact: foo 19-Apr-2015 16:53:44 Finished publishing of artifact Shared artifact: [foo], pattern: [foo] in 0s 19-Apr-2015 16:53:44 Running post build plugin 'Post Command Agent Runner' 19-Apr-2015 16:53:44 Running post build plugin 'npm Cache Cleanup' 19-Apr-2015 16:53:44 Running post build plugin 'NCover Results Collector' 19-Apr-2015 16:53:44 Running post build plugin 'Clover Results Collector' 19-Apr-2015 16:53:44 Finalising the build... 19-Apr-2015 16:53:44 Stopping timer. 19-Apr-2015 16:53:44 Build FOO-137 completed. 19-Apr-2015 16:53:45 Running on server: post build plugin 'Clover Delta Calculator' 19-Apr-2015 16:53:46 Running on server: post build plugin 'Build Hanging Detection Configuration' 19-Apr-2015 16:53:46 Running on server: post build plugin 'deploymentResultProcessor' 19-Apr-2015 16:53:46 Running on server: post build plugin 'NCover Results Collector' 19-Apr-2015 16:53:46 Running on server: post build plugin 'Maven Dependencies Postprocessor' 19-Apr-2015 16:53:46 All post build plugins have finished 19-Apr-2015 16:53:46 Generating build results summary... 19-Apr-2015 16:53:46 Saving build results to disk... 19-Apr-2015 16:53:46 Indexing build results... 19-Apr-2015 16:53:46 Finished building FOO-137.
"Produced artifacts" paragraph on stage Artifacts tab for this build says
There have been no artifacts set up for this job.
Imagine a user configuring artifact definition for a build plan, verifying it works for couple of builds, and then after some time realising that it has stopped working, that no artifacts were available for past n builds, while all those past builds have been labeled as successful.
At least allow from artifact definition one to choose what number of artifacts must come out of artifact definition. "Any"/-1 can be default value.
[BAM-15872] Build with artifact definition passes even when no artifacts get attached
Chris G
added a comment - This behavior makes no sense to me. If a build fails to produce the expected output why would Bamboo consider that a pass? I fail to see the logic in this design.
Chris G
added a comment - This behavior makes no sense to me. If a build fails to produce the expected output why would Bamboo consider that a pass? I fail to see the logic in this design.
Just ran into this myself on Bamboo 6.3.2. Artifact failed to be created due to us having just recently changed the server's SSL cert (error: "com.atlassian.bamboo.build.artifact.BambooRemoteArtifactHandler: javax.net.ssl.SSLHandshakeException: server certificate change is restricted during renegotiation") yet the build still passed.