• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 2.3
    • Dependencies
    • None
    • Tomcat 6, WAR deployment
    • 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.

      Not clear whether this is a bug or an enhancement as doc is not explicit on the subject.

      The triggering of builds based on dependencies is rather primitive.

      Let's take an example: plan A depends on B & C. Both B & C depend on D.

      If D changes we would like that B and C, then A, are compiled, ONCE. What actually happens is that B & C are both compiled (fine) but then A is compiled twice.

      Evidently this is not efficient, and in a large tree of dependencies as we have, means that project compilation takes much longer than it should.

            [BAM-1844] Implement intelligent dependency checking

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3018965 ] New: JAC Suggestion Workflow 3 [ 3598485 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2703260 ] New: JAC Suggestion Workflow [ 3018965 ]
            Owen made changes -
            Backlog Order (Obsolete) Original: 3390000000
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Owen made changes -
            Workflow Original: Bamboo Workflow 2016 v1 [ 1417044 ] New: Confluence Workflow - Public Facing v4 [ 2703260 ]
            Marek Went (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2014 v2 [ 618594 ] New: Bamboo Workflow 2016 v1 [ 1417044 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2014 [ 604733 ] New: Bamboo Workflow 2014 v2 [ 618594 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2010 [ 205462 ] New: Bamboo Workflow 2014 [ 604733 ]
            MarkC made changes -
            Workflow Original: reviewflow [ 197673 ] New: Bamboo Workflow 2010 [ 205462 ]
            MarkC made changes -
            Workflow Original: Feature Request Workflow [ 169320 ] New: reviewflow [ 197673 ]

            Looking at the documentation, I think there's a strong argument to be made that this issue is not, in fact, fixed. From the docs:

            Please note, dependency blocking only works when triggered by code updates (i.e. polling or check-in). It will not work when a build is triggered on a schedule or triggered via a parent build (when there are multiple parent builds in progress).

            For this issue, that means that project A is still going to be built twice as parent builds B and C each trigger builds of A that ignore the dependency blocking strategy.

            I really have no idea why you would implement dependency blocking this way, but it makes it pretty useless.

            Chris Hilton added a comment - Looking at the documentation, I think there's a strong argument to be made that this issue is not, in fact, fixed. From the docs : Please note, dependency blocking only works when triggered by code updates (i.e. polling or check-in). It will not work when a build is triggered on a schedule or triggered via a parent build (when there are multiple parent builds in progress). For this issue, that means that project A is still going to be built twice as parent builds B and C each trigger builds of A that ignore the dependency blocking strategy. I really have no idea why you would implement dependency blocking this way, but it makes it pretty useless.

              Unassigned Unassigned
              387b49b1181a Craig Morrison
              Votes:
              29 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: