[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
David Cullen commented on JENKINS-22820 Changes are not commited when using a recent git client The problem is that the scm-sync-plugin no longer supports git+ssh URIs: ssh: Could not resolve hostname git%2bssh: Name or service not known After I removed the "git+" from the URI, the plugin worked with git 1.9.1. I still do not get commit message dialogs. Will I be able to debug that using the setup in your blog post? Also, what JDK should I install? I think that Java 7 was installed because I used the PPA to install Jenkins and it pulled in the default JRE during the install. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
rogerhu commented on JENKINS-22820 Changes are not commited when using a recent git client I just rechecked with this latest plugin and it works fine on Ubuntu 14.04 and Git 1.9.1. Furthermore, Git 2.1.0 also works fine. I would go to System Log -> add a Log recorder for "hudson.plugins.scm_sync_configuration". It should be more obvious what the issue is on your system. Yes, Java 6. Also you can skip setting the parent version (leave it) since there are dependencies going from Hudson to Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
David Cullen commented on JENKINS-22820 Changes are not commited when using a recent git client > What other symptoms are you seeing? When I install git 1.9.1 the checkoutConfiguration directory is created but the .git repository is not cloned from the remote. I am unable to build the plugin. If I change the parent version to 1.509 so that the plugin will build with Java 7, the tests fail: org.jenkins-ci.plugins plugin 1.509 ../pom.xml Are you building against Java 6? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
rogerhu commented on JENKINS-22820 Changes are not commited when using a recent git client The commit message dialog not being displayed is a different issue and a regression from a previous change. What other symptoms are you seeing? You can debug this too by using IntelliJ Community Edition and importing the project too...click right-click on the hpi:run and you can startup your own instance of Jenkins (bit.ly/1t9vKDd) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
David Cullen commented on JENKINS-22820 Changes are not commited when using a recent git client I have installed the 0.0.8 version of the scm-sync-configuration plugin and it still does not work with git 1.9.1 on Ubuntu 14.04. The 0.0.8 version of the plugin partially works with git 1.8.3.2; however, the commit message dialog is not displayed. Is there anything I can do to help resolve these problems? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
SCM/JIRA link daemon commented on JENKINS-22820 Changes are not commited when using a recent git client Code changed in jenkins User: Frédéric Camblor Path: pom.xml src/main/resources/META-INF/plexus/components.xml http://jenkins-ci.org/commit/scm-sync-configuration-plugin/5fd7d4b3e6a8c293529cd7db3dca667d460c1306 Log: Merge pull request #21 from rogerhu/jenkins_22820 JENKINS-22820 fix - Bump maven.scm to 1.9.1 to avoid issues with Git v1.9 upgrades. Compare: https://github.com/jenkinsci/scm-sync-configuration-plugin/compare/a6d775bbaafa...5fd7d4b3e6a8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Frédéric Camblor resolved JENKINS-22820 as Fixed Changes are not commited when using a recent git client Thanks @rogerhu for the PR, merged ! It will be part of v0.0.8 (release in progress) Change By: Frédéric Camblor (24/Aug/14 8:58 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
SCM/JIRA link daemon commented on JENKINS-22820 Changes are not commited when using a recent git client Code changed in jenkins User: Roger Hu Path: pom.xml http://jenkins-ci.org/commit/scm-sync-configuration-plugin/1a6dfc6febbd024ae3b09beea87284932b19f0a5 Log: Bump org.apache.maven.scm dependencies to be able to support Git v1.9.1. Related to issue: https://issues.jenkins-ci.org/browse/JENKINS-22820 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
rogerhu commented on JENKINS-22820 Changes are not commited when using a recent git client I had to bump all org.apache.maven.scm related packages to 1.9.1. https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/21 The fix works for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
David Cullen edited a comment on JENKINS-22820 Changes are not commited when using a recent git client After some research, I figured out how to downgrade git to the version in Ubuntu 13.10. I created "/etc/apt/sources.list.d/sausy.list" with these contents: # I need access to the 13.10 repositories so that I can downgrade git deb http://us.archive.ubuntu.com/ubuntu/ saucy main restricted deb-src http://us.archive.ubuntu.com/ubuntu/ saucy main restricted I ran aptitude and did an update (the equivalent of apt-get update). After that, I was able to find the older version of git and install it. I used dependency resolver in aptitude to downgrade the dependencies. If you are using apt-get, you can avoid this by uninstalling git first. I still have the problem described here: https://issues.jenkins-ci.org/browse/JENKINS-22666 I tried downgrading the scm-sync-plugin to 0.0.7.3, but it did not fix the problem This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
David Cullen commented on JENKINS-22820 Changes are not commited when using a recent git client After some research, I figured out how to downgrade git to the version in Ubuntu 13.10. I created "/etc/apt/sources.list.d/sausy.list" with these contents: I need access to the 13.10 repositories so that I can downgrade git deb http://us.archive.ubuntu.com/ubuntu/ saucy main restricted deb-src http://us.archive.ubuntu.com/ubuntu/ saucy main restricted I ran aptitude and did an update (the equivalent of apt-get update). After that, I was able to find the older version of git and install it. I used dependency resolver in aptitude to downgrade the dependencies. If you are using apt-get, you can avoid this by uninstalling git first. I still have the problem described here: https://issues.jenkins-ci.org/browse/JENKINS-22666 I tried downgrading the scm-sync-plugin to 0.0.7.3, but it did not fix the problem This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
David Cullen commented on JENKINS-22820 Changes are not commited when using a recent git client I have the same problem: Jenkins 1.565.1 LTS, scm-sync-plugin 0.0.7.5, git plugin 2.2.5, git client plugin 1.10.1, Ubuntu 14.04.1 LTS. I downloaded the source for the plugin so that I could try to fix the problem, but I am having difficulty figuring out how it works. Also, is there a way to pass LANG=en_US.UTF-8 to git? If I can't fix the problem, maybe this would be a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
M Chon commented on JENKINS-22820 Changes are not commited when using a recent git client I am also experiencing this on Windows 7, msysgit 1.9. I will try downgrading to cygwin git 1.7.9 and see if that clears up the issue. Same exact symptoms - log file says " pushed to SCM !" but files are not actually committed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Frédéric Camblor commented on JENKINS-22820 Changes are not commited when using a recent git client ok, since it was quite a long time (sorry for the late reply ), I would have thought you tested with a version before 1.9 (which seems to contain a fix for the --porcelain command line) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Brice Jaglin commented on JENKINS-22820 Changes are not commited when using a recent git client Oh, sorry Then I can reiterate that bumping maven-scm-provider-gitexe to 1.9 did NOT help when I first investigated the issue, as already mentioned in the description. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Frédéric Camblor commented on JENKINS-22820 Changes are not commited when using a recent git client I'm not speaking about maven-release-plugin, but about the direct pom dependency This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Brice Jaglin commented on JENKINS-22820 Changes are not commited when using a recent git client Great news! About the gitexe bump: I had only tried to upgrade the project dependency (which didn't help), not to force the dependency of the maven-release-plugin plugin, so I can't tell whether what that would solve the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Brice Jaglin edited a comment on JENKINS-22820 Changes are not commited when using a recent git client Great news! About the gitexe bump: I had only tried to upgrade the project dependency (which didn't help), not to force the dependency of the maven-release-plugin plugin, so I can't tell whether that would solve the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Frédéric Camblor commented on JENKINS-22820 Changes are not commited when using a recent git client Hi there ! It seems Emmanuel was right. First, there seems to have a "simple" workaround described here (setting LANG to en_US.UTF-8) @Brice did you try to use maven-scm-provider-gitexe v1.9 (or above) as stated here ? If this confirm the resolution, I'll align on this version of the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
John Ferlito commented on JENKINS-22820 Changes are not commited when using a recent git client I'm seeing the same issue. Let me know if there is anything I can do to help debug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Kathryn McClintic commented on JENKINS-22820 Changes are not commited when using a recent git client I have a question about this issue. I am also experiencing the same problem. Please excuse my ignorance (still learning!). Can someone please advise me if my thought process regarding this problem is correct? When someone makes a change to one of the Jenkins config files, the changes attempt to get pushed to the local git hub repo connected to the account, even though they should actually be pushed to to the online repo. The files actually end up in checkOutConfigurations directory and since nothing is connected to that directory, the changes are never pushed to the git repo. If everything was going smoothly, would the files actually be pushed to the local repo and then the online repo? Thank you so much. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Adam Crews commented on JENKINS-22820 Changes are not commited when using a recent git client I can also confirm that it seems to be something related to git 1.9. I do not have this issue with git 1.7 nor 1.8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Erik Riemers commented on JENKINS-22820 Changes are not commited when using a recent git client Same issue here.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Emmanuel Vasseur edited a comment on JENKINS-22820 Changes are not commited when using a recent git client Same bug for me, with git 1.9.0, and a downgrade to git 1.8.2.3 fix the problem. Git command used by the plugin are prompted in the log file. git status is used just before git commit and git push. git status output of 1.8.2.3 and 1.9.0 version are different. Maybe the problem come from there. git status has a --porcelain option, dedicated for automated processing, with an output that not change between versions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Emmanuel Vasseur commented on JENKINS-22820 Changes are not commited when using a recent git client Same bug for me, with git 1.9.0, and a downgrade to git 1.8.2.3 fix the problem. Git command use by the plugin are prompted in the log file, and git status are used just before git commit and git push. git status output of 1.8.2.3 and 1.9.0 version are different. Maybe the problem come from there. git status has a --porcelain option, dedicated for automated processing, with an output that not change between versions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Nepomuk Seiler commented on JENKINS-22820 Changes are not commited when using a recent git client We are affected by this bug, too. Ubuntu 14.04, git 1.8.1.2 and the latest version for scm-plugin. Can you post the details of the git command? Or are they logged somewhere? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
