Skip to content

Publish a public "source of truth" apk push config #218

Open
@mitchhentges

Description

@mitchhentges

This is based off the work laid out in #217, but improves it by removing the need to keep downloading the new "apk push configuration" from taskcluster each time you use the mozapkpublisher CLI. Instead, when build-puppet synchronizes a new APK config, it should publish it to a public location. Then, when mozapkpublisher runs, it should download the config from this public location and use it. This could make mozapkpublisher commands as easy as mozapkpublisher push target.apk nightly --account boxwood-axon@google.com --credentials credentials.p12

Notes:

  • Where should this source of truth be? S3 bucket? An endpoint of shipit? 🤔
  • When doing a pushapkscript run, do we want to version the "source of truth" it uses? Should re-running the task grab the newest config (like the behaviour now, where you can update pushapkscript and run your task again?) or should it consistently use the same config?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions