# Buildkite Source Control Integration

**URL:** <https://discourse.pijul.org/t/buildkite-source-control-integration/780>\
**Category:** Development\
**Created:** [June 11, 2021, 10:59am UTC](https://discourse.pijul.org/t/buildkite-source-control-integration/780 "2021-06-11T10:59:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![avalonx](https://avatars.discourse-cdn.com/v4/letter/a/fbc32d/32.png) [@avalonx](https://discourse.pijul.org/u/avalonx)\
**Post date:** [June 11, 2021, 10:59am UTC](https://discourse.pijul.org/t/buildkite-source-control-integration/780/1 "2021-06-11T10:59:58Z")

</div>

It would be great if Pijul can be integrated with Buildkite CI. Their

> [Buildkite features webpage](https://buildkite.com/features)

shows that they provide an API for custom SCM integration. (Scroll down a bit past midway down the page the page to the section - Source Control Integration)

---

<div class="post-metadata">

**Author:** ![pmeunier](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/pmeunier/32/4_2.png) [@pmeunier](https://discourse.pijul.org/u/pmeunier)\
**Post date:** [June 11, 2021, 11:28am UTC](https://discourse.pijul.org/t/buildkite-source-control-integration/780/2 "2021-06-11T11:28:25Z")

</div>

Sounds interesting. We had a CI at some point, but the OVH fire took that away. I’m hopeful to get it back on track again.

Our CI was using cool tricks made possible by patches. One issue is that I first want to make 100% that the replication strategy is really solid. It seems more solid every day, and I’m monitoring it closely. Once this is done, we can totally start talking about restoring all the services that were destroyed by the fire.

---

<div class="post-metadata">

**Author:** ![avalonx](https://avatars.discourse-cdn.com/v4/letter/a/fbc32d/32.png) [@avalonx](https://discourse.pijul.org/u/avalonx)\
**Post date:** [June 11, 2021, 5:06pm UTC](https://discourse.pijul.org/t/buildkite-source-control-integration/780/3 "2021-06-11T17:06:55Z")

</div>

That sounds great. I want to mention that although I put the title of the thread to specifically refer you to Buildkite, I rather intended to indicate integration for all the mainstream CI/CDs as a good goal (eventually), to further ease pijul (and Nest) adoption. Not having this integration would be a big barrier to adoption for orgs and users who rely on a particular automated build flows.

Drone CI and Jenkins are equally good first targets as an example being they are open source (or mostly).