Good work team (me, myself and I)!
-
This morning I deleted my entire development environment. A couple of Azure Functions, a WCF SOAP service and a ASP.NET Core app hosted in App Services, Azure SQL Database, Application Insights, ServiceBus, Storage Account, Key Vault... I changed the names of pretty much all Azure resources, pipelines, repositories and projects so there's some consistency between them. Then I deployed them all using my Azure DevOps pipelines. I got a couple of errors, which are now fixed and the development environment is up and running again. Overall, this wasn't so bad :)
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
This morning I deleted my entire development environment. A couple of Azure Functions, a WCF SOAP service and a ASP.NET Core app hosted in App Services, Azure SQL Database, Application Insights, ServiceBus, Storage Account, Key Vault... I changed the names of pretty much all Azure resources, pipelines, repositories and projects so there's some consistency between them. Then I deployed them all using my Azure DevOps pipelines. I got a couple of errors, which are now fixed and the development environment is up and running again. Overall, this wasn't so bad :)
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
:thumbsup:
-
This morning I deleted my entire development environment. A couple of Azure Functions, a WCF SOAP service and a ASP.NET Core app hosted in App Services, Azure SQL Database, Application Insights, ServiceBus, Storage Account, Key Vault... I changed the names of pretty much all Azure resources, pipelines, repositories and projects so there's some consistency between them. Then I deployed them all using my Azure DevOps pipelines. I got a couple of errors, which are now fixed and the development environment is up and running again. Overall, this wasn't so bad :)
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
This morning I deleted my entire development environment. A couple of Azure Functions, a WCF SOAP service and a ASP.NET Core app hosted in App Services, Azure SQL Database, Application Insights, ServiceBus, Storage Account, Key Vault... I changed the names of pretty much all Azure resources, pipelines, repositories and projects so there's some consistency between them. Then I deployed them all using my Azure DevOps pipelines. I got a couple of errors, which are now fixed and the development environment is up and running again. Overall, this wasn't so bad :)
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
This morning I deleted my entire development environment. A couple of Azure Functions, a WCF SOAP service and a ASP.NET Core app hosted in App Services, Azure SQL Database, Application Insights, ServiceBus, Storage Account, Key Vault... I changed the names of pretty much all Azure resources, pipelines, repositories and projects so there's some consistency between them. Then I deployed them all using my Azure DevOps pipelines. I got a couple of errors, which are now fixed and the development environment is up and running again. Overall, this wasn't so bad :)
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
You're a braver man than me. I'm not sure I would have dared make such changes :omg:
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
This morning I deleted my entire development environment. A couple of Azure Functions, a WCF SOAP service and a ASP.NET Core app hosted in App Services, Azure SQL Database, Application Insights, ServiceBus, Storage Account, Key Vault... I changed the names of pretty much all Azure resources, pipelines, repositories and projects so there's some consistency between them. Then I deployed them all using my Azure DevOps pipelines. I got a couple of errors, which are now fixed and the development environment is up and running again. Overall, this wasn't so bad :)
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
A few months ago a new consultant attempted to deploy a change she had made to a component to our dev environment. She did that successfully. However, all other components were deleted in the process. Took about an hour of running various Jenkins jobs to get it back again.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
-
Wot, no Docker mentioned :wtf:
Nah, not really necessary :D Although I do plan to take a look at it sometime soon. I see it asked a lot!
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
You're a braver man than me. I'm not sure I would have dared make such changes :omg:
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
You have to break a few eggs to make an omelette :D Also, this code is not yet in production and apart from another developer, who works a few hours a week on this project, I'm the only developer. Basically, this was all mine and it was all new. The reason it wasn't consistent in the first place was that I had to make a few things work rather quickly to impress the customer. Now that I'm in I can make it beautiful (and rather now than later) :D
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
A few months ago a new consultant attempted to deploy a change she had made to a component to our dev environment. She did that successfully. However, all other components were deleted in the process. Took about an hour of running various Jenkins jobs to get it back again.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
Wow :wtf: That's either some impressive incompetency or your release pipelines are very weird :laugh: I once pushed a chance to production, at the request of a client. I simply pushed the deploy button of that project's release pipeline (because all my changes worked locally and on test and on acceptance). Turned out that the version that was currently on production wasn't a version that was in source control, some manual steps had to be done. I did not have the privileges to enter the production server at all, let alone do those manual steps. The version I released fixed my issue, but broke another part of the application completely, because some unfinished changes were sitting on the master branch since long before I got there. To make things worse, this component had two release pipelines and I used the wrong one. Even though they used VSTS, the version I had just overwritten was gone, so I couldn't put it back either. This was at 07:00, the person who could fix this came in at 07:30 and it all had to be back up before opening time at 08:00. Needless to say, no one was amused, and the release pipelines were from then on off limits for contractors. Kind of defeats the whole purpose of having CI/CD in the first place :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
All good that ends good! And it was a good experience ;)
Yeah, I did kind of make it a thing to deploy everything automatically. I've got ARM templates, Azure CLI scripts, PowerShell, everything, but once I press that button I know I'll get a working environment. Even the SQL database is automatically updated using EF Code First (we'll see how that works out) :D I'm having a progress report with the IT manager next week. I hope to release an entire new environment right before his eyes. This guy is used to old skool server and desktop deployments, the entire team comes in at weekends to make sure it works on Monday morning. So this should make him very happy :D
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
Wow :wtf: That's either some impressive incompetency or your release pipelines are very weird :laugh: I once pushed a chance to production, at the request of a client. I simply pushed the deploy button of that project's release pipeline (because all my changes worked locally and on test and on acceptance). Turned out that the version that was currently on production wasn't a version that was in source control, some manual steps had to be done. I did not have the privileges to enter the production server at all, let alone do those manual steps. The version I released fixed my issue, but broke another part of the application completely, because some unfinished changes were sitting on the master branch since long before I got there. To make things worse, this component had two release pipelines and I used the wrong one. Even though they used VSTS, the version I had just overwritten was gone, so I couldn't put it back either. This was at 07:00, the person who could fix this came in at 07:30 and it all had to be back up before opening time at 08:00. Needless to say, no one was amused, and the release pipelines were from then on off limits for contractors. Kind of defeats the whole purpose of having CI/CD in the first place :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Sander Rossel wrote:
That's either some impressive incompetency or your release pipelines are very weird :laugh:
She'd found a long dormant (about 4 years) script and used that. Not really her fault, it certainly shouldn't have been sitting around where someone could run it, but I still don't understand how she managed to find it and think it would do what she wanted. First time she deployed something to QA she managed to kill that environment with a bug, everything unresponsive about 10 minutes after she deployed. I never did let her get near production.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
-
Sander Rossel wrote:
That's either some impressive incompetency or your release pipelines are very weird :laugh:
She'd found a long dormant (about 4 years) script and used that. Not really her fault, it certainly shouldn't have been sitting around where someone could run it, but I still don't understand how she managed to find it and think it would do what she wanted. First time she deployed something to QA she managed to kill that environment with a bug, everything unresponsive about 10 minutes after she deployed. I never did let her get near production.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
That somehow reminded me of Deedee in Dexter's Lab[^]. Spoiler: The button almost always destroyed one thing or another :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
You have to break a few eggs to make an omelette :D Also, this code is not yet in production and apart from another developer, who works a few hours a week on this project, I'm the only developer. Basically, this was all mine and it was all new. The reason it wasn't consistent in the first place was that I had to make a few things work rather quickly to impress the customer. Now that I'm in I can make it beautiful (and rather now than later) :D
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Phew that makes a lot more sense. Making those changes to a live system would scare the cr*p out of me :laugh:
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
Phew that makes a lot more sense. Making those changes to a live system would scare the cr*p out of me :laugh:
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
I've done it before, in production environments. Now that I'm using CI/CD with Azure and micro services I find that it's indeed a lot easier to drastically change certain parts of the system :D Especially if it's necessary. Just change it, test it, and if anything still happens on production it happens... Of course I don't work on any critical systems, a bug is annoying at worst. Programmers get scared to change anything, then make their changes so that it impacts existing functionality as little as possible. Ultimately, decision making becomes about software rather than business. We want x, but make it y because the software is to hard to change. If the business wants x they should get x even if that means rewriting parts of the application. Although such decisions are also often driven by money. It's difficult, but I always try to own the code and not the other way around :)
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
