Skip to content
This repository has been archived by the owner on Apr 29, 2020. It is now read-only.

[WIP] Transifex automation #28

Closed
wants to merge 1 commit into from

Conversation

lidel
Copy link
Contributor

@lidel lidel commented Sep 6, 2018

Update: turns out we can set up a daily sync without Jenkins: ipfs/ipfs-gui#50 (comment) 🤦‍♂️

Click to expand anyway

This is a part of Translation Project for IPFS GUIs, see it for more context.

The goal of this PR is to add transifex() script support to ci/Jenkinsfile.

We want to make it easy for IPFS projects to add translations. A big help would be if CI could automatically publish new strings from source language (en) to Transifex via the tx CLI tool. That way translators would get notified about new strings to translate on the same day they land in master branch.

The transifex() script should run only:

  • when master branch is built (eg. after PR merge)
  • and only if .tx/config file is present (it means project is added to Transifex)

The setup is similar to ci-websites/: tx (Transifex CLI client) is a python app that runs in an ephemeral container ci-transifex.

TODO

- `tx` client runs is ephemeral container
- source language is uploaded only if build is for `master` branch
  and `.tx/config` file exists

TODO: pass TX_TOKEN somehow

License: MIT
Signed-off-by: Marcin Rataj <[email protected]>
@lidel
Copy link
Contributor Author

lidel commented Sep 9, 2018

I'm closing this for now: we were able to set up Transifex to fetch source locales twice a day from GitHub raw URL, which is good enough and does not require Jenkins.

Keeping branch as a base for future, eg. if we want Jenkins to open a PR with new translations when 100% strings is translated.

@lidel lidel closed this Sep 9, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant