​ CI/CD Pipelines for UiPath Process

Deployment Series: GitHub Actions

​
​ like dicd pipelines for UA PA deployment using asure and today today we will be having our
day two the automation of u pa press using GitHub actions so today's event will be led by
Ashwin and uh we welcome you all and thanks for being here yeah so you can see in the
screen we have displayed the QR codes for the K chapter official community group and as well
as this event is co-hosted by the Chennai chapter you also have the Chennai chapter official
community group so if you haven't even like yet registered or joined the community
​ groups you can just scan the QR code from here and just join it so you can see the full updates
and like we will post an event in the chapter groups chapter pages and you can there register it
and get to know well about the chapter there and if you wish to start like hosting event or say
uh like BS speaker or everything you have like all the things up on here so feel free to join the
community group so you can quickly yeah scan the QR code can the QR coding join the
WhatsApp groups so we we don't spam uh anything
​ there all the content is strictly around any challenges that you might might be facing we want
the community to drive the conversations there and any new events that are happening in and
around the city um we post it uh uh post the details about that once the event gets published
um also lately what we have also been seeing is uh when anyone uh needs help from the
communities it can be we want to conduct a session and we are looking for a speaker or you
know XYZ college is looking for a for for a speaker to take a session on uh in XY
​ that city so we really leverage these WhatsApp groups to kind of ask for for for your help and if
and when you can kind of contribute uh any of those uh you can you can volunteer directly
over there as well so so join the join the group which is the most relevant for you don't join all
of them uh and uh and and please feel free to post about anything over there some of us Post
about any job opportunities um if if you are looking to expand your team within your
organization you can posted on those as well um so this is only for uh the
​ Kerala and and Chennai um so you do not need to if if you are not from this region you can
skip this okay yeah so uh meet our community team that is RO Rak Krishna Regional
Community manager APC we have him right now let look it few words yeah so quite uh excited
thank you all for uh uh joining this uh sessions um any of these topics that uh is given by the
community is not something that we are sitting in a um uh in a in a in a room thinking what we
should do uh it has to come from you so any requirements any um you know
​ suggestions that you have on how we can improve your experience in the community feel free
to write to me you can connect with me on LinkedIn as well I'm fairly active there um and um
and happy to connect with anyone if you just want to have a have a one-on-one call just feel
free to schedule it there you'll find an open link and I'm happy to connect over to weo who is
our Global Community advocacy manager you can connect him to the LinkedIn profile on the
QR code yeah so as you all know this 3D series is taken over by Jin Rahul and
​ ashin a huge panel of MVPs Jobing works at Wonder boards as a technical account manager
and Rahul Krishna as a automation specialist at Tech Mahindra and aswin basar as a senior
developer as at millenum and they will be taking over the session and today's day two will be
 led by Ashwin Baska as you all know that this event is co-hosted with the Chennai chapter we
have pal Anda on board for as the moderators at noo dis as solution architect intelligent
Automation and Al as salaries as sen RP developer and for the organizers as the
​ lead of ker chapter Community chapter myself alen I work at NOA Solutions private limited as
a Senor softare engineer and Shan c a solution architect in exponential digital Solutions
private limited you can also like uh if you have any ideas like or something which as do just
mentioned if you have something like to be a host or to volunteer and even or as a speaker just
feel free to reach to any of us our team we will like we will more will be more than happy to
help you there and I guess that that's it we can
​ uh begin with the day two cicd pipelines for U deployment series get have actions over to you
thank you yeah thank you Alan and Rohit hi everyone I hope you all are doing great and thank
you so much for joining in this webinar uh now we are on the second day of our cicd Series
right yesterday we learned insights on CCD using Azure devops from jobin and today our topic
is creating cicd pipeline using GitHub action for a UAP project okay and let's see what's our
agenda is um we will start with intro to the cicd GitHub
​ and GitHub actions then we'll discuss what are the core concept behind GitHub actions and
next I will show you how to set up the cicd pipeline and deploy a process built in Via Studio to
the orchestrator and finally followed by an interesting CU and a Q&A session okay that's all
about our agenda and let's see uh what is cicd okay actually uh cicd means its full form is
continuous integration and continuous deployment okay it is a modern practice followed in
software development for automating and streamlining the process of development
​ testing and to uh until the deployment stage of a particular project okay um there are different
csad platforms available such as genins assure devop G laab it actions Etc So based on the
organization requirement we'll be using one of these okay and today we'll be focusing on cicd
using GitHub actions okay what is GitHub so as we know uh like GitHub is a fundamental tool
used in software development domain where uh it helps in team collaboration version controls
project managements Etc uh in U PA uh as most of us know right we have a team tab
​ which allows us to seamlessly integrate our automation project to uh G repositories I hope
most of you have used this team stab to integrate your projects to the giab repository yeah so
uh next what is GitHub actions um GitHub actions is used to set up CD pipelines U it can be
set up for seamless integration and deployment of codes I mean uh it's a feature provided by
GitHub for automating different workflows based on the events uh so that it helps to
automatically build and deploy packages whenever a code change
​ is pushed to the Target Branch okay that's the basic concept about the GitHub actions uh next
we can discuss what are the main benefits of this GitHub actions um in uip part point of view
uh we can liberate this GitHub action for automating the uh deployment of UAP process to the
orchestrator so normally uh when we are using the UAP Studio UA we will be publishing uh
these uh process uh using the publish tab which is available on the studio right so other than
that using the cacd pipeline and leveraging the IT of actions feature
​ we can use the same for uh building the package as well as publishing the same to the
orchestrator okay that means validation s workflow analysis building the Nugget package and
finally the deployment of the process with like automatic versioning so whenever we are
pushing a latest code of a existing process now it has to be uh like deployed with a new
version right so using the GitHub actions itself there's a feature uh we can get the like uh next
higher version of the process and it will the same will be deployed to the uh
​ orchestrator okay so the versioning is also there and everything will be automated cool right
so in order to achieve this we can you uh we are using the different poal strips which are
available on the U public repositories okay um to do this uh like GitHub actions needs to
communicate with the uath orchestrator account right anyway uh it is uh going to publish a
process to our uipath orchestrator account so in order to do that it has to get our secure
orchestrator credential and all then only it will be able to interact
​ with the orchestrator right for that uh anyway these scps request different credential such as
our AP Keys client ID Etc uh but uh as we know as a best practice we know it's not
recommended to store any credentials directly into any code right uh if it's for a u project uh
what will be our approach uh as you know we make consider using the credential assets right
the same way GitHub comes with a feature called secrets and uh the same can be called
anywhere inside the GitHub action scripts okay so uh in case if you need
​ to use any secrets for a GitHub SCP or workflow uh for the GitHub actions we can store the
same uh inside a tab called Secrets which is available in the GitHub and we can call that
anywhere based on our needs okay that's the concept about the scripts um and also in GitHub
actions um there are scripts available not only for building and Publishing the Nugget package
uh but also for rening test cases creating like Auto pull request based on our requirement and
managing the Assets in our orchestrator Etc uh but in our demo
​ I'll be mainly focusing on two scripts that is building the package using uipath pack and
deploying the same to orchestrator and uh now I believe now you might have many confusions
and uh difficulty to understand what I'm telling right but don't worry uh you will get more idea
when we do the live demo also feel free to ask your questions on the chat as well so that uh
we can reply on the go okay so uh feel free to ask your questions on the q& and let's go to the
next slide okay uh what are the Core Concepts beh and
​ this guub actions and what are the main terminologies we are using here okay uh one is
Runner VM as I told uh we will be running different Powershell scripts from GitHub actions
whenever a code is pushed to the git right in normal case when we are using the publish tab in
our WEA studio uh so anyway we will be accessing the UA but there will be different codes
running in the background on our development machine right so there will be running the
same way in G action also we need a virtual machine to perform these actions and
​ it's directly available in GitHub and uh we can use either ubu Windows or Mac based VMS
which is available in the GitHub itself alternatively like if required you can use selfhosted
Runners as well based on your infra okay that's all about uh the runner VMS uh next one is
workflows um workflows are nothing uh but a yaml file we need to store inside the GitHub
repository in a predefined folder okay so the predefined folder in the sense I will come into that
when we are doing the demo you'll get more idea anyway uh using uh this only So based on
​ the content and config inser the yaml file only the GitHub actions will run okay that's the main
conern and next one is events um in simple words uh events are the triggers for starting an
action workflow for example in our cicd case now the actions for cicd has to start when a
code is pushed to the GitHub repository right so we can call Push as an event here okay here
push will be the event next one is jobs uh what are jobs uh uh in the point of view from like
guub actions whenever workflow runs there can be different scripts rending
​ inside it uh which which can be called as Jobs okay in now cicd like forour Action cleaning the
temporary files building packages deploy the package are three different jobs okay you'll get
more idea during the demo don't worry about that and finally Secrets this one we have already
discussed secrets are something similar to our uipath assets which is used to store the secure
 credentials in G action so what will be the credentials we need to store for this scripts and
workflow we'll be storing that in the secrets that's
​ it okay so meanwhile if you have any questions please post that in the chat and uh we can
answer the same as well and now we can have a live demo so you will be getting more idea on
these things okay for that first uh let me go to my ITB account okay so this is my GitHub
account and uh if you see uh I'm switching to the repository okay and currently I'm having only
one repository here that is weather report project for our demo case I'm going to create a new
repository okay for that I need to click on new and just provide the repository name
​ for now anyway this is for testing the cacd right we can put it as cacd test okay now we just
need to click on create repository then now we have created our repository but it didn't open
any branch or something like that and doesn't contain any code now we need to uh start a
process in weer studio and the same should be uh merged to this particular repository right
that's the thing which we do normally right for that let me open the U Studio okay let me create
a new process and cicd test this is the process name I'm
​ going to provide and just clicking on create okay now we are in our main uh right now uh the
main step which we need to do for the cacd setup using uh GTO actions is in our project folder
we have to add a specific folder and few files okay I will show what are those files okay okay
here I'm having a folder named scripts inside that you can see different Powershell scripts
okay these are directly available from the uip
​ public repository and you can see uipa deploy U job rent manage asset pack rent test Etc in
our demo as I told we are going to build the package and deploy the same to the orchestrator
for that from this we need only two scripts so those are uipath deploy and uipath pack and just
just copying this okay and I'm going to my project folder here I need to create a folder okay
and the name should be scripts I will tell you why am name this as scripts so if you need you
can provide other names as well so based on that there will be some conf creation
​ changes in the workflow yl file also okay so that's the concept here I'm going to paste these
two okay now we are having the scripts inside our project folder okay this is my project folder
uh what is next we have connected our studio to the GitHub repository yet right for that I'm
going to connect uh just go to uh teams Tab and click on get in it okay and this is our project
folder right just click on select folder okay now you can see everything here and finally sorry
first I am going to give the commit message okay just for connecting this
​ with our D repos now we are not doing the cicd and cicd just going to connect my uh process
with the U sorry giup repository okay just click on Commit and push okay now it will be asking
for a name and URL name can be anything for now I'm providing it as CD test so you can
provide any name So based on this name you you can find your like Target Target Branch
easily if you're working with multiple branches in the same project okay so I'm just providing
cacd test and we need to provide the URL here okay so for the
​ URL uh I need to go to my GI of depository and from here I'm going to copy this HTTP URL
okay just copying this and I can go back to to my studio and just paste here okay now we have
the repository URL here okay and next click on ADD and click on Save okay now our repository
is added here and if we click on save it will be merged to the deposit our code will be available
there as that's the concept okay now if we are going to the repository uh Let me refresh this
​ one and you can see main so our main branch is uh merged to this repository and it is
available here normally uh in our uh Enterprise case and all right the main branch will be
directly linked to the production orchestrator right so anyway in our concept I'm going to
publish uh my process to a development environment okay my development orchestrator and
 for that anyway I'm not going to deal with the main branch for that I'm going to create a Dev
Branch separately okay for that let me click here and just type the branch name uh
​ let me name name it as Dev slash CA CD test okay Dev SL test is my uh Branch name okay let
me click here on create Branch okay now uh we have my uh Branch also here we are we are
having Main in main we are having the code and in d/d test also we are having the same okay
including our scripts which we have added okay now uh uh in order to implement the cicd
anyway uh when we are pushing some uh code change to the to this particular repository itup
has to identify uh there is a uh workflow I have to start there is a action I have
​ to start for uh building the package and deploying the same to orchestrator right for that as I
told earlier the workflow should be stored inside a predefined folder so there's a general folder
which we are following for storing the GitHub actions okay and uh in order to create that I will
uh tell you the steps before that let me show you what is that workflow file which we are using
and what is the concept behind that okay for that uh one second let me go to my yl file okay so
this is the file which we are going to store inside that
​ particular uh GitHub rep Branch uh in order to trigger the workflow okay if you see uh this is a
file with yl format that is a coming with do yml with extension okay we need to store this file
inside that uh like directory so that's the concept and if you see here uh you can see lot of
things okay so uh if you are a beginner and seeing this you may get confused and uh you will
get some difficulty to understand this anyway uh let me just collapse these things and I will try
to explain each things separ uh maybe you will get some more
​ idea on the same okay if you see on the top you can see name what is the name development
workflow Okay so development workflow is the name for this uh particular action sorry to we
lost AIO okay how about now Jin yeah now it's perfect thank you oh okay okay so I will just
start with this one uh again so uh for this one uh you can see uh there's a name provided like
development workflow okay anyway uh whatever be the name which we are providing here it
will be showing in the G of actions okay so uh currently I have
​ named it as development workflow that's just for letting uh us know and we will be getting uh
understood like the target workflow is the one which ran in the actions okay and next you can
see on push okay on push means here we are defining the events okay now if I'm uh like on
push to branches okay so it will be triggering this particular workflow whenever A push is
happened to some branch and which is the branch can get that here see Dev SL cicd test okay
this is my uh Branch name okay so devd test let's confirm uh
​ is this is the same which we have created now cacd test okay this is the same okay now we
have provided like whenever there is a new push happening to this Branch this particular
workflow should run okay that's what here uh Jin is everything fine now is my am I audible yes
yes yeah you are yeah yeah okay and next is en M okay let me close this one and open okay
this is environment okay it is like as I told earlier we have to pass different values related to our
orchestrate enironment and all to this GitHub action right then
​ only it can be able to communicate with our orchestrator whenever we we are pushing
something to get right so now uh as we have provided here replace with your orchestrator
values okay now we need to provide the the project name that's the first thing so I have already
provided cicd test is our project name okay next is orchestrator folder okay I will just show you
my orchestrator and I have already created a folder called cicd Dev here okay and it doesn't
have any process inside okay so when we are pushing through our CD
​ only we'll be having uh some process to be available here okay now I have provided this folder
name as well okay so cicd Dev is my folder name next is orchestrator URL okay now we
 haven't provided any URL here that needs to be provided uh for the orchestrator URL we need
to provide the general uipath uh Cloud URL only that is HTTP cloud. ap.
​ com okay I'm just providing this here so replacing this with our normal Cloud URL okay and
next is orchestrator tenant for uh this one we need to provide our tenant name and after that
we need to provide the client ID user key account name and a CLA URL okay I will uh tell
what's that to get the orchestrator tenant name and uh all these things like client ID user key
and account name we need to go to our orchestrator and from this turn we need to go to the
user icon from here you can click on preferences okay uh just click
​ on the preferences fine so in the preferences you can see uh privacy and security so I'm just
clicking here and you can see uh the tenant name is default tenant and service orchestrator
and all the API access details will be available on this link okay uh you can see the user key
organization uh ID and tenant uh name and client ID okay so what and all we need here uh in
our um workflow first one is the tenant name right so I can just copy that from here this is my
ten name okay this is copied okay default tenant I have put
​ next one is the client ID uh user key you can see here we have provided like secrets.
orchestrator client ID Dev right so that means we are going to store that in the G of action
secrets and from there we are going to call the same anyway we are not going to store these
credentials inside this particular yaml file okay so we can go to that before that let me fill this
or like orchestrator account name as well the orchestrator account name in the sense you can
get that from here the organization ID okay just copy
​ that F uh now we need to set up our uh client ID and user key in the secret stab okay for that
uh let's go to the GitHub okay and here uh just go go back to our um repository this is our
repository and click on settings okay on the right you can see the settings in the settings tab if
you go down in the security you can see secrets and variables okay and inside this one you
can see actions just clicking on actions and going to create some repository secrets in our
case we have to create two repository Secrets right
​ I'm going to create just click on new repository secret and provide the name and the value
okay uh so what's your first secret that is orchestrated client ID Dev right this one I need to
copy so for your understanding this is how we are calling okay uh any secrets we have to
provide like this and inside that Secrets dot our uh Secrets name so that's the method which
we need to follow in order to get the secrets okay I have just copied this and now we need to
paste it here this is orchestrational Cent ID d right any we need the client ID from
​ where we can get the same from our orchestrator client ID okay the same I'm copying going
back to G and pasting it here okay next uh we can click on ADD secret now we have added the
same and next we need to create one more secret right for that we need to click on uh new
repository secret again and provide the name what's the name orchestrator user key this one I
copying okay and the value user key I think you are clear until this part just click on ADD secret
okay now we have uh like two
​ Secrets available here in our uh Repository okay okay now what is next we need to add few
more things right here you can see the client URL sorry CLA URL CLA URL in the sense uh
anyway in order to create the U package okay we need the uip CLA file available right using the
CLA file on only uh from Studio itself it will be creating the packages okay that's the concept
for that in our scenario we will be downloading the uapa CLA each time when we run this
workflow uh to our Target VM where we are Runing this particular workflow we'll be
downloading
​ that file to a particular drive from there we will be uh installing that uh I mean everything will be
happening in the backround like in our script okay so after that using that only it will be
developing the package okay for that we need to provide the CLA URL here from where you
can get that I just show you so for that can get that from the uh uath official repository okay
this is the repository just opening that one it's okay okay so uh this is the uh repository which
we need to download the CLA if you want to download the uip CLA means just
​ uh type uipath in the filter okay uipath do CLA so it will be displayed here currently you can see
two CLA files available uh one is uipath CLA next one is uh uipa Windows okay what does that
means uh currently uh anyway we are using the windows compatibility projects right for that
we have to use the uipa CLA Windows okay let me just click on this u.a.
​ windows and if you want to uh like get the link you don't need to download it just click on this
particular uh like uh three dots and from here you can copy so you will get the link and the
same link I have provided here as well okay now we have the uath CLA downloadable link
inside our yl file I hope this is clear next we can go to the next part that is jobs okay in jobs so
all these things are jobs I have told ear right so what will be the different different work block
we are executing in this particularl so those are called jobs in
​ our case print details cleaner build we nugget package publish V nugget package all these are
jobs now I'm going to open this print details okay if you see here you can see uh this is print
details and it runs on ubu latest now we have defined abundo latest as the like environment
which we are going to run for printing the details okay and next you can see uh different things
uh these are nothing but different G workspace values which we are going to print in order to
make sure everything is working as expected
​ the working repository uh and the event name and which is the workspace every data will be
just printed before we start the job okay that's it that's what we are doing in the print details
area okay next we are having a cleaner it is also running on ubu latest and you can see uh it is
like Anyway in your GI workspace there can be different temporary files uh available before we
uh start our workflow to run right anyway we are going to clean all these things all the
temporary fires and we are going to start it as a fresh okay
​ that's the concept and we'll be using the cleaner here okay this is the area where we are calling
the cleaner let me close this one again we are having two our main part one is build net
package and next one is publish U net package okay let's go to the build U net package area in
this one uh so you can see what is the prerequisites to start this one needs is cleaner if the
cleaner has run successfully it will be starting and it is going to run on Windows latest anyway
we will be uh running the UAP Bas things
​ all things in the windows right for that we are using Windows latest only for uh running this
particular script okay now if you see uh you can see different uh uh things here uh for running
this particular action we are calling an action which is already available from the git that is
action SL checkout for for checking out okay so we are calling the same here check out at V2
and next we are going to to run our script so as you have noticed we have stored that script in
our like project folder right two script one is for the build package
​ and next one is for deploying the same to orchestrator anyway now we are going to run the
build package okay that's the job which we have opened right so we are going to build the net
package here it is asking shell now we are using the power shell script in order to do that so
that we have provided poers shell and what is next run is going to run a script from the GitHub
workpace currently GitHub workpace in the sense our like Target Branch okay from there it is
going to call a script from the uh directory scripts slath pack.
​ PS1 okay now you should be able to understand why I have provided that particular name
while creating that folder as well in my project folder so whatever be the folder we are
providing there the same name should be available here as well then only it will be able to pick
that okay that's the concept and also it is passing different values which you have different
above uh in that first step right the same things it is passing to uh the particular uh script as
well that's happening here next one is upload uath artifacts if you
​ have joined yesterday session so you might have more idea on this artifacts artifacts means
that is the output getting from a particular job after it's run right so now we are building the
package so once the package is built anyway we are going to get that get one output what is
that that is our nugget package right that nugget package we are going to upload okay we are
going to upload that to a particular directory and we need to use the same where we need to
use that to publish the u n package anyway we need to use that right
​ so for it to be used by different like job we need to upload the same as an artifact and it can be
called for the next job as okay uh that's the concept let me close this nugget package part um
and finally we are having publish WEA nugget package right so publish uh nugget package
here uh what is the pr request build U neet package once this is run it will be coming to the uip
uh like public part okay and it will be also running on Windows latest and here you can see uh
like uh here it requests the artifact okay so first it will be getting that
​ artifact artifact using the download index okay this is the synx available from GitHub itself so
it will be downloading that particular artifact so first it will be downloading our uh like uh
uipath nugget packages location uh to this particular particular script and from here using this
it will be uploading that to our orchestrator okay here also we are using the Powershell script
and you can see is also going to run something what is that scripts uapa deploy PS1 which we
have inside our project skps folder okay so we are uh
​ just uh calling both of these for building we are calling the like uipath build and we are uipath
pack and also for deployment we Ina deploy PS1 this is also a partial script okay so that is the
main concept behind these things so I think now you got more uh some more idea idea about
how this yaml file is going to work and uh so if you can if you spend some more time so when
we are investigating these things no so if you are going through each line you'll be getting
more idea on how to do these things okay so for the first look it may
​ be uh like you may feel feel as a difficult thing but it's not like that in the like real case okay so
now we have everything here uh me just confirm okay we are having everything and next we
need to copy this one and we have to paste that in a like General uh directory which I have told
earlier right so we are going to that directory now uh for that I'm going to Second yeah now I
am in my uh d/ ACD test branch and here we need to create a like uh the we need to uh add
the file in the uh like General directory so I
​ will just show you what is the general format and all okay just click on ADD file and create new
file okay so in our uh like uh main directory so first GitHub will look for is there any uh folder
with the name do GitHub okay and inside that we have to create one more folder with the
name workflows okay now I have CLI like provided workflows now G uh understand okay there
is a workflow I need to take care of I have to start some action okay that is the concept here
so this is a general format which you need to follow
​ to store the yaml okay so inside. GW workflows and again provide a slash and provide a name
uh for now I am providing it as deploy do yml this extension is like import important we have
to Prov it as yml itself okay then only it will trigger okay and now I'm going to paste all the
things I have copied from uh this particular yl file the same thing we are going to paste here
 okay if you see you can see everything uh everything is added here right okay I think uh we are
good on this and after this I need to click on Commit
​ changes if needed we can provide any description or you can just click on com changes okay
now if you see uh we are having the do GitHub slw workflows in this particular branch and if
I'm opening this you can see the workflow file as well okay inside this workflow now we need
to pull uh this particular uh like uh files whichever is available on the particular Branch to our U
Studio again in order to get this/ workflows there okay so for that uh currently I am in my main
branch right now I need to uh switch to the one
​ second uh Dev Branch for that I think I need to refresh this one okay after refreshing you might
see cicd test/ cicd test okay so cicd test in the sense while create while in while we doing that
initial commit right that time I have provided the name as ACD test so whatever be the name
you have provided that will be coming here and after that our Branch name so I am choosing
this one and now uh I need to like uh full rebase whatever there available inside that Hub
Branch we need to call that our project folder as well
​ for that just right click on this particular project name and full rebase if you see now we don't
have that uh dot okay do Gib is already available here which I have created recently okay uh
one second okay now uh I'm going to pull rebase okay okay now like whatever is there in our
studio as well as whatever is there in the uath sorry that GitHub Branch right both are same
okay now uh if we are uh pushing some new changes to this particular Branch anyway we are
having our do G workflows and yl file available there
​ and we are having the scripts available in our project folder and and if we are pushing
something new to this particular Branch our cacd should be triggered and it should be able to
publish uh the same uh that particular process to the orchestrator by creating that nugget
package okay so let's try that in order to do that uh I'm going to add a slight change to this
particular process anyway are not going to do any advanced things in this particular process
this is for testing the cacd right I'm just providing One log message
​ like hello okay so this is the one what I am going to push since we have some update to our uh
project there will be a pencil icon available here so once we are pushing the same okay once
we are pushing the uh same uh to this particular Branch our uh workflow should be triggered
okay that's all it now I am going to commit the changes okay the commit message I am
providing as added loog message and just click on Commit and push okay now it has pushed
right uh let me go back okay it has pushed and now if you are going to actions there should be
​ some jobs running let's see that see uh one job has just started that is added log message
when I have added the log message it has started this action and let's wait for it to run and if
you need to go in detail from the actions stab you can just click on this particular uh like link
then it will be opening now as I discussed earlier you can see the name also which we have
provided on top of the yl F so whatever you are providing there it will be showing okay so I'm
just opening this one and if you see the cleaner has
​ already completed and print details also completed now it is trying to build the UA nugget
package let's wait for it to run is trying to build an a package yeah the built package part is
completed okay and if you need need to go in detail if you need to see the logs for this
particular job just click on this one and you can see everything okay and every logs which is
written from the script script will be available here you can see now the publish VI nuget
package is running
​ just downloaded theath artifacts it is deploying the package and this is is also completed now
uh if we are going back to our orchestrator uh let's see I'm going to the cacd D and you can see
 a new process added here right me open this one and the process name is CD test with a
version okay so if you are pushing again to the same uh process now it will be coming with a
latest version number which is higher than the current one okay that's the concept uh which
we are getting here okay so it will be added with a new version
​ number um that's it and this is just a demo on how to set up a basic cacd pipeline using
GitHub actions and S you can uh do more advancements to this by using different scripts such
as Runing the test cases managing assets Etc and also you can customize the yl file so I have
explained the yl file right based on that you can customize based on your like actual
requirement okay that is also possible okay I hope you're clear about this one uh let me go
back to the presentation and this is time for uh the C and over to
​ Palani be stop sharing yeah thanks thanks um we'll have a question I hope I'm audible yeah
yes sir can someone come okay uh so let's have a quick Quest um that you can use your
mobiles and then we'll share a screen and then there will be a QR code um maybe let me just
quickly share my screen yeah so I hope you can see my screen is it visible not take well it's
coming yeah it is okay so you can use your Mobile and then scan this QR or you can uh open
this website and then you can use this URL and then type this code so that it will
​ enable you to uh log in there one second SL maybe uh ashin if you can address the questions
we have uh I can get this question ready me yeah as one specific question is people are asking
for the the file and that poell script okay yeah for the same they need a link right so I can p that
in the chat yes yeah mean if you have some other questions please ask in the chat yeah you
can put it in the chat or better you can unmute yourself and then have the queries uh
meantime this get
​ load Lo but have any get the and then you can W up this question then maybe you can unmute
yourself and you can ask him right um hi just a quick question on the DAT actions yeah is this
uh feature that is open and free or is it something that is related to GitHub Enterprise users or
should you have some kind of a you know a premium version of GitHub or subscription for this
so the current one which I have shown you right this is my like personal uh gab account I have
created using my uh normal email ID and I have been using
​ the same uh for last two to three years so you should you should be able to do the same
without the purchase as well I believe okay and regarding the VM so I need to check whether
we need to pay something for using the VMS available from the guub I'm not sure maybe I will
just check that and I will let you know you can connect with me on LinkedIn if you need more
data on the see you have anys on that yeah I would like to add some more thing so yes gup
having some dedicated virtual machines technically they call that build surveys but when
​ you are doing this from on and Enterprise standpoint your codee will be residing under that
servers right that could be a problem so most of the organization will look for their own build
machines so on that case you can integrate that server into GitHub and make use of it so if
you I'm not sure whether you attended yesterday's uh C I mean event so we was talking about
how we can create agents on the dedicated machine so most of the organization will go with
that approach to prevent a data leak kind of thing
​ oh okay thank you all right uh I think we have got 16 responses are people still finding any
challenges to scan this up or if you're good then you can give a thumbs up so that we ensure
that everyone is there yeah okay is there any other query in the chat I think one got addressed
by Rahul himself all right so let's get started okay perfect let's get started then so we go for the
first question I don't know apologize for the delay n
​ okay okay I'm just starting go for the first question now okay so what does cicd stands from
the context of software development you have 15 seconds oh nice cool okay continuous
integration and continuous development um um that's the right answer and let's see who is on
the top of the leaderboard so the person who comes at the top uh will collect the email ID and
then Alan from uh was the C chapter be uh send sending you the goodies for the
​ top PE top person on the leaderboard yeah so Shiva yeah you're in leading Sheriff not much of
difference there just four points let see we'll go for the next one all right in GitHub actions what
is the purpose of a workflow file good so the right answer is configuring actions um good let's
see the leaderboard nice there are some changes in the
​ leaderboard Sheriff has gone to the top question and then I could see some Elmo the second
place okay we have still three more questions let's see how it goes here you go the third
question what is a job in the context of GitHub actions oh nice so it's actually unit of work and
a workflow great we got a good response let's see who's leading now okay morat who's morat I
think it's
​ the auto generat name I guess or fine so okay there so many changes uh I apprciate the
momentum let's see let's go for the fourth question now which feature is commonly used to
store credential securely in GitHub actions okay let's see wow okay I think good Secrets let's
see the leader now oh so many close calls Nash she you're leading now uh this is a final
​ question that we are going to see so uh keep your phones ready and then let's go for the fifth
one and the final One how can you view the logs and details of a specific job in a computer
giab acction workflow run for a uipath process right yeah it's it's accessing the job details you
know all right let's see who's the winner for today's CH oh right congrats mad um maybe I
would appreciate if you can share your
​ email ID in the chat so that I can forward that to Alan and then he can send you the goodies
sure thanks congrats M thank congrats again and U yeah so I think we good I'll just stop
sharing the screen uh if there is no questions uh I would appreciate if you can turn on the
camera if if your people are comfortable we'll take a quick click and then we'll wind up for the
day hey hi go he the winner is here yeah yeah sh sh sh hi sh hi a hi sh sh you keep changing
your
​ background nice okay let's take a quick pick uh let's wait for a few more minutes I think people
are getting getting prepared for the okay okay it'll take another minute yeah sure yeah hi n all
right uh are we good to go now yeah ready hey hi Santos hi nice thanks thanks for joining and
uh I I just quickly share the link for tomorrow's session uh if you haven't registered yet you can
and uh if you are looking for the previous day I mean yesterday session from jobin if you're
looking for the recording you can look
​ uh with this link you can copy this link uh for your prise and you can register for tomorrow's event and that's uh again will be taken by Rahul
I guess tomorrow right yeah so me you all tomorrow uh and uh thanks for joining today yeah thanks byebye thank you bye thank you all
byebye