Bala, I already told you on the Sonar list, now I'll repeat this on the Jenkins list as well. Mailing lists are not some sort of "dump-your-problems" facility. Seriously. Usually one should do the following before approaching others:
- get the basics straight. The basics and also advanced topics can be found in the respective documentation (you read that, right? if you didn't you know what to do the next days) - analyze your problem (google is a fantastic tool btw) - stuck? analyze it again - if you're really stuck, then is the time to search for help from others All your mails scream, that you neither did read any introductory documentation nor did take a closer look into any of your issues. This is not how it's meant to be played. This may sound harsh, but you're generating loads of traffic that nobody helps. regards Andreas Schilling CAE Processes & Data Management ------------------------------------------------------------------- Dipl. Inf. Andreas Schilling Senior Software Architect TWT GmbH Science & Innovation Bernhäuser Str. 40 - 42 73765 Neuhausen Tel: +49.7158.17 15.6 73 Mobil: +49.1 72.6 22 88 70 E-Mail: andreas.schill...@twt-gmbh.de -------------------------------------------------------------------- www.twt-gmbh.de -------------------------------------------------------------------- Geschäftsführung: Dimitrios Vartziotis, Joachim Laicher (Stv.), Frank Beutenmüller (Stv.) Registergericht: Amtsgericht Stuttgart, HRB Nr. 212778 Umsatzsteuer: ID-Nr.: DE147841145 -------------------------------------------------------------------- Von: bala nageswar Chadalavada <baluch...@gmail.com> An: Slide <slide.o....@gmail.com> Kopie: "jenkinsci-users@googlegroups.com" <jenkinsci-users@googlegroups.com> Datum: 23.01.2013 09:15 Betreff: request on version Jenkins ver. 1.494 upgrade Gesendet von: jenkinsci-users@googlegroups.com Hi Slide thanks a lot.i will chek on that now we are planning to move from 1.494 to Latest version of jenkins we have 1) Linux Environment path located under opt /apachetomcat/webapps Now if we upgrade it to new version of jenkins do we need re-configure the LDAP Settings and all what about the JOB HISTORY Created till please explain thanks bala On Wed, Jan 23, 2013 at 1:05 PM, Slide <slide.o....@gmail.com> wrote: If they are showing as red, then they failed somehow. You need to paste your build log, or look further into it. Jenkins shows a red ball when _something_ (not necessarily just your build steps) fail during that project's execution. Without further info (build log, etc) no one here can help you. On Wed, Jan 23, 2013 at 12:30 AM, bala nageswar Chadalavada < baluch...@gmail.com> wrote: OK i Enabled AUTO Fresh. for example...yesterday Nightly builds are scheduled ran successfully but it has shown as RED little confused here thanks bala On Wed, Jan 23, 2013 at 12:55 PM, Slide <slide.o....@gmail.com> wrote: I understand your request and I am telling you that something in the build, whether it is your stuff or something that happens in post-build is failing and making the job be marked as failure. You need to look at your build log and find out why. Otherwise, check to make sure that you have auto-refresh enabled so that if the build occurs it updates the main page. On Wed, Jan 23, 2013 at 12:23 AM, bala nageswar Chadalavada < baluch...@gmail.com> wrote: My request was.. Even after the SUCCESSFUL BUILD the main jenkins page showing as RED Actual should be BLUE On Wed, Jan 23, 2013 at 12:44 PM, Slide <slide.o....@gmail.com> wrote: It sounds like your builds are failing at some point, you need to look at the build log and find out why its being marked as a failure. On Tue, Jan 22, 2013 at 11:25 PM, bala nageswar Chadalavada < baluch...@gmail.com> wrote: hI PLEASE let me know why he builds show red after success ful builds i am using the Jenkins ver. 1.494 please suggest further -- Bala.ch -- Website: http://earl-of-code.com -- Bala.ch -- Website: http://earl-of-code.com -- Bala.ch -- Website: http://earl-of-code.com -- Bala.ch
