integrating with continuum
Hi there, I am new to Continuum and was wondering if it is possible to extend Continuum by adding new project types. I'd like to add my own Add XXX Project link on the Continuum page next to the other links for Maven, Maven2, Ant, and Shell projects. Or alternatively if I could use an API to add my projects programatically to the database. Is this already possible? TIA, Knut Wannheden
Re: integrating with continuum
You can't add an other type of project. What is your project type? We have a start of xmlrpc client in jira that can manage continuum, but it don't help you with new project type. Emmanuel Knut Wannheden a écrit : Hi there, I am new to Continuum and was wondering if it is possible to extend Continuum by adding new project types. I'd like to add my own Add XXX Project link on the Continuum page next to the other links for Maven, Maven2, Ant, and Shell projects. Or alternatively if I could use an API to add my projects programatically to the database. Is this already possible? TIA, Knut Wannheden
[jira] Commented: (CONTINUUM-385) run.sh on MacOS X fails with problem in wrapper
[ http://jira.codehaus.org/browse/CONTINUUM-385?page=comments#action_57523 ] Konstntin Polyzois commented on CONTINUUM-385: -- Any news on this one? run.sh on MacOS X fails with problem in wrapper --- Key: CONTINUUM-385 URL: http://jira.codehaus.org/browse/CONTINUUM-385 Project: Continuum Type: Bug Components: Core system Versions: 1.0 Environment: Mac OS X 10.4 Reporter: Mark Donszelmann Priority: Minor Fix For: 1.1 Hi running continuum 1.0 on MacOS X 10.4 gives me the following when started as: bin/macosx/runs.h start or bin/macosx/runs.h console -- Output Running continuum... Removed stale pid file: ./continuum.pid wrapper | -- Wrapper Started as Console dyld: lazy symbol binding failed: Symbol not found: _ftime Referenced from: /Users/duns/java/continuum-1.0/bin/macosx/wrapper Expected in: /usr/lib/libcrypto.0.9.7.dylib dyld: Symbol not found: _ftime Referenced from: /Users/duns/java/continuum-1.0/bin/macosx/wrapper Expected in: /usr/lib/libcrypto.0.9.7.dylib Trace/BPT trap -- while if I run bin/plexus.sh all works fine (but only interactively. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: integrating with continuum
Knut Wannheden a écrit : Emmanuel, On 2/1/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: You can't add an other type of project. What is your project type? In our development enviroment we have our own project file format (similar to Maven POM) and our own build tools on top of this. The reason we are not using any existing tools, like Maven, ist that we had some specific requirements which other tools could not handle at the time we implemented this. This development and build environment is developed in Java so I was hoping that it would be easy to integrate as some kind of extension to Continuum. I'd like to add projects with interdependencies to Continuum. Can I also use the shell project type for this? You can use the shell project type. You only need a command line to launch your build. Interdependencies between projects are available for now only for maven projects. We'll add this feature for ant and shell projects in 1.1 As we have very many projects, which also change over time, I'd like to use some kind of API to keep the project definitions in Continuum in sync. Thus I was wondering about adding new project types or an API to add projects. What sort of changes do you want to do? Can you see a viable solution to this? Or should I enter a feature request in JIRA? Look at CONTINUUM-544 for a xmlrpc client. I'll integrate it later in continuum. Regards, --knut
Re: integrating with continuum
Knut Wannheden a écrit : I'd like to add projects with interdependencies to Continuum. Can I also use the shell project type for this? You can use the shell project type. You only need a command line to launch your build. Interdependencies between projects are available for now only for maven projects. We'll add this feature for ant and shell projects in 1.1 OK. I think I remember reading somewhere that the shell project type is currently limited in that way. So I'm looking forward to the 1.1 release. As we have very many projects, which also change over time, I'd like to use some kind of API to keep the project definitions in Continuum in sync. Thus I was wondering about adding new project types or an API to add projects. What sort of changes do you want to do? I'm not sure I quite understand your question. But let me explain what I'd like to do. We have 100+ projects in our development environment and occasionally we add new projects and change the dependencies between existing projects. We also change the developer list for the projects. Obviously I'd like the definitions in Continuum to stay in sync without having to enter and verify that manually. I have my answer ;-) You'll can do it by xmlrpc client api. Can you see a viable solution to this? Or should I enter a feature request in JIRA? Look at CONTINUUM-544 for a xmlrpc client. I'll integrate it later in continuum. That certainly looks interesting. I see this is also scheduled for 1.1. Is there an estimated relases date for 1.1? It's perhaps in 1.0.3. alpha of 1.1 will probably release in 2006Q1 and final in 2006Q2 Emmanuel Regards, --knut
Re: integrating with continuum
Emmanuel, I'm not sure I quite understand your question. But let me explain what I'd like to do. We have 100+ projects in our development environment and occasionally we add new projects and change the dependencies between existing projects. We also change the developer list for the projects. Obviously I'd like the definitions in Continuum to stay in sync without having to enter and verify that manually. I have my answer ;-) You'll can do it by xmlrpc client api. Excellent! That certainly looks interesting. I see this is also scheduled for 1.1. Is there an estimated relases date for 1.1? It's perhaps in 1.0.3. alpha of 1.1 will probably release in 2006Q1 and final in 2006Q2 Sounds good. I'm looking forward for these enhancements! Cheers, --knut
[jira] Updated: (CONTINUUM-510) big year schedule 2099 prevents continuum from startup
[ http://jira.codehaus.org/browse/CONTINUUM-510?page=all ] John Casey updated CONTINUUM-510: - Fix Version: (was: 1.1-alpha-1) 1.0.3 big year schedule 2099 prevents continuum from startup Key: CONTINUUM-510 URL: http://jira.codehaus.org/browse/CONTINUUM-510 Project: Continuum Type: Bug Components: Web interface, Core system Versions: 1.0.2 Environment: xp,starteam Reporter: Dan Tran Assignee: Emmanuel Venisse Fix For: 1.0.3 - Create a scheduler with year 2099 ( ex 0 15 10 * * ? 2100 ) Continuum does throw exception letting user know it will never got fired but still add it to dabase - Assign the newly create scheduler to a project - restart - Continuum webapp never get started The only solution i can think of is to remove database and start from scratch According to Evenisse, Quart does not allow year 2099 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-531) Add back the build now button on the view project page.
[ http://jira.codehaus.org/browse/CONTINUUM-531?page=all ] John Casey updated CONTINUUM-531: - Fix Version: (was: 1.1-alpha-1) 1.0.3 Add back the build now button on the view project page. --- Key: CONTINUUM-531 URL: http://jira.codehaus.org/browse/CONTINUUM-531 Project: Continuum Type: Bug Components: Web interface Versions: 1.0.2 Reporter: Trygve Laugstol Assignee: nick gonzalez Fix For: 1.0.3 Attachments: CONTINUUM-531.patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-567) A build must be launched if we have changes since last build (for same build definition) and not only if we have detected changes when we run scm update commad
[ http://jira.codehaus.org/browse/CONTINUUM-567?page=all ] John Casey updated CONTINUUM-567: - Fix Version: (was: 1.1-alpha-1) 1.0.3 A build must be launched if we have changes since last build (for same build definition) and not only if we have detected changes when we run scm update commad --- Key: CONTINUUM-567 URL: http://jira.codehaus.org/browse/CONTINUUM-567 Project: Continuum Type: Improvement Components: Core system Versions: 1.0.2 Reporter: Emmanuel Venisse Assignee: nick gonzalez Fix For: 1.0.3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-354) Need a way to poll for new projects
[ http://jira.codehaus.org/browse/CONTINUUM-354?page=all ] John Casey updated CONTINUUM-354: - Fix Version: (was: 1.1-alpha-1) 1.0.3 Need a way to poll for new projects --- Key: CONTINUUM-354 URL: http://jira.codehaus.org/browse/CONTINUUM-354 Project: Continuum Type: Improvement Versions: 1.0-beta-1 Reporter: Matthew Beermann Assignee: nick gonzalez Fix For: 1.0.3 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-496) End Time contains junk value when I forced a build to run
[ http://jira.codehaus.org/browse/CONTINUUM-496?page=all ] John Casey updated CONTINUUM-496: - Fix Version: (was: 1.1-alpha-1) 1.0.3 End Time contains junk value when I forced a build to run - Key: CONTINUUM-496 URL: http://jira.codehaus.org/browse/CONTINUUM-496 Project: Continuum Type: Bug Components: Core system Versions: 1.0.2 Reporter: John Sisson Assignee: Emmanuel Venisse Priority: Minor Fix For: 1.0.3 The following is from the build history when it was building. Note the end time on the first line: Dec 1, 2005 10:23:11 PM Dec 31, 1969 4:00:00 PM BuildingResult 22Dec 1, 2005 10:00:18 PM Dec 1, 2005 10:06:51 PM Success Result 21Dec 1, 2005 7:00:16 PM Dec 1, 2005 7:03:57 PM Success Result This occurred on http://ci.gbuild.org/continuum/servlet/continuum running a 1.1-SNAPSHOT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-576) all builds stuck in in progress/scheduled state
all builds stuck in in progress/scheduled state - Key: CONTINUUM-576 URL: http://jira.codehaus.org/browse/CONTINUUM-576 Project: Continuum Type: Bug Components: Core system Reporter: Brett Porter Fix For: 1.0.3 ci.codehaus.org was stuck in this state for about 20 days and noone noticed :) I know we have corrective measures on startup - is that something that can be done when a build is triggered? Another option is to go all the way to detecting if the build process still exists, which would allow the ability to implement stop functionality as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
