Skip to content

Simon/ci/stage jvm android before publish wpb 22853#1875

Merged
typfel merged 12 commits intomainfrom
simon/ci/stage-jvm-android-before-publish-WPB-22853
Mar 6, 2026
Merged

Simon/ci/stage jvm android before publish wpb 22853#1875
typfel merged 12 commits intomainfrom
simon/ci/stage-jvm-android-before-publish-WPB-22853

Conversation

@SimonThormeyer
Copy link
Member

What's new in this PR


PR Submission Checklist for internal contributors
  • The PR Title
    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

@SimonThormeyer SimonThormeyer force-pushed the simon/ci/stage-jvm-android-before-publish-WPB-22853 branch 30 times, most recently from 2eb56e1 to be9a42d Compare February 20, 2026 13:08
@SimonThormeyer SimonThormeyer force-pushed the simon/ci/stage-jvm-android-before-publish-WPB-22853 branch 3 times, most recently from db676c7 to 9e429e0 Compare February 20, 2026 14:14
@typfel typfel force-pushed the simon/ci/stage-jvm-android-before-publish-WPB-22853 branch 6 times, most recently from 121ba32 to 0f454fa Compare March 3, 2026 14:41
@typfel typfel marked this pull request as ready for review March 4, 2026 09:07
@typfel typfel requested a review from a team March 4, 2026 09:07
Copy link
Contributor

@coriolinus coriolinus left a comment

Choose a reason for hiding this comment

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

There's a large-ish caveat here, in that I am flying blind when it comes to Gradle and the JVM ecosystem. I don't know what I'm talking about, there.

That said, aside from the one nit, I see nothing to complain about here. Looks plausible!

@@ -0,0 +1,65 @@
name: prepare publish
Copy link
Contributor

Choose a reason for hiding this comment

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

Name could be significantly more descriptive here. Maybe "prepare publish jvm" or "... sonatype" or something?

Copy link
Member Author

@SimonThormeyer SimonThormeyer Mar 5, 2026

Choose a reason for hiding this comment

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

This workflow is supposed to contain prepare publish jobs for any platform, not just jvm. E.g., the verify-tag job is platform-independent. Potentially in the future, we might require additional prepare jobs for platforms other than jvm, which is why keeping the workflow name generic here makes sense imo.

The "prepare publish jvm" naming you suggest is pretty similar to what you get if you compose the workflow name "prepare publish" and the respective job name, "jvm".

Note, there's also an "android" job.

@typfel typfel force-pushed the simon/ci/stage-jvm-android-before-publish-WPB-22853 branch from 0f454fa to 7ae24a6 Compare March 6, 2026 09:28
@typfel typfel force-pushed the simon/ci/stage-jvm-android-before-publish-WPB-22853 branch from 7ae24a6 to 6f07736 Compare March 6, 2026 09:55
@typfel typfel merged commit 6f07736 into main Mar 6, 2026
50 checks passed
@typfel typfel deleted the simon/ci/stage-jvm-android-before-publish-WPB-22853 branch March 6, 2026 10:33
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