How to backtrack when asking dumb technical questions

[Telugodura456]

developer saying pushed code to dev but TC failing. I asked him can we backmerge to higher environment and check TC there.

My point dev is gajibiji because peopel are always comitting code. So higher environment lo better chance to know if TC are failing only due to our code.

did i ask a dumb question ?

[dasari4kntr]

5 minutes ago, Telugodura456 said:

developer saying pushed code to dev but TC failing. I asked him can we backmerge to higher environment and check TC there.

My point dev is gajibiji because peopel are always comitting code. So higher environment lo better chance to know if TC are failing only due to our code.

did i ask a dumb question ?

TC means test cases..?

if you do that…in higher environment…your higher environment also become dev (gajibiji…)…

[Telugodura456]

2 minutes ago, dasari4kntr said:

TC means test cases..?

yes

[dasari4kntr]

1 minute ago, Telugodura456 said:

yes

 

4 minutes ago, dasari4kntr said:

TC means test cases..?

if you do that…in higher environment…your higher environment also become dev (gajibiji…)…

 

[Telugodura456]

4 minutes ago, dasari4kntr said:

 

 

yea but he is saying dev is gajibiji now because of some other changes. If higher environment fail then we know it failed only due to our code and we can backtrack.

Right now dev is saying he does not know why tc is failing and is saying some ongoing dev work is reason not his f ix.

[Complex]

2 minutes ago, Telugodura456 said:

yea but he is saying dev is gajibiji now because of some other changes. If higher environment fail then we know it failed only due to our code and we can backtrack.

Right now dev is saying he does not know why tc is failing and is saying some ongoing dev work is reason not his f ix.

if you think environment is causing the TC failures  and you want to isolate 

try to deploy on to another non-prod environment and verify 

[Telugodura456]

Just now, Complex said:

if you think environment is causing the TC failures  and you want to isolate 

try to deploy on to another non-prod environment and verify 

yea thats exactly my thought. So i may have not asked as dumb a question as i thought.

[Thokkalee]

4 minutes ago, Telugodura456 said:

yea but he is saying dev is gajibiji now because of some other changes. If higher environment fail then we know it failed only due to our code and we can backtrack.

Right now dev is saying he does not know why tc is failing and is saying some ongoing dev work is reason not his f ix.

If you push a bug to higher environment, doesn’t it make the qa unstable as well? Or else ask for a down time and deploy and check.. 

[VendyHalwa]

20 minutes ago, Telugodura456 said:

developer saying pushed code to dev but TC failing. I asked him can we backmerge to higher environment and check TC there.

My point dev is gajibiji because peopel are always comitting code. So higher environment lo better chance to know if TC are failing only due to our code.

did i ask a dumb question ?

push it to prod akada direct ga fix chedam admin right ichesai

[Telugodura456]

5 minutes ago, Thokkalee said:

If you push a bug to higher environment, doesn’t it make the qa unstable as well? Or else ask for a down time and deploy and check.. 

it is not qa ..they have another environment which they use to validate all testing  ONLY FOR FIXES before pushing it in to prod gatra. it is not for general code movement which goes to qa.

[Thokkalee]

5 minutes ago, Telugodura456 said:

it is not qa ..they have another environment which they use to validate all testing  ONLY FOR FIXES before pushing it in to prod gatra. it is not for general code movement which goes to qa.

Whatever.. what is your doubt here?? 

[dasari4kntr]

38 minutes ago, Telugodura456 said:

yea but he is saying dev is gajibiji now because of some other changes. If higher environment fail then we know it failed only due to our code and we can backtrack.

Right now dev is saying he does not know why tc is failing and is saying some ongoing dev work is reason not his f ix.

does your team follow git flow model..?

if yes…dont merge your branch to either develop or release…

just deploy the feature directly in higher environment (non prod)…(by tweaking the pipeline configuration..)

once testing is done …re run the untouched develop and release branches…to restore the old  environments..

 

[Spartan]

  anna.... master branch code checkout chesi..

manam raase code update , and run the test cases local...

if they fail then its bug in ur code...

if it works push the code to Prod...anna...

Robust testing is important

-----------

if you are talking about integration tests, then u can mock the environment and make ur local build run the tests on other environment.

 

 

[Spartan]

back merging from higher env to lower env is dumb anna...

isunti jugaad lu chestarane...I keep 2 reviewers mandatory for merging.

no shortcuts there.

[Picha lite]

44 minutes ago, Spartan said:

  anna.... master branch code checkout chesi..

manam raase code update , and run the test cases local...

if they fail then its bug in ur code...

if it works push the code to Prod...anna...

Robust testing is important

-----------

if you are talking about integration tests, then u can mock the environment and make ur local build run the tests on other environment.

 

 

iyanni oddu antha direct prod lo avtada leda cheppu