# Adding a CI build to a Slicer extension

**URL:** <https://discourse.slicer.org/t/adding-a-ci-build-to-a-slicer-extension/30857>\
**Category:** SlicerDMRI\
**Tags:** build\
**Created:** [July 28, 2023, 2:52pm UTC](https://discourse.slicer.org/t/adding-a-ci-build-to-a-slicer-extension/30857 "2023-07-28T14:52:17Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [July 31, 2023, 4:50pm UTC](https://discourse.slicer.org/t/adding-a-ci-build-to-a-slicer-extension/30857/24 "2023-07-31T16:50:03Z")

</div>

The standard for CI today is immediate build for pull requests. It would be nice to achieve this for Slicer, too. Currently, most extension developers rely on local builds and the nightly automatic build. The only exception is OpenDose3D, which has [CI pipeline](https://gitlab.com/opendose/opendose3d/-/pipelines) set up on gitlab.

---

_[View the full topic](https://discourse.slicer.org/t/adding-a-ci-build-to-a-slicer-extension/30857)._