This repository was archived by the owner on Jan 27, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 102
Promote packages between stages #123
Comments
@ph I assigned you for now so you can push this forward. |
I will take care of this. |
Thank you! |
thomasneirynck
pushed a commit
to thomasneirynck/package-storage
that referenced
this issue
Sep 28, 2021
The registry so far contained generated packages. These packages contained all the same assets and were mainly designed to test the overview page of the package manager. But this now caused problems as many dashboards for example had the same ids. Because of this, all the assets are removed from these example packages and only the package with the icons are now left which is enough to show a nice home screen.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Idea
Use Jenkins pipelines wherever it's possible model the (semi-)continuous delivery solution, that will help with releasing.
Release stages
With #86 the package-storage has 3 release branches: production, staging, snapshot. Packages can be promoted from one branch to an other. This looks as following:
snapshot -> staging
Important is that changes are only pushed, if both checks/CI passed.
staging -> production
Notes:
The main difference here is that there is manual PR involved. It would be great if this PR would contain a diff in the PR description between the current and previous package.
An initial draft of such a script for the snapshot->staging part was opened here: #110 It does not contain all steps yet.
The text was updated successfully, but these errors were encountered: