Title:

Write your CI/CD in TypeScript - An Open-Source Project - Would You Be Interested?

Hello everyone and happy 2025 ! Topic : For internal reasons, we developed a framework that enables writing CI/CD pipelines (more precisely, writing a complete orchestrator in the context of an engineering platform) in TypeScript. The use cases that led us to this include, e.g. : • On AWS, CloudFormation and AWS CDK have limitations when handling cross-region or cross-account scenarios. • On Kubernetes and CDK8s, we needed model-driven orchestration on CDK8s (and for other reasons, Helm didn’t meet our requirements). • When infrastructure templates are distributed across multiple Git repositories, as is often the case with complex stacks, managing dependencies (e.g., serviceA depends on serviceB, which depends on serviceC) and deployment order can become challenging. Advantages: • Replaces YAML with standard code. • Runs on Node.js as a standard package, giving access to a rich ecosystem and making easy to build APIs on top of it. • The same best practices we enforce in code repositories can be applied to the infrastructure orchestrator. • With this framework, cloud resource orchestration can be treated as standalone software. This has significantly reduced the time required to build and maintain our infrastructure. Request for input: We believe this framework is valuable and could benefit the community. Likewise, it could also benefit from the community, as the scope of possible integrations is vast, and we are reaching the limits of what we can achieve with our current team size. Therefore, we are planning to open-source this framework soon (under an MIT or GPL license), and we are wondering if this might interest some of you here. Would any of you find it relevant for your projects ? Would you be interested in joining the community or even contributing to the project ?

Have you considered joining a foundation like CDF? https://cd.foundation/

Yes, we were able to discuss with the Linux Foundation and the Eclipse Foundation as well. From what I understood (I can mistake), this involves quite a few constraints initially and would be more appropriate to consider in a second step.

Fair enough.

I find the idea interesting. I’m a DevOps Team Leader, and I’m handling complex system and complex architecture, and I’m looking to simplify it. Would be interested in giving it a try.

Great, thanks for your response! If that works for you, I’ll share the project with you once it is released. ☺️ In the meantime, I can send you some examples via DM if you’re interested in. Also, if you have time, feel free to reach out or share your thoughts, and we can brainstorm how it might fit into your workflows!

That sounds good. Looking forward to checking the examples!