JENKINS_HOME .gitignore テンプレート

1### JENKINS_HOME ###
2# Learn more about Jenkins and JENKINS_HOME directory for which this file is
3# intended.
4#
5#  http://jenkins-ci.org/
6#  https://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins
7#
8# Note: secret.key is purposefully not tracked by git. This should be backed up
9# separately because configs may contain secrets which were encrypted using the
10# secret.key.  To back up secrets use 'tar -czf /tmp/secrets.tgz secret*' and
11# save the file separate from your repository.  If you want secrets backed up
12# with configuration, then see the bottom of this file for an example.
13 
14# Ignore all JENKINS_HOME except jobs directory, root xml config, and
15# .gitignore file.
16/*
17!/jobs
18!/.gitignore
19!/*.xml
20 
21# Ignore all files in jobs subdirectories except for folders.
22# Note: git doesn't track folders, only file content.
23jobs/**
24!jobs/**/
25 
26# Uncomment the following line to save next build numbers with config.
27 
28#!jobs/**/nextBuildNumber
29 
30# For performance reasons, we want to ignore builds in Jenkins jobs because it
31# contains many tiny files on large installations.  This can impact git
32# performance when running even basic commands like 'git status'.
33builds
34indexing
35 
36# Exclude only config.xml files in repository subdirectories.
37!config.xml
38 
39# Don't track workspaces (when users build on the master).
40jobs/**/*workspace
41 
42# Security warning: If secrets are included with your configuration, then an
43# adversary will be able to decrypt all encrypted secrets within Jenkins
44# config.  Including secrets is a bad practice, but the example is included in
45# case someone still wants it for convenience.  Uncomment the following line to
46# include secrets for decryption with repository configuration in Git.
47 
48#!/secret*
49 
50# As a result, only Jenkins settings and job config.xml files in JENKINS_HOME
51# will be tracked by git.
52