Skip to main content

continuous integration

I've been in devops for almost 30 years. This clearly predates the origin of the word. Back in those days we did not care about what we called ourselves it was just about the work. In the last few years that has changed as freshman programmers have entered the field and wish to distinguish themselves in order to catch the wave that others have already rode.

I have used or familiar with a number of CI systems. Drone, Travis, Jenkins/Hudson, TeamCity, Go(aka continuum), IBM had a huge build system for it's OS/2 build. One could make a distant argument that some IDEs and Makefiles are also CI systems, however, it would be wrong.

So while I have been working on my IDE project I decided that I would start with tmux (still not there) and a change triggered makefile. This is not exactly a CI system but it is the foundation. The "autobuilder" takes some lessons from the CI systems...
  • when the user saves a file then start the build
  • ignore some files
  • do not get confused by meta artifacts
  • custom build tasks
  • stop on the first failure
  • capture the output
  • stream the logs
This will eventually get some new features.
  • implement git receive (integrate with github and bitbucket)
  • trigger docker builds similar to Apcera Gnatsd (link)
  • integrate with my remote IDE so that it can build local and trigger git builds
  • auto builder dashboard
Pull Requests are welcome.

UPDATE: and I forgot the other point I was trying to make. Depending on the size of the project(s) you are working on your $$$ will go a long way. The think that bugs me is that companies like and charge a lot of money.  Travis charges $129/mo and Drone $20/mo. But you can build your own micro build machine for $20/mo on a VPS anywhere and if you implement a dynamic build system you can shave that price even lower.

UPDATE: I was boyscouting my inbox a few minutes ago and I stumbled over emails from Cloud9, Nitrous, and Codeenvy. While these projects are awesome I think we can all implement our own. With some basic skills in server side programming implementing a websocket app, static server, something that looks like the rmate server, and a CI makefile thing... it's all very doable.


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…