Configuration and Release Management with NPloy

Transcript

1. Configuration and Release Management with NPloy Continuous Delivery in Windows environments
2. Continuous Delivery reduce the cost, time, and risk of delivering incremental changes to users
3. Individuals and interactions over processes and tools • Still right but it is almost impossible to have continuous feedback without automation and automation is processes and tools! • So DevOps over Automation • But the following slides are about automation – that should support DevOps
4. Continuous Delivery says: • Put everything under source control • Incl. configuration – for application and infrastructure • Only Build Your Binaries Once • Use technologies that fits well in your OS • E.g. package technologies • Linux has a lot of cool stuff but what to do on Windows
5. We need • Tools and technology that fits well on Windows • Packageformat that supports versioning and easy mangement • NuGet works really well for libraries and tools and are getting tracktion for applications (Chocolatey and OctopusDeploy) • Configuration that fits well into a source control system of your choice • Some kinde of text file should work • A scripting environment for automation • Many of us developers doesn’t really like Powershell but we should get used to it – it’s the best option on Windows and it is build in.
6. NPloy Puts it all together 1. Package your system as NuGet packages • Including application management powershell scripts in the App_Install-folder 2. Define your system configuration as nodes, roles and environment configuration in text files. • See example here https://github.com/jasperdk/NPloy/tree/master/samples/.nploy 3. Run ‘nploy installnode localhost’
7. How is it different • Others are using the NuGet package format but NPloy is the only solution if you want all configuration in source control
8. Comming features • Update commands • NuGet feed with promotion/tagging features • Support of other configuration file formats • Support for Infrastructure management through PowerShell Desired State Configuration • Web administration • Change configuration • Deployment dashboard • Deploy agents (if you dont want to use your build server agents as deploy agents)
9. NPloy • https://github.com/jasperdk/NPloy