- reads tests results data from Jenkins output (json or csv)
- creates a new folder to place the genarated files
- creates a spreadsheet from a template in a Google Drive folder (from item 2, above)
- fills the spreadsheet with data from datasource (Jenkins output)
- creates a document from a template in the same folder as the spreadsheet
- replaces data in the document (place holders)
There is a .properties file in the * drools.reports.resources folder *. It is possible to setup:
- input data params for the generated documents (template's place holders)
- datasource paths (json and csv): Jenkins output files
- template files IDs on Google Drive
- folder ID to place the generated report
- csv as alternative
- Follow the instructions: [1]
- Download the Google API Key File (Json format)
- Rename the file to "client_secret.json"
- Place the file on this folder: src/main/java/org/benchmarks/reports/resources/client_secret.json
- Call GoogleAuthorizeAsUser.authorize() on GoogleService() constructor.
- Follow the instructions: [2]
- Download the Service Google API Key File (Json format)
- Rename the file to "service-account.json"
- Place the file on this folder: src/main/java/org/benchmarks/reports/resources/service-account.json
- Take note of the service account e-mail address (API Console -> learn more [2])
- Go to the sharing configurations on the Google Drive Folder where the reports and templates are
- Set the service account e-mail address as a "People" to share the folder
- Call GoogleAuthorizeAsService.authorize() on GoogleService() constructor.
- DONE | draw chats and place them in the document
- DONE | do the authentication process automated
- DONE | set the output of the project in a shared space in Google Docs
- Major | integrate it with the Jenkins jobs to have reports more often (once a day/night?)
- Optional | improvements in the code
- Optional | improvements in the templates
- Optional | suggestions and feedbacks are welcome