thanks. i have gone through the wiki page. i guess following may be the issue :
1: back porting is not yet done from mainline release for this specific issue 2: baseline for current LTS candidate does not include jenkins version 1.515 in first case, do i need to create JIRA ticket and assign label as "lts-candidate" if yes, where is that option ? OR just create JIRA ticket and request for backporting through mail regards On Thu, Jul 4, 2013 at 11:54 AM, Vincent Latombe <[email protected]>wrote: > Hello Irfan, > > please read https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line > Most likely you won't get the mentioned issue in 1.509.x line as this > is an improvement. > There is always a tradeoff between stability and new features. > > Regards, > > Vincent > Vincent > > > 2013/7/4 Irfan Sayed <[email protected]>: > > thanks. > > after installing latest LTS release , the issue resolved. > > further, i am seeing one issue. > > > > there was one jira issue : > > https://issues.jenkins-ci.org/browse/JENKINS-17858 > > which got fixed in release 1.515 > > > > but, that change i am not able to see in latest LTS release 1.509.2 > > how we can ensure that these changes are pulled in latest LTS release ? > > > > regards > > irfan > > > > > > > > > > On Thu, Jul 4, 2013 at 12:15 AM, Oleg Nenashev <[email protected]> > > wrote: > >> > >> Hello Irfan, > >> > >> As you see, there many unresolved issues in JIRA (and many unanswered > >> threads at Google group). So, you should be patient and just hope for > the > >> answer... Anyway, nobody can keep track on all Jenkins issues. > Moreover, most > >> of "Jenkins experts" uses LTS builds for their production > installations, so > >> they don't even know about "new" issues :) > >> > >> Kevin is right, you should use LTS versions in order to avoid issues > with > >> updates. Jenkins (even the core) has not enough test coverage, so only > the > >> time and backports allow getting of "stable" versions. > >> > >> Regarding your issue... Probably, you should provide more detailed and > >> accurate description for the issue. For example, you have specified > >> "active-directory" component, so owners/watchers of the core component > had > >> not been notified about your issue. Moreover, there's no logs/job > configs, > >> so it would be difficult to reproduce issue. I haven't managed to do it > at > >> my installation... > >> > >> Best regards, > >> Oleg Nenashev > >> > >> > >> среда, 3 июля 2013 г., 21:06:38 UTC+4 пользователь Irfan Sayed написал: > >>> > >>> i am just seeking help from experts. just checking if someone has > already > >>> come across such issue > >>> sending email again and again does not mean that i am not putting > anyone > >>> under obligation. on the contrary, this implies that, i am really in > trouble > >>> and seek help. > >>> so, please consider this as request only and not anything else > >>> > >>> i feel proud myself that i am part of such nice Jenkins CI. > >>> let me try deploying LTS release and see if the issue vanishes > >>> > >>> regards > >>> > >>> > >>> > >>> > >>> On Wed, Jul 3, 2013 at 10:01 PM, Andrew Kujtan <[email protected]> > wrote: > >>>> > >>>> Not to mention the many commercial support options available, > >>>> > >>>> > >>>> > >>>> https://wiki.jenkins-ci.org/display/JENKINS/Commercial+Support > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> From: [email protected] [mailto:[email protected]] > On > >>>> Behalf Of Kevin Fleming (BLOOMBERG/ 731 LEXIN) > >>>> > >>>> > >>>> Sent: Wednesday, July 03, 2013 11:49 AM > >>>> To: [email protected] > >>>> Subject: Re: jenkins issue > >>>> > >>>> > >>>> > >>>> Nobody on this mailing list is under any obligation to help you, > nearly > >>>> everyone here participates as a volunteer to the project. > >>>> > >>>> > >>>> > >>>> If you need a stable, production ready version of Jenkins, you should > be > >>>> using an LTS release, not a weekly release. If you want to run weekly > >>>> releases, you need to be prepared for occasional breakage and capable > of > >>>> debugging and troubleshooting problems on your own. > >>>> > >>>> ----- Original Message ----- > >>>> From: [email protected] > >>>> To: [email protected], [email protected] > >>>> At: Jul 3 2013 11:40:47 > >>>> > >>>> i still haven't got any reply. > >>>> > >>>> this is very critical for me > >>>> > >>>> > >>>> > >>>> can someone please help > >>>> > >>>> > >>>> > >>>> regards > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> On Wed, Jul 3, 2013 at 1:50 PM, Irfan Sayed <[email protected]> > wrote: > >>>> > >>>> can someone please suggest on this issue? > >>>> > >>>> regards > >>>> > >>>> > >>>> > >>>> On Wed, Jul 3, 2013 at 12:38 PM, Irfan Sayed <[email protected]> > wrote: > >>>> > >>>> please suggest > >>>> > >>>> > >>>> > >>>> regards > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> On Tue, Jul 2, 2013 at 10:37 PM, Irfan Sayed <[email protected]> > wrote: > >>>> > >>>> please suggest. > >>>> > >>>> really stuck > >>>> > >>>> > >>>> > >>>> please > >>>> > >>>> > >>>> > >>>> regards > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> On Tue, Jul 2, 2013 at 8:07 PM, Irfan Sayed <[email protected]> > wrote: > >>>> > >>>> hi jesse, > >>>> > >>>> > >>>> > >>>> i am using jenkins for CI. > >>>> > >>>> facing one issue. https://issues.jenkins-ci.org/browse/JENKINS-18571 > >>>> > >>>> > >>>> > >>>> i have seen you have already fixed such issue some time back > >>>> > >>>> can you please have a look and give me some pointers > >>>> > >>>> > >>>> > >>>> please suggest > >>>> > >>>> > >>>> > >>>> regards > >>>> > >>>> irfan > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> You received this message because you are subscribed to the Google > >>>> Groups "Jenkins Developers" group. > >>>> To unsubscribe from this group and stop receiving emails from it, send > >>>> an email to [email protected]. > >>>> > >>>> For more options, visit https://groups.google.com/groups/opt_out. > >>>> > >>>> > >>>> > >>>> -- > >>>> You received this message because you are subscribed to the Google > >>>> Groups "Jenkins Developers" group. > >>>> To unsubscribe from this group and stop receiving emails from it, send > >>>> an email to [email protected]. > >>>> > >>>> For more options, visit https://groups.google.com/groups/opt_out. > >>>> > >>>> > >>>> > >>>> -- > >>>> You received this message because you are subscribed to the Google > >>>> Groups "Jenkins Developers" group. > >>>> To unsubscribe from this group and stop receiving emails from it, send > >>>> an email to [email protected]. > >>>> > >>>> For more options, visit https://groups.google.com/groups/opt_out. > >>>> > >>>> > >>> > >>> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "Jenkins Developers" group. > >> To unsubscribe from this group and stop receiving emails from it, send > an > >> email to [email protected]. > >> For more options, visit https://groups.google.com/groups/opt_out. > >> > >> > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Jenkins Developers" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
