: Permission to jenkinsci/build-history-metrics-plugin.git denied to
mcgin.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
On Thursday, 9 October 2014 16:04:55 UTC+1, Aidan McGinley wrote:
Great thanks. Will take a look
06.10.2014 um 21:32 schrieb Aidan McGinley aidm...@gmail.com
javascript::
It's a fair point, I have to say I have struggled to come up with a better
name, and wasn't even happy with quality-metrics. Perhaps
build-history-metrics would be better given the focus is more on aggregate
metrics across
schrieb Aidan McGinley aidm...@gmail.com
javascript::
Hi,
I've developed a new plugin for capturing quality metrics for a build.
It's heavily influenced by the now defunct mttr plugin (
https://github.com/jenkinsci/mttr-plugin), but different enough that it
warrants it's own space in my
, Ullrich Hafner wrote:
I think quality metrics is also somewhat misleading as this name is
normally used for source code metrics like McCabe's complexity, etc. What
do you think? What would be an appropriate name for the plugin?
Am 06.10.2014 um 15:46 schrieb Aidan McGinley aidm...@gmail.com
Hi,
I've developed a new plugin for capturing quality metrics for a build.
It's heavily influenced by the now defunct mttr plugin
(https://github.com/jenkinsci/mttr-plugin), but different enough that it
warrants it's own space in my view. It's been generalised to be able to
capture more
