jaceklaskowski

Requirements

• no upfront installation/agents on remote/slave machines - ssh should be enough
• application components should use third-party software, e.g. HDFS, Spark's cluster, deployed separately
• configuration templating
• environment requires/asserts, i.e. we need a JVM in a given version before doing deployment
• deployment process run from Jenkins

Solution

JonasGroeger

#!/usr/bin/env bash

# Documentation
# https://docs.gitlab.com/ce/api/projects.html#list-projects

NAMESPACE="YOUR_NAMESPACE"
BASE_PATH="https://gitlab.example.com/"
PROJECT_SEARCH_PARAM=""
PROJECT_SELECTION="select(.namespace.name == \"$NAMESPACE\")"
PROJECT_PROJECTION="{ "path": .path, "git": .ssh_url_to_repo }"

zaenk

Create Linux images on Windows with Packer

Prerequisites:

• Windows 10 Pro
• WLS, Ubuntu 16.04 (a.k.a.: Bash on Ubuntu on Windows)
• Hyper-V
• Packer (1.0.0, added to path)
• Ansible (2.3.0, installed on WSL)
• qemu-img (2.3.0, added to path)

bryanbraun

Example Git Branching Diagram

You can use this diagram as a template to create your own git branching diagrams. Here's how:

1. Create a new diagram with diagrams.net (formerly draw.io)
2. Go to File > Open From > URL
3. Insert this url (it points to the xml data below): https://gist.githubusercontent.com/bryanbraun/8c93e154a93a08794291df1fcdce6918/raw/bf563eb36c3623bb9e7e1faae349c5da802f9fed/template-data.xml
4. Customize as needed for your team.

---

brikis98

	Workspaces	Branches	Terragrunt
Minimize code duplication	■■■■■	□□□□□	■■■■□
See and navigate environments	□□□□□	■■■□□	■■■■■
Different settings in each environment	■■■■■	■■■■□	■■■■■
Different backends for each environment	□□□□□	■■■■□	■■■■■
Easy to manage multiple backends	□□□□□	■■■■□	■■■■■
Different versions in each environment	□□□□□	■■□□□	■■■■■
Share data between modules	■■□□□	■■□□□	■■■■■
Work with multiple modules concurrently	□□□□□	□□□□□	■■■■■