I am facing this same problem (“No extensions found for win:64-bit, revision: ‘27339’. Please try a different combination”) with the latest Nightly build which I downloaded from the Slicer homepage.
Indeed, for some reason there are only extensions for Linux and Mac at this moment. It is possible that the factory computers have not finished the builds yet. You can wait to see if this is true, or download yesterday’s nightly that looks OK on the dashboard: http://download.slicer.org/?offset=-1
Windows extension builds are now coming up from the factory machine. It seems to be later than they have been in the past. I will take a look at the factory system log to see if something weird happened. If not, perhaps we should consider moving the factory build start earlier.
So I think we should consider moving the start time earlier for the nightly build, or changing up the build order. Currently, we build the stable extensions before the preview (except if its Sunday …?). Each build (slicer, stable extensions, preview extensions) appears to be taking ~4 hrs according to the logs, so most days the preview extensions don’t finish until late morning.
Also, for either the Preview or Stable extension, considering that some extension used branches like origin/master-XY or origin/master, we have no way of knowing if we can skip the build of the index or not.
We could also update the nighty build time. It is currently set in Slicer/CTestConfig.cmake as 3:00:00 UTC (23:00 EDT). May be we could start all nightly build at (8pm) 20:00 EDT (0:00:00 UTC) ?
For reference, the order of build is specified here:
However, the comment from the commit you mentioned states that it should implement the behavior suggested by Sam:
Lacking automatic detection of the 4.5 extensions index changes and
building of the modified extensions only, it is proposed that the order
between 4.5 and nightly is changed manually on as needed basis. It is
expected that nightly builds will be changing at a faster pace than 4.5,
thus it is natural to have nightly built in the first place.
So I think something changed since that commit, if indeed stable extensions are built before the preview.
Another option would be to show yesterday’s nightly build (…?offset=-1) on the download page. Developers and advanced users would know that a more recent, potentially incomplete build is available for early testing.