Skip to end of metadata
Comment: Migrated to Confluence 4.0
Go to start of metadata

Based on Kenney proposal

Problem 

If project A depends on project B, and project B was updated/rebuilt, then A should also be rebuilt to check for any api breaking changes etc.

Solution

After the SCM check to see if there are any source changes, we need to add an other check to see if any dependencies artifacts are newer.

 Dependency is a Continuum project

 For each dependency added in Continuum, we need to check the date of the latest build. If it is more recent than the latest build of the current project and it is in success, the dependency is newer and it is added in dependencies changes list.

Dependency isn't a Continuum project

 Continuum look in repositories (local and remote) if a new timestamped version of the dependency is available. A new timestamped version is a version that is more recent than the latest build of the current project.

 It isn't necessary to check dcependencies if they aren't SNAPSHOT dependencies.

Parent projects

 A parent can be considerated as a dependency (Continuum project or not). The parent must be added in the dependency list during the project creation/update.

Questions

  •  I'm not sure it's necessary to check latest build for depencencies that are in Continuum? Maybe we can check only timestamped versions.
Labels
  • None

3 Comments

Hide/Show Comments

  1. Nov 12, 2006

    Brett Porter

    • on snapshot dependencies, you'd need to track which versions were used last time, not just if the local repository has been updated. I'd suggest leaving this for a later enhancement and just do the inter-Continuum dependencies
    • we need to check that the dependency version == the continuum project version (otherwise it's using it from the repository anyway)
    • I don't understand the question at the end? The description you have in "dependency as a continuum project" sounds right.

  2. Nov 13, 2006

    Emmanuel Venisse

    about the question, I meant that if we implement build on dependencies changes where the dependency isn't a continuum project, we need to look in the repo for new version checks. For this reason, we can look in repo too for dependency that is a continuum project too, because it is in the local repo too. If we do it, we don't have to implement the latest build check but only a repo check.

  3. Nov 13, 2006

    Brett Porter

    right - thanks. However, given that the repo check is not going to be accurate without additional work, I think we should just go with the build times (pull #2 from Kenney's mail)