Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Re-enables pushing nightly to org.mozilla.fenix #3823

Merged

Conversation

mitchhentges
Copy link
Contributor

In addition to pushing Nightly to org.mozilla.fenix.nightly, re-enable the legacy action of pushing it to org.mozilla.fenix under the nightly track.

Pull Request checklist

  • Quality: This PR builds and passes detekt/ktlint checks (A pre-push hook is recommended)
  • Tests: This PR includes thorough tests or an explanation of why it does not
  • Changelog: This PR includes a changelog entry or does not need one
  • Accessibility: The code in this PR follows accessibility best practices or does not include any user facing features

return (build_tasks, signing_tasks, push_tasks)


def nightly_to_production_app(is_staging, version_name):
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This function is very very similar to the one that used to be here

@@ -131,6 +131,45 @@ def release(channel, is_staging, version_name):
signing_task_id,
apks=apk_paths,
channel=channel,
# TODO until org.mozilla.fenix.nightly is made public, put it on the internally-testable track
override_google_play_track=None if channel != "nightly" else "internal",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Note: we want to test org.mozilla.fenix.nightly before it's released.
By default, nightlies are published to the beta track, which is public.
So, we're going to override and publish on internal for a while, so we can internally test. Once org.mozilla.fenix.nightly is made public, we'll put this back to normal, so each nightly is automatically published publicly

Copy link
Contributor

@JohanLorenzo JohanLorenzo left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Contributor

@pocmo pocmo left a comment

Choose a reason for hiding this comment

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

Looks good.

I am a bit afraid that in the worst case we may end up pushing to production for the wrong app. But since we only push the actual nightly to "internal" for now this shouldn't really happen.

@mitchhentges mitchhentges merged commit aebcc92 into mozilla-mobile:master Jul 2, 2019
@mitchhentges mitchhentges deleted the reenable-nightly-legacy branch July 2, 2019 18:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants