Bootstrap the repository (#1)

Author: fwilhe

.github/main.workflow

@@ -0,0 +1,13 @@
+workflow "Lint all Dockerfiles" {
+  on = "push"
+  resolves = ["Haskell Dockerfile Linter"]
+}
+
+action "Haskell Dockerfile Linter" {
+  uses = "docker://cdssnc/docker-lint-github-action"
+  # https://github.com/hadolint/hadolint/wiki/DL3008
+  # https://github.com/hadolint/hadolint/wiki/DL3013
+  # https://github.com/hadolint/hadolint/wiki/DL3016
+  # https://github.com/hadolint/hadolint/wiki/DL3018
+  args = "--ignore DL3008 --ignore DL3013 --ignore DL3016 --ignore DL3018"
+}

.gitignore

@@ -0,0 +1,4 @@
+.idea
+.vscode
+*.DS_Store
+test-project

.travis.yml

@@ -0,0 +1,8 @@
+branches:
+  only:
+  - master
+  - /^it\/.*$/
+language: minimal
+services:
+- docker
+script: chmod +x runTests.sh && ./runTests.sh

CONTRIBUTING.md

@@ -0,0 +1,35 @@
+# Guidance on how to contribute
+
+There are two primary ways to help:
+* using the issue tracker, and
+* changing the code-base.
+
+## Using the issue tracker
+
+Use the issue tracker to suggest feature requests, report bugs, and ask
+questions. This is also a great way to connect with the developers of the
+project as well as others who are interested in this solution.
+
+Use the issue tracker to find ways to contribute. Find a bug or a feature,
+mention in the issue that you will take on that effort, then follow the
+guidance below.
+
+## Changing the code-base
+
+Generally speaking, you should fork this repository, make changes in your own
+fork, and then submit a pull-request. All new code should have been thoroughly
+tested end-to-end in order to validate implemented features and the presence or
+lack of defects. All new scripts and docker files _must_ come with automated (unit)
+tests.
+
+The contract of functionality exposed by docker files functionality needs
+to be documented, so it can be properly used. Implementation of a functionality
+and its documentation shall happen within the same commit(s).
+
+#### Consistent USER Instruction in the Dockerfile
+
+Set the user name (or UID) and the user group (or GID) to UID 1000 and GID 1000 to be consistent ith the Jenkins image.
+
+````
+USER 1000:1000
+````

Dockerfile

@@ -0,0 +1,28 @@
+FROM buildpack-deps:stretch-curl
+
+ENV VERSION 0.1
+
+# https://github.com/hadolint/hadolint/wiki/DL4006
+SHELL ["/bin/bash", "-o", "pipefail", "-c"]
+
+# ps needs to be available to be able to be used in docker.inside, see https://issues.jenkins-ci.org/browse/JENKINS-40101
+RUN apt-get update && \
+    apt-get install -y --no-install-recommends procps && \
+    rm -rf /var/lib/apt/lists/*
+
+# add group & user
+RUN addgroup -gid 1000 piper && \
+    useradd piper --uid 1000 --gid 1000 --shell /bin/bash --create-home && \
+    curl --location --silent "https://cli.run.pivotal.io/stable?release=linux64-binary&source=github" | tar -zx -C /usr/local/bin && \
+    cf --version
+
+USER piper
+WORKDIR /home/piper
+
+ARG MTA_PLUGIN_VERSION=2.1.0
+ARG MTA_PLUGIN_URL=https://github.com/cloudfoundry-incubator/multiapps-cli-plugin/releases/download/v${MTA_PLUGIN_VERSION}/mta_plugin_linux_amd64
+
+RUN cf add-plugin-repo CF-Community https://plugins.cloudfoundry.org && \
+    cf install-plugin blue-green-deploy -f -r CF-Community && \
+    cf install-plugin ${MTA_PLUGIN_URL} -f && \
+    cf plugins

NOTICE

@@ -0,0 +1,2 @@
+Copyright (c) 2018 SAP SE or an SAP affiliate company. All rights reserved.
+

README.md

@@ -0,0 +1,71 @@
+## CloudFoundry CLI Image
+
+The CX Server is a collection of [_Dockerfiles_](https://docs.docker.com/engine/reference/builder/) for images that can be used in _Continuous Delivery_ (CD) pipelines for SAP development projects.
+The images are optimized for use with project ["Piper"](https://github.com/SAP/jenkins-library) on [Jenkins](https://jenkins.io/).
+Docker containers simplify your CD tool setup, encapsulating tools and environments that are required to execute pipeline steps.
+
+If you want to learn how to use project "Piper" please have a look at [the documentation](https://github.com/SAP/jenkins-library/blob/master/README.md).
+Introductory material and a lot of SAP scenarios not covered by project "Piper" are described in our [Continuous Integration Best Practices](https://developers.sap.com/tutorials/ci-best-practices-intro.html).
+
+This repository contains Dockerfiles that are designed to run project "Piper" pipelines.
+Nevertheless, they can also be used flexibly in any custom environment and automation process.
+
+## About this repository
+
+Dockerfile for an image with the CloudFoundry CLI and plugins for blue-green deployment and MTA.
+This image is intended to be used in Jenkins pipelines.
+
+## Download
+
+This image is published to Docker Hub and can be pulled via the command
+
+```
+docker pull ppiper/cf-cli
+```
+
+## Build
+
+To build this image locally, open a terminal in the directory of the Dockerfile an run
+
+```
+docker build -t ppiper/cf-cli .
+```
+
+## Usage
+
+Recommended usage of this image is via [`cloudFoundryDeploy`](https://sap.github.io/jenkins-library/steps/cloudFoundryDeploy/) pipeline step.
+
+For using the `cf` tool via this image, it can be invoked like in this command
+
+```
+docker run ppiper/cf-cli cf
+```
+
+## Testing
+
+### Running as a Service
+
+See `.travis.yml` file for configuration.
+
+Configure the following variables (secrets)
+
+* `CX_INFRA_IT_CF_USERNAME` (user name for deployment to SAP Cloud Platform)
+* `CX_INFRA_IT_CF_PASSWORD` (password for deployment to SAP Cloud Platform)
+
+### Running locally
+
+Docker is required, and at least 4 GB of memory assigned to Docker.
+
+```bash
+export CX_INFRA_IT_CF_USERNAME="myusername"
+export CX_INFRA_IT_CF_PASSWORD="mypassword"
+./runTests.sh
+```
+
+## License
+
+Copyright (c) 2018 SAP SE or an SAP affiliate company. All rights reserved.
+This file is licensed under the Apache Software License, v. 2 except as noted
+otherwise in the [LICENSE file](https://github.com/SAP/devops-docker-images/blob/master/LICENSE).
+
+Please note that Docker images can contain other software which may be licensed under different licenses. This License file is also included in the Docker image. For any usage of built Docker images please make sure to check the licenses of the artifacts contained in the images.

runTests.sh

@@ -0,0 +1,36 @@
+#!/bin/bash -e
+
+# Sanity check
+if [ -z "$CX_INFRA_IT_CF_USERNAME" ]; then
+    echo "Failure: Variable CX_INFRA_IT_CF_USERNAME is unset"
+    exit 1
+fi
+
+if [ -z "$CX_INFRA_IT_CF_PASSWORD" ]; then
+    echo "Failure: Variable CX_INFRA_IT_CF_PASSWORD is unset"
+    exit 1
+fi
+
+set -x
+
+# Start a local registry, to which we push the images built in this test, and from which they will be consumed in the test
+docker run -d -p 5000:5000 --restart always --name registry registry:2 || true
+
+docker build -t localhost:5000/ppiper/cf-cli:latest .
+docker tag localhost:5000/ppiper/cf-cli:latest ppiper/cf-cli:latest
+docker push localhost:5000/ppiper/cf-cli:latest
+
+git clone https://github.com/piper-validation/cloud-s4-sdk-book.git -b validate-cf-cli test-project
+pushd test-project
+
+docker run -v //var/run/docker.sock:/var/run/docker.sock -v $(pwd):/workspace -v /tmp \
+ -e CX_INFRA_IT_CF_PASSWORD -e CX_INFRA_IT_CF_USERNAME -e BRANCH_NAME=master \
+ -e CASC_JENKINS_CONFIG=/workspace/jenkins.yml -e HOST=$(hostname) \
+ ppiper/jenkinsfile-runner
+
+popd
+
+function cleanup {
+  rm -rf test-project
+}
+trap cleanup EXIT