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

Use internal snapshot repository for OSS snapshot packages [DI-154][DI-212][5.2.z] #212

Merged
merged 3 commits into from
Aug 1, 2024

Conversation

JackPGreen
Copy link
Collaborator

@JackPGreen JackPGreen commented Jul 30, 2024

ldziedziul and others added 3 commits July 30, 2024 15:34
…2] (#204)

In order to control which editions (OSS/EE/ALL) should be released
`.github/release_type` file is introduced.

This file is required now for newly created git tags. It should contains
only one of the following values:
- OSS
- EE
- ALL

When a new tag is pushed we read the file to decide which editions
should be released.
For manual runs of the `publish-packages.yml` we ignore this file and
use `RELEASE_TYPE` input from the workflow

`.github/release_type` should be added during the release by the
automation. It's forbidden to add it master or maintenance branches
through PRs.

Fixes: https://hazelcast.atlassian.net/browse/DI-52

---------

Co-authored-by: Jack Green <[email protected]>
….5.z] (#209)

Backport of #207

- Use internal snapshot maven repository for getting OSS snapshot
distribution zip
- Do not produce brew packages for OSS snapshot as it would expose
password-protected urls

Fixes https://hazelcast.atlassian.net/browse/DI-154

Implemented similar like hazelcast-docker:
hazelcast/hazelcast-docker#774
@JackPGreen JackPGreen self-assigned this Jul 30, 2024
@JackPGreen JackPGreen merged commit d6e675a into 5.2.z Aug 1, 2024
19 of 20 checks passed
@JackPGreen JackPGreen deleted the use-internal-repo-5.use-internal-repo-5.2.z branch August 1, 2024 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants