[tor-bugs] #32746 [Internal Services/Service - jenkins]: translations repo and jenkins: reduce builds

[Tor Bug Tracker & Wiki]

#32746: translations repo and jenkins: reduce builds
-------------------------------------------------+------------------------
 Reporter:  emmapeel                             |          Owner:  weasel
     Type:  enhancement                          |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Internal Services/Service - jenkins  |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  lektor, l10n, jenkins                |  Actual Points:
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+------------------------
Description changed by emmapeel:

Old description:

> i have been thinking on how to use our resources more wisely regarding
> the translations and the websites.
>
> At this moment we are building many branches anew each time we push
> changes to our translations repository.
>
> This results on a situation when if there is people translating the
> support portal to Malayalam, which is still not published, and therefore
> making changes to the translation repository, the website is rebuild
> several times when there have been no actual changes to it.
>
> On the other hand, the quick updates are very useful for translators, and
> they use the staging version of the site a lot, since most of the
> translators work happens _before_ the website is released.
>
> But the lots of updates from translators and the amount of yet-incomplete
> languages that are built on the staging site causes some trouble to other
> web developers and confuses tehir development, also it makes staging hard
> to update regarding master because of the language configurations, etc.
>
> So I propose the following scheduling in lektor-jenkins-translation
> branches:
>
> master/staging/develop ---> when there is a change on this branches,
>                             we pull the translation repo and update all
> together
>
> translations           ---> we rebuild when there are changes on the
> branch
>                             AND changes on the translation repo branch as
> well
>
> If we would want to update the translations in branches
> master/staging/develop, we should be able to do it simply by building
> from the web interface or similar.
>
> This way we can reduce the builds and make development less cumbersome,
> while also providing a quick preview of their changes to active
> translators.
>
> We can also prevent accidentally publishing incomplete languages, or
> removing languages from the 'preview' website.

New description:

 i have been thinking on how to use our resources more wisely regarding the
 translations and the websites.

 At this moment we are building many branches anew each time we push
 changes to our translations repository.

 This results on a situation when if there is people translating the
 support portal to Malayalam, which is still not published, and therefore
 making changes to the translation repository, the website is rebuild
 several times when there have been no actual changes to it.

 On the other hand, the quick updates are very useful for translators, and
 they use the staging version of the site a lot, since most of the
 translators work happens _before_ the website is released.

 But the lots of updates from translators and the amount of yet-incomplete
 languages that are built on the staging site causes some trouble to other
 web developers and confuses tehir development, also it makes staging hard
 to update regarding master because of the language configurations, etc.

 So I propose the following scheduling in lektor-jenkins-translation
 branches:

 master/staging/develop ---> when there is a change on this branches,
                             we pull the translation repo and update all
 together

 translations           ---> we rebuild when there are changes on the
 branch
                             AND changes on the translation repo branch as
 well

 If we would want to update the translations in branches
 master/staging/develop, we should be able to do it simply by building from
 the web interface or similar.

 This way we can reduce the builds and make development less cumbersome,
 while also providing a quick preview of their changes to active
 translators.

 We can also prevent accidentally publishing incomplete languages, or
 removing languages from the 'preview' website.


 So, for this to be implemented we need to:

 * Make sure that the 'translations' branches are updated when their
 corresponding branch at https://gitweb.torproject.org/translation.git/
 gets updated.
 * Stop building the master/develop/staging builds each time there is a
 commit in  their corresponding
 https://gitweb.torproject.org/translation.git/ branch, and only build when
 a commit is pushed to lektor itself.
 * Remove extra languages in staging and develop, and leave them only in
 translations.

 Please let me know what you think

--

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32746#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online