RE: Proxy port
These settings come from your Buckminster install: /path/to/buckminster/configuration/.settings/org.eclipse.core.net.prefs -Original Message- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of CLOSE Dave Sent: 24 May 2013 02:30 To: jenkinsci-users@googlegroups.com Subject: Proxy port Somehow I've managed to get my Jenkins system's proxy configuration screwed up and I can't find how to get it back again. This affects Buckminster. When I run a Buckminster job, it fails and the log contains these lines: !ENTRY org.eclipse.core.net 1 0 2013-05-23 18:04:35.729 !MESSAGE System property http.proxyHost is not set but should be localhost. !ENTRY org.eclipse.core.net 1 0 2013-05-23 18:04:35.729 !MESSAGE System property http.proxyPort is not set but should be 3128. !ENTRY org.eclipse.core.net 1 0 2013-05-23 18:04:35.729 !MESSAGE System property https.proxyHost is not set but should be localhost. !ENTRY org.eclipse.core.net 1 0 2013-05-23 18:04:35.730 !MESSAGE System property https.proxyPort is not set but should be 3128. !ENTRY org.eclipse.core.net 1 0 2013-05-23 18:04:35.732 !MESSAGE System property https.proxyHost is not set but should be localhost. !ENTRY org.eclipse.core.net 1 0 2013-05-23 18:04:35.732 !MESSAGE System property https.proxyPort is not set but should be 3128. However, those values don't seem to appear anywhere in either the Jenkins or the job configuration. In fact I have: 1. In Manage Jenkins/System Configuration/Environment variables, each variable above is defined and set to a different value. 2. In Manage Jenkins/System Configuration/Buckminster configuration/additional startup parameters, each variable is defined and set to a different value. For example, -Dhttp.proxyPort=8000. 3. In the job configuration/Build/Run Buckminster/JVM parameters, I have the same definitions. 4. Outside Jenkins, the system environment variables are set to different values. Jenkins has been restarted. So where are the values above originating? And how can I change them? The first time I tried Buckminster, the values were correct. I can't see what I did to change them but I can't get them back, either. -- Dave Close -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins build hangs on sending email (in hudson.model.User.getProjects)
Hi, What you observe is a mail address resolution. A process that scans all project in the instance in order to find user's email address. It is usually implemented by scm plugin (SVN in your case). Resolver implementation was deleted from CVS plugin (in 2.8) and from SVN plugin (in 1.45). If you do not need this functionality, upgrading your subversion plugin to at least 1.45 should fix it. [1] https://issues.jenkins-ci.org/browse/JENKINS-14755 -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins build hangs on sending email (in hudson.model.User.getProjects)
Thank you for prompt answer! On Fri, May 24, 2013 at 10:00 AM, oliver gondža ogon...@gmail.com wrote: Hi, What you observe is a mail address resolution. A process that scans all project in the instance in order to find user's email address. It is usually implemented by scm plugin (SVN in your case). Resolver implementation was deleted from CVS plugin (in 2.8) and from SVN plugin (in 1.45). If you do not need this functionality, upgrading your subversion plugin to at least 1.45 should fix it. [1] https://issues.jenkins-ci.org/**browse/JENKINS-14755https://issues.jenkins-ci.org/browse/JENKINS-14755 -- oliver -- Tomasz Kowalczewski -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: PATH being ignored on SLES 10 with Jenkins ver. 1.466.2
Hi,
On 05/21/2013 07:47 AM, rusty wrote:
I am running into an interesting problem with jenkins on SLES 10.4. I have
two different python versions installed because I need python2.6 and not
2.4 for portability reasons that are not important.
Obviosly, I set up path variables on the machine so that jenkins would
build using python2.6 and not 2.4 I have set a node variable
PATH
/usr/local/bin/python:/usr/local/bin/:$PATH:/usr/local/bin/python:/usr/local/bin/
I have set the .bashrc file
I have set the /etc/profile
yet the path returned, even after a machine restart,disconnect-reconnect or
both, jenkins always returns the path...
PATH /usr/bin:/bin:/usr/sbin:/sbin
But running a simple job of :
import os
import sys
print sys.executable
print os.getenv(PATH, None)
print sys.path
import automate
Returns
*23:11:38* [sysn0t4] $ python /tmp/hudson3083762089535439523.py*23:11:38*
/usr/local/bin/python*23:11:38*
/usr/local/bin/python:/usr/local/bin/:/usr/local/bin/python:/usr/local/bin/:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin/python:/usr/local/bin/:/usr/local/bin/python:/usr/local/bin/*23:11:38*
['/tmp', '/usr/lib/python24.zip', '/usr/lib64/python2.4',
'/usr/lib64/python2.4/plat-linux2', '/usr/lib64/python2.4/lib-tk',
'/usr/lib64/python2.4/lib-dynload', '/usr/lib64/python2.4/site-packages',
What on earth is going on acording to the path returned.
/usr/local/bin/python (python2.6) should have been found first, but it
isn't. How do I insert python 2.6 onto the path correctly?
I have just experienced the same issue with a Mac salve. I couldn't
figure out the reason, but a workaround is to define the PATH variable
in the jenkins configuration for that slave (environment variables
section) with the correct entries. This is automatically propagated to
all jobs on that slave then. You can even reuse the existing path like
foo:${PATH}.
Cheers,
Johannes
signature.asc
Description: OpenPGP digital signature
Re: Build Flow job errors when run from Groovy
Yep, that's it. Thanks!
On Thursday, May 23, 2013 5:56:34 PM UTC-5, slide wrote:
This is an issue with email-ext, I am working on a fix and should release
soon. See [1] for more info.
slide
1 - https://issues.jenkins-ci.org/browse/JENKINS-17910
On Thu, May 23, 2013 at 3:48 PM, Foxgang tev...@gmail.com
javascript:wrote:
I am running the following Groovy from the system console:
def dummyBuildFlow = Jenkins.instance.getItem(my dummy job);
// Start it
println(Starting dummy build flow at +new Date());
def job = Queue.instance.schedule(dummyBuildFlow).future.get();
println(Dummy build flow finished at +new Date());
if (job.result.isWorseOrEqualTo(Result.UNSTABLE)) {
println(Build Flow had an error, failing this build.);
return false;
}
This was working earlier this morning. Since then, I have been making
configuration changes to emails and such, and I installed the latest PAM
Plugin update, but that's it.
However, the dummy build flow job has since begun failing:
ERROR: Failed to run DSL Scriptgroovy.lang.MissingMethodException
http://stacktrace.jenkins-ci.org/search?query=groovy.lang.MissingMethodException:
No signature of method: java.lang.String.rescue() is applicable for
argument types: (Script1$_run_closure2) values:
[Script1$_run_closure2@15be3df]
Possible solutions: execute(), size(), size(), reverse(), reverse(),
each(groovy.lang.Closure)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:55)
at
org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:46)
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at Script1.run(Script1.groovy:2)
at Script1$run.call(Unknown Source)
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at Script1$run.call(Unknown Source)
at
com.cloudbees.plugins.flow.FlowDSL.executeFlowScript(FlowDSL.groovy:82)
at com.cloudbees.plugins.flow.FlowRun$RunnerImpl.doRun(FlowRun.java:195)
at
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586)
at hudson.model.Run.execute(Run.java:1575)
at hudson.model.Run.run(Run.java:1521)
at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:174)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:241)
at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
FATAL: No signature of method: java.lang.String.rescue() is applicable for
argument types: (Script1$_run_closure2) values:
[Script1$_run_closure2@15be3df]
Possible solutions: execute(), size(), size(), reverse(), reverse(),
each(groovy.lang.Closure)groovy.lang.MissingMethodException
http://stacktrace.jenkins-ci.org/search?query=groovy.lang.MissingMethodException:
No signature of method: java.lang.String.rescue() is applicable for
argument types: (Script1$_run_closure2) values:
[Script1$_run_closure2@15be3df]
Possible solutions: execute(), size(), size(), reverse(), reverse(),
each(groovy.lang.Closure)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:55)
at
org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:46)
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at Script1.run(Script1.groovy:2)
at Script1$run.call(Unknown Source)
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at Script1$run.call(Unknown Source)
at
com.cloudbees.plugins.flow.FlowDSL.executeFlowScript(FlowDSL.groovy:82)
at com.cloudbees.plugins.flow.FlowRun$RunnerImpl.doRun(FlowRun.java:195)
at
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586)
at hudson.model.Run.execute(Run.java:1575)
at hudson.model.Run.run(Run.java:1521)
at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:174)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:241)
at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
If I had to guess, I'd say it looks like there some kind of classloader
contention between Groovy and Java that's causing methods to get invoked on
the wrong class when running in a Groovy instance. It happens every time I
try. Interestingly, if I trigger the job from the normal Build button, it
runs fine,
Re: Build Flow job errors when run from Groovy
I released a new version last night.
On May 24, 2013 5:07 AM, Foxgang teve...@gmail.com wrote:
Yep, that's it. Thanks!
On Thursday, May 23, 2013 5:56:34 PM UTC-5, slide wrote:
This is an issue with email-ext, I am working on a fix and should release
soon. See [1] for more info.
slide
1 -
https://issues.jenkins-ci.org/**browse/JENKINS-17910https://issues.jenkins-ci.org/browse/JENKINS-17910
On Thu, May 23, 2013 at 3:48 PM, Foxgang tev...@gmail.com wrote:
I am running the following Groovy from the system console:
def dummyBuildFlow = Jenkins.instance.getItem(my dummy job);
// Start it
println(Starting dummy build flow at +new Date());
def job = Queue.instance.schedule(**dummyBuildFlow).future.get();
println(Dummy build flow finished at +new Date());
if (job.result.isWorseOrEqualTo(**Result.UNSTABLE)) {
println(Build Flow had an error, failing this build.);
return false;
}
This was working earlier this morning. Since then, I have been making
configuration changes to emails and such, and I installed the latest PAM
Plugin update, but that's it.
However, the dummy build flow job has since begun failing:
ERROR: Failed to run DSL Scriptgroovy.lang.**MissingMethodException
http://stacktrace.jenkins-ci.org/search?query=groovy.lang.MissingMethodException:
No signature of method: java.lang.String.rescue() is applicable for
argument types: (Script1$_run_closure2) values:
[Script1$_run_closure2@15be3df**]
Possible solutions: execute(), size(), size(), reverse(), reverse(),
each(groovy.lang.Closure)
at
org.codehaus.groovy.runtime.**ScriptBytecodeAdapter.unwrap(**ScriptBytecodeAdapter.java:55)
at
org.codehaus.groovy.runtime.**callsite.PojoMetaClassSite.**call(PojoMetaClassSite.java:**46)
at
org.codehaus.groovy.runtime.**callsite.CallSiteArray.**defaultCall(CallSiteArray.**java:42)
at
org.codehaus.groovy.runtime.**callsite.AbstractCallSite.**call(AbstractCallSite.java:**108)
at
org.codehaus.groovy.runtime.**callsite.AbstractCallSite.**call(AbstractCallSite.java:**116)
at Script1.run(Script1.groovy:2)
at Script1$run.call(Unknown Source)
at
org.codehaus.groovy.runtime.**callsite.CallSiteArray.**defaultCall(CallSiteArray.**java:42)
at Script1$run.call(Unknown Source)
at
com.cloudbees.plugins.flow.**FlowDSL.executeFlowScript(**FlowDSL.groovy:82)
at
com.cloudbees.plugins.flow.**FlowRun$RunnerImpl.doRun(**FlowRun.java:195)
at
hudson.model.AbstractBuild$**AbstractBuildExecution.run(**AbstractBuild.java:586)
at hudson.model.Run.execute(Run.**java:1575)
at hudson.model.Run.run(Run.java:**1521)
at com.cloudbees.plugins.flow.**FlowRun.run(FlowRun.java:174)
at
hudson.model.**ResourceController.execute(**ResourceController.java:88)
at hudson.model.Executor.run(**Executor.java:241)
at hudson.model.OneOffExecutor.**run(OneOffExecutor.java:66)
FATAL: No signature of method: java.lang.String.rescue() is applicable for
argument types: (Script1$_run_closure2) values:
[Script1$_run_closure2@15be3df**]
Possible solutions: execute(), size(), size(), reverse(), reverse(),
each(groovy.lang.Closure)groovy.lang.**MissingMethodException
http://stacktrace.jenkins-ci.org/search?query=groovy.lang.MissingMethodException:
No signature of method: java.lang.String.rescue() is applicable for
argument types: (Script1$_run_closure2) values:
[Script1$_run_closure2@15be3df**]
Possible solutions: execute(), size(), size(), reverse(), reverse(),
each(groovy.lang.Closure)
at
org.codehaus.groovy.runtime.**ScriptBytecodeAdapter.unwrap(**ScriptBytecodeAdapter.java:55)
at
org.codehaus.groovy.runtime.**callsite.PojoMetaClassSite.**call(PojoMetaClassSite.java:**46)
at
org.codehaus.groovy.runtime.**callsite.CallSiteArray.**defaultCall(CallSiteArray.**java:42)
at
org.codehaus.groovy.runtime.**callsite.AbstractCallSite.**call(AbstractCallSite.java:**108)
at
org.codehaus.groovy.runtime.**callsite.AbstractCallSite.**call(AbstractCallSite.java:**116)
at Script1.run(Script1.groovy:2)
at Script1$run.call(Unknown Source)
at
org.codehaus.groovy.runtime.**callsite.CallSiteArray.**defaultCall(CallSiteArray.**java:42)
at Script1$run.call(Unknown Source)
at
com.cloudbees.plugins.flow.**FlowDSL.executeFlowScript(**FlowDSL.groovy:82)
at
com.cloudbees.plugins.flow.**FlowRun$RunnerImpl.doRun(**FlowRun.java:195)
at
hudson.model.AbstractBuild$**AbstractBuildExecution.run(**AbstractBuild.java:586)
at hudson.model.Run.execute(Run.**java:1575)
at hudson.model.Run.run(Run.java:**1521)
at com.cloudbees.plugins.flow.**FlowRun.run(FlowRun.java:174)
at
hudson.model.**ResourceController.execute(**ResourceController.java:88)
at hudson.model.Executor.run(**Executor.java:241)
at hudson.model.OneOffExecutor.**run(OneOffExecutor.java:66)
If I had to guess, I'd say it looks like there some kind of classloader
Re: Looking for XML report format that supports multiple iterations per test
I am looking at the NUnit samples, but I don't find an example of how to write a test report. However, I have noticed the following with JUnix XML in Jenkins: if there are two identical tests in the test suite, Jenkins reports them separately: testsuite name=TestsuiteName1 testcase classname=Package1.Class1 name=Test1 time=4 seed=3/testcase testcase classname=Package1.Class1 name=Test1 time=5 seed=9/testcase /testsuite I wonder if this would work, or if it would silently break something else? On Thursday, May 23, 2013 9:29:31 PM UTC-4, Mark Waite wrote: The NUnit framework supports that type of execution ( http://nunit.org/?p=testCaser=2.5.5), so you might try the NUnit plugin to see if its format meets your need. Mark Waite -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Clover Plug-in, Statement Coverage is always 0.
Hello, I have the same problem here but no solution. Notice that you also can use covhtml with the same syntax as bullshtml to generate even better output html than bullshtml. Statement coverage is really unneeded according to the bullseye guys. The best solution would possibly be that the bullseye guys either make a jenkins plugin or that they generate clover output files :) best regards, Tom, On Monday, 4 June 2012 13:33:08 UTC+2, Paul Schwann wrote: Hi there! I am using the clover plugin along with google's bullshtml to create a test coverage report in Jenkins out of my Bullseye Coverage data. It works very nice, the data are shown and in snyc with what Bullseye's own browser shows. There is one little detail though: Clover shows Conditional, Method and Statement coverage. For some reason, the statement coverage is always 0 (the other two are fine) Can I: 1) somehow make the plugin to show a value for statement coverage? or (if not) 2) somehow disable the statement coverage statistics in the clover plug-in? Thanks for your answer(s)! Regards, Paul -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: Unable to start ssh slave from OSX master
One final piece of info for the hypothetical future reader: The same JENKINS_HOME directory, copied to a Linux master, has the same failure, but a fresh Linux master didn't have the failure. Thus, the issue was somehow contained in Jenkins's saved state. Perhaps that will be useful to someone; perhaps not. -- Todd From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Todd Greer Sent: Wednesday, May 22, 2013 10:29 AM To: jenkinsci-users@googlegroups.com Subject: RE: Unable to start ssh slave from OSX master Yes, the Jenkins user can ssh to the slave without a password. I have even verified that this is possible in the Jenkins Groovy console (I was able to run a shell script in that user's home directory, and that script successfully used ssh). The slave launching process seems to fail somewhere before actually running a script (in the run a script to launch configuration). -- Todd From: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Chanda Unmack Sent: Tuesday, May 21, 2013 8:20 PM To: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com Subject: Re: Unable to start ssh slave from OSX master I came to that conclusion in our environment, for many other reasons. I inherited the setup which had a master on osx, with slaves connected via ssh (linux osx) as well as jnlp (windows) which is why I didn't feel that I could offer up any help. The only thing I wasn't clear on with your set up is whether or not the user you specify jenkins to ssh to the slave as can log into the slave without entering a password. chanda On Tue, May 21, 2013 at 5:05 PM, Todd Greer tgr...@affinegy.commailto:tgr...@affinegy.com wrote: In case anyone comes across this in web searches, I've tried many different things, and now suspect that using an OSX master with ssh slaves may simply not be a workable configuration, for unknown reasons. I've seen plenty of reports that it does work well with a Linux master, so that is my intent, and my suggestion to anyone in my situation. -- Todd From: Todd Greer Sent: Friday, May 17, 2013 2:48 PM To: 'jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com' Subject: Unable to start ssh slave from OSX master I'm trying to use the ssh slave plugin (v.21) from OSX, and have been unable to get it to initiate the ssh connection. The node is configured with the username and password, using the default port (which is correct). From a manual connection, there is an entry for the slave node in ~/.ssh/known_hosts. Other types of slave nodes are fine. When I try to start the node, or to look at the node's logs, I just get a spinner. In Jenkins's logs, I see Excess workload 1.0 detected. (planned capacity=0.0,Qlen=0.9976,idle=0.00,total=0m,=0.5). In system.log, I see Attempting to reconnect node-name. Other than that, I see no signs of activity, including in the slave node's auth log. Can anyone provide me with guidance on where to look next? Thank you, Todd -- Todd Greer Principal Scientist, Affinegy, Inc. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
xunit does not recognize failed tests anymore when I run a coverage tool
Hi, I recently started to use Opencover with my MSTest unit tests to get code coverage results. Since then the xunit plugin does not recognize errors as a Failure anymore. The TRX file is parsed and you can see at the summary page that there are tests failed and since when, but the job is counted as success and no email is triggered. Could it be that there is some delay now introduced inbetween writing the MSTest results file and processing by xunit that causes this behaviour? Any thoughts very welcome... Dirk PS: Here is the log: 18:44:02 D:\WS\CommonFunctionsTests\ContestContinuous\contest_swC:\Program Files\OpenCover\OpenCover.Console.exe -target:C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools\..\IDE\MSTEST.EXE -output:coverage.xml -targetargs:/testcontainer:D:\WS\CommonFunctionsTests\ContestContinuous\contest_sw\Bin\Debug\CommonFunctionsTests.dll /testsettings:D:\WS\CommonFunctionsTests\ContestContinuous\contest_sw\localtestrun.testsettings /resultsfile:D:\WS\CommonFunctionsTests\ContestContinuous\contest_sw\TestResults\CommonFunctionsTests\CommonFunctionsTests.trx -mergebyhash -targetdir:Bin\Debug -filter:+[CommonFunctions*]* 18:44:03 Executing: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\MSTEST.EXE 18:44:06 Microsoft (R) Test Execution Command Line Tool Version 10.0.30319.1 18:44:06 Copyright (c) Microsoft Corporation. All rights reserved. 18:44:06 18:44:06 Loading D:\WS\CommonFunctionsTests\ContestContinuous\contest_sw\localtestrun.testsettings... 18:44:07 Loading D:\WS\CommonFunctionsTests\ContestContinuous\contest_sw\Bin\Debug\CommonFunctionsTests.dll... 18:44:08 Starting execution... 18:44:18 18:44:18 Results Top Level Tests 18:44:18 --- --- 18:44:18 Passed CommonFunctionsTest.BufferedTraceListenerTest.BufferedTraceListenerConstructorTest [... Passes removed ...] 18:44:31 Passed CommonFunctionsTest.CommonFunctionsTest.ResizeTwoDimensionalArrayTest2 18:44:31 Failed CommonFunctionsTest.ContestConfigurationParametersTest.ContestConfigurationParametersFileTest 18:44:31 Passed CommonFunctionsTest.ContestSecurityStreamTest.ContestSecurityStreamConstructorTest [... Passes removed ...] 18:44:59 Passed TestcaseInformationTest.TestcaseXmlElementTest.TestcaseXmlElementConstructorTest2 18:45:00 216/217 test(s) Passed, 1 Failed 18:45:00 18:45:00 Summary 18:45:00 --- 18:45:00 Test Run Failed. 18:45:00 Passed 216 18:45:00 Failed1 18:45:00 --- 18:45:00 Total 217 18:45:00 Results file: D:\WS\CommonFunctionsTests\ContestContinuous\contest_sw\TestResults\CommonFunctionsTests\CommonFunctionsTests.trx 18:45:00 Test Settings: localtestrun 18:45:00 Committing... 18:45:00 Visited Classes 70 of 114 (61.4) 18:45:00 Visited Methods 588 of 1049 (56.05) 18:45:00 Visited Points 5763 of 12043 (47.85) 18:45:00 Visited Branches 1629 of 4073 (40.00) 18:45:00 18:45:00 Alternative Results (includes all methods including those without corresponding source) 18:45:00 Alternative Visited Classes 70 of 127 (55.12) 18:45:00 Alternative Visited Methods 676 of 1266 (53.4) 18:45:00 18:45:00 D:\WS\CommonFunctionsTests\ContestContinuous\contest_swC:\Program Files\ReportGenerator_1.8.1.0.\bin\ReportGenerator.exe -reports:coverage.xml -targetdir:coverage 18:45:01 Loading report 'D:\WS\CommonFunctionsTests\ContestContinuous\contest_sw\coverage.xml' 18:45:01 Preprocessing report 18:45:02 Indexing classes in directory 'c:\Snapshots\ContestContinuous\contest_sw\CommonFunctions\CommonFunctions\' 18:45:03 Added coverage information of 86/90 auto properties to module 'CommonFunctions' 18:45:03 Initiating parser for OpenCover 18:45:03 Current Assembly: CommonFunctions 18:45:03 Current Assembly: CommonFunctionsTests 18:45:03 Analyzing 89 classes 18:45:03 Creating report 1/89 (Assembly: CommonFunctionsTests, Class: CommonFunctionsTest.CommonFunctionsTest) [] 18:45:04 Creating report 84/89 (Assembly: CommonFunctions, Class: TSTraceOrigin) 18:45:04 Creating summary 18:45:04 Report generation took 3 seconds 18:45:04 Archiving artifacts 18:45:04 [htmlpublisher] Archiving HTML reports... 18:45:04 [htmlpublisher] Archiving at BUILD level D:\WS\CommonFunctionsTests\ContestContinuous\contest_sw\coverage to D:\Jenkins\jobs\CommonFunctionsTests\builds\2013-05-24_18-43-55\htmlreports\Coverage_Report 18:45:06 [xUnit] [INFO] - Starting to record. 18:45:06 [xUnit] [INFO] - Processing MSTest-Version N/A (default) 18:45:06 [xUnit] [INFO] - [MSTest-Version N/A (default)] - 1 test report file(s) were found with the pattern 'ContestContinuous\contest_sw\TestResults\CommonFunctionsTests\CommonFunctionsTests.trx' relative to 'D:\WS\CommonFunctionsTests' for the testing framework 'MSTest-Version N/A (default)'. 18:45:06 [xUnit] [INFO] - Check 'Failed Tests' threshold. 18:45:06 [xUnit] [INFO] - Check 'Skipped Tests' threshold. 18:45:06 [xUnit] [INFO] - Setting the build status to SUCCESS 18:45:06 [xUnit] [INFO] - Stopping
Re: Mass Jenkins job updates
On Monday, May 20, 2013 5:44:48 PM UTC-4, Bob Bick wrote: We have many Jenkins jobs defined that were copied from a “template” Jenkins job. Now, I discovered that I’d like to add a new build step to most (not all) of the jobs. I used the Job DSL plugin for a while but that turned out to be less flexible than I needed. Now, I use Python scripts which use the jenkinsapi library to grab a template job's config, replace the necessary parts, and create or update target jobs with the modified config. The excellent lxml library makes it easy to modify the XML document of the config. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
how to run applescript from Jenkins?
Hi, I've spent a couple days now trying to figure out why our build script runs fine from the command line, but gets execution error: An error of type -10810 has occurred. (-10810) when Jenkins runs it. The problem is a bit of Applescript we run towards the end of our script. When I simply put this line in Jenkins' Execute shell Command box: osascript -e 'tell application Finder to activate' I get the same error: execution error: An error of type -10810 has occurred. (-10810) How can I get Jenkins to run a bit of Applescript? Thanks, David -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
