GitHub Actions

Fiorano CI/CD

Creating a new repository

1. Create an account on Github.com.

2. Create a new repository for your work.

3. Give a suitable name for your repository.

Repository can be public

Development Machine

Downloading certificate

Before getting started, download the certificate from the GitHub website by following these steps:

1. Provide the GitHub URL in a web browser (Firefox is used in this instance) and press Enter.

2. Click the icon on the left side of the URL.

3. Click the Connection secure option.

4. Click the More information option

5. In the dialogbox, click View Certificate button.

6. In the window that opens, scroll down and click the PEM cert link against Download under the Miscellaneous section to download the certificate in the PEM format.

7. Add the downloaded github-com.pem certificate file to jssecacerts properties (present at FIORANO_HOME/esb/server/profiles/certs) file using the keystore explorer Software

Configuring eStudio with GIT details

1. Open eStudio and login to the enterprise server.

2. Right-click on the Event Process Repository and go to Version Control > Configuration.

3. Enable the Version Control checkbox and provide the username and password (Personal Access Tokens for GitHub) and the URL where you want to push the flows or the changes.

4. Click Finish.

5. Place the provided actions.yml file in FIORANO_HOME/runtimedata/repository/applications

6. Remember to mention the same tags under the heading of runs-on in the .yml that you gave while installing the runner for the production environment.

The next section explains how to create a self-hosted runner on the production machine.

Production Machine

Creating a self-hosted runner

In your repository, go to Settings > Actions > Runners.

1. Click the new self-hosted runner.

2. Select your OS and follow the commands given (scripts for Linux are used here).

3. Provide the tags related to your runner and specify those in the .yml file

4. Start the runner by executing the script run.sh

The runner will be present in the actions-runner folder.

5. If the runner is connected to GitHub, the screen appears as below.

Creating pipelines

1. Start the servers and login to eStudio

2. A push command from the development machine initiates a CI/CD job, prompting the GitHub server to add the job to its queue. The runner, during its next poll, picks up the job and executes it on the Production machine.

As the runner is constantly polling the server, whenever there is a commit from development machine to GitHub, pipeline will be triggered automatically by the runner.

The results, logs, and status are then sent back to the Github server by the runner.

Deploying in the Production machine

1. Create a folder named “githubaction”.

2. Place CI-CD.sh in this folder.

3. Start the runner, FES and FPS.

   1. The process of installing a runner is the same as seen previosuly. The same runner can be used with same tags if already installed

   2. The runner will carry out continuous polling and whenever there is a commit it will run the pipeline and execute it by following the steps in actions.yml

Viewing Logs in the pipeline

1. In GitHub, go to your repository.

2. Go to the Actions tab.

3. Click the commit name.

4. Click the job-name to view the logs.