Hey Ulli, Looks like I don't have access to push to that repo, just tried it, see below:
$ git remote -v origin g...@github.com:jenkinsci/build-history-metrics-plugin.git (fetch) origin g...@github.com:jenkinsci/build-history-metrics-plugin.git (push) $ git push origin master ERROR: 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 when I get backfrom holidays > > On Tuesday, 7 October 2014 22:57:34 UTC+1, Ullrich Hafner wrote: >> >> I created a new empty repository since you already forked from jenkinsci: >> https://github.com/jenkinsci/build-history-metrics-plugin >> >> Welcome aboard! Ulli >> >> Am 06.10.2014 um 21:32 schrieb Aidan McGinley <aidm...@gmail.com>: >> >> 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 the entire build history? >> >> On Monday, 6 October 2014 19:16:11 UTC+1, 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>: >>> >>> So this one should really replace the old one as the old one was only >>> designed for a specific metric and it's name is misleading if it is >>> extended to include other metrics. >>> >>> >>> On Monday, 6 October 2014 10:04:56 UTC+1, Ullrich Hafner wrote: >>>> >>>> Wouldn’t it then make sense to combine these two plugins? Or continue >>>> the development in the old plugin? Or should the old one be dereleased >>>> afterwards? >>>> >>>> BTW: We can’t fork a fork of a Jenkins plugin (technical reasons). You >>>> need to provide another git repository (or we create an empty one where >>>> you >>>> can commit to). >>>> >>>> Am 05.10.2014 um 12:52 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 than just the single metric that the MTTR plugin handled. >>>> >>>> Plugin name: Quality Metrics Plugin >>>> Existing repo: https://github.com/mcgin/quality-metrics-plugin >>>> Github id: mcgin >>>> >>>> Thanks. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Jenkins Developers" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to jenkinsci-de...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to jenkinsci-de...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-de...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
