
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 29/May/06 09:02 PM
Updated: 09/Jun/06 03:15 AM
|
|
|
| Component/s: |
Configuration
|
| Affects Version/s: |
1.0.4
|
| Fix Version/s: |
1.1
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
Having the ability to build dependent projects automatically would be a crucial feature. For example, project Y is dependent on the result (e.g. JAR file) from project X. If X changes, it should be possible to set up Pulse so that Y is built as well. Luntbuild currently have very nice support for this requirement.
|
|
Description
|
Having the ability to build dependent projects automatically would be a crucial feature. For example, project Y is dependent on the result (e.g. JAR file) from project X. If X changes, it should be possible to set up Pulse so that Y is built as well. Luntbuild currently have very nice support for this requirement.
|
Show » |
|
Dependant projects is something that we have been considering and will schedule it for the up coming 1.1 release.
As I understand it, there are two components to dependant builds.
1) Simple triggering of dependant projects. When project A finishes building successfully (and assuming that there was a change associated with that build), then project B should be triggered if it depends on project A.
2) propogation of artifacts: This involves taking some of the artifacts of project A and then making them available to the dependant build of project B.
The simple triggering is something that pulse will certainly support in the upcoming releases.
As for the propogation of artifacts, do you require this? If so, where do you normally publish your bulid artifacts so that they are made available to subsequent builds?
Regards,
-Daniel