Key: |
QB-1156
|
Type: |
New Feature
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Unassigned
|
Reporter: |
Robin Shen
|
Votes: |
2
|
Watchers: |
2
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 01/Dec/11 11:53 PM
Updated: 27/Feb/13 01:03 PM
|
|
|
Component/s: |
None
|
Affects Version/s: |
4.0.17
|
Fix Version/s: |
5.0.8
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Do I understand it correctly, that any pom.xml analysis has been dropped and has never got resurrected? Is there a chance to have it back? Otherwise the whole CI idea stops making sense for our maven-pom-based-huge-dependency-tree projects, as if an updated library snapshot does not trigger re-building all the gazillion applications which depend on this snapshot, automatic CI just stops working, as one needs to 1) know, which apps depend on which lib, 2) go through all of them and click "run" to trigger re-building. And, "no", referencing repositories to watch and trigger the build on commit won't work either. Neither does scheduled builds, just because of too many projects and interdependencies. Jenkins has this very proper pom-based dependency analysis which works very well. Having this in QB would be amazing too.
|
Description
|
Do I understand it correctly, that any pom.xml analysis has been dropped and has never got resurrected? Is there a chance to have it back? Otherwise the whole CI idea stops making sense for our maven-pom-based-huge-dependency-tree projects, as if an updated library snapshot does not trigger re-building all the gazillion applications which depend on this snapshot, automatic CI just stops working, as one needs to 1) know, which apps depend on which lib, 2) go through all of them and click "run" to trigger re-building. And, "no", referencing repositories to watch and trigger the build on commit won't work either. Neither does scheduled builds, just because of too many projects and interdependencies. Jenkins has this very proper pom-based dependency analysis which works very well. Having this in QB would be amazing too. |
Show » |
Change by PMEase JIRA Administrator [19/Feb/13 11:38 AM]
|
Fix Version/s
|
|
5.0.8
[ 11442
]
|
Change by PMEase JIRA Administrator [19/Feb/13 11:38 AM]
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
Assignee
|
Robin Shine
[ robinshine
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
Change by Robin Shen [01/Dec/11 11:53 PM]
|
Field |
Original Value |
New Value |
Description
|
|
Do I understand it correctly, that any pom.xml analysis has been dropped and has never got resurrected? Is there a chance to have it back? Otherwise the whole CI idea stops making sense for our maven-pom-based-huge-dependency-tree projects, as if an updated library snapshot does not trigger re-building all the gazillion applications which depend on this snapshot, automatic CI just stops working, as one needs to 1) know, which apps depend on which lib, 2) go through all of them and click "run" to trigger re-building. And, "no", referencing repositories to watch and trigger the build on commit won't work either. Neither does scheduled builds, just because of too many projects and interdependencies. Jenkins has this very proper pom-based dependency analysis which works very well. Having this in QB would be amazing too.
|
|