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

ci: deploys bom separately to allow re-do on partial failure #241

Merged
merged 1 commit into from
Jan 10, 2024

Conversation

codefromthecrypt
Copy link
Member

Before, the bom project deployed only after the parent succeeded. This meant a timeout would prevent it from being deployed, even if the timeout was not critical. This deploys the bom independently so that such a situation doesn't cause us to have to re-cut a version.

This also fixes where we didn't actually use the release args in tests.

Before, the bom project deployed only after the parent succeeded. This
meant a timeout would prevent it from being deployed, even if the
timeout was not critical. This deploys the bom independently so that
such a situation doesn't cause us to have to re-cut a version.

This also fixes where we didn't actually use the release args in tests.

Signed-off-by: Adrian Cole <adrian@tetrate.io>
@codefromthecrypt
Copy link
Member Author

this can be tested prior to release as it also runs on master

@@ -69,4 +69,4 @@ jobs:
# via forks, and login session ends up in ~/.docker. This is ok because
# we publish DOCKER_PARENT_IMAGE to ghcr.io, hence local to the runner.
- name: Test
run: build-bin/configure_test && build-bin/test
run: build-bin/configure_test && build-bin/test ${{ matrix.maven_args }}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@reta I feel like this copy/paste is missing elsewhere, too ;) that said I think the only ones that are critical on this are zipkin, reporter and brave, as they have java 6 artifacts..

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it, thanks @codefromthecrypt !

@codefromthecrypt codefromthecrypt merged commit 9c666c4 into master Jan 10, 2024
3 checks passed
@codefromthecrypt codefromthecrypt deleted the deploy-separate branch January 10, 2024 00:30
@codefromthecrypt
Copy link
Member Author

@codefromthecrypt
Copy link
Member Author

worked.. will cut 3.1.1 and hope the sonatype snafu is over

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.

2 participants