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

Simplify the docs CI pipeline #48005

Closed
wants to merge 1 commit into from
Closed

Conversation

ptgott
Copy link
Contributor

@ptgott ptgott commented Oct 28, 2024

Closes #35796

Only run the workflow on pull_request. It is not strictly necessary to run the workflow on merge_group, and doing so on pull_request simplifies the branching logic we use in the workflow.

Test the docs build using the checkout GitHub Actions workflow, rather than using the name of the branch. This way, we don't need custom logic to identify the branch name. To get this to work, turn the git-update script in package.json into a no-op script. This will also make it easier to add the prose linting step to Lint (Docs) in the future, since we pull the gravitational/teleport source outside of the yarn update-and-build command.

Combine the Vercel preview workflow and "test the docs build" step: Both of these run the docs build, so there is no need to separate the build step from the Vercel preview. This saves around 8-10 minutes of runner time per workflow run.

Closes #35796

**Only run the workflow on `pull_request`**. It is not strictly
necessary to run the workflow on `merge_group`, and doing so on
`pull_request` simplifies the branching logic we use in the workflow.

**Test the docs build using the `checkout` GitHub Actions workflow**,
rather than using the name of the branch. This way, we don't need custom
logic to identify the branch name. To get this to work, turn the
`git-update` script in `package.json` into a no-op script. This will
also make it easier to add the prose linting step to `Lint (Docs)` in
the future, since we pull the `gravitational/teleport` source outside of
the `yarn update-and-build` command.

**Combine the Vercel preview workflow and "test the docs build" step:**
Both of these run the docs build, so there is no need to separate the
build step from the Vercel preview. This saves around 8-10 minutes of
runner time per workflow run.
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-48005.d3pp5qlev8mo18.amplifyapp.com

@ptgott
Copy link
Contributor Author

ptgott commented Oct 29, 2024

Closing since the Vercel preview workflow will soon become obsolete, so it'll be simpler to remove it.

@ptgott ptgott closed this Oct 29, 2024
@ptgott ptgott deleted the paul.gottschling/35796-build branch October 29, 2024 19:41
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.

Remove the "Test the docs build" GitHub Actions step
1 participant