VSoft Technologies Blogs

A brief look at system-defined Continua CI server properties - old and new.

Version 1.9.2 of Continua CI has been released. This post is a reminder of the new functionally in this version for exporting project configurations to a file (which can then be imported back into Continua CI), the ability to requeue failed stages, and improvements to build cleanup settings to allow each type of build by-product to have a different shelf life.

This new beta release includes functionally for exporting project configurations to a file (which can then be imported back into Continua CI), the ability to requeue failed stages, and improvements to build cleanup settings to allow each type of build by-product to have a different shelf life.

This post explores the options currently available in Continua CI for running daily builds.

Today we released version 1.9 of Continua CI. Here's a summary of the main new features.

I'm not usually one for publishing roadmaps, mostly because I don't like to promise something and not deliver. That said, we've had a few people ask recently what is happening with Continua CI. This post outlines our plans for the rest of 2018 and into the future.

New archiving functionality added to the workspace and repository rules in Continua CI

SSL standards are changing, and older SSL/TSL protocols are slowly being deprecated, or even turned off by some services. This post shows how to enable TLS 1.2 support in Continua CI.

In this post, I'm going to look at how to structure a FinalBuilder project so that it will run on your dev machine, or on your Continua CI Server without modification. This allows the best of both worlds, develop and debug your build process on your development machine, and then later run it on your CI server.

Continuous Integration Servers are often underspecified when it comes to hardware. In the early days of Automated Builds, the build server was quite often that old pc in the corner of the office, or an old server in the data center that no one else wanted. Developers weren't doing many builds per day, so it worked, it was probably slow but that didn't seem to matter much. Fast forward 20 years, and the CI server is now a critical service. The volume and frequency of builds has increased dramatically, and a slow CI server can be a real problem in an environment where we want fast feedback on that code we just committed (even though it "worked on my machine"). Continuous Deployment only adds to the workload of the CI server. In this post I'm going to cover off some ideas to hopefully improve the performance of your CI server.