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
Hotel - also maybe as a side project, set up auto-deploy forCI build artifacts from PRs to a staging URL so the results can be verified online (:
Jonathan - I would love to see that happen, not really sure what all we have in the way of a staging domain though. My first thought was to use github pages or something similar, could we do this with the existing azure-pipelines setup though?
Hotel - my initial thought was to set up a branch on this repo for gh-pages to use and then have the pipeline commit the artifacts there under a folder keyed to the PR so you'd be able to get to the build for a PR at https://purduesigbots.github.io/pros-docs/204/ or something. i'm sure there's a way to do this in azure, but failing all else i have some sample github workflows we might be able to adapt
The text was updated successfully, but these errors were encountered:
Hotel - also maybe as a side project, set up auto-deploy forCI build artifacts from PRs to a staging URL so the results can be verified online (:
Jonathan - I would love to see that happen, not really sure what all we have in the way of a staging domain though. My first thought was to use github pages or something similar, could we do this with the existing azure-pipelines setup though?
Hotel - my initial thought was to set up a branch on this repo for gh-pages to use and then have the pipeline commit the artifacts there under a folder keyed to the PR so you'd be able to get to the build for a PR at https://purduesigbots.github.io/pros-docs/204/ or something. i'm sure there's a way to do this in azure, but failing all else i have some sample github workflows we might be able to adapt
The text was updated successfully, but these errors were encountered: