Development on Windows

Development on Mac OS X

Release Management to Test Environment

Release Management to Production Environment

Administrative Notes

Overview

We switch to a new model for version control. The new model has 2 branches, including master to release to Production environment, and test to release to Test environment. Developers work on the test branch (commit, push, pull, etc.), and RMs work on both branches. Developers can easily release their changes to Test environment if RMs are not available. Release Management is taken care of in several special cases when the primary/back-up RMs are not available.

Roles

There are 4 roles in this process: Requester, Developer, Functional Approver, and Release Manager.

Development Prerequisites

When a developer joins FAMIS project, the developer needs to

1. Work with the release manager to get access to Bitbucket server using his NetID and password
2. Download and install JRE, JDK, SQL Developer, NetBeans (or Aptana), Git, and SourceTree for Windows (or Mac OSX). The developer may want to update to newer versions if any has already been installed previously.
3. Work with server group to get access to the development web server, and the development database server. This can be accomplished by filing a FootPrints ticket on serviceit.uconn.edu and assigning to the group.

Release Management Prerequisites

When a release manager joins FAMIS project, the release manager needs to

1. Work with the primary release manager to get access to Bitbucket server using his NetID and password
2. Download and install JRE, JDK, Git, and SourceTree for Windows (or Mac OSX). The release manager may want to update to newer versions if any has already been installed previously.
3. Work with server group to get access to the deployment tools on the development, test, and production web servers. This can be accomplished by filing a FootPrints ticket on serviceit.uconn.edu and assigning to the group.