February 2016 Summaries

Semaphore has enhanced its interaction with Bitbucket repositories following the latest updates to the Bitbucket API, improving continuous integration and deployment workflows. The integration now sends real-time commit status updates directly to the Bitbucket UI, allowing users to see when it's safe to merge changes without leaving the platform. Additionally, branches are automatically deleted on Semaphore when a pull request is closed on Bitbucket or when remote branches are deleted from the command line, streamlining branch management. Enhancements have also been made to Semaphore's project setup interface, providing better differentiation of repositories with admin access and grouping them by teams. Furthermore, Semaphore's Heroku add-on now supports Bitbucket projects, allowing users who manage tools through Heroku to integrate Bitbucket projects seamlessly alongside GitHub.

Scheduled for February 23rd, 2016, the upcoming platform update includes various software updates such as Bundler to version 1.11.2, Cassandra to 2.2.5, and ChromeDriver to 2.21. Elixir, Git, Java, MySQL, Node.js, PHP, and RethinkDB also receive updates, with significant security enhancements in Node.js and a notable addition of new Node.js versions 5.6.0 and 4.3.0 to the platform. Users are encouraged to try these updates by switching to the Ubuntu 14.04 LTS v1602 release candidate platform and providing feedback to help address potential issues and improve the platform. Additionally, PhantomJS 2.2.1 has been added, and users can test these changes by adjusting their setup commands during the release candidate period, which ends on the update's release date, with further details available in the platform changelog.

Semaphore scheduled a planned maintenance on Sunday, February 14th, 2016, beginning at 10am UTC, which included a database migration and was expected to last up to four hours. The maintenance aimed to improve infrastructure and enhance service quality. Updates were promised to be provided on Semaphore's Twitter account during the downtime, and users were invited to join a discussion about the maintenance on Discord.