/
Using Java Agents - Uploading git commit logs
Using Java Agents - Uploading git commit logs
If you do not work with github
or cannot provide access to the source folder where the git logs are located, you can generate them on your own and upload them separately to the SeaLights servers.
See 'Java Command Reference - Upload report files' for full parameter details
Generating the commit reports
The file must be a JSON file with an array "commitLog
" of commits. Below, a sample command which generate 2 days of commit logs:
echo "{ \"commitLog\": " > commitLog.json
git log --pretty=format:'{"commit": "%H","authorName": "%an","authorEmail": "%ae","commiterName": "%cn","commiterEmail": "%ce","authorDate": "%at000","commiterDate": "%ct000","title": "%f"},' --since="2 days ago" | sed "$ s/,$//" | sed ':a;N;$!ba;s/\r\n\([^{]\)/\\n\1/g'| awk 'BEGIN { print("[") } { print($0) } END { print("]") }' >> commitLog.json
echo "}" >> commitLog.json
Upload git generated commit log reports
java -jar sl-test-listener.jar uploadReports -tokenfile /path/to/sltoken.txt -buildsessionidfile buildSessionId.txt -reportFile commitLog.json -type "commitLog" -source "script"
See 'Using Java Agents - Uploading multiple files' for information on how to upload multiple files
Related content
SeaLights Java agent - Command Reference
SeaLights Java agent - Command Reference
More like this
Using Node.js Agents - Uploading git commit logs
Using Node.js Agents - Uploading git commit logs
More like this
Analyzing a GitHub.com Pull Request
Analyzing a GitHub.com Pull Request
More like this
Using Sealights from a Jenkins Pipeline job
Using Sealights from a Jenkins Pipeline job
More like this
Configuring your Pull Request flow to report to SeaLights
Configuring your Pull Request flow to report to SeaLights
More like this
Analyzing a GitHub Enterprise Pull Request
Analyzing a GitHub Enterprise Pull Request
More like this