Martin Jackson actionjack

README

Services declared as oneshot are expected to take some action and exit immediatelly (thus, they are not really services, no running processes remain). A common pattern for these type of service is to be defined by a setup and a teardown action.

Let's create a example foo service that when started creates a file, and when stopped it deletes it.

Define setup/teardown actions

Create executable file /opt/foo/setup-foo.sh:

Paper cuts

This is a log of things that have hurt us in the current environment that while not necessarily being technical debt, could possibly be things for us to discuss and possibly fix in the future.

If you're writing bare-bones javascript for the browser, creating Chrome Apps and Extensions, or using remote coding apps like cloud9, Koding, or Nitrous, you may not need to install Ubuntu. Some tutorials can be done entirely within the browser. The tradeoff is that you won't have a full-featured command line, and you may hit a point where you can't install something that you need.

To start coding within Chrome OS, install Text or Caret as a text editor. (Text stores files in Google Docs and Caret stores the files locally on your machine, which may help you choose.) After that, you're good to go, since Chromebooks come with a browser installed.

Optio

Concourse Tutorial - Example Tasks

This gist includes some https://concourse.ci job tasks

hello-world.yml - displays "hello world"
display-other-task.yml - uses this task as a resource itself and displays the hello-world.yml YAML; assumes that the gist is available in the concourse pipeline as resource-gist.
display-other-task-renamed-resource-input.yml - is like the task above, but assumes the resource is now named gist rather than resource-gist

AB benchmark and plotting

Small script to execute a apache benchmark ab from one host to other.

The scripts are designed for benchmark tsuru routers, and compare between hipache+nginx vs. vulcand.

It will gather metrics of request time and CPU in the target so they can be later plot using gnuplot.

S3 as Yum repo

There are two parts to this:

Managing access to non-public S3 resources.
Building RPM repositories in an automated, deterministic way that Yum can use.

Environment

In general, a CentOS 7 x86_64 box in AWS EC2; in specific, this Packer profile.

	import java.util.ArrayList;
	import hudson.model.*;

	def q = Jenkins.instance.queue
	for (queued in Jenkins.instance.queue.items) {
	q.cancel(queued.task)
	}

	for (job in Jenkins.instance.items) {
	stopJobs(job)

	'Update or create a stack given a name and template + params'
	from __future__ import division, print_function, unicode_literals

	from datetime import datetime
	import logging
	import json
	import sys

	import boto3
	import botocore

	#!/bin/bash

	profile={replace}
	s3bucket={replace}
	folder={specify}
	queueprefix={replace}

	purge-sqs-queue() {
	if [ -z "$1" ]; then
	echo "need to pass queue name prefix"

	node {
	echo 'Results included as an inline comment exactly how they are returned as of Jenkins 2.121, with $BUILD_NUMBER = 1'
	echo 'No quotes, pipeline command in single quotes'
	sh 'echo $BUILD_NUMBER' // 1
	echo 'Double quotes are silently dropped'
	sh 'echo "$BUILD_NUMBER"' // 1
	echo 'Even escaped with a single backslash they are dropped'
	sh 'echo \"$BUILD_NUMBER\"' // 1
	echo 'Using two backslashes, the quotes are preserved'
	sh 'echo \\"$BUILD_NUMBER\\"' // "1"