Re: ldap config
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 dn: like dc=sun,dc=com,dc=cn
> > manager dn :XXX
> > manager password:
> > it is not right?
>
> Check to make sure your computer has port access to your LDAP server.
>
> If your LDAP server is an Active Directory machine, you might need to
> change the LDAP port to 3268.
>
> Here's a link to a Java based LDAP browser. Make sure you can log in
> with it, then use the same credentials for your Jenkins
> server:http://db.tt/PXK3dceQ. You might need to experiment with various
> things.
>
> The manger DN might be something like "DN=bob, OU=users, dc=com,
> dc=mycorp," or you might only need "DN=bob, OU=users" since Jenkins
> might append the root to the manager DN.
> --
> David Weintraub
> qazw...@gmail.com
Re: manual promotion of two jobs to pass parameters to a third job
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 parameters from both job A and B (i've included job version numbers): job_a_var1.1 job_a_var2.1 job_b_var1.1 job_b_var2.1 job_b_var3.1 Now let's say job A triggers, the new environment variable file will be: job_a_var1.2 job_a_var2.2 job_b_var1.1 job_b_var2.1 job_b_var3.1 So this way I can have variables persistent. I'll need to probably save and copy the file to the CI server from the nodes. Are there existing ways to do this or will I need to write my own plugin? I would have thought that joining two jobs with parameters would have been easier. Any help would be appreciated. Thanks, Matt On Thu, Feb 16, 2012 at 11:32 PM, Matt Fair wrote: > I have two jobs that I want to manually approve, let's call them Job A > and Job B. Job C is a job that I want to be executed when there is an > approved Job A and B. The scenario is one where I have separate > builds that I to join together to execute a deployment stage. > > Job A has the following parameters that I want to pass to Job C: > job_a_var1 > job_a_var2 > > Job B has the following parameters I want to pass to Job C: > job_b_var1 > job_b_var2 > job_b_var3 > > So when Job C is executed I want it to have the following parameters: > job_a_var1 > job_a_var2 > job_b_var1 > job_b_var2 > job_b_var3 > > If I update the code for Job A and approve it, I want it to use the > new parameters from Job A but the old once I last approved from Job B. > > Using the promotion plugin I have not been able to get the variables > from Job A and B to join properly to be parameters in Job C. It only > uses the newly approved job's parameters. > > So is a scenario like this possible? Any help would be greatly appreciated. > > Thanks, > Matt
Re: constant building from svn - no change
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 integrity as SCM.
>
> This issue is due to Multiple SCM plug in , Which uses same set of change log
> .xml for all the repos you configured.
>
> Only way to avoid this Is configuring Multiple Projects for each repo and
> Using Join Plug in
>
> Else Use "PreBuild Plugin (not yet released) "
>
> Thanks,
> Jagan Kalluri
> Build and Release Engineer
> Travelex Global Business Payments
> Email: jagan.kall...@travelex.com
> Phone: +1 (202) 408 1200 Ext: 6372
>
> http://travelexbusiness.com/na
> Twitter:www.twitter.com/travelexfx
> Winner Innovation of the Year 2010
> Financial-i Leaders in Innovation Awards
>
>
>
> -Original Message-
> From: jenkinsci-users@googlegroups.com
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of fiona
> Sent: Friday, February 17, 2012 7:45 AM
> To: Jenkins Users
> Subject: Re:constantbuildingfrom svn - no change
>
> I also met this situation, my the 1st line of the console of a build:
> started by scm change
>
> On 2月17日, 下午7时25分, Didier Durand wrote:
> > Hi,
>
> > Can you tell us what the very 1st line of the consol of a build: it
> > usually gives the reason for starting the build .
>
> > regards
>
> > didier
>
> > On 17 fév, 06:03, wrote:
>
> > > Hi Guys
>
> > > I have a multi repo project, both checkouts are from svn servers, and I
> > > have a 'poll scm' every 15 mins to build it.
>
> > > However, in the subversion changes, I can't see any changes, and the
> > > repos version numbers are not changing either, but it just keeps
> > >buildingmy project
>
> > > 500 builds later (oops - should have turned that off), I still can't work
> > > out what is triggering a build and why.
>
> > > I am running Jenkins 1.450 and subversion 1.37. Do you have any
> > > suggestions?
>
> > > Terry
> ***-
> Information in this email including any attachment ('email') is confidential,
> may be privileged and is intended solely for the addressee. Unauthorised
> recipients are requested to preserve the confidentiality of this email, advise
> the sender immediately of any error in transmission, and then delete the email
> from the recipient's mailbox without making copies. Any disclosure, copying,
> distribution or action taken, or omitted to be taken, in reliance upon the
> contents of this email by unauthorised recipients is prohibited and may be
> unlawful.
>
> Please note that no contracts or commitments may be concluded on behalf of
> Travelex Holdings Limited and its subsidiary companies ('Travelex') by means
> of
> email, and no statement or representation made in this email is binding on
> behalf of Travelex.
>
> DISCLAIMER: Whilst this message has been scanned for viruses, Travelex
> disclaims any responsibility or liability for viruses contained therein. It is
> therefore recommended that all emails should be scanned for viruses.
>
> Travelex -www.travelex.com
> ***--
> 隐藏被引用文字 -
>
> - 显示引用的文字 -
Optional File Parameterization?
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 with the file parameterization, which works great. However, any existing processes that try to submit a job end up failing if they don't pass in a file with the http request. Is there a way to have jenkins ignore if a file isn't passed in (perhaps making a zero-length file)? Or is there a better way to go about this? (Our job configuration is super complex, so maintaining two jobs with identical options modulo the build parameterization would probably end up with them desynchronizing). Thanks, Andrew
Re: Build next on failure and build periodically after failure
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 has failed. The plugin is - by the way - a real swiss army knife for chaining builds, so it's worth a look in any case. Also, I would like to build once a month at a particular place, until there is a failure, at which point I would like to start building daily until there is a success, after which I would like to go back to the monthly schedule. You could schedule builds once a month, but in addition use the https://wiki.jenkins-ci.org/display/JENKINS/Retry+Failed+Builds+Plugin with a delay of 1440 (=24*60) minutes. Cheers, Simon.
Build next on failure and build periodically after failure
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 possible? Also, I would like to build once a month at a particular place, until there is a failure, at which point I would like to start building daily until there is a success, after which I would like to go back to the monthly schedule. Is there a way to do this? Thanks...John
Re: Jenkins running Python website functional tests
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 good to know how you've configure python, how you've installed the selenium python library you refer to, etc) cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
