VirtualTam's bookmarks
114 bookmarks found
-
Code review memes
2015-06-12 Why Jenkins don't love me? http://m.memegen.com/oqruus.jpg Much stable. Success. https://raw.githubusercontent.com/ahmednuaman/meme-says-jenkins/master/assets/img/build-blue.jpg A code review fail http://m.memegen.com/oojxsc.jpg No idea https://regmedia.co.uk/2015/01/28/dog_meme_.jpg We will invade http://www.mememaker.net/static/images/memes/3675436.jpg Your own code http://devopsreactions.tumblr.com/post/120682285491/reading-your-own-code I have done my code reviews http://cdn.meme.am/instances/500x/58587913.jpg Too complex? https://i.imgur.com/nXrYiub.jpg Ship it https://qph.ec.quoracdn.net/main-qimg-d656a4e5537062cd665afe7c9ff46c53
-
SonarQube™
2015-05-18 SonarQube is an open platform to manage code quality.
https://github.com/SonarSource/sonarqube http://www.sonarsource.com/products/features/continuous-inspection/
-
Original script @ https://gist.github.com/yuvipanda/5174162
-
Obey the testing goat...
2015-05-10 - Test first! Test first!
-
Martin Fowler
2015-04-05 "Any fool can write code that a computer can understand. Good programmers write code that humans can understand."
see http://martinfowler.com/articles/continuousIntegration.html ;-)
-
Flow: a static Javascript typechecker
2015-02-11 -
Starting and Accessing Jenkins
2015-01-09 To increase the memory allocated and available:
1# /etc/default/jenkins 2JAVA_ARGS='Xms4G -Xmx16G -Djava.awt.headless=true'
See also
- Jenkins performance hints: http://soldering-iron.blogspot.com/2014/01/jenkins-performance-hints.html
- Java commandline options: http://docs.oracle.com/javase/7/docs/technotes/tools/windows/java.html
-
Cobertura - Jenkins Plugin
2015-01-04 DIsplay code coverage stats
-
nose: python testing helper
2015-01-04 Includes support for Coverage, Xunit and other cool stuff ;-) Oh, and there is parallel testing, too \o/
nosetests --with-coverage --cover-erase --cover-tests --cover-html --cover-html-dir=htmlcov --with-xunit --xunit-file=unit.xml
via http://www.alexconrad.org/2011/10/jenkins-and-python.html
-
Continuous integration in Python
2014-11-27 http://ilovesymposia.com/2014/10/01/continuous-integration-0-automated-tests-with-pytest/ http://ilovesymposia.com/2014/10/02/continuous-integration-1-test-coverage/ http://ilovesymposia.com/2014/10/13/continuous-integration-in-python-3-set-up-your-test-configuration-files/ http://ilovesymposia.com/2014/10/15/continuous-integration-in-python-4-set-up-travis-ci/ http://ilovesymposia.com/2014/10/15/continuous-integration-in-python-5-report-test-coverage-using-coveralls/ http://ilovesymposia.com/2014/10/17/continuous-integration-in-python-6-show-off-your-work/ http://ilovesymposia.com/2014/10/27/continuous-integration-in-python-7-some-helper-tools-and-final-thoughts/
-
Uses a project or repository's history to plot user contributions, displaying an elegant, colored graph of the file arborescence.
After running it on quite different projects...
- Python/Bash CI/Jenkins scripts
- Qt apps: GoldenDict, Psi+
- PHP website: Shaarli
...watching some vids on teh intartubez:
- Minecraft: https://www.youtube.com/watch?v=zRjTyRly5WA
- Linux kernel: https://www.youtube.com/watch?v=AhDiYPLo3p4
- Python: https://www.youtube.com/watch?v=cNBtDstOTmA
It allows to arbitrary spot some interesting implementation aspects (sorted by descending impact):
- language-dependent trees (oh hai Java packages ^^)
- framework-dependent trees
- project-management method (none, Agile, TDD)
Having a graphical tool also quickly shows:
- the overall structure of the project (a bit cooler than a simple $ tree, way quicker than loading the project on an IDE)
- the repartition of files (by extensions)
- who are the most active contributors
- what are the most modified files over time
- who does what: additions, deletions, refactoring
Some more CI-related matters:
- are there any tests?
- what is the source code / test code ratio? (we could expect a project/lib with N modules to have at least N test modules)
- who initiates / implements / optimizes test code?
-
Awesome thread! The topvoted comments show extremely good - yet simple - reasons to become a unit test maniac ;-)
See also: