Home / Companies / Semaphore / Blog / April 2014

April 2014 Summaries

4 posts from Semaphore

Filter
Month: Year:
Post Summaries Back to Blog
Semaphore has introduced a new API feature allowing users to trigger deployments directly through the API, simplifying the process with a straightforward curl command. This enhancement is accompanied by updates to the API documentation to reflect the new capabilities. Additionally, there have been updates to the server API response structures, with the latest specifications available in the documentation. Users are invited to join the discussion about this update on Semaphore's Discord channel.
Apr 30, 2014 91 words in the original blog post.
The platform update scheduled for May 5, 2014, includes several significant software upgrades, such as Bundler to version 1.6.2, which enhances Gemfile resolving speed by tenfold, and Firefox to version 29, necessitating a bundle update for selenium-webdriver in many projects. ElasticSearch now moves to version 1.1.1, while MySQL is upgraded to version 5.6, bringing notable performance and stability improvements. To prevent errors related to the outdated mysql gem cache, caches will be removed for all affected projects, and users encountering issues are advised to adjust their build commands accordingly. A comprehensive list of changes is provided in the platform changelog, and users are invited to discuss the update on Discord.
Apr 29, 2014 181 words in the original blog post.
A critical security vulnerability known as Heartbleed was discovered in OpenSSL on April 7th, allowing unauthorized access to 64k chunks of memory without leaving traces in server logs. This prompted Semaphore to upgrade OpenSSL to a secure version and replace SSL certificates across their infrastructure to prevent future attacks. Although no harm was detected, Semaphore advised users to change their passwords and reset API tokens, providing a straightforward method to do so in their project settings. Additionally, they recommended enabling GitHub's two-factor authentication and resetting OAuth tokens, which was applied to all users. For those deploying to Heroku, users were informed that after changing their Heroku password, a new API token needs to be set in the server settings. Semaphore offered support through their app and email for any further concerns and invited users to discuss the issue on Discord.
Apr 11, 2014 345 words in the original blog post.
Semaphore has introduced an innovative reporting feature that combines modern technology with a nostalgic touch by sending full test reports printed in dot-matrix font directly to Pro customers' addresses. This service, set to begin deliveries today after 2 PM UTC, requires users to add their mailing address in account settings to enable it. The reports will arrive in water-resistant packaging to ensure their protection against weather conditions. This initiative aims to pioneer a new era in continuous integration (CI) communication, reflecting Semaphore's commitment to combining cutting-edge technology with unique customer interaction methods.
Apr 01, 2014 155 words in the original blog post.