magnum-ui is a special snowflake in that its project name is magnum-ui,
but the directory base for source and translations is magnum_ui. Since
it's a Django project, it also isn't treated like a general Python
project anyway, so treat it like django_openstack_auth, by performing
a little refactoring.
Since the repo now contains files, and is marked for translations in
projects.yaml anyway, enable it for translations jobs.
Change-Id: I7eb73181cccae6d4bfb81848d39099d3502a044c
This adds tarball constraints jobs and adds a new template section
that defines only the test jobs, while keeping the full set named
as expected.
Implements Blueprint: Requirements-Management
Change-Id: Ib6f2e7677dfa348cf5ddc077557d7fa16b9d7ccd
Adds cover-constraints jobs and adds it to Neutron's check queue
Implements Blueprint: Requirements-Management
Change-Id: Ia3cb7d69cac0e4763525516702aea0b214400c94
Adds pep8-constraints jobs and adds it to Neutron's check queue
Implements Blueprint: Requirements-Management
Change-Id: I821a7b6056f2b7e469f47bd8e01aacf6ebde6c8b
Ignore alpha, beta, rc versions when determining if we are publishing
the latest version of a projects documentation. These pre release
versions will still publish to /developer/project/$version but won't
update the root location of /developer/project.
This works around an issue with sort -V sorting the alphas, betas, and
rcs higher than the actual release. It also arguable better represents
what we want to do when publishing the latest of a release.
Change-Id: I2a4cd00414dee2e8307c681ed2bc6b61f7c670d6
Adds docs-constraints job and adds it to Neutron's check queue
Implements Blueprint: Requirements-Management
Change-Id: Ic03387337fc760f3ecc6041cf1d7a7724d722b70
OpenStack has stopped using date based versioning. Dates sort before
shorter semver'd versions which breaks the doc builds determination if
the docs should be writting to root of doc location or /$TAG. We can use
the old hack that we have in place for the clients on all the projects
now to fix this.
Change-Id: I71b0bb6604a9adf3cb898d0b3fdff77f900f83d4
The tarballs that are uploaded to tarballs.openstack.org are suffixed
with *.tar.gz, rather than *.tgz. This corrects the typo.
http://tarballs.openstack.org/eslint-config-openstack/
Change-Id: I526e421dd54b184bcc1e01d8052852c6e089a3e0
Use sudo to rename horizon config file because the default permissions do not allow it.
Without sudo, the mv fails because of "Permission denied".
Change-Id: Iec7f557c8565c5f70c490a32e1ad1d0ebd39868a
This will make it so ceph-related configuration and logs
will be picked up too since puppet-ceph is still in
stackforge for the time being.
Change-Id: Ib6e6cb72eb7f9188155cc5d393771aa5105d6937
We do not need to store any empty source translation files in git or in
Zanata. There are many empty LOG source translation files, so let's
remove them.
Note we always keep the "main" files, the "main" files should always
have content.
The change tests after generation of LOG source translation files
whether these are empty and deletes them from filesystem and git.
Change-Id: I0957c66fca5aa5ded93c858766a4c0a93f963032
Today's import includes some files where only the Generated-By line
changes since Babel updated from 2.0 to 2.1.1. Add line to blacklist so
that a review is not generated for files with just this single line
changed.
Change-Id: I8bd477882ca621ece95faa90b4edf2da39925785
If /etc/openstack-dashboard is present, copy the Horizon config file(s)
in LOG_DIR/etc/openstack-dashboard and make sure they can be read by the
browser (txt files).
Change-Id: I55e8aac6a066820d3e24967ac68bc46ab95e67b6
Extend query-zanata-project-version.py to parse the response it gets
back from the Zanata server, and to also exit 1 if the version is marked
as read-only, saves the proposal slave performing the work if the server
will reject the upload anyway.
Change-Id: I9f66bd34c6d34703b47836f91737282193beb0af
To allow us to check if a version exists for a Zanata project without
requiring us to create a zanata.xml first, add a small script that
uses the Zanata REST API to query for its existance.
Make use it instead of the zanata-cli in upstream_translation_update,
since we can't create a zanata.xml if the version doesn't exist.
Change-Id: I93a72845aa705ce6b72acec9b5d62b5565368ab0
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
As our release versions change keep Zanata up to date with those
changes by pushing them to specific versions in Zanata.
Note that because Zanata can't handle /'s in version names we replace
/'s with -'s and map between git and Zanata that way. We also will exit
0 for success if the current git branch does not have a corresponding
version in Zanata.
Change-Id: I806b2a01c8d4fec2d149be3647931f95b559e76f
Merge the two pull_from_zanata functions. We do not need the special
50 % rule for manuals anymore.
Change-Id: I80ed31b5d59020ece3abcfc4bd9e6f8145dd566a
This adds the {name}-npm-publish job. It downloads a tarball built
by npm-publish-tarball and publishes it to npm.
Both of these have been grouped in publish-to-npm templates and/or
groups, and the job has been added to eslint-config-openstack.
Depends-on: Icce880e7f1d0df427e6cf55db6e8cd98e816c141
Change-Id: I1206d002c31d0960f76d65a364c37716dc583430
Create extract_messages function that can be used by both python and
django_openstack_auth repositories.
This enables the extra keywords for django_openstack_auth as well.
Change-Id: Ica998700215db5a0eae6aa88f4462ae416af2bdd
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
Building on the excellent work done in
I54d560398daa67af8effeb794fce11e53affa1a6, collapse two case blocks
into one.
Change-Id: I9dfe79ed12fa93c30aab3e52a8357c44d1cba938
There is code in ZanataUtils that will read an existing zanata.xml,
and parse the details into an instance to support changing an
existing XML file. We have never made use of this functionality,
and it just tripped me up when testing a change for the last time,
destroy it.
Change-Id: Ie3e3ba3d8171ae912f2706dfeb756c007b51b703
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
When the code was refactored into ZanataRestService, one part
was missed -- namely, _fetch_zanata_xml() in ZanataUtils still
supported a verify argument, but never used it. Remove it.
Change-Id: Id6d39f24bacbf784b2cd230268cdc67ab3fe75fa
Update comments for switch to Zanata.
Remove special handling for glossary that was needed by transifex and is
now a nop.
Change-Id: I74b40d15b652de036dd94a0c024aeee828d31236
Remove all invocations of transifex client "tx".
This removes also the script populate-zanata-project.sh that is not
needed anymore, since we have switch to Zanata and started translating
there. The script is broken with the removal of "tx" support in other
places and not needed anymore.
Change-Id: I74350c92da425a6bf32ea1debd217a531dc2f400
Rename .conf file to .txt, so we can use the browser to view the files
directly. Currently it's a *.conf.gz file so we need to download the
file, and extract it to see it.
Renaming to .txt.gz will be consistent with other files and will
simplify debug.
Change-Id: I8c6e029124b98190baf94f7d8e7dc179f92bc80d
With the exception of openstack-manuals, we don't want glossary
changes proposed to Gerrit. Adjust common_translation_update.sh
to add the glossary directories to the excluded files.
Change-Id: Id732c048200f241f160188969737bd38b679ecf6
Add X-Generator header to ignore list: If this variable changes, there's
no need to update the translations.
Refactor to write regex only once.
Change-Id: Ic4d1ef140c1419bf14e43bd89b371d8324c79193
Switch the translation scripts to only pull from Zanata, no matter
what extra arguments they are passed on the command line. This does
not completly remove support for Transifex, which will be cleaned up
in a future commit.
Change-Id: I21bd54d4205693315da1152a310ff4faf22531a5
Translations proposals are being moved to being submitted by Zanata rather than
Transifex, reflect this in the Gerrit topic.
Change-Id: I9bd7dc8c6cd761cdcd50b7ec0dcd34e57b253f47
This removes the code from all four upstream_translation_* scripts
that pushes new .pot files up to Transifex, and forces the comments
around them to be in line.
This leaves Transifex setup in place for the moment, since the
propose jobs that pull from Transifex are still utilising it.
Change-Id: I702e6073f92faaa79a7aa53c44022f9e437721af
Rather than pass verify to each function that requires it, refactor
it down the stack into __init__. Now that we have moved to using
translate.o.o which has a trusted certificate, switch the default
to True.
Add a command-line argument --no-verify to create-zanata-xml to ease
testing against translate-dev.
Change-Id: I0f2314a8e82c3b7f1c96f28408c36ea1dd786e2f