-
Another subversion repository
Wellcome in 2002 subversion users!
Some very old and stable customers has just discovered Subversion. Bad luck: a lot of cool 聽open source software are on git already!
Read More -
Suppose you are developing a boring Jenkins pipline (like Jenkinsfile-s) with no time at all.
You are forced to commit and then run the jenkins pipeline. Jenkins download the code from your LOCAL repository.
To avoid commit& push roundtrip you are using the simple git daemon command to expose your local repository to jenkins. So jenkins see every commit you has just done.
And you end up doing a lot of commits, full of trial and errors: you would like to “squash” them before pushing your work to your remote repository, to avoid co-worker laugh your wasted time(!)
Git can do that, but I have an hard time to find the easier way of doing it, even reading git books!
So let me explain to you:
Read More -
Nice tool to test:
Git hook scripts are useful for identifying simple issues before submission to code review. We run our hooks on every commit to automatically point out issues in code such as missing semicolons, trailing whitespace, and debug statements. By pointing these issues out before code review, this allows a code reviewer to focus on the architecture of a change while not wasting time with trivial style nitpicks.
As we created more libraries and projects we recognized that sharing our pre-commit hooks across projects is painful. We copied and pasted unwieldy bash scripts from project to project and had to manually change the hooks to work for different project structures.
Read More