You can find the guidelines here:
четверг, 1 февраля 2018 г., 16:09:19 UTC+1 пользователь Jack Zylkin написал:
> I would not know what to do with ownership if I had it. I don't know how
> to build and release a version of a Jenkins plugin. Can you point me to
> On Friday, January 26, 2018 at 12:59:27 PM UTC-5, Oleg Nenashev wrote:
>> Hi Jack,
>> The best way would be to take ownership of the plugin if you are
>> In order to grant you release permissions, we just need a confirmation
>> from any of the current maintainers a pull request with a
>> modification. The latter option would be preferable. Once we have such
>> authorization, we will be able to transfer ownership.
>> Hopefully it helps,
>> среда, 24 января 2018 г., 15:35:06 UTC+1 пользователь Jack Zylkin написал:
>>> An important bugfix was recently merged to the CppCheck plugin repo
>>> (JENKINS-42727). It allows multiple instances of CppCheck builds to run
>>> concurrently without blocking each other. Each of my CppCheck builds takes
>>> about 1 hr to run, and I am unable to run them in parallel because of this
>>> bug. This bug is causing a substantial bottleneck in my pipeline, so I
>>> would really like the fix to be incorporated into a release so I can deploy
>>> The fix has already been merged into the project – someone just needs to
>>> make a new tagged release of this plugin. I have already contacted one of
>>> the admins for this plugin, who has said he does not work on it anymore.
>>> The other admin was not responsive.
>>> How can I make a build of this plugin and release it myself?
>>> If I am not able to do it myself, who should I approach about doing it?
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 view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.