August 2018 Release: GitHub Cloud Integration

In this video, learn how you can get CI/CD benefits, including increased collaboration and version control with SnapLogic’s GitHub Cloud Integration feature.

To learn more about SnapLogic’s GitHub Cloud Integration, visit the SnapLogic Blog.

Read full transcript

Hi! In this demo, I will walk through the GitHub Cloud Integration feature. The GitHub Cloud Integration allows management and movement, at a project level, of SnapLogic assets from one Organization to another.

For this demo, I am working in the ‘Tim’ space and the GIT and GIT3 project. To integrate GitHub with SnapLogic, I have to first authenticate my GitHub Cloud account and allow SnapLogic to connect. I can go over to the upper right-hand corner and click on my name. If authentication is required, there will be a “GitHub Authentication” button. Otherwise, you will see the GitHub ID and last authentication date.

When authenticating to GitHub Cloud, users may have to sign-in to GitHub with their username and password, and then authorize SnapLogic to connect.

If a repository is not yet connected to the SnapLogic app, users will have to first connect  the SnapLogic app through the GitHub Marketplace. The link to the GitHub Marketplace can be found in the SnapLogic documentation.

Now that everything is properly authenticated, I can begin using the feature. You can see that I have a  Twitter2 pipeline in my Git project and I will use this as an example of an existing asset in my project.

The first thing I’ll do is  check out the GitHub repository.

The list of repositories in the dropdown are repositories that have been connected to the SnapLogic app that I am also a part of collaborating with. There are different branches and tags that I can check-out but I will check out the master branch in the demo.

I can see the assets that are tracked in the master branch within GitHub.

In the case of having a blank repository, then no assets would be brought in,  and thereby, nothing to track. I would just have my untracked assets. Since I have assets in the repository, the assets are now checked-out into my project.

Now I am going into another project, Git3, and for this demo, this project will represent a project from another org.

I’m going to check out the same repository in this Git3 project.

I can see that in this project I don’t have any assets, but I will show how to add or update assets in one project, check them in, and then pull them in a downstream project through the feature.

Now, we see that there are a total of 7 tracked assets in this project. Going back to the GIT project, there are 7 tracked files and 1 untracked pipeline.

To illustrate adding new assets and a check-in,  I will add a file to this project.

After adding the hulk jpg file, I am now going to add that to my repository.

and I’m going to check in or commit this to GitHub.

If I want to make additional changes I can make those changes and check them in. The Hulk jpg is now committed to the project.

Once again for this demo, the  GIT folder is our development environment and the GIT3 folder is our production environment, I can easily bring the Hulk.jpg file into GIT3 production environment by doing a pull.

The Hulk JPEG file has been created and the new Hulk file is added to GIT3.

To review what i did earlier in the setup, I have one repository connected to two different projects. GIT is the project in the development environment and GIT3 is the project in the production environment. I also showed how I added an asset or made changes to assets in the development environment. I then committed the changes to GitHub and brought those changes to the production environment, GIT3. We did this by doing a GitHub “Pull” from the project in production to obtain the latest changes. If I wanted to remove something from the repository I could also

Remove the Hulk file from the repository and then perform a check-in. Then I would commit this back to GitHub so that the repository gets updated and removed from GitHub. At this point, I can also completely remove the Hulk file from my project.

In the case of a rollback scenario where a mistake was made, I can check the prior build, which I presumably have the build tagged so that I can easily access to that version from GitHub.

The GitHub Cloud Integration helps users manage the lifecycle of a project and the versioning of assets across multiple environments from within the SnapLogic platform.

Thanks for watching this demo. Visit docs-snaplogic.atlassian.net to learn more about SnapLogic.

Analyst Report

451 Research: SnapLogic eyes international growth with iPaaS updates and…

Read Now

Analyst Report

Gartner Names SnapLogic a Leader in the 2018 Enterprise iPaaS…

Read Now

Case Study

Turning data into decisions at Pure Storage

Read Now
Contact Us Free Trial