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

Don't set taskcluster variables when we don't want to run the task #20542

Merged
merged 1 commit into from Dec 2, 2019

Conversation

jgraham
Copy link
Contributor

@jgraham jgraham commented Nov 29, 2019

Previously we had a single let block setting all the variables for the
.taskcluster.yml file. But this was evaluated even on events for which
we don't run tasks. That caused bogus failures because the logic
didn't account for all the possible event types.

Instead only evaluate the variables used in the task definition in
a block guarded by "if run_task".

Previously we had a single let block setting all the variables for the
.taskcluster.yml file. But this was evaluated even on events for which
we don't run tasks. That caused bogus failures because the logic
didn't account for all the possible event types.

Instead only evaluate the variables used in the task definition in
a block guarded by "if run_task".
Copy link
Contributor

@stephenmcgruer stephenmcgruer left a comment

Choose a reason for hiding this comment

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

This LGTM, although if we want to solve the epochs problem first we might want to hold off on changes to the yml outside of that context (your call, no strong opinion).

@jgraham jgraham merged commit cf170f5 into master Dec 2, 2019
@jgraham jgraham deleted the taskcluster_guard branch December 2, 2019 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants