[jira] Updated: (CONTINUUM-264) Keep trying after scm failed updating
[ http://jira.codehaus.org/browse/CONTINUUM-264?page=all ] Emmanuel Venisse updated CONTINUUM-264: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 Keep trying after scm failed updating - Key: CONTINUUM-264 URL: http://jira.codehaus.org/browse/CONTINUUM-264 Project: Continuum Type: Improvement Components: continuum-core Versions: 1.0-alpha-3 Environment: linux, sun jdk 1.4 (not important) Reporter: Torsten Curdt Fix For: 1.0-beta-2 Currently a failed update from the scm and a broken build are being treated the same. IMO it would be better just to set a warning state for that project and retry building with the next trigger. Whether the warning emits an email or not should be configurable. -- 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-264) Keep trying after scm failed updating
[ http://jira.codehaus.org/browse/CONTINUUM-264?page=all ] Emmanuel Venisse updated CONTINUUM-264: --- Fix Version: (was: 1.0-alpha-4) 1.0-beta-1 Keep trying after scm failed updating - Key: CONTINUUM-264 URL: http://jira.codehaus.org/browse/CONTINUUM-264 Project: Continuum Type: Improvement Components: continuum-core Versions: 1.0-alpha-3 Environment: linux, sun jdk 1.4 (not important) Reporter: Torsten Curdt Fix For: 1.0-beta-1 Currently a failed update from the scm and a broken build are being treated the same. IMO it would be better just to set a warning state for that project and retry building with the next trigger. Whether the warning emits an email or not should be configurable. -- 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
