I want to apologize for the tone in my original post. Just feeling a bit
overwhelmed at the moment.
The plugin on Github still contains the `adopt-this-plugin` tag and the
"Seeking a new maintainer" section.
https://github.com/jenkinsci/dependency-check-plugin
Please let me know if there is
> however I don't have the permissions to push the branch. Worth an
attempt.
You would do it in your fork, not the actual repo.
On Thu, Nov 11, 2021 at 7:21 AM Mark Waite
wrote:
> As one of the items in Part 4 of the 5 part "Modernizing Jenkins Plugins"
> video series, there is a segment that
As one of the items in Part 4 of the 5 part "Modernizing Jenkins Plugins"
video series, there is a segment that shows how we enabled automated
releases for a plugin.
https://www.youtube.com/watch?v=pk1gweLvcEI=346s
On Thursday, November 11, 2021 at 8:14:13 AM UTC-7 jsupun wrote:
> I'm
I'm attempting to follow
https://www.jenkins.io/doc/developer/publishing/releasing-cd/. It looks
like I enable it via jenkins-infra/repository-permissions-updater. Wasn't
sure if I need to checkout the repo, make the changes to my plugin
permissions, and then make a PR. I tried, however I
As a side note for this plugin: if someone is willing to refactor the existing
parser so that it rather writes the output to the object model of the
analysis-model plugin then we simply can integrate it into the parser
collections of the warnings plugin. Then the whole OWASP Dependency Check
Updated JEP with fixed numeration reference. Thanks @Oleg Nenashev
! It should be JEP-234
On Thu, Nov 11, 2021 at 12:51 PM Ildefonso Montero
wrote:
> Just added the topic about JEP-401 inside agenda of next Jenkins UX SIG
> meeting Nov 24:
>
Just added the topic about JEP-401 inside agenda of next Jenkins UX SIG
meeting Nov 24:
https://docs.google.com/document/d/1QttPwdimNP_120JukigKsRuBvMr34KZhVfsbgq1HFLM/edit#
On Thu, Nov 11, 2021 at 12:46 PM Ildefonso Montero
wrote:
> Hi all,
>
> Created the following JEP that I want to share
Hi all,
Created the following JEP that I want to share with you:
https://github.com/jenkinsci/jep/pull/380
Reference implementation draft PR in:
https://github.com/jenkinsci/jenkins/pull/5909
Also, planning to present this approach in the next Jenkins UX SIG meeting.
Looking for your feedback
