-
Notifications
You must be signed in to change notification settings - Fork 6k
Fixes to the CI document #2161
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
Fixes to the CI document #2161
Conversation
* use install script in build matrix * add travis docs, and template * travis, add custom install using install script
* use install script in build matrix * add travis docs, and template * travis, add custom install using install script
Stand-by ... I'll see if I can get that failure fixed. |
Update
@mairaw @rpetrusha Nice ... a little extra polish on this last pass. It's ready for 👀 now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@guardrex This looks great.
I had one wording suggestion. See what you think. Then,
docs/core/tools/using-ci-with-cli.md
Outdated
# Run the build process now. Implement your build script here. | ||
``` | ||
|
||
You provide the implementation for your build process at the end of the script. When run and after the tooling is acquired, the script executes your build process. For UNIX machines, the following bash script performs the actions described in the PowerShell script in a similar manner: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: "When run and after tooling is acquired" seems awkward. Maybe say "The script acquires the tools and then executes your build process."
Various fixes to the CI document.
Replaces #1556
Fixes #1454