Commit Graph

3 Commits

Author SHA1 Message Date
James E. Blair e74f571085 Do not add implied branch matchers in project-templates
We parse the project-pipeline definition of a job at the location
of the project-pipeline.  This includes both 'project' stanzas and
'project-templates' which are parsed in exactly the same way.  This
normally gives us the behavior we expect in that the job variants
defined by the project or project-template appear to be defined in
the location of the project or project-template.  However, in one
case, we want a 'late-binding' rather than 'early-binding' behavior.

When it comes to calculating implied branch matchers, we want to
use the value that would be derived if there were no project-template,
and instead the job were simply defined on the project stanza itself.

What is intended to happen is that project-pipeline job variants in
a config project should never have implied branch matchers (since
config projects don't have more than one branch).  However, project-
pipeline job variants on in-repo project stazas should get an implied
branch matcher for the branch it's defined on.  This is how we end up
with behavior where the project definition in a project's master branch
controls behavior only on the master branch (unless branches are
explicitly specified), and the definition in a stable branch controls
only the stable branch.

That behavior should happen regardless of where a project-template is
defined.  Currently we are setting an implied branch matcher for job
variants in a project template at the location of definition.  Instead,
set them when the job is actually used in a project.

Change-Id: I5c8fbb3e0a2ecfac8bd95795be002e8cd15e61db
2017-09-30 10:19:07 -07:00
James E. Blair 8a3729d4dc Add playbooks for all test jobs
A subsequent change will expect a playbook to exist for every job
that is run, including tests.  Satisfy that by making noop playbooks
for all current test jobs.

Change-Id: Ic19ad8d124ba34fcde0b2056da70f950f841cf17
2017-02-03 14:23:58 -08:00
James E. Blair 6cdf2f2047 Add utility program to print test fixture configuration
In-repo configuration means that test configs are more complex,
requiring directory hierarchies representing multiple git repos.
To aid a developer wanting to see a test configuration at a glance,
add a script to print out the relevant files.

Change-Id: I5599c72be343c0e391d8789434e7793cac83ec41
2016-08-02 16:52:34 -07:00