Fixed in version fitnesse-1.9
https://github.com/jenkinsci/fitnesse-plugin/commit/d784a62b1f82b87506346ad11eab7a1aade3647c
See pull request : https://github.com/jenkinsci/fitnesse-plugin/pull/10
Le samedi 9 mars 2013 21:30:30 UTC+1, Stanimir Stamenkov a écrit :
Starting with version 1.6 of the
We have a regressions server, running regressions of different
applications, using Jenkins.
Some of these applications, tend to misbehave during the regression run,
and the build needs to be aborted. The runtimes of these applications are a
mix of JVM and native code, interfaced via JNI, and
You forgot to mention your Jenkins version. Killing processes was broken on
Linux from 1.553-1.574.
On 28.08.2014, at 11:48, ptol...@tibco.com wrote:
We have a regressions server, running regressions of different applications,
using Jenkins.
Some of these applications, tend to misbehave
Daniel,
thanks for your message. its currently 1.565.1 and yes we are using linux.
so looks like we need to upgrade?
regards,
pankaj
On 28 August 2014 11:14, Daniel Beck m...@beckweb.net wrote:
You forgot to mention your Jenkins version. Killing processes was broken
on Linux from
many thanks for the pointer. we have upgraded to the latest which is 1.577.
hope this was it.
On 28 August 2014 11:21, Pankaj Tolani ptol...@tibco.com wrote:
Daniel,
thanks for your message. its currently 1.565.1 and yes we are using linux.
so looks like we need to upgrade?
regards,
Within the Jenkins environment you can have multiple build jobs that do
different things.
The idea is that you have one source repository, one build environment
(Jenkins) and one binary repository (Artifactory). You can manage the
versions of source to produce builds and then place build in
I'm in a company that builds both .NET Java applications. I want to be able
to use a common process to deploy previous built applications to target
servers. To further complicate issues, I have to be able to deploy code to both
in-house, cloud, and client side servers. I use Jenkins as my CI
Thanks Mark Vincent!
Terry
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: Wednesday, August 27, 2014 11:57 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Question about git polling nonexisting_workspace
Vincent is correct.
Hi All,
I'm using some groovy post build script to kick off a job:
manager.listener.logger.println(Test job needs triggering)
ds_job = manager.hudson.getItem('MyTestJob')
def params = [ new StringParameterValue('Param1', param)]
ds_job.scheduleBuild2(0, new
it appears that jumbo frames were causing problems for the ssh connections
between the master and slaves systems.
setting my MTU back to the default (1500) from 9000 has allowed my builds
to run.
On Wednesday, August 27, 2014 7:49:28 PM UTC-7, Aaron Molitor wrote:
updated Jenkins to 1.577
Hi,
I am planning to use Jenkins to build CI process with AccuRev as the SCM.
I saw in one of the blogs that it supports AccuRev Plugin.
I tried to download / Install the Plugin through “Manage Jenkins à Manage
Plugins àAvailable TabàAccuRev Plugin (0.6.30 Version) à Install Without
Hi All,
I´m using the LDAP in order to authenticate the users in Jenkins, but I
would like to allow an user outside of LDAP, also authenticate in Jenkins.
I mean, execute the authentication trough LDAP and Jenkins own user
database.
Is it possible?
Thanks.
Rodrigo
Need to display text at the top of the login screen only, giving a warning
about unauthorized access (and so on). Suggestions?
--
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,
Copied from: https://issues.jenkins-ci.org/browse/JENKINS-24006
Thanks for implementing this.
I tried it out and have an issue. After saving a job with a new
amplification factor, going back to the config screen always loads the
default 1.0 amplification factor, rather than the saved
Unable to access https://svn.mogucaifu.com:8596/svn/mogu/android/trunk :
svn: E175002: OPTIONS /svn/mogu/android/trunk failed
org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS
/svn/mogu/android/trunk failed
at
I don’t know if you can do that. But I do know that you could support both
users authenticated through LDAP and anonymous users. Perhaps that would work
for you?
Terry
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Rodrigo Maccari
Sent: Thursday,
Am 29.08.2014 um 05:04 schrieb Xinglin Cai:
Caused by: svn: E170001: OPTIONS of '/svn/mogu/android/trunk': 403 Forbidden
(https://svn.mogucaifu.com:8596)
Check your credentials.
HTH...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*,
17 matches
Mail list logo