-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Test or_later formula changes. #20
Conversation
When the diff contains an `or_later` bottle change then don’t try to build the bottle but just install it and test it that way.
It seems like it should be using json merges rather than manually editing bottle blocks, which we've emphasized as verboten. |
Can you elaborate more on "json merges"? In the short-term: do you object to this approach to verify if this is going to work for us? Happy to iterate on the workflow if it proves annoying but would be good to be able to use this for some more Sierra bottles temporarily. |
Yeh, I see. In this case I think although it's different it's a feature because it doesn't require us to rebuild/reupload the bottle. |
I don't think we'd need to rebuild/reupload to go through brew pull for this.
As long as (A) we know the build fails on 10.12 and (B) the bottle goes through CI in some form before getting an or_later stamp, I think whatever works is fine in the short-run. But I'd prefer to see these go through brew pull / git push, no upload/download of bottles involved, and the commit be attributed to test-bot not a maintainer. |
Yep, this will allow us to do this.
I'd rather avoid modifying e.g. |
I think it depends how many we're talking about. Given there are 65 left on Homebrew/homebrew-core#6408 and maybe at most 1/4th of them actually need this right now, it's probably moot for the time being. |
When the diff contains an
or_later
bottle change then don’t try tobuild the bottle but just install it and test it that way.
CC @ilovezfs for thoughts.