On 17/02/2012 19:02, SteveB wrote:
Trying to use Jenkins to run python-selenium-testng scripts to do
website functional testing and have Jenkins collect the testng
result. (FYI this is on a ubuntu system)
Can you please include full examples of the tracebacks you're seeing?
(It'd also be goo
For post-build actions, jenkins allows
Build other projects under the following conditions:
Trigger only if build succeeds
Trigger even if the build is unstable
Trigger even if the build fails
But I want to build the other project only if this project
fails. Is that
Hi John,
John R. Cary wrote (19.02.2012 19:45):
But I want to build the other project only if this project
fails. Is that possible?
The
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin
has a dedicated option to trigger downstream projects _only_ if the
current build
Hello, everyone-
We currently use jenkins to test commits that are in our Git
repository, but I'd like to add support for developers to test their
current workspace with jenkins before the commit makes it up. I added
some logic to the beginning of the build process to unpack a tarball
passed in wi
hi,
I met this problem when use master and slave, I have only one repo,
this issue happened in no regular time
BTW, the problem arised when we have built many hundreds builds .
On 2月18日, 上午12时41分, "Kalluri, Jagan"
wrote:
> Hello Fiona,
>
> I also experience this problem, We are using Mks integrit
So I have come up with a way to do this, but not sure what the best
way to implement it. Basically if I save the previous parameters to
a file so when the job is re-executed, they are loaded and new
variables are updated.
Let's assume I have an environment variable file already saved with
parame
now it works, I modify 'user search filter' to 'sAMAccountName{0}',
thanks for the support!
On 2月17日, 下午11时48分, David Weintraub wrote:
> On Fri, Feb 17, 2012 at 5:09 AM, fiona wrote:
> > After I config ldap security, when anyone can't logon, my
> > configuration is:
> > server : X
> > root
