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

Shared artifacts should be configurable to optionally fail the build or not

    XMLWordPrintable

Details

    • 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

      The artifact configuration for jobs should have an additional configuration option similar to the share/unshare link that defines whether the artifact will be "required" or "optional". A required artifact is expected to be created by the job, and if not created it is considered that the entire job has failed.
      An optional artifact is a by-product the job will collect at the end of its run, but it may sometimes not be created and in such cases it is not considered as a failure.

      This proposal is to mitigate the current behavior where artifacts not created or copied from remote agent to build server has no effect on the build status unless if it is a subscribed artifact.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              smaiyaki Sultan Maiyaki (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: