First day of job

>first day of job
>asked to upgrade postgres to next major version in prod

This seems inappropriate, right? At least give me a few days to get up to speed.

Attached: zm2conyrn9f01.jpg (500x375, 18K)

Where do you work?

>modifying production directly
Tell them no

how big is the company?

any company that doesn't have testing servers for their database operations is a place you want to leave asap. start looking for a new job

That attitude will get you nowhere.
Just fucking do it retard. Are you competent enough for your job or not?
>why c-can't it all be play the first week like back in my high school
Eat shit.

It's a test, OP. Tell them no.

if they're pricks like just do it wrong on purpose and make them lose the whole database

If a little bit of downtime late at night is acceptable you can just do it, just make sure everything is backed up. Otherwise that's unreasonable for your first day to do a 0 downtime db upgrade without knowing the entire application architecture.

I sure love when OP makes a thread and leaves

Enforcing the basics of proper deployment isn't being obstructionist or lazy, it's how you avoid outages and down time. Hotfixes to critical bugs can be done on production if the impact is big enough, but playing with component upgrades without testing is fully retarded.

200+

I don't think it was a test, the CTO was asking my status

Against my better judgement, I just did it. Lots of stress but it worked.

apt upgrade

wow that was hard

what is your job title user? what did they hire you to do?

job title is DevOps Engineer

hurr durr it wasn't a single instance

I know that feeling. Rawdogging production gets your heart racing sometimes.

>DevOps
translation: Fuck testing and security, that gets in the way of the new shit that marketing wants. besides, sysadmins cost money, lets fire the bastards

remember to build a dead man's switch if they start fucking you over for any reason

>implying there aren't intricate pipelines that include every kind of testing imaginable
translation: probably some noob front-end dev

It is inappropriate, but not uncommon unfortunately.

this

only an actual retard who wants to be fired would make live changes to prod, especially if they're not familiar with the existing infrastructure

>Against my better judgement, I just did it. Lots of stress but it worked.
did you check for incompatibilities, potential bugs, etc? how much time did it take you to do it?

Hah I was just doing something similar this week

Hey guys look at me I push out code so fast I don't even need to run it to test it, I just know it works cuz I'm so good. Wow!!!

>sysadmin at medium small manufacturing company
>we produce the software that runs our hardware in-house too
>IT department builds and maintains nice test servers for them
>devs constantly BEGGING to force the entire company to switch to their latest build to "speed up testing"
NO, motherfucker, NO.

>Reply
Funny part is...devs probably know as much as you guys...but yall are slowing them down.

Sometimes working in the pharmaceutical industry and having change control up the ass isn't so bad...

>not having staging servers with h-1 data
>not having QA department

pleb office tbqh

wtf am i looking at

There's no reason to use dev in prod, that's why it's dev, not prod.

No, if the devs want it that's something else, they'll also be willing to deal with the flaws of the latest version unless reverted.

Why don't you have a clone of the latest data and database running on another container / VM for them?

PS: Of course these need to be able to be staged "forward" onto production at any time, too.

I don't know what else they could mean when they say I need to roll out the dev build to every workstation in the company so that everyone is testing it. We have a QA team for that.

Sure, "everyone" in the company probably isn't going to want to test it.

It would make sense if the people from individual dpt had some individual(s) that worked with the in-development versions so issues can be identified before weeks or months of time went into the respective changes, but all of them generally won't participate.

>not testing in prod

no do your job faggot

That's the final ouput, it's up to you to define the procedures and backout, test them in test and then promote on prod.