Magnum CI Blog

[magnum-ci]

OpenSSL Security Update

Two days ago, on April 7th, an OpenSSL vulnerability had been publicly disclosed. This security threat, a.k.a the Heartbleed bug, can be used to compromise servers that use SSL to encrypt their network communications. We've already addressed this concern and have upgraded our service's components with a fixed version of the OpenSSL library and have replaced all certificates and credentials. We have no evidence of any breach and, like most networks, our team took immediate action to fix the issue. Although it is unlikely that our service's security had been breached, we strongly recommend that you change all passwords and API tokens that you are using with our service as a precaution.

For any additional questions you can reach out to us via our support email: [email protected]

[magnum-ci]

Build VMs Update

Every build that gets executed on Magnum CI is based on 64-bit Ubuntu 12.04 image that has a majority of popular tools and databases already preinstalled for your convenience. We run periodic software updates on all our build VM images (Ruby, Node, Go, PHP, Generic) to stay up to date. There has been a few changes in supported database and language versions in the past 2 weeks. 

Recent update includes the following changes:

Switch to PostgreSQL 9.3 for all projects by default.

Deprecate node.js v0.6 support, only 0.8, 0.10 and 0.11 are supported now

Added MRI Ruby 2.1

Git is updated to 1.8.5.2

Subversion is updated to 1.7.9

Mercurial is updated to 2.8.2

Updated OpenJDK / JRE to 1.7

Added heroku toolbelt to all project images

Added QT dev libraries to all project images

Added ImageMagick dev libraries

If you're missing something or would like to get help with installing a custom software or package, hit us at [email protected], we'll try to help as much as we can. 

Also, all updates that happen on Magnum CI infrastructure, api or site are being tracked in our github changelog repository. You can access it here: https://github.com/magnumci/changelog

Keep shipping.

[magnum-ci]

Build notification addons

We're rolled out a new project settings section "Addons". There are not many addons yet, but it'll grow fast. Today we added 3 addons for build notifications: Hipchat, Slack and IRC. 

Hipchat notification example:

Slack notification example:

Open Source

These addons are available on our github page:

https://github.com/magnumci/addon-slack

https://github.com/magnumci/addon-hipchat

https://github.com/magnumci/addon-irc

Need to integrate with something else? Ping support and we'll get it sorted out. 

[magnum-ci]

Interface lift

Magnum CI just got a new fresh look. This is the very first interface update since our launch and part of overall UX improvement. As our set of features continues to grow we wanted to keep everything simple and clean. Thanks to Masha Safina, its possible now. 

Updated documentation styles:

New builds page:

Build page got cleaner:

All build extras are available from sidebar:

Project summary:

[magnum-ci]

Extended build coverage details

Build coverage percent has been collected by Magnum CI worker for ruby projects for quite some time. Until now it did not include per-file coverage metrics: total lines, lines covered, etc. Now this feature is available for all ruby projects that use SimpleCov. 

To see details, click on coverage status icon on build details:

This is just a summary of coverage report that you typically see in "coverage/index.html" file. You dont need to configure SimpleCov with any additional formatters, parsing is done directly on html. Currently it supoorts SimpleCov >= 0.4.5 (which is pretty old).

Magnum CI does not collect or store any customer code in the database or anywhere else so this report does not include any per-line coverage details. 

[magnum-ci]

Public project build status pages

Today we rolled out a new feature: public project build status pages. Since most of the projects on Magnum CI are private, you have to be a collaborator to see recent builds. Now you can simply share the public project link with anyone. To grab the link, go to project "overview" tab:

Includes recent builds page:

And individual build details page:

[magnum-ci]

Select build status image branch

Until now there has been no way to select a different branch for build status images. By default it shows build status on master branch. Some projects don't use master branch as primary so image was not reflecting a correct project build status. 

Now you can simply select branch using dropdown on project overview page:

[magnum-ci]

Changes to push receive URLs

There has been a new change in push receive URL structure. Currently, to connect Magnum CI to code hosting provider you use url like this: https://magnum-ci.com/api/v1/payload/:provider

Today we rolled out a new endpoint to receive payloads:

https://magnum-ci.com/receive/github - Github

https://magnum-ci.com/receive/bitbucket - Bitbucket

https://magnum-ci.com/receive/gitlab - Gitlab

https://magnum-ci.com/receive - Generic

Old endpoint is deprecated and will be removed on December 1st, 2013. Setup form already includes the new URL:

[magnum-ci]

Testing Rails Applications

Magnum CI offers a very easy way to test Rails applications. Database creation and migration, services and test framework detection, dependencies installation, build execution: its all done automatically.

By default, you dont need to define any custom build steps. Most of standard rails applications that use RSpec and Cucumber could be tested without any additional configuration.

Here is how Magnum CI will execute your build from start to finish:

Clone repository and checkout code revision

Check which ruby version to use from .ruby-version or .rbenv-version files.

Examine project Gemfile for special dependencies. Start services if needed.

Install dependencies with Bundler

Create and setup test database (PostgreSQL, MySQL, MongoDB, SQLite3)

Execute RSpec or Test::Unit tasks

Execute Cucumber tasks if feature tests are present

If you're using non-standard database credentials for testing, please check Database Configuration manual for more details. Takes a few seconds.

As a bonus, your application's dependencies will be checked for updates and you'll see a detailed report on the build page. Code coverage metrics will also be collected if SimpleCov gem detected in the Gemfile.

For any questions or suggestions, please contact [email protected]

[magnum-ci]

Integration with Gitlab

Gitlab is so far the most popular self-hosted code collaboration platform today. You can either run it on your own infrastructure or use their hosted version at gitlab.com. Its completely open to public (view on github) and perfect for individuals and teams of various sizes. Unfortunately, most of the CI services (Travis, Circle, etc) out there does not support anything except Github or Bitbucket.

Magnum CI brings direct support to both self-hosted and hosted Gitlab applications. You can now easily hook your application and run tests in a matter of minutes. This post will show how to get started.

 Connect repository to Magnum CI

Assuming that you already have an existing repository on Gitlab, go ahead and create a new project on Magnum CI. You will see the following service integration screen right after.

Copy the web hook url from Step 1 textfield and open repository settings on gitlab. Navigate to "Web Hooks" section and create a new hook from previously copied url.

Copy deploy key from Magnum CI project integration screen from Step 2 textfield and navigate to "Deploy Keys" section. Paste key contents and hit "Create". 

You're done. Next step would be testing a web hook if you have any commits in the repository, or by simply pushing a new code update to the repository. 

How it Works

Basically, Magnum CI works pretty much with anything that supports git/mercurial over SSH. It allocates SSH keys pair for each project. So if you're rolling your own Gitlab setup it will work as long as there is access to the server from outside. Every time you do code push, Magnum CI will receive a web hook payload with commit details and will trigger a new build by cloning repository and checking out specified code revision. 

Security

Codebase, database content or anything else from repository is not being stored after build execution is complete. Builds are executed in isolated environment that is permanently destroyed after completion. Repository code is never being accessed by any crew member without a written permission and only in cases of troubleshooting. For any questions hit [email protected]

Features

Unlimited private projects

Unlimited builds

Unlimited collaborators

Build execution is limited by 30 minutes

Deep build customizations

Automatic code dependencies checks

1GB RAM per build

Languages: Ruby, Node.js, Go, PHP, Python

Databases: PostgreSQL, MySQL, MongoDB, Redis, Memcached, ElasticSearch, Beanstalk

Got interested? Signup for Magnum CI today!

[magnum-ci]

New splash page

For a quite while (or for the whole time to be exact) Magnum CI never had a publicly facing interface. Nothing to look at, nothing to check out. All the good stuff is hidden behind login page. Well, not any more! New landing page has been rolled out! 

Check it out: https://magnum-ci.com/

[magnum-ci]

Build badges and dependencies status

Magnum CI is getting better and better with every new release. Today we rolled out a few new features that will help to improve the overall project codebase quality. 

Build Badges

Build coverage and dependencies status badges are the new addition to the build details interface. It gives you a quick overview on how your project's code is covered and its dependencies status. OpenSource moves fast and every day brings more updates to popular libraries. Magnum CI will help you keep your codebase up to date. 

Dependencies Status

Every time you push code (Ruby or Node.js) Magnum CI worker will evaluate dependencies status and generate a detailed report that you can view by clicking on "dependencies" badge. 

Email Alerts

Too busy to check website for updates? No worries, Magnum CI will include coverage and dependencies status alerts in build email notifications:

Dont need code coverage or dependencies? Simply disable unwanted features in project settings:

Stay tuned for more updates!

[magnum-ci]

Code Coverage for Ruby Projects

Code coverage is a measure used in software testing. It describes the degree to which the source code of a program has been tested. The goal is to highlight untested or uncovered spots of the application.

With recent Magnum CI update its a new metric being collected when build execution is complete. Currently, its only available for Ruby projects that use SimpleCov. If your project is already using SimpleCov then code coverage metrics (percentage, LOC) will be collected automatically:

To get started with SimpleCov you need to add dependency to Gemfile:

group :test do gem 'simplecov', require: false end

Load and launch SimpleCov at the very top of your test/test_helper.rb (or spec_helper.rb, cucumber env.rb, or whatever your preferred test framework uses):

require 'simplecov' SimpleCov.start # Previous content of test helper now starts here

SimpleCov works with most of ruby test frameworks. Check documentation for details.

[magnum-ci]

Build Branches

Magnum CI now supports build branch configuration. By default build is triggered when code is pushed to any branch. In many cases you might want to limit builds to run on a specific list of branches or skip unwanted or experimental ones.

This could be done with new branch settings interface. Go you project build settings (Project -> Customize Build) and select rule to run builds.

[magnum-ci]

Build configuration customizations

Magnum CI offers a few ways to customize build configuration. You can either specify language version, environment variables and build steps using .magnum.yml file in your project root directory or via project build settings interface. 

Build configuration screen just got better today. Now you can select services your project needs with just a simple click.

For each project you can define language runtime version (Ruby, Node.js, Go, Python) and services that'll be started. PostgreSQL, MySQL and MongoDB are available by default. 

Services currently available on Magnum CI:

PostgreSQL

MySQL

MongoDB

Redis

Memcached

ElasticSearch

RabbitMQ

CouchDB

Xvfb

If you like to use .magnum.yml config, here is an example on how to start services (example ruby project):

ruby: 2.0.0 services: - redis-server - memcached - xvfb

[magnum-ci]

Hello World

Every project needs a blog to keep up with updates. This one will be for Magnum CI.