eugenestarchenko

# I wrote this program after several attempts to work with jenkinsapi and python-jenkins packages. 
# This script got the job done without any issues.
import requests
import sys

jenkins_host = "localhost:8080"
jenkins_user = "admin"
jenkins_api = "z01c688ffc46511f7e8dd95014ggaf05"

# Check command line args

eugenestarchenko

So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear!

Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy.

* Off the top of my head *

1. Fork their repo on Github
2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it

    git remote add my-fork [email protected]

eugenestarchenko

#!/usr/bin/php
<?php
/**
 * ELB Internal Route53 Updater
 * @author Cyril Aknine https://github.com/darylounet
 */

$vpcId = 'your-vpc-id';
$elbNetworkDescription = 'Your ELB network interface description (generated like "ELB your-elb-name")';
$route53InternalHostedZoneId = 'Your Route53 Internal hosted zone ID';

eugenestarchenko

Tar

Compress (backup) files and directories

Common arguments

-c create an archive

-f file.tar filename of archive

-v verbose

eugenestarchenko

#!/bin/bash

# error handling
 error_handler() {
	   echo "Error occurred in script at line: ${1}"
	     echo "Line exited with status: ${2}"
     }

     trap 'error_handler ${LINENO} $?' ERR

eugenestarchenko

#!/bin/bash
# MKDIR /backup
# git clone this script there
# SETUP CRONTAB:
# crontab -e
# PATH=/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/aws/bin
# 0 0 * * * cd /backup && ./jenkins-backup-s3.sh

set -ex

eugenestarchenko

Deploy updates to aws ecs services based on github commits. Posts deploy notifications to slack.

Assumptions:

• Task definitions map 1:1 with services, and they have the same name.
• Code is stored on github
• You want to deploy the latest commit in a branch
• Docker images are tagged with commit SHA
• Docker images are stored on AWS ECR

eugenestarchenko

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

eugenestarchenko

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AllowAllUsersToListAccounts",
            "Effect": "Allow",
            "Action": [
                "iam:ListAccountAliases",
                "iam:ListUsers",
                "iam:GetAccountPasswordPolicy",

eugenestarchenko

How to setup AWS lambda function to talk to the internet and VPC

I'm going to walk you through the steps for setting up a AWS Lambda to talk to the internet and a VPC. Let's dive in.

So it might be really unintuitive at first but lambda functions have three states.

1. No VPC, where it can talk openly to the web, but can't talk to any of your AWS services.
2. VPC, the default setting where the lambda function can talk to your AWS services but can't talk to the web.
3. VPC with NAT, The best of both worlds, AWS services and web.