As part of the Release Management process in Jiffy, we need to set up the workspace first. To achieve this, as a demonstration exercise, we will create four environments, which are as listed below:
We need to setup a
Project,
Release and a
Environment to create a code/Task. In this example, we have created a
Project CSS, which has a
Dev_Release and
Dev_Environment, as shown below:
Note that the Dev Environment has few Tasks created and stored in the SCM Repository
Similarly a
QA Release and
QA Environment has been set upf or the QA stage, as shown below:
As a primary step, the Release Manager needs to create a SCM Repository in Jiffy. To achieve this, he has to go to
Settings,
Applications and click on
+Add in the SCM Repository page. This opens up a new
Add Repository window, where we need to provide a unique name, select a
Repository Type, provide a base version to start the version control management with a user credential, as shown below:
Upon clicking the
Save button, you will see your new SCM Repository in the list:
Now a Bot Designer would work on his automated Task. Naturally this Task would undergo many changes and thereby have a default version associated with his Task. For example, in our example, you can see below the Task TK000319 has a current version v0.5. Everytime he makes a change/develops in his code, JiffyRPA would upgrade the version of his Task in steps of 0.1:
Now a Bot Designer would want to check-in his code on the newly created SCM Repository for a Build activity. To do his, he has to check-in his code into the newly created SCM Repository. To achieve this, he needs to go to his
Overview tab and click on the
Checkin To Repository button, which is as highlighted below:
Upon clicking, a new
Comments window will pop up, where he needs to provide information on the edits that he has made on the specific Task that he is trying to check-in. This is an important and best practice where in the changes you push into the SCM Repository is captured/logged and does not impact the overall build. This is as shown below:
Once you click
Push, you will see a pop-up on the top, as shown below: