Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Need to release registries (devfile + plugin) automatically via dedicated centos ci job #13953

Closed
ibuziuk opened this issue Jul 22, 2019 · 10 comments
Closed

Need to release registries (devfile + plugin) automatically via dedicated centos ci job #13953

ibuziuk opened this issue Jul 22, 2019 · 10 comments
Assignees
@ibuziuk
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P2 Has a minor but important impact to the usage or development of the system. status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community.
Milestone
7.0.0

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Jul 22, 2019 •
edited
Loading

The idea is to have a dedicated release branch in registries (devfile + plugin) and setup CI so that after pushing to this branch image with the correct tag e.g. 7.0.0-rc-4.0 would be pushed to the dedicated repository of the https://quay.io/organization/eclipse

The release branch could contain a VERSION / RELEASE file which would contain a dedicated version of the registry which would be used for tagging during CI / CD
@ibuziuk ibuziuk added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Jul 22, 2019
@ibuziuk ibuziuk added this to the 7.0.0 milestone Jul 22, 2019
@ibuziuk ibuziuk self-assigned this Jul 22, 2019
@ibuziuk
Copy link
Member Author

ibuziuk commented Jul 22, 2019 •
edited
Loading

@l0rd I have not added processing of the latest tag as part of this issue since currently, it is not clear what exactly the latest is. Basically, if we have 7.1.0 and more recent bug fix 7.0.1 which one should be treated as latest? (I suppose we could technically tag only major releases as latest while bug-fix releases would be only version tagged).

@ibuziuk ibuziuk changed the title Need to release registries (devfile + plugin) automatically via centos ci job template Need to release registries (devfile + plugin) automatically via dedicated centos ci job Jul 22, 2019
@l0rd l0rd added severity/P1 Has a major impact to usage or development of the system. severity/P2 Has a minor but important impact to the usage or development of the system. team/osio and removed severity/P1 Has a major impact to usage or development of the system. labels Jul 22, 2019
@l0rd
Copy link
Contributor

l0rd commented Jul 22, 2019

I would say that in your example latest is 7.1.0. But a patch release may be latest as well. For instance if we release a 7.1.1 (before releasing 7.2.0) we should tag it as latest.

Anyway since this looks like a complicated problem I would take care of it in a second step after Che 7 GA: we can add the tag manually for the time being.

@ibuziuk
Copy link
Member Author

ibuziuk commented Jul 23, 2019

@l0rd ok, sounds good. Just to clarify - we are putting on hold only the latest tag processing but the release / tag process e.g. 7.0.0-rc-4.0 via CI should be automated for Che 7 GA. Or the whole issue could be postponed and we are ok with the manual tagging for the time being?

@ibuziuk ibuziuk mentioned this issue Jul 23, 2019
Closed
@l0rd
Copy link
Contributor

l0rd commented Jul 23, 2019

We should create a job to release / tag and putting on hold tagging as latest (something that can be done manually)

@ibuziuk ibuziuk mentioned this issue Jul 24, 2019
Closed
@ibuziuk
Copy link
Member Author

ibuziuk commented Jul 24, 2019 •
edited
Loading

@l0rd sent a PR with a simple mechanism to automatically release devfile registry using the existing 'build-master' CI - eclipse-che/che-devfile-registry#47

@ibuziuk ibuziuk added the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Jul 24, 2019
This was referenced Jul 24, 2019
Merged
Merged
Merged
@l0rd
Copy link
Contributor

l0rd commented Jul 25, 2019

@ibuziuk @vparfonov we should do that for plugin registry as well

@ibuziuk
Copy link
Member Author

ibuziuk commented Jul 25, 2019

sure, in my TODO list, but plugin registry automatic release process is planned to be done after the RC 4 since we still need some time to automate it

@l0rd l0rd mentioned this issue Jul 25, 2019
Closed
3 tasks
@l0rd
Copy link
Contributor

l0rd commented Jul 25, 2019

Well yes I was hoping that we could semi-automate the release for plugin registry because that's identical to the devfile registry. But we can wait for it

@ibuziuk
Copy link
Member Author

ibuziuk commented Jul 25, 2019 •
edited
Loading

devfile regitry 7.0.0-rc-4.0 has been released via the new automatic CI CD process:

@l0rd
Copy link
Contributor

l0rd commented Jul 29, 2019

plugin registry has it's own CI CD release process as well:

closing the issue

@l0rd l0rd closed this as completed Jul 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ibuziuk ibuziuk

Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P2 Has a minor but important impact to the usage or development of the system. status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community.
Projects
None yet
Milestone
7.0.0
Development

No branches or pull requests
2 participants
@l0rd @ibuziuk