July 2014 Summaries

"Developer Interview" is a series on the Semaphore blog that showcases insights from developers at companies using Semaphore, starting with Agworld, an agriculture tech startup from Australia. Agworld provides software solutions for farm management, enabling farmers, agronomists, and contractors to plan operations, manage records, and share information through web and mobile apps. The company is dedicated to making global food production profitable and sustainable, tackling complex agricultural challenges. Their development process involves direct customer interaction, field trips, and collaboration between product managers, developers, and designers using Scrum and frequent releases. Agworld emphasizes comprehensive test coverage, peer reviews, and utilizes tools like RSpec, Cucumber, and Semaphore for continuous integration. Key programming realizations include the importance of code clarity and understanding problems before coding. Semaphore's integration aids Agworld by streamlining builds, managing multiple branches, and reducing configuration efforts across diverse projects.

Semaphore has introduced a new feature called Organizations, designed to streamline project management and permission systems within companies, allowing for scalable continuous integration as operations grow. Organizations enable users to consolidate projects under a single billing account, offering fine-grained permissions that allow different levels of access and control for team members. This feature facilitates transferring projects from personal accounts to organizational accounts, with teams being granted specific permission sets such as Access, Edit, and Admin. Alongside Organizations, Semaphore has updated its pricing structure with options for personal and organization plans, featuring no project limits and discounts for higher plans, and introducing annual payment options for simplification and savings. The development aims to enhance user-centricity and scalability, reflecting Semaphore's commitment to supporting users in delivering exceptional software.

Semaphore has introduced a more flexible approach to managing project collaborators, moving away from a system that required collaborators to be directly mapped from GitHub repositories. Previously, access to a Semaphore project necessitated having a GitHub account and being a collaborator on the corresponding repository, which posed limitations when users wanted to join or leave projects. The new system allows project owners to invite collaborators via email, irrespective of their status on GitHub, enhancing flexibility and enabling easier access for teams like QA. Existing users are automatically added to projects, while new users receive an invitation email, and anyone can now exit a project with a single click, streamlining the workflow and improving user experience.

In a blog post series inspired by a Stack Overflow thread, the concept of a "local hero" is explored, which refers to test cases that run successfully in a specific development environment but fail elsewhere due to dependencies on local configurations. Such issues often arise from differences in settings between a developer's machine and a Continuous Integration (CI) system, with screen resolution being a notable example, as seen in Semaphore's historical resolution settings causing test failures in Selenium. Another challenge is hidden dependencies, such as when tests rely on pre-existing data that isn't automatically populated, leading to failures that provide little context for developers. To address these problems, the post emphasizes the importance of automating database state management in tests to avoid manual interventions and maintain a consistent testing environment, recommending tools like 'database_cleaner' for Ruby and similar packages for Node.js.

Scheduled for July 7, 2014, the platform update introduces several software upgrades, including Elasticsearch 1.2.1 and NodeJS versions 0.8.27 and 0.10.29, which address an OpenSSL vulnerability and introduce a UTF-8 change. The update also includes JRuby 1.7.13, Firefox 30, PHP versions 5.4.30 and 5.5.14, and Bundler 1.6.3. Additionally, the AWS CLI is now part of the platform. Projects using selenium-webdriver may need to update due to the new Firefox version, with issues reportable via the provided link. A full change log is available, and discussions about the update can take place on their Discord channel.