# Windows extensions not being built

**URL:** <https://discourse.slicer.org/t/windows-extensions-not-being-built/6142>\
**Category:** Development\
**Created:** [March 14, 2019, 11:04am UTC](https://discourse.slicer.org/t/windows-extensions-not-being-built/6142 "2019-03-14T11:04:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [March 14, 2019, 11:04am UTC](https://discourse.slicer.org/t/windows-extensions-not-being-built/6142/1 "2019-03-14T11:04:33Z")

</div>

I’ve noticed that Windows extensions for stable and preview weren’t built during the build process last night or the night before.  
[http://slicer.cdash.org/index.php?project=Slicer4&date=2019-03-14](http://slicer.cdash.org/index.php?project=Slicer4&date=2019-03-14)

Also the preview Slicer package for Windows wasn’t uploaded either though the build passed.

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [March 14, 2019, 4:50pm UTC](https://discourse.slicer.org/t/windows-extensions-not-being-built/6142/2 "2019-03-14T16:50:22Z")

</div>

@jcfr Is there an issue with the Windows build machine? Or was the packaging turned off to prioritize Mac/Linux extension builds in the short term?

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [March 15, 2019, 2:02pm UTC](https://discourse.slicer.org/t/windows-extensions-not-being-built/6142/3 "2019-03-15T14:02:17Z")

</div>

**Update:** Windows related items were built, packaged, and uploaded with last night’s builds. [http://slicer.cdash.org/index.php?project=Slicer4&date=2019-03-15](http://slicer.cdash.org/index.php?project=Slicer4&date=2019-03-15)

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [March 15, 2019, 3:43pm UTC](https://discourse.slicer.org/t/windows-extensions-not-being-built/6142/4 "2019-03-15T15:43:55Z")

</div>

> Is there an issue with the Windows build machine? Or was the packaging turned off to prioritize Mac/Linux extension builds in the short term?

There are three difference build machine. More details at [Documentation/Nightly/Developers/Factory - Slicer Wiki](https://www.slicer.org/wiki/Documentation/Nightly/Developers/Factory)

> with last night’s builds

To follow up, you may also have notice that the revision number is not displayed on the dashboard. This is because, the regular nightly built on macOS and Linux was disabled, source code manually updated to a version newer than `r28019` and build manually triggered.

By disabling automatic update, this allowed to make sure the nightly build on macOS would account for changes associated with [r28020](http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=28020) done after the nightly cut-off time.

The linux failure is unrelated.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/f/1/f1b7932699212e302b204dc5b5066387a9732d2d.png)