Building and Pushing Products to Production

The process of building and pushing products to the machines at DCT is mostly a manual process which should probably be automated at some point in the future. The basic process flow is:

• Set up a proper build environment
• Update the work space from the repository
• Modify about.mappings and plugin.xml files to reflect the new version number
• Export the product using the correct platform; joe uses linux (gtk/x86_64) and all others use macosx (cocoa/x86_64)
• Transfer the product to the appropriate machine at Happy Jack
• Update the alias on the desktop
  

Build Environment

I recommend to have separate build and development environments for any one who is going to work extensively on the code. If the changes are very minor, one can use the build environment to make changes and test them before building the product. Fundamentally there is no difference between the two except the name and the idea of isolation. There are instructions on Confluence for setting up the proper environment.

Synchronizing with Repository

The first step in the process of building products is to update the workspace from the repository. If one has made code changes in the build environment, update first. Then test the product and if every thing looks good, commit the changes. Update again and start building if every thing looks good.

The update process causes eclipse to automatically recompile and rebuild the work space. This process does NOT build products.

Update Version Number

Export Product

Transfer Product

Update Alias