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
Currently, after the nightly build is complete, each DUNE DAQ repo gets individually built against the nightly as a check (see, e.g., https://github.com/DUNE-DAQ/appfwk/actions/runs/7882862207). However, there's no way to see all the results in one location, making it difficult to determine whether all single-repo CIs have passed. Three years ago as I recall a successful (but temporary) attempt was made, and the link still exists in https://github.com/DUNE-DAQ/daq-release/blob/develop/docs/ci_github_action.md . Either using the same service https://meercode.io/ or another one, we should investigate bringing back this dashboard.
The text was updated successfully, but these errors were encountered:
Currently, after the nightly build is complete, each DUNE DAQ repo gets individually built against the nightly as a check (see, e.g., https://github.com/DUNE-DAQ/appfwk/actions/runs/7882862207). However, there's no way to see all the results in one location, making it difficult to determine whether all single-repo CIs have passed. Three years ago as I recall a successful (but temporary) attempt was made, and the link still exists in https://github.com/DUNE-DAQ/daq-release/blob/develop/docs/ci_github_action.md . Either using the same service https://meercode.io/ or another one, we should investigate bringing back this dashboard.
The text was updated successfully, but these errors were encountered: