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-21733

Trigger a Plan when downloaded shared artifacts from another plan are updated

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Dependencies
    • None
    • 1
    • 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.

      I have a plan that builds a library and publishes the binary as a shared artifact. I have several plans that each build an application that uses that library via Artifact Download task.

      When the libraries are updated, I would like this to automatically trigger the application plans so they rebuild against the new version of the library. 

      Currently the only way to achieve this is to add each applications as a "child plan" in the library plan. This is not ideal because it requires the library plan to know about every one of it's consumers. This is especially a problem when the application developers may not have permission to edit the library plan. Instead, a "consumer depends-on producer" link set in the consumers would be much better.

      It would be nice to have a trigger option that rebuilds a plan following any successful rebuild of a plan from which it had previously downloaded an artifact. 

      This should include a plan branch that downloaded an artifact from another plan branch.

            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-21733

            Trigger a Plan when downloaded shared artifacts from another plan are updated

              • Icon: Suggestion Suggestion
              • Resolution: Unresolved
              • None
              • Dependencies
              • None
              • 1
              • 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.

                I have a plan that builds a library and publishes the binary as a shared artifact. I have several plans that each build an application that uses that library via Artifact Download task.

                When the libraries are updated, I would like this to automatically trigger the application plans so they rebuild against the new version of the library. 

                Currently the only way to achieve this is to add each applications as a "child plan" in the library plan. This is not ideal because it requires the library plan to know about every one of it's consumers. This is especially a problem when the application developers may not have permission to edit the library plan. Instead, a "consumer depends-on producer" link set in the consumers would be much better.

                It would be nice to have a trigger option that rebuilds a plan following any successful rebuild of a plan from which it had previously downloaded an artifact. 

                This should include a plan branch that downloaded an artifact from another plan branch.

                        Unassigned Unassigned
                        ed6c4f8a2447 Ben
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            ed6c4f8a2447 Ben
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            1 Start watching this issue

                              Created:
                              Updated: