Stuck on CircleCI

 2 years later and where did my CI journey take me? 

Well as it turns out not very far. My first migration to CircleCI was so successful that I didn't feel the need to go any further!

CircleCI hasn't been perfect, there have been issues with performance and a pretty public data breach but that has not put me off! Once you have fixed on a CI system that fulfils the basic requirements then they are pretty sticky! In hindsight I knew CircleCI would be pretty good if you look at the number of posts and public reviews it always comes out well so I should probably have started with the unlikely candidates first!

Now we're 2 years on has anything changed? The answer is no - not really. As of the date of this post this GitHub repo ligurio/awesome-ci has a great well maintained list of CI servers/services so if CircleCI doesn't do it for you then you're bound to find one that does by reviewing that list. 

For me, I'll stick with CircleCI - at least for now!

Comments

Post a Comment

Popular posts from this blog

Gradle and the parent pom

We've all got used to various maven features that we have come to rely on, and in my effort to migrate to Gradle I have endeavoured to find alternative replacments, one of which is the parent POM functionality. Gradle does not natively have this feature that as Maven users we rely on. Workarounds There are a number of workarounds documented, firstly the most common is to use the apply from to load a file from a URI (you can use a URL) but this is not ideal for many reasons. The alternative is to write your own plugin that alters your build.gradle file. Anorakgirl has a great write-up on how to do this here  Gradle and the parent POM  and is the inspiration for my plugin. Gradle pater-build plugin I love Anorakgirls write up but I was thinking that it really is a workaround and devs would need to start to understand the internal Gradle API, so if the apply from syntax has its short comings as Anorakgirl pointed out then how about subverting or working around them. I cr...
Read more

Pushing changes from Shippable to Github

If you use Shippable as your Continuous Integration server on an open source project hosted on Github you will find that by default you cannot push any changes back to Github such as when you increment a version number and wish to push the changes back. This is because Shippable uses HTTPS for public Github repositories so trying to push changes back to it will require a username and password. Solution The solution is actually simple and requires two steps, firstly installing the the deployment key in your user or repository and then switching git over to ssh rather than https. Deployment key You can find your shippable deployment key on the right hand side of your account, this is a standard SSH public key, copy this key. You can either add this key to your repository or to your user (or another user if you so choose) that has access to your repositories. Be aware though that Github restricts the re-use of keys so if you add it to your repository then you can only have it...
Read more

Maven Repository on Cloudflare R2 with Gradle

Image
 Here's a challenge with the public availability of the R2 Cloudflare blob storage is it possible to use it as a Maven repository with Gradle as the build system? The short answer is yes! The longer answer is that it is, but it is a bit disappointing with Gradle, I'll explain why it's disappointing later, but first (and probably the only bit you will read) is how. Step 1: R2 storage I'm assuming you have a Cloudflare account and have signed up for the R2 storage option. Navigate to the R2 Storage option on the R2 page Click 'Create bucket' Give the bucket a name, for the purpose of this tutorial I'm calling the bucket ' tutorial-r2-maven-bucket ' Click create and you should have your new bucket all ready for use Make note of the URL for the bucket, you'll need this later Step 2: S3 Auth token The secret sauce with using R2 as a maven repository is to treat it as an S3 bucket and use it's S3 compatible API. To do this you next need an S3 Auth...
Read more