Improve CI to support independent development teams

Description

Our current trunk-based development approach has been working well for us with some notable exceptions:

  • Code lands in master sometimes half-baked (before any code-review)

  • Some devs utilize branches to keep master cleaner and experiment, to their detriment as the build server isn't able to provide them, or their reviewers feedback on

    • if it builds

    • if it passes code-quality

    • if it breaks contract tests

  • It doesn't support pull-requests which is the recommended approach for external developers

Overall we'd like enhance our CI server to support building and providing feedback on branches while also retaining our trunk-based development model.

In this epic we'll:

  • Improve our CI server to build branches of each component

  • Evaluate and introduce feature flags so that branches are short-lived.

  • Harmonize our process for internal and external developers

  • Update our documentation to better inform contributors what the commit, review and branching process is

  • Update the development community with how this process works and show them the steps.

This epic is not to achieve branching for release which is covered by OLMIS-4115.

100% Done
Loading...

is blocked by

QAlity Plus - Test Management

Checklists

Activity

Mary Jo Kochendorfer 
September 21, 2018 at 10:03 PM

are we planning to wrap these up for 3.5?

Josh Zamor 
August 6, 2018 at 9:26 PM

This is almost done, however there are a few items left before we can declare this. After the 3.4 release we should put the effort in to complete this. This doesn't hold back any release.

Mary Jo Kochendorfer 
June 21, 2018 at 8:52 PM

, we are planning the 3.4 release. In your mind, once all the 16 tickets are completed -> the goals listed are achieved? Or are there still more tickets to be added to this epic?
FYI

Sebastian Brudziński 
May 24, 2018 at 12:09 PM

We will also need a ticket to figure out how to handle Sonar builds on branches. It would be great to have the Sonar analysis there, but the results should not impact the projects and probably shouldn't notify on failed quality gates on Slack.

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Fix versions

Priority

Epic Name

Time Assistant

Created April 17, 2018 at 5:15 AM
Updated December 3, 2018 at 5:12 PM
Resolved October 22, 2018 at 9:12 PM