continuous-deployment

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 running: the unit tests in the "test" phase the acceptance tests in the "verify" phase There are two CI jobs

I understand that during development build artifacts are placed in the snapshot repository. When a product needs to go to QA for testing, do teams pull from the snapshot repository? Or do they do a full build, deploy to the release repository, and then give it to QA from there? Also, if my snapshots repository holds all the build artifacts from each build, how is this commonly cleaned up? I could see keeping the last 5 builds from the build server, but not every one. I'm using Artifactory if it helps. Mark O'Connor Opinions differ, here'e my approach: Snapshots are for Dev Typically used for

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 on each commit. Instead, we want it to be incremented automatically whenever a new build is triggered

I am very new to Bitbucket pipelines (Beta) and docker.No previous experience on CI integration I followed this question , But no clear description for beginners I am trying to set up Continuous Integration (CI) in Bitbucket Pipelines for Android Project using docker container I want to use my previous android project with this container Steps I followed Step 1 . Installed Docker Software tools . Successfully installed. Step 2 . Created Virtual Machine Successfully Step 3 . Created container from Kitematic (Beta) Uber/Android-Build-Environment Step 4 . Build Project Successfully using $ eval "

Under certain conditions, I need to abort/end a Chef run with a non-zero status code, that will then propagate back through our deployment chain and eventually to Jenkins resulting in a big, fat red ball. What is the best way to do this? For the readers coming to this question and answer in the future that may not be familiar with Chef, a Chef run "converges" the node, or brings it in line with the policy declared in the recipe(s) it is running. This is also called "convergence." This has two phases, "compile" and "execute." The compile phase is when Chef evaluates ("compiles") the recipes'

I need the latest artifact (for example, a snapshot) from a repository in Artifactory . This artifact needs to be copied to a server (Linux) via a script. What are my options? Something like Wget / SCP ? And how do I get the path of the artifact? I found some solutions which require Artifactory Pro. But I just have Artifactory, not Artifactory Pro. Is it possible at all to download from Artifactory without the UI and not having the Pro-Version? What is the experience? I'm on OpenSUSE 12.1 (x86_64) if that matters. noamt Artifactory has a good extensive REST-API and almost anything that can be

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 celery tasks are finished Stop the upstart jobs Push code to server Run any db migrations Start the