Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upgitignore for JENKINS_HOME Jenkins settings #1763
+25
−0
Conversation
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
stephengroat
Feb 18, 2016
Contributor
This has been working well for me. I've been using it to version control configs for different slaves
|
This has been working well for me. I've been using it to version control configs for different slaves |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
samrocketman
Feb 26, 2016
Awesome :). I also use a dailycommit.sh script in a cron job so that it regularly takes a snapshot of the commits. https://gist.github.com/samrocketman/9391439
samrocketman
commented
Feb 26, 2016
|
Awesome :). I also use a dailycommit.sh script in a cron job so that it regularly takes a snapshot of the commits. https://gist.github.com/samrocketman/9391439 |
samrocketman
referenced this pull request
Feb 26, 2016
Open
Allow for user defined gitignore instead of custom "includes" #40
shiftkey
added
the
new template
label
Mar 6, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
samrocketman
commented
Jul 2, 2016
|
Is there any interest in merging this? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
samrocketman
commented
Nov 30, 2017
|
@shiftkey mind taking a look at this again? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
samrocketman commentedNov 20, 2015
This allows an admin to use git to keep a backup of Jenkins settings without tracking binary artifacts. Useful for preserving settings during plugin upgrades.
Note:
secret.keyis purposefully not tracked by git. This should be backed up separately because configs may contain secrets which were encrypted using thesecret.key.See also: