Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error recovery #15

Open
scottgonzalez opened this issue Dec 19, 2013 · 2 comments
Open

Error recovery #15

scottgonzalez opened this issue Dec 19, 2013 · 2 comments

Comments

@scottgonzalez
Copy link
Member

@scottgonzalez scottgonzalez commented Dec 19, 2013

If a task errors out, we should log all the state so we can restart the release process. When restarting, it should be possible to pick which step to start from, but there should be a sane default if that's possible.

@jzaefferer
Copy link
Member

@jzaefferer jzaefferer commented Mar 19, 2014

If npm is down, it should be easy to try that again, without having to delete tags and what not. If a commit message ends up wrong, it should be possible to fix that and go from there again.

@jzaefferer
Copy link
Member

@jzaefferer jzaefferer commented Mar 21, 2014

Working on changelog and contributors is super painful right now, since our fake-project has no commits nor issues, and while we could generate both, we're not going to have trac issues. Testing with jquery-ui I currently remove big chunks from the tasks in release.js, but since _cloneRepo also does npm install, its gonna take a while anyway.

One option we should consider is exatracting the changelog and contributors generation into a separate module. It just writes two files and doesn't need to commit anything, so lends itself well to unit test automation.

If we don't want to extract, we should at least come up with a way to run those methods directly, without all the slow setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.