Reference(s):
http://www.sourcegear.com/diffmerge/downloads.php - get the installer version, NOT the dmg version
Reference(s):
http://www.sourcegear.com/diffmerge/downloads.php - get the installer version, NOT the dmg version
/** | |
* Jenkins Job DSL Groovy Script showing how to write & read files to Jenkins Workspace | |
*/ | |
import groovy.json.JsonSlurper | |
import groovy.json.JsonBuilder | |
import groovy.json.JsonOutput | |
import hudson.FilePath | |
import hudson.* | |
def projects = [] |
# checkout | |
git fetch origin refs/meta/config:refs/remotes/origin/meta/config | |
git checkout meta/config | |
#directly: | |
git push origin meta/config:meta/config | |
#via review: | |
git push origin meta/config:refs/for/refs/meta/config |
You may not know that [the most awesome validation engine for PHP][1] out there is [Respect/Validation][2]. If you do, this is tailored for you!
All rules on [Respect/Validation][2] are meant to be used together, composing a more complex validation rule that is closer to the domain of your application than the existing ones, let's try an example:
master
branch is always production-ready, deployable, 100% green test suitegit pull
is configured to automatically rebase)At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.