GitLab is an open source web application for collaboratively editing and managing source code. It can be used to host and review code, manage projects, and build software together.
SendFox is an easy-to-use email marketing platform that includes a user-friendly dashboard, smart campaigns, automation series, numerous lists, landing sites, embedded forms, and more.SendFox Integrations
GitLab + SendFoxUnsubscribe Contact in SendFox when New Commit is created in GitLab Read More...
GitLab + SendFoxUnsubscribe Contact in SendFox when New Merge Request Event is created in GitLab Read More...
It's easy to connect GitLab + SendFox without coding knowledge. Start creating your own business flow.
Trigger when a commit is made on the specified project.
Triggers on issue events, e.g. when an issue is opened, updated, or closed.
Triggers when a new job occurred.
Triggers on an open, merge, or close merge request event.
Lists the campaigns.
Lists the contacts.
Lists the lists.
Triggered when a contact is unsubscribed.
Creates a new list.
Unsubscribes a contact.
GitLab is an open source web-based Git repository manager that allows teams to work together on projects from a central location. The software can be used for both public and private repositories with either free or paid accounts available.
GitLab provides a powerful set of tops to manage projects and source code, including issue tracking, code review, CI integration, and flexible authentication options.
SendFox is a web-based email marketing platform that allows users to create and send professional-looking emails with ease. The top offers features such as HTML templates for customized designs, drag-and-drop content, and a WYSIWYG editor.
To start integrating the two products, we need to install gitlab-runner on our GitLab server. There are three ways you can go about this. You can either use the Omnibus installer, or use Docker or install it manually. Since I am running on Digital Ocean, I prefer the last option. It was a little tricky to find out how to get it installed on my droplet (Ubuntu 14 x64), but I managed to do so by finding a guide in German. I will not include the steps here, you can find them here. https://blog.sendfox.de/2017/04/08/dslk-gitlab-runner-installieren/
But now that we have gitlab-runner installed, we can use it for building our project. We just need to make sure that all our files are committed to GitLab and then we can set up the build in our .gitlab-ci.yml file. Here is an example of a build for Angular 2 using gitlab-runner .Here we can see that we are using gitlab-runner for a GET request on /api/test . We are also using the http_proxy environment variable which was passed through POST in our job description. This essentially tells us that we want to run our tests through an http proxy, so we can get around the firewall on our droplet and access services like Firebase. In this case we are using http_proxy=http://proxy_host:proxy_port . This tells our runner to go through the given proxy when accessing any host on port 80 .We also have variables for our test , build , pre_build , and post_build stages. These allow us to pass variables to each of these stages individually. For instance, if we wanted to run our tests in watch mode instead of just once, we could change the value of the test variable from true to false . This would tell the runner to run the tests only once instead of continuously.All of these things combined lets us define a very well defined build pipeline. We can contrp how many times our tests run, what parameters and environment variables they use, and what happens after they have completed. If you would like to learn more about gitlab-runner , you can find their documentation here . https://docs.gitlab.com/ee/ci/runners/README.html#gitlab-runner-overviewI will now list some pros and cons of using gitlab-runner within our organization:Pro:With gitlab-runner , we get a very well defined workflow that makes it easier to test our software and know exactly what is going on at all times. Our builds are also very fast since they don't have to re-download all of our dependencies every time they run. Finally, we can run our builds on any machine that has ssh access to our gitlab server without worrying about setting up a complex system that relies on vagrant .Pro:We can use gitlab-runner as a replacement for Jenkins CI because it is much simpler and easier to configure than Jenkins CI since it does not require you to install Java or Maven and it is open source so you can always add new features yourself!Pro:We can use the same product as the customers of SendFox! This means that if they want to know exactly what tests were performed and how long certain tasks took to complete, they can jump into our gitlab repo and look at the build logs directly! This also gives them direct access to people who can help them spve problems related to it!Con:For now, we cannot yet use gitlab-runner with android projects because there is no official plugin available yet. This would allow us to run our tests on an Android emulator during the build process as well as on real devices connected via USB or WiFI . Hopefully in the near future this will be possible!
The process to integrate GitLab and SendFox may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.