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

Build custom revision not working across all repositories definitions even if they point to one repository

XMLWordPrintable

      Hi,

      we are using the following scenario, all our source is on a single repository but we split our code in main trunk into folders per technology (trunk/db, trunk/web, trunk/c, trunk/java):

      • database is built on stage 1
      • web, c++, java are built on stage 2 in parallel on a pool of compilation machines
      • tests run on stage 3
      • deployments on stages 4,5,6.

      The problem is if we want to recreate the artifacts by running a build for a specific revision only the default repository definition uses the custom revision the rest are updated to head.

      Due to the size of the code we cannot checkout full trunk on each build server and use default repository everywhere, we need a way to filter out database code and ansi c code from the web servers, or web and c from database.

      Regards,
      Iulius

        1. screenshot-1.jpg
          screenshot-1.jpg
          28 kB

            [BAM-12835] Build custom revision not working across all repositories definitions even if they point to one repository

            Martyna Wojtas (Inactive) added a comment -
            Atlassian Update - 23 June 2020

            Hi,

            Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

            We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users.

            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Thank you,

            Bamboo Team

            Martyna Wojtas (Inactive) added a comment - Atlassian Update - 23 June 2020 Hi, Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Bamboo Team

            James Dumay added a comment -

            Thanks for the report Iulius.

            James Dumay added a comment - Thanks for the report Iulius.

              Unassigned Unassigned
              720a51a4c761 Julius Hutuleac
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: