November 2013 Summaries

A new version of the branches page has been launched, featuring a design that allows users to view ongoing builds for each branch. Users can also prioritize specific branches, such as the master branch, by using a star button to keep them at the top of the list. Feedback on the new design is encouraged.

The Multiple Project Summary Reporting Standard, also known as cctray.xml or cc.xml, is an XML feed format initially developed by ThoughtWorks for CruiseControl.net to provide an RSS-like continuous integration (CI) service build status. This format has since been adopted by various CI services and can be accessed on platforms like Buildbox by using a specific URL format that includes the account name and API key, which can be obtained from the user's account settings. Users can customize the feed to monitor specific branches by appending the branch name to the URL. The feed is compatible with several desktop clients, including CCMenu for OS X and CCTray for Windows, allowing users to easily track the status of their builds.

A new feature has been introduced to improve the user experience of monitoring long-running builds in a web browser. Now, the browser's icon will change to reflect the build's status, providing users with a visual indication of when the build finishes or its status changes, making the process more convenient and efficient.

Buildbox allows users to bypass unnecessary builds by adding "[ci skip]" to commit messages, particularly useful for non-essential changes like documentation edits. This feature ensures that such commits are neither built nor stored in the build history, streamlining the development process by focusing resources on more critical changes. In practice, this command can be implemented directly within platforms like GitHub.

Buildbox now allows users to upload files associated with any build they run, which is particularly beneficial for generating documentation or code coverage analysis for projects. Users can specify which artifacts to upload by defining a directory glob on the Pipeline Settings page, with guidance available in the Ruby documentation. To begin uploading artifacts, users must update to the latest version of the agent (0.6), with release notes and upgrade instructions available on GitHub.

Buildbox has announced the launch of a new blog alongside the news that they are now officially out of their Beta phase, allowing users to sign up without needing an invitation. Pricing information has been made available, and the company expressed gratitude to those who participated during the Beta phase, highlighting the value of their contributions and feedback. Buildbox looks forward to facilitating users' builds as part of this new chapter.