CI/CD

[DiSSaRRaY]

Hello fellow devs,

I'm sure quite a lot of you are using CI/CD, but the question is always - which one?

Currently we are using a custom Jenkins setup, and VSTS.

Jenkins does the bulk of our stuff, and VSTS is "the new kid" on the block in our environment - we don't have many things running on that side.

We're also going to port our mobile projects over the MS/VS App Center.

What do you use, and why?

 

[Priapus]

We're using Jenkins too. But for mobile only. We've integrated Fastlane with it as well for iOS and now everything is automated. Android is next to have Fastlane integration as well.

As for why Fastlane - for the automation of course. It handles all the certs / signing and publishing to the App Store. Easily saves me 20 mins each day using it.

 

[DiSSaRRaY]

We're using Jenkins too. But for mobile only. We've integrated Fastlane with it as well for iOS and now everything is automated. Android is next to have Fastlane integration as well.

As for why Fastlane - for the automation of course. It handles all the certs / signing and publishing to the App Store. Easily saves me 20 mins each day using it.

Very cool. I had a read through some of their documentation and github posts.

It doesn't seem to support Xamarin?

 

[Gingervitus]

We use Jenkins as well and have a nice setup going. With one button you can kick off a build, run tests, tag the build in sourcetree and it uploads to the playstore for us with the correct version codes etc. We only add the release notes and voila!

I see a lot of advertisements for CircleCI, but I have never used it

 

[CarboVan]

We recently moved to Bamboo (for sites and services) Though we might ditch that again in favor of TFS online
For mobile, our okes are using Bitrise.io. Works pretty well, and supports React Native, so Xamarin should work also.

 

[dalion619]

Azure DevOps aka VSTS.

Some with the hosted agents and some with private build agents.
It is all integrated with Azure so no need to store environment deployment config secrets.

 

[Reegz]

Jira+Bitbucket+Jenkins+SonarQube+Artifactory+Ansible+Docker

 

[PHalanKS]

Old setup for Android apps and ASP web apps was TeamCity and then web apps deployed with Octopus. Tickets on JIRA. Source code in TFS.

First change was source code from TFS to Git.
Next change was replacing TeamCity and Octopus with VSTS for the web apps and then eventually the Android apps too.
Also changed from a Nuget VM to what's now "Artifacts" on Azure DevOps (it used to be an extension on VSTS).
Next and more recent change was replacing JIRA with Azure DevOps Boards too.

Still have some stuff sitting on Confluence that needs to move over to being markdown in the repo (which will "automatically" become the Azure DevOps Wiki.

 

[Reegz]

@PHalanKS - how has your experience using Azure been?

 

[PHalanKS]

@PHalanKS - how has your experience using Azure been?

Sorry only saw this now. Do you mean azure as a whole or just azure DevOps?

Sent from my SM-G950F using Tapatalk

 

[Reegz]

Azure's Devops-y tools. And we'll Azure as a whole.

 

[PHalanKS]

At the end of the day all CI/CD tools are basically just running stuff on the "command line" anyway so they all pretty much do the same thing. The interface is updated fairly regularly and seems be getting better and better. Their big advantage is that they are building one big tool that does source code, tickets, build, deploy, artifact/package management and documentation so you don't even have to think about integration. Everything is also all in one place. You also don't have much to set up or maintain, where previously we had a VM for teamcity/octopus and another for nuget packages (was a bit of a waste). My only complaint is that if you go with the "hosted" agents at $40/ea a month everything is always a fresh build etc. Your other option is to use a "private" agent and then you have to set up and maintain everything. I would prefer the ability to have a "standard" VM/docker image but to be able to select something like the VM levels, but have it still fully managed, just a bit faster and the ability to have incremental builds, saved packages etc.

As for Azure as a whole I haven't used other clouds extensively so I can't really compare. It doesn't seem to be the cheapest solution for certain things like just hosting an "html" site (lowest "proper" service plan is ~R800 a month) but it's a winner when you need a SQL database in a hurry...

Sent from my SM-G950F using Tapatalk

 

[DiSSaRRaY]

We use continuous deployment and unit testing on Azure for web apps and APIs. (it was done before our current build server)

The way the one specific project is set up, is to deploy for different clients depending on what code is committed, using gulp to set everything up.

Azure's job runs pretty fast and flawless, we haven't had a single issue with it.

 

[Reegz]

Cool. Thanks for the insights folks.

Been using AWS for some time as a IAAS for our Openshift installations. We've had our share of teething issues over the last couple of years. A lot of them ended up being due to bugs in either Openshift of AWS specifically around accessing shared volumes. Also, our Infrastructure team are overly price sensitive and tried using the cheapest options available rather than fit-for-purpose specced VM's.

So, it's been a but tricky trying to apportion blame when the reality is that the components have had their hands somewhat tied behind their backs.

AWS are planning to launch a data centre housed in Cape Town by 2020; that's going to be quite interesting to see if businesses react and change their attitudes towards off-prem hosting.

Amazon’s first African AWS datacenter will open in Cape Town in 2020