baserock/baserock/morph.git - Morph -- Baserock build tool

	Commit message (Collapse)	Author	Age	Files	Lines
*	Yarns: Preserve the output of morph foo in out-foo	Richard Maw	2014-08-12	1	-2/+3
\|
*	Convert colons to slashes for chunk name	Lars Wirzenius	2014-03-06	1	-0/+9
\|
*	Pass in user's PYTHONPATH to morph when run from yarns	Lars Wirzenius	2014-03-06	1	-1/+10
\| \| \| \| \| \| \| \| \| \| \| \| \|	We carefully _add_ to PYTHONPATH in ./check, if it was set by the user. However, yarn cleans the environment when it runs tests, so we tell it to add PYTHONPATH from ./check to the test environment. Additionally, we change yarns/morph.shell-lib so it doesn't override PYTHONPATH, but adds to it. All of this is necessary to get morph, when run by yarn steps, to have the right PYTHONPATH, which can be (and currently is) to allow the user to specify un-installed versions of dependencies, such as cliapp.
*	Remove setting of SRCDIR in morph.shell-lib	Lars Wirzenius	2014-03-05	1	-9/+0
\| \| \| \| \|	Yarn in Baserock now sets SRCDIR, so it is not necessary for us to set it anymore.
*	yarns: Fix how Morph is run	Sam Thursfield	2014-03-04	1	-6/+2
\| \| \| \| \| \| \| \|	As we are running Morph from the source dir we need to set PYTHONPATH so that extensions are correctly loaded. Also, the version of Yarn in Baserock sets 'SRCDIR' so we do not need to set a default any more.
*	Remove tests for working with null refs	Richard Maw	2014-02-13	1	-6/+1
\| \| \| \| \|	Refs should be completely omitted, and this is now the standard behaviour, so there's little value in testing the behaviour separately.
*	yarns: Correctly allow run_morph to output stderr on failure	Richard Maw	2013-11-29	1	-7/+10
\| \| \| \| \|	Set -e meant that the stderr could never be re-output, catching the return code and re-outputting was not sufficient.
*	yarns: Also output error messages to terminal	Richard Maw	2013-11-22	1	-0/+3
\| \| \| \| \|	Saving the result is useful for the tests, but diagnostics of failures are quicker if the result is printed to the terminal as well.
*	Modify morph test suite to use the new cmdtest	Pedro Alvarez	2013-10-30	1	-0/+19
\|
*	Added scenario test for preventing cross-building	Daniel Firth	2013-10-30	1	-1/+3
\|
*	Move helper script to scripts for use in cmdtests	Richard Maw	2013-09-26	1	-17/+1
\|
*	Make branch commands work with null refs	Richard Maw	2013-09-26	1	-0/+21
\|
*	Refactor code for clarity	Lars Wirzenius	2013-07-31	1	-4/+4
\| \| \| \|	Reported-by: Tiago Gomes
*	Add scenario (yarn) tests for most of branching and merging	Lars Wirzenius	2013-07-30	1	-0/+153
	These scenarios test the basics of most of the subcommands the branch and merge plugin provides. They don't purport to be complete, but give some indication that things work, and form a basis upon which further things can be built. Yarn also isn't included in a Baserock release yet, so we need to keep the cmdtests until Baserock 10 has been released. The existing cmdtest tests are not modified by this: they are left intact, until they can analysed in detail for things to be added to the scenarios. After that, the cmdtest tests will start to go away. Merging is not covered by these tests: it is not clear how merge should work, and the current code is known to do the wrong thing in many cases. Scenarios for merge will be added later. Building is also not covered. Testing builds well needs some additional, careful thinking, and that isn't ready for this patch series. It will be added later.