Deploying code deploying-code

Transcript

Hello everyone, my name is Varun Mitra and welcome to the video. In this particular lesson we are going to deploy a custom project, by integrating Adobe Git repository, with an external Git repository. After completing this training you will be able to use - Adobe Git repository and integrate Adobe Git repository with an external Git repository. Now this particular video has a lot of learning resources that are provided along it. If you want to go to - the link provided below you will be able to - arrive at a white paper, wherein we have detailed all of the steps that are being performed in this video. On the left-hand side we - have the local workspace, that has been updated regularly. The first commit to the Git workspace creates a branch called as Master, and the branch here has a - specific commit identifier. Now let’s just go ahead and perform a couple of - more commits on our branch, and this should move - the branch pointer along with its own unique identifier. Now, I want to copy these - commits to the remote repository on the right-hand side of the screen. Here, I have set up the - Cloud Manager Git repository as a remote called as Origin. The name origin is simply used to identify the primary - remote Git repository. The station is especially useful when working with multiple - remote repositories. In GitHubs coping commits and branches from local repository to a remote repository is - called as Doing a Push. The command for that is - simply called as Push.

Here we have pushed the master branch and all of its history to the - remote origin Git repository. Let’s say someone else on our - team has pushed another commit to the origin remote. To copy the commit from - the remote Git repository to the local workspace, we use the Pull command. Git Pull will help us in maintaining the tracking relationship between origin and local workspace. Now let’s say one of our teammates has actually created another branch and now I want to pull - this branch locally. This can be done with the - help of a two-step process. The first step is to - make our local repository aware of this branch and it’s commits with the help of Git Fetch. The second step is the Checkout command. The Checkout command switches the branches on the local repository. -b option creates a new local branch using the second branch - fetch from the remote. Many Cloud Manager customers - push their good to a repository that they managed themselves as well as to a Cloud Manager - provided Git repository. You would typically use origin to refer to customers repository because that is the primary - place where development happens. Then you would use a name like Adobe as a remote name for the - Cloud Manager Git repository. The customer Git repository - in the local workspace have the same history and the data is only pushed to the customer manage repository. Initially this is the situation most migrating and adopted - customers would be in. You have data and history - and your local workspace and remote repository, and - you need to get your code in the new Cloud Manager based repository. So, we actually already saw - how push, but in this case because we do not want to - change the tracking relationship so we will omit minus U and - use Git Push Adobe Master. Sometimes so whatever it isn’t, you may want to use different branches between remote and local remote space. So, to do this you specify - the remote project a part of the push. You will notice that the local name master has gone before the remote branch that is being developed in this case. When the Cloud Manager runs a - stage to production pipeline it points to a specific commit - when to run the pipeline. Now if you ever need - to inspect this locally you can first them from - the Cloud Manager remote using Git Fetch. I want to stress here that Cloud Manager is not a new commit during execution, it simply texts with an existing commit. This does not change the - history of your branch. Now let’s just quickly go ahead and see how you can push a custom project to your newly provisioned AEM - as a Cloud Service Instance. So right over here, I’ve - opened up my command prompt. Most of this particular demo will be done using the command prompt and - using different Git commands. If you are not well-versed with GitHub or you have trouble using - command prompt on your machine, you can also download a tool - called as GitHub Dexter which will make it easier for you to push and commit - code to your Git repository. So right over here, what I’ve - done is I created or cloned the WKND Site that is available - on Adobe’s publicator. I’ve simply created a - copy of the WKND Site so that I can do some changes onto it. Now, what I’m going to do is I’m going to push this - particular copy of WKND Site to my Cloud Manager Git repository. You should know the URL pointing to your Cloud - Manager Git repository. If you don’t have the URL ready what you can do is you can go - to your Cloud Manager Instance and in the pipeline card you can click the manage kit button. From here, you can get - access, or you can verify the URL pointing to a - Cloud Manager GitHub. You can also generate a new username and password for yourself. If you don’t already have that I already have the username - and password generated for me so I’m going to skip this particular step.

Going back to my command prompt the very first command - that I’m going to run is get remote add origin. And I’m going to point to - my Cloud Manager key tab. So, by doing that I’m adding my Cloud Manager - GitHub as an origin repository or I’m labeling my Cloud - Manager GitHub as an origin and I’m going to add it - to my local WKND Site that I’ve created.

Once this particular command is run my Cloud Manager GitHub will be registered with my local project. Now this local project - could be your own code base and you might want to push it - to your Cloud Manager GitHub. Once this is done I will add all the files that are in there to my Cloud Manager GitHub. So, let me quickly find - the appropriate command. By doing git add . I will be able to add all of the files.

Once this is done, I - would perform a commit. This will ensure that all of the changes that have been done in my local project are committed properly and - a tag is attached to them.

With this done, I’m - going to simply go ahead and push all of my changes to my origin. Origin happens to be my - Cloud Manager GitHub. Let me execute this command it might take a few minutes - for this command to execute. Since I read this command - quite recently, as such I’m able to see that - everything is up to date. However, if there were changes that would have been reflected over here. At this point, you can go - back to your Cloud Manager and you can execute a suitable pipeline to deploy your newly added code to an appropriate environment. So, this is how you can integrate your cloud management GitHub - with an external system. Now, this particular system - could be your own get repository or it could be one of our WKND Sites or it could be one of the sites - which contained a demo site for your AEM as a Cloud Service Instance. Now I’m going to quickly - also show you the GitHub link or the white paper that - we have created for you. The white paper is hosted right over here and the URL to it should - be available to you in our Learning Management System. You can directly go to this particular URL and you can get access - to all of the commands that we have used in this demo. You can directly copy paste these commands and you will be able to - arrive at the same reserve as I just did.

So, I would suggest to you to go ahead and open up this particular tutorial and follow the steps that are in here. It will make it a lot more easier for you to follow alongside this particular video that we have created.

So now, we just saw how you - can deploy a custom project within your Adobe Git repository.

Now, you should be able to - use Adobe Git repository and integrate Adobe Git repository with an external Git repository. Thank you very much - for watching this video and have a great day. - -