3 ms·
> Of course having solved one problem (discoverability and organisation of scripts) you now have another one: Jenkins. I called this phase 2. Discovery, docume
by neduma 8y ago
> Of course having solved one problem (discoverability and organisation of scripts) you now have another one: Jenkins.
I called this phase 2. Discovery, documentation and ongoing maintenance going to be the problem. We need to another jenkins to CI/CD the main tooling Jenkins.
My other though is that there is significant market for this kind of back office tooling clean up and ongoing maintenance. If we could come with a process to clean up and package it. we could sell it. I would definitely buy it cause it gives lot of time saving for day to day toils especially in operational space.
- scarface74 8y agoThere are hosted CI solutions that can orchestrate locally installed agents. The two that come to mind are Microsoft’s Visusl Studio Team Services and AWS Code Deploy. For both, you install a local agent that polls the website for commands. You can manually kick off a “deployment” that just downloads and run scripts. Both have agents for Windows and Linux. VSTS is free for private environments for five users and like $5 a month for additional users for one simultaneously running agent - you can have as many agents as you want installed but only one will deploy at a time. Additional simultaneously running agents are cheap or free for each registered MSDN subscriber who is a user. AWS Code Deploy is similar. It’s free for AWS hosted EC2 instances and a 1 cent for each on prem deployment. They both support the concept of deployment groups where you can run the same deployments on a group of machines. Code Deploy uses a simple YML file that tells Code Deploy which scripts/batch files to run. They both support integration with GitHub via webhooks.