continuous-deployment

How to specify branch in .gitlab-ci.yml for a submodule (different repo) in gitlab-ci? You don't. You specify it in the .gitmodules file of the project you are building. [submodule "MyRepo"] path = MyRepo url = https://github.com/vendor/MyRepo.git branch = master Along with @stefan's answer to this question. You also have to tell Git to only look at the specified branch for the latest commit. git submodule update seems to always fetch the latest commit regardless of the branch. Doing git submodule update --remote seems to force git to focus on the branch you specify in the .gitmodules file. So

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? MaTePe Can't you do something like this, it will be blue/green whatever you choose from input, and you can then run the deployment depending on it too? def deployToProduction = true try{ input 'Deploy to Production'

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 used instead. $ apt-get install jq Reading package lists... Building dependency tree... Reading state

We practice continuous deployment with TFS (2008) and are looking for a nice way to handle IIS settings changes. MSDeploy seems like it should be the way to handle this, but after much reading and searching, I haven't found a good answer. The problem with MSDeploy, as I see it, is that you need to create a deployment package using an existing IIS website. I would like to be able to have the appropriate IIS configuration for the website in source control and have the build create the package. The only way I can see to do this is to hand craft the archive.xml file. Is my thinking correct or is

I'm a big fan of continuous integration / deployment and we build our Android apps with Jenkins and deploy every build from specific branches (mostly git flow 's develop branch) to our testers via HockeyApp . What I want to achieve is that every new (tagged) commit to master will endup in the Play Store. So I don't have to manually upload APKs via the Play Store developer console . I've already searched for an API. But Google doesn't provide any and the two unofficial projects I found ( Android Market API and Play PHP API ) only support downloading metrics like the download count of your app.

Given I started working with Chef using the Chef Server Management Console and I now want to start using a files and upload them via knife. Is there a way to retrive roles and environments that are stored on the ChefServer via knife, so I can them into git? You can use the knife environment list and knife environment show commands to download environments and replace "environment" with "role" to do the same for roles. mkdir environments for env in `knife environment list`; do knife environment show $env --format=json > environments/$env.json done You can then check these JSON files into git