How to setup Jenkins on Minikube

-

Setting up Jenkins on Kubernetes  is very efficient than setting it up on a local agent.  

Hence, I have listed down steps to setup Jenkins on Minikube so that you get a good understanding of how Jenkins works on Kubernetes before you set it up on multi node clusters. 

1. minikube config set memory 16384
(If space is full or your total memory is only 16384 then set to lower, 8192)

2. minikube config set cpus 4
3. minikube config set kubernetes-version 1.16.0
4. minikube start --driver=virtualbox
5. Create a namespace yaml file: 
jenkins-namespace.yaml 

Contents:

apiVersion: v1

kind: Namespace

metadata:

   name: jenkins

_________________________________________________

kubectl apply -f jenkins-namespace.yaml

6. Persistent volume :
jenkins-volume.yaml

Contents: 

apiVersion: v1

kind: PersistentVolume

metadata:

  name: jenkins-pv

  namespace: jenkins

spec:

  storageClassName: jenkins-pv

  accessModes:

    - ReadWriteOnce

  capacity:

    storage: 10Gi

  persistentVolumeReclaimPolicy: Retain

  hostPath:

    path: /data/jenkins-volume/

_________________________________________________

kubectl apply -f jenkins-volume.yaml


7. helm repo add bitnami https://charts.bitnami.com/bitnami


8. helm install jenkins -f bitnami_values.yaml bitnami/jenkins --namespace jenkins --set serviceType=NodePort


9. kubectl get pods -n jenkins NAME READY STATUS RESTARTS AGE jenkins-759cb4547c-x9qwm 1/1 Running 0 18m


10. kubectl port-forward jenkins-759cb4547c-h8jbm 8088:8080 -n jenkins


11. Access Jenkins on http://127.0.0.1:8088/

12. Username : user
Password -
echo Password: $(kubectl get secret --namespace jenkins jenkins -o jsonpath="{.data.jenkins-password}" | base64 --decode)

Thats it ! Enjoy Jenkins on http://127.0.0.1:8088/ ! 

Comments

Post a Comment

Popular posts from this blog

RestAssured : Redirect console logging to a file or a string object

-
  RestAssured has rich features to be explored and customised.    One of the things we can customize is logs. If you would want to capture the request body along with headers and the response body which definitely helps in case of failure analysis of test here is a simple approach. The  RequestLoggingFilter & ResponseLoggingFilter    allows you to specify a default java.io.PrintStream that is used for logging when calling e.g. log().all(). You could choose to log just the Request / Response or both. If you do not specify a PrintStream explicitly then  RestAssured  will default to the PrintStream defined by System.out, i.e. it will print the logs to the console.  Let us look into how we can change this to write a file or a String Object instead: File f = new File(".//src//test//resources//temp.txt"); PrintStream printStream = null; try { printStream = new PrintStream(f); } catch (FileNotFoundException e) { e.printStackTrace(); ...
Read more

Benefits of Customised Assertions

-
Customised Assertions in your test automation framework : For complex and repetitive test scenarios, it can be useful to create custom assertions where  logic is plugged away from the tests and placed into separate class Customised assertions help us dive into the intent of the tests Plug in various features like attaching the responses , logging and so on which other wise gets complex using assertions straight away in tests  Example Custom assertion class : public abstract class Verify extends BaseClass {     public static void verifyTrue(boolean condition, String message, Object... response) {         try {             Assert.assertTrue(condition, message);         } catch (AssertionError e) {             // Perform actions like attaching or logging             Assert.fail(message);         }     } ...
Read more