They include:
- Actual documentation.
- Various scripts to import log files sparse in /afs to the git repository.
A reasonable amount of processed log files, usually in json format, can be stored in this git repository and not cause scalability issues, since git is extremely good at compressing similar files.
This allows us to serve integration builds results via Github Pages
In order to populate the data directory:
git clone cms-sw.github.com
cd cms-sw.github.com
./process-logs --logdir <path-to-your-toplevel-log-directory>
make -j 20
git commit data -m'Results updated'
git push origin master
This repository contains two branches - master and code. All user submitted changes should go to code branch which will then be merged into master branch. Auto-generated data such as JSON files submitted by Cms Bot should go directly in to master. This should solve PR issues like this.
