-
Suggestion
-
Resolution: Fixed
-
None
-
Tomcat 6, WAR deployment
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
Workflow | Original: JAC Suggestion Workflow [ 3018965 ] | New: JAC Suggestion Workflow 3 [ 3598485 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2703260 ] | New: JAC Suggestion Workflow [ 3018965 ] |
Backlog Order (Obsolete) | Original: 3390000000 | |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1417044 ] | New: Confluence Workflow - Public Facing v4 [ 2703260 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 618594 ] | New: Bamboo Workflow 2016 v1 [ 1417044 ] |
Workflow | Original: Bamboo Workflow 2014 [ 604733 ] | New: Bamboo Workflow 2014 v2 [ 618594 ] |
Workflow | Original: Bamboo Workflow 2010 [ 205462 ] | New: Bamboo Workflow 2014 [ 604733 ] |
Workflow | Original: reviewflow [ 197673 ] | New: Bamboo Workflow 2010 [ 205462 ] |
Workflow | Original: Feature Request Workflow [ 169320 ] | New: reviewflow [ 197673 ] |
Fix Version/s | New: 2.3 [ 14572 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |