Introducing Workflow with GitHub Integration
F. Mustafa Kurt
Excited to share that Yelken Cloud now has Workflow resource with GitHub integration that enables CI/CD pipeline for your GitHub repositories.
It’s been exactly 5 months since we announced and launched Yelken Cloud, a cloud platform where you can run containerized workloads or easily create websites using supported applications. During this period, we continually improved our platform and added new features. In this blog, we will talk about a new feature we have been cooking for quite some time: Workflow with GitHub integration.
Imagine that, as a developer, you have a web application project located inside a private GitHub repository, and you are working on a fancy feature in a branch called new-feature.
As you develop on your local computer and push commits to the branch, you would like to build and deploy these changes to a staging environment to test them outside your local computer without affecting production.
Additionally, you may also want your colleagues to test the new feature on their own without building the project locally.
This is where a CI/CD pipeline comes to the rescue, building and deploying the project to a staging environment as you push your changes to your branch.
With Yelken Cloud’s new Workflow resource, you can define automated tasks that will be performed when a matching event happens, such as a commit push. In summary, Workflow enables you to define a CI/CD pipeline for your GitHub repositories that continuously builds your project into a container image and deploys it as you push commits. Only requirement for your repository is to include a Dockerfile that defines build steps for your container image. While Workflow is designed to support many kind of events, it currently supports only GitHub events.
By default, when you push a commit to your repository’s default branch, the Workflow will create a Pipeline resource that builds a container image from your repository and deploys it to your production service. You can also configure your Workflow to create a new environment and a new service when you open a Pull Request (PR) targeting your default branch. For the time being, the PR feature is disabled by default for your Workflow; however, you can easily enable it in the Workflow settings. There are also other possible ways to configure a Workflow resource. For more information, please check the Workflow documentation.
To start integrating your GitHub repository with Yelken Cloud, you can either create a new service from your GitHub repository or create a Workflow resource manually. When creating a service or workflow, you will be prompted to install our GitHub App if you have not already. This installation will help Yelken Cloud integrate with your GitHub repositories.
Workflow was the latest addition to Yelken Cloud. We have already started working on the next big feature that will enhance your experience. As a clue, we can tell that we want you to define your services in a structured way using Infrastructure as Code (IaC). Lastly, you should be able to construct this definition automatically from a Docker Compose file. Stay tuned for the upcoming changes.
Disclaimer: We have not used (yet) any kind of Artificial Intelligence (AI) tools in any of our works.