Skip to content
This repository has been archived by the owner on Aug 16, 2024. It is now read-only.

Add a GitHub action based release job #309

Merged
merged 3 commits into from
Dec 11, 2020
Merged

Add a GitHub action based release job #309

merged 3 commits into from
Dec 11, 2020

Conversation

ericwill
Copy link
Contributor

Signed-off-by: Eric Williams ericwill@redhat.com

What does this PR do?

Adds a GitHub action based release job system to the devfile registry.

Screenshot/screencast of this PR

N/A

What issues does this PR fix or reference?

Part of eclipse-che/che#18072

How to test this PR?

Modify the VERSION file on the release branch and push the changes.

PR Checklist

As the author of this Pull Request I made sure that:

Reviewers

Reviewers, please comment how you tested the PR when approving it.

Part of eclipse-che/che#18072

Signed-off-by: Eric Williams <ericwill@redhat.com>
make-release.sh Outdated Show resolved Hide resolved
make-release.sh Outdated Show resolved Hide resolved
Signed-off-by: Eric Williams <ericwill@redhat.com>
Signed-off-by: Eric Williams <ericwill@redhat.com>
@nickboldt nickboldt self-requested a review December 7, 2020 21:38
@ericwill
Copy link
Contributor Author

ericwill commented Dec 7, 2020

About the secrets, you can add the secret via GitHub API like so: https://developer.github.com/v3/actions/secrets/#create-or-update-a-repository-secret

There is an automated way to do it (thanks to @benoitf), just make sure you change the generate.sh script to set DOCKERHUB_USERNAME and DOCKERHUB_PASSWORD instead of the QUAY_* ones.

@nickboldt
Copy link
Contributor

As I'm not privy to the values of these secrets, and can't copy them from another eclipse/che-* repo (I'm not an admin)... I'll ask that someone like @benoitf runs his script and pushes the secrets to this and teh che-plugin-registry repo too.

If feeling particularly bored, could repeat the same steps for all the other repos that need to be migrated to GH action from centos ci: eclipse-che/che#17857

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 this pull request may close these issues.

3 participants