You are looking at the user documentation for the most recent
master branch of RepoSense (not released to the public yet). The documentation for the latest public release is here.
You can use the CI tool Travis to automate generating and publishing of RepoSense reports.
The instructions below assume you are using GitHub pages to host your report.
Step 1 Fork the publish-RepoSense repository using this link. Optionally, you can rename the fork to match your RepoSense report e.g.,
Step 2 Generate a personal access token or deploy key on GitHub as explained in the panel below.
Step 3 Login to Travis-CI. You may have to sign up first.
Step 4 Syncy your Travis account with GitHub:
Sync accountto fetch all your repositories into Travis-CI.
Step 5 Activate the repository:
Currenttab, click on
Step 6 Set the token/key:
More optionson the right.
Environment Variables, name a variable as
GITHUB_DEPLOY_KEYdepending on your earlier choice and paste the token/key into its value field; then click
Display value in build logis
switched offfor security reasons:
Step 7 Update the report configuration:
In your fork, edit
run.sh (and if applicable,
group-config.csv) to customize the command line parameters or repositories to be analyzed.
Step 8 View the generated report:
Settingspage of your fork in GitHub.
GitHub Pagessection, look for
Your site is published at [LINK]. It should look something like
It takes a few minutes for report generation. Meanwhile, you can monitor the progress live at Travis-CI's Builds.
Manual: Travis UI has a way for you to trigger a build, using which you can cause the report to be updated.
More optionson the right then
Trigger custom build.
Automated: Travis-CI offers
Cron Jobs in intervals of daily, weekly or monthly.
More optionson the right then access
Cron Jobs, choose
Optionsand pick an
Intervalof your choice; then click