Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The machines and processes described on this page are a proposal and have not be setup/implemented yet

To avoid port collisions, developers should not start/stop any services on these two machines.  All development should happen on personal machines.

Are we going to set up a shared space for showing work-in-progress to others? Or is the intention to just wait until the end of each cycle before getting feedback?

Developer Testing

For testing individual commits to master, we will use a crash-and-bash machine that Chris will setup.  The Continuous Integration server will automatically deploy to this machine so it should always be up-to-date with the last commit to master.

Partner Testing

At the end of each cycle, a manual build can be started on the Continuous Integration server which will build, run tests, build documentation, tag in the git repo, release in JIRA (if possible), and deploy to pawpaw.  This instance should be stable and only updated at the end of each cycle.

  • No labels