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.

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

Release process for OperatorHub #70

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mabartos
Copy link
Contributor

@mabartos mabartos commented Oct 27, 2022

Closes keycloak/keycloak#10438

Testing is still in progress.[1]

In the end, it'd be maybe better to explicitly set the previous version of Keycloak required for OLM settings, as @vmuzikar suggested.

Testing progress:
Still struggling with used credentials for the GHA bot as it's not possible to push changes to particular branches[2]. I've changed the fork repos to keycloak-rel-testing organization in order to try if it's really an issue with the credentials. As for the keycloak-rel-testing, it should be possible to push some commits to repositories included in a particular organization (due to the Workflow settings).

[1] https://github.com/keycloak-rel-testing/keycloak-rel/actions/runs/3337653430

[2] main...keycloak-rel-testing:keycloak-rel:operatorhub#diff-732921da58cc64279cba94408ed726519ab0ed149a441c33ce515586dded5f22R106

@mabartos mabartos marked this pull request as draft October 31, 2022 15:31
@mabartos mabartos force-pushed the operatorhub branch 3 times, most recently from b96dff5 to d8b1cb2 Compare November 8, 2022 14:57
@mabartos mabartos force-pushed the operatorhub branch 3 times, most recently from ec6867c to 62b262a Compare November 15, 2022 11:31
@abstractj
Copy link

@mabartos @vmuzikar reading the issue and the comments here, it appears that we need push rights for the Keycloak bot. Is that correct? What is required from the repo admin to unblock this task?

@vmuzikar
Copy link
Contributor

vmuzikar commented Aug 28, 2023

The bot needs to be able to push into a forks of:

and create PRs from it.

These forks already exists for the rel-testing org:

but we'll also need to create two more forks in a different GH org for the live (non-testing) release process.

@mabartos Is that correct?

@mabartos
Copy link
Contributor Author

@vmuzikar Yes, that's correct.

I've tried to experiment with GH bot and Keycloak bot, but it'd be good to have a unified approach for that.

I'll try to find the best approach for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Release process for OperatorHub
3 participants