Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 39,511
    • Issues 39,511
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,222
    • Merge requests 1,222
  • Requirements
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #19896

Closed
Open
Created Oct 20, 2017 by James Ramsay (ex-GitLab)@jramsay-gitlab🔴Contributor

Automatic merge of Crowdin translations

Goal

To have an automatic trigger of the pipeline created in #250314 so that we do not need manual intervention to get the translation MR ready to be merged.

Pre-requisites

This can be completed after we have:

  1. Created a script(s) which can execute the steps we currently perform manually: #23256
  2. Created a pipeline that can be triggered manually: #250314

Notes

Investigation was completed into how we can achieve this here: #227181 (comment 410472981)

It looks like we have two main options for the trigger:

Crowdin triggered

We can set up the Crowdin integration to regularly push to the i18n-master branch. The possible intervals from the Crowdin integration are:

  1. 10 20 30 40 50 minutes
  2. 1 3 6 12 24 hours

This will sync the translations, adding to the branch if it already exists or creating a new one if it's missing.

GitLab triggered

We can set up a Pipeline Schedule to trigger our own pipeline on any schedule we want.

This requires a target branch and currently we delete the master-i18n branch after every merge. It also doesn't look like there is an API endpoint on Crowdin for managing integrations. I think to get this working, we would have to leave the integration enabled and always have a master-i18n branch available (with a large number of commits).

Edited Sep 16, 2020 by Josianne Hyson
Assignee
Assign to
Time tracking