Alok Kumar Singh alok15ee

## restart-ssh-gist.sh
killall ssh-agent; eval `ssh-agent`

## gist:fdc3bb48392a4d871140
Jenkins Best Practices
https://en.wikipedia.org/wiki/Continuous_integration<- Read this!
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Best+Practices
http://www.slideshare.net/andrewbayer/7-habits-of-highly-effective-jenkins-users
Set up version control of job configurations
Keep jobs simple! Don't put a ton of bash in each job. If a job needs to do something complex, put it in a script in GitHub and check it out as needed.
Use templated builders to simplify common tasks
Keep all scripts in version control - avoid running scripts that live on the Jenkins server filesystem
Don't install unnecessary plugins - plugins are often written by third parties and can interact with each other in strange ways
Use LDAP authentication if possible for traceability - avoid anonymous access

## gist:11391984


TL;DR - It was proving to be more buildsystem than I needed,
and I had found that there were other buildsystems that met my needs
that I felt were lighter and more nimble. It's still a fine product
that I continue to recommend to this day, I just no longer see it as
"The One True Way".

=========================
1: Bamboo was consuming a significant amount of system resources,

## gist:2779392
# source: http://st-on-it.blogspot.com/2010/01/how-to-move-folders-between-git.html
# First of all you need to have a clean clone of the source repository so we didn't screw the things up.

git clone git://server.com/my-repo1.git

# After that you need to do some preparations on the source repository, nuking all the entries except the folder you need to move. Use the following command

git filter-branch --subdirectory-filter your_dir -- -- all

# This will nuke all the other entries and their history, creating a clean git repository that contains only data and history from the directory you need. If you need to move several folders, you have to collect them in a single directory using the git mv command.
	Jenkins Best Practices
	https://en.wikipedia.org/wiki/Continuous_integration<- Read this!
	https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Best+Practices
	http://www.slideshare.net/andrewbayer/7-habits-of-highly-effective-jenkins-users
	Set up version control of job configurations
	Keep jobs simple! Don't put a ton of bash in each job. If a job needs to do something complex, put it in a script in GitHub and check it out as needed.
	Use templated builders to simplify common tasks
	Keep all scripts in version control - avoid running scripts that live on the Jenkins server filesystem
	Don't install unnecessary plugins - plugins are often written by third parties and can interact with each other in strange ways
	Use LDAP authentication if possible for traceability - avoid anonymous access


	TL;DR - It was proving to be more buildsystem than I needed,
	and I had found that there were other buildsystems that met my needs
	that I felt were lighter and more nimble. It's still a fine product
	that I continue to recommend to this day, I just no longer see it as
	"The One True Way".

	=========================
	1: Bamboo was consuming a significant amount of system resources,
	# source: http://st-on-it.blogspot.com/2010/01/how-to-move-folders-between-git.html
	# First of all you need to have a clean clone of the source repository so we didn't screw the things up.

	git clone git://server.com/my-repo1.git

	# After that you need to do some preparations on the source repository, nuking all the entries except the folder you need to move. Use the following command

	git filter-branch --subdirectory-filter your_dir -- -- all

	# This will nuke all the other entries and their history, creating a clean git repository that contains only data and history from the directory you need. If you need to move several folders, you have to collect them in a single directory using the git mv command.