trivelop   home of @rrrene   –  

InchEx 0.3.0 released

I was a fan of the mix hex.docs task since it was first introduced. I liked the simplicity of the process and even wrote a blog post about automating it.

Elixir on Inch CI was another story:

Up until now, getting Elixir projects up and running was a bit of a hassel.

You had to configure Travis to report the exaluation to Inch CI and then wait for the two services to finish talking to each other before you could view your project page (the URL of which you had to guess). Then, you had to find out how to get your badge, see suggestions etc. yikes

This ends today, with the release of InchEx 0.3.0.

You can now add your Elixir project to Inch CI by typing

$ mix inchci.add

This adds and evaluates your project and gives the URL so you can take a look.

If you like it, the task gives you assistence in setting up your badge and Travis configuration. If you don't, well, at least you were able to find out without having to jump through all the hoops first.

What do you think? Tell me via Twitter or create an issue in the InchEx project!.


Pour me an Inch of that Elixir

I recently announced the addition of Build History to Inch CI. I did not disclose however that Elixir played a vital part in this.

Inch CI

Build History gives you an overview of what changed over time regarding Inch's evaluation. It does so in real-time and that magic is provided by Gossip, a socket server that uses Phoenix Channels for passing messages between Inch CI's worker processes and connected clients.

The idea is simple: We can use Phoenix Channels to publish "build events" to all subscribed clients via PubSub. The events are received by JavaScript-clients, which then change the currently displayed build history.

The workers on the other hand can "ping" the Gossip server with a simple HTTP request to signal events that are taking place. As you may have noticed, these clients and workers are not written in Phoenix or Elixir, nor do they need to be, since the used technologies are all based on open technology/standards.

This way, it was easy to connect the existing infrastructure (Rails web app, Ruby workers and its JS-flavored frontend) with the new Gossip server written in Elixir.

The result: builds appear auto-magically in the history of a project whenever a build starts, updates or finishes. It's like magic.

Read all about Phoenix Channels and if you haven't, give Elixir a try.


Inch CI: Introducing Build History

In my last blog post I wrote that the new design sets up Inch CI for extensions in the future. Today marks the release of the first of those extensions: Build History.

Inch CI

The Build History gives you an overview of all the builds that happened in a project. New builds are added automatically to the "newsfeed" showing if something changed regarding the project's docs, giving you props for improved docs and a red heads-up if Inch thinks something became worse.

As always: if you have any feedback or suggestions, contact me via Twitter, create an issue in the Inch CI project or simply email me (mail in Github profile).


Fork me on GitHub