History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CIB-412
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Fixed
Priority: 3 3
Assignee: jason
Reporter: Niklas Gustavsson
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Pulse

Build dependent projects

Created: 29/May/06 09:02 PM   Updated: 09/Jun/06 03:15 AM
Return to search
Component/s: Configuration
Affects Version/s: 1.0.4
Fix Version/s: 1.1

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
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.



 All   Comments   Work Log   Change History      Sort Order:
Daniel Ostermeier - 30/May/06 02:21 AM
Hi Niklas,

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



Niklas Gustavsson - 31/May/06 01:08 PM
For our needs, only item 1 would be required since we use Maven for our build. So, project A would run with jar:install to upload the produced JAR file into the local repository. Project B would then be triggered and be able to download the produced JAR file.

Getting item 1 in 1.1 would be great. Is there a time frame for 1.1?

Thanks!
Niklas

Daniel Ostermeier - 31/May/06 02:16 PM
I have scheduled dependant builds for 1.1. We are tentatively targetting 1.1 for the end of the month of June, so all will be done by the time the world cup lets us get back to our normal day to day routines :)

jason - 07/Jun/06 03:13 PM
Added the backend: a new type of event trigger filter for build completed events. Refer to change 1486.

jason - 09/Jun/06 03:15 AM
Added a front end to create and edit build completed triggers in change 1494.