Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-378

Retrieve artifacts for inclusion in dependent projects

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

      It would be a great advantage of Bamboo to be able to retrieve an artifact from a project build (specifically JAR files), to be included in the classpath of other dependent projects. Many development shops maintain a "common" library of code that is reused between different projects and even development teams. This concept is not supported in most CI environments. What I would recommend would be a way to import dependencies from artifacts. These dependencies may or may not trigger a build of the parent project to produce the artifacts, depending on the configuration. These artifacts could simply be referenced in the Ant script with the -lib option.

            [BAM-378] Retrieve artifacts for inclusion in dependent projects

            In order to share artifacts across plans and projects you might want to use Artifact downloader task

            Cheers,
            Bamboo Team

            Krystian Brazulewicz added a comment - In order to share artifacts across plans and projects you might want to use Artifact downloader task Cheers, Bamboo Team

            This issue is still on our radar. Our next release (4.1) is rather short and it will be scheduled for a future release.

            James Dumay added a comment - This issue is still on our radar. Our next release (4.1) is rather short and it will be scheduled for a future release.

            jens added a comment -

            This is certainly something we are considering implementing. However, there is a low chance for it to make it into 3.3. We have plans for a revamp of the artifact UI and this would go well as part of that work.

            jens added a comment - This is certainly something we are considering implementing. However, there is a low chance for it to make it into 3.3. We have plans for a revamp of the artifact UI and this would go well as part of that work.

            This is a feature which my company is VERY interested in. We have a build pipeline that cannot be fully orchestrated in a single plan so we need to pass data to subsequent plans. Without the ability to pass data to a dependent plans we'd have to implement a process outside of bamboo which we'd really like to avoid. Hopefully this feature will make it's way into bamboo 3.3.

            David Brown added a comment - This is a feature which my company is VERY interested in. We have a build pipeline that cannot be fully orchestrated in a single plan so we need to pass data to subsequent plans. Without the ability to pass data to a dependent plans we'd have to implement a process outside of bamboo which we'd really like to avoid. Hopefully this feature will make it's way into bamboo 3.3.

            AjayA added a comment -

            AjayA added a comment - Also requested in http://forums.atlassian.com/thread.jspa?messageID=257283076&#257283076

            relating this to another request for having a link to the 'latest successful build' of a project would make this capability fairly easy to accomplish with just a relative path.

            Charles Brown added a comment - relating this to another request for having a link to the 'latest successful build' of a project would make this capability fairly easy to accomplish with just a relative path.

              Unassigned Unassigned
              c1f69c7dc5af Paul Allen
              Votes:
              25 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: