Support username and password credentials about jenkins-plugin HOT 8 CLOSED

As an FYI, we are tracking this request with this trello card

from jenkins-plugin.

@bparees @mfojtik FYI

A couple of preliminary points:

1. short term, the openshift-restclient-java component already has user/password support; the effort would be simply exposing means through the UI to store those values for the build steps

2. haven't looked in detail yet, but I suspect this falls in line with @mfojtik 's comment about how the k8s plugin leverages the credentials plugin and that we probably should do the same

in any event, it certainly is a call to move beyond the pre-plugin sample job that only leveraged token based auth

from jenkins-plugin.

sounds reasonable to me.

from jenkins-plugin.

Up. Very inconvenient with tokens. We have about 40 builds + 30 deployment configurations - it's hell of tokens.

from jenkins-plugin.

Up. Very inconvenient with tokens. We have about 40 builds + 30 deployment configurations - it's hell of tokens.

i take it you can't simply grant permissions to a single token to access all of those builds and deployments?

from jenkins-plugin.

I wanted do that at first step, but after some reflections I decided to set permissions separately, by projects (some users can to do some things in other projects too). At this moment it is working, but after I see Jenkins tasks, I can't definitely understand who from users can tag "IS" or can launch "DC", it is impersonal, I need username and password.

from jenkins-plugin.

closing out ... tracking with trello card

from jenkins-plugin.

closing issue - will track via previously noted (on May 16) trello card

from jenkins-plugin.