Synthetic File System Build and Deployment Documentation

Build and Deployment Processes

To avoid data loss and failures, and thus user dissatisfaction, the software must be properly built and deployed.

Build process

In the build process the agile team implements these processes:

1. If a developer needs to develop a functionality or make fixes, the developer creates a branch from the main branch or from the existing branch with a name that indicates the functions or fixes and work on that branch.
2. After a developer completes development and testing of source code changes in the cloned repository, the developer merges that branch to the parent branch or waits until the developer receives permission to merge his working branch with the main branch.
3. When all code changes are completed and tested in the programming environment, the release manager requests the product owner to decide whether the changes can be released.
4. With the product owner’s approval, the release manger creates a pull request to merge the parent branch or a working branch with the main branch. Deployment process In the scope of our specific project, the agile team and the industry partner focus on obtaining a prototype virtual file system. Therefore, no actual deployment process is performed. After the changes and fixes are accepted by the product owner, the remote main branch is updated and can be downloaded for use.