- Add templates for Pike translation
- Set up horizon and plugin projects who currently have
stable/pike branch listed in https://translate.openstack.org/
Change-Id: I224ffceb49fad380ab894dc2d8b476b8edf76aab
openstack-manuals is the only repo that has mitaka translations set up
but the project is since some time read-only in zanata. Thus, remove the
now unneeded job and remove all unused templates.
Change-Id: I513ce52fa3bd31e4a7cf53fc412cc5addcf98a65
- Add templates for Ocata translation
- Set up horizon and plugin projects who currently have
stable/ocata branch listed in https://translate.openstack.org/
Change-Id: I1384dc9a6feb891799b72af527e44b22d9dbd376
Zuul-cloner / zuul-merger have been fixed and can be used again.
This reverts commit 759da2b1cf.
Change-Id: I99bf00b046951ed6ea544572c52138f671e78be0
Depends-On: If22d8cfbe591afe4f5516da1eb3b0be98b2de874
This is a partial revert of I7787daf025f4f14cf665db0366fa81f54adfa884.
We cannot use zuul-cloner in the periodic job right now since
zuul-cloner will reach out to a zuul-merger (thanks to a passed
environment variable) and that zuul-merger might not have the latest.
This is only hitting us in periodic jobs.
This leads to changes that have directly merge conflicts since they are
based on older jobs.
Use normal git commands for checking out - those go to git.openstack.org
instead to a zuul-merger.
Once zuul-cloner/zuul-merger is fixed, this change can get reverted
again.
Change-Id: I2dfac4c36ace4942840bf05048272fab0a0512ba
Since we have zuul-cloner on the proposal node now, we can use it there.
So, remove the constraints-git-prep and
zuul-git-branch-prep-upper-constraints and replace it with the normal
zuul-cloner builders that set up constraints.
The two builders have been used only for translation jobs, we can remove
them completely now.
Change-Id: I7787daf025f4f14cf665db0366fa81f54adfa884
The translation jobs run on the proposal node that does not have
zuul-cloner installed. To allow useage of constraints in venv
environment, setup constraints with manual checkout of requirements
repository.
Change-Id: I080990ecc2c7ea725eae930d8597fb7937bf1f1d
Run all jobs on xenial for the documentation team jobs, for most cases
these are only run on master anyhow - and those few repos with branches
do not need trusty for running.
Change-Id: I337888e74bae983439cbf0f5e047f4f4023bc8ec
Translations for liberty are done, remove them from the only project
that still had it - openstack-manuals.
Change-Id: Ieedbd00a06616cf7105567ab93ce505a445bc9d9
This is related to zuulv25, we make sure console-log is the last
publisher to ensure zuul-launcher logs are also uploaded.
Change-Id: I1616b97fad2b97fb9e977ec14543aab4bc673b58
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
So we can avoid using the jenkins-specific postbuildscript plugin,
move the proposal slave cleanup to a builder. Run it first so that
it always runs. Since we're running it first, we can't use it to
clean up our current workspace, so instead, ask it to clean up all
workspaces.
Change-Id: I54a187d643fb76f10cc11411d546c41348b5592e
Add subunit testr output at end of run of the translation scripts, so
that healthcheck will have information about success/failure of the job.
This is implemented as an exit trap since we abort on every error and
need to provide the failure message.
Also, upload the healthcheck data to logs.openstack.org so that
healthcheck can import it.
This should be a temporary solution until healthcheck can get data from
Zuul about failure/success of job runs using database access.
Change-Id: I74bba9659a9767027e2daa649ec6f38bf822b65a
We want to publish to
tarballs.openstack.org/translation-source/PROJECT/VERSION . Correctly
construct path for it.
Change-Id: I9802f50cae5dd461f76d8ba016a5f404fe74f4f3
Publish all pot files to
tarballs.openstack.org/translation-source/{name}/VERSION
This way we have always the most recent pot files available for
reviewers and can remove them from the git repositories in a followup.
Change-Id: I3c5e145115206b773466a74d63fad84da17f25e5
Setup translations for all projects that are part of the translation
plan of the i18n team (see https://translate.openstack.org/) and which
will have stable/mitaka branches.
Note that manual projects are not ready for stable/mitaka, so those are
not included.
Change-Id: Ieedd94bc7b5214b2b036971c62406ca52f282082
Use again tox-ENV as standard tox job instead of tox-nodb-ENV.
The old tox-ENV job was bare-trusty based and can get removed now.
Change-Id: I837e02dc74c5860235b1a58e9a304fdaec281c2e
Translation team has said these are the priority projects for liberty
translations to start with them when adding version support. Horizon
will be in a follow up patch as they haven't made a liberty branch yet.
Change-Id: I8049b7ad0a9524c0bfaff6090cf484dccc505836
To support multiple translation versions in Zanata we need to make the
reverse push into Gerrit branch aware as well. Do this by setting up the
existing propose translation jobs to accept a branch parameter which
tells them which version to pull from Zanata and where to push into
Gerrit.
This will add a new periodic jenkins job for each release/branch.
Change-Id: Ia206bfaa7dd6eaad6aa1f6e5ddbbbf9cdadf8db0
Merge
jenkins/scripts/propose_translation_update_django_openstack_auth.sh,
jenkins/scripts/propose_translation_update_horizon.sh, and
jenkins/scripts/propose_translation_update_manuals.sh into
jenkins/scripts/propose_translation_update.sh.
Update Jenkins and Zuul files, we can use now the same job
in all cases.
Change-Id: Idb9e8534dfc0454d75fe186e1a4a454832c8fdae
Merge upstream_translation_update_manuals.sh,
upstream_translation_horizon.sh, and
upstream_translation_django_openstack_auth.sh into
upstream_translation_update.sh.
Adjust job definition for these projects so that the new scripts
get used.
Adjust layout.yaml for change, remove now obsolete condition.
Change-Id: I54d560398daa67af8effeb794fce11e53affa1a6
Now that we are switched to zanata we don't need two sets of job names
to keep the transifex vs zanata split straight in JJB and Zuul. Just
condense down to translation-jobs.
Change-Id: Ic512b2f58a1c9a084f4e25fdf4761fd0c4e6ff0a
Now that we have switched all projects to pulling translations from
Zanata, as a first step, destroy all the jobs and their related job
groups that are no longer used.
Change-Id: I616dba7a8e81dfefeaa246ec5a80c1fdb47a2208
The existing function pull_from_zanata would only work for the simple
Python project case of pulling translations from Zanata -- with only
locales directory and trivial rules to apply, with no real hope of
working for Horizon or OpenStack Manuals, given the current
functionality of the Zanata CLI utility.
Rewrite it to download every translation from Zanata and perform some
checks by hand if we keep the file or remove it. This also required
refactoring a large portion of cleanup_po_files so both functions could
leverage the same code. OpenStack Manuals treats downloaded
translations sufficiently different that a similar function was required.
This also adds full support for Horizon and OpenStack Manuals projects,
including jobs, as well as new job templates to make it easier to
transition projects to pulling from Zanata. Adding -zanata jobs for the
Python projects and django_openstack_auth is not required, they are
already present.
Change-Id: I5b9f2eca7f099c56057fc5d09b4bbfe5ea5c596d
To help move to Zanata, we should pull down translations from
the server. Add a function that should behave the same way as
the existing Transifex function, as well as changing two existing
scripts to call it based on a command-line parameter. Add two new
jobs with a -zanata suffix so we can switch projects one at a time.
This change deals with all of the Python projects and
django_openstack_auth. Horizon and OpenStack manuals will be dealt with
in a future patch.
Change-Id: I8003ac37aeb89d59ceeba2e75eed2f8100b82367
To avoid cruft in the long living proposal node which leads to a full
disk, regularly cleanup some parts.
Create a new macro to build up the repository workspace and have
it cleanup at most once a day.
Use the macro in all translation jobs.
Change-Id: I0f78bb21c4f15ae3974150eb83e5144a469a0554
This repo was created from filter branching the openstack-infra/
config repo. This process brought a lot of cruft with it in the
form of directories that we no longer need. This patch removes
that cruft so we begin with a tidier repo.
Change-Id: Ibffad1b11c0c5f84eedfb0365369f60c4961a0f3
Monty Taylor