continuous-deployment

问题 I want to change release names like V.1.0.00 for manual release in Continuous Delivery of Azure DevOps but i can't able to delete or change the naming without this $(rev:r) , how can I use a custom name? Default Name: Release- $(rev:r) Required Name: V.1.0.0 回答1: You can't. release name must be a unique name, therefore Azure DevOps requires you to put $(rev:r) in the name, because it's adding a incremental number for each release. Another option is to use $(Build.BuildNumber) or $(Release

问题 Is it possible for GitHub to trigger a new test deployment when a pull request is submitted? I'd like for it to create a new folder on the server (Azure preferred) so that a test URL (e.g. http://testserver.com/PR602/) is generated that we can refer to in the pull request. This would allow anyone to test a pull request without having to clone the repo, check out the branch, and build it locally. In my initial research I found that Travis CI can deploy all branches, but I'm not clear how this

问题 I want to enable continuous deployment on Azure DevOps for a Node.js app, by creating a Release pipeline. How do I make this happen? 回答1: See my newer answer for a better solution. I spent several hours trying to figure out how to get CI/CD working for a Node.js app, on Azure DevOps, because there is very little documentation that I could reference. I finally got it working, so I hope these steps will help you. Note: the UI may change over time. This is written in October of 2018.

问题 What I am trying to do is to enable Continuous delivery from GitLab to my compute engine on Google Cloude. I have Ubuntu 16.04 TSL running over there. I did install all components needed to run my project like: Swift, vapor, nginx. I have manage to install Gitlab runner as well and created a runner whcihc is accessible from my gitlab repo. Everytime I do push on master the runner triggers. What happen is a failure due to: could not create leading directories of '/home/gitlab-runner/builds

问题 I'm investigating Puppet as our future deployment and provisioning tool in our shop, but now I'm stuck at how to make a clever Continuous Integration/Delivery tool chain with deployment through Puppet. In any of our environments (dev, test, qa, demo, prod) we have a range of components. We need to be able to deploy each component separately and possibly even concurrently. I'd like a way to initiate (through script) a deploy of a single component package (=Puppet module) and gather the output

问题 I have a project in VS Team Services git repository with the following structure (simplified): / scripts (for typescript) styles (for sass) wwwroot (public directory with images, css, js...) ... All typescript and sass files are built with gulp into appropriate directory inside wwwroot. What I'd like to do but can't find how, push only wwwroot directory to Azure Website instead of entire project. If not possible, what are alternatives? 回答1: There are two ways you could do this The Easier Way

问题 I have created an ARM template and am using it to: Create a resource group. Create and Application Service. Deploy code from GitHub (repoUrl) to said Application Service. All works wonderfully when I place my project inside GitHub but we are using VSTS Git to hold our code. I know I can create a VSTS jobs that will do this for me and this is the track we will get to again however we need to be able to run these ARM templates from our developer machines, running direct from our Visual Studios

问题 Imagine I have a vanilla continuous delivery scenario with a Java webapp. This scenario has: - one build server running cruisecontrol - one web server running Tomcat with tomcat manager running One of the Ant build targets running on the build server builds a war file and then uses catalina-ant to remotely deploy the web server using the Tomcat manager. To be truly useful - we need to be able to roll back the deployment. Given this vanilla setup, what extra pieces of the puzzle do I need to

问题 We practice continuous deployment with TFS (2008) and are looking for a nice way to handle IIS settings changes. MSDeploy seems like it should be the way to handle this, but after much reading and searching, I haven't found a good answer. The problem with MSDeploy, as I see it, is that you need to create a deployment package using an existing IIS website. I would like to be able to have the appropriate IIS configuration for the website in source control and have the build create the package.

问题 We practice continuous deployment with TFS (2008) and are looking for a nice way to handle IIS settings changes. MSDeploy seems like it should be the way to handle this, but after much reading and searching, I haven't found a good answer. The problem with MSDeploy, as I see it, is that you need to create a deployment package using an existing IIS website. I would like to be able to have the appropriate IIS configuration for the website in source control and have the build create the package.