Make activeDeadlineSeconds for backup job configurable (#86)

Signed-off-by: Prabhu Jayakumar <[email protected]>

Author: prabhu43

charts/jenkins/CHANGELOG.md

@@ -10,6 +10,10 @@ Use the following links to reference issues, PRs, and commits prior to v2.6.0.
 
 The change log until v1.5.7 was auto-generated based on git commits. Those entries include a reference to the git commit to be able to get more details.
 
+## 2.10.0
+
+Make activeDeadlineSeconds for backup job configurable
+
 ## 2.9.0
 
 Make namespace of PrometheusRule configurable

charts/jenkins/Chart.yaml

@@ -1,7 +1,7 @@
 apiVersion: v1
 name: jenkins
 home: https://jenkins.io/
-version: 2.9.0
+version: 2.10.0
 appVersion: lts
 description: Open source continuous integration server. It supports multiple SCM tools
   including CVS, Subversion and Git. It can execute Apache Ant and Apache Maven-based

charts/jenkins/templates/jenkins-backup-cronjob.yaml

@@ -16,6 +16,9 @@ spec:
   startingDeadlineSeconds: 120
   jobTemplate:
     spec:
+{{- if .Values.backup.activeDeadlineSeconds }}
+      activeDeadlineSeconds: "{{ .Values.backup.activeDeadlineSeconds }}"
+{{- end }}
       template:
         metadata:
           {{- if .Values.backup.labels }}

charts/jenkins/values.yaml

@@ -694,6 +694,8 @@ backup:
     # Example for authorization to AWS S3 using kube2iam
     # Can also be done using environment variables
     # iam.amazonaws.com/role: "jenkins"
+  # Set this to terminate the job that is running/failing continously and set the job status to "Failed"
+  activeDeadlineSeconds: ""
   image:
     repository: "maorfr/kube-tasks"
     tag: "0.2.0"