[jira] Created: (CONTINUUM-412) Add a "Build Now" link after each build definition
Add a "Build Now" link after each build definition -- Key: CONTINUUM-412 URL: http://jira.codehaus.org/browse/CONTINUUM-412 Project: Continuum Type: Wish Components: continuum-web Versions: 1.0 Reporter: David Blevins Priority: Minor It would be great to have a "Build Now" link on the same line as each build definition on a project's "Info" screen. Then it would be possible to force a build of a specific build definition in a project. This also solves another thing that I found it was oddly not possible to kick off a build from any of the project detail screens (Info, Builds, Working Copy). -- 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
[continuum build - SUCCESS - update] Wed Nov 2 04:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20051102.043000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051102.043000.txt
[continuum build - FAILED - update] Wed Nov 2 04:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051102.04.txt
[continuum build - FAILED - update] Wed Nov 2 03:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051102.033000.txt
[continuum build - FAILED - update] Wed Nov 2 03:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051102.03.txt
[continuum build - FAILED - update] Wed Nov 2 02:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051102.023000.txt
[continuum build - FAILED - update] Wed Nov 2 02:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051102.02.txt
[jira] Created: (CONTINUUM-411) add support to switch different jvm in one contimuum instance
add support to switch different jvm in one contimuum instance - Key: CONTINUUM-411 URL: http://jira.codehaus.org/browse/CONTINUUM-411 Project: Continuum Type: New Feature Components: continuum-core Versions: 1.1 Reporter: Jonas Lim Fix For: 1.1 It would be great feature if we can have continuum support switching of different JVM. For example, if I have 2 project X in continuum , it would be great if the first project builds on JDK 1.4 and the second project builds on JDK1.5. -- 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
[continuum build - FAILED - checkout] Wed Nov 2 01:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051102.013000.txt
Build schedules
I have a hard time understanding what exactly build schedules are supposed to do affect. The default schedule is hourly, but this doesn't cause builds to be kicked off hourly. What is the deal here? -David
[jira] Commented: (CONTINUUM-384) Build Error while queueing projects to be built
[ http://jira.codehaus.org/browse/CONTINUUM-384?page=comments#action_49762 ] witek wolejszo commented on CONTINUUM-384: -- We experience the same behaviour. java version "1.5.0_03" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_03-b07) Java HotSpot(TM) Client VM (build 1.5.0_03-b07, mixed mode, sharing) Sometimes, after database errors, state of a project on the list is inconsistent (error) with state of the latest build (success). Moving to the trunk version of Derby (Version 10.1 latest snapshot * Derby 10.1.1.1 (Oct 5, 2005 / SVN 292855) does not fix the problem - replaced the library and restarted Continuum. > Build Error while queueing projects to be built > --- > > Key: CONTINUUM-384 > URL: http://jira.codehaus.org/browse/CONTINUUM-384 > Project: Continuum > Type: Bug > Components: continuum-core > Versions: 1.0 > Environment: Linux running JDK 1.5.0_01 > Reporter: Bob Allison > Attachments: wrapper.log > > > I get periodic deadlock exceptions from Derby while building projects. It > does not happen regularly, just occasionally. I have two projects (IDs 1 and > 7) which are on a schedule to run every 15 minutes, and I have had the > problem occur four times in the last 18 hours. I have a third project (ID 6) > which runs once each day; there was no problem at the time it was scheduled > to run. Attached is a file with snippets from wrapper.log which show the > entire log from the four runs of the schedule which had a failure. -- 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] Reopened: (CONTINUUM-406) irc notifications: support for registered nicks
[ http://jira.codehaus.org/browse/CONTINUUM-406?page=all ] Brett Porter reopened CONTINUUM-406: I've not confirmed, but I think you will need to test this on freenode. they actually require you send something like /msg nickserv identify PASSWORD to the server to acknowledge you own the nick. What this probably requires is configuration to send a set of messages on connection - I couldn't see this in hte fix. > irc notifications: support for registered nicks > --- > > Key: CONTINUUM-406 > URL: http://jira.codehaus.org/browse/CONTINUUM-406 > Project: Continuum > Type: Improvement > Versions: 1.0 > Reporter: David Blevins > Assignee: Emmanuel Venisse > Priority: Minor > Fix For: 1.1 > > > It seems IRC notifications don't work on irc.freenode.net. i assume it's due > to them removing anonymous msg'ing. > Probably need to set it up to use a registered nick, and do the /msg identify > thing first -- 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-409) Email notifications could still include build stats when includeBuildResult is false
Email notifications could still include build stats when includeBuildResult is false Key: CONTINUUM-409 URL: http://jira.codehaus.org/browse/CONTINUUM-409 Project: Continuum Type: Wish Versions: 1.0 Reporter: David Blevins I really like the "Build statistics" and "Changes" sections continuum creates in the emails and definitely want them in every email. It's really just the section that contains the output generated from the build itself that I don't want as that will consistently be several megs of text for our project. Basically, I assumed 'includeBuildResults=false' would just exclude out everything after these lines Output: I really don't care what the option is called as long as I can get an email as described. Maybe you want to do something like this true true false -- 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
[continuum build - SUCCESS - update] Tue Nov 1 16:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20051101.163000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051101.163000.txt
[jira] Commented: (CONTINUUM-365) add shell command execution
[ http://jira.codehaus.org/browse/CONTINUUM-365?page=comments#action_49748 ] Emmanuel Venisse commented on CONTINUUM-365: yes, it what I mean. absolute path is now allowed. So, now, we search in working directory, in path. If executable isn't found, we use it without modification, so you can use rake or path_to/rake > add shell command execution > --- > > Key: CONTINUUM-365 > URL: http://jira.codehaus.org/browse/CONTINUUM-365 > Project: Continuum > Type: New Feature > Reporter: yo > Assignee: Emmanuel Venisse > Fix For: 1.1 > Attachments: build_def.png, continuum Kopie.log, project_def.png > > > add support for shell command execution and not only for shell script > execution. > This way, there is no need for the dedicated ant execution and shell script > execution module. This can be accomplished by running a shell command and you > automatically added support for make, rake, ... . -- 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
[continuum build - SUCCESS - update] Tue Nov 1 15:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20051101.15.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051101.15.txt
[continuum build - FAILED - update] Tue Nov 1 14:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051101.143000.txt
[jira] Closed: (CONTINUUM-365) add shell command execution
[ http://jira.codehaus.org/browse/CONTINUUM-365?page=all ] Emmanuel Venisse closed CONTINUUM-365: -- Assign To: Emmanuel Venisse Resolution: Fixed Fixed. I don't know why your rake isn't find in your path, but I create a little patch that fixed your pb. For other error in your log (scm pb and FileNotFoundException), it's already fixed. > add shell command execution > --- > > Key: CONTINUUM-365 > URL: http://jira.codehaus.org/browse/CONTINUUM-365 > Project: Continuum > Type: New Feature > Reporter: yo > Assignee: Emmanuel Venisse > Fix For: 1.1 > Attachments: build_def.png, continuum Kopie.log, project_def.png > > > add support for shell command execution and not only for shell script > execution. > This way, there is no need for the dedicated ant execution and shell script > execution module. This can be accomplished by running a shell command and you > automatically added support for make, rake, ... . -- 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
[continuum build - FAILED - update] Tue Nov 1 14:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051101.14.txt
[jira] Closed: (CONTINUUM-406) irc notifications: support for registered nicks
[ http://jira.codehaus.org/browse/CONTINUUM-406?page=all ] Emmanuel Venisse closed CONTINUUM-406: -- Resolution: Fixed Done. > irc notifications: support for registered nicks > --- > > Key: CONTINUUM-406 > URL: http://jira.codehaus.org/browse/CONTINUUM-406 > Project: Continuum > Type: Improvement > Versions: 1.0 > Reporter: David Blevins > Assignee: Emmanuel Venisse > Priority: Minor > Fix For: 1.1 > > > It seems IRC notifications don't work on irc.freenode.net. i assume it's due > to them removing anonymous msg'ing. > Probably need to set it up to use a registered nick, and do the /msg identify > thing first -- 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
[continuum build - SUCCESS - update] Tue Nov 1 13:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20051101.133000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051101.133000.txt
[jira] Commented: (CONTINUUM-378) "Build All" only builds the last project
[ http://jira.codehaus.org/browse/CONTINUUM-378?page=comments#action_49728 ] Emmanuel Venisse commented on CONTINUUM-378: Are you sure all your project as attached to an active schedule? It seems with your logs that only one project is attach to DEFAULT_SCHEDULE and DAILY schedules > "Build All" only builds the last project > > > Key: CONTINUUM-378 > URL: http://jira.codehaus.org/browse/CONTINUUM-378 > Project: Continuum > Type: Bug > Versions: 1.0 > Reporter: Scott Schram > Priority: Minor > Fix For: 1.1 > > > I have 4 projects in Continuum, and when I am on the "Show Projects" page, > and press "Build All" only the last project shows up as "In Queue", and the > other 3 projects don't get built. -- 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] Closed: (CONTINUUM-408) Description for DEFAULT_SCHEDULE is wrong
[ http://jira.codehaus.org/browse/CONTINUUM-408?page=all ] Emmanuel Venisse closed CONTINUUM-408: -- Resolution: Won't Fix we use quartz syntax > Description for DEFAULT_SCHEDULE is wrong > - > > Key: CONTINUUM-408 > URL: http://jira.codehaus.org/browse/CONTINUUM-408 > Project: Continuum > Type: Bug > Components: continuum-web > Versions: 1.0 > Reporter: David Blevins > Priority: Trivial > > > Description for DEFAULT_SCHEDULE says hourly, when "0 0 * * *" is daily. -- 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] Commented: (CONTINUUM-408) Description for DEFAULT_SCHEDULE is wrong
[ http://jira.codehaus.org/browse/CONTINUUM-408?page=comments#action_49723 ] David Blevins commented on CONTINUUM-408: - Never mind, I didn't realize the syntax was different that vixie cron > Description for DEFAULT_SCHEDULE is wrong > - > > Key: CONTINUUM-408 > URL: http://jira.codehaus.org/browse/CONTINUUM-408 > Project: Continuum > Type: Bug > Components: continuum-web > Versions: 1.0 > Reporter: David Blevins > Priority: Trivial > > > Description for DEFAULT_SCHEDULE says hourly, when "0 0 * * *" is daily. -- 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
