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.

Sign up for GitHub

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

Jump to bottom

Support multiple scope prefixes in bitrisescript #953

Merged
merged 3 commits into from
Mar 28, 2024
Merged

Support multiple scope prefixes in bitrisescript #953

merged 3 commits into from
Mar 28, 2024

Commits on Mar 26, 2024

  1. Bug 1876573 - Allow 'bitrisescript' to specify multiple scope prefixes 

    It turns out that we need to use consistent scope prefixes as the other
scriptworkers as Taskgraph configures a single prefix across all
scriptworkers. This means that the repo name can appear in the prefix,
which in turn means we'll need to support multiple valid prefixes per
trust domain.

This is how the other scriptworkers work, so it's a good change to make
anyway.
    @ahal
    ahal committed Mar 26, 2024
    Configuration menu
    Copy the full SHA
    53c26cd View commit details
    Browse the repository at this point in the history

  2. fix(bitrisescript): Use proper config key for artifact_dir and access… 

    … token
    @ahal
    ahal committed Mar 26, 2024
    Configuration menu
    Copy the full SHA
    e44a2d0 View commit details
    Browse the repository at this point in the history

  3. fix(bitrisescript): only log Bitrise response content on error 

    This is actually very verbose and makes the Taskcluster logs very
difficult to read, so only log it on error.
    @ahal
    ahal committed Mar 26, 2024
    Configuration menu
    Copy the full SHA
    b173820 View commit details
    Browse the repository at this point in the history