continuous-deployment

问题 Background I have a third-party web service with methods for installing and uninstalling an artifact. Both when installing and uninstalling, you specify an artifact named package-%maven.project.version%.zip. Before installing a new package, I need to uninstall the previously installed package. Solutions I found this solution, but as this is the final step to achieve continuous deployment, I need something automated and not a prompt. Another solution that can be automated by a build step is to

问题 I need to install a couple of cli's every time the workflow runs, it takes up a lot of time in installation and then building and publishing the package. What are some good alternatives to get rid of installation every time? 回答1: To expand on the answer by @joseph, create a Docker image that prepares an environment with the CLI tools that you need and then publish it to DockerHub. Take care not to include any secrets as the image must be public for GitHub Actions to make use of it. In your

问题 I am looking to dive into a project using AppSync. So far I have been able to find plenty of articles and such online giving all the steps as to what buttons to click in order to get a sample project running, but none of them seem to touch on how one deals with it from a local development or in a CI/CD environment. Its probably my "old school" idea of how dev usually works, but I was expecting some way to simulate enough of the environment locally to do development and run unit tests, but I

问题 I am trying to test automated builds in tfs/vs.net 2012. I have set the workpaths in the source control explorer but now I am getting an error: Exception Message: There is no working folder mapping for $/testing/buildtest. (type ItemNotMappedException) 回答1: I had the same problem. Turned out I had forgotten to expand the Items to Build section of the Process tab. To fix you need to: Edit build definition Open Process tab on left Open the 1. Required section open up Items to Build ensure the

问题 ​In our Web API application, Continuous deployment need a following scenario. User will check in code in VS, Code will get automatically build, Code will be Published, Code will be deployed. But If we are using Entity Framework Code First approach, How can we update database without manual commands (Add-Migration/Update Database)and make database up to date with that check-in. 回答1: You can try to run Add-Migration/Update Database commands in the build/deploy process. Assume you are using

问题 So I setup TFS continuous deployment and I'm running into a situation where my build compiles just alright but fails in the deployment phase when communicating with Azure. My log looks like Get Default Azure Cloud Service Publish Profile Set Project to build CSPack Run MSBuild for Project Run Visual Studio Test Runner for Test Sources Publish Output Deploy application to Azure 8/23/2012 7:20:04 AM - Preparing deployment for rcfoapi with SubscriptionID: mysubscriptionidhere.veryverylong

问题 So I setup TFS continuous deployment and I'm running into a situation where my build compiles just alright but fails in the deployment phase when communicating with Azure. My log looks like Get Default Azure Cloud Service Publish Profile Set Project to build CSPack Run MSBuild for Project Run Visual Studio Test Runner for Test Sources Publish Output Deploy application to Azure 8/23/2012 7:20:04 AM - Preparing deployment for rcfoapi with SubscriptionID: mysubscriptionidhere.veryverylong

问题 i am trying to deploy the spring boot app to AWS EC2 instances. i have seen lot of blog and tutorial explained deployment process completely which is understandable. i am struggling how to do continuous deployment or delivery in jenkins which main feature where spring boot app name or jar file name changes that time. my pipeline pipeline { agent any tools{ maven 'localmaven' } stages { stage('Build') { steps { sh 'mvn clean package' } post { success { echo 'Now Archiving...' archiveArtifacts

问题 I'm trying to upload log files created by a 3rd party exe during a deployment and including it in the results of my deployment, on a separate tab if possible. I tried using the publish artifact build tasks but that only works for build not release. I tried logging tasks but ##vso[build.uploadlog]<local file path> seems to be for builds as well since it complains about finding a container for the build. 回答1: Release management does not have a container for build artifacts, that's why you see

问题 UPDATE 2017/02/28 The tags in the release triggers are not source control tags, they are tags that can be generated by your build step. You can tag your builds automatically (see below), or manually during a build, I haven't tried this yet. My assumption about the tags were flawed , which makes this question pretty much invalid. However I am going to try and see if I can find some sort of workaround for my exact scenario, and then I will post it here. Background I am setting up our CI/CD