stevemcghee

http://tiny.cc/ipashz --- OR --- https://tinyurl.com/cap1-gcp

https://cloud.google.com/docs/compare/aws/  <-- "Google Cloud for AWS Professionals"

https://research.google.com/seedbank/seed/gansynthtwo
https://research.google.com/seedbank/seed/deepdream

https://cloud.google.com/blog/products/gcp/analyzing-nyc-biking-data-with-google-bigquery

Analyzing a financial ML model deployed on Cloud AI Platform with the What-if Tool

micw

#!/bin/bash

set -e

if [ $# -eq 0 ]; then
  echo "USAGE: $0 plugin1 plugin2 ..."
  exit 1
fi

plugin_dir=/var/lib/jenkins/plugins

audionerd

Forwarding ports from a docker container with Vagrant 1.6

Vagrant 1.6 has a really nice feature which allows you to run a docker environment from any machine that can run Vagrant (even a Mac)

Behind the scenes, Vagrant creates a host VM which runs the docker containers.

The "gotcha" is: Vagrant won't automatically forward ports all the way back from the container->vagrant host VM->your mac. You have to do that step manually, by configuring your own host VM for Vagrant to use for hosting docker containers with. That host VM is told what ports to open.

Here's how I set up a local Wordpress development testing container.

rowan-m

$ java -jar jenkins-cli.jar -s http://localhost:9000 install-plugin findbugs
findbugs is neither a valid file, URL, nor a plugin artifact name in the update center
No update center data is retrieved yet from: http://updates.jenkins-ci.org/update-center.json
findbugs looks like a short plugin name. Did you mean 'null'?


# Specifying a full URL works!
$  java -jar jenkins-cli.jar -s http://localhost:9020 install-plugin http://updates.jenkins-ci.org/download/plugins/AdaptivePlugin/0.1/AdaptivePlugin.hpi

# Get the update center ourself