DEV Community

aldrin312
aldrin312

Posted on

Implementing CI Workflow

For this lab I needed to set a CI workflow on my project. This can be done directly in GitHub whenever a commit or pull request is done. I have mine set up where it would run the unit tests I made and check whether they pass or not. Basically on the YAML it set up to run the CI, the build and the tests.

Comparing what I did on my project and on my partners, we have to partner up for this lab and add a test for the CI workflow, its really different. For instance, their project uses Python while mine uses JavaScript. So it uses different frameworks for creating the tests. Another is that it uses a different environment. I'm assuming that they uses a Mac environment for this, so the testing framework that they used, MakeFile, is already installed. But on windows it is not. I had to install on windows and configure it to be able to run make commands.

What I Think of CI Workflow.

Generally, I think CI is useful, especially on an open source project. It ensures consistency on all the contributions on it and make sure that all the functions still functions the same on each iteration. I learned so much from this and I think I should always try to implement CI on my projects. Considering that setting the CI workflow is not that hard that I thought.

Image of Timescale

🚀 pgai Vectorizer: SQLAlchemy and LiteLLM Make Vector Search Simple

We built pgai Vectorizer to simplify embedding management for AI applications—without needing a separate database or complex infrastructure. Since launch, developers have created over 3,000 vectorizers on Timescale Cloud, with many more self-hosted.

Read full post →

Top comments (0)

Billboard image

The Next Generation Developer Platform

Coherence is the first Platform-as-a-Service you can control. Unlike "black-box" platforms that are opinionated about the infra you can deploy, Coherence is powered by CNC, the open-source IaC framework, which offers limitless customization.

Learn more