JustCode
From APIDesign
| Line 1: | Line 1: | ||
Recently [[Truffle]] project decided to change its repository structure. Rather than keeping [[Truffle]] and its [[API]] in its own repository, the project decided to merge the code into a common repository with [[Graal]] compiler (currently available [https://github.com/graalvm/graal/ here]). This was a simple change from the point of view of the code - merging two git repositories into one is a matter of '''pull''' and '''merge'''. However, a working system isn't just about the code, there are other services around and they may get broken when the code gets shuffled away. | Recently [[Truffle]] project decided to change its repository structure. Rather than keeping [[Truffle]] and its [[API]] in its own repository, the project decided to merge the code into a common repository with [[Graal]] compiler (currently available [https://github.com/graalvm/graal/ here]). This was a simple change from the point of view of the code - merging two git repositories into one is a matter of '''pull''' and '''merge'''. However, a working system isn't just about the code, there are other services around and they may get broken when the code gets shuffled away. | ||
| - | [[Truffle]] repository was primarily the [[API]] repository. With its own release cycles, evolution rules and special tools associated with it. Most importantly there was [[TruffleSigtest]] setup - [[netbeans:Sigtest]] tool is something everyone who seriously thinks about [[API]] has to include in own workflow. Some parts of the [[TruffleSigtest]] rely just on the code - e.g. they still work - it is still possible to execute: | + | [[Truffle]] repository was primarily the [[API]] repository. With its own release cycles, evolution rules and special tools associated with it. Most importantly there was [[TruffleSigtest]] setup - [[netbeans:Sigtest]] tool is something everyone who seriously thinks about [[API]] design has to include in own workflow. Some parts of the [[TruffleSigtest]] rely just on the code - e.g. they still work - it is still possible to execute: |
<source lang="bash"> | <source lang="bash"> | ||
$ mx sigtest --generate | $ mx sigtest --generate | ||
Revision as of 15:20, 5 June 2017
Recently Truffle project decided to change its repository structure. Rather than keeping Truffle and its API in its own repository, the project decided to merge the code into a common repository with Graal compiler (currently available here). This was a simple change from the point of view of the code - merging two git repositories into one is a matter of pull and merge. However, a working system isn't just about the code, there are other services around and they may get broken when the code gets shuffled away.
Truffle repository was primarily the API repository. With its own release cycles, evolution rules and special tools associated with it. Most importantly there was TruffleSigtest setup - netbeans:Sigtest tool is something everyone who seriously thinks about API design has to include in own workflow. Some parts of the TruffleSigtest rely just on the code - e.g. they still work - it is still possible to execute:
$ mx sigtest --generate $ mx sigtest --check binary $ mx sigtest --check all
however other parts of the system (especially the Notification of Daily Changes) are more cloud-like - e.g. they require properly setup jenkins builders to work properly. Obviously they no longer work after the original Truffle repository changed its location. Last Friday I was asked to fix that.
Follow
