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

Feature/add android complete codefreeze #13215

Merged
merged 5 commits into from Oct 27, 2020

Conversation

loremattei
Copy link
Contributor

This PR adds the complete_code_freeze lane to this project.
At this point, the Android lane only runs the usual prechecks (make sure git repo is clean, make sure a release branch is checked out, confirm the version with the user) and pushes the tags.

Related release-toolkit PR: wordpress-mobile/release-toolkit#169

To test:

  • Checkout a new release/test branch from this one and push it.
  • Update the version in build.gradle for both the beta and the alpha, and commit.
  • Run bundle exec fastlane complete_code_freeze.
  • Verify that the lane finishes without errors and that the tags related to your new version have been pushed.

Clean up:

  • Remove the test tags from GitHub.
  • Remove the test tags from your local repository.
  • Delete the test branch from GitHub.
  • Delete the test branch from your local repository.

Note: After review and approval, before merging this PR, I'll release a new version of release-toolkit and update the reference to the released version,

PR submission checklist:

  • I have considered adding unit tests where possible.
  • I have considered adding accessibility improvements for my changes.
  • I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

@loremattei loremattei added this to the 16.1 milestone Oct 23, 2020
@peril-wordpress-mobile
Copy link

peril-wordpress-mobile bot commented Oct 23, 2020

You can trigger optional UI/connected tests for these changes by visiting CircleCI here.

@peril-wordpress-mobile
Copy link

peril-wordpress-mobile bot commented Oct 23, 2020

You can test the changes on this Pull Request by downloading the APK here.

@loremattei loremattei requested review from a team, AliSoftware, jkmassel and mokagio and removed request for a team October 23, 2020 10:00
@loremattei loremattei marked this pull request as ready for review October 23, 2020 10:00
Copy link
Contributor

@AliSoftware AliSoftware left a comment

Choose a reason for hiding this comment

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

Tested as described in PR body but also tested by running be complete_code_freeze on a non-release branch and validated it printed the right error and stopped. All good 👍

@@ -6,5 +6,5 @@ group :screenshots, optional: true do
gem 'rmagick', '~> 4.1'
end

gem 'fastlane-plugin-wpmreleasetoolkit', git: 'https://github.com/wordpress-mobile/release-toolkit', tag: '0.9.14'
gem 'fastlane-plugin-wpmreleasetoolkit', git: 'https://github.com/wordpress-mobile/release-toolkit', ref: 'a53b7c2'
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Just a reminder that this PR should NOT be merged until a new release toolkit has been released and this switched back to new tag (as described in the PR description) though

Copy link
Contributor

Choose a reason for hiding this comment

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

I guess we could put in place a Peril check for this, like we do for our pods.

Every time we do this kind of PRs, either the author writes this or a reviewers points it out. 😄 If we automate it, we'll get the benefit of actually blocking the merge.

@loremattei loremattei merged commit 17d1f27 into develop Oct 27, 2020
@loremattei loremattei deleted the feature/add-android-complete-codefreeze branch October 27, 2020 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants