continuous-deployment

问题 I have a web service written in Clojure which is continuously delivered. To allow our automated deployment tools to know which version of the codebase has been deployed, the web service should provide a way to query which version it is. The version is declared as part of the project setup in the Leiningen build tool, like this: (defproject my-web-service "1.2-SNAPSHOT" ; ... rest of project.clj ) The codebase is packaged as a JAR file. We developers do not want to increment the version number

问题 The scenario: System running on a server consisting of a Python/Flask web application and background tasks using Celery Both web application and celery workers are run as upstart jobs (Web app behind Nginx) Deployment to production is done with a script that: Stop the upstart jobs Push code to server Run any db migrations Start the upstart jobs How can I enhance the deployment script so it does the following?: Tell the celery worker to stop accepting tasks Wait until any currently running

问题 I'm setting up TeamCity for Continuous Integration and (hopefully) Continuous Deployment. Some of the build steps will involve private files, e.g. .snk files for strong naming .NET assemblies password/token files for publishing artifacts (for example to NuGet or CodePlex) Since these files contain private data I don't want to put them into the (publicly accessible) source control system. I'm setting up http://teamcity.codebetter.com for AutoFixture so I don't have physical access to the

问题 What's the difference between these three terms? My university provides the following definitions: Continuous Integration basically just means that the developer's working copies are synchronized with a shared mainline several times a day. Continuous Delivery is described as the logical evolution of continuous integration: Always be able to put a product into production! Continuous Deployment is described as the logical next step after continuous delivery: Automatically deploy the product

问题 We have a Jenkins/Maven/Wildfly/Artifactory job that builds and deploys EAR file on wildfly and then in Artifactory . I'm trying to create another Jenkins manual job that retrieves a specific build from Artifactory and deploys to Wildfly . How do I tell Jenkins to retrieve artifacts from Artifactory ? I'm using ' Copy artifacts from another project '. Is there a similar plugin that will help me to download artifacts from Artifactory ? Thanks! 回答1: The artifactory plugin for Jenkins has the

问题 How to spin up a local version of Spinnaker? This has been answered and addressed in detail here. https://github.com/spinnaker/spinnaker/issues/1729 回答1: Ok, so I got it to work, but not without you valuable help! @lwander So I'll leave the steps here for posterity. Each line is a separate command in the command line, I've installed this on a virtual machine with a freshly installed Ubuntu 14.04 copy with nothing else than SSH. Then SSH as root, You will need to configure sshd on your console

问题 I am trying to setup the Continuous deployment process for a Tomcat based java app using Github for source code hosting, TravisCI for building the WAR file, running the unit tests and then Heroku to deploy the packaged WAR file. I tried following the tutorial from https://devcenter.heroku.com/articles/deploying-war-files-to-heroku-from-travis-ci#creating-a-java-web-application I am getting an error while running the below step from the above tutorial: mvn clean heroku:deploy-war Command outpt

问题 I have a single solution full of projects that are to be shared amongst my organization as general nuget packages. The solution is encompassed by one git repository and we have TeamCity running our builds for us, although we are not overly advanced in that we manually kick off the Teamcity builds when we are ready to generate/publish a new Nuget package for a given project in the solution, every project has its own TeamCity build configuration. When built, the projects generate nuget packages

问题 I am a Newbie using gitlab-CI and my english is not very good. I want to use gitlab ci to deploy one project to i686, x86_64 linux machine respectively. So I can generate an update package on different types linux centos. Now I use gitlab-server(192.168.1.240), gitlab runner (192.168.1.184) production server1(192.168.1.162) production server2(192.168.1.163); gitlab-server(240) --> runner(184) ^ ^ product_s1(162) product_s2(163) /etc/gitlab-runner/config.toml: concurrent = 1 [[runners]] url =

问题 Imagine a Java project built using Maven for which I have: some fast-running unit tests that: developers should run before committing my CI server (Hudson, FWIW) should run upon detecting a new commit, giving almost instant feedback in case of failures some slow-running automated acceptance tests that: developers can run if they choose, e.g. to reproduce and fix failures my CI server should run after successfully running the unit tests This seems like a typical scenario. Currently, I'm