English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Continuous Integration (CI) implies that a whole developer team workstogether on the mainline of a software project. CI systems automate the buildsof a software. Sometimes a developer checks in code, which breaks the build. Abroken build might not be a problem by itself, but it has the potential todisrupt co-workers, hence it affects the performance of the team. In thisstudy, we investigate the interplay between nonfunctional requirements (NFRs)and builds statuses from 1,283 software projects. We found significantdifferences among NFRs related-builds statuses. Thus, tools can be proposed toimprove CI with focus on new ways to prevent failures into CI, specially forefficiency and usability related builds. Also, the time required to put abroken build back on track indicates a bimodal distribution along all NFRs,with higher peaks within a day and lower peaks in six weeks. Our resultssuggest that more planned schedule for maintainability for Ruby, and forfunctionality and reliability for Java would decrease delays related to brokenbuilds.

On the Interplay between Non-Functional Requirements and Builds on Continuous Integration