Add automatic snapshot publishing #6
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| name: Publish Snapshot builds | ||
|
|
||
| on: | ||
| push: | ||
| branches: | ||
| - develop | ||
| workflow_dispatch: | ||
|
|
||
| concurrency: | ||
| group: snapshot-release | ||
| cancel-in-progress: false | ||
|
|
||
| jobs: | ||
| release: | ||
| permissions: | ||
| contents: write | ||
| uses: ./.github/workflows/release.yml | ||
| with: | ||
| bump: patch | ||
gpunto marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| snapshot: true | ||
| secrets: | ||
| github-token: ${{ secrets.STREAM_PUBLIC_BOT_TOKEN }} | ||
| maven-central-username: ${{ secrets.OSSRH_USERNAME }} | ||
| maven-central-password: ${{ secrets.OSSRH_PASSWORD }} | ||
| signing-key: ${{ secrets.SIGNING_KEY }} | ||
| signing-key-id: ${{ secrets.SIGNING_KEY_ID }} | ||
| signing-key-password: ${{ secrets.SIGNING_PASSWORD }} | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -38,7 +38,42 @@ on: | |
| required: true | ||
|
|
||
| jobs: | ||
| publish-snapshot: | ||
| if: ${{ inputs.snapshot }} | ||
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
| - name: Checkout | ||
| uses: actions/checkout@v4 | ||
| with: | ||
| token: ${{ secrets.github-token }} | ||
| ref: develop | ||
|
|
||
| - name: Bump version | ||
| id: bump | ||
| uses: GetStream/stream-build-conventions-android/.github/actions/bump-version@develop | ||
| with: | ||
| bump: ${{ inputs.bump }} | ||
| file: ${{ inputs.version-properties-file }} | ||
gpunto marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| - name: Setup Gradle | ||
| uses: GetStream/stream-build-conventions-android/.github/actions/setup-gradle@develop | ||
| with: | ||
| cache-read-only: false | ||
|
|
||
| - name: Build and publish snapshot | ||
| run: ./gradlew publish --no-configuration-cache | ||
| env: | ||
| ORG_GRADLE_PROJECT_mavenCentralUsername: ${{ secrets.maven-central-username }} | ||
| ORG_GRADLE_PROJECT_mavenCentralPassword: ${{ secrets.maven-central-password }} | ||
| ORG_GRADLE_PROJECT_signingInMemoryKey: ${{ secrets.signing-key }} | ||
| ORG_GRADLE_PROJECT_signingInMemoryKeyId: ${{ secrets.signing-key-id }} | ||
| ORG_GRADLE_PROJECT_signingInMemoryKeyPassword: ${{ secrets.signing-key-password }} | ||
| ORG_GRADLE_PROJECT_RELEASE_SIGNING_ENABLED: true | ||
| SNAPSHOT: true | ||
|
|
||
| publish-release: | ||
| if: ${{ !inputs.snapshot }} | ||
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
|
|
@@ -85,15 +120,14 @@ jobs: | |
| push: false | ||
|
|
||
| - name: Push changes to ci-release branch | ||
|
Collaborator
Author
There was a problem hiding this comment. Took the opportunity to completely split snapshot and final release publishing. I think it's less error prone this way, as we now have two separate jobs instead of one job with excluded steps. I also considered splitting the workflow into two files, but discarded that approach because I find it clearer to see the publishing in one place, so you don't have to know that two workflows exist. |
||
| run: git push origin HEAD:ci-release --force-with-lease | ||
|
|
||
| - name: Setup Gradle | ||
| uses: GetStream/stream-build-conventions-android/.github/actions/setup-gradle@develop | ||
| with: | ||
| cache-read-only: false | ||
|
|
||
| - name: Build and publish release | ||
| run: ./gradlew publish --no-configuration-cache | ||
| env: | ||
| ORG_GRADLE_PROJECT_mavenCentralUsername: ${{ secrets.maven-central-username }} | ||
|
|
@@ -102,11 +136,9 @@ jobs: | |
| ORG_GRADLE_PROJECT_signingInMemoryKeyId: ${{ secrets.signing-key-id }} | ||
| ORG_GRADLE_PROJECT_signingInMemoryKeyPassword: ${{ secrets.signing-key-password }} | ||
| ORG_GRADLE_PROJECT_RELEASE_SIGNING_ENABLED: true | ||
| SNAPSHOT: false | ||
|
|
||
| - name: Create Github Release | ||
| uses: ncipollo/[email protected] | ||
| with: | ||
| generateReleaseNotes: true | ||
|
|
@@ -117,7 +149,7 @@ jobs: | |
|
|
||
| sync_branches: | ||
| if: ${{ !inputs.snapshot }} | ||
| needs: publish-release | ||
| name: Sync main and develop with release | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We just rely on the defaults (also, the idea is to align all SDKs to use the same mechanisms, so nobody will have to specify the version properties file).