Getting together to define some secure setup guidelines for users
would be useful, too. It's not that helpful that Jenkins and its
plugins are more secure if users end up configuring Jenkins insecurely
in the first place!
On Thu, Jan 21, 2021 at 7:12 AM 'Olblak' via Jenkins Developers
wrote:
>
>
I'd argue that without a maintainer, a plugin would be better off
archived until someone with sufficient interest to maintain it
volunteers.
On Fri, Jan 22, 2021 at 3:05 AM ogondza wrote:
>
> I understand it feels strange, though it is the second best thing we can do
> in case we lack a maintain
You should look at potentially integrating this plugin into your code:
https://plugins.jenkins.io/oauth-credentials/
On Fri, Jan 22, 2021 at 9:52 AM Michael Carter
wrote:
>
> I've basically been tasked with "converting to oauth2" for all my API calls.
>
> Can someone point me in the right directi
That's a good point. I still see people who don't know about pipelines
even though they've been around since Jenkins 2.0 IIRC. The updated UI
is also less well known.
On Fri, Jan 22, 2021 at 9:23 PM Ming Tang wrote:
>
> I think the release of Jenkins 3.x is very urgent. Let me put forward another
