[JIRA] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Mark Waite commented on JENKINS-21137 git fetch does not have support for --progress option in 1.7.x version of git client binary Wouldn't you be better served by upgrading your git version on Ubuntu 10.04 LTS by using the instructions from askubuntu.com ? http://askubuntu.com/questions/333095/install-a-more-recent-version-of-git-on-a-lts 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Mark Waite edited a comment on JENKINS-21137 git fetch does not have support for --progress option in 1.7.x version of git client binary Wouldn't you be better served by upgrading your git version on Ubuntu 10.04 LTS by using the instructions from askubuntu.com ? http://askubuntu.com/questions/333095/install-a-more-recent-version-of-git-on-a-lts I admit that it is using a PPA to upgrade that package, but I suspect that you can upgrade your git version using that technique without disrupting the rest of the operating system. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Mark Waite commented on JENKINS-21137 git fetch does not have support for --progress option in 1.7.x version of git client binary I believe you have misunderstood what you are sacrificing by staying with an outdated version of a critical part of the Jenkins process. Nicolas noted that credentials support is not available in that git version. Substantial work has been put into the git and subversion plugins to support credentials. It may not be relevant to you, but it is relevant to the larger community of Jenkins users. If you are unwilling to update git, then you could evaluate the recently added JGit support. It is not yet full featured, but when a feature is missing it will generally tell you clearly that the feature is missing. If neither of those meet your needs then you will probably need to pin an older version of the git plugin and accept that the new features won't be available to you. 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/groups/opt_out.
[JIRA] [git] (JENKINS-21270) Add licenses to jenkins core and plugins
Mark Waite updated JENKINS-21270 Add licenses to jenkins core and plugins Change By: Mark Waite (16/Feb/14 5:17 AM) Component/s: git-client 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/groups/opt_out.
[JIRA] [github-api] (JENKINS-21270) Add licenses to jenkins core and plugins
Mark Waite commented on JENKINS-21270 Add licenses to jenkins core and plugins Removed git-plugin and git-client-plugin after confirming that both those plugins include a license section in their pom.xml. 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/groups/opt_out.
[JIRA] [github-api] (JENKINS-21270) Add licenses to jenkins core and plugins
Mark Waite updated JENKINS-21270 Add licenses to jenkins core and plugins Change By: Mark Waite (16/Feb/14 5:18 AM) Component/s: git 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Mark Waite closed JENKINS-21137 as Wont Fix git fetch does not have support for --progress option in 1.7.x version of git client binary Change By: Mark Waite (16/Feb/14 5:23 AM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Mark Waite resolved JENKINS-21137 as Wont Fix git fetch does not have support for --progress option in 1.7.x version of git client binary Change By: Mark Waite (16/Feb/14 5:23 AM) Status: Reopened Resolved Resolution: WontFix 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21032) git executable should be determined by node, not by the host
Mark Waite commented on JENKINS-21032 git executable should be determined by node, not by the host As far as I can tell, the default git executable is "git", not git.exe. That works on both Windows and Linux if the PATH setting includes the directory which contains the git executable. I assume your master node is a Windows machine with a Linux slave, and you set the Git location in the Jenkins global configuration to either be git.exe, or to be c:\Program Files\Git\bin\git.exe. If you'll set it to "git" rather than "git.exe" (or leave it unset), I believe it will work in both environments. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-19294) Build tagging does not work when using a local subdirectory for the GIT repo
Mark Waite closed JENKINS-19294 as Fixed Build tagging does not work when using a local subdirectory for the GIT repo Change By: Mark Waite (16/Feb/14 5:41 AM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-19294) Build tagging does not work when using a local subdirectory for the GIT repo
Mark Waite resolved JENKINS-19294 as Fixed Build tagging does not work when using a local subdirectory for the GIT repo Confirmed that I'm able to tag each build using the JGit implementation in git-client-plugin 1.6.2 and git-plugin 2.0.1 Change By: Mark Waite (16/Feb/14 5:41 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21015) NullPointerException in Jenkins Git Plugin
Mark Waite closed JENKINS-21015 as Fixed NullPointerException in Jenkins Git Plugin Change By: Mark Waite (16/Feb/14 5:44 AM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21015) NullPointerException in Jenkins Git Plugin
Mark Waite resolved JENKINS-21015 as Fixed NullPointerException in Jenkins Git Plugin Fixed in git-client-plugin 1.6.2, and possibly was already fixed in 1.6.1 Change By: Mark Waite (16/Feb/14 5:43 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx
Mark Waite commented on JENKINS-21369 Git client fails to remove files/directories with git clean -fdx Can you provide more details that would make this a repeatable bug? The stack trace shows you are using the command line git implementation. That implementation has no known problems with leaving files open. If you can provide a repeatable case, it has a much better chance of being investigated. The JGit implementation has known problems with leaving files open (see JENKINS-19994). There is also a risk that some other program is keeping the files open. There were cases in the past where a virus scanner prevented a directory from being deleted because it was keeping one or more files open from the directory. 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/groups/opt_out.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Mark Waite updated JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Change By: Mark Waite (17/Feb/14 11:58 AM) Component/s: core Component/s: git 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21032) git executable should be determined by node, not by the host
Mark Waite resolved JENKINS-21032 as Not A Defect git executable should be determined by node, not by the host The user has configured the Jenkins master incorrectly. This is not a bug, but rather an incorrect configuration. Change By: Mark Waite (17/Feb/14 12:10 PM) Status: Open Resolved Resolution: NotADefect 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21032) git executable should be determined by node, not by the host
Mark Waite closed JENKINS-21032 as Not A Defect git executable should be determined by node, not by the host Change By: Mark Waite (17/Feb/14 12:10 PM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails http://stackoverflow.com/questions/5343068/is-there-a-way-to-skip-password-typing-when-using-https-github describes alternatives based on the version of git you are running. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21745) [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL
Mark Waite closed JENKINS-21745 as Fixed [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL Change By: Mark Waite (17/Feb/14 12:15 PM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21745) [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL
Mark Waite resolved JENKINS-21745 as Fixed [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL Marking this issue as resolved, since the submitter noted that it was a configuration error, not a bug in the git-client plugin. Change By: Mark Waite (17/Feb/14 12:14 PM) 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21520) NoClassDefFoundError in git client 1.6.1
Mark Waite commented on JENKINS-21520 NoClassDefFoundError in git client 1.6.1 The related bug report has been closed as a configuration error. Have you found a configuration related solution to this problem as well? If not, can you provide more details about the configuration you're running? Have you installed the latest version of the plugins (including credentials)? Are any of your plugins disabled? Are any of your plugins pinned to older 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-19921) Git clone fails with JGit and SSH Credentials
Mark Waite commented on JENKINS-19921 Git clone fails with JGit and SSH Credentials Could you check to see if this problem still exists in git-client-plugin 1.6.2 and in git-plugin 2.0.1? A number of other authentication issues have been resolved since this bug was reported, and this one may have been resolved as well. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Mark Waite updated JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH Removed git-client and git-parameter since the definition of the GIT_BRANCH environment variable is in git-plugin Change By: Mark Waite (17/Feb/14 12:26 PM) Labels: git git-client Component/s: git-client Component/s: git-parameter 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/groups/opt_out.
[JIRA] [git] (JENKINS-21298) Git polling not ignoring excluded users
Mark Waite updated JENKINS-21298 Git polling not ignoring excluded users Assigned to git component, since exclusion processing is handled in git-plugin rather than in git-client-plugin. Change By: Mark Waite (17/Feb/14 12:28 PM) Labels: git git-clientgitplugin Component/s: git Component/s: git-client 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Mark Waite commented on JENKINS-20196 Failed to connect to URL (status = 404) Is this still an issue with git-plugin 2.0.1 and git-client-plugin 1.6.2? I'm able to insert the bitbucket user name and password into my https URL and it works as expected. I used https://markewaite:mypassw...@bitbucket.org/markewaite/git-client-plugin.git to check that works. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21469) Change from git clone to init+fetch makes clone from local GIT mirror a lot slower
Mark Waite commented on JENKINS-21469 Change from git clone to init+fetch makes clone from local GIT mirror a lot slower Won't the reference repository option available in "Advanced clone options" give you most of the same performance benefits? 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20614) Git client discards the exception message on error case in HttpClient
Mark Waite resolved JENKINS-20614 as Fixed Git client discards the exception message on error case in HttpClient The method has been replaced in the current implementation and now includes the generated exception in the GitException which is thrown from the checkCredentials() method. Change By: Mark Waite (17/Feb/14 12:48 PM) 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20614) Git client discards the exception message on error case in HttpClient
Mark Waite closed JENKINS-20614 as Fixed Git client discards the exception message on error case in HttpClient Change By: Mark Waite (17/Feb/14 12:48 PM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails Is the Windows machine running the Jenkins process (master or slave) as a service? JENKINS-20356 reports that credentials don't work as expected on Windows when the Jenkins process is running as a service. Jenkins behaves differently on Windows and Linux in many cases, most often due to platform differences (symbolic links are handled quite differently between the two platforms, open files are handled quite differently between the two platforms, etc.). 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21469) Change from git clone to init+fetch makes clone from local GIT mirror a lot slower
Mark Waite commented on JENKINS-21469 Change from git clone to init+fetch makes clone from local GIT mirror a lot slower I believe that should be sufficient. The --reference argument is not precisely the same as the --local argument, but I've seen significantly faster and smaller clones of large repositories since I've been using the --reference argument to refer to a bare repository copy which is kept on each of the slaves. 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/groups/opt_out.
[JIRA] [git] (JENKINS-21057) Cannot checkout git repository with submodules: FATAL: No remotes found!
Mark Waite closed JENKINS-21057 as Fixed Cannot checkout git repository with submodules: FATAL: No remotes found! Change By: Mark Waite (17/Feb/14 2:03 PM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git] (JENKINS-21057) Cannot checkout git repository with submodules: FATAL: No remotes found!
Mark Waite resolved JENKINS-21057 as Fixed Cannot checkout git repository with submodules: FATAL: No remotes found! git-plugin 2.0.1 and git-client-plugin 1.6.2 include the fix for this. Future versions of git-client-plugin (after 1.6.2) will have the further refinement that the plugin consistently assigns a remote when cloning, whether using JGit or command line git, and whether the internal implementation is a clone or an init and fetch. Change By: Mark Waite (17/Feb/14 2:03 PM) 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/groups/opt_out.
[JIRA] [core] (JENKINS-5065) Installing Hudson as a windows service on Vista 64 Bit
Mark Waite resolved JENKINS-5065 as Fixed Installing Hudson as a windows service on Vista 64 Bit Resolving this bug because Windows Vista is no longer a relevant operating system Windows 7 installs and runs as a service with 1.532.2 (and earlier) Other Windows operating systems are expected to work just as reliably Change By: Mark Waite (17/Feb/14 2:07 PM) Status: Reopened 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/groups/opt_out.
[JIRA] [core] (JENKINS-5065) Installing Hudson as a windows service on Vista 64 Bit
Mark Waite closed JENKINS-5065 as Fixed Installing Hudson as a windows service on Vista 64 Bit Change By: Mark Waite (17/Feb/14 2:07 PM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21469) Change from git clone to init+fetch makes clone from local GIT mirror a lot slower
Mark Waite commented on JENKINS-21469 Change from git clone to init+fetch makes clone from local GIT mirror a lot slower I'm of the opposite opinion. I think the "--local" option is unintuitive in a Jenkins context, since it seems it will only work if the repository URL is a path to a repository on the same file system as the Jenkins workspace. I rarely have a Jenkins environment with no slaves, and when I add the slaves, that "same file system" requirement is no longer a workable requirement. The reference option allows me to use the same configuration on the job whether it executes on the master or the slave, and I get the benefit of the reference repository if the referenced bare repository is available. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21469) Change from git clone to init+fetch makes clone from local GIT mirror a lot slower
Mark Waite commented on JENKINS-21469 Change from git clone to init+fetch makes clone from local GIT mirror a lot slower If that's not workable for you, you could submit a pull request with unit tests and the code change to implement the --local option to meet your needs. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails I rarely run Jenkins as a service on any of the Windows machines I configure. Most of the products which I need to build and test are working from the assumption that if they are running on Windows they have access to the Windows Desktop. Access to the Windows Desktop is most directly available by running the Jenkins master and Jenkins slaves from a command prompt on the Windows Desktop. I realize that there is a setting which allows a service to interact with the Desktop, but that is not the typical environment where my programs run. They are more likely to run on a real desktop, as real desktop programs. There have been several bugs reported which have been related to Jenkins running as a service on Windows. I prefer to avoid those bugs by running on the Desktop. I don't know why the git-client-plugin has this difference when running from a service or not. If I find a way to write automated tests of credentials in the git-client-plugin, that will probably also lead to a solution to JENKINS-20356. Until then, it will probably remain open as a bug. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails Your assertion that Jenkins is supposed to provide a service function solely within the context of a Windows service does not match my use model, nor does it match the use model of many Jenkins users. Jenkins provides the capability to build, test, and report results. Many test contexts require desktop access. As an example, Selenium tests need access to a desktop so that they can drive the web browser. Desktop applications often assume desktop access even when running in test mode. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20818) git plugin 2.0 started giving error to connect git over https
Mark Waite commented on JENKINS-20818 git plugin 2.0 started giving error to connect git over https Could you check again with git-plugin 2.0.1 and git-client-plugin 1.6.2? The git-client-plugin credentials implementation is more mature now and has been confirmed to work over https with or without credentials to GitHub and to bitbucket. There is a known bug ( JENKINS-20356 ) that the cloning with credentials does not work when Jenkins is running as a Windows service. There may also be issues with self-signed certificates on https servers, though I don't have access to a server with a self-signed certificate for testing. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20861) git plugin 2.0 does not correctly migrate 1.5 configs using reference repo option
Mark Waite resolved JENKINS-20861 as Fixed git plugin 2.0 does not correctly migrate 1.5 configs using reference repo option Released with git-client-plugin 1.62 or earlier. Change By: Mark Waite (17/Feb/14 2:59 PM) 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/groups/opt_out.
[JIRA] [git] (JENKINS-20861) git plugin 2.0 does not correctly migrate 1.5 configs using reference repo option
Mark Waite closed JENKINS-20861 as Fixed git plugin 2.0 does not correctly migrate 1.5 configs using reference repo option Change By: Mark Waite (17/Feb/14 3:00 PM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails This exchange seems to be no longer useful. It seems you will continue to insist that I'm on the wrong path if I require desktop access for tests. I've invested many years contributing to Jenkins, using Jenkins, and administering continuous integration servers. I'm comfortable that mine is not the only use model, but am just as comfortable that the use model you're proposing is also not the only use model. The Selenium test users (including Jenkins' own testing with Selenium) would likely disagree with you, as would all those users who use the Xvnc plugin on Linux. I'll resume trying to contribute to Jenkins, without worrying about your perceptions of how I use 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/groups/opt_out.
[JIRA] [core] (JENKINS-20204) Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file
Mark Waite commented on JENKINS-20204 Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file As far as I can tell, Oracle decided that unsigned rich internet applications (RIA) should not be allowed. They displayed warnings to users in JDK 1.7.0_45, alerting that a future JRE would change the warning to an error. They changed the warning to an error in JDK 1.7.0_51. I'm not an expert on RIA security, but I'm sure Kohsuke and other Jenkins maintainers would be more than happy to receive pull requests to fix the issue. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21520) NoClassDefFoundError in git client 1.6.1
Mark Waite commented on JENKINS-21520 NoClassDefFoundError in git client 1.6.1 That's bad news. I'm not aware of any changes which should have altered the class loading. What version of Jenkins are you running? I'm currently using 1.532.2 (the long term support release) and have not done any experiments with the new versions (like 1.551). 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/groups/opt_out.
[JIRA] [git] (JENKINS-21845) Command git rev-parse /develop^{commit} returned status code 128
Mark Waite
commented on JENKINS-21845
Command git rev-parse /develop^{commit} returned status code 128
I think you may have a different issue than is described in that posting on the mailing list. The "ambiguous argument" may be due to the absence of a remote name in the call to "git rev-parse". The failing seems to be "git rev-parse /developAutoMerge^{commit}", but I think it should be something like "git rev-parse origin/developAutoMerge^{commit}".
In the "Advanced" section of the git repository portion of the job definition, you'll find a field labeled "Name". That field needs a value for the merge use case you're attempting. I set mine to "upstream" and "downstream" to remind myself which one should be the destination of the push.
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/groups/opt_out.
[JIRA] [git] (JENKINS-21553) Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL
Mark Waite commented on JENKINS-21553 Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL I tried to duplicate this problem with a maven test job using git-client-plugin as the git repository with Jenkins 1.532.2, git-client-plugin 1.6.2 and git-plugin 2.0.1. I could not duplicate the problem. The job creation steps I used were: Create new job named "JENKINS-21553-maven-https-NPE" - Maven job type Git source control, use "https://github.com/jenkinsci/git-client-plugin.git" as the repository maven version, use 3.1.1 downloaded from apache.org automatically maven goal, "-Dmaven.test.failure.ignore=true install" Can you provide a more detailed description of your configuration? What Jenkins and plugin versions were you using? Were you using an https server with a self-signed certificate? Does the same problem happen if you use the https URL I tried? 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/groups/opt_out.
[JIRA] [git] (JENKINS-21845) Command git rev-parse /develop^{commit} returned status code 128
Mark Waite
commented on JENKINS-21845
Command git rev-parse /develop^{commit} returned status code 128
Yes, you're right. Unless you're using multiple repositories in a single job, it is probably best to name the repository "origin" so that it will have the typical name provided by git as a default.
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/groups/opt_out.
[JIRA] [git] (JENKINS-21845) Command git rev-parse /develop^{commit} returned status code 128
Mark Waite
closed JENKINS-21845 as Not A Defect
Command git rev-parse /develop^{commit} returned status code 128
Change By:
Mark Waite
(18/Feb/14 1:47 PM)
Status:
Resolved
Closed
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/groups/opt_out.
[JIRA] [git] (JENKINS-21845) Command git rev-parse /develop^{commit} returned status code 128
Mark Waite
resolved JENKINS-21845 as Not A Defect
Command git rev-parse /develop^{commit} returned status code 128
It would be better if we could find a way to provide a much better error message than a failure from git rev-parse when the origin field is left empty, but I'm not sure if that failure message would be enough either.
Change By:
Mark Waite
(18/Feb/14 1:47 PM)
Status:
Open
Resolved
Resolution:
NotADefect
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/groups/opt_out.
[JIRA] [git] (JENKINS-20991) Git checkout fails in some projects
Mark Waite
edited a comment on JENKINS-20991
Git checkout fails in some projects
That message "Result has multiple lines" is not clear enough about what is really happening. Sorry about that.
I suspect the root cause of the problem is that the command "git rev-parse master^{commit}" (or some variant) is reporting more than one line of output. That is unexpected, since master^{commit} should report that the working repository used by Jenkins for that specific job has an ambiguously revision named "master". There are two or more things which can legitimately resolve the name "master^{commit}" for the "git rev-parse" command.
If you're interested in seeing the test case in the git-client-plugin which shows the problem, look at test_jenkins_11177 in https://github.com/jenkinsci/git-client-plugin/blob/master/src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java#L766 . The bug report which inspired that test was JENKINS-11177 .
I'm not sure what's causing the case you've detected, since that bug was fixed over 6 months ago. Could you run the "git rev-parse master^{commit}" command in that repository and attach its output? There must be more cases where that is not handled correctly.
Looking at the source code, and making guesses based on the stack trace, I think the problem comes from the revParse which is used to read the names of the branches.
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/groups/opt_out.
[JIRA] [git] (JENKINS-18303) Cannot do checkout of a git repository in BitBucket in Jenkins
Mark Waite resolved JENKINS-18303 as Fixed Cannot do checkout of a git repository in BitBucket in Jenkins The addition of credentials support to the git-client-plugin and the git-plugin has made this type of failure much less frequent. I have a bitbucket test job which regularly performs a checkout and build of the git-client-plugin source code from a copy I keep on bitbucket. Could you check if this bug is fixed with git-client-plugin 1.6.2 (or later) and git-plugin 2.0.1 (or later)? Change By: Mark Waite (18/Feb/14 1:58 PM) 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/groups/opt_out.
[JIRA] [git] (JENKINS-17413) Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instant
Mark Waite resolved JENKINS-17413 as Cannot Reproduce Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.git.GitSCM I tried to duplicate this problem using git-client-plugin 1.6.2 and git-plugin 2.0.1 without success. Does the original submitter or the first person who commented still see the problem with the most recent versions of those plugins? Change By: Mark Waite (18/Feb/14 2:07 PM) Status: Open Resolved Resolution: CannotReproduce 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/groups/opt_out.
[JIRA] [git] (JENKINS-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.
Mark Waite resolved JENKINS-16693 as Fixed Heap error while polling Git Plug-in after upgrade to 1.1.26. As far as I can tell, there are no uses of "git show" in the git-client-plugin 1.6.2 or in the git-plugin 2.0.1. There is a single use of the "git whatchanged" command which might cause this type of problem, but was not listed in the original analysis of the bug. Can the original submitter or others who have seen the problem confirm it is fixed? Change By: Mark Waite (18/Feb/14 2:16 PM) 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/groups/opt_out.
[JIRA] [git] (JENKINS-16523) Git plugin fails with NullPointerException (Error trying to determine the git version: Error performing command: --version)
Mark Waite resolved JENKINS-16523 as Fixed Git plugin fails with NullPointerException (Error trying to determine the git version: Error performing command: --version) The current git-client-plugin and git-plugin releases do not call "git --version", so I believe this is resolved Change By: Mark Waite (18/Feb/14 2:20 PM) 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/groups/opt_out.
[JIRA] [git] (JENKINS-15020) Fails to build a successful build
Mark Waite resolved JENKINS-15020 as Fixed Fails to build a successful build The current git-client-plugin and git-plugin no longer call git --version, so I believe this is resolved. Change By: Mark Waite (18/Feb/14 2:20 PM) 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/groups/opt_out.
[JIRA] [git] (JENKINS-12703) jenkins and git over windows7 permission denied
Mark Waite closed JENKINS-12703 as Fixed jenkins and git over windows7 permission denied Change By: Mark Waite (18/Feb/14 2:24 PM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git] (JENKINS-12703) jenkins and git over windows7 permission denied
Mark Waite resolved JENKINS-12703 as Fixed jenkins and git over windows7 permission denied Credentials support has been added to git-client-plugin and git-plugin to simplify both the use and the diagnosis of this type of failure. Try credentials with the most recent plugins and the long term support version of Jenkins. Change By: Mark Waite (18/Feb/14 2:24 PM) 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/groups/opt_out.
[JIRA] [git] (JENKINS-12103) git polling constantly triggers for new (empty) git repos
Mark Waite resolved JENKINS-12103 as Fixed git polling constantly triggers for new (empty) git repos As far as I can tell from my initial verification attempt, this bug is resolved in git-plugin 2.0.1 and git-client-plugin 1.6.2. I don't have a gerrit server, so I created an empty bare repository using git protocol on my Debian git server, then defined a job which read that git protocol repository. I ran the job interactively once. It failed because there was no version to build. I then confirmed that the polling did not cause further jobs to be launched. I think failing because there is no version to build is a reasonable behavior, since an empty repository is quite exceptional and I'd rather have the failure indicate that exceptional condition, rather than having to read log files to realize that a successful job had no revision to build. Change By: Mark Waite (18/Feb/14 2:33 PM) 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/groups/opt_out.
[JIRA] [git] (JENKINS-12103) git polling constantly triggers for new (empty) git repos
Mark Waite closed JENKINS-12103 as Fixed git polling constantly triggers for new (empty) git repos Change By: Mark Waite (18/Feb/14 2:33 PM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git] (JENKINS-17413) Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instant
Mark Waite closed JENKINS-17413 as Cannot Reproduce Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.git.GitSCM Unfortunately, I don't think the exception you were seeing is related to the refspec. I'm not sure what causes those types of JSON conversion errors, but the cases I've detected have seem to be related to jobs defined with git-plugin 1.x versions that are now being edited with git-plugin 2.x. There were significant improvements in usability with git-plugin 2.x, but those improvements caused some compatibility changes. Change By: Mark Waite (18/Feb/14 2:36 PM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21139) Git client fails to handle slashes in branch refs
Mark Waite closed JENKINS-21139 as Fixed Git client fails to handle slashes in branch refs Change By: Mark Waite (18/Feb/14 2:40 PM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21139) Git client fails to handle slashes in branch refs
Mark Waite resolved JENKINS-21139 as Fixed Git client fails to handle slashes in branch refs Submitter notes that the problem was a configuration issue. Previous versions of the plugin assumed "origin" if the remote name field from the advanced tab was left blank. Current versions seem to require that field when referring to the remote. Change By: Mark Waite (18/Feb/14 2:40 PM) 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/groups/opt_out.
[JIRA] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite updated JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect Removed git-client-plugin from the list of components, since the bitbucket URL is included in the git-plugin, not in the git-client-plugin Change By: Mark Waite (18/Feb/14 2:41 PM) Component/s: git-client 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/groups/opt_out.
[JIRA] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect The bug was originally assigned to two components, the git-plugin and the git-client-plugin. I investigated the source code and confirmed that in order to fix this bug, the only component that needs to change is the git-plugin, not the git-client-plugin. Since no change would be required to the git-client-plugin to fix this bug, I removed it from list of components. 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/groups/opt_out.
[JIRA] [git] (JENKINS-21774) Jenkins Git plugin some times shows incorrect and very long changelist (files) in commit
Mark Waite commented on JENKINS-21774 Jenkins Git plugin some times shows incorrect and very long changelist (files) in commit Interesting. I'll need to learn more about the specific impact of "shallow clone" on the contents of a git repository. I thought that "shallow clone" was only retrieving a subset of the history, so I would expect it to have some risk of not correctly detecting the "before" state of the repository due to the shallow clone. 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/groups/opt_out.
[JIRA] [git] (JENKINS-21168) Git core.symlinks option not correctly auto-detected on Windows
Mark Waite commented on JENKINS-21168 Git core.symlinks option not correctly auto-detected on Windows Using a default msysgit installation on multiple Windows machines, I was unable to duplicate this problem with git-client-plugin 1.6.2 and git-plugin 2.0.1. When the checkout is performed on Windows 2011 home server, Windows 7, and Windows 8.1 (in my Jenkins environment) with a symbolic link to a file in the root directory, and with a symbolic link to a directory in the root directory, the checkout is successful. The Windows based checkout of the symbolic links is not very useful on Windows, but it does not prevent the checkout. Can you provide any further hints that could help with verifying the bug still exists? 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/groups/opt_out.
[JIRA] [git] (JENKINS-21168) Git core.symlinks option not correctly auto-detected on Windows
Mark Waite commented on JENKINS-21168 Git core.symlinks option not correctly auto-detected on Windows The git plugin has two alternative implementations. Both implementations are available, so you can choose between them. The default implementation uses command line git. It assumes you already have git installed and configured on your computer. It is the most feature-rich implementation, but requires that you install and configure git. That is not hard, but it is one more step in the process. The JGit implementation uses a pure Java implementation of git. It does not require any git installation on your computer. It is not as feature-rich, with several operations (like push, and reference repositories, and shallow clones) not yet implemented. However, it is good at declaring in the console output if you requested something which is not implemented. The JGit implementation is not visible to jobs until it is added to the global Jenkins configuration. Once it has been added (through http://localhost:8080/configure, for example), then you can select which git implementation you will use on a job by job basis. 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/groups/opt_out.
[JIRA] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect That is correct. Alternately, you could fork the git plugin (https://github.com/jenkinsci/git-plugin) on github, make the change in your forked copy, verify the change works, push that change to your forked copy, and submit a pull request for the change. I've been impressed how easy it is to propose small changes to a Jenkins plugin. The maintainer of the git plugin is very responsive and reviews pull requests quickly. 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/groups/opt_out.
[JIRA] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect The URL in the job definition does not match the URL that I see in the source code. That means I don't understand the source code well enough to map the string you're seeing as default to the string in the source code. It will require a debugger and some time investigating actual behavior, rather than just reading the source code. 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] [git] (JENKINS-24086) Add GIT_SPARSE or similar environment variable
Mark Waite commented on JENKINS-24086 Add GIT_SPARSE or similar environment variable Can't you just read the contents of .git/info/sparse-checkout? That is the file which git uses to record the definition of the sparse checkout, and it doesn't require that you determine how many environment variables were set. 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] [git] (JENKINS-24086) Add GIT_SPARSE or similar environment variable
Mark Waite resolved JENKINS-24086 as Wont Fix Add GIT_SPARSE or similar environment variable Change By: Mark Waite (02/Aug/14 12:42 AM) Status: Open Resolved Resolution: WontFix 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] [git] (JENKINS-24082) Be able to force push for branch on git publisher
Mark Waite commented on JENKINS-24082 Be able to force push for branch on git publisher Force push from a Jenkins job seems like a very dangerous option. Can you describe further why you want a Jenkins job to be able to delete history from a repository? The Jenkins plugin can merge, and can push that merge result, so long as no intervening commit has been pushed to the destination branch in the central repository. If an intervening commit has been pushed to the destination branch, then the Jenkins job is not allowed to push the merge result because it would overwrite the intervening commit with that forced push. 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] [git] (JENKINS-21886) Push notifications don't work if JOB_NAME variable is in repository URL
Mark Waite
commented on JENKINS-21886
Push notifications dont work if JOB_NAME variable is in repository URL
I'm able to duplicate this bug. The remote polling works, and when the next polling happens, the changes are detected. The push notifications seem to be the only thing that is ignored.
Steps I took to duplicate the problem:
Create a freestyle project named "bin"
Configure git as its SCM, with git://wheezy64b/git/mwaite/${JOB_NAME}.git as the git repository URL
Configure the job to poll SCM every minute (for testing purposes)
Add a build step to execute "git log -n 1"
Save the job
Wait 1 minute for first poll to build the job
After first build is complete, switch polling from every minute to @monthly
Push a change to the repository
Run "curl http://centos7x64:8080/git/notifyCommit?url="">"
Confirm that the job does not start
Change the job polling frequency to once a minute
Wait 1 minute, confirm the job detects the change and runs correctly
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] [git] (JENKINS-23791) Wrong timestamp retrieved from git ChangeSet
Mark Waite closed JENKINS-23791 as Fixed Wrong timestamp retrieved from git ChangeSet Fixed in git plugin 2.2.4 Change By: Mark Waite (02/Aug/14 7:11 PM) Status: Resolved Closed 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] [git] (JENKINS-23179) git pre-merge fails with matrix project
Mark Waite commented on JENKINS-23179 git pre-merge fails with matrix project Will be available in the next git plugin release after 2.2.4 (probably 2.2.5). 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] [git] (JENKINS-11337) Git plugin only triggers a build for one branch
Mark Waite closed JENKINS-11337 as Fixed Git plugin only triggers a build for one branch Was fixed a long time ago. Confirmed still working as expected with git client plugin 1.10.1 and git plugin 2.2.2 Change By: Mark Waite (03/Aug/14 3:46 PM) Status: Resolved Closed 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] [gitlab-hook] (JENKINS-23743) Failure on Git Polling Log when using Linux Master and Windows Slave
Mark Waite commented on JENKINS-23743 Failure on Git Polling Log when using Linux Master and Windows Slave No change was made to the plugin to resolve this issue. Marco Lovato reported that someone had changed the configuration of his system. Once he changed the configuration back to the original, the problem was resolved. If you have a case which shows this type of problem and can provide steps which will duplicate the problem, please open a new bug report with those steps described in detail. 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] [bitbucket] (JENKINS-24151) Jenkins timing out to connect to Bitbucket when building project
Mark Waite closed JENKINS-24151 as Not A Defect Jenkins timing out to connect to Bitbucket when building project Change By: Mark Waite (08/Aug/14 4:06 AM) Status: Resolved Closed 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] [bitbucket] (JENKINS-24151) Jenkins timing out to connect to Bitbucket when building project
Mark Waite resolved JENKINS-24151 as Not A Defect Jenkins timing out to connect to Bitbucket when building project Please use the jenkinsci-users mailing list rather than a bug report when requesting help. Many more people read the mailing list than read bug reports, so you are much more likely to receive help there. Change By: Mark Waite (08/Aug/14 4:06 AM) Status: Open Resolved Resolution: NotADefect 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] [git] (JENKINS-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)
Mark Waite resolved JENKINS-24125 as Not A Defect Git Polling fails for job restricted to Mac OS X slave (with Windows master) I strongly suspect that you have a configuration problem. The "ls-remote" command is executed on the master node, though it likely uses the git executable defined by that job. Please confirm that your master node has the git executable correctly specified for the master node (git.exe), and that the OS/X node has the git executable correctly specified for it (/usr/local/bin/git). Change By: Mark Waite (08/Aug/14 4:12 AM) Status: Open Resolved Resolution: NotADefect 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] [git] (JENKINS-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)
Mark Waite edited a comment on JENKINS-24125 Git Polling fails for job restricted to Mac OS X slave (with Windows master) I strongly suspect that you have a configuration problem. The "ls-remote" command is executed on the master node, though it likely uses the git executable defined by that job. Please confirm that your master node has the git executable correctly specified for the master node (git.exe), and that the OS/X node has the git executable correctly specified for it (/usr/local/bin/git). The location of the default git executable is set in the node configuration page for the OS/X slave node. It needs to be "/usr/local/bin/git". The location of the default git executable for the master node needs to be configured in the "Git installations" section of the "Manage Jenkins" page. 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] [git] (JENKINS-24144) reference repos appear broken
Mark Waite edited a comment on JENKINS-24144 reference repos appear broken I just confirmed that using a reference repository with my 3 GB repository makes the fetch portion of the checkout almost instantaneous on the Linux slave I'm using. I use reference repositories on Windows machines as well with a 7 GB repository at work, so I'm reasonably confident that reference repositories are honored on both Windows and Linux. I configured a copy of that job to use shallow clone and it also completed the "git fetch" portion of the job very quickly. I see from your log that it was generated on Windows, yet the bug report says it was visible on both Windows and Linux. Is the combination of reference and shallow not matching your expectations on both platforms, or only on one? Are you attempting to provide a syntax for the reference repository which will work on both Windows and Linux within the same job? I've not found such a syntax in any of my experiments. 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] [git] (JENKINS-24144) reference repos appear broken
Mark Waite commented on JENKINS-24144 reference repos appear broken I just confirmed that using a reference repository with my 3 GB repository makes the fetch portion of the checkout almost instantaneous on the Linux slave I'm using. I use reference repositories on Windows machines as well with a 7 GB repository at work, so I'm reasonably confident that reference repositories are honored on both Windows and Linux. I configured a copy of that job to use shallow clone and it also completed the "git fetch" portion of the job very quickly. I see from your log that it was generated on Windows, yet the bug report says it was visible on both Windows and Linux. Are you attempting to provide a syntax for the reference repository which will work on both Windows and Linux within the same job? I've not found such a syntax in any of my experiments. 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] [git] (JENKINS-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)
Mark Waite commented on JENKINS-24125 Git Polling fails for job restricted to Mac OS X slave (with Windows master) The master Jenkins git location is the default and is applied to the master and all slaves (as the default). That usually leads to me preferring to have the default be "git", and then if I'm running a Windows master, I assure that the Jenkins process includes the C:\Program Files(x86)\Git\bin directory in its path. In your case, I suspect your default is "git.exe", and when that is attempted as the default on OS/X, there is no "git.exe". Thus, if you want the system wide default for the git program to be "git.exe" (possibly because most of your machines will be Windows based), then you'll need to define the git location for each slave that is not Windows. You need to override tool locations if the default tool location does not work for that slave. You defined the default as "git.exe" and that only work for Windows. 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] [git] (JENKINS-24179) Intermittent git timeouts with error Could not create directory 'c/users/user/.ssh'
Mark Waite resolved JENKINS-24179 as Wont Fix Intermittent git timeouts with error Could not create directory c/users/user/.ssh As far as I can tell from the command output, the "git fetch" command itself is reporting on its "stderr" that it could not create the .ssh directory. The git client plugin uses the command line git implementation, and is thus connected to bugs which may exist in the command line git implementation. In this case, the command line implementation appears to have a race condition where it attempts to create a directory that already exists. You will probably need to take this sort of bug to the msysgit community for a fix. There is not much which the git client plugin can do to prevent the problem. You could experiment with JGit to see if it shows the same issues, and if it behaves any better in your use case. There are still feature gaps in the JGit portion of the git client plugin, but it is worth a "test drive" to see if it will meet your use cases. Change By: Mark Waite (08/Aug/14 5:06 PM) Status: Open Resolved Resolution: WontFix 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] [git] (JENKINS-24179) Intermittent git timeouts with error Could not create directory 'c/users/user/.ssh'
Mark Waite closed JENKINS-24179 as Wont Fix Intermittent git timeouts with error Could not create directory c/users/user/.ssh Your suspicion matches with my suspicion. I would still be interested to hear if the JGit implementation used in the plugin is able to address the use case you're running. The JGit implementation is pure java, so it is slower than the command line git implementation, but since it is pure Java, it does not require a git command line client. Change By: Mark Waite (08/Aug/14 6:10 PM) Status: Resolved Closed 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] [git] (JENKINS-24179) Intermittent git timeouts with error Could not create directory 'c/users/user/.ssh'
Mark Waite commented on JENKINS-24179 Intermittent git timeouts with error Could not create directory c/users/user/.ssh The git commands are logged more clearly with the current git client plugin (1.10.2) than they are with the version you're using. 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] [git] (JENKINS-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)
Mark Waite closed JENKINS-24125 as Not A Defect Git Polling fails for job restricted to Mac OS X slave (with Windows master) The git plugin defaults to use "fast remote polling" to reduce the disc and I/O overhead of polling for updates. That fast remote polling is performed on the master. If you would rather not use fast remote polling, you can add "Additional Behaviours" to "Force polling using workspace". That will then require a workspace before performing a poll, and will heed the platform restrictions of the job definition. That restriction will cause polling to be significantly slower in certain cases, but it will assure the job restriction is honored by the polling process. Change By: Mark Waite (08/Aug/14 10:49 PM) Status: Resolved Closed 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] [bitbucket] (JENKINS-24153) publish with MSBuild use wrong branch in latest Jenkins
Mark Waite closed JENKINS-24153 as Cannot Reproduce publish with MSBuild use wrong branch in latest Jenkins Change By: Mark Waite (09/Aug/14 1:23 PM) Status: Resolved Closed 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] [bitbucket] (JENKINS-24153) publish with MSBuild use wrong branch in latest Jenkins
Mark Waite resolved JENKINS-24153 as Cannot Reproduce publish with MSBuild use wrong branch in latest Jenkins Considering how serious such a problem would be, and the number of users of the git plugin (now over 40 000 installations worldwide), I'm confident this is a user error. Closing it as "Cannot reproduce" Change By: Mark Waite (09/Aug/14 1:23 PM) Status: Open Resolved Resolution: CannotReproduce 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] [git] (JENKINS-20392) Git plugin 2.0 Recent Changes is always empty in merge job
Mark Waite
updated JENKINS-20392
Git plugin 2.0 Recent Changes is always empty in merge job
Change By:
Mark Waite
(09/Aug/14 1:36 PM)
Description:
TheRecentChangeslistinmergejobswhichusetheGitpluginarenowempty.PriortoGitplugin2.0,theRecentChangeslistshowedthosechangeswhosemergewasattempted,whetherthemergesucceededornotStepstoduplicatetheproblem(withapologiesforthenumberofsteps)#CreateabaregitrepoonthemasternodeasJenkinsuser##{{rm-rf/tmp/changes.git/tmp/changes}}##{{gitinit--bare/tmp/changes.git}}##{{echo#!/bin/sh/tmp/changes.git/hooks/post-receive}}##echocurl--silenthttp://127.0.0.1:8080/git/notifyCommit?url="">
\
/tmp/changes.git/hooks/post-receive##{{chmoda+x/tmp/changes.git/hooks/post-receive}}##{{cd/tmp}}##{{gitclonechanges.git}}##{{cdchanges}}##{{echoGitplugin2.0nolongershowschangesfrommergesREADME}}##{{gitaddREADME}}##{{gitcommit-mAddREADMEtodescribethisrepositoryREADME}}##{{gitpushoriginmaster}}#CreateaJenkinsmergejobusingthatbaregitrepo##Createanewfree-stylesoftwareprojectmerge-changes##Restrictwherethisprojectcanberun###Label_expression_:master##Gitsourcecodemanagementsettings###RepositoryURL:/tmp/changes.git###Branchestobuild:\*/master\*##Additionalbehaviors:Mergebeforebuild###Nameofrepository:origin(erroronmergeifthisisblank-helpsaysshouldusedefault,butdidnt)###Branchtomergeto:master##PollSCM(forconveniencewiththegithookinstalledearlier)###H##Addpost-buildaction:GitPublisher###GitPublishersettingsMergeresults:YesBranches:#Branchestopush:master#Targetremotename:origin##Savethejob#BuildJenkinsjob##curl--silenthttp://127.0.0.1:8080/job/merge-changes/build?delay=0sec###NotethattheRecentChangeswillreportnochangesinanybuild#Createnewmaster-add-timestampbranchandcommitfromit##{{gitcheckout-bmaster-add-timestamp}}##{{datetimestamp}}##{{gitaddtimestamp}}##{{gitcommit-mAddtimestamptimestamp}}##{{gitpushoriginmaster-add-timestamp}}#Jenkinsjobruns,butRecentChangesstillreportsNochangesinanyofthebuilds#Confirmmasterbranchreceivedthemergeresult##{{gitcheckoutmaster}}##{{gitpull}}#Createnewmaster-add-timestamp2branchandcommitfromit##{{gitcheckout-bmaster-add-timestamp2}}##{{datetimestamp2}}##{{gitaddtimestamp2}}##{{gitcommit-mAddnewtimestamp2timestamp2}}##{{gitpushoriginmaster-add-timestamp2}}##BUG:Mergewillhappenandbepushed,butnochangelisted#Confirmmasterbranchreceivedthemergeresult##{{gitcheckoutmaster}}##{{gitpull}}
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] [git] (JENKINS-20392) Git plugin 2.0 Recent Changes is always empty in merge job
Mark Waite commented on JENKINS-20392 Git plugin 2.0 Recent Changes is always empty in merge job Sorry that I missed your request to evaluate your patch. I've compared the "before" and the "after" with your patch and much prefer the "after". Thanks! 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] [git] (JENKINS-20392) Git plugin 2.0 Recent Changes is always empty in merge job
Mark Waite resolved JENKINS-20392 as Fixed Git plugin 2.0 Recent Changes is always empty in merge job Fixed in next release of git plugin - 2.2.5 Change By: Mark Waite (09/Aug/14 2:51 PM) 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] [git] (JENKINS-20392) Git plugin 2.0 Recent Changes is always empty in merge job
Mark Waite closed JENKINS-20392 as Fixed Git plugin 2.0 Recent Changes is always empty in merge job Change By: Mark Waite (09/Aug/14 2:51 PM) Status: Resolved Closed 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] [git] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Mark Waite commented on JENKINS-20393 Git plugin 2.0 JGit implementation does not publish merge result Confirmed still an issue with git client plugin 1.10.1 and git plugin 2.2.4. 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] [git] (JENKINS-24144) reference repos appear broken
Mark Waite resolved JENKINS-24144 as Cannot Reproduce reference repos appear broken As far as I can tell from my experiments, reference repository and shallow clone both are working as expected, whether used individually or in combination. Change By: Mark Waite (09/Aug/14 7:56 PM) Status: Open Resolved Resolution: CannotReproduce 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] [git] (JENKINS-24144) reference repos appear broken
Mark Waite closed JENKINS-24144 as Cannot Reproduce reference repos appear broken Change By: Mark Waite (09/Aug/14 7:56 PM) Status: Resolved Closed 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] [git] (JENKINS-24144) reference repos appear broken
Mark Waite commented on JENKINS-24144 reference repos appear broken Ah, yes, I had not considered that as a possible bottleneck. The ssh client bundled with msysgit can't transfer more than about 1 MB per second. It is an older version of ssh and it is a lot of work to switch to a newer version. 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] [git] (JENKINS-24261) Assembla browser breaks config page
Mark Waite assigned JENKINS-24261 to Mark Waite Assembla browser breaks config page Change By: Mark Waite (15/Aug/14 12:00 PM) Assignee: NicolasDeLoof MarkWaite 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] [git] (JENKINS-24261) Assembla browser breaks config page
Mark Waite commented on JENKINS-24261 Assembla browser breaks config page Thanks for the report. The pull request that introduced Assembla (this commit and this commit) missed a few files. I obviously didn't test it well enough (shame on me). The author corrected the mistake, but it was after the release of the 2.2.4 version of the plugin. It will be fixed in the 2.2.5 version of the plugin. The commit which fixed it has been on github for almost two weeks (on both the master branch and the 2.2.x branch). I'll release 2.2.5 within the next few days to fix that 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.
