Skip to content
This repository has been archived by the owner on Jan 27, 2023. It is now read-only.

Promote packages between stages #123

Closed
ruflin opened this issue Jul 3, 2020 · 3 comments · Fixed by elastic/elastic-package#43
Closed

Promote packages between stages #123

ruflin opened this issue Jul 3, 2020 · 3 comments · Fixed by elastic/elastic-package#43
Assignees

Comments

@ruflin
Copy link
Contributor

ruflin commented Jul 3, 2020

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

  • select package
  • add to staging
  • remove from snapshot
  • run checks for staging
  • run checks for snapshot
  • push changes to staging
  • push changes to snapshot

Important is that changes are only pushed, if both checks/CI passed.

staging -> production

  • select package
  • add to production
  • remove from staging
  • run checks for production
  • run checks for staging
  • open PR to master + CI
  • If PR is merged, remove from staging

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.

@ruflin ruflin assigned ph Jul 3, 2020
@ruflin
Copy link
Contributor Author

ruflin commented Jul 3, 2020

@ph I assigned you for now so you can push this forward.

@mtojek
Copy link
Contributor

mtojek commented Jul 30, 2020

I will take care of this.

@mtojek mtojek changed the title Script to promote packages between releases Promote packages between stages Jul 30, 2020
@ruflin
Copy link
Contributor Author

ruflin commented Jul 31, 2020

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.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants