You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a temporary URL of the docs when a PR is submitted to any of the docs/<version> branches so the person who submits it can preview the docs
Create a temporary URL of the website when a PR is submitted so the person who submits it can preview the website
Create a temporary URL of the docs and website to be part of a release pipeline so it can be previewed during the release vote
Numbers 1 through 3 are higher priority than 4 through 6.
Due to the fact we cannot use Azure DevOps for PRs due to Apache permission limitations, we should use GitHub Actions for those tasks. It would also be pretty simple to setup GitHub actions to auto-deploy the website when master is updated. I recently used path filters on a GitHub Actions workflow to exclude paths that don't apply to the workflow, which would work perfectly for this scenario.
GitHub Actions doesn't load workflow files with a . in the name
Apache has a limited number of build agents for GitHub Actions, so long-running tasks should be done in Azure DevOps
A GitHub Actions PR workflow will run if additional commits are pushed to the PR branch
The only two steps above that need to be part of the Azure DevOps release are numbers 2 and 6. Number 6 could be part of the Release stage on the build pipeline in YAML (preferred) or as a step prior to the Manual Intervention step (the vote) on the Release pipeline. Number 2 could be fully automated after the Manual Intervention step.
I believe all of the other workflows can be added as GitHub Actions.
Breaking this task down into 6 different workflows, can you think of anything that was overlooked or that cannot be fully automated?
Depends on #282
Part of the docs building process is to update the website with new links/pages to the docs. This part should be automated.
The text was updated successfully, but these errors were encountered: