On 15-08-08 10:39 AM, Martin Holmes wrote:
Yes, we could create one that you could start manually. I can give you a login for the Jinks server and permission to do that.
On the other hand, if all three of us can now build this locally, and you don't want to see fresh builds from every commit, is there a point? Cheers, Martin
Cheers, Martin
On 15-08-08 10:18 AM, Lou Burnard wrote:
I *knew* we must have met this problem before!
A Jinks job which tries to build from P5-Pure might well be a good idea, though I would prefer it not to kick off every time I make a modification in the source: that's something I can check locally. Is it possible to have one that I can start manually?
On 08/08/15 17:40, Martin Holmes wrote:
Our Jenkins servers use the latest stylesheets build from the Stylesheets job, not the release version. We did this on purpose so that we wouldn't have to force stylesheets releases just to do P5 development.
Would you like me to set up a build job on Jenkins for P5-Pure?
Cheers, Martin
On 15-08-08 02:40 AM, Lou Burnard wrote:
This means, of course, that this branch cannot be merged with the trunk until there has been a new stylesheet release and we have moved over to using it on our jinxes. Which is a pain, but not too great a one. In the circs, I think I might proceed to phase 2 of operation purity: namely, switching the content models in P5 to use pure ODD. It ought to All Just Work, but...
On 07/08/15 22:39, Martin Holmes wrote:
Ah -- I'm forgetting I should be pointing at a fresh Stylesheets repo. I'll try that when I get a chance. Mine will be building with the usual installed deb.
Cheers, Martin
On 15-08-07 02:36 PM, Syd Bauman wrote:
And I should mention that my builds with a local, up-to-date copy of the Stylesheets/ repo.
MH> The failure comes on make validate for me.