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

Destructure Jenkins build result after knowing it's not an error #237

Merged
merged 1 commit into from
Jun 6, 2019

Conversation

phillipj
Copy link
Member

@phillipj phillipj commented Jun 5, 2019

We've seen some error logs in production suggesting that we get errors back from Jenkins when triggering builds, as the result is null | undefined. Destructuring fields out of that result causes unchaught exceptions, meaning the bot process dies.

Therefore postponing the destructuring until we're confident the build didn't result in an error.

/cc @nodejs/github-bot @richardlau

Refs #235

We've seen some error logs in production suggesting that we get errors
back from Jenkins when triggering builds, as the result is
`null | undefined`. Destructuring fields out of that result causes
unchaught exceptions, meaning the bot process dies.

Therefore postponing the destructuring until we're confident the build
didn't result in an error.
@phillipj phillipj merged commit e782b55 into nodejs:master Jun 6, 2019
@phillipj phillipj deleted the handle-build-errors branch June 6, 2019 07:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants