Real-world

Workflow for development, release and versioning with OSGi / bndtools: real-world challenges (continued)

Session Type: 
Standard Talk [25 minutes]
Speakers

Seeing the advantages of the OSGi modularity level, we want to introduce it into our daily workflow, based on Eclipse and the bndtools plugin.
In this talk we concentrate on the modularity level, independent of whether the service layer is used or not.

Initial requirements for our research group at Siemens, Corporate Technology include:
- integration of OSGi with the currently-used VCS (subversion, hg, git)
- integration of OSGi with our Jenkins CI server
- automated creation of deployable applications, which might include a collection of artifacts, start scripts, installers

Schedule info

Status: 
Accepted

Audience

Track: 
OSGi
Experience level: 
Intermediate

Desktop, Web and Mobile: Learn one get two for free

Session Type: 
Standard Talk [25 minutes]
Speakers

The frameworks of the Eclipse platform make it possible to use the same code base for desktop, web and mobile clients. This talk will tell you how our product OTIS (Oil Trading and Information System) evolved from a single-plugin RCP application into a multi-plugin RCP, RAP and Tabris application. At MEKO|S we have a small development team. It's a big advantage of having to learn only one framework to use for all three types of applications. We only have to write the code for a new feature once and it can be used on all three platforms immediately.

Schedule info

Room: 
Schubartsaal
Status: 
Accepted

Audience

Track: 
Building Industry Solutions
Experience level: 
Intermediate

Workflow for development, release and versioning with OSGi / bndtools: real-world challenges

Session Type: 
Standard Talk [25 minutes]
Speakers

Seeing the advantages of the OSGi modularity level, we want to introduce it into our daily workflow, based on Eclipse and the bndtools plugin.
In this talk we concentrate on the modularity level, independent of whether the service layer is used or not.

Initial requirements for our research group at Siemens, Corporate Technology include:
- integration of OSGi with the currently-used VCS (subversion, hg, git)
- integration of OSGi with our Jenkins CI server
- automated creation of deployable applications, which might include a collection of artifacts, start scripts, installers
- workflow easy of use for developers
- meaningful bundle/package versions

As this process proved less straightforward than one might expect, we present the challenges we encountered, such as:
- consistent versioning of bundles - both the conventions and the tooling support
- internal bundle release for the other developers
- reproducible deployment artifacts for external customers
- partial checkouts: checkout from a VCS repository only the projects relevant for the current developer task, without all the required dependencies (both third party and intra-project dependencies)
- usage of remote OBRs with mandatory authorization
- heterogeneous development OSs (windows, linux)

In this talk we document our quest for a practical workflow: the relevant use cases, the analyzed solutions, the various criteria that came into play and, finally, the chosen solution for our team.

Schedule info

Status: 
Accepted

Audience

Track: 
OSGi
Experience level: 
Intermediate

Copyright © 2012 The Eclipse Foundation. All Rights Reserved.