-
Notifications
You must be signed in to change notification settings - Fork 4
NRL-633 Persistent Environments for Pull Requests #559
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
NRL-633 Persistent Environments for Pull Requests #559
Conversation
|
💥 Something went wrong while deploying the pull request environment. |
|
🚀 PR environment successfully deployed. |
|
|
🚀 PR environment successfully deployed. |
mattdean3-nhs
left a comment
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.
Worked a treat for me 👏 nice work!!!
Only thing I spotted was a warning in the action that a Terraform output.json file is not found but, given we're considering dropping the Terraform artifacts from the build, this should be fine left as is.
|
💥 Something went wrong while destroying the pull request environment. |




This adds new environments that get spun up when a pull request is opened.
The environment is updated every time the pull request is synchronised (updated).
When an environment is created or updated, a comment is added to the pull request with the latest deployed commit hash and the URL of the environment.
If an environment deploy fails, a comment should be added to the pull request with details of the run.
If the pull request is closed, the environment will be destroyed. This will take precedence over any create/update jobs in progress and will cancel those jobs if running.
If the pull request is reopened, the environment is recreated.