Integração GitLab
Integration with GitLab synchronizes source and translation files between your GitLab repository and translation project in Crowdin Enterprise. Todos os ficheiros traduzidos e aprovados, serão automaticamente, enviados como um merge request para o ramo l10n no repositório do GitLab.
Connecting GitLab with Crowdin Enterprise
There are two possible options you can choose from. You can either use your GitLab account or GitLab Enterprise account.
Connecting GitLab Account
- Abra seu Crowdin projeto empresarial e vá para Aplicações > Sistema.
- Click on GitLab in the Integrations list.
- Click Set Up Integration to integrate via your GitLab account.
- Then authorize the connection with Crowdin Enterprise on the GitLab side.
Connecting GitLab Enterprise Account
-
To integrate via GitLab Enterprise Account you should create an access token. Make sure to select the required scope:
- api – Grants complete read/write access to the API, including all groups and projects, the container registry, and the package registry
- Click on GitLab Enterprise in the Integrations list.
- Then insert your access token and Base URL into corresponding fields. Click Set Up Integration to proceed.
Selecting Repository
In the appeared dialog, select your repository and branches that should be translated. It’s recommended to switch Duplicate Strings to Show within a version branch, so identical strings will be hidden between branches. If your source files contain strings with apparent identifiers (keys), it’s better to use a strict version of this option. In other cases, feel free to use a regular one.
Leia mais sobre Frases Duplicadas.
When you work with private integrations (e.g., integrations with self-hosted VCS), you need to add dedicated Crowdin Enterprise IP addresses to the whitelist to ensure that it operates properly while staying secure.
Read more about IP Addresses.
Ramos de Serviço
When translations are finished and your languages are ready to go live, Crowdin Enterprise sends the merge request with translations to your version control system. Para cada ramo que está em localização, o Crowdin cria ramos de serviço adicionais com traduções. We don’t commit directly to the master branch so that you can verify translations first.
By default, l10n_ is added to the created service branch name. If necessary, you can easily change it.
Synchronization Settings
By default, sources are not pushed to the repo with translations. </5090>.
There are cases when it’s necessary to disable translations from being pushed to the repo temporarily. In this situation, click Edit, clear Sync Schedule in the integration settings, and click Save. When ready to sync translations with the repo, select the Sync Schedule, and click Save.
The synchronization is processed every hour automatically. If necessary, you can change the update interval in the integration settings. To configure the synchronization schedule – click Edit, scroll down to the Sync Schedule, set the preferred interval, and click Save.
Não dependendo das configurações de sincronização, as alterações dos arquivos de origem no repositório ainda serão sincronizadas com o Crowdin Enterprise a cada dez minutos.
Branches to Sync Automatically
When you set up the integration you select existing repository branches to be added to the Crowdin Enterprise project. To add future branches from GitLab to Crowdin Enterprise automatically, create a pattern for the branch names in the integration settings.
For example, you add a pattern *feature in the GitLab integration settings. In this case, the future branches that contain this word at the end of the title will be added to the project.
To add a pattern for branch names, follow these steps:
- Click Edit in the GitLab integration section.
- In the appeared dialog, scroll down to the Branches to Sync Automatically.
- In the Branches to Sync Automatically field, use wildcard selectors such as ‘*’, ‘?’, ‘[set]’, ‘' and others to identify the necessary branches.
- Clica em Guardar.
Default configuration file names is saif
crowdin.yml is the default file name that is used for automatically synchronized branches. To change the default settings, click Edit, specify the preferred name in the Default configuration file name field in the integration settings, and click Save.
Selecionar Conteúdo para Sincronização
Para obter a integração a funcionar, deves especificar quais ficheiros de origem devem ser traduzidos e como o Crowdin Enterprise deve estruturar ficheiros traduzidos no teu repositório. Bay code free access to mobile If you see a red icon with an exclamatory mark next to the service branch name, it means that you didn’t select content for synchronization.
There are two ways to do that: configuring online or manually by creating a configuration file.
Configuração Online
Este procedimento é o mesmo para todas as integrações com sistemas de controlo de versão (VCS). Verifica Integrações VCS: Configuração Online para saber como selecionar o conteúdo para sincronização online.
Criar Ficheiro de Configuração
Configuration file crowdin.yml should be stored in the GitLab repository along with each separate branch that you want to translate, so Crowdin Enterprise knows what files exactly should be sent for translations.
It should have the same structure as required for CLI, but your project’s credentials should not be stored in the file’s header for security reasons.
Lê mais sobre criar um ficheiro de configuração.
Working with Multiple Repositories within One Project
When working with a multiplatform product that has versions for different operating systems, you might want to connect multiple repositories that contain source files for each operating system. In this case, localization resources (e.g., TMs, Glossaries) and translations could be used more efficiently, reducing the time needed for project localization.
To add another repository, follow these steps:
- Abra seu Crowdin projeto empresarial e vá para Aplicações > Sistema.
- Click on GitLab in the Integrations list.
- Click Add Repository.
- Configure the integration with the new repository according to your needs and preferences.
Verificar o Estado de Sincronização
Once the integration is set up, all the related information is stored in the Applications > System > GitLab section.
After the integration is connected, the settings can be updated only by the project member who configured it. All project managers except the person who configured the integration will see the Edit button disabled with the following notice when hovering over it: Integration was configured by {Full Name}.
The synchronization is processed every hour automatically. If you need to launch the synchronization instantly – click Sync Now. Alternatively, if you need to sync only one branch separately, click 
on the needed branch and select Sync branch.
Uploading Translations from Repo
By default, the translations stored on the repo are uploaded to Crowdin Enterprise during the first synchronization only. To upload translations to Crowdin Enterprise manually, click next to the Sync Now button, and click Upload Translations. The integration will upload existing translations to your Crowdin Enterprise project.
Q&A
Q: I have an application build configured to be triggered by every commit. Since Crowdin commits each translation file in a separate commit, how can I avoid unnecessary application builds triggered by commits from Crowdin?
A: Since VCS integrations in Crowdin use API to commit files but not Git, each file is committed separately.
Here are a few recommendations that might help solve similar situations:
- Use the
export_languagesoption to skip commits from languages you’re not interested in yet. Read more about the Export languages parameter for VCS integrations. - Use the [ci skip] tag in the commit messages to skip unnecessary builds. Read more about the Commit Message parameter for VCS integrations.
- Configure the preferred sync interval using Sync Schedule (e.g., set the sync once in 24 hours).
- Squash commits when merging a localization branch to keep the master branch history clean and uncluttered.