Hi Arvind, We are in the same state as explained in this thread.
1. One of the pipeline is not getting triggered and below is the "INFO" [which looks like an error] we get in the Log. What do we do to avoid this issue? 2017-02-27 16:40:17,658 INFO [qtp1172769370-88076] PipelineScheduler:124 - [Pipeline Schedule] [Requested] Manual trigger of pipeline 'BetaWd_Regress' requested by [email protected] 2017-02-27 16:40:17,660 INFO [qtp1172769370-88076] PipelineScheduler:130 - [Pipeline Schedule] [Accepted] Manual trigger of pipeline 'BetaWd_Regress' accepted for user [email protected] 2017-02-27 16:40:17,663 INFO [qtp1172769370-88076] PipelineScheduler:134 - [Pipeline Schedule] [Processed] Manual trigger of pipeline 'BetaWd_Regress' processed with result 'com.thoughtworks.go.serverhealth.ServerHealthState@3c45bfa6[healthStateLevel=OK,type=<HealthStateType DATABASE_DISK_FULL LogScope[GLOBAL, scope=GLOBAL]>,message=,description=,expiryTime=<null>,timestamp=Mon Feb 27 16:40:17 IST 2017]' On Friday, 8 May 2015 19:45:07 UTC+5:30, Aravind SV wrote: > > Which is the pipeline you forced? If it is BCB_DSE_RLS, I see that it did > build. > > On Thu, May 7, 2015 at 8:46 PM, 강호진 <[email protected] <javascript:>> > wrote: > >> Thank you for your answer. >> >> It is correct scenario. Just I did like that. There is no event log on >> the right corner. >> >> And very sad.. server operator deleted server logs... I got backup logs >> only. here (http://blog.naver.com/df93/220353266375) >> >> >> 2015년 5월 8일 금요일 오전 8시 49분 32초 UTC+9, Aravind SV 님의 말: >>> >>> I think we should step back a bit and understand this. Can you tell me >>> whether this is correct? >>> >>> Scenario: You have pipelines setup, and you choose one pipeline and >>> click the trigger button. It disables the trigger button, and then enables >>> the trigger button, without running a build. Correct? >>> >>> If so, do you have a warning or error in the bottom right corner (little >>> red box), for that pipeline? >>> >>> If the earlier scenario is not correct, what is it? What is the behavior >>> like? It might help if you zip the whole server log and send it, once the >>> scenario is understood. >>> >>> - Aravind >>> >>> On Thu, May 7, 2015 at 12:00 PM, 강호진 <[email protected]> wrote: >>> >>>> All pipelines. >>>> I was not check every pipelines but I can not see pipeline assigned >>>> agent. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "go-cd" 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/d/optout. >>>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "go-cd" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "go-cd" 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/d/optout.
