We've switched the default OS for new Linux projects to Ubuntu 14.04 Trusty. 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.
feature • Rebuild from the builds dashboard
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 Discuss!
feature • Browser Notifications
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 Post.
feature • Option to auto-cancel redundant builds
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.
feature • Email UI Improvement
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 Discuss!
feature • Email Alerts for OS X Overages
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%.
feature • SSH functionality on OS X builds
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 users were noticing a loading spinner rather than the test results under the “Test Summary” section.
We have fixed the issue where users were unable to see commit information for builds triggered via API.
bugfix • Email address getting switched issue
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.
We have fixed the issue where users were unable to click “Follow” or “Unfollow” button under “Project Settings”.
You would now be able to select email notifications for each individual GitHub organization. Please navigate to the following link to update your notification settings.
feature • Ability to select “Build Environment”
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 added functionality to retrieve build artifacts for the latest completed, successful, or failed build on a given project branch. Read more about it here.
feature • Python symlink behavior change
We have updated our handling of Python virtual environment. 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 firstname.lastname@example.org.
feature • New environment variables
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 Environment Variables section of our documentation.
feature • Detecting GitHub SSH Key Audits
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 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 here.
feature • Announcing our new Insights feature
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 here, and look for the new button on the navigation.
'Triggered By' field on build output page will show `API` if the build was triggered via API.
We now release your parallel containers at the beginning of the deploy phase, so that you can use them for other builds.
Tag build will work as expected even if your previous commit messages have [ci skip] in them.
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
You can now scoll to the bottom of the page by hitting the down-arrow button on the build output page.
Detailed commit message that shows on hover on build page was fixed to not be cropped.
Pull request entries in the branch list (created when building pull requests from forks that are not set up on circle) now get cleaned up when pull requests are closed
feature • More flexible SSH builds
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 the documentation for details on what configuration information is denied to these builds for security reasons.
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/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/configuration/#cache-directories for more information.
Circle will now automatically re-run iOS tests if the simulator fails to launch. This allows us to work around known issues with the iOS simulator that have been causing builds to fail.
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.
If your build produced test metadata, we will now include the specific failing test names in chatroom and email notifications, so you more immediately know what to act on.
Explain how to get CircleCI builds working again after turning on third-party access restrictions for GitHub organizations
Better support for showing all the useful information for some junit formatter behavior, including that of xcode
feature • Failure messages in the failed test list
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/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 https://github.com/circleci/frontend.
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.
Config overrides in the project settings page are now monospaced inputs instead of using variable-width fonts.
The sidebar UI used to show cancelled builds as failures in the sidebar. Now it shows up as cancelled instead.
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 X-forwarding over SSH, 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.
We now support building pull requests from forks. It's still experimental so you'll need to enable it from Project settings > Experimental settings page
Add detailed instructions for caching SDK components and testing against the Android emulator.
update • Update the simplecov warning.
simplecov 0.9 was released, which no longer gives erroneous exit codes, 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 Project settings > Checkout SSH keys 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: https://developer.github.com/changes/2014-03-27-combined-status-api/
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 interact with browser tests as they run on CircleCI.
We've added an experimental API for creating parameterized builds. This API lets you pass environment variables into your build environment which you can then use to customize your build steps, e.g. nightly builds.
We have added Ruby 2.1.2 and 2.0.0-p481, JRuby-1.7.12, Rubinius 2.2.6, PHP 5.5.11, and Node.js 0.10.28. We also updated Heroku toolbelt to 3.7.3.
feature • We added paging to the build dashboards
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 recent builds API which is also available for scripting goodness.
feature • Fork-specific deployments
If you do continuous deployment of a project with multiple forks, you can now specify which fork of the project a deployment subsection applies to.