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
We're currently using Skopeo to do a remote copy from the CI Docker repository to the public-facing testing & stable repositories. I'd like to investigate using CI jobs triggered by the CircleCI API to run these steps.
The API request will require:
git sha of sensu-enterprise-go to use
version number (e.g. 6.3.0)
The text was updated successfully, but these errors were encountered:
Perhaps even implemented as a Docker container which executes the uploading of the release to the repos? Then it's portable if we ever decide to move off of Circle CI?
We now have internal scripts to simplify the promotion process of Docker images from one repository to another. Implementing what's described in this issue would involve:
Implementing a promotion job in CI that can only be triggered via an API call
Trigger has mandatory parameters (e.g. action: ci-to-testing)
Uses the scripts described above with the parameters that are set
Writing a script / tool which:
Accepts the required parameters to trigger the job in CI
We're currently using Skopeo to do a remote copy from the CI Docker repository to the public-facing testing & stable repositories. I'd like to investigate using CI jobs triggered by the CircleCI API to run these steps.
The API request will require:
e.g. 6.3.0
)The text was updated successfully, but these errors were encountered: