Automatic build of translation branch

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Automatic build of translation branch

John Mandereau
Dear translators,

As you might have noticed on lilypond-devel list, an autobuild script
Patchy runs at least every 8 hours to build staging branch, and if
successful fast-forward master from it and put built docs on
http://grenouille.lilynet.net/lilypond-web/master

How about doing a similar thing for translation branch?
There are two possible scenarios.

1) Build translation branch every 8 hours, send a report to this list
and if succesful put the built docs on grenouille.lilynet.net.

2) Use the staging/master mechanism for translations: add a new branch
translation-staging where work on translations should be pushed to,
build this branch every 8 hours, and if succesful fast-forward
translation from it and put the built docs on grenouille.lilynet.net.
No commits should be pushed to translation branch directly.  Merges with
master and staging should be done only these ways, manually because
there may be conflicts when merging:
master into translation-staging
translation into staging

Scenario 2) is good in case translation branch breakage is frequent and
annoys translators, I think it doesn't add burden to the translations
meister Francisco, but it might make commits propagation between master
and translation a bit slower (or not).

I'm counting on your comments,
Best,
John



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Automatic build of translation branch

Francisco Vila
2012/8/3 John Mandereau <[hidden email]>:
> How about doing a similar thing for translation branch?

I welcome this idea.

> 1) Build translation branch every 8 hours, send a report to this list
> and if succesful put the built docs on grenouille.lilynet.net.

every 8 hours in presence of any new commits, I understand.

>
> 2) Use the staging/master mechanism for translations: add a new branch
> translation-staging where work on translations should be pushed to,
> build this branch every 8 hours, and if succesful fast-forward
> translation from it and put the built docs on grenouille.lilynet.net.
> No commits should be pushed to translation branch directly.  Merges with
> master and staging should be done only these ways, manually because
> there may be conflicts when merging:
> master into translation-staging
> translation into staging
>
> Scenario 2) is good in case translation branch breakage is frequent and
> annoys translators, I think it doesn't add burden to the translations
> meister Francisco, but it might make commits propagation between master
> and translation a bit slower (or not).

I like 1) best because translation branch already works as a staging
for translations, breakage is not frequent (some could not see it that
way) and occasional breakage is not causing much annoyance. I only
merge to staging if docs build; it would be more interesting to know
when "distribution" problems happen, and this requires running GUB.
This is what really annoys me because this is why I've been scolded
for in the past.

Propagation to master is already slow (5-10 days max) but frequent
build of translation branch would make this less important.

Despite of this all, I am willing to take the road of
translation/staging if you think it worths the trouble.

> I'm counting on your comments,

I am going to be a bit slow on commenting from now on until last ten
days of August.

Thanks for your work,
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Automatic build of translation branch

John Mandereau
Il giorno ven, 03/08/2012 alle 18.10 +0200, Francisco Vila ha scritto:
> 2012/8/3 John Mandereau <[hidden email]>:
> > How about doing a similar thing for translation branch?
>
> I welcome this idea.
>
> > 1) Build translation branch every 8 hours, send a report to this list
> > and if succesful put the built docs on grenouille.lilynet.net.
>
> every 8 hours in presence of any new commits, I understand.

Sure.  It could be more often if the server could run the overall build
in less than three hours (it currently takes 3 hours and a quarter), but
every 8 hours is a fair frequence.


> I like 1) best because translation branch already works as a staging
> for translations, breakage is not frequent (some could not see it that
> way) and occasional breakage is not causing much annoyance.

OK, so I'll go for setting this up this weekend.


>  I only
> merge to staging if docs build; it would be more interesting to know
> when "distribution" problems happen, and this requires running GUB.
> This is what really annoys me because this is why I've been scolded
> for in the past.

I have a big patch in dev/jmandereau for making dist from Git, that also
removes tons of GNUmakefiles that were present only to tell the build
system which files to dist, so much of distribution nightmares we've had
will be stories from the past very soon, as long as people with pushing
permission check build *and* check (with "git status") that their
working directory is clean before pushing (even the daily automatic
build will help with this).


> Despite of this all, I am willing to take the road of
> translation/staging if you think it worths the trouble.

It's up to the translators who work on translation branch to tell, as a
build manager I don't care :-)

Cheers,
John



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Automatic build of translation branch

Jean-Charles MALAHIEUDE
In reply to this post by Francisco Vila
Le 03/08/2012 18:10, Francisco Vila disait :

> 2012/8/3 John Mandereau <[hidden email]>:
>> How about doing a similar thing for translation branch?
>
> I welcome this idea.
>
>> 1) Build translation branch every 8 hours, send a report to this list
>> and if successful put the built docs on grenouille.lilynet.net.
>
> every 8 hours in presence of any new commits, I understand.
>

That's what I understand as well!
We might even advertise it on the different LANG-lists for proofreading.

>>
>> 2) Use the staging/master mechanism for translations [...]
>
> I like 1) best because translation branch already works as a staging
> for translations, breakage is not frequent (some could not see it that
> way) and occasional breakage is not causing much annoyance. I only
> merge to staging if docs build; it would be more interesting to know
> when "distribution" problems happen, and this requires running GUB.
> This is what really annoys me because this is why I've been scolded
> for in the past.
>

This happened several time in the past year, mainly by my fault (not
renaming a .ly in .texidoc). This could have been avoided if "make dist"
(which makes the tarball) included the check that is on GUB... and every
translator did launch it before sending NEW files.

> Propagation to master is already slow (5-10 days max) but frequent
> build of translation branch would make this less important.
>

2.15.42 nevertheless missed our last updates and the amendments to the
English version.

> Despite of this all, I am willing to take the road of
> translation/staging if you think it's worth the trouble.
>

I think we need a ping from Release Meister when he updates the
building-branch for a last "Mary-go-round" in the 2 or 3 days time
window before releasing, or increase the merge frequency depending on
the "traffic" in Documentation/ (I've noticed that updating something
that has not been merged from master gets tracked by check-translation).


Cheers,
Jean-Charles

ps : by the way, John, since the French version seems to be complete
now, if you need some test on your branch, I'm still at work until the 20th.


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Automatic build of translation branch

Francisco Vila
2012/8/3 Jean-Charles Malahieude <[hidden email]>:
> Le 03/08/2012 18:10, Francisco Vila disait :
>> Propagation to master is already slow (5-10 days max) but frequent
>> build of translation branch would make this less important.
>>
>
> 2.15.42 nevertheless missed our last updates and the amendments to the
> English version.

Unavoidable. It is impossible to include every update and/or amendment
to English versions, even if I merged whenever every single commit
reached staging.

Last merge was July 26, (10 days ago now). The updates you mention are
7 days old today.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Loading...