Re: Jenkins with iOS development

[Sami Tikka]

I would still like to know if installing the Xcode plugin only is enough or 
does the standard Jenkins installation on Mac need some tweaks. 

-- Sami

Christopher Orr  kirjoitti 11.4.2012 kello 23.18:

> On 04/02/2012 12:15 AM, Sami Tikka wrote:
>> I am not an iOS developer myself, so I have not run into this problem.
>> Is there anyone here who can verify that adding the SessionCreate
>> setting to orgi.jenkins-ci.plist fixes the problem? Probably this is
>> not the whole solution. The keys and certificates still need to be
>> copied to the jenkins user keychain, I believe. Is there something we
>> can do to make it easier?
> 
> I'm not an iOS developer either, but I had the impression that the Jenkins 
> Xcode Plugin was designed to automate some of this keychain stuff.
> 
> I haven't seen that mentioned here or on Stack Overflow, so perhaps it's 
> worth a look:
> https://wiki.jenkins-ci.org/display/JENKINS/Xcode+Plugin
> 
> Regards,
> Chris

Re: Promoted Builds Plugin: Does not automatically promote despite qualifications being met

[Sami Tikka]

At least the Copy Artifact plugin knows about the promotions. When configuring 
Copy Artifact build step in the job that gets triggered by promotion, choose 
Specific build and under that Promoted build. 

-- Sami

Nicky Ramone  kirjoitti 12.4.2012 kello 21.29:

> It looks like a weird bug. It happens on one set of jobs but not on another 
> one I have.
> Another problem I'm having is that when you manually promote a build that 
> triggers a downstream build,  the triggered downstream build does not include 
> information from the upstream project, which is a big problem.
> 
> On Thu, Apr 12, 2012 at 4:05 AM, Taubert, Helge  wrote:
> Hi!
> 
>  
> 
> We have a similar issue for some versions back now. We get the following 
> warning:
> 
>  
> 
>  
> 
> WARNING: Job_A appears to use this job as a promotion criteria, but no 
> fingerprint is recorded. Fingerprint needs to be enabled on both this job and 
> Job_A
> 
>  
> 
> If you check the fingerprints manually, everything is fine, but the promotion 
> does not work.
> 
> It worked one and a half year ago. Then there were some race condition which 
> made it fail sometimes. These were fixed and it worked for a while. Then it 
> stopped working at all.
> 
>  
> 
> It would be nice to have this feature working again.
> 
>  
> 
> Greetings,
> 
>  
> 
> Helge
> 
>  
> 
> From: jenkinsci-users@googlegroups.com 
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Nicky Ramone
> Sent: Mittwoch, 11. April 2012 18:31
> To: jenkinsci-users@googlegroups.com
> Subject: Promoted Builds Plugin: Does not automatically promote despite 
> qualifications being met
> 
>  
> 
> Hello.
> 
>  
> 
> I have the following build sequence with Maven jobs: A --> B --> C and I want 
> to promote A when C has finished successfully.
> 
> I am tracking fingerprints of the same artifact in all 3 jobs, and I verify 
> that they are correct.
> 
>  
> 
> When C finishes, the "Promotion Status" looks fine with met qualifications:
> 
>  
> 
> Promotions
> 
>  my_promotion
> 
> [Force promotion]
> 
> This promotion has not happened.
> 
> Met Qualification 
> 
> Downstream builds succeeded
> 
> C #8
> 
> Unmet Qualification 
> 
>  
> 
> Despite that, the promotion never occurs (you can see the label "This 
> promotion has not happened").
> 
> I found a couple of threads/issues that seem to be pointing to the same 
> problem, but no solution available:
> 
> http://jenkins.361315.n4.nabble.com/Promotion-is-not-working-td3643188.html
> 
> https://issues.jenkins-ci.org/browse/JENKINS-10199
> 
>  
> 
> I'm using Jenkins 1.455 and Promoted Builds Plugin 2.4
> 
> Has anyone else come across this issue?
> 
>  
> 
> Thanks
> 
> Cheers.
> 
>  
> 
> 

Re: WARNING: Failed to advertise the service to DNS multi-cast

[Sami Tikka]

I'm afraid that might be caused by the recent fix I made to Jenkins mDNS 
advertisement. 

It almost seems like Jenkins is unable to parse its own address. What do you 
have set as Jenkins' own address in Manage Jenkins / Configure system? Would 
you mind reporting the bug into issues.jenkins-ci.org?

Frankly I do not know if the exception causes something else to be skipped in 
the startup.

-- Sami

SamL  kirjoitti 13.4.2012 kello 20.02:

> Hello Folks.
> 
> I just installed Jenkins ver. 1.459 on a CentOS 6 machine and I am
> getting the following WARNING during  start up.
> 
> Does anyone know what this mean and is it something I should be
> concern about?
> 
> Does anyone know what this w
> WARNING: Failed to advertise the service to DNS multi-cast
> java.net.MalformedURLException
>at java.net.URL.(URL.java:617)
>at java.net.URL.(URL.java:480)
>at java.net.URL.(URL.java:429)
>at hudson.DNSMultiCast.(DNSMultiCast.java:45)
>at jenkins.model.Jenkins.(Jenkins.java:787)
>at hudson.model.Hudson.(Hudson.java:81)
>at hudson.model.Hudson.(Hudson.java:77)
>at hudson.WebAppMain$2.run(WebAppMain.java:217)
> Caused by: java.lang.NullPointerException
>at java.net.URL.(URL.java:522)
>... 7 more
> Apr 13, 2012 12:25:26 AM hudson.WebAppMain$2 run
> INFO: Jenkins is fully up and running

Jenkins SLOCCount plugin - unable to see job configuration option after plugin install

[Buser, Stephanie]

Hi,

We recently installed the SLOCCount plugin but are unable to see the "Publish 
SLOCCount analysis results" on the job configuration page (i.e. under the 
post-build actions).  We've tried completely uninstalling and reinstalling the 
plugin with no luck.  Has anyone come across this issue and if so is there a 
solution for it?  Is there anything we need to be configuring outside of the 
instructions on the install page?  Perhaps another installed plugin is 
overriding the configuration for the SLOCcount plugin?

https://wiki.jenkins-ci.org/display/JENKINS/SLOCCount+Plugin

Thanks!

Re: git checkout fails on Windows

[Thomas Sondergaard]

On 2012-04-13 09:30, B.Latinville wrote:

Hi

Have a look at this issue :

https://issues.jenkins-ci.org/browse/JENKINS-13007

You should use git.exe instead of git.cmd.
You shall specify full path of git.exe in node option, Tool Locations.


Thanks, I'll give that a try!

Thomas

clean up maven repo in Jenkins slave

[JasonX]

I saw maven repo is copied to /opt/.m2 directory on Jenkins slave from
maven server and it fills up Jenkins slave disk. I wanna clean it up.
How  can I do it? can I remove all of the repos from Jenkins slave
after each build? is that necessary to keep all dependencies on
Jenkins slave but they are already existing in maven server.

How do I get Jenkins to skip failed branches till they change?

[fREW Schmidt]

I'm using Jenkins with the Multiple SCMs + Git plugin. Jenkins is correctly
doing a new build for each branch, but for some reason when it fails a
build it just keeps trying to redo the build, even if the branch has not
changed. How can I fix it so that Jenkins will move on to the next branch
and only try to rebuild if the current branch changes?

Note, I originally asked this question on ServerFault (it's since been
migrated to StackOverflow) so if you answer and also want credit on SO feel
free to copy paste your answer to there:
http://stackoverflow.com/questions/10144733/how-do-i-get-jenkins-to-skip-failed-branches-till-they-change

-- 
fREW Schmidt
http://blog.afoolishmanifesto.com

WARNING: Failed to advertise the service to DNS multi-cast

[SamL]

Hello Folks.

I just installed Jenkins ver. 1.459 on a CentOS 6 machine and I am
getting the following WARNING during  start up.

Does anyone know what this mean and is it something I should be
concern about?

Does anyone know what this w
WARNING: Failed to advertise the service to DNS multi-cast
java.net.MalformedURLException
at java.net.URL.(URL.java:617)
at java.net.URL.(URL.java:480)
at java.net.URL.(URL.java:429)
at hudson.DNSMultiCast.(DNSMultiCast.java:45)
at jenkins.model.Jenkins.(Jenkins.java:787)
at hudson.model.Hudson.(Hudson.java:81)
at hudson.model.Hudson.(Hudson.java:77)
at hudson.WebAppMain$2.run(WebAppMain.java:217)
Caused by: java.lang.NullPointerException
at java.net.URL.(URL.java:522)
... 7 more
Apr 13, 2012 12:25:26 AM hudson.WebAppMain$2 run
INFO: Jenkins is fully up and running

Re: High CPU usage

[Andrew Melo]

On Apr 13, 2012, at 11:47, "Mandeville, Rob"  wrote:

> Yes.  So you aren’t auto-refreshing.  Sorry, I thought that this would be the 
> problem.

Maybe the JavaScript polling for build status is firing too quickly...I'm not 
sure how to profile JS though

>  
> --Rob
>  
> From: jenkinsci-users@googlegroups.com 
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Andrew Melo
> Sent: Friday, April 13, 2012 12:46 PM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: High CPU usage
>  
> The pages have it and it says, "Enable auto-refresh". Does that mean it's off 
> and clicking it will turn it on?
> 
> On Fri, Apr 13, 2012 at 11:42 AM, Mandeville, Rob  
> wrote:
> Do you have auto-refresh on?  Each Jenkins window should have an “enable 
> auto-refresh” or “disable auto-refresh” tag on it.
>  
> --Rob
>  
> From: jenkinsci-users@googlegroups.com 
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Andrew Melo
> Sent: Friday, April 13, 2012 12:36 PM
> To: jenkinsci-users@googlegroups.com
> Subject: High CPU usage
>  
> Hello,
>  
> I work on a laptop most of the time, and I've noticed that leaving a jenkins 
> window open will cause firefox to use nearly an entire core (which drains the 
> battery real quickly). Even starting with a brand new browser window, it 
> still happens. Are there any options to help reduce that? 
>  
> Thanks,
> Andrew
>  
> -- 
> --
> Andrew Melo
> 
> The information in this message is for the intended recipient(s) only and may 
> be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
> protected from disclosure. If you are not the intended recipient(s), or an 
> employee or agent responsible for delivering this message to the intended 
> recipient, you are hereby notified that any use, dissemination, distribution 
> or copying of this communication is prohibited. If you have received this 
> communication in error, please notify Litle & Co. immediately by replying to 
> this message and then promptly deleting it and your reply permanently from 
> your computer.
> 
> 
>  
> -- 
> --
> Andrew Melo

RE: High CPU usage

[Mandeville, Rob]

Yes.  So you aren’t auto-refreshing.  Sorry, I thought that this would be the 
problem.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Andrew Melo
Sent: Friday, April 13, 2012 12:46 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: High CPU usage

The pages have it and it says, "Enable auto-refresh". Does that mean it's off 
and clicking it will turn it on?
On Fri, Apr 13, 2012 at 11:42 AM, Mandeville, Rob 
mailto:rmandevi...@litle.com>> wrote:
Do you have auto-refresh on?  Each Jenkins window should have an “enable 
auto-refresh” or “disable auto-refresh” tag on it.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com]
 On Behalf Of Andrew Melo
Sent: Friday, April 13, 2012 12:36 PM
To: jenkinsci-users@googlegroups.com
Subject: High CPU usage

Hello,

I work on a laptop most of the time, and I've noticed that leaving a jenkins 
window open will cause firefox to use nearly an entire core (which drains the 
battery real quickly). Even starting with a brand new browser window, it still 
happens. Are there any options to help reduce that?

Thanks,
Andrew

--
--
Andrew Melo
The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.



--
--
Andrew Melo

Re: High CPU usage

[Andrew Melo]

The pages have it and it says, "Enable auto-refresh". Does that mean it's
off and clicking it will turn it on?

On Fri, Apr 13, 2012 at 11:42 AM, Mandeville, Rob wrote:

>  Do you have auto-refresh on?  Each Jenkins window should have an “enable
> auto-refresh” or “disable auto-refresh” tag on it.
>
> ** **
>
> --Rob
>
> ** **
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Andrew Melo
> *Sent:* Friday, April 13, 2012 12:36 PM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* High CPU usage
>
> ** **
>
> Hello,
>
> ** **
>
> I work on a laptop most of the time, and I've noticed that leaving a
> jenkins window open will cause firefox to use nearly an entire core (which
> drains the battery real quickly). Even starting with a brand new browser
> window, it still happens. Are there any options to help reduce that? 
>
> ** **
>
> Thanks,
>
> Andrew
> 
>
> ** **
>
> --
> --
> Andrew Melo
>   The information in this message is for the intended recipient(s) only
> and may be the proprietary and/or confidential property of Litle & Co.,
> LLC, and thus protected from disclosure. If you are not the intended
> recipient(s), or an employee or agent responsible for delivering this
> message to the intended recipient, you are hereby notified that any use,
> dissemination, distribution or copying of this communication is prohibited.
> If you have received this communication in error, please notify Litle & Co.
> immediately by replying to this message and then promptly deleting it and
> your reply permanently from your computer.
>



-- 
--
Andrew Melo

RE: High CPU usage

[Mandeville, Rob]

Do you have auto-refresh on?  Each Jenkins window should have an “enable 
auto-refresh” or “disable auto-refresh” tag on it.

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Andrew Melo
Sent: Friday, April 13, 2012 12:36 PM
To: jenkinsci-users@googlegroups.com
Subject: High CPU usage

Hello,

I work on a laptop most of the time, and I've noticed that leaving a jenkins 
window open will cause firefox to use nearly an entire core (which drains the 
battery real quickly). Even starting with a brand new browser window, it still 
happens. Are there any options to help reduce that?

Thanks,
Andrew

--
--
Andrew Melo

The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

High CPU usage

[Andrew Melo]

Hello,

I work on a laptop most of the time, and I've noticed that leaving a
jenkins window open will cause firefox to use nearly an entire core (which
drains the battery real quickly). Even starting with a brand new browser
window, it still happens. Are there any options to help reduce that?

Thanks,
Andrew

-- 
--
Andrew Melo

Re: Promoted Builds Plugin: Does not automatically promote despite qualifications being met

[Brian J. Murrell]

On 12-04-12 02:29 PM, Nicky Ramone wrote:
> 
> Another problem I'm having is that when you manually promote a build that
> triggers a downstream build,  the triggered downstream build does not
> include information from the upstream project, which is a big problem.

Yes, I agree.  I posted a message only a few days ago about this.  The
answer seemed to be to use a parameterized trigger, which does work, but
this behavior really seems like it ought to be implied.  If one executes
a downstream build from a promotion, I'd say there is a good chance the
downstream job wants to know about why it was triggered so that it can
act accordingly.  i.e. operate on the artifacts of the upstream
job/build -- in this case the promoted build.

b.



signature.asc
Description: OpenPGP digital signature

Re: Is there a way to read a string (version numbers) from a file into jenkins variable?

[shanz]

REM create a file to hold environment variables for all subsequent
labelled build jobs
del C:\hudson\jobs\shareableCustomWorkspace\labelledJobsEnvVars.txt
echo APPLICATION_BINARY_VERSION=%APPLICATION_BINARY_VERSION% > C:
\hudson\jobs\shareableCustomWorkspace\labelledJobsEnvVars.txt
echo BUILD_STRING=%BUILD_STRING% >> C:\hudson\jobs
\shareableCustomWorkspace\labelledJobsEnvVars.txt
echo SVN_TAG_DATE=%SVN_TAG_DATE% >> C:\hudson\jobs
\shareableCustomWorkspace\labelledJobsEnvVars.txt
echo SVN_TAG=IQ4 WinCE OS v%BUILD_STRING% %SVN_TAG_DATE% >> C:\hudson
\jobs\shareableCustomWorkspace\labelledJobsEnvVars.txt

Then in any subsequent jobs ...
Tick "Inject environment variables to the build process"
Properties File Path
C:\hudson\jobs\shareableCustomWorkspace\labelledJobsEnvVars.txt

then just use the variables as normal.

That's it!




On Apr 6, 12:12 am, shanz  wrote:
> You could create another file with the version number in the java
> property (key=value) format.
> Then you can use the EnvInject plugin to inject the environment
> variable (MY_NEW_VAR) into your job/build.
> The advantage of this approach is that the variable can be visible
> throughout the whole job/build.
> You just enter the path/myVersion.txt in the Properties File field of
> the plugin.
>
> Alternatively just use DOS, eg: To place the first line of a file into
> a variable, do this
> Set /P MyVar=
> The downside to this later approach is that you may have to repeat it
> if you open several shells.

Re: Plugins are not updating

[Emil B]

Yes, plugin updates works from GUI without any manual "pinnings" in version 
1.459. Great!

/Emil

Den tisdagen den 10:e april 2012 kl. 12:30:12 UTC+2 skrev (okänd):
>
>  I checked with 1.459 and the issue is fixed there. That is, a plugin 
> gets pinned automatically during an upgrade. Pinning (or unpinning 
> actually) was and is still supported through UI.
>
>  
>
> Mikko
>
>  
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *ext Jeff
> *Sent:* 6. huhtikuuta 2012 2:52
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: Plugins are not updating
>
>  
>  
> Documented, but not obvious.  The update/pinning of integrated plugins is 
> fairly non-intuitive from a user perspective.  The fact that it doesn't 
> work appears to be a bug and I'd wager countless people spend hours if not 
> longer trying to figure out why.
>  
>  
>  
> Could the user experience be enhanced to either make it more obvious 
> and/or allow the pinning of plugins via the UI instead of the current 
> manual way?
>  
> On Thu, Apr 5, 2012 at 2:12 PM, Dirk Strauss  wrote:
>
> Hi, Jeff,
>  
>  
>  
> thx for the hint. Plugin update now "empty" instead of having 3 plugins 
> still to update.
>  
>  
>  
> Regards,
>  
> Dirk
>  
>
>
>
> -- 
>  
> Jeff Vincent
> predato...@gmail.com
> See my LinkedIn profile at:
> http://www.linkedin.com/in/rjeffreyvincent
>  
> I ♥ DropBox  !!  
>  
>  
>  

Re: RE: Anyone seen these GIT Errors?

[Alexei Novikov]

Lee Goddard  net-a-porter.com> writes:

> 
> This problem came about because Hudson was running through Tomcat, which
> was started by /etc/init.d/, which is run by root - the init.d script
> did not change directory out of root's $HOME, /root, hence the problem.
> 
> Problem was solved by having Tomcat's start-up script change directory
> before calling Tomcat.
> 

We had same problem and the suggested solution did help us to fix it.

The symptoms we observed were aggravated by the fact that two instances of 
Jenkins and Tomcat that were configured identically did in fact behave 
differently. 
One instance of Jenkins failed to create new tasks, while the other 
had no problem with that. It appeared that the instance that ran problem-free 
was started manually (by a root user of course) from a directory owned by a 
Tomcat user. 
That instance of Jenkins never had to change directory to /root, 
and that one have functioned properly. The other instance was started 
automatically by the system and had /root as a working directory. That one 
failed.

problem during startup on GlassFish 3.1.1b12 - Nullpointer Exception

[Maciej Matecki]

Hi,
I've got a problem with startup of Jenkins. After deploy I've got such 
exception:

org.jvnet.hudson.reactor.ReactorException: java.lang.NullPointerException
at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246)
at jenkins.InitReactorRunner.run(InitReactorRunner.java:43)
at jenkins.model.Jenkins.executeReactor(Jenkins.java:811)
at jenkins.model.Jenkins.(Jenkins.java:732)
at hudson.model.Hudson.(Hudson.java:81)
at hudson.model.Hudson.(Hudson.java:77)
at hudson.WebAppMain$2.run(WebAppMain.java:217)
Caused by: java.lang.NullPointerException
at 
hudson.LocalPluginManager.loadBundledPlugins(LocalPluginManager.java:69)
at hudson.PluginManager$1$1.run(PluginManager.java:175)
at 
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at jenkins.model.Jenkins$5.runTask(Jenkins.java:800)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)


I have no idea what could be wrong.
Environment: Debian 6.0.4 amd64, GlassFish 3.1.1b12

Any advices?

Regards,
Maciej Matecki

Re: Findbugs report with excluded packages

[jhoomsharabi]

I looked into it and did not found any issue with reports generated by mvn 
findbugs:findbugs command the html report generated looks good, but the xml 
reports findbugsXml.xml still shows exculded class and packages.


-Original Message-
From: Ullrich Hafner 
To: jenkinsci-users 
Sent: Thu, Sep 29, 2011 6:48 pm
Subject: Re: Findbugs report with excluded packages


The FindBugs Jenkins plug-in does not read the exclude filters specified 
n your pom it just renders the results of the maven plug-in. I.e., this 
ust be a problem in your filter configuration.
Ulli
On 09/29/2011 02:44 PM, Christoph Kutzinski wrote:
 Is it working if you call mvn install findbugs:findbugs manually, i.e. from a 
hell?

 If not, we need to see your exclude and include files.


  Original-Nachricht 
> Datum: Thu, 29 Sep 2011 08:22:26 -0400 (EDT)
> Von: jhoomshar...@netscape.net
> An: jenkinsci-users@googlegroups.com
> Betreff: Findbugs report with excluded packages
> I am using Jenkins findbugs plugin v4.29, now I configured my pom to
> exclude few packages, but when I run my project which contains configuration
> mvn install findbugs:findbugs
>
> I am still seeing that findbugs is generating report for excluded
> packages, I have no idea if this is an issue with findbugs maven plugin or 
indbugs
> Jenkins plugin, my pom with finbugs configuration looks like this
>
> 
>org.codehaus.mojo
>findbugs-maven-plugin
>2.3.1
>
>true
>
> true
>true
>
> findbugs-exclude.xml
>
> findbugs-include.xml
>   
> 
>
> Any help in this regard will be highly appreciated.
>
> Thanks,
> Jhoom
>

Re: git checkout fails on Windows

[B.Latinville]

Hi

Have a look at this issue :

https://issues.jenkins-ci.org/browse/JENKINS-13007

You should use git.exe instead of git.cmd.
You shall specify full path of git.exe in node option, Tool Locations.

Bertrand

On Apr 12, 10:34 pm, Thomas Sondergaard 
wrote:
> I have a problem with git checkout failing on Windows. It is a
> multi-configuration job with an axies running on different slaves, and
> it works on the linux slave. The job is configured to build branches
> "origin/for-master/*" and merge to master before building.
>
> I've pasted in the error that I'm getting below, and hoping for some
> helpful pointers
>
> Thanks,
>
> Thomas
>
> Checkout:win32 /
> c:\jenkins\workspace\easyviz-master-integrate\arch/win32 -
> hudson.remoting.Channel@65400211:bob-w7-64
> Using strategy: Default
> Checkout:win32 /
> c:\jenkins\workspace\easyviz-master-integrate\arch\win32 -
> hudson.remoting.LocalChannel@2a8113d5
> Fetching changes from 1 remote Git repository
> Fetching upstream changes from
> ssh://jenk...@git.medical-insight.com/var/git/easyviz.git
> Pruning obsolete local branches
> Commencing build of Revision ce20df8fd667060b0cbcca8f786dc2a0d4639cd7
> (origin/for-master/tst-jenkins)
> Merging Revision ce20df8fd667060b0cbcca8f786dc2a0d4639cd7
> (origin/for-master/tst-jenkins) onto master
> FATAL: Error performing command: C:\Program Files (x86)\Git\cmd\git.cmd
> rev-parse origin/master^{commit}
> Command "C:\Program Files (x86)\Git\cmd\git.cmd rev-parse
> origin/master^{commit}" returned status code 128: origin/master{commit}
> fatal: ambiguous argument 'origin/master{commit}': unknown revision or
> path not in the working tree.
> Use '--' to separate paths from revisions
>
> hudson.plugins.git.GitException: Error performing command: C:\Program
> Files (x86)\Git\cmd\git.cmd rev-parse origin/master^{commit}
> Command "C:\Program Files (x86)\Git\cmd\git.cmd rev-parse
> origin/master^{commit}" returned status code 128: origin/master{commit}
> fatal: ambiguous argument 'origin/master{commit}': unknown revision or
> path not in the working tree.
> Use '--' to separate paths from revisions
>
>         at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:776)
>         at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:741)
>         at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:751)
>         at hudson.plugins.git.GitAPI.revParse(GitAPI.java:254)
>         at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1166)
>         at hudson.plugins.git.GitSCM$3.invoke(GitSCM.java:1149)
>         at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
>         at hudson.remoting.UserRequest.perform(UserRequest.java:118)
>         at hudson.remoting.UserRequest.perform(UserRequest.java:48)
>         at hudson.remoting.Request$2.run(Request.java:287)
>         at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>         at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
>         at java.util.concurrent.FutureTask.run(Unknown Source)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>         at hudson.remoting.Engine$1$1.run(Engine.java:60)
>         at java.lang.Thread.run(Unknown Source)
> Caused by: hudson.plugins.git.GitException: Command "C:\Program Files
> (x86)\Git\cmd\git.cmd rev-parse origin/master^{commit}" returned status
> code 128: origin/master{commit}
> fatal: ambiguous argument 'origin/master{commit}': unknown revision or
> path not in the working tree.
> Use '--' to separate paths from revisions
>
>         at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:771)
>         ... 16 more