summaryrefslogtreecommitdiff
path: root/yarns/splitting.yarn
Commit message (Collapse)AuthorAgeFilesLines
* Test nested deploymentsRichard Maw2014-03-141-1/+4
|
* yarns: set deployment name based on system nameRichard Maw2014-03-141-1/+1
|
* Don't use repo or ref in test suiteRichard Maw2014-02-131-2/+0
|
* yarns: Move system artifact inclusion implementationRichard Maw2014-01-221-15/+2
| | | | | | This moves the GIVEN system $system uses $artifacts from $source to the generic implements section, and the Python implementation into the edit-morph helper script.
* yarns: Add test for not building unnecessary chunksRichard Maw2014-01-221-0/+55
| | | | | | | | | | | | | | | | It's an unintended, but possibly not unwelcome feature, that if you have a system that includes stratum artifacts that don't require building the whole stratum, that those chunks are not built. It's debatable whether the confusion of being able to have chunks defined that aren't built outweighs reduced build-times, indeed the test works by having a chunk that can never successfully build, which shows that one pitfall is the possibility of not noticing some chunks fail to build. However, whether it's a good thing or not, we should document this behaviour with a test, so that we don't accidentally break behaviour that someone depends on.
* yarns: Add commentary for splitting scenariosRichard Maw2014-01-221-0/+36
|
* yarns: Add tests for building systems with splittingRichard Maw2014-01-161-0/+129
This includes tests for systems with the default splits and a system that selects only one of the produced stratum artifacts to go into the system artifact, since this is roughly the expected use-case for the tiny system morphologies.