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

Automation of the technical part of the release process #63

Open
hendrikebbers opened this issue Jun 8, 2024 · 0 comments
Open

Automation of the technical part of the release process #63

hendrikebbers opened this issue Jun 8, 2024 · 0 comments
Labels
epic Group: Supply Chain (Security) Size: M Esitmated size of the issue (S,M,L,XL) STF

Comments

@hendrikebbers
Copy link
Member

hendrikebbers commented Jun 8, 2024 •
edited
Loading

Today, a Maven release (+ plus a plugin release) must be done by hand on a local machine. That is mostly based on signing the release artifacts, which are always signed with keys that belong to the persons who do the release. We need global keys for the Maven project handled by the Apache Foundation. Those keys must be available as secret tokens in GitHub for use in a build.

Based on #27
@hendrikebbers hendrikebbers added Size: M Esitmated size of the issue (S,M,L,XL) epic Group: Supply Chain (Security) labels Jun 8, 2024
@support-and-care support-and-care locked and limited conversation to collaborators Jun 17, 2024
@sparsick sparsick added the STF label Jan 7, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
epic Group: Supply Chain (Security) Size: M Esitmated size of the issue (S,M,L,XL) STF
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sparsick @hendrikebbers