Комментарии:
Helps with version control too! Love ur vids
ОтветитьI appreciate your explanation here. As a career DevOps professional, I have had many challenges explaining what CI/CD is and why we NEED to use it.
ОтветитьLove this simple explanation ❤
ОтветитьIt's an incomplete definition. How will it become continuous? Feedback should be taken into consideration. Thanks.
ОтветитьLove your gorgeousness
ОтветитьThanks so much for this
ОтветитьNever heard it called that before, it’s the standard software development lifecycle. You develop your code in the development system, if it works there you get it promoted to the test system (sometimes called QA) which is near production and has production data, and you test it more thoroughly and with other production functionality etc, basically you want to make sure it works properly and doesn’t break acting else. You write test scripts to do this with Expected outcomes and a test team will typically carry them out. If they pass it gets promoted to production which is the live environment, if they don’t you fix the bugs in dev and start again
ОтветитьOKay CI/CD in less time than the video. Continuous Integration is where you develop your code and park it in a repository before someone gives it the all clear to push to production. Continuous Deployment, Develop, Test, Deploy directly to production. Done. There's a details of course, but that's the concept.
ОтветитьSo I started coding a 'professionally' written app in 97 and deployed in 98.
I used, C++ Builder version 3 (1997 product). I use the same product today, but a 2013 version of the product.
But this is what I knew, code,compile, test, build, deploy.
When I started coding I did not do topics or anything in IT. It was not taught in schools. Boot camps did not exist, internet don't exist, I got a bunch of CDs and I learned from those. Eventually I got very heavy in the win 32 API.
C+ Builder made it very easy to build complex graphically driven applications. The enterprise versions makes it easy to deploy data driven apps.
But as you put it we were doing continuous integration and continuous deployment.
The first few years was tough because there were bugs all around.
Had to do a lot of rewriting to make things work stable. Using of course CI/ CD.
Really needed this explanation. Thanks.
ОтветитьI love the guys here who try to correct you by saying exactly what you just said. lol Thanks, Tiff!
Ответитьare there tools for CI/CD? great explanation there :)
ОтветитьInteresting
ОтветитьCI/CD is a powerful tool that can help to improve the quality, reliability, and speed of software delivery. However, it is important to note that CI/CD is not a silver bullet. It requires careful planning and implementation in order to be successful.
ОтветитьExcellent 😊my hat 🎩 is off to you !
Ответить❤
ОтветитьWell done and thoughtful
After 30 years of code Development this is angelic
Thank you! Im a security guy trying to work with DevOps more often and has never made sense to me
ОтветитьFirst time people be like
"Damn so I just have to git push , and the it will update itself "😮
Ahahah
GitHub action and Jenkins with docker , does everything , literally save your time a lot ahah
I subbed because of the nails!
ОтветитьThe name explains it, couldn't be simpler
ОтветитьNice video, a lot of these comments are not passing the vibe check lol
ОтветитьThank you so much for explaining this in simple words.
Ответитьhit, next question
ОтветитьI appreciated the explanation,but i honestly felt that you look so beautiful.
ОтветитьStill missing few things if this is for beginners
ОтветитьThanks
Ответить❤❤❤
Ответить