continuous-delivery

We are using Visual Studio Team Services w/ GIT and VSTS Release Management. We are running a continuous delivery model using pull requests. So each merged pull request triggers a potential release from an according build that ultimately would end up in production. Each release lists the linked work items associated to the according direct pull request. VSTS states: All work items that were included in commits will be displayed in the below list. Comparing current release with %previous release%. However, not all pull requests make it to production, although they have been merged into the

I was using publish to folder option through Visual Studio by right-clicking on the project -> publish -> publish to folder. Result was always ready-to-copy project with applied transformations. I wanted to automate this process using VSTS and have setup build on VSTS. I used next steps: - NuGet restore - Build solution - Publish Build Artifacts to $(build.artifactstagingdirectory) - Windows machine file copy from $(build.artifactstagingdirectory) to remote machine using admin login and password And finally I'm getting zip package on remote machine with complicated folder structure without

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 to add it under global but that didn't work there was no errors but in robolectric it needs to be set if you are using gradle:3.0.0-beta3 . language: android jdk: oraclejdk8 env: global: - ANDROID_TARGET=android-25 - ANDROID_ABI=armeabi-v7a - android.enableAapt2=false android: components: - tools - platform-tools - build-tools-25.0.3 - android-25 -

With Jenkins 2 Pipeline plugin, there's a useful feature allowing a quick overview of the pipeline stages and status of steps, including logging output. However, if you use the "Shell script" (sh) step, there doesn't seem to be a way to label that script with a useful name, so the display merely shows a long list of "Shell Script" (shown in the image below). How can I assign a useful name, or how can I use some other step to accomplish the same effect? Update Feb 2019 : According to gertvdijk's answer below , it is now possible to assign an optional label to the sh step , starting from v2.28,

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 UAT can be carried out. But I wonder what frequency should we deploy on? Everytime a source code changes

I want to deploy an angular 2 app on bluemix. The code is located at github and i want to deploy my app when i push something. So i created a pipeline. First the build pipeline: to build the angular app i need angularCLI, so i want to install it. Unfortunately the default node version is 4.2 but the cli needs at least 6.9. Here is my build-shell-command: #!/bin/bash # The default Node.js version is 0.10.40 # To use Node.js 0.12.7, uncomment the following line: #export PATH=/opt/IBM/node-v0.12/bin:$PATH # To use Node.js 4.2.2, uncomment the following line: export PATH=/opt/IBM/node-v6.9/bin:

Using below Git work flow, for any release, For continuous delivery, my understanding is, two Jenkins pipe lines need to be created, as shown below: 1) Build pipeline that gets triggered on merge of every Feature branch(green) into Develop branch(Purple). Pipeline will push product-x.y-snapshot.jar in Nexus repo. Purpose of this jar is for QA testing 2) Release pipeline that gets triggered on merge of every new Release branch to Master branch. Pipeline will push product-x.y.jar in Nexus repo. This jar goes in production directly. Both pipelines have auto-tests for every functionality. Same