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