Skip to content

Instantly share code, notes, and snippets.

Paolo D'Incau pdincau

  • XPeppers
  • Trento
Block or report user

Report or block pdincau

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
View gist:ce754a4290d048799947
cowboy static files:
in priv
index referenzia js come <script src="/static/js/controllers.js"></script>
pdincau / gist:ea60d1fc7d900a61ae0c
Created Feb 17, 2015
separatore string calculator
View gist:ea60d1fc7d900a61ae0c
Estrarre separatore string calculator
Pattern pattern = Pattern.compile("//(.+?)\n(.+)");
Matcher matcher = pattern.matcher(input);
if (matcher.matches()) {
View Jenkins top ten lowest
grep -h "<testcase" `find . -iname "TEST-*.xml"` | sed 's/<testcase name="\(.*\)" classname="\(.*\)" time="\(.*\)".*/\3\t\2.\1/' | sort -rn | head
View CI

Continuous Integration - Know your opportunities

Continuous Integration in a nutshell

Continuous Integration (CI) is an important practice every team should adopt in order to detect defects and errors early and solve integration problems easily. Roughly speaking we may say that CI is a practice that allows the growth of solid software by giving greater confidence to the developers and better products to the final customers.

The concept behind CI is fairly simple: the codebase is owned by several developers that continuously integrate their changes to a common version control system. For each integration the system runs a predefined set of tasks automatically; these tasks may vary from running all the tests to building all the components.

You can’t perform that action at this time.