tuning github for spl development branching models and operations for product engineers oscar díaz...

Tuning Github for SPL development

Branching models and operations for product engineers

Oscar DíazUniversity of the Basque Country

ONEKIN Research GroupSan Sebastian, Spain

Leticia MontalvilloUniversity of the Basque Country

ONEKIN Research GroupSan Sebastian, Spain

SPLC’15 Nashville 2015, TN

Onekin Reserch Group 2

SPL SettingEvolving SPLsFeature-Oriented SPLs

Onekin Research Group 3

SPL Scope of reuse

Deestral&Bosch2005: Product Derivation in Software Product Families: A Case Study


Domain engineering development

Feature-Oriented SPLsFeature implementation =


Application engineering development

1. Get initial feature configuration

2. Customization

3. Assemble

Customized core asset

Brand newasset


It looks like two kinds of repositories exist

…

1 Core_Asset_Repository + N Product_Repository


Where do we keep the assets?

VCSs


Github highlights

More than 10 million of users

More than 24 million of repositories

Web-based Git Repository hosting service

Popular for collaborative development

"GitHub Press Info". github.com. Github. Retrieved 2015-07-23

https://github.com/about/press


?A Look into a Github Repository

Repository Owner

Repository Name

User logged

Default branch

Source Code


?A look into a Forked Repository

Cloned Source Code

All branches & commits

A link to the “original” repository

My account


How do both repositories look like on Github?

…


How does a core asset repository look like in Github?

Domain developer

Features implementation

Core asset repository name


How does a Product Repository look like in Github?

Application developer Product repository name

Product assets


The problemThe sync Challenge


?Now, let’s have a show of hands …


Should a product repository be obtained after a core asset repository?


Should reusable core asset updates be propagated to existing products?


Should product specific customizations be upgraded as core assets?


If you answered “Yes” to any ….There is a sync challenge


The problem: The Sync Challenge

The sync challenge implies to:

1. Create product repositories from core asset repositories along a feature configuration

2. Update product assets with newer versions available at core asset repository

3. Feedback product customizations from product repository to core asset repository


Does Github support the sync challenge?

Fork & pull Request operate at high granularity. We want them at feature level

Fork Granularity: at repository level (branches and commit history) What if we only want a subset of the features?

Pull Requests Granularity: at branch level ( branches hold a project’s

snapshot) What if we only want the changes related to a given feature to

be propagated? What happens if my product is not reusing that feature?


How can we tune Github to support engineers on the sync challenge?


The solutionGitLine: a Firefox plug-in that extends Github functionality


Github operations for the sync challenge3 OPERATIONS FOR PRODUCT ENGINEERS

1. Create product repositories from Core Asset repositories along a core asset configuration

PRODUCT FORK

2. Update product assets with newer versions from core asset repository

UPDATE PROPAGATION

3. Feedback product specific assets from product repositories to core asset repository

FEEDBACK PROPAGATION


Product Fork operation

Product Fork ( User_Account X Core_Asset_Repository X Configuration_of_core_assets ) :: Product_Repository


Product Fork: Accesing the Core Asset Repository


Product Fork: Getting the feature configuration

Product Fork Update Propagation Feedback Propagation

Feature selection Configuration steps


Behind the scenes …

… GitLine creates a new product repositoryinitialized only with the core assets of the selected features: deleting not wanted assets & branches & setting up the branching model for the user



Product Fork: A new Product Repository



Update Propagation Operation

Update Propagation ( User_Account X Core_Asset_Repository X Product_Repository):: Pull_Request


Core Asset Repository has new updates

Product Fork

Update Propagation

Feedback Propagation


Update Propagation: Enacting the operation



… GitLine is accessing the core asset repositoryand checks where there are newer feature versions that my product is reusing & brings them into a product’s repository dedicated branch

Product Fork

Update Propagation



Update Propagation pulling new versions of Core Assets


Opening the update request: Diff view

Product Fork

Update Propagation




Feedback Propagation ( User_Account X Product_Repository X customization_branch X Core_Asset_Repository ):: Pull_Request


There is a new product specific asset

Product specific customizationWe want to feedback


Selecting the product specific asset



… GitLine traverses the branch history to cherry-pick only the changes that occurred under that branch and propose them as feedback for a core asset repository feature.


A new Feedback Pull Requestin the Core Asset Repository


Opening the feedback request: Diff view

Product Fork Update Propagation

Feedback PropagationComparing PlayMovie Feature


Almost reaching the end…


What can you find in the paper?

Things I did not explained during the presentation:

A branching model for core asset repositories

A branching model for product repositories

The operational semantics for 3 sync repository operations


A branching model for Core Asset Repository

4 main type of branches.Branch-per-purpose style


A branching model for Product Repository

7 main type of branches.Branch-per-purpose style


What can you find in the Web?

A realization of these operations as a Firefox plug-in: GitLine

GitLine is freely-available as a GitHub project


https://github.com/letimome/GitLine

FORK & SEND PULL REQUEST


http://letimome.github.io/GitLine

ASK FOR A LIVE DEMO!!


Summary

ProblemSync DE & AE developments

ContributionBranching models for Core Asset & Product

RepositoryFormalization of three sync SPL operations

ValidationFeasibility: GitLine tool, Firefox plug-in for GitHub


Limitations and future lines

Evaluation of the branching model & operations with practitioners

GitLine depends on Github

Provide GitLine with different composition mechanisms

53Onekin Reserch Group

@

Contact us,[email protected]

Thanks for your attention!


Extra to illustrate operations in action …

55

Product Fork Operation

Onekin Research Group


Update Propagation

Enact update propagation…

Diff=




Diff=

Enact Feedback…

tuning github for spl development branching models and operations for product engineers oscar díaz...

Documents