search

conda-forge / conda-smithy

The tool for managing conda-forge feedstocks.
https://conda-forge.org/
BSD 3-Clause "New" or "Revised" License
146 stars 169 forks source link

How to test updates to `.travis.yml` #1940

Closed mfansler closed 1 month ago

mfansler commented 1 month ago

Comment:

I've been in touch with Travis CI Support regarding https://github.com/conda-forge/status/issues/178. In a recent email, they've suggested try changing:

to see if that makes any difference. How should I actually test these? I realize this could be a simple PR here, but seems like jumping the gun to update conda-smithy itself without evidence that these changes aren't superficial.

Should I test manually overwriting these (i.e., temporarily edit the .travis.yml without a rerender) in a draft PR on an affected repository?

hoechenberger commented 1 month ago

Hello @mfansler, were you able to make any progress on this? 🙂

mfansler commented 1 month ago

@hoechenberger no. I was kinda hoping someone from @conda-forge/core would share some guidance 🤞. I also have low expectation the suggested changes will make any difference - as is works perfectly fine for aarch64, and seems mostly superficial API changes.

The other thing they suggested is disconnecting and reconnecting the repositories - but I have no control on that, and we're talking hundreds of potentially impacted feedstocks.

But I give it a go on https://github.com/conda-forge/r-backbone-feedstock/pull/15. (i.e., test changing .travis.yml).

beckermr commented 1 month ago

Just make an edit by hand in a feedstock and see what happens.