Some fresh news
I'm currently cleaning/rewriting some core functionality such as the persistence of build results. This was a good opportunity to implement a nice feature : the build results are now based on the git tree rather than the commit. Let me explain it to you.
In git, a commit is a message, an author, a date, some parents commit (1 most of the time, 2 or more if merge commit) and a tree.
Git trees are a pseudo filesystem. This mimics the content of your working copy. A git tree, as every object, is referenced by the SHA1 of its content.
When you trigger a build, this is the tree which is important, not the commit. For instance, if you do a git commit --amend to fix a typo in the message, the commit wouldn't be the same, but the tree will because the content hasn't been altered. So if you've already build this commit, changing the commit message won't alter the result of the build (OK/Fail).
This is the purpose of the feature #38 I've merged by this night (https://github.com/ptitfred/magrit/commit/b6a02b5fdbdb9ac8d8e96f17b58621d4a0bd3c4c
I'm very pleased to announce my "jobs offers" have been answered by 2 developers.
The range of functionality we're able to deliver will so be enlarged a lot! Thanks both of you.
cc +Dani Perez +Fabrice SZNAJDERMAN
My "jobs offers" are still opened on similar topic for those who could be interested.
There's also work to do in core of Magrit, so any benevolant will be welcome!