3 ms·
Don’t you have automated builds? The step in those builds should works on developer machines. Is that too much to ask? If the step in the build do not work? H
by dopidopHN 4y ago
Don’t you have automated builds?
The step in those builds should works on developer machines. Is that too much to ask?
If the step in the build do not work? How did that get merged in the first place ?
- Akronymus 4y ago> Don’t you have automated builds? Ideally, you would > The step in those builds should works on developer machines. Is that too much to ask? Quite often, yes. (Secrets that are only on the build server/shared database you cna't connect to without a barely working VPN and such) > If the step in the build do not work? How did that get merged in the first place ? Because there is no CI/CD pipeline to stop you? There are tons of reasons why it can be extremely hard to get into a legacy project as a new person. And that's just setting it up. Ideally, this wouldn't be the case. But sadly, the real world sucks
- dopidopHN 4y agoMan, you’re bringing me back a long long while ago. Last time I worked without reproducible builds was 2005-ish ? My experience : once someone in the C-suite vicinity enforce a lock-down, things fall in place rather quickly. Ex : nothing get deploy manually. I don’t care if we miss the next prod push, we will catch the next one. > the real world sucks My work is as grounded in the real world as well. And I spend year contracting for bottom feeders company. Hard to do more real crap. At some point is valuable to define priorities. > Because there is no CI/CD pipeline to stop you? There are tons of reasons why it can be extremely hard to get into a legacy project as a new person Fine. But lack of validation should not be a reason. If no pipeline checks and no humans checks as well. Then you are deploying un-vetted software.