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

Remove assumptions about release blobs from rule evaluation #3065

Merged
merged 1 commit into from
Nov 30, 2023

Conversation

jcristau
Copy link
Contributor

Closes #2985

Copy link
Contributor

@bhearsum bhearsum left a comment

Choose a reason for hiding this comment

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

(I'm going to try using Conventional Comments for this review, FYI.)

I have a few non-blocking suggestions, but this looks good to me overall. Thank you for doing this!

tests/blobs/test_guardian.py Outdated Show resolved Hide resolved
src/auslib/blobs/base.py Outdated Show resolved Hide resolved
src/auslib/AUS.py Show resolved Hide resolved
`evaluateRules` can't reliably call `blob.getApplicationVersion`, because that
method is specific to certain types of blobs.  Instead, we change the
`blob.shouldServeUpdate` method to return a tristate instead of a boolean: `No`
means no update should be served.  `Maybe` means the update can be served but
the pin version should be checked.  `Yes` means the update should be served.

In the `Maybe` case, `evaluateRules` can look for a release corresponding to
the pin version and return that instead if found.

Closes mozilla-releng#2985
@jcristau jcristau merged commit 1e3d856 into mozilla-releng:main Nov 30, 2023
1 of 2 checks passed
@jcristau jcristau deleted the issue2985 branch November 30, 2023 16:43
jbuck pushed a commit to jbuck/balrog that referenced this pull request Jun 15, 2024
…releng#3065)

`evaluateRules` can't reliably call `blob.getApplicationVersion`, because that
method is specific to certain types of blobs.  Instead, we change the
`blob.shouldServeUpdate` method to return a tristate instead of a boolean: `No`
means no update should be served.  `Maybe` means the update can be served but
the pin version should be checked.  `Yes` means the update should be served.

In the `Maybe` case, `evaluateRules` can look for a release corresponding to
the pin version and return that instead if found.

Closes mozilla-releng#2985
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

evaluateRules throws exceptions when pin=1 and the query maps to a DesupportBlob
2 participants