[tei-council] Commits, builds, errors and Jenkins

[James Cummings]

On 20/04/11 15:57, Martin Holmes wrote:
>> A full build environment is *not* required for those wanting to
>> make textual changes to the Guidelines.  Martin is undertaking to
>> do a full build because he wants to make sure he can understand
>> and eventually duplicate the process.
>
> That's true, but I was starting from Lou's recommendation last Wednesday
> morning that whenever you change the source, you should test it with a
> local build before committing.

Sure, I don't in any way disagree that this is a good principle. 
  But Stuart was suggesting that this might be a barrier to those 
who only wanted to do prose-related changes.  If the changes 
aren't actually changing the schema, I'd argue using Jenkins is 
probably enough. ;-)

> He also suggested adding a test case to
> the build, to really make sure the changes does what you think it should
> do, but I haven't figured out how to do that yet; for my nested bibl
> thing, I was relying on the fact that my two examples of nested bibls
> were validated successfully.

In this case I *think* it is a case of adding an example of this 
to something like this to P5/Test/testbibl.xml and then running 
the test. When adding a new element you have to make sure that is 
included in the ODD sources being used to generate the schema 
that will validate against it.  But given your examples validate...

-James


-- 
Dr James Cummings, InfoDev,
Computing Services, University of Oxford