kevinawoo

---
swagger: "2.0"
info:
  title: "Spinnaker API"
  contact: {}
host: "localhost"
basePath: "/"
tags:
- name: "v-2-pipeline-templates-controller"
  description: "V 2 Pipeline Templates Controller"

kevinawoo

inline code: 👍 should see thumbsup

codeblock:

👍 thumbs up
👯‍♀️ women dancers 

kevinawoo

# At a minimum, all we care about is when it's stable/succesful so we know if a stage should continue
# if one of stable.* is TRUE, then it's stable!
stability.spinnaker.io/stable/handler: Field
stability.spinnaker.io/stable/field: ".status.status=successful"
stability.spinnaker.io/stable.1/handler: Field
stability.spinnaker.io/stable.1/field: ".status.status=ok"
stability.spinnaker.io/stable.2/handler: Field
stability.spinnaker.io/stable.2/field: ".status.status=yay"

  # another way of handling it maybe to just do comma separated conditions (same for failed status)

kevinawoo

# At a minimum, all we care about is when it's stable/succesful so we know if a stage should continue
# if one of stable.* is TRUE, then it's stable!
stability.spinnaker.io/stable/handler: Field
stability.spinnaker.io/stable/field: ".status.status=successful"
stability.spinnaker.io/stable.1/handler: Field
stability.spinnaker.io/stable.1/field: ".status.status=ok"
stability.spinnaker.io/stable.2/handler: Field
stability.spinnaker.io/stable.2/field: ".status.status=yay"

  # another way of handling it maybe to just do comma separated conditions (same for failed status)

kevinawoo

# Create a directory for the Spinnaker Operator YML files downloaded from https://github.com/armory-io/spinnaker-operator/releases/download/v0.1.0/manifests.tgz
mkdir spinnaker-operator
cd spinnaker-operator
VERSION=v0.2.0 && curl -L https://github.com/armory-io/spinnaker-operator/releases/download/$VERSION/manifests.tgz | tar -xvf -




# Apply the Spinnaker Operator Custom Resource (CRD)
# A Kubernetes custom resource is an extension of the Kubernetes API which represents a customization of a particular Kubernetes installation.

kevinawoo

function sync() {

  var id="XXXXXXXXXX"; // CHANGE - id of the secondary calendar to pull events from

  var today=new Date();
  var enddate=new Date();
  enddate.setDate(today.getDate()+7); // how many days in advance to monitor and block off time
  
  var secondaryCal=CalendarApp.getCalendarById(id);
  var secondaryEvents=secondaryCal.getEvents(today,enddate);

kevinawoo

schema: "1"
id: myFirstBareBones
protect: true
metadata:
  name: Bare Bone Pippeline Template
  description: A generic application bake & tag pipeline.
  owner: example@example.com
  scopes: [global]

variables:

kevinawoo

#!/bin/bash

set -e

root=$PWD

# This loads NVM
[[ -s $HOME/.nvm/nvm.sh ]] && . $HOME/.nvm/nvm.sh
[[ -s /usr/local/opt/nvm/nvm.sh ]] && . "/usr/local/opt/nvm/nvm.sh"

kevinawoo

{
  "restartable": "rs",
  "colours": true,
  "execMap": {
    "py": "python",
    "rb": "ruby",
    "sh": "bash"
  },
  "watch": [
    "**/*"

kevinawoo

Git Commit Messages

• Messages answers the following sentence:

  Apply this commit to _______________

• Use the present tense ("Add feature" not "Added feature")
• Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
• Limit the first line to 72 characters or less
• Reference issues and pull requests liberally
• When only changing documentation, include [ci skip] in the commit description
• Consider starting the commit message with an applicable emoji: