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
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
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
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;
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
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:
I wonder if this would work, or if it woul
I released a new version last night.
On May 24, 2013 5:07 AM, "Foxgang" 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
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,
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 machi
Thank you for prompt answer!
On Fri, May 24, 2013 at 10:00 AM, oliver gondža 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). Re
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)
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: je
Hi,
we are running Jenkins v1.515 and occasionally have problems with hanging
builds. After all tests run with success and build is over from the test
runner perspective Jenkins will go into hudson.tasks.MailSender class and
will spend there dozens of minutes. The build will eventually complete
13 matches
Mail list logo
