Re: git plugin busted

For the inverse choosing strategy I will continue to experiment with it and if I come up with some steps to cause it I will submit a bug report. On Tue, Jan 7, 2014 at 9:29 AM, Mark Waite wrote: > The inverse choosing strategy building the "deselected" branch sounds like > a bug. I've not seen

Re: git plugin busted

This is my problem. I have wiped out my workspace and there is no .git/config file to read. This seems like a basic ordering problem. The workspace needs to be cloned before any git operations happen. On Tue, Jan 7, 2014 at 9:28 AM, Mark Waite wrote: > I think that the reason the "git config --g

Re: git plugin busted

The inverse choosing strategy building the "deselected" branch sounds like a bug. I've not seen any bug report like that in my looking at bugs related to the git plugin. Can you find a set of steps which make that bug repeatable, and then submit it as a bug? On Tue, Jan 7, 2014 at 7:00 AM, Jon

Re: git plugin busted

I think that the reason the "git config --get remote.origin.url" command returns status code 1 is that the value of remote.origin.url is not set in the .git/config file in the workspace. My thought was that if the first build step in your job was a "git config --set remote.origin.url your_url", th

Re: git plugin busted

Using 1.4.0, everything appears to work fine. Using 2.0 I have the following problems: If I manually delete the workspace using the Wipe out workspace link AND have prune stale remote branches on, the plugin will not clone the repository with the error: *08:56:16* Started by user Jon Schewe

Re: git plugin busted

I don't see how using git commands from within the job itself would help as there is no local git repository at this point. > Another possibility might be to attempt to use git commands from within the job itself to define remote.origin.url if it is not already defined. On Mon, Jan 6, 2014 at 4

Re: git plugin busted

I don't understand your comment that you're "not sure how that would help as the job won't start until the workspace is cloned." The log output reports "pruning obsolete local branches". Until the workspace is cloned, there is no repository, so there is nothing to prune. I assumed that meant the

Re: git plugin busted

Changing "prune remote branches" doesn't help. I'm not using regions either. On Sun, Jan 5, 2014 at 9:30 PM, Mark Waite wrote: > That stack trace looks a lot like > https://issues.jenkins-ci.org/browse/JENKINS-20258 . You might consider > removing the "prune branches" option from the job config

Re: git plugin busted

Not sure how that would help as the job won't start until the workspace is cloned. On Sun, Jan 5, 2014 at 9:32 PM, Mark Waite wrote: > Another possibility might be to attempt to use git commands from within > the job itself to define remote.origin.url if it is not already defined. > > > On Sun,

Re: git plugin busted

I had to stop using the Git Publisher for this specific reason, I just moved the publish operation into a build step. I'd really like to have the Git plugin fixed though. On Sun, Jan 5, 2014 at 7:12 PM, Jon Schewe wrote: > Anyone else running into problems with the git plugin version 2.0? I'm >

Re: git plugin busted

That really needs to be fixed; if include/exclude specifications cannot be processed without "Force polling using workspace", then the plugin should just turn that on itself. Allowing the user to select options that will never result in a working configuration is user-hostile. If at some point

Re: git plugin busted

Another possibility might be to attempt to use git commands from within the job itself to define remote.origin.url if it is not already defined. On Sun, Jan 5, 2014 at 8:30 PM, Mark Waite wrote: > That stack trace looks a lot like > https://issues.jenkins-ci.org/browse/JENKINS-20258 . You might

Re: git plugin busted

That stack trace looks a lot like https://issues.jenkins-ci.org/browse/JENKINS-20258 . You might consider removing the "prune branches" option from the job configuration to see if that helps avoid the problem. If you're using include region, exclude region, or exclude user, then you'll need to al

git plugin busted

Anyone else running into problems with the git plugin version 2.0? I'm using Jenkins 1.509.4 and have run into the problem that if I wipe out my workspace either manually that the plugin can't clone a new workspace. It errors like this: *16:08:58* Started by user Jon Schewe