Continuum

build in the correct order

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 1.0-alpha-3
  • Fix Version/s: 1.0
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

I'm unsure if this is already the case - it didn't appear to be.

If a project is going to depend on the output of another scheduled continuum build (ie dependency id including version matches that of the other project's id), then they should be built in the correct order, as in the reactor.

Issue Links

This issue depends upon:
CONTINUUM-137 Store dependency information at the ContinuumProject level Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jason van Zyl added a comment -

This would effect scheduled builds where all, or a group of, projects are built and when the "Build All" button is used.

This would require us storing dependency information for each of the continuum projects which we currently do not have.

We would need to make forms to input the dependency data for Ant and Shell projects. This is making me wonder if we're not just going to end up with pseudo POMs for all project types anyway.

We do not currently have support for dependencies amongst the builds so I have entered a new issues for this and will link it. But this will have to go to alpha-3.

Show
Jason van Zyl added a comment - This would effect scheduled builds where all, or a group of, projects are built and when the "Build All" button is used. This would require us storing dependency information for each of the continuum projects which we currently do not have. We would need to make forms to input the dependency data for Ant and Shell projects. This is making me wonder if we're not just going to end up with pseudo POMs for all project types anyway. We do not currently have support for dependencies amongst the builds so I have entered a new issues for this and will link it. But this will have to go to alpha-3.
Hide
Permalink
Trygve Laugstol added a comment -

It will require that Continuum stores the dependencies of a project. I think the best way is to add Ant and shell projects the way it's done today and if someone want's to make project A depend on project B they can do so from the user interface.

Continuum should always store the entire <dependencies> section of all Maven 1 and 2 projects, even if the dependent project isn't in Continuum. This makes it possible for Continuum to schedule a build if any of the (external/file) dependencies for a project has changed. Other CI systems have this feature and I think it's a useful feature.

Show
Trygve Laugstol added a comment - It will require that Continuum stores the dependencies of a project. I think the best way is to add Ant and shell projects the way it's done today and if someone want's to make project A depend on project B they can do so from the user interface. Continuum should always store the entire <dependencies> section of all Maven 1 and 2 projects, even if the dependent project isn't in Continuum. This makes it possible for Continuum to schedule a build if any of the (external/file) dependencies for a project has changed. Other CI systems have this feature and I think it's a useful feature.
Hide
Permalink
Emmanuel Venisse added a comment -

Done. We'll add ant and shell dependency in a new issue.

Show
Emmanuel Venisse added a comment - Done. We'll add ant and shell dependency in a new issue.

People

Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.