-
Notifications
You must be signed in to change notification settings - Fork 426
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
iOS release flow automation #3818
base: main
Are you sure you want to change the base?
Conversation
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.
LGTM with the exception of "update asana" part that should be happening for every internal bump.
- name: Set up fastlane | ||
run: bundle install | ||
|
||
- name: Prepare release bump #KS update is_scheduled_release |
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.
Is this comment still relevant?
with: | ||
fetch-depth: 0 # Fetch all history and tags in order to extract Asana task URLs from git log |
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.
It seems to me that we can skip this in this job (I realize it was copied over from macOS where it's also not needed). Asana task URLs are only fetched in increment_build_number
job below.
tag_and_merge: | ||
name: Tag and Merge Branch | ||
needs: [ create_release_branch, prepare_release ] | ||
uses: ./.github/workflows/ios-tag-release.yml | ||
with: | ||
asana-task-url: ${{ needs.create_release_branch.outputs.asana_task_url }} | ||
base-branch: ${{ github.ref_name }} | ||
branch: ${{ needs.create_release_branch.outputs.release_branch_name }} | ||
prerelease: true | ||
secrets: | ||
ASANA_ACCESS_TOKEN: ${{ secrets.ASANA_ACCESS_TOKEN }} | ||
GHA_ELEVATED_PERMISSIONS_TOKEN: ${{ secrets.GHA_ELEVATED_PERMISSIONS_TOKEN }} |
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.
The one thing that Publish DMG Release workflow on macOS does for all releases is posting a comment to Asana saying that a new build is available for internal testing (listing tasks added since last internal release). Now I'm thinking that we should ideally call ios-tag-release-update-asana
here (and restore "internal" release-type
), instead of ios-tag-release
.
Task/Issue URL: https://app.asana.com/0/1205419239275955/1208056445209269/f
Tech Design URL:
CC:
Description:
Initial automation sharing for iOS release flow based on macOS release flow.
Steps to test this PR:
Definition of Done (Internal Only):
Copy Testing:
’
rather than'
Orientation Testing:
Device Testing:
OS Testing:
Theme Testing:
Internal references:
Software Engineering Expectations
Technical Design Template