You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doubling back to this (and cyclus/cycamore#631) there are a few ways to go about it:
Add a macos_build_test.yml to cyclus/cycamore and cyclus/cymetric that use the cyclus_dev (and cycamore_dev in the case of cymetric) conda packages and build/test off of those so the workflow doesn't completely rebuild cyclus. This requires that we resolve Add CI to trigger feedstock rebuild on push to main cyclus#1834 to ensure the feedstock is always up to date with our main branch. This is the most complete/thorough of the 3 options, but adds some complexity to the CI.
Only build/test cyclus/cyclus in the cyclus/cyclus CI, similar to our support for Rocky linux. This would require no further changes, but we could run into issues downstream.
Build/test all three repositories in cyclus/cyclus, similar to our CI for Ubuntu. I'm not sure how much value this adds, since that strategy is intended to expose changes that break downstream projects, and is less focused on architecture support.
Wanted to open this up for discussion before implementing any unwanted/unnecessary infrastructure, @gonuke what are your thoughts?
Cyclus supports macOS, we should add CI workflows in this repo as well.
The text was updated successfully, but these errors were encountered: