![]() ![]() We are also able to define what event should occur (e.g. That’s the POSIX cron syntax = “Minute Hour DayOfTheMonth MothOfTheYear DayOfTheWeek”. In our case, we defined the workflow that fires every day at 1:30 am. So, we are able to define a specific UTC time when it should trigger. on - it is responsible for triggering workflow.It is also visible on GitHub in the Actions tab. name - just a name for a workflow, describing it in a few words.So let’s begin with a straightforward example.Ĭonfiguration files are simple YAML files. Introduction and simple usage of GitHub Action One file equals one workflow and each of them is independent. github/workflows/ directory at the root of your project. To some extent, we are able to configure that using UI on GitHub under Actions tab in our repository page:īut in this article, I am going to focus on setting CI/CD manually, writing configuration files. To configure what should be done, we have to create a workflow. The first point is that most of the work is done using GitHub’s servers in the cloud and doesn't require local machine setup. ![]() I am going to show an example of CI/CD pipeline with the use of GitHub’s actions - GitHub tool for configuring CI/CD. And the best thing is that you only have to merge the newest changes to the main branch (to be honest, you even don’t have to do that, a simple push to your own branch is sometimes sufficient). Whenever someone needs the newest version, it is ready to be tested with recently added features. That means you have to sacrifice a few hours (realistically even more) at the start of the project to set up the process, and then you don’t have to worry about the process of releasing a new version of the application. for Quality Assurance team) or even to the final clients on production. ![]() CD, on the other hand, is used to release a working version of the application to our team members (e.g. In short, CI is responsible for building, testing, and merging our application to one shared source between developers. For those of you interested in acronyms, CI/CD means Continuous Integration/Continuous Delivery (or Continuous Deployment). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |