Questions tagged [continuous-delivery]

Continuously building, testing and deploying (to non-production environments) applications to prove which instances are fit to be deployed to production.

Continuous delivery is the process of automating as much of the build pipeline as possible to produce deployable applications as quickly as is reasonable. It is the last step before continuous deployment, which also puts the deployable application into production automatically.

This tag is suitable for questions about

  • creating and managing the pipeline used to coordinate the build, test and deploy process
  • environment configuration management
  • wiring build tools to assist with the automated configuration of deployments
  • configuration of continuous integration tools such as Jenkins, Thoughtworks' Go and Atlassian's Bamboo
  • the configuration and deployment of temporary virtual machines and environments specifically for the testing of deployment processes
  • configuration of tools for managing those temporary environments, such as Vagrant
584 questions
16
votes
3 answers

Export existing CodePipeline/CodeBuild projects to Cloudformation

Is there a way to export existing CodePipeline/CodeBuild projects to Cloudformation? I'm in the process of converting our existing CI/CD infrastructure into code so it would be easy to replicate them on other AWS regions. Currently, we've done all…
16
votes
3 answers

What is the difference between continuous integration, continuous delivery and DevOps?

I hear these terms together and wonder what is the difference? How are they related to continuous builds and continuous deployments?
Chaka
  • 1,709
  • 11
  • 33
  • 58
14
votes
2 answers

How to prevent docker images on docker hub from being overwritten?

Is there any way to prevent images being uploaded to docker hub with the same tags as existing images? Our use case is as follows. We deploy to production with a docker-compose file with the tags of images as version numbers. In order to support…
Russell
  • 1,946
  • 1
  • 16
  • 14
12
votes
1 answer

In artifactory repositories, what is the difference between a file integration revision and a folder integration revision?

I'm looking at different repository layouts, and I see a distinction between folder integration revisions and file integration revisions. Are these the same revision number (just placed on a file and/or folder) or are they different things? Here…
DonBecker
  • 2,424
  • 3
  • 25
  • 43
12
votes
2 answers

Github Actions: using workflow_run based on new tags

I have two workflows: CI (for continuous integration) and CD (for continuous delivery). Both are working fine individually. My goal is to run the CD workflow only when: A new tag like v1.1.1 is created on the master branch The CI workflow is…
12
votes
1 answer

How do I include end-to-end tests across microservices into multiple continuous delivery pipelines?

My team develops three microservices. The three work together to provide a business scenario. They communicate with REST and RabbitMQ. Looks like in Toby Clemson's presentation on Microservice Testing. Each microservice has its own continuous…
Florian
  • 4,821
  • 2
  • 19
  • 44
11
votes
2 answers

Use two sources in an AWS-CodePipeline pipeline

I have a specific case which I'm not sure if it's possible with AWS CodePipeline. I'm not able to find any information about such scenario in the documentation and google. So I would like to know if I can set two sources in a pipeline (it could be…
11
votes
2 answers

How to Deploy On-Premises with Visual Studio Online Continuous Delivery

My team uses Visual Studio Online ("VSO") to manage our ALM. We already have a push-button build-process in place to build code from our local Git repo (remotely) and deploy it to a Microsoft Azure Website on Azure. In addition to this we want a…
10
votes
2 answers

How to automatically create a Build Pipeline TAG (not a GIT TAG) after a successful build?

The story so far: When I have a commit that I wish to deploy, I create a GIT TAG to base the build on, eg "RC1" The creation of the GIT TAG automatically triggers the PipeLine Build to start. On successful completion of the PipeLine Build, it…
David
  • 113
  • 1
  • 1
  • 4
10
votes
1 answer

Can I resume a Maven lifecycle from an arbritrary phase?

I would like to convince Maven to "continue where it left off". I first do a mvn package to build the package. At a later time I may want to continue the lifecycle to do the integration test etc. by doing a mvn install. In this case I would prefer…
Rinke
  • 6,095
  • 4
  • 38
  • 55
10
votes
5 answers

Command-line Package Service Fabric Application

Our continuous delivery set-up, until recently, was delivering Service Fabric packages using the following command: msbuild SFApp.sfproj /t:Package This was necessary because the target Package is unavailable at the solution level. I.e. The…
9
votes
2 answers

GitHub action Manual approval process

I know that GitHub Action manual triggers is a very discussed issue, manual approval is a bit less discussed but still present in the community. I have a question for those who use Github actions for CD purposes. As you know Bitbucket, Gitlab, Azure…
guyl
  • 2,158
  • 4
  • 32
  • 58
9
votes
3 answers

Optimize continuous deployment (cancel throu chain-of-responsibility)

Id like to improove continuous delivery. I am using a Tomcat 8 and maven. I use mvn tomcat:redeploy to deploy the webapp. In tomcat documentation I found this part: Deploy A New Application Archive (WAR) Remotely If installation and startup is…
Grim
  • 1,938
  • 10
  • 56
  • 123
9
votes
2 answers

Configure gradle.properties android.enableAapt=false on travis yml file

In my android's gradle.properties I have the following: android.enableAapt2=false My gradle.properties is located in my ~/.gradle/gradle.properties in my local machine. I am wondering how I can add android.enableAapt=false to my yml file. I tried…
ant2009
  • 27,094
  • 154
  • 411
  • 609
9
votes
3 answers

Continuous integration is there any job naming conventions in the jenkins

I would like to know if we have any job naming conventions exist in the continuous integration. we are using Jenkins for Ci , please suggest . naming conventions should be something like this , environment, service, purpose build or deploy etc. any…
user2750116
  • 109
  • 1
  • 1
  • 3
1
2
3
38 39