Skip to content

Merge GitHub release steps to maven release workflow - #2017

Merged
Philip Gichuhi (Ndiritu) merged 1 commit into
mainfrom
fix/compare-packages
May 23, 2024
Merged

Merge GitHub release steps to maven release workflow#2017
Philip Gichuhi (Ndiritu) merged 1 commit into
mainfrom
fix/compare-packages

Conversation

@Ndiritu

@Ndiritu Philip Gichuhi (Ndiritu) commented May 23, 2024

Copy link
Copy Markdown
Contributor

Uploading the build artifacts (JARs) for 6.11.0's GitHub release fails since it can't find the build artifacts to upload to the GitHub release.

The workflow was expecting build artifacts to be produced by the maven release step, however this step was recently updated to upload build artifacts on tag creation

This PR adds the GitHub release step after a maven release so that build artifacts generated in the maven release are immediately available for the GitHub release.

@Ndiritu
Philip Gichuhi (Ndiritu) requested a review from a team as a code owner May 23, 2024 08:50
@Ndiritu Philip Gichuhi (Ndiritu) changed the title Set previous build branch to dev Set previous successful build branch to dev for package comparison May 23, 2024
Comment thread .github/workflows/gradle-build.yml Outdated
@Ndiritu Philip Gichuhi (Ndiritu) changed the title Set previous successful build branch to dev for package comparison Merge GitHub release steps to maven release workflow May 23, 2024
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.

3 participants