Collect and visualize product related data from Bugzilla and Github
nailed
consists of a back-end CLI for data collection and a sinatra based web front-end for visualization of relevant development data of Products that have their bugtracker on Bugzilla and (optionally) their codebase on GitHub.
Be aware
that the bugzilla layout (metadata) is still SUSE specific, which may not be useful for everybody.
e.g. it relies on bugs being tagged as L3. The plan is to make it optional in the future.
You can use nailed directly from a git checkout as well. Make sure to fetch the dependencies and call nailed
from the bin
directory.
zypper in ruby ruby-devel ruby2.5-rubygem-bundler gcc gcc-c++ libz1 zlib-devel sqlite3 sqlite3-devel
bundle install
.oscrc
file with your credentials in ~$ nailed -h
Options:
--new, -n: Create new database
--migrate, -m: Migrate/Upgrade database
--bugzilla, -b: Refresh bugzilla database records
--github, -g: Refresh github database records
--list, -l <s>: List github repositories within organization
--server, -s: Start a dashboard webinterface
--help, -h: Show this message
.netrc
with a valid GitHub OAuth-Token in ~# example .netrc
machine api.github.com
login MaximilianMeister
password <your OAuth Token>
All configuration is read from config/config.yml
nailed --migrate
nailed --migrate
nailed --bugzilla
nailed --github
create a cronjob
for automated data collection with nailed
e.g. 0 * * * * cd /path/to/bin/nailed; ./nailed -b && ./nailed -g
start the webserver with nailed --server
git clone https://github.com/MaximilianMeister/nailed
cd nailed
docker build -t nailed:latest .
mkdir -p /tmp/storage/config
Add ~/.netrc
when you want to collect data from a private GitHub repo, config/colors.yml
config/config.yml
, and if you are from SUSE ~/.oscrc
into /tmp/storage/config
.
For trying out Nailed, just use test/config.yml
That directory will be mounted as the /nailed/data volume in the container.
docker run -ti -v /tmp/storage:/nailed/data -p 8000:4567 nailed:latest