| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
This is looking in good shape!
Sorry, something went wrong.
| ); | ||
| core.setOutput("environment", result); | ||
| } catch (unwrappedError) { | ||
| const error = wrapError(unwrappedError); |
There was a problem hiding this comment.
Are there any known user errors that we should ignore? Eg- trying to resolve an unknown language? Trying to avoid spurious triggers of our SLOs.
Sorry, something went wrong.
There was a problem hiding this comment.
I think this will probably get addressed by the proposed handling of CLI errors in general: #1684 (comment)
Sorry, something went wrong.
There was a problem hiding this comment.
Nice! Some minor suggestions to improve this before we merge.
Sorry, something went wrong.
Co-authored-by: Henry Mercer <henry.mercer@me.com>
Co-authored-by: Henry Mercer <henry.mercer@me.com>
|
In addition to the basic integration test included in this PR, we also have an internal repo with a more comprehensive test matrix which covers most cases that the Go autobuilder distinguishes between when resolving build environments. That forms an end-to-end test for all the new components related to this work. |
Sorry, something went wrong.
There was a problem hiding this comment.
One improvement around better CLI error handling for old CLIs, otherwise this LGTM.
Sorry, something went wrong.
There was a problem hiding this comment.
Checks are currently failing since nightly-latest doesn't have a version number of 2.13.4+ yet. I suggest we point to the new 2.13.4 bundle directly (stable-v2.13.4) or alternatively wait until #1721 is merged and use latest in the checks.
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for addressing the feedback on the naming of the check step! This LGTM ![]()
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
This PR adds a new resolve-environment action which calls the new CLI resolve build-environment command to try and infer a configuration for the build environment that is suitable for the autobuilder. Example workflow (assuming a repository with a Go project):
The action performs the following work: