[jira] Updated: (CONTINUUM-34) Keep trying till build works, notify via email what is required
[ http://jira.codehaus.org/browse/CONTINUUM-34?page=all ] Brett Porter updated CONTINUUM-34: -- Fix Version: (was: 1.0) 1.1-alpha-1 Keep trying till build works, notify via email what is required --- Key: CONTINUUM-34 URL: http://jira.codehaus.org/browse/CONTINUUM-34 Project: Continuum Type: Wish Reporter: David Blevins Priority: Minor Fix For: 1.1-alpha-1 I don't know if this is relevant to continuum's style of building, but I have a script that scm updates then builds an m1 project with the default, i.e. using just 'maven' with no goals supplied. This works the majority of time, but every once in a while someone refactors something and i need to do a clean build to really get everything to build. The idea: Have the concept of escalating the depth of the build till it works (or until you've tried everything). If you find one that works send an email that lists the exact steps (or maven command) required to get your build to work again. Example scenario 1: $ cvs update -dP $ maven BUILD FAILED $ maven clean default BUILD SUCCESSFUL (email sent suggesting people do a 'maven clean default' after updating) Example scenario 2: $ cvs update -dP $ maven BUILD FAILED $ maven clean default BUILD FAILED $ cvs co alanparsons $ cd alanparsons $ maven BUILD SUCCESSFUL (email sent suggesting people get a clean checkout of the alanparsons project before attempting to build) -- 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-265) Concurrent builds
[ http://jira.codehaus.org/browse/CONTINUUM-265?page=all ] Brett Porter updated CONTINUUM-265: --- Fix Version: (was: 1.0) 1.1-alpha-1 Concurrent builds - Key: CONTINUUM-265 URL: http://jira.codehaus.org/browse/CONTINUUM-265 Project: Continuum Type: New Feature Components: continuum-core Reporter: Torsten Curdt Fix For: 1.1 Instead of processing the builds sequentially it would be great to be able to specify how many projects are being build concurrently. -- 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-156) should validate that an updated pom doesn't change too drastically
[ http://jira.codehaus.org/browse/CONTINUUM-156?page=all ] Brett Porter updated CONTINUUM-156: --- Fix Version: (was: 1.0-beta-1) 1.1 should validate that an updated pom doesn't change too drastically -- Key: CONTINUUM-156 URL: http://jira.codehaus.org/browse/CONTINUUM-156 Project: Continuum Type: Improvement Reporter: Brett Porter Fix For: 1.1 I added maven-core's POM, which is using a post -alpha-2 technique of inheriting the SCM connection URL and appending the artifact ID. This resulted in the new SCM URL being different and so it checked out the root POM and proceeded to checkout all of maven/components/trunk. IF the group ID/artifact ID of the POM changes on update, I think this needs to go into an error state that requires user intervention to either accept it has changed, or find out what is wrong. -- 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-143) We need to categorize error states and display them useful messages to the user
[ http://jira.codehaus.org/browse/CONTINUUM-143?page=all ] Brett Porter updated CONTINUUM-143: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 We need to categorize error states and display them useful messages to the user --- Key: CONTINUUM-143 URL: http://jira.codehaus.org/browse/CONTINUUM-143 Project: Continuum Type: Improvement Versions: 1.0-alpha-3 Reporter: Jason van Zyl Fix For: 1.0-beta-2 Right now we're only tracking checkout errors but we need to categorize all error so that we can easily extract them and display useful messages to the user. -- 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-153) GET has side effects - Deleting a project.
[ http://jira.codehaus.org/browse/CONTINUUM-153?page=all ] Brett Porter updated CONTINUUM-153: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 GET has side effects - Deleting a project. -- Key: CONTINUUM-153 URL: http://jira.codehaus.org/browse/CONTINUUM-153 Project: Continuum Type: Bug Components: continuum-web Reporter: Brett Porter Fix For: 1.0-beta-2 I'm paranoid google web accelerator is going to delete projects from continuum :) The delete link should use a POST HTTP method (probably make it a form button) instead of GET. -- 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-176) adding parent pom create duplicate continuum projects for all children
[ http://jira.codehaus.org/browse/CONTINUUM-176?page=all ] Brett Porter updated CONTINUUM-176: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 adding parent pom create duplicate continuum projects for all children -- Key: CONTINUUM-176 URL: http://jira.codehaus.org/browse/CONTINUUM-176 Project: Continuum Type: Bug Versions: 1.0-alpha-2 Reporter: Ryan Sonnek Assignee: Trygve Laugstol Fix For: 1.0-beta-2 adding my parent maven2 project to continuum creates a continuum project for each of my subprojects. the continuum project's start off with the label of my subprojects, but once the build run's they all revert to the label of the parent projects. the build process for each of the subproject's is the same as well. they don't actually just build the subproject. continuum builds the entire project. try using my project's pom at https://shard.dev.java.net/source/browse/*checkout*/shard/pom.xml for an example. -- 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-225) Collect all build/execution classes for a particular tool like Maven into a single package
[ http://jira.codehaus.org/browse/CONTINUUM-225?page=all ] Brett Porter updated CONTINUUM-225: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 Collect all build/execution classes for a particular tool like Maven into a single package -- Key: CONTINUUM-225 URL: http://jira.codehaus.org/browse/CONTINUUM-225 Project: Continuum Type: Improvement Reporter: Jason van Zyl Fix For: 1.0-beta-2 Right now there are build execution classes for Maven in one place and project builder classes for maven in another. We need to package them up into a single module for clarity. -- 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-319) Project state is set to check when build reports failure.
[ http://jira.codehaus.org/browse/CONTINUUM-319?page=all ] Brett Porter updated CONTINUUM-319: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 Project state is set to check when build reports failure. --- Key: CONTINUUM-319 URL: http://jira.codehaus.org/browse/CONTINUUM-319 Project: Continuum Type: Bug Versions: 1.0-alpha-4 Environment: Windows XP and Sun JDK142_04 Reporter: Fritz Oconer Fix For: 1.0-beta-2 Attachments: scrn_shot.GIF When building a project where it return test failures, the states is set to check image instead of x. -- 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-203) Plexus runtime should have solaris capability
[ http://jira.codehaus.org/browse/CONTINUUM-203?page=all ] Brett Porter updated CONTINUUM-203: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 Plexus runtime should have solaris capability - Key: CONTINUUM-203 URL: http://jira.codehaus.org/browse/CONTINUUM-203 Project: Continuum Type: Improvement Reporter: Jason van Zyl Assignee: Trygve Laugstol Fix For: 1.0-beta-2 The plexus runtime generator needs to be improved to have this. -- 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-245) Define what default information Continuum should populate on its first startup
[ http://jira.codehaus.org/browse/CONTINUUM-245?page=all ] Brett Porter updated CONTINUUM-245: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 Define what default information Continuum should populate on its first startup -- Key: CONTINUUM-245 URL: http://jira.codehaus.org/browse/CONTINUUM-245 Project: Continuum Type: Task Reporter: Jason van Zyl Fix For: 1.0-beta-2 Continuum is becoming more configurable but it would still be nice if Continuum could run out of the box by picking up system information like the: o JDK (the one used to run Continuum) o Default schedule (hourly is probably fine using update mode) o Ant o Maven 1.x o Maven 2.x -- 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-150) Continuum site needs screenshots
[ http://jira.codehaus.org/browse/CONTINUUM-150?page=all ] Brett Porter updated CONTINUUM-150: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 Continuum site needs screenshots Key: CONTINUUM-150 URL: http://jira.codehaus.org/browse/CONTINUUM-150 Project: Continuum Type: Improvement Reporter: Henri Yandell Priority: Minor Fix For: 1.0-beta-2 The Continuum site needs to show screenshots to better sell Continuum to interested parties. -- 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] Thu Sep 29 14:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050929.14.txt
[continuum build - FAILED - update] Thu Sep 29 15:30:03 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050929.153003.txt
[continuum build - FAILED - update] Thu Sep 29 17:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050929.173000.txt
[jira] Created: (CONTINUUM-325) Refactor configurationService tor store conf in database instead of configuration.xml
Refactor configurationService tor store conf in database instead of configuration.xml - Key: CONTINUUM-325 URL: http://jira.codehaus.org/browse/CONTINUUM-325 Project: Continuum Type: Task Components: continuum-core Reporter: Emmanuel Venisse Assigned to: Emmanuel Venisse Fix For: 1.0-beta-1 -- 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] Thu Sep 29 19:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050929.193001.txt
[jira] Closed: (CONTINUUM-326) Create an initialization page for setup the continuum configuration
[ http://jira.codehaus.org/browse/CONTINUUM-326?page=all ] Emmanuel Venisse closed CONTINUUM-326: -- Resolution: Fixed Done. Create an initialization page for setup the continuum configuration --- Key: CONTINUUM-326 URL: http://jira.codehaus.org/browse/CONTINUUM-326 Project: Continuum Type: New Feature Components: continuum-web Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-beta-1 -- 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 - checkout] Fri Sep 30 01:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20050930.013000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050930.013000.txt
