Exceptionally, we need to use the Slicer build infrastructure for supporting an other project. (Usually, we rely on the spare cycle of the infrastructure to support other projects)
This means:
you should only expect the nightly Slicer packages for Linux, macOS and Windows
it is also normal if no test results are available on the dashboard, we disabled them on purpose
these packages are built against the latest VTK and most (if not all) of Volume Rendering issues are addressed
extensions will either be skipped or build later today
@jcfr Next time in similar situation it is better to disable Slicer package builds as well. For users, it is better if they download a version that is built from a few-day-old code than getting a version built from latest master but without extensions.
It would be great to have pinning but just the ability to temporarily add an alternative download link with some explanation would be enough.
We should also rename “nightly” to “preview” on the download page as we planned before (since extensions for both stable and master versions are rebuilt nightly).
An other option would be transfer the project to Slicer · GitHub or we could fork it into the Slicer organization (and rename it to download.slicer.org)