So you doesn't want to do linting for non job functionality? Global/cloud 
configuration and etc?

On Tuesday, July 7, 2015 at 10:25:20 AM UTC+3, Victor Martinez wrote:
>
> Thanks Daniel & Richard for that spot. I believe Jenkins Job Lint Plugin 
> matches exactly what it does. I will rename it today. I'll will update 
> those details later on. 
>
> Thanks again
>
>
>
> On Tuesday, 7 July 2015 02:49:53 UTC+2, Richard Bywater wrote:
>>
>> It's up to Victor of course but perhaps Jenkins Job Lint Plugin as it 
>> would presumably come out as Job Lint Plugin which still fits?
>>
>> Richard.
>>
>> On Tue, 7 Jul 2015 at 09:58 Daniel Beck <[email protected]> wrote:
>>
>>> This looks interesting! I (and I assume many others) write scripts to 
>>> check e.g. that all 'marked as keep forever' builds have a non-empty 
>>> description and such. A dedicated plugin would have been a much more 
>>> elegant solution.
>>>
>>> One issue is the name though; Jenkins internally strips the 'Jenkins' 
>>> prefix to a plugin name (and may soon do more) because so many plugins 
>>> unnecessarily add that, so only 'Lint Plugin' would be left, which seems 
>>> misleading. Can you think of another name?
>>>
>>> On 05.07.2015, at 19:12, Victor Martinez <[email protected]> wrote:
>>>
>>> > Hi there,
>>> >
>>> > I've been working on some Jenkins automation to highlight when Jobs 
>>> are not using some of the best practices I've already found/defined based 
>>> on others or in my own experience. It's exactly the same approach as other 
>>> lint detect tools: such as: checkstyle, pmd, puppet-lint, so on.
>>> >       • Github repo: https://github.com/v1v/jenkins-lint-plugin
>>> >       • repository name: jenkins-lint-plugin
>>> >       • Github user: v1v
>>> >       • jenkins-ci.org: v2v
>>> >       • Description: Checks Jenkins Jobs for practices and behaviour 
>>> that could potentially be improved.
>>> >       • Wiki: 
>>> https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Lint+Plugin
>>> > Looking forward for having some feedback.
>>> >
>>> > Thanks,
>>> >
>>> > Víctor
>>> >
>>> >
>>> > --
>>> > 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 [email protected].
>>> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/1861c0f5-73fd-4e69-bd08-3f75c24f2443%40googlegroups.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 [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/B69A736C-F5A8-4D03-93CF-0699F159EC24%40beckweb.net
>>> .
>>> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/20af5d17-b414-4e4a-a8a7-af6e62e655bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to