Promote Changes Through Environments

18 steps

Promote your changes from Development to Staging and Production via GitOps.

  1. 1

    Check in your changes to the remote origin. Please note you will need to log in to your GitHub if its the first time you are using git since the dev environment was instantiated. A code will be displayed on the screen of the code-server and you need to copy and paste this into GitHub to authorize VSCode.\ \ [[git add \*]] [[git commit -m “making a change”]] [[git push origin <branch name>]]

  2. 2

    Navigate back to your GitHub repo and click “compare & pull request

    Promote Changes Through Environments, step 2
  3. 3

    Select the base- in this case, Staging

    Promote Changes Through Environments, step 3
  4. 4

    Click “staging

    Promote Changes Through Environments, step 4
  5. 5

    Click “Create pull request

    Promote Changes Through Environments, step 5
  6. 6

    Click “Squash and merge

    Promote Changes Through Environments, step 6
  7. 7

    Click “Confirm squash and merge

    Promote Changes Through Environments, step 7
  8. 8

    Click “Actions” to see the build progress (the containerization of your app and push to the container repo)

    Promote Changes Through Environments, step 8
  9. 9

    Click the title of the action to see the build output.

    Promote Changes Through Environments, step 9
  10. 10

    Click “build

    Promote Changes Through Environments, step 10
  11. 11

    When you see this print out, your build has succeeded. This will trigger a function that redeploys your staging application.

    Promote Changes Through Environments, step 11
  12. 12

    Switch to tab DevOpser AI Webhosting"

  13. 13

    Click “Staging” to get the URL to your staging app.

    Promote Changes Through Environments, step 13
  14. 14

    You can see the Staging environment is in an “applying” state - that means your new container has not been deployed yet.

    Promote Changes Through Environments, step 14
  15. 15

    If you go to the Staging URL, you will see the new route hasn't been added yet.

    Promote Changes Through Environments, step 15
  16. 16

    Once the status of Staging is “Active”, the deployment to staging is complete.

    Promote Changes Through Environments, step 16
  17. 17

    You will now see your new route and changes published to Staging. Congrats!

    Promote Changes Through Environments, step 17
  18. 18

    To promote to Production, follow the same steps, but select “main” as the base branch for the pull request instead of “staging”. Happy coding!