Re: Help w/ maven release and git
Yup - works like a charm :-) ssh: svcSCM: no address associated with name fatal: Could not read from remote repository. That implies to me that it can't find the server calls svcSCM which comes from your developerConnection in the POM. have you verified whats in the workspace after a failed build and that the pom its trying to checkin is what you expect. On Saturday, 26 January 2013 00:00:34 UTC, Jeff Vincent wrote: Bumpanyone using GIT w/ maven-release-plugin in Jenkins? On Wed, Jan 23, 2013 at 9:41 PM, Jeff preda...@gmail.com javascript:wrote: Two questions (from a Git n00b) dealing with Git + Maven in Jenkins: 1) When I do a release, I either want a new branch based on the maven release version or a release branch sync'd w/ the latest master code and tagged with the latest release version so we can pull it if we ever need to do a hot fix based on release code. I haven't found the thing that helps me do this using the Maven Release Plugin and Git. Can anyone point me in the right direction? 2) I've configured Jenkins w/ the SSH keys for our Git service account to our internal gitolite repository. I can successfully pull and it seems that during the maven release process, the commit works when updating the POM, but it seems pushing the new branch fails with: MyGitProject: Unable to commit files Provider message: The git-push command failed. Command output: ssh: svcSCM: no address associated with name fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. The user has the same rights as my personal user and I can do branching and pushing operations manually with either account on the Jenkins box. I've tried leaving the SCM username/password blank when scheduling a maven release and I've also tried just setting the user name to match the Git service account user with similar failed results. I'm sure I'm missing something fundamentally simple, but I'm not seeing it. Any and all help is much appreciated. -- Jeff Vincent preda...@gmail.com javascript: See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- Jeff Vincent preda...@gmail.com javascript: See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group, send email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Help w/ maven release and git
Teilo ... thanks for the response! Your response poked my brain enough that I realized that my SCM URL in my POM had a problem. I was missing the // in the url (D'oH!) I fixed it and have successfully performed a release! I'm unsure though if I am following a best practice in terms of branching/tagging and would be interested to know how you (or others) do it. So far, I am just releasing off of 'master'. It didn't create a new branch like I expected, but simply seemed to tag the master branch with the release version. I thought I saw a blog somewhere that talked about a way to do releases using branches, but I can't seem to find it again. On Mon, Jan 28, 2013 at 1:15 PM, teilo teilo+goo...@teilo.net wrote: Yup - works like a charm :-) ssh: svcSCM: no address associated with name fatal: Could not read from remote repository. That implies to me that it can't find the server calls svcSCM which comes from your developerConnection in the POM. have you verified whats in the workspace after a failed build and that the pom its trying to checkin is what you expect. On Saturday, 26 January 2013 00:00:34 UTC, Jeff Vincent wrote: Bumpanyone using GIT w/ maven-release-plugin in Jenkins? On Wed, Jan 23, 2013 at 9:41 PM, Jeff preda...@gmail.com wrote: Two questions (from a Git n00b) dealing with Git + Maven in Jenkins: 1) When I do a release, I either want a new branch based on the maven release version or a release branch sync'd w/ the latest master code and tagged with the latest release version so we can pull it if we ever need to do a hot fix based on release code. I haven't found the thing that helps me do this using the Maven Release Plugin and Git. Can anyone point me in the right direction? 2) I've configured Jenkins w/ the SSH keys for our Git service account to our internal gitolite repository. I can successfully pull and it seems that during the maven release process, the commit works when updating the POM, but it seems pushing the new branch fails with: MyGitProject: Unable to commit files Provider message: The git-push command failed. Command output: ssh: svcSCM: no address associated with name fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. The user has the same rights as my personal user and I can do branching and pushing operations manually with either account on the Jenkins box. I've tried leaving the SCM username/password blank when scheduling a maven release and I've also tried just setting the user name to match the Git service account user with similar failed results. I'm sure I'm missing something fundamentally simple, but I'm not seeing it. Any and all help is much appreciated. -- Jeff Vincent preda...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/**rjeffreyvincenthttp://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- Jeff Vincent preda...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/**rjeffreyvincenthttp://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group, send email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Help w/ maven release and git
Bumpanyone using GIT w/ maven-release-plugin in Jenkins? On Wed, Jan 23, 2013 at 9:41 PM, Jeff predato...@gmail.com wrote: Two questions (from a Git n00b) dealing with Git + Maven in Jenkins: 1) When I do a release, I either want a new branch based on the maven release version or a release branch sync'd w/ the latest master code and tagged with the latest release version so we can pull it if we ever need to do a hot fix based on release code. I haven't found the thing that helps me do this using the Maven Release Plugin and Git. Can anyone point me in the right direction? 2) I've configured Jenkins w/ the SSH keys for our Git service account to our internal gitolite repository. I can successfully pull and it seems that during the maven release process, the commit works when updating the POM, but it seems pushing the new branch fails with: MyGitProject: Unable to commit files Provider message: The git-push command failed. Command output: ssh: svcSCM: no address associated with name fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. The user has the same rights as my personal user and I can do branching and pushing operations manually with either account on the Jenkins box. I've tried leaving the SCM username/password blank when scheduling a maven release and I've also tried just setting the user name to match the Git service account user with similar failed results. I'm sure I'm missing something fundamentally simple, but I'm not seeing it. Any and all help is much appreciated. -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !!
Help w/ maven release and git
Two questions (from a Git n00b) dealing with Git + Maven in Jenkins: 1) When I do a release, I either want a new branch based on the maven release version or a release branch sync'd w/ the latest master code and tagged with the latest release version so we can pull it if we ever need to do a hot fix based on release code. I haven't found the thing that helps me do this using the Maven Release Plugin and Git. Can anyone point me in the right direction? 2) I've configured Jenkins w/ the SSH keys for our Git service account to our internal gitolite repository. I can successfully pull and it seems that during the maven release process, the commit works when updating the POM, but it seems pushing the new branch fails with: MyGitProject: Unable to commit files Provider message: The git-push command failed. Command output: ssh: svcSCM: no address associated with name fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. The user has the same rights as my personal user and I can do branching and pushing operations manually with either account on the Jenkins box. I've tried leaving the SCM username/password blank when scheduling a maven release and I've also tried just setting the user name to match the Git service account user with similar failed results. I'm sure I'm missing something fundamentally simple, but I'm not seeing it. Any and all help is much appreciated. -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !!
