[JIRA] (JENKINS-13417) git-plugin: rev-parse dereferencing tags breaks on Windows

2012-05-23 Thread m...@lcorneliussen.de (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163127#comment-163127
 ] 

Lars Corneliussen commented on JENKINS-13417:
-

Same problem here - took me hours to find this... 

Workaround: Downloaded 1.1.15 from 
http://updates.jenkins-ci.org/download/plugins/git/,  renamed to git.jpi, put 
into JENKINS_HOME/plugins, then restarted - works fine.

 git-plugin: rev-parse dereferencing tags breaks on Windows
 --

 Key: JENKINS-13417
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13417
 Project: Jenkins
  Issue Type: Bug
  Components: git
 Environment: Windows 2008 R2 slave launched with cygwin ssh, cygwin 
 git
Reporter: Jay Berkenbilt
Assignee: Nicolas De Loof

 The change to GitAPI.java in commit 13f6038acc4fa5b5a62413155da6fc8cfcad3fe0 
 seems to break the git plugin for Windows, at least in some circumstances.  
 The syntax rev^{commit} gets mangled by cmd because ^ is a quote character.  
 This means that cmd passes rev{commit} to git, which as a cygwin executable 
 being run from Windows, further tries to do wildcard expansion and maps this 
 to revcommit.  Putting  around rev^{commit} empirically seems to work, 
 though I haven't tried it in the git plugin itself.
 This C fragment:
 {code}
 #include stdio.h
 int main(int argc, char* argv[])
 {
 int i;
 for (i = 0; i  argc; ++i)
 {
 printf(%s\n, argv[i]);
 }
 return 0;
 }
 {code}
 when compiled with mingw to a native Windows application (a.exe) and invoked 
 from cmd as a.exe a^{b} prints a{b}.  When the same fragment is compiled with 
 cygwin gcc to cygwin executable a.exe and is invoked the same way from cmd, 
 it prints ab.  Both print a^{b} when invoked from cmd as a.exe a^{b}.
 I'm not sure what the fix is here other than perhaps detecting that this is 
 windows and putting quotes around the argument in Windows.
 On another note, I left the Affects Version/s field blank.  My Jenkins 
 installation claims that it is using version 1.1.6.  Looking at the git repo 
 for the plugin, it appears that 1.1.6 should not have the ^{commit} fix, yet 
 running strings on 
 plugins/git/WEB-INF/classes/hudson/plugins/git/GitAPI.class clearly shows 
 that my git plugin has that change in it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-11964) [Regression] Cannot build a single module in a Maven multi-module job with Maven 3

2012-05-02 Thread m...@lcorneliussen.de (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-11964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162313#comment-162313
 ] 

Lars Corneliussen commented on JENKINS-11964:
-

How much work would it be?

 [Regression] Cannot build a single module in a Maven multi-module job with 
 Maven 3
 --

 Key: JENKINS-11964
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11964
 Project: Jenkins
  Issue Type: Bug
  Components: maven
Reporter: henryju
Assignee: olamy

 We have upgraded from Jenkins 1.399 to Jenkins 1.441. Our Maven jobs are now 
 run by Maven 3.0.3 instead of Maven 2.2.1.
 When a job is a Maven multi-module project, it is possible to run a single 
 submodule (on the job page, click on Modules, then start the build for a 
 given submodule). It was working fine with our old instance but now the build 
 fails with status ABORTED.
 See thread: 
 http://jenkins.361315.n4.nabble.com/Build-Maven-submodule-gt-ABORTED-td4128116.html
 Is it possible to reintroduce this feature?
 Thanks

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira