# Need to fix GitLab CI for Duniter-v2s

**URL:** https://forum.duniter.org/t/need-to-fix-gitlab-ci-for-duniter-v2s/10164
**Category:** Duniter-v2s
**Created:** [13 December 2022 19:25 UTC](https://forum.duniter.org/t/need-to-fix-gitlab-ci-for-duniter-v2s/10164 "2022-12-13T19:25:28Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![HugoTrentesaux](https://forum.duniter.org/user_avatar/forum.duniter.org/hugotrentesaux/32/6396_2.png) [@HugoTrentesaux](https://forum.duniter.org/u/HugoTrentesaux)
#### Post date: [14 December 2022 14:11 UTC](https://forum.duniter.org/t/need-to-fix-gitlab-ci-for-duniter-v2s/10164/10 "2022-12-14T14:11:37Z")

</div>

I’m not confortable with these kind of limitations. As @poka told me, the CI should be here to make the developer’s work easier, but as elois implemented it, they actually make it a nightmare (see [Bootstraper une ĞDev](https://forum.duniter.org/t/bootstraper-une-gdev/9757) and [Difficultés avec l'outillage](https://forum.duniter.org/t/difficultes-avec-loutillage/9945) for examples of what an undocumented CI can make me feel link). If nobody is here to manage this part, I’m in favor of removing all the limitations so that @poka and I can publish docker images for smith to use and for developers to test (like duniter-indexer, gecko…).

---

_[View the full topic](https://forum.duniter.org/t/need-to-fix-gitlab-ci-for-duniter-v2s/10164)._