Need a way to poll for new projects

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 1.0-beta-1
  • Fix Version/s: None
  • Component/s: Core system
  • Labels:
    None
  • Complexity:
    Intermediate

Description

The feature where Continuum can populate its build list from a URL is wonderful; it'd be even more wonderful if it could remember that URL and poll it periodically. We have a "master build list" of all projects that we'll use to initially populate the build database; but ideally we could simply add a new project to that in CVS and have Continuum just pick it up.

This is a feature that we've (somewhat painfully) managed to implement in CruiseControl, and it's a must-have if we're going to switch over... this might or might not depend on CONTINUUM-330.

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. CONTINUUM-330 POM-only projects ignored. Causes problems with parent/child module pattern

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is superceded by

Improvement - An improvement or enhancement to an existing feature or task. CONTINUUM-798 Modules automatic discovery

  • Major - Major loss of function.
  • In Progress - This issue is being actively worked on at the moment by the assignee.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Trygve Laugstol added a comment -

I'm pretty sure that CONTIUUM-330 will solve this automatically, but it might be possible that we might want a smarter way, including includes and exclude patterns for projects etc.

Show
Trygve Laugstol added a comment - I'm pretty sure that CONTIUUM-330 will solve this automatically, but it might be possible that we might want a smarter way, including includes and exclude patterns for projects etc.
Hide
Permalink
Matthew Beermann added a comment -

No, CONTINUUM-330 didn't solve this. Here's why:

1. Add a new <module/> to the parent project and check in.
2. Rebuild the parent project.
3. I would expect the new module to be added to the Continuum project list, if it doesn't exist already. However, no such thing occurs.

It seems that Continuum will check/add modules when the parent project is first added, but not when the parent project changes. It should, IMO.

Show
Matthew Beermann added a comment - No, CONTINUUM-330 didn't solve this. Here's why: 1. Add a new <module/> to the parent project and check in. 2. Rebuild the parent project. 3. I would expect the new module to be added to the Continuum project list, if it doesn't exist already. However, no such thing occurs. It seems that Continuum will check/add modules when the parent project is first added, but not when the parent project changes. It should, IMO.
Hide
Permalink
Brill Pappin added a comment -

+1 for adding new sub modules when detected. Its a real pain in the ass that it doesn't.

I've actually managed to currupt the database (and can't seem to get it to recover) when the same project got added twice.

Show
Brill Pappin added a comment - +1 for adding new sub modules when detected. Its a real pain in the ass that it doesn't. I've actually managed to currupt the database (and can't seem to get it to recover) when the same project got added twice.

People

  • Assignee:
    Unassigned
    Reporter:
    Matthew Beermann
Vote (4)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved: