# Remove legacy in CI builds?

**URL:** https://discourse.itk.org/t/remove-legacy-in-ci-builds/4609
**Category:** Engineering
**Created:** [November 24, 2021, 2:27pm UTC](https://discourse.itk.org/t/remove-legacy-in-ci-builds/4609 "2021-11-24T14:27:33Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![dzenanz](https://discourse.itk.org/user_avatar/discourse.itk.org/dzenanz/32/1093_2.png) [@dzenanz](https://discourse.itk.org/u/dzenanz)
#### Post date: [November 24, 2021, 2:27pm UTC](https://discourse.itk.org/t/remove-legacy-in-ci-builds/4609/1 "2021-11-24T14:27:33Z")

</div>

It has happened several times that ITK fails to build on one of the dashboard machines which has [ITK\_LEGACY\_REMOVE=ON](https://github.com/InsightSoftwareConsortium/ITK/blob/356710288b4c98b40cfbdf1e17af37ec28e8d0c2/Testing/ContinuousIntegration/AzurePipelinesLinux.yml#L51-L53). This could be avoided if we had a CI build without legacy. Probably the best would be to add another build, e.g. `LinuxWithoutLegacy` (because Linux builds are usually the fastest). Do you foresee any problems with this?

---

<div class="post-metadata">

### Author: ![jhlegarreta](https://discourse.itk.org/user_avatar/discourse.itk.org/jhlegarreta/32/476_2.png) [@jhlegarreta](https://discourse.itk.org/u/jhlegarreta)
#### Post date: [November 24, 2021, 2:49pm UTC](https://discourse.itk.org/t/remove-legacy-in-ci-builds/4609/2 "2021-11-24T14:49:48Z")

</div>

I’d say that setting up a build with the flag set to `ON` would be very much welcome.