vdice

Our first foray using the Jenkins Pipeline plugin was used in the docker-shell-dev repo.

We're still researching how it might fit in and/or replace our current Jenkins CI job configurations and here are some of the resources we've used to study up:

Brief Pipeline Overview

In-Depth Pipeline Overview

Jenkinsfile Intro

vdice

Keybase proof

I hereby claim:

• I am vdice on github.
• I am vdice (https://keybase.io/vdice) on keybase.
• I have a public key ASDewBkxUwMJiWAOdaPe6jruDNnixs-j15rZ8dsPXKjV0Ao

To claim this, I am signing this object:

vdice

$ az group create --name "${AZURE_RG_NAME}" --location "${AZURE_DC_LOCATION}"
{
  "id": "/subscriptions/7dbf3de9-32a5-4e90-b0ea-e86672956a7f/resourceGroups/vrd-rg",
  "location": "westus",
  "managedBy": null,
  "name": "vrd-rg",
  "properties": {
    "provisioningState": "Succeeded"
  },
  "tags": null

vdice

Agenda

- Brigade 1.0
    - https://github.com/Azure/brigade/projects/1
    - decide on features to bump to 1.1
    
- `brigadecore` GitHub Org
    - CLA bot?
    - Brigade CI for the org
    - anything else keeping us from migrating everything there?

vdice

 $ porter version
porter v0.3.0-ralpha.1+caipirinha-20-g106ccfe (106ccfe)

 $ porter schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "definitions": {
    "azure.install": {
      "additionalProperties": true,

vdice

 $ docker info
Client:
 Debug Mode: false
 Plugins:
  app: Docker Application (Docker Inc., v0.8.0)
  buildx: Build with BuildKit (Docker Inc., v0.3.1-tp-docker)
  ecs: Docker ECS (Docker Inc., v1.0.0-beta.1)

Server:

vdice

Spin App as OCI image diagnostics

Publish and pull app

Navigate to app directory and perform a roundtrip push/pull of the app to/from a registry (here using ttl.sh):

export IMAGE_NAME=$(uuidgen | tr '[:upper:]' '[:lower:]')
spin registry push ttl.sh/${IMAGE_NAME}:1h
spin registry pull ttl.sh/${IMAGE_NAME}:1h