You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (Created) (JIRA)" <ji...@apache.org> on 2011/10/13 19:09:12 UTC
[jira] [Created] (DERBY-5461) ant release should not continue
automatically if svn commit fails
ant release should not continue automatically if svn commit fails
-----------------------------------------------------------------
Key: DERBY-5461
URL: https://issues.apache.org/jira/browse/DERBY-5461
Project: Derby
Issue Type: Improvement
Components: Build tools
Reporter: Myrna van Lunteren
Priority: Minor
On my windows system, ant release results in a release.properties file with inconsistent line endings. While that may be a problem in itself, what's a bigger issue is that the build process attempts to issue svn commit, and when that fails, goes on merrily, resulting in a build with a revision number with 'M' because the tree isn't clean.
There could be other issues resulting in a failed svn commit.
This could be improved if the build process would halt on failure and e.g. prompt for 'a(bort) /c(continue)'. This pause would give the release manager a chance to evaluate in another window/shell what's wrong with svn commit and possibly resolve manually (including manual svn commit) and continue, or start over.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5461) ant release should not continue
automatically if svn commit fails
Posted by "Myrna van Lunteren (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren updated DERBY-5461:
--------------------------------------
Description:
On my windows system, ant release results in a release.properties file with inconsistent line endings. While that may be a problem in itself, what's a bigger issue is that the build process attempts to issue svn commit, and when that fails, goes on merrily, resulting in a build with a revision number with 'M' because there uncommitted changes in the tree.
There could be other issues resulting in a failed svn commit.
This could be improved if the build process would halt on failure and e.g. prompt for 'a(bort) /c(continue)'. This pause would give the release manager a chance to evaluate in another window/shell what's wrong with svn commit and possibly resolve manually (including manual svn commit) and continue, or start over.
was:
On my windows system, ant release results in a release.properties file with inconsistent line endings. While that may be a problem in itself, what's a bigger issue is that the build process attempts to issue svn commit, and when that fails, goes on merrily, resulting in a build with a revision number with 'M' because the tree isn't clean.
There could be other issues resulting in a failed svn commit.
This could be improved if the build process would halt on failure and e.g. prompt for 'a(bort) /c(continue)'. This pause would give the release manager a chance to evaluate in another window/shell what's wrong with svn commit and possibly resolve manually (including manual svn commit) and continue, or start over.
> ant release should not continue automatically if svn commit fails
> -----------------------------------------------------------------
>
> Key: DERBY-5461
> URL: https://issues.apache.org/jira/browse/DERBY-5461
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Reporter: Myrna van Lunteren
> Priority: Minor
>
> On my windows system, ant release results in a release.properties file with inconsistent line endings. While that may be a problem in itself, what's a bigger issue is that the build process attempts to issue svn commit, and when that fails, goes on merrily, resulting in a build with a revision number with 'M' because there uncommitted changes in the tree.
> There could be other issues resulting in a failed svn commit.
> This could be improved if the build process would halt on failure and e.g. prompt for 'a(bort) /c(continue)'. This pause would give the release manager a chance to evaluate in another window/shell what's wrong with svn commit and possibly resolve manually (including manual svn commit) and continue, or start over.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira