Currently, developers can deploy their code in two ways:
Pushing a commit to Git that triggers auto-build/deploy
Issuing nullstone deploy/launch through the CLI
These are helpful, but there are scenarios where a developer wants to deploy directly from the UI.
Roll back to a previous version.
Auto-build is disabled, but a user wants to pick a commit from Git to build and deploy.
How will it work?
To support both scenarios, this new functionality would allow deployment from activity screen and app page.
On the activity screen for code deployments, a user has the ability to deploy with a button labeled "Deploy this code".
On the app screen, a user has a new drop-down button with the following options:
Deploy from commit
Deploy previous version
Deploy from commit
This option would show a dialog listing the available commits for the connected repository.
To keep familiarity, this dialog should be similar to the page in GitHub for listing commits.
(Note the ability to switch branches. This allows for simpler display of commits without constraining to master)
Deploy previous version
This option would show a dialog listing all images or artifacts previously pushed to the app module.
Since these artifacts were previously built, this would kick off a deploy-only workflow.
Considerations
If auto-build is not enabled, we still would like to perform this deployment
How do we configure the build configuration?
Can we skip the build process if we detect a version already in the app's artifact registry?
Should "deploy this commit" also update IaC based on the commit?
Overview
Currently, developers can deploy their code in two ways:
nullstone deploy/launchthrough the CLIThese are helpful, but there are scenarios where a developer wants to deploy directly from the UI.
How will it work?
To support both scenarios, this new functionality would allow deployment from activity screen and app page.
Deploy from commit
This option would show a dialog listing the available commits for the connected repository. To keep familiarity, this dialog should be similar to the page in GitHub for listing commits. (Note the ability to switch branches. This allows for simpler display of commits without constraining to
master)Deploy previous version
This option would show a dialog listing all images or artifacts previously pushed to the app module. Since these artifacts were previously built, this would kick off a deploy-only workflow.
Considerations
If auto-build is not enabled, we still would like to perform this deployment
Should "deploy this commit" also update IaC based on the commit?