Uploaded image for project: 'Bamboo'
  1. Bamboo
  2. BAM-16619

Bamboo is not failing builds when artifact failed to get published

    XMLWordPrintable

Details

    • Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Duplicate
    • None
    • Artifacts
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Summary
      Bamboo is not failing builds when artifact failed to get published.

      27-Oct-2015 13:59:16 	[INFO] ------------------------------------------------------------------------
      27-Oct-2015 13:59:16 	[INFO] BUILD SUCCESS
      27-Oct-2015 13:59:16 	[INFO] ------------------------------------------------------------------------
      27-Oct-2015 13:59:16 	[INFO] Total time: 29.433 s
      27-Oct-2015 13:59:16 	[INFO] Finished at: 2015-10-27T12:59:16+00:00
      27-Oct-2015 13:59:17 	[INFO] Final Memory: 64M/780M
      27-Oct-2015 13:59:17 	[INFO] ------------------------------------------------------------------------
      27-Oct-2015 13:59:17 	Finished task 'Deploy' with result: Success
      27-Oct-2015 13:59:17 	Running post build plugin 'Docker Container Cleanup'
      27-Oct-2015 13:59:17 	Running post build plugin 'NCover Results Collector'
      27-Oct-2015 13:59:17 	Running post build plugin 'Clover Results Collector'
      27-Oct-2015 13:59:17 	Running post build plugin 'npm Cache Cleanup'
      27-Oct-2015 13:59:17 	Running post build plugin 'Artifact Copier'
      27-Oct-2015 13:59:17 	Publishing an artifact: Cloud: deploy.properties
      27-Oct-2015 13:59:18 	Unable to publish artifact [Cloud: deploy.properties]: Unable to publish artifact Shared artifact: [Cloud: deploy.properties], pattern: [deploy.properties] anchored at: [build/target] for ABC-DEFAULT-JOB1-3465 via com.atlassian.bamboo.build.artifact.S3ArtifactHandler@25893476
      27-Oct-2015 13:59:18 	Finished publishing of artifact Shared artifact: [Cloud: deploy.properties], pattern: [deploy.properties] anchored at: [build/target] in 0s
      

      This is confusing as the artifact might be a required item in the next process and users need to check the builds manually to see if the build has artifact or not.

      Expected behavior
      Bamboo should mark the builds as failed when it failed to publish the artifact as the publishing task is part of build process.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mfahd Fahd
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: