Dear all,
I would like to start two new special interest groups in Jenkins: Embedded
SIG and "Hardware and Electronic Design Automation" (HW and EDA) SIG. Just
to provide some background, I have originally came from the
Hardware/Embedded area, and industry-specific CI/CD is still one of my main
in
Yes, the master pod logs showed SUCCESSFUL whether the IP is cluster1 or
cluster2. However, the slave pods are always launching in cluster1,
regardless of what's set in Kubernetes URL. Seems the Kubernetes URL is not
being used at all or if did it's overridden by cluster1 IP.
On Mon, 7 Jan 2019 at
*Dear All:*
*My Jenkins was previously version 2.138 using the official image on docker
hub, using gitlab for authorization, upgrading to any version of the
general user's project view cannot be displayed, error 404 and An error
occurred when retrieving jobs for this view. Please consult the Jen
check the logs
https://github.com/jenkinsci/kubernetes-plugin/#debugging
On Mon, Jan 7, 2019 at 9:07 AM Don Capito wrote:
> No joy. Regardless whether Kubernetes URL is set to cluster1 (ie, jenkins
> master pod) or cluster2 (jenkins slave) IP, the jenkins slave pods are
> still launched in cl
No joy. Regardless whether Kubernetes URL is set to cluster1 (ie, jenkins
master pod) or cluster2 (jenkins slave) IP, the jenkins slave pods are
still launched in cluster1.
Am I missing some setttings?
On Fri, 4 Jan 2019 at 15:01, Carlos Sanchez wrote:
> master can be anywhere, on prem, vm, kub
