“Development cycle with GeneXus Server”

Presented By: Daniel Coellar

@dcoellar#GXSUMMIT

What is GeneXus Server?

#GXSUMMIT

GeneXus in the Cloud (Read only)

Source Control Repository (Team support)

Software Configuration Management (Versioning)

The Project

#GXSUMMIT

Barnes and Noble: TextAid

Meet the Team

#GXSUMMIT

Name: Laura Aguiar

Role: Project Manager

Name: Carlos Canessa

Role: Developer

1st Round – Send KB to Server

#GXSUMMIT

Send KB To Server

New KB from Server

Trunk

2nd Round – Commit & Update

#GXSUMMIT

Lock ModelCommitUpdate

Simple Update, no Merge, no Conflicts

2nd Round – Commit & Update

#GXSUMMIT

Without LocksCommitUpdate

Automatic Merge / manual conflict management

Commit

3rd Round – Branching

#GXSUMMIT

UpdateTrunk

Freeze

v1Branch

Updates to v1

3rd Round – Branching

#GXSUMMIT

Trunk

v1

Updates to v1

One KB, sync to all versions!

3rd Round – Branching

#GXSUMMIT

Trunk

v1

Updates to v1

Multiple KBs, sync to specific versions!

4th Round – Parallel Development

#GXSUMMIT

Trunk

v1

Updates to v1

Commit

Trunk

v1

Updates to v1 Update

Bring Changes

Commit

Bring Changes from specific Commit!

4th Round – Merge for QA

#GXSUMMIT

Trunk

v1

Updates to v1Trunk

v1

Updates to v1 Update

Merge

Commit

Complete merge of two version!

Freeze

v2QA

Branch Updates to v1QA

v2

Updates to v2

At this point these versionsshould not be updated anymore

Summary

#GXSUMMIT

TEMASProject Manager: 1 KB – N versions

Developers: N KBs – 1 version per KB

Developer: Keep Trunk KB, Add/Remove other versions

Continuously bring changes hotfixes to the trunk

Merge versions when reaching milestones

Questions

#GXSUMMIT

?

THANK YOU!Daniel Coellar, GeneXus USAdcoellar@genexususa.com

@dcoellar