Bring Jenkins UI into the current decade
From a design standpoint:
- Text is too small. A build server is frustrating enough without having to squint at the screen to read.
| Some experiments, which worked but were eventually not used. | |
| See http://www.greenhills.co.uk/2011/06/10/lxc.html | |
| Now, the next big milestone is to get networking working. | |
| In the config, we told lxc-create to use br0 as the link, | |
| and inside the container we have eth0: | |
| root@thunder:/# brctl show br0 | |
| bridge name bridge id STP enabled interfaces | |
| br0 8000.962e6bb72480 no vethP70LNx |
| # How to sign your custom RPM package with GPG key | |
| # Step: 1 | |
| # Generate gpg key pair (public key and private key) | |
| # | |
| # You will be prompted with a series of questions about encryption. | |
| # Simply select the default values presented. You will also be asked | |
| # to create a Real Name, Email Address and Comment (comment optional). | |
| # | |
| # If you get the following response: |
| // From http://www.tannerhelland.com/4435/convert-temperature-rgb-algorithm-code/ | |
| // Start with a temperature, in Kelvin, somewhere between 1000 and 40000. (Other values may work, | |
| // but I can't make any promises about the quality of the algorithm's estimates above 40000 K.) | |
| function colorTemperatureToRGB(kelvin){ | |
| var temp = kelvin / 100; |
| #!/usr/bin/env bash | |
| # ~/.osx — http://mths.be/osx | |
| # Ask for the administrator password upfront | |
| sudo -v | |
| # Keep-alive: update existing `sudo` time stamp until `.osx` has finished | |
| while true; do sudo -n true; sleep 60; kill -0 "$$" || exit; done 2>/dev/null & |
| # This gist is compatible with Ansible 1.x . | |
| # For Ansible 2.x , please check out: | |
| # - https://gist.github.com/dmsimard/cd706de198c85a8255f6 | |
| # - https://github.com/n0ts/ansible-human_log | |
| # This program is free software: you can redistribute it and/or modify | |
| # it under the terms of the GNU General Public License as published by | |
| # the Free Software Foundation, either version 3 of the License, or | |
| # (at your option) any later version. | |
| # |
There are two parts to this:
In general, a CentOS 7 x86_64 box in AWS EC2; in specific, this Packer profile.
| # vim: set ft=python: | |
| # see the README at https://gist.github.com/phiresky/4bfcfbbd05b3c2ed8645 | |
| # source: https://github.com/mpv-player/mpv/issues/2149 | |
| # source: https://github.com/mpv-player/mpv/issues/566 | |
| # source: https://github.com/haasn/gentoo-conf/blob/nanodesu/home/nand/.mpv/filters/mvtools.vpy | |
| import vapoursynth | |
| core = vapoursynth.get_core() |
| # closure - defined by Peter Landin in 1964 | |
| # closure - a function, plus a pointer to that functions scope | |
| # In programming languages, closures (also lexical closures or function closures) are a technique for | |
| # implementing lexically scoped name binding in languages with first-class functions. Duh. | |
| # Operationally, a closure is a record storing a function[a] together with an environment:[1] | |
| # A mapping associating each free variable of the function (variables that are used locally, but defined in an enclosing scope) | |
| # with the value or storage location to which the name was bound when the closure was created. |