devops team

[rokalibanda]

10 hours ago, Dimpy123 said:

itu randi, oka question undi...

Dimpy neku manam app unda 

[Dimpy123]

16 minutes ago, rokalibanda said:

Dimpy neku manam app unda 

enti....

[ManchoduSrinu]

17 minutes ago, rokalibanda said:

Dimpy neku manam app unda 

Sastaav

[Bangaruu]

3 hours ago, Dimpy123 said:

enti....

Rokalibanda asking about manam app ...Banda bumchiked desi girl from manam app 

[JasonBourne13]

On 2/10/2017 at 1:02 PM, Dimpy123 said:

let me explain , I am not deleting any one's commit 

developer

Manual tester

Automation Tester(me)

Requirement enti ante: normal ga everyday job schedule chesta night script run email notification vastundi(regression testing), but ma manager everyday automation script run cheyadam enduku, when developer did some changes appudu automation script run avvali automatic ga annaru, which we can able to it, but ippudu problem enti 2 or 1 hour difference tho 2 developers code commit chesinappudu automation script run avuthundi first developer commit ki, 2 nd developer commit chesinappudu queue lo untundi, but nenu emi antunna ante script mottam run avvadaniki 3 or 4 hours paduthundi I dont want wait till 4 hours anduku current job ni kill chesi new job ni fetch cheyali automatic ga

 

Nuv everyday developers 1-2 hour gap lo multiple commits ante... it's better to have a single build everyday. Everytime build trigger avvali ante 4 hours wait cheyalsinde. Or manual ga kill it and let it go. 

There are different ways to configure build triggers such as cron based scheduling, single build or poll repo etc. Jenkins lo aithe Quiet period set cheskovachu to keep the build from triggering ASAP.

My suggestion is since you have 4 hour build time, it's better to have a single build everytime or let all the builds run. Running all builds is a good thing because you can get to know which build has issues. If you have 20 commits within 4 hours, then your current requirement builds the last build and any problem needs to be dug deep into those 20 commits rather than accurately pointing to the faulty one.

One last resort, since iit's 4 hours, you can stop it manually!

[tom bhayya]

https://confluence.atlassian.com/bamboo/configuring-tasks-289277036.html

[Dimpy123]

6 hours ago, JasonBourne13 said:

Nuv everyday developers 1-2 hour gap lo multiple commits ante... it's better to have a single build everyday. Everytime build trigger avvali ante 4 hours wait cheyalsinde. Or manual ga kill it and let it go. 

There are different ways to configure build triggers such as cron based scheduling, single build or poll repo etc. Jenkins lo aithe Quiet period set cheskovachu to keep the build from triggering ASAP.

My suggestion is since you have 4 hour build time, it's better to have a single build everytime or let all the builds run. Running all builds is a good thing because you can get to know which build has issues. If you have 20 commits within 4 hours, then your current requirement builds the last build and any problem needs to be dug deep into those 20 commits rather than accurately pointing to the faulty one.

One last resort, since iit's 4 hours, you can stop it manually!

20 commits ithe 20 times script run avuthadi man, script running duration 4 hours 

[Dimpy123]

5 hours ago, tom bhayya said:

https://confluence.atlassian.com/bamboo/configuring-tasks-289277036.html

Thanks re Alex, I will look into it..

[KTR]

1 hour ago, Dimpy123 said:

Thanks re Alex, I will look into it..

em chustave Dimpy . Are you cheating Bangaru ?