Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "continuous deployment"
Feeling like I've gone back in time about 15 years!
Just told my CTO about various improvements we could make to the development process. Things like git, continuous delivery, agile project management apps such as Jira, task management such as Gulp, etc.
His response - "never heard of them. I bet they'll pass in a few months. Just another round of fads".8
I've been fired today and somehow it was an relief :)
As I know that I am pretty much the only one who knows how the infrastructure works and I am the only one who actively tried to get the company to a better level of coding (tests, code reviews, proper deployment / continuous integration,...) It somehow feels like that gif.10
When good developers are afraid of refactoring and adding new classes is something to be feared, you need to rethink your architecture.
In fact, if there's ever that "dark corner" of code that no-one likes to work with, you've got to fix it.
It's like continuous deployment. We do it often because it's hard and having to deploy regularly forces us to make it easier.3
Tl;Dr Im the one of the few in my area that sees sftping as the prod service account shouldn't be a deployment process. And the ONLY ONE THAT CARES THAT THIS IS GONNA BREAK A BUNCH OF SHIT AT SOME POINT.
The non tl;dr:
For a whole year I've been trying to convince my area that sshing as the production service account is not the proper way to deploy and/or develop batch code. My area (my team and 3 sister teams) have no concept of using version control for our various Unix components (shell scripts and configuration files) that our CRITICAL for our teams ongoing success. Most develop in a "prodqa like" system and the remainder straight in production. Those that develop straight in prodqa have no "test" deployment so when they ssh files straight to actual production. Our area has no concept of continuous integration and automated build checking. There is no "test cases", no "systems testing" or "regression testing". No gate checks for changing production are enforced. There is a standing "approved" deployment process by the enterprise (my company is Whyyyyyyyyyy bigger than my area ) but no one uses it. In fact idk anyone in my area who knows HOW to deploy using the official deployment method. Yes, there is privileged access management on the service account. Yes the managers gets notified everytime someone accesses the privileged production account. The managers don't see fixing this as a priority. In fact I think I've only talk to ONE other person in my area who truly understands how terrible it is that we have full production change access on a daily basis. Ive brought this up so many times and so many times nothing has been done and I've tried to get it changed yet nothing has happened and I'm just SO FUCKING SICK that no one sees how big of a deal this. I mean, overall I live the area I work in, I love the people, yet this one glaring deficiency causes me so much fucking stress cause it's so fucking simple to fix.
We even have an newer enterprise deployment. Method leveraging a product called "urban code deploy" (ucd) to deploy a git repository. JUST FUCKING GIT WITH THE PROGRAM!!!!..... IT WAS RELEASED FUCKING 12 YEARS AGO......
Please..... Please..... I just want my otherwise normally awesome team to understand the importance and benefits of version control and approved/revertable deployments2
So, right now we upload production code by means of FTP.
I said it would be better to use continuous deployment using Docker, but they said it was overkill (I work at a small company).
Because manually uploading by means of FTP is so much better right...6
Salutations fellow devs,
I come here today to seek your wisdom about an issue that is troubling me more and more lately. Here is the situation: I am a data scientist, my core skills are to build and implement models for classification/regression/clustering purposes. Working at a Startup, we don't have a person in charge of putting into production the models I build, so I'm in charge of that; the problem is that I'm really not skilled at it. We use an IaaS cloud service to deploy our code, and I manage to somehow make things work, but the whole thing could be improved to make the deployment faster, do continuous integration, make the servers handle more requests per time unit, and reduce the costs of the cloud infrastructure. So here is the question: can you point me to books/tutorials/online courses about "this stuff" (I'm guessing DevOps but I'm not really familiar with the term)?
Side note: I would really like to know if any of you was in this situation and how did you manage it.
Every time we have a release, "Release Engineering" stops building our test environments from master. I've been preaching Continuous Deployment for months and here we are with the most broken system. The build actually builds all test environments AND prod from the same branch because "it's easier" for "Release Engineering". So now I have to wait for the code freeze on release and hope RE doesn't fuck up and deploy an untested branch to prod... AND hope we're given enough time to test and debug the next release since we can't right now...1
For all the effort it takes to setup CI/CD it's totally worth it. My god this is marvellous I've wasted over 40 build minutes already just to see a spinner spin until it turns green :-D2
The integration of technologies project I have this year. Not yet finished but I already learned a lot of very cool stuff.
First, I learned a new programming language + framework (Ruby on Rails)
Second, for the first time, I implemented a continuous deployment pipeline with Capistrano and Travis ci.
Third, first time I programmed a Restful API.
And more cool stuff coming up ! :D
I freaking love learning !
Auto Login feature enables itself when a certain config flag is present - the app will login as an admin without requiring username or password.
I pray to the Continuous Deployment monsters that the config setting never gets copied to production by mistake.2
Finally successfully set up continuous deployment on a personal project. Ever, really. And on one of my few open source applications. Destiny Clan Manager... it uses the Bungie API to help you manage your clan on Destiny 2. Neat little weekend project. Made some changes today, and thought... why not. It's all using Azure.
If you're interested: https://github.com/demortes/DCM2
What is the best approach for Continuous Integration / Continuous Delivery/Deployment? I'm using SVN as code repository and I need to identify the files that goes to Test/QA env. and the ones that goes do Prod env. (by Commit message or something else) via sFTP.
Any help would be appreciated. Already tested Jenkins, GoCD and Jetbrains Teamcity.1
Yesterday we had discussion on with developers about continuous deployment. When I asked one of the senior developers why they can't uncommit what commits you made to integration branch and which led to integration test failures. He said it's against the basic philosophy of git to uncommit... I don't know how git works...but seriously you can't use previous version of code or can't uncommit??6
I've been thinking about ways to improve my workflow for my personal projects.
I'm getting to grips with continuous integration and deployment etc, but I want to also automate, or at least semi automate my changeling generation.
I don't like using any sort of gitlog shenanigans, and I quite like the girls way of doing it.
I.e you run a script which generates a yaml file with your changeling info in, and then all the files are written into the changelog.md file.
How do you guys handle the generation of your changelings?3