![]() ![]() Again, we opted to script both the Chocolatey install step, and the configuration step. Regardless of which path you take, there’s a final step of configuring options for your tentacle, including the secure key it uses to handshake with your server. Knowing that we would likely require new agents in the future, we created a script which uses Chocolatey to install these extra pre-requisites.įor the Octopus Tentacles, you can either download and run the standard Tentacle installer on each target machine, or alternatively use the Chocolatey tentacle package. Yours will vary according to the dependencies of the projects you’re building, but Git and Visual Studio were two dependencies that we installed which most people will probably also need. On the build agents there are some pre-requisites that we installed on each agent. Install Octopus deployment server + tentacles as required on target servers. ![]() Install Team City Build Server + minimum of one build agent.There are plenty of resources available about how to install these products, so I’m not going to dwell on these: There are a lot of links in here to other articles with more detailed information, but there weren’t many articles which pulled together everything into one place, which is what I wanted to cover here. If anyone’s going through an installation and configuration of these tools, here’s the steps we carried out, and some lessons learned along the way. The harder part came later: how do we configure those tools in the best way to support our development workflow? As we configured the tooling, this was also an opportunity to look again at our processes and identify ways in which the new tools allow us to improve quality. In some senses coming to that decision was the easy part. We went through a 2-month period of thinking deeply about our requirements and trialling different software in order to land at the tools which we felt were the correct long-term fit: Git, TeamCity and Octopus Deploy. Around 18 months ago, we went through a significant shift in deployment pipeline tooling within our agency.Īfter 7 years of using an on-premise Team Foundation Server (TFS) instance for version control and builds, integrating with MSDeploy for deployment, I realised we needed to be doing more within our build processes, and there were better tools available for our needs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |