re-enable jenkins autoprovisioning #11065
Conversation
bparees
changed the title
|
@smarterclayton do we really want to do this before oauth is enabled? it means we need to update a bunch of doc(this tutorial, official docs) telling people how to find out their jenkins password when the jenkins server gets provisioned for them. |
|
@smarterclayton bump |
|
I guess not - since we're getting close to oauth and routes. On Mon, Sep 26, 2016 at 3:39 PM, Ben Parees notifications@github.com
|
|
I will hold this until the oauth stuff goes in and then revisit this PR. |
bparees
changed the title
|
oauth has landed in the jenkins centos image and should be in the rhel image we publish for 3.4. |
bparees
force-pushed
the
enable_autoprovision
branch
from
4460377
to
e8708cd
Compare
|
[Test]ing while waiting on the merge queue |
bparees
force-pushed
the
enable_autoprovision
branch
2 times, most recently
from
354b6c8
to
f21c7b7
Compare
|
swagger regen'd |
bparees
force-pushed
the
enable_autoprovision
branch
from
f21c7b7
to
1cbf66e
Compare
|
Evaluated for origin test up to 1cbf66e |
|
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10501/) (Base Commit: 2047a73) |
|
flake #11114 |
|
Evaluated for origin merge up to 1cbf66e |
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10501/) (Base Commit: 35b539d) (Image: devenv-rhel7_5234) |
|
Update swagger On Oct 22, 2016, at 12:45 AM, OpenShift Bot notifications@github.com continuous-integration/openshift-jenkins/test FAILURE ( — |
|
@smarterclayton did you mean to comment on this PR? it's already merged. |
|
(and yes, swagger was updated as part of it) |
No description provided.