continuous-deployment

问题 A simplified pipeline will look something like: 1. build 2. unit test 3. deploy to dev 4. integration tests 5. deploy to prod For step #5 I've setup a Jenkins pipeline input command. We won't be deploying to prod on every commit so if we abort all those jobs it will have a big list of grey builds. Is it possible to have a skip option so the build can still be shown as green blue? 回答1: Can't you do something like this, it will be blue/green whatever you choose from input, and you can then run

问题 A simplified pipeline will look something like: 1. build 2. unit test 3. deploy to dev 4. integration tests 5. deploy to prod For step #5 I've setup a Jenkins pipeline input command. We won't be deploying to prod on every commit so if we abort all those jobs it will have a big list of grey builds. Is it possible to have a skip option so the build can still be shown as green blue? 回答1: Can't you do something like this, it will be blue/green whatever you choose from input, and you can then run

问题 Build Errors unable to find jq. Err http://deb.debian.org jessie/main amd64 Packages 404 Not Found Err http://deb.debian.org jessie-updates/main amd64 Packages 404 Not Found Fetched 723 kB in 2s (357 kB/s) W: Failed to fetch http://deb.debian.org/debian/dists/jessie/main/binary-amd64/Packages 404 Not Found W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found E: Some index files failed to download. They have been ignored, or old ones

问题 I am trying to connect bitbucket source repository from azure for continuous integration but I am getting error like "Invalid client_id This integration is misconfigured. Contact the vendor for assistance" in authorization step.is there any idea what's happening? Please help me!! Thanks 回答1: The issue should now be resolved. It was caused by a bad update on the Azure side which caused unwanted side effect. Important : note that at this point, the fix is only in the new portal (portal.azure

问题 I have found a few questions (this one, this one, and this one) related to this question, however none of them clearly answer my question: Do I really need TFS or VSO in order to achieve this? What I have is: A solution with two projects: demo.Web and demo.Api. In Azure I have demo-web.azurewebsites.net (with demo-web-staging.azurewebsites.net) and demo-api.azurewebsites.net (with demo-api-staging.azurewebsites.net). I have the whole solution (with both projects each containing the correct

问题 Continuous integration concept has just been integrated in my team. Assume we have an integration branch named Dev . From it derived 3 branches, one for each specific current project : Project A Project B Project C First, Teamcity is configured on a dedicated server and it goals is : Compiles and launches unit and integration tests from versioned sources from each branch including Dev Then, of course, each project branch (A,B and C) must be tested in a cloned production environment so that

问题 I got a build in VSTS that are triggered on every commit in the repository. Everything works great with one exception. We do not release a new version of the nuget package on every commit. So our nuget push build step fails with http status code 409. I've configured that step so that it can continue anyway. Due to the error the build is just "partially successful". I'm using the a build badge which also states the same (without context). How can I tell VSTS to ignore 409 or just replace the

问题 I have created an Azure Web Site and connected it to Visual Studio Online, and this automatically set up a continuous deployment build (as per this page). Initially this worked for a solution with one project, but now I have added a Web API project as a back end. This is named such that it is the first of the two projects alphabetically, and so now it is the only project that gets built and deployed whenever files are checked in. Which leads to my question: How can I modify the default

问题 I have created an Azure Web Site and connected it to Visual Studio Online, and this automatically set up a continuous deployment build (as per this page). Initially this worked for a solution with one project, but now I have added a Web API project as a back end. This is named such that it is the first of the two projects alphabetically, and so now it is the only project that gets built and deployed whenever files are checked in. Which leads to my question: How can I modify the default

问题 Is it possible to trigger a Hudson/Jenkins build only when a certain string appears in a commit-message? For instance, I want to trigger a build that rolls out my application to the dev environment by writing a commit message like: MYPROJECT-123 Fixed NPE in MyClass.java #deploy:DEV The general idea is described in this great talk on Continuos Deployment but I couldn't find any information on how to do this in Hudson. I would prefer to have this behavior in Hudson itself and not in an