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

Allow task separation through release.properties #21

Open
mp911de opened this issue Jan 4, 2023 · 1 comment
Open

Allow task separation through release.properties #21

mp911de opened this issue Jan 4, 2023 · 1 comment
Assignees
Labels
type: enhancement A general enhancement

Comments

@mp911de
Copy link
Member

mp911de commented Jan 4, 2023

We should introduce means of controlling what targets should be run by the automated release tooling, ideally through release.properties as this is a place that needs to be edited for a given release.

We have three scenarios:

  1. Run the full release (full)
  2. Prepare the release and push tags (tag)
  3. (Re-)run binary and documentation builds including staging. This step requires release tags to be present (build)

The full target is composed from tag and build targets. That separation allows for retries.

@mp911de mp911de added the type: enhancement A general enhancement label Jan 4, 2023
mp911de added a commit that referenced this issue Jan 9, 2023
mp911de added a commit that referenced this issue Jan 9, 2023
Use only test properties to avoid local config interference.

See #21
@gregturn
Copy link
Contributor

This mechanism should allow, through Jenkins' ability to read properties files, to conditionally run different phases of the build.

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

No branches or pull requests

2 participants