-
Notifications
You must be signed in to change notification settings - Fork 23
Development workflow
Tadashi Maeno edited this page Apr 6, 2017
·
6 revisions
Harvester is developed based on GitHub Flow with small customization. The sequence is as follows:
- Create a branch or folk. In git, branches are light weight things that are often temporary and may be deleted anytime. The master branch is protected, so that only a couple of persons can push commits there.
- Add commits to the branch. You can experiment any changes since they don't affect the master branch.
- Deploy changes on a test instance. All changes must be verified before being merged to the master branch.
- Open a Pull Request. Pull Requests initiate discussion about your changes.
- Discuss and review your code. Once a Pull Request has been opened, your changes are reviewed to check functionalities, the coding style, test results, and so one. Note that your code must follow PEP8.
- Merge changes. Once your changes are approved they will be merged to the master branch. The branch can be deleted at this stage since commit logs are also merged.
| Getting started |
|---|
| Installation and configuration |
| Testing and running |
| Debugging |
| Work with Middleware |
| Admin FAQ |
| Development guides |
|---|
| Development workflow |
| Tagging |
| Production & commissioning |
|---|
| Scale up submission |
| Condor experiences |
| Commissioning on the grid |
| Production servers |
| Service monitoring |
| Auto Queue Configuration with CRIC |
| SSH+RPC middleware setup |
| Kubernetes section |
|---|
| Kubernetes setup |
| X509 credentials |
| AWS setup |
| GKE setup |
| CERN setup |
| CVMFS installation |
| Generic service accounts |
| Advanced payloads |
|---|
| Horovod integration |