-
Notifications
You must be signed in to change notification settings - Fork 0
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
Releases/irios/build firefox #4
base: main
Are you sure you want to change the base?
Conversation
@ahal I may have missed something else.. but the workaround of creating a PR from a releases branch does not fix the |
Sorry, I meant to just use the The good news is that fix for this landed in scriptworker: But we haven't created a new release yet. I can prioritize doing this if you specifically need to use a PR for testing. |
oh sorry for the misunderstanding... I will try that while the patch is ready in a release, there is not any hurry for that on our side. Thanks for sharing the updates :) |
taskcluster/kinds/complete/kind.yml
Outdated
- taskgraph.transforms.task | ||
|
||
task-defaults: | ||
worker-type: bitrise |
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.
Bug: In order to fix
scriptworker_client.exceptions.TaskVerificationError: No workflow scopes starting with 'project:mobile:firefox-ios:releng:bitrise:' found
the worker-type should be something else than bitrise. We don't need to run the complete task on the Bitrise infra given that this task just checks some Taskcluster metadata
worker-type: bitrise | |
worker-type: misc |
bafde9a
to
3c37e9c
Compare
creating a PR from a branch named releases/irios/build-firefox to build firefox
We would like to work on managing the dependencies between the build and test workflows to be able to run the complete workflow. In order to do that, we need a green build that creates the artifacts.