We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-16771

Artifact downloader should support downloading artifacts from triggering plan.

    • 0
    • 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.

      We have a number of plans that all require the same post-processing/deployment step (with a few variable items that are defined as variables/etc. on the plan).

      It would be very nice to be able to have a single dependency plan that handles that work for every such plan. However the post-processing/deployment step needs shared artifacts from the triggering plan and, as far as I can tell, there isn't a way to have the Artifact Download task use the triggering plan as its source.

      I realize the difficulty in supporting downloading specific artifacts from different triggering plans if they have different artifacts but even only supporting all artifacts would be useful (and supporting a manually specified artifact name and accepting build failures if that doesn't exist would be even better).

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Bamboo Data Center'
            1. Bamboo Data Center
            2. BAM-16771

            Artifact downloader should support downloading artifacts from triggering plan.

              • 0
              • 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.

                We have a number of plans that all require the same post-processing/deployment step (with a few variable items that are defined as variables/etc. on the plan).

                It would be very nice to be able to have a single dependency plan that handles that work for every such plan. However the post-processing/deployment step needs shared artifacts from the triggering plan and, as far as I can tell, there isn't a way to have the Artifact Download task use the triggering plan as its source.

                I realize the difficulty in supporting downloading specific artifacts from different triggering plans if they have different artifacts but even only supporting all artifacts would be useful (and supporting a manually specified artifact name and accepting build failures if that doesn't exist would be even better).

                        Unassigned Unassigned
                        b53ff39fdc8b Etan Reisner
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            b53ff39fdc8b Etan Reisner
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated:
                              Resolved: