AlloyCI v0.5 released!

Major changes ahead

Patricio Cano
Mar 30, 2018 · 4 min read
Image for post
Image for post
Photo by Kristopher Roller on Unsplash

This week marks the first year anniversary since the first commit of AlloyCI, and to celebrate it, we are releasing the v0.5 version. With it we get closer to the much coveted v1.0 release, when AlloyCI will be fully ready (and fully supported) for production environments.

This version of AlloyCI comes with a wide variety of changes. The most noticeable being the new and improved design, and support for GitHub Enterprise.

Design Changes

We decided it was time for a change. The new design feels clean, modern, and is easy to look at.

Some elements remained, like the use of cards to represent the projects, and the use of panels to separate related information:

Image for post
Image for post
New projects view

The use of colors to represent statuses also stayed, but with a new pantone:

Image for post
Image for post
New pipelines view (single project)

The builds view was completely reworked to better illustrate the different stages of a pipeline, and to give a quick overview of the status of each build within that pipeline:

Image for post
Image for post
New builds view (single pipeline)

The single build view also suffered major changes. Now each build has its own page, with dedicated, always visible information about the build on an aside to the left, and the entire build output (which will automatically update if the build is running) to the the right.

Image for post
Image for post
New build view

The project settings view did not change that much, but it still looks cleaner and now groups related information more tightly:

Image for post
Image for post
Project settings view

New features

GitHub Enterprise

Builds

Build Artifacts

  • Artifacts can be managed and downloaded from the build view
  • Expired artifacts will be pruned once a day (or at any configurable interval)
  • Artifacts can be kept forever, if the user chooses to

Bug fixes

  • When cancelling a pipeline, all builds were marked as cancelled, now only builds that are either created, running, or pending are updated.
  • After the upgrade to Guardian 1.0, it became impossible to add another authentication method to an existing user. This has been fixed.

This is pretty much it for this release. The roadmap ahead includes adding S3 bucket support for build artifacts, so that they can be uploaded to services like AmazonS3, or Digital Ocean Spaces. With this support implemented, it will become possible for AlloyCI installations that are hosted on Heroku to also make use of build artifacts, something that is not possible right now.

Until next time! ❤️

HackerNoon.com

#BlackLivesMatter

Sign up for Get Better Tech Emails via HackerNoon.com

By HackerNoon.com

how hackers start their afternoons. the real shit is on hackernoon.com. Take a look

By signing up, you will create a Medium account if you don’t already have one. Review our Privacy Policy for more information about our privacy practices.

Check your inbox
Medium sent you an email at to complete your subscription.

Patricio Cano

Written by

Senior Software Engineer @ Panda Strike — Living in Guadalajara 🇲🇽

HackerNoon.com

Elijah McClain, George Floyd, Eric Garner, Breonna Taylor, Ahmaud Arbery, Michael Brown, Oscar Grant, Atatiana Jefferson, Tamir Rice, Bettie Jones, Botham Jean

Patricio Cano

Written by

Senior Software Engineer @ Panda Strike — Living in Guadalajara 🇲🇽

HackerNoon.com

Elijah McClain, George Floyd, Eric Garner, Breonna Taylor, Ahmaud Arbery, Michael Brown, Oscar Grant, Atatiana Jefferson, Tamir Rice, Bettie Jones, Botham Jean

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app