| Jenkins Best Practices | |
| https://en.wikipedia.org/wiki/Continuous_integration<- Read this! | |
| https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Best+Practices | |
| http://www.slideshare.net/andrewbayer/7-habits-of-highly-effective-jenkins-users | |
| Set up version control of job configurations | |
| Keep jobs simple! Don't put a ton of bash in each job. If a job needs to do something complex, put it in a script in GitHub and check it out as needed. | |
| Use templated builders to simplify common tasks | |
| Keep all scripts in version control - avoid running scripts that live on the Jenkins server filesystem | |
| Don't install unnecessary plugins - plugins are often written by third parties and can interact with each other in strange ways | |
| Use LDAP authentication if possible for traceability - avoid anonymous access |
| - info | |
| cat ~/.ssh/id_rsa.pub | ssh forge@yourserverIP "cat >> ~/.ssh/authorized_keys" | |
| ssh 'forge@yourserverIP' | |
| mkdir vips | |
| cd vips | |
| wget -c http://www.vips.ecs.soton.ac.uk/supported/current/vips-7.38.5.tar.gz | |
| tar xzvf vips-7.38.5.tar.gz | |
| cd vips-7.38.5/ |
| let hasBlobConstructor = typeof(Blob) !== 'undefined' && (function () { | |
| try { | |
| return Boolean(new Blob()); | |
| } catch (e) { | |
| return false; | |
| } | |
| }()); | |
| let hasArrayBufferViewSupport = hasBlobConstructor && typeof(Uint8Array) !== 'undefined' && (function () { | |
| try { |
| let hasBlobConstructor = typeof(Blob) !== 'undefined' && (function () { | |
| try { | |
| return Boolean(new Blob()); | |
| } catch (e) { | |
| return false; | |
| } | |
| }()); | |
| let hasArrayBufferViewSupport = hasBlobConstructor && typeof(Uint8Array) !== 'undefined' && (function () { | |
| try { |
| package main | |
| import ( | |
| "os/exec" | |
| ) | |
| func newCmd(imageFile, audioFile, outFile string) *exec.Cmd { | |
| return exec.Command("ffmpeg", | |
| "-r", "1", | |
| "-loop", "1", |
I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.
So below I made a list of leetcode problems that are as close to grokking problems as possible.