date:20140406















































Mark Waite
 commented on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision















I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for 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-22510) Clean After Checkout Results in Failed to Checkout Revision

Mark Waite
edited a comment on JENKINS-22510

Clean After Checkout Results in Failed to Checkout Revision

I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them. My attempts have persuaded me that I don't understand submodules. I used my fork of the git-client-plugin for my experiments.

Clone the repository

git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp

Checkout tests/getSubmodules

git checkout tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # Shows there is content in modules/ntp

Checkout master again

git checkout master
ls modules/ntp # reports an error, no content in modules/ntp

Create a branch containing a conflicting file

git checkout -b tests/notSubmodules
mkdir -p modules/ntp
echo "This is not a contribution" modules/ntp/CONTRIBUTING.md

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-22510) Clean After Checkout Results in Failed to Checkout Revision













































 
Mark Waite
 edited a comment on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision
















I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for my experiments.

Clone the repository


git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp



Checkout tests/getSubmodules


git checkout tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # Shows there is content in modules/ntp



Checkout master again


git checkout master # warns there are untracked files in modules directory
ls modules/ntp # shows content in modules/ntp is still there

git clean -xfd # skips modules/ntp and modules/firewall
ls modules/ntp # shows content in modules/ntp is still there

git clean -xffd # deletes modules/ntp and modules/firewall
ls modules/ntp # no content in modules/ntp



Create a branch containing a conflicting file


git checkout -b tests/notSubmodules
mkdir -p modules/ntp
echo "This is not a contribution"  modules/ntp/CONTRIBUTING.md





























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-22510) Clean After Checkout Results in Failed to Checkout Revision













































 
Mark Waite
 edited a comment on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision
















I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for my experiments.

Clone the repository


git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp



Checkout tests/getSubmodules


git checkout tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # Shows there is content in modules/ntp



Checkout master again


git checkout master # warns there are untracked files in modules directory
ls modules/ntp # shows content in modules/ntp is still there

git clean -xfd # skips modules/ntp and modules/firewall
ls modules/ntp # shows content in modules/ntp is still there

git clean -xffd # deletes modules/ntp and modules/firewall
ls modules/ntp # no content in modules/ntp



Checkout branch containing a conflicting file - works


git checkout tests/notSubmodules
ls modules/ntp # one file in modules/ntp



Checkout tests/getSubmodules again


git checkout tests/getSubmodules
git submodule update --init --recursive



Checkout branch containing a conflicting file - fails


git checkout tests/notSubmodules # fails - untracked files would be overwritten



Unfortunately, I've not yet found a sequence of "clean" and "checkout" commands which will allow me to switch from tests/getSubmodules to tests/notSubmodules.




























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-22510) Clean After Checkout Results in Failed to Checkout Revision













































 
Mark Waite
 edited a comment on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision
















I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for my experiments.

Clone the repository - works


git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp



Checkout tests/getSubmodules - works


git checkout tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # Shows there is content in modules/ntp



Checkout master again - works


git checkout master # warns there are untracked files in modules directory
ls modules/ntp # shows content in modules/ntp is still there

git clean -xfd # skips modules/ntp and modules/firewall
ls modules/ntp # shows content in modules/ntp is still there

git clean -xffd # deletes modules/ntp and modules/firewall
ls modules/ntp # no content in modules/ntp



Checkout branch containing a conflicting file - works


git checkout tests/notSubmodules
ls modules/ntp # one file in modules/ntp



Checkout tests/getSubmodules again - works


git checkout tests/getSubmodules
git submodule update --init --recursive



Checkout branch containing a conflicting file - fails


git checkout tests/notSubmodules # fails - untracked files would be overwritten



Unfortunately, I've not yet found a sequence of "clean" and "checkout" commands which will allow me to switch from tests/getSubmodules to tests/notSubmodules.

In that repository, the branch to branch transitions seem behave like this:



Current Branch  
Branch to Checkout  
 Result 


 master  
 tests/getSubmodules 
 ok  


 master  
 tests/notSubmodules 
 ok  


 tests/getSubmodules 
 master  
 ok  


 tests/notSubmodules 
 master  
 ok  


 tests/getSubmodules 
 tests/notSubmodules 
 fails   


 tests/notSubmodules 
 tests/getSubmodules 
 fails   





























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-22510) Clean After Checkout Results in Failed to Checkout Revision













































 
Mark Waite
 edited a comment on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision
















I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for my experiments.

Clone the repository - works


git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp



Checkout tests/getSubmodules - works


git checkout tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # Shows there is content in modules/ntp



Checkout master again - works


git checkout master # warns there are untracked files in modules directory
ls modules/ntp # shows content in modules/ntp is still there

git clean -xfd # skips modules/ntp and modules/firewall
ls modules/ntp # shows content in modules/ntp is still there

git clean -xffd # deletes modules/ntp and modules/firewall
ls modules/ntp # no content in modules/ntp



Checkout branch containing a conflicting file - works


git checkout tests/notSubmodules
ls modules/ntp # one file in modules/ntp



Checkout tests/getSubmodules again - works


git checkout tests/getSubmodules
git submodule update --init --recursive



Checkout branch containing a conflicting file - fails


git checkout tests/notSubmodules # fails - untracked files would be overwritten



Unfortunately, I've not yet found a sequence of "clean" and "checkout" commands which will allow me to switch from tests/getSubmodules to tests/notSubmodules.

In that repository, the branch to branch transitions seem behave like this:



Current Branch  
Branch to Checkout  
 Result 


 master  
 tests/getSubmodules 
 ok  


 master  
 tests/notSubmodules 
 ok  


 tests/getSubmodules 
 master  
 ok  


 tests/notSubmodules 
 master  
 ok  


 tests/getSubmodules 
 tests/notSubmodules 
 fails 


 tests/notSubmodules 
 tests/getSubmodules 
 fails 



However, the failure message I'm seeing is not the same as the failure message you're seeing.  I'm confident that means I don't understand enough about submodules.  Can you provide a similar series of steps (preferably using a fork of the git-client-plugin repository) to show your case?



























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-22510) Clean After Checkout Results in Failed to Checkout Revision













































 
Mark Waite
 edited a comment on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision
















I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for my experiments.

Clone the repository - works


git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp



Checkout tests/getSubmodules - works


git checkout tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # Shows there is content in modules/ntp



Checkout master again - works


git checkout master # warns there are untracked files in modules directory
ls modules/ntp # shows content in modules/ntp is still there

git clean -xfd # skips modules/ntp and modules/firewall
ls modules/ntp # shows content in modules/ntp is still there

git clean -xffd # deletes modules/ntp and modules/firewall
ls modules/ntp # no content in modules/ntp



Checkout branch containing a conflicting file - works


git checkout tests/notSubmodules
ls modules/ntp # one file in modules/ntp



Checkout tests/getSubmodules again - works


git checkout tests/getSubmodules
git submodule update --init --recursive



Checkout branch (force) containing a conflicting file - works


git checkout -f tests/notSubmodules # works - but warns unable to rmdir
git clean -xffd
ls modules/ntp # one file in modules/ntp as expected



Checkout tests/getSubmodules (force) - fails


git checkout -f tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # one file in modules/ntp - should be more files there



The working sequence in my case seems to be "force checkout, then use git clean -xffd".  That doesn't work for the transition from "getSubmodules" to "notSubmodules", but covers the other cases.  Even a clean before checkout does not work for the transition from "getSubmodules" to "notSubmodules" (as far as I can tell).  However, since my case does not duplicate your message, I'm not sure if you'll see the same behavior as I see.

In that repository, the branch to branch transitions seem to behave like this:



Current Branch  
Branch to Checkout  
 Result 


 master  
 tests/getSubmodules 
 ok  


 master  
 tests/notSubmodules 
 ok  


 tests/getSubmodules 
 master  
 ok  


 tests/notSubmodules 
 master  
 ok  


 tests/getSubmodules 
 tests/notSubmodules 
 fails 


 tests/notSubmodules 
 tests/getSubmodules 
 ok  



However, the failure message I'm seeing is not the same as the failure message you're seeing.  I'm confident that means I don't understand enough about submodules.  Can you provide a similar series of steps (preferably using a fork of the git-client-plugin repository) to show your case?



























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-22510) Clean After Checkout Results in Failed to Checkout Revision













































 
Mark Waite
 edited a comment on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision
















I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for my experiments.

Clone the repository - works


git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp



Checkout tests/getSubmodules - works


git checkout tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # Shows there is content in modules/ntp



Checkout master again - works


git checkout master # warns there are untracked files in modules directory
ls modules/ntp # shows content in modules/ntp is still there

git clean -xfd # skips modules/ntp and modules/firewall
ls modules/ntp # shows content in modules/ntp is still there

git clean -xffd # deletes modules/ntp and modules/firewall
ls modules/ntp # no content in modules/ntp



Checkout branch containing a conflicting file - works


git checkout tests/notSubmodules
ls modules/ntp # one file in modules/ntp



Checkout tests/getSubmodules again - works


git checkout tests/getSubmodules
git submodule update --init --recursive



Checkout branch (force) containing a conflicting file - works


git checkout -f tests/notSubmodules # works - but warns unable to rmdir
git clean -xffd
ls modules/ntp # one file in modules/ntp as expected



Checkout tests/getSubmodules (force) - fails


git checkout -f tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # one file in modules/ntp - should be more files there



The working sequence in my case seems to be "force checkout, then use git clean -xffd".  That doesn't work for the transition from "getSubmodules" to "notSubmodules", but covers the other cases.  Even a clean before checkout does not work for the transition from "getSubmodules" to "notSubmodules" (as far as I can tell).  However, since my case does not duplicate your message, I'm not sure if you'll see the same behavior as I see.

In that repository, the branch to branch transitions seem to behave like this:



Current Branch  
Branch to Checkout  
 Result 
 Command   


 master  
 tests/getSubmodules 
 ok  
 git checkout -f tests/getSubmodules ; git clean -xffd ; git status 


 master  
 tests/notSubmodules 
 ok  
 git checkout -f tests/notSubmodules ; git clean -xffd ; git status 


 tests/getSubmodules 
 master  
 ok  
 git checkout -f master  ; git clean -xffd ; git status 


 tests/notSubmodules 
 master  
 ok  
 git checkout -f master  ; git clean -xffd ; git status 


 tests/getSubmodules 
 tests/notSubmodules 
 fails 
 git checkout -f tests/notSubmodules ; git clean -xffd ; git status 


 tests/notSubmodules 
 tests/getSubmodules 
 ok  
 git checkout -f tests/getSubmodules ; git clean -xffd ; git status 



However, the failure message I'm seeing is not the same as the failure message you're seeing.  I'm confident that means I don't understand enough about submodules.  Can you provide a similar series of steps (preferably using a fork of the git-client-plugin repository) to show your case?



























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-22510) Clean After Checkout Results in Failed to Checkout Revision













































 
Mark Waite
 edited a comment on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision
















I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for my experiments.

Clone the repository - works


git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp



Checkout tests/getSubmodules - works


git checkout tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # Shows there is content in modules/ntp



Checkout master again - works


git checkout master # warns there are untracked files in modules directory
ls modules/ntp # shows content in modules/ntp is still there

git clean -xfd # skips modules/ntp and modules/firewall
ls modules/ntp # shows content in modules/ntp is still there

git clean -xffd # deletes modules/ntp and modules/firewall
ls modules/ntp # no content in modules/ntp



Checkout branch containing a conflicting file - works


git checkout tests/notSubmodules
ls modules/ntp # one file in modules/ntp



Checkout tests/getSubmodules again - works


git checkout tests/getSubmodules
git submodule update --init --recursive



Checkout branch (force) containing a conflicting file - works


git checkout -f tests/notSubmodules # works - but warns unable to rmdir
git clean -xffd
ls modules/ntp # one file in modules/ntp as expected



Checkout tests/getSubmodules (force) - fails


git checkout -f tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # one file in modules/ntp - should be more files there



The working sequence in my case seems to be "force checkout, then use git clean -xffd".  However, since my case does not duplicate your message, I'm not sure if you'll see the same behavior as I see.

In that repository, the branch to branch transitions seem to behave like this:



Current Branch  
Branch to Checkout  
 Result 
 Command   


 master  
 tests/getSubmodules 
 ok  
 git checkout -f tests/getSubmodules ; git clean -xffd ; git status 


 master  
 tests/notSubmodules 
 ok  
 git checkout -f tests/notSubmodules ; git clean -xffd ; git status 


 tests/getSubmodules 
 master  
 ok  
 git checkout -f master  ; git clean -xffd ; git status 


 tests/notSubmodules 
 master  
 ok  
 git checkout -f master  ; git clean -xffd ; git status 


 tests/getSubmodules 
 tests/notSubmodules 
 ok  
 git checkout -f tests/notSubmodules ; git clean -xffd ; git status 


 tests/notSubmodules 
 tests/getSubmodules 
 ok  
 git checkout -f tests/getSubmodules ; git clean -xffd ; git status 



However, the failure message I'm seeing is not the same as the failure message you're seeing.  I'm confident that means I don't understand enough about submodules.  Can you provide a similar series of steps (preferably using a fork of the git-client-plugin repository) to show your case?



























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-22510) Clean After Checkout Results in Failed to Checkout Revision













































 
Mark Waite
 edited a comment on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision
















I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for my experiments.

Clone the repository - works


git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp



Checkout tests/getSubmodules - works


git checkout tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # Shows there is content in modules/ntp



Checkout master again - works


git checkout master # warns there are untracked files in modules directory
ls modules/ntp # shows content in modules/ntp is still there

git clean -xfd # skips modules/ntp and modules/firewall
ls modules/ntp # shows content in modules/ntp is still there

git clean -xffd # deletes modules/ntp and modules/firewall
ls modules/ntp # no content in modules/ntp



Checkout branch containing a conflicting file - works


git checkout tests/notSubmodules
ls modules/ntp # one file in modules/ntp



Checkout tests/getSubmodules again - works


git checkout tests/getSubmodules
git submodule update --init --recursive



Checkout branch (force) containing a conflicting file - works


git checkout -f tests/notSubmodules # works - but warns unable to rmdir
git clean -xffd
ls modules/ntp # one file in modules/ntp as expected



Checkout tests/getSubmodules (force) - works


git checkout -f tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # one file in modules/ntp - should be more files there



The working sequence in my case seems to be "force checkout, then use git clean -xffd".  However, since my case does not duplicate your message, I'm not sure if you'll see the same behavior as I see.

In that repository, the branch to branch transitions seem to behave like this:



Current Branch  
Branch to Checkout  
 Result 
 Command   


 master  
 tests/getSubmodules 
 ok  
 git checkout -f tests/getSubmodules ; git submodule update --init --recursive ; git clean -xffd ; git status 


 master  
 tests/notSubmodules 
 ok  
 git checkout -f tests/notSubmodules ; git clean -xffd ; git status 


 tests/getSubmodules 
 master  
 ok  
 git checkout -f master  ; git clean -xffd ; git status 


 tests/notSubmodules 
 master  
 ok  
 git checkout -f master  ; git clean -xffd ; git status 


 tests/getSubmodules 
 tests/notSubmodules 
 ok  
 git checkout -f tests/notSubmodules ; git clean -xffd ; git status 


 tests/notSubmodules 
 tests/getSubmodules 
 ok  
 git checkout -f tests/getSubmodules ; git submodule update --init --recursive ; git clean -xffd ; git status 



However, the failure message I'm seeing is not the same as the failure message you're seeing.  I'm confident that means I don't understand enough about submodules.  Can you provide a similar series of steps (preferably using a fork of the git-client-plugin repository) to show your case?



























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-22510) Clean After Checkout Results in Failed to Checkout Revision













































 
Mark Waite
 edited a comment on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision
















I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for my experiments.

Clone the repository - works


git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp



Checkout tests/getSubmodules - works


git checkout tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # Shows there is content in modules/ntp



Checkout master again - works


git checkout master # warns there are untracked files in modules directory
ls modules/ntp # shows content in modules/ntp is still there

git clean -xfd # skips modules/ntp and modules/firewall
ls modules/ntp # shows content in modules/ntp is still there

git clean -xffd # deletes modules/ntp and modules/firewall
ls modules/ntp # no content in modules/ntp



Checkout branch containing a conflicting file - works


git checkout tests/notSubmodules
ls modules/ntp # one file in modules/ntp



Checkout tests/getSubmodules again - works


git checkout tests/getSubmodules
git submodule update --init --recursive



Checkout branch (force) containing a conflicting file - works


git checkout -f tests/notSubmodules # works - but warns unable to rmdir
git clean -xffd
ls modules/ntp # one file in modules/ntp as expected



Checkout tests/getSubmodules (force) - fails


git checkout -f tests/getSubmodules
git submodule update --init --recursive
ls modules/ntp # one file in modules/ntp - should be more files there



The working sequence in my case seems to be "force checkout, then use git clean -xffd".  However, since my case does not duplicate your message, I'm not sure if you'll see the same behavior as I see.

In that repository, the branch to branch transitions seem to behave like this:



Current Branch  
Branch to Checkout  
 Result 
 Command   


 master  
 tests/getSubmodules 
 ok  
 git checkout -f tests/getSubmodules ; git submodule update --init --recursive ; git clean -xffd ; git status 


 master  
 tests/notSubmodules 
 ok  
 git checkout -f tests/notSubmodules ; git clean -xffd ; git status 


 tests/getSubmodules 
 master  
 ok  
 git checkout -f master  ; git clean -xffd ; git status 


 tests/notSubmodules 
 master  
 ok  
 git checkout -f master  ; git clean -xffd ; git status 


 tests/getSubmodules 
 tests/notSubmodules 
 ok  
 git checkout -f tests/notSubmodules ; git clean -xffd ; git status 


 tests/notSubmodules 
 tests/getSubmodules 
 fails 
 git checkout -f tests/getSubmodules ; git submodule update --init --recursive ; git clean -xffd ; git status 



However, the failure message I'm seeing is not the same as the failure message you're seeing.  I'm confident that means I don't understand enough about submodules.  Can you provide a similar series of steps (preferably using a fork of the git-client-plugin repository) to show your case?



























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-22510) Clean After Checkout Results in Failed to Checkout Revision













































 
Mark Waite
 edited a comment on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision
















I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for my experiments.

The failing sequence I see currently is:


	checkout master
	checkout tests/notSubmodules
	checkout tests/getSubmodules
	checkout tests/notSubmodules



I defined a bash shell function "checkout" for my testing convenience.  It is


checkout ()
{
branch=$1;
git checkout -f $branch;
git clean -xffd;
git submodule update --init --recursive;
git status
}



Clone the repository - works


git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp



Checkout tests/notSubmodules - works


checkout tests/notSubmodules



Checkout tests/getSubmodules - works


checkout tests/getSubmodules



Checkout tests/notSubmodules - works


checkout tests/notSubmodules



Checkout tests/getSubmodules - fails


checkout tests/getSubmodules



The "mostly" working sequence in my case seems to be "force checkout, git clean -xffd, submodule update".  That seems to work for all the cases I've tested except the master to not to get to not to get case.  However, since my case does not duplicate your message, I'm not sure if you'll see the same behavior as I see.

In that repository, the branch to branch transitions seem to behave like this:



Current Branch  
Branch to Checkout  
 Result 
 Command   


 master  
 tests/getSubmodules 
 ok  
 git checkout -f tests/getSubmodules ; git submodule update --init --recursive ; git clean -xffd ; git status 


 master  
 tests/notSubmodules 
 ok  
 git checkout -f tests/notSubmodules ; git clean -xffd ; git status 


 tests/getSubmodules 
 master  
 ok  
 git checkout -f master  ; git clean -xffd ; git status 


 tests/notSubmodules 
 master  
 ok  
 git checkout -f master  ; git clean -xffd ; git status 


 tests/getSubmodules 
 tests/notSubmodules 
 ok  
 git checkout -f tests/notSubmodules ; git clean -xffd ; git status 


 tests/notSubmodules 
 tests/getSubmodules 
 fails 
 git checkout -f tests/getSubmodules ; git submodule update --init --recursive ; git clean -xffd ; git status 



However, the failure message I'm seeing is not the same as the failure message you're seeing.  I'm confident that means I don't understand enough about submodules.  Can you provide a similar series of steps (preferably using a fork of the git-client-plugin repository) to show your case?



























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] [core] (JENKINS-18537) ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6















































SCM/JIRA link daemon
 commented on  JENKINS-18537


ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 core/pom.xml
http://jenkins-ci.org/commit/jenkins/de5e12f3b64669ea4febdc08f2516bc0283a8bf4
Log:
  FIXED JENKINS-18537

Integrated the new version of XStream that contains the fix.

(cherry picked from commit 585eb87c2d1fdd93c585efca2b993ad734afdb20)

Conflicts:
	changelog.html





























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] [crowd2] (JENKINS-20871) Unable to login with plugin v1.6
















































Kanstantsin Shautsou
 closed  JENKINS-20871 as Cannot Reproduce


Unable to login with plugin v1.6
















Change By:


Kanstantsin Shautsou
(06/Apr/14 8:52 PM)




Status:


Open
Closed





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] [gradle] (JENKINS-15406) When using gradlew, root build script field is not used to locate gradlew
















































SCM/JIRA link daemon
 resolved  JENKINS-15406 as Fixed


When using gradlew, root build script field is not used to locate gradlew
















Change By:


SCM/JIRA link daemon
(06/Apr/14 9:23 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/d/optout.

[JIRA] [conditional-buildstep] (JENKINS-18629) Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single).















































SCM/JIRA link daemon
 commented on  JENKINS-18629


Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single).















Code changed in jenkins
User: Gregory Boissinot
Path:
 pom.xml
 src/main/java/hudson/plugins/gradle/Gradle.java
 src/main/resources/hudson/plugins/gradle/Gradle/config.jelly
http://jenkins-ci.org/commit/gradle-plugin/1dac78bcda1a5e0145d2906eafb80c1ad636bf68
Log:
  Merge pull request #20 from imod/JENKINS-18629

JENKINS-18629 - use Gradle in conditional-buildstep


Compare: https://github.com/jenkinsci/gradle-plugin/compare/c6365698b1a9...1dac78bcda1a




























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] [gradle] (JENKINS-15406) When using gradlew, root build script field is not used to locate gradlew















































SCM/JIRA link daemon
 commented on  JENKINS-15406


When using gradlew, root build script field is not used to locate gradlew















Code changed in jenkins
User: Gregory Boissinot
Path:
 src/main/java/hudson/plugins/gradle/Gradle.java
http://jenkins-ci.org/commit/gradle-plugin/8e6f838a6d051ca087b2e936be61b0e7675c75c8
Log:
  Merge pull request #21 from denis-zhdanov/master

FIXED JENKINS-15406


Compare: https://github.com/jenkinsci/gradle-plugin/compare/1dac78bcda1a...8e6f838a6d05




























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] [gradle] (JENKINS-15406) When using gradlew, root build script field is not used to locate gradlew















































SCM/JIRA link daemon
 commented on  JENKINS-15406


When using gradlew, root build script field is not used to locate gradlew















Code changed in jenkins
User: denis.zhdanov
Path:
 src/main/java/hudson/plugins/gradle/Gradle.java
http://jenkins-ci.org/commit/gradle-plugin/19a81cfa7f1ee6073a0b589811cba61e9763c569
Log:
  FIXED JENKINS-15406

Use gradle wrapper from a project which is located not at the workspace root





























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] [conditional-buildstep] (JENKINS-18629) Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single).
















































SCM/JIRA link daemon
 resolved  JENKINS-18629 as Fixed


Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single).
















Change By:


SCM/JIRA link daemon
(06/Apr/14 9:23 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/d/optout.

[JIRA] [conditional-buildstep] (JENKINS-18629) Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single).















































SCM/JIRA link daemon
 commented on  JENKINS-18629


Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single).















Code changed in jenkins
User: imod
Path:
 pom.xml
 src/main/java/hudson/plugins/gradle/Gradle.java
 src/main/resources/hudson/plugins/gradle/Gradle/config.jelly
http://jenkins-ci.org/commit/gradle-plugin/f4319ad6130bfbd6b1312577b1f10a2d944e10cf
Log:
  FIXED JENKINS-18629 inline attribute instead of deprecated newInstance() call, this allows use Gradle in ConditionalBuildstep with DataBoundConstructor





























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-22510) Clean After Checkout Results in Failed to Checkout Revision













































 
Mark Waite
 edited a comment on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision
















I've been trying to understand the sequence of git operations which arrive at that state, and haven't yet understood them.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for my experiments.

The failing sequence I see currently is:


	checkout master - ok
	checkout tests/notSubmodules - ok
	checkout tests/getSubmodules - ok
	checkout tests/notSubmodules - fails



I defined a bash shell function "checkout" for my testing convenience.  It is


checkout ()
{
branch=$1;
git checkout -f $branch;
git clean -xffd;
git submodule update --init --recursive;
git status
}



Clone the repository - works


git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp



Checkout tests/notSubmodules - works


checkout tests/notSubmodules



Checkout tests/getSubmodules - works


checkout tests/getSubmodules



Checkout tests/notSubmodules - works


checkout tests/notSubmodules



Checkout tests/getSubmodules - fails


checkout tests/getSubmodules



The "mostly" working sequence in my case seems to be "force checkout, git clean -xffd, submodule update".  That seems to work for all the cases I've tested except the master to notSubmodules to getSubmodules to notSubmodules to getSubmodules case.  However, since my case does not duplicate your message, I'm not sure if you'll see the same behavior as I see.

In that repository, the branch to branch transitions seem to behave like this:



Current Branch  
Branch to Checkout  
 Result   


 master  
 tests/getSubmodules 
 ok


 master  
 tests/notSubmodules 
 ok


 tests/getSubmodules 
 master  
 ok


 tests/notSubmodules 
 master  
 ok


 tests/getSubmodules 
 tests/notSubmodules 
 fails in some cases 


 tests/notSubmodules 
 tests/getSubmodules 
 fails in some cases 



However, the failure message I'm seeing is not the same as the failure message you're seeing.  I'm confident that means I don't understand enough about submodules.  Can you provide a similar series of steps (preferably using a fork of the git-client-plugin repository) to show your case?



























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] [core] (JENKINS-21720) Don't ask for confirmation when it doesn't make any sense

2014-04-06 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-21720


Dont ask for confirmation when it doesnt make any sense















https://github.com/jenkinsci/jenkins/pull/1175



























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] [core] (JENKINS-21720) Don't ask for confirmation when it doesn't make any sense

2014-04-06 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 updated  JENKINS-21720


Dont ask for confirmation when it doesnt make any sense
















Change By:


Daniel Beck
(06/Apr/14 10:46 PM)




Summary:


Jenkinsasks
Dontask
forconfirmation
toleave
when
submittingtheformbypressingthereturnkey
itdoesntmakeanysense





Assignee:


DanielBeck





Description:


Introducedinthiscommit:https://github.com/jenkinsci/jenkins/pull/962/files#r9552059
---Afewoftheoddbehaviors:*Asksforconfirmationwhenbrowsingawayafternavigatingbetweenformelementsbypressingtab*Asksforconfirmationwhentriggeringformsubmitusingkeyboard*Asksforconfirmationwhennavigatingawayafterclickingan*Advanced…*button.



























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] [parameterized-remote-trigger] (JENKINS-22384) Add EnvironmentVar feature to allow people access to Remote job















































Maurice W.
 commented on  JENKINS-22384


Add EnvironmentVar feature to allow people access to Remote job















Tim, when you think it's ready please go ahead an issue PR.
And this entire plugin is lacking unit tests 



























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] [parameterized-remote-trigger] (JENKINS-22427) Parameterized Remote Trigger Plugin fails when remote job waits for available executor















































Maurice W.
 commented on  JENKINS-22427


Parameterized Remote Trigger Plugin fails when remote job waits for available executor















Kevin - could you either share the patch you did as a gist (http://gist.github.com) or issue a PR.
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] [parameterized-remote-trigger] (JENKINS-22493) 400 when remote job has default parameters















































Maurice W.
 commented on  JENKINS-22493


400 when remote job has default parameters















This plugin checks if any parameters have been set in the local job, and based on that it decides if what URL to use to call the remote one. So what you are describing is expected.

But hitting the /job/remoteJobName/api/json URL and checking for the "parameterDefitnitions" property might not be a terrible idea.



























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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.















































Kanstantsin Shautsou
 updated  JENKINS-17060


Jenkins errors when Remember me on this computer is checked.
















Change By:


Kanstantsin Shautsou
(06/Apr/14 11:13 PM)




Assignee:


KohsukeKawaguchi



























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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.















































Kanstantsin Shautsou
 commented on  JENKINS-17060


Jenkins errors when Remember me on this computer is checked.















jenkins-1.557
realm - crowd2
strategy - Anyone can do anything

Stack trace

java.lang.IllegalArgumentException: Object of class [java.lang.String] must be an instance of interface org.acegisecurity.userdetails.UserDetails
	at org.springframework.util.Assert.isInstanceOf(Assert.java:337)
	at org.springframework.util.Assert.isInstanceOf(Assert.java:319)
	at hudson.security.TokenBasedRememberMeServices2.loginSuccess(TokenBasedRememberMeServices2.java:105)
	at org.acegisecurity.ui.AbstractProcessingFilter.successfulAuthentication(AbstractProcessingFilter.java:488)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:266)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
	at org.eclipse.jetty.server.Server.handle(Server.java:370)
	at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
	at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960)
	at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021)
	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)
	at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
	at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
	at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668)
	at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
	at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:724)




























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

[JIRA] [crowd2] (JENKINS-13279) Interface with Crowd embedded that runs in Jira















































Kanstantsin Shautsou
 commented on  JENKINS-13279


Interface with Crowd embedded that runs in Jira















Merged change, but now i have this error JENKINS-17060



























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] [core] (JENKINS-22514) Zip generated from all files in zip contains the wrong slashes

2014-04-06 Thread trej...@java.net (JIRA)















































trejkaz
 created  JENKINS-22514


Zip generated from all files in zip contains the wrong slashes















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


06/Apr/14 11:52 PM



Description:


The zip downloaded from "all files in zip" contains backwards slashes, which result in these becoming part of the filename when the zip is extracted (instead of becoming subdirectories.)

Here is the output I get from unzip -t:


Archive:  /Users/daniel/Downloads/functional-tests.zip
testing: functional-tests/0095eaafc6104c20af6ec6f3cee22ba0\derby.log   OK
testing: functional-tests/0095eaafc6104c20af6ec6f3cee22ba0\app.log   OK
testing: functional-tests/0095eaafc6104c20af6ec6f3cee22ba0\stderr.log   OK
testing: functional-tests/0095eaafc6104c20af6ec6f3cee22ba0\stdout.log   OK
testing: functional-tests/06f5fd94c53849378657dff5682e6610\derby.log   OK
testing: functional-tests/06f5fd94c53849378657dff5682e6610\app.log   OK
testing: functional-tests/06f5fd94c53849378657dff5682e6610\stderr.log   OK
testing: functional-tests/06f5fd94c53849378657dff5682e6610\stdout.log   OK
testing: functional-tests/0869e783b162411fa8fadae3b28c98e2\app.log   OK
testing: functional-tests/0869e783b162411fa8fadae3b28c98e2\stderr.log   OK
testing: functional-tests/0869e783b162411fa8fadae3b28c98e2\stdout.log   OK






Project:


Jenkins



Priority:


Major



Reporter:


trejkaz

























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] [parameterized-remote-trigger] (JENKINS-22493) 400 when remote job has default parameters















































Maurice W.
 started work on  JENKINS-22493


400 when remote job has default parameters
















Change By:


Maurice W.
(07/Apr/14 12:16 AM)




Status:


Open
InProgress



























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-21906) NumberFormatException occurs when accessing the JSON api















































Mark Waite
 commented on  JENKINS-21906


NumberFormatException occurs when accessing the JSON api















The NumberFormatException is fixed.  

Since Moosh Ben reports that the data returned is not available and was available before, then I assume there is an unreported bug that the timestamp which was available previously is no longer 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/d/optout.

[JIRA] [git] (JENKINS-21954) Jenkins can not enter Job's api page with latest version 1.552
















































Mark Waite
 closed  JENKINS-21954 as Duplicate


Jenkins can not enter Jobs api page with latest version 1.552
















Change By:


Mark Waite
(07/Apr/14 12:39 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] [git] (JENKINS-22510) Clean After Checkout Results in Failed to Checkout Revision













































 
Mark Waite
 edited a comment on  JENKINS-22510


Clean After Checkout Results in Failed to Checkout Revision
















I've been trying to understand the sequence of git operations which arrive at that state described in the bug report, and haven't yet understood how to do that.  My attempts have persuaded me that I don't understand submodules.  I used my fork of the git-client-plugin for my experiments.

The failing sequence I see currently is:


	checkout master - ok
	checkout tests/notSubmodules - ok
	checkout tests/getSubmodules - ok
	checkout tests/notSubmodules - fails



I defined a bash shell function "checkout" for my testing convenience.  It is


checkout ()
{
branch=$1;
git checkout -f $branch;
git clean -xffd;
git submodule update --init --recursive;
git status
}



Clone the repository - works


git clone git://github.com/MarkEWaite/git-client-plugin
cd git-client-plugin
ls modules/ntp # reports an error, no content in modules/ntp



Checkout tests/notSubmodules - works


checkout tests/notSubmodules



Checkout tests/getSubmodules - works


checkout tests/getSubmodules



Checkout tests/notSubmodules - works


checkout tests/notSubmodules



Checkout tests/getSubmodules - fails


checkout tests/getSubmodules



The "mostly" working sequence in my case seems to be "force checkout, git clean -xffd, submodule update".  That seems to work for all the cases I've tested except the master to notSubmodules to getSubmodules to notSubmodules to getSubmodules case.  However, since my case does not duplicate your message, I'm not sure if you'll see the same behavior as I see.

In that repository, the branch to branch transitions seem to behave like this:



Current Branch  
Branch to Checkout  
 Result   


 master  
 tests/getSubmodules 
 ok


 master  
 tests/notSubmodules 
 ok


 tests/getSubmodules 
 master  
 ok


 tests/notSubmodules 
 master  
 ok


 tests/getSubmodules 
 tests/notSubmodules 
 fails in some cases 


 tests/notSubmodules 
 tests/getSubmodules 
 fails in some cases 



However, the failure message I'm seeing is not the same as the failure message you're seeing.  I'm confident that means I don't understand enough about submodules.  Can you provide a similar series of steps (preferably using a fork of the git-client-plugin repository) to show your case?



























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] [parameterized-remote-trigger] (JENKINS-22427) Parameterized Remote Trigger Plugin fails when remote job waits for available executor















































Maurice W.
 commented on  JENKINS-22427


Parameterized Remote Trigger Plugin fails when remote job waits for available executor















My alternate solution is to have RemoteBuildConfiguration::sendHTTPCall() treat 404's as a non-error when it's called from RemoteBuildConfiguration::getBuildStatus()

Might not be the safest solution (since it walks up the call-stack to figure out who called it) but it certainly seems to be the most effective so far.



























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] [parameterized-remote-trigger] (JENKINS-22427) Parameterized Remote Trigger Plugin fails when remote job waits for available executor















































Maurice W.
 reopened  JENKINS-22427


Parameterized Remote Trigger Plugin fails when remote job waits for available executor
















Change By:


Maurice W.
(07/Apr/14 3:49 AM)




Resolution:


Fixed





Status:


Resolved
Reopened





Assignee:


KevinVanPoppel
MauriceW.



























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] [parameterized-remote-trigger] (JENKINS-22384) Add EnvironmentVar feature to allow people access to Remote job
















































Maurice W.
 assigned  JENKINS-22384 to Tim Brown



Add EnvironmentVar feature to allow people access to Remote job
















Change By:


Maurice W.
(07/Apr/14 4:02 AM)




Assignee:


MauriceW.
TimBrown



























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] [parameterized-remote-trigger] (JENKINS-22231) Allow parameterized remote trigger to be a post-build action















































Maurice W.
 updated  JENKINS-22231


Allow parameterized remote trigger to be a post-build action
















Change By:


Maurice W.
(07/Apr/14 4:02 AM)




Issue Type:


Improvement
NewFeature



























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] [parameterized-remote-trigger] (JENKINS-20828) Allow to block the build untill target job finished
















































Maurice W.
 assigned  JENKINS-20828 to Tim Brown



Allow to block the build untill target job finished
















Marking Tim as the assignee because he's the one that implemented this feature





Change By:


Maurice W.
(07/Apr/14 4:06 AM)




Assignee:


MauriceW.
TimBrown



























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-22510) Clean After Checkout Results in Failed to Checkout Revision