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
As I recall, these builds are present to notify us of any changes upstream in MOAB that might break DAGMC builds/tests.
We currently require these to pass in CI, which I think is a little overkill. IMO it's sufficient to require that our builds/tests pass and Docker images publish successfully only for official releases of MOAB. I'm curious if @shimwell may have a need for Docker images using MOAB's develop and master branches?
It's still very useful to have these builds of course, so I'm going to look into allowing failures for these builds but always running them for merges into our develop branch.
The text was updated successfully, but these errors were encountered:
As I recall, these builds are present to notify us of any changes upstream in MOAB that might break DAGMC builds/tests.
We currently require these to pass in CI, which I think is a little overkill. IMO it's sufficient to require that our builds/tests pass and Docker images publish successfully only for official releases of MOAB. I'm curious if @shimwell may have a need for Docker images using MOAB's
develop
andmaster
branches?It's still very useful to have these builds of course, so I'm going to look into allowing failures for these builds but always running them for merges into our
develop
branch.The text was updated successfully, but these errors were encountered: