Jenkins-X | A OSX client for Jenkins

After trying to create a new Kubernetes cluster in AKS with version v1.16.7, I still received the same error. Also, creating a cluster in Google Cloud Platform using command jx create cluster gke --skip-installation and then running jx boot resulted in the same error as shared in this stack overflow question.

So, it turns out that I had to manually create a workspace/source directory in the default jenkins-x-boot-config's cloned repository directory. This is because even when I set the directory to '.' in the jenkins-x.yaml file for step jx step git validate it still appends the path workspace/source to ~/jenkins-x-boot-config when executing this jenkins x step resulting in an error due to the fact that the directory ~/jenkins-x-boot-config/workspace/source does not exist. Additionally, I had to upgrade jx cli to a newer version, version 2.1.34.

Example of new file structure for jenkins-x-boot-config:

After experimenting all day...

I came with a solution, it's not the best or straight forward but at least it's working. My slave is connected! INFO: Connected

So, I edited the jenkins-agent service and from type: ClusterIP I changed to type: LoadBalancer. That gave me a new fresh loadbalancer and after I decided to add the port 8080 because in the service yaml file it's using the same selector as in jenkins service.

(jenkins-agent service yaml)

When you run an external command (or any command), the output of that command can be piped into a PowerShell command. Since your command outputs single lines containing a package name, that output can be piped into Foreach-Object where each package (object in PowerShell terms) can be processed.