CircleCI offers the ability to link directly to build output steps. We've now extended this feature into build email notifications. You should now see a clickable 'Failing Command' on (failed) build notification emails which will open the build page to the failed command in your build output.
We've switched the default OS for new Linux projects to <a href="https://circleci.com/docs/1.0/build-image-trusty/">Ubuntu 14.04 Trusty</a>. Please note that the change applies only to new projects added to CircleCI from today on. If you wish to change the OS of your existing projects, you can do so from the “Build Environment” tab under Build Settings on your project's settings page.
We have added functionality to rebuild failed and timedout builds directly from circleci.com/dashboard. This feature is enabled automatically. If you have any feedback regarding rebuilding or the dashboard, please feel free to post on <a href="https://discuss.circleci.com">Discuss</a>!
We have begun to roll out a new feature that enables browser notifications for finished builds. If this feature is turned on by a user for a given browser, the user will receive browser notification when respective builds have finished. To learn more or to provide feedback, check out this Discuss <a href="https://discuss.circleci.com/t/browser-notifications-linked-from-changelog/5558">Post</a>.
We have added a new guide to CircleCI Docs that provides an example of how to deploy an app or static site to Amazon S3. Find it <a href="https://circleci.com/docs/1.0/continuous-deployment-with-amazon-s3/">here</a>.
We have added functionality to auto-cancel redundant builds. If this feature is turned on, we will automatically cancel any queued or running builds on a branch when a newer build is triggered on that same branch. To enable this feature you can navigate to “Advanced Settings” for your project and enable the “Auto-cancel builds” option.
We have added functionality to only run builds when a pull request is open. To enable this functionality you can navigate to “Advanced Settings” for your project and enable the “Only build pull requests” option.
We have finished a series of changes to our build results email templates (i.e., emails sent upon build completion). 1) We have moved all emails to one consistent pattern that should improve clarity and legibility. 2) When available, we now add a value identifying the user that triggered the build called 'Triggered By'. 3) We have optimized the width on the build results output to accomodate narrower viewports (e.g., emails on mobile screens). If you have any feedback regarding notifications, please feel free to post on <a href="https://discuss.circleci.com">Discuss</a>!
In response to an uptick in Error Code 65 issues for OS X customer, we no longer charge minutes for builds that fail this way and we now auto-retry such failures up to 3x. Read more about it <a href="https://discuss.circleci.com/t/xcode-exit-code-65/4284">here</a>
This additional feature pertains to customers using OS X plans. Prior to this, we provided only alerts in-app regarding approaching and passing minute limits. With this change, we now trigger an email to a plan's billing-email when usage for a given billing period passes 80% and again when it passes 95%.
This change enables users to always see the SSH button on OS X builds. This brings OS X builds to parity with Linux builds in this regard. Users have found that one of the the best ways to troubleshoot problems is to SSH into a running or finished build to look at log files, running processes, and more.
You can now override the channel your Slack notifications are sent to directly in the Chat Notification settings of your project. This is particularly handy for larger organizations where dev teams have a hard time getting new Slack webhook URLs provisioned.
We have fixed the issue where user email addresses were getting switched on “Notification” under “Account Settings”. There was problem in our Github user information synch cron job for a period of 10 days where we overwrote the user's preferences using Github's default email. This was a result of unexpected interaction of two seemingly unrelated areas. We really apologize for all the inconvenience it has caused.
You would now be able to select email notifications for each individual GitHub organization. Please navigate to the following <a href="https://circleci.com/account/notifications">link</a> to update your notification settings.
We have added a new section called “Build Environment” under “Project Settings”. You can now select between Ubuntu 12.04 or Ubuntu 14.04 images. If you are building an OS X project, you can enable it under the “Build OS X project” section on “Build Environment” settings page.
We have fixed a number of issues contributing to build pages rendering browsers unresponsive. We are currently displaying the first 400,000 lines of console output and provide you with the ability to download your full log.
We have added functionality to retrieve build artifacts for the latest completed, successful, or failed build on a given project branch. Read more about it <a href="https://circleci.com/docs/1.0/api/#build-artifacts">here</a>.
We now display JUnit format XML output parse errors under the 'Test Summary' tab. If the build generates an invalid XML we will display a warning with filename and the line number where the error occurred.
We now support both annotated and lightweight tags. You can now supply 'tag' as a key in the JSON body for POST request. Read more about it <a href="https://circleci.com/docs/1.0/api/#new-build">here</a>.
We have updated our handling of Python <a href="https://docs.python.org/3/library/venv.html">virtual environment</a>. Previously, we created a symlink in your project root to the system 'venv' directory. We will no longer do this for projects created after March 11, 2016. If you need the new defaults to be overridden per-project or per-org, please email us at email@example.com.
We have added logic to restrict any non-admin Github users from modifying project settings. If you would like to enable this feature for your organization, or specific projects within your organization, please email us at firstname.lastname@example.org.
We have added 2 new environment variables, `CIRCLE_REPOSITORY_URL` and `CIRCLE_BUILD_URL`. These variables are available in your builds and give easy access to the URL of your repo on GitHub and the URL of the build on CircleCI. This very handy for adding metadata to automated deployments. You can read more about our environment variables in the <a href="https://circleci.com/docs/1.0/environment-variables/#build-details">Environment Variables</a> section of our documentation.
You can now view the slowest test under the 'Test Results' tab after your build is successful. Need help setting up test results tab? View our test metadata collection <a href="https://circleci.com/docs/1.0/test-metadata/#automatic-test-metadata-collection/">doc</a>.
If you have not built a project for a few months, GitHub will sometimes ask you to verify the credentials that CircleCI uses to checkout your project. GitHub does this to keep your account safe. CircleCI will now automatically detect when your SSH keys require verificitation and will put a link on your build page to the GitHub page where you can re-authorize CircleCI's deployment keys.
We are excited to announce public beta for our new look. Starting today all our users will have the ability to opt-in to the new design with the click of a button. Read more about it <a href="https://circleci.com/blog/learn-about-our-new-ui-now-in-public-beta/">here</a>.
We are actively working on our mobile iOS offering to prepare it for general release. For our beta users Xcode 7.1.1 is now available for all iOS builds. In addition, Fastlane and Carthage are now installed by default. Cocoapods and xctool have also been updated to the latest versions. Users in the current iOS beta should see more information <a href="https://discuss.circleci.com/t/new-ios-build-image-xcode-7-1-1-fastlane-and-more/611">here</a>.
Available for all paid and open source customers, Insights is an interactive visual dashboard enabling you to see and understand all your builds for CircleCI at a glance. Read more about it <a href="https://circleci.com/blog/announcing-circleci-insights-helping-you-understand-your-builds/">here</a>, and look for the new button on the navigation.
You can now link to different sections on the build output page (and can safely send someone the URL you are viewing to link directly to that section). The anchors are: #commits, #config, #usage-queue, #tests, #artifacts, #build-parameters, #ssh-info
The Add Projects page is now faster to load and won't bog down if you have a large number of projects. Also, collaborators will now have an easier time following your projects, and we fixed a few annoying UI quirks.
Now multiple people can ssh to the same build to collaborate on debugging, and you can ssh to a build that is already running instead of having to start a new one. Just click the "Enable SSH for this build" button in the "Debug via SSH" tab.
Enables automatic safe builds of fork PRs for public repositories (you can see if tests pass before merging without the fork-er using CircleCI.) See <a href="https://circleci.com/docs/1.0/fork-pr-builds/">the documentation</a> for details on what configuration information is denied to these builds for security reasons.
We have added a new notification system to CircleCI to let you know when we update the changelog. When there is new changelog entry, you will see an icon to highlight the Changelog link on the left nav.
We inaugurated a new circle.yml 'experimental:' section with the ability to specify exactly which branches you should receive build notifications from in your chat channels - see https://circleci.com/docs/1.0/configuration/#per-branch-notifications for more information.
At CircleCI we are committed to performance, and we are always trying to find ways to run your builds faster. Today we have added the ability to cache dependencies when building on iOS. By default we will automatically cache any CocoaPods or Ruby Gems that are downloaded during your build. You can also cache any other build dependencies that you need, just like you can on Linux builds - see https://circleci.com/docs/1.0/configuration/#cache-directories for more information.
We've significantly improved support for Android builds -- we now pre-install more tools and packages, so setting up new projects should be quicker and easier. Check out our <a href="https://circleci.com/docs/1.0/android/">documentation</a> for details.
We have changed the default steps that we take to build an iOS project. We have split the compilation phase and the testing phase in two. This improves the stability when running tests in the iOS simulator.
We've extended the default timeout for build commands to 10 minutes where the command produces no output. Longer running quiet commands now have more breathing room to complete without needing to modify circle.yml.
During the iOS beta we have noticed that XCode can sometimes fail unexpectedly. When this happens CircleCI will now automatically capture relevant XCode log files and store them with your build's artifacts.
If your build produced <a href="https://circleci.com/docs/1.0/test-metadata/">test metadata</a>, we will now include the specific failing test names in chatroom and email notifications, so you more immediately know what to act on.
You can now access the full failure message for each test from the list in the failures tab. There's variation in exactly how test runners output this information, so let us know if we're not showing you quite what you'd like to see.
Lots of small improvements to the container image: added JRuby 1.7.16, pypy versions 2.3.1 and 2.4.0, and php 5.6; updated the node.js default to v0.10, Java 8 to build 25 (up from build 20), and lxc to 1.0.6.
Added the CI_PULL_REQUEST and CI_PULL_REQUESTS environment variables to assist external services wanting to know more build information, and added documentation in resources/assets/docs/1.0/environment-variables.md. This is populating information similar to what coveralls does.
We rewrote our frontend in React.js/Om. We've seen a nice bump in stability -- React's component lifecycle events have made memory leaks a thing of the past. It's now safe to leave a tab open overnight! The code is also open-source: please check it out and contribute at <a href="https://github.com/circleci/frontend">https://github.com/circleci/frontend</a>.
If you're using our inferred RSpec or Cucumber commands, we've added an experimental setting to collect structured test output. You can toggle it from the Project settings > Experimental page. We currently use the data to give you better parallelism splits and we provide an API to access the test data for a given build.
We've added PHP 5.5.15 and Ruby 1.9.2-p330 to the base image. We've also fixed a bug that was preventing <a href='https://circleci.com/docs/1.0/browser-debugging/#x11-forwarding-over-ssh'>X-forwarding over SSH</a>, which many of you use to debug webdriver tests.
Non-logged-in browsers of the site can now view OSS project dashboards and build pages. If you have an open source repo on GitHub, then you can enable public access to your build pages from the Project settings > Experimental page.
<a href='https://github.com/colszowka/simplecov/blob/master/CHANGELOG.md#bugfixes-1'>simplecov 0.9 was released, which no longer gives erroneous exit codes,</a> so new builds with fixed versions won't trigger warnings.
A long-standing bug caused us to check out using users' personal GitHub keys, instead of deploy keys, even for projects without a configured GitHub user. A small number of projects relied on this bad behavior: the fix is to specify a GitHub user for your projects, from the <strong>Project settings > Checkout SSH keys</strong> page.
Consumers of GitHub's commit status API will now see "ci/circleci" in the context field of the API response. You won't see any changes to the merge button on the Pull Request page until GitHub moves the feature out of preview mode. Read more about the Combined Status API on GitHub's blog: <a href="https://developer.github.com/changes/2014-03-27-combined-status-api/">https://developer.github.com/changes/2014-03-27-combined-status-api/</a>
Debugging Selenium browser tests can be a frustrating experience, especially when they're running on a remote machine. To help tighten the feedback loop, we've added support for connecting to the test container over VNC. With VNC, you can <a href="https://circleci.com/docs/1.0/browser-debugging/#interact-with-the-browser-over-vnc">interact with browser tests as they run on CircleCI</a>.
We've added an experimental API for creating <a href="https://circleci.com/docs/1.0/parameterized-builds/">parameterized builds</a>. This API lets you pass environment variables into your build environment which you can then use to customize your build steps, e.g. <a href="https://circleci.com/docs/1.0/nightly-builds/">nightly builds</a>.
We've added the much-requested feature of paging to the build dashboards. And not just on the frontend, behind the scenes we're using our recent addition of paging to the <a href="https://circleci.com/docs/1.0/api/#recent-builds">recent builds API</a> which is also available for scripting goodness.
If you do continuous deployment of a project with multiple forks, you can now <a href="https://circleci.com/docs/1.0/configuration/#deployment">specify which fork of the project a deployment subsection applies to</a>.