Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I will be moving to git for my version control soon. My continuous build system is Hudson and I use maven to build my artifacts.
Anyone have a best practice for setting up git to work best with these other tools.
recommendations on how packages and plugins should be managed in git to most easily pull down into Hudson would also be appreciated.
Please and thank you.
We are using git-maven-hudson daily.
For hudson there is a git plugin which works great and has a killer feature.
Maven takes care of its own dependencies and does not need to know about either git or hudson, which makes for nice decoupling and less moving parts.
Now for the killer feature :
We work ticket based. In git we use a branch per ticket and do all development for a single ticket on that branch. When ready to share we push the branch to a central repo. The Git plugin will check and load all new branches, merge them to the master and compile/run tests/deploy to Nexus and push the patches to the master branch.
We pull regularly from the master branch to keep close to head.
This works incrediby well with hardly any merge conflicts on the server.