ehmicky
ehmicky
Since logs might contain security-sensitive information that Build plugins should not access, I have opened a separate issue for that at #844.
(Side note from last meeting: this utility should be implemented as a separate package)
Done by #373.
Just to be very clear, what I meant was: buildbot would do: ```bash export NETLIFY_AUTH_TOKEN=token netlify-build ... unset NETLIFY_AUTH_TOKEN ``` `netlify-build` would remove `NETLIFY_AUTH_TOKEN` from the environment variables passed to...
It turns out that are some ways to do it indeed. > Imho, the only completely secure solution is to use pipes (stdin) or put the token into a file...
Thanks for finding this bug @ascorbic. This is a bug in Bitballoon and the buildbot. I have filed https://github.com/netlify/buildbot/issues/1911 to keep track of it. The problem and its solution seems...
Hi @seandstewart, Thanks for reaching out! This repository is not directly involved in post-processing. However, I have transferred the bug description to the team working on this feature, so we...
Hi @seandstewart, Thanks for following up. Unfortunately not. We'll keep you updated as soon as this is fixed!
Would the error monitoring in Datadog and Bugsnag be more appropriate to catch those failures? Which value would we get from knowing how long failed builds last in average?
We do have this build duration metric in place out of the box, which would make it easy to implement sending the build duration of failed builds. However, I am...