The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to the following alert:

Translation status

15 Strings
6%
Browse Translate
380 Words
1%
2,564 Characters
2%

Strings status

Strings Words Characters
15 380 2,564
All strings Browse Translate Zen
1 4 56
Translated strings Browse Translate Zen
14 376 2,508
Unfinished strings Browse Translate Zen
14 376 2,508
Strings marked for edit Browse Translate Zen

Summary

Project website tuist.dev
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses monolingual files.
  • The translation base language can not be edited.
Source code repository https://github.com/tuist/tuist
Repository branch main
Last remote commit feat(server): add Quarantined Tests page with analytics and filtering (#9245) 21d8b6d91c
Marek Fořt authored 01/29/2026
Last commit in Weblate Translated using Weblate (Korean) c381825434
DeepL authored 01/26/2026
Weblate repository https://translate.tuist.dev/git/tuist/documentation-pages/
File mask docs/docs/*/guides/features/registry/continuous-integration.md
Monolingual base language file docs/docs/en/guides/features/registry/continuous-integration.md
Translation file Download docs/docs/es/guides/features/registry/continuous-integration.md
Last change Jan. 22, 2026, 1:07 p.m.
Last change made by Background commit
Language Spanish
Language code es
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 507,599,381
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
01/25/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 15 380 2,564
Translated 6% 1 1% 4 2% 56
Needs editing 93% 14 98% 376 97% 2,508
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 24 changes 0 changes 7 changes 0 changes 43 changes
JanFebMarAprMayJunJulAugSepOctNovDec

Quick numbers

380
Hosted words
15
Hosted strings
6%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+6%
—
Contributors
+100%
User avatar weblate:commit

Changes committed
Changes committed 01/22/2026
User avatar mt:deepl

Automatically translated
Here's an example workflow for GitHub Actions for resolving and caching dependencies when using the default Xcode package integration:
A continuación se muestra un ejemplo de flujo de trabajo de ejemplo para las Acciones de GitHubGitHub Actions para resolver y almacenar en caché las dependencias cuando se utiliza la integración predeterminada del paquetes de Xcode:
01/22/2026
User avatar mt:deepl

Automatically translated
Creating a new pre-unlocked keychain is required only if you are using the Xcode integration of packages.
La creación deSolo es necesario crear un nuevo llavero predesbloqueado sólo es necesaria si sei utiliza la integración de paquetes den Xcode.
01/22/2026
User avatar mt:deepl

Automatically translated
Additionally, you will need to find a path of the `Package.resolved`. You can grab the path by running `ls **/Package.resolved`. The path should look something like `App.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved`.
Además, necesitarátendrás que encontrar unla ruta del paquete `Package.resolved`. Puedes obtener la ruta ejecutando `ls **/Package.resolved`. La ruta debería ser algo parecidosimilar a `App.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved`.
01/22/2026
User avatar mt:deepl

Automatically translated
Clean/cold resolutions are slightly faster with our registry, and you can experience even greater improvements if you persist the resolved dependencies across CI builds. Note that thanks to the registry, the size of the directory that you need to store and restore is much smaller than without the registry, taking significantly less time. To cache dependencies when using the default Xcode package integration, the best way is to specify a custom `clonedSourcePackagesDirPath` when resolving dependencies via `xcodebuild`. This can be done by adding the following to your `Config.swift` file:
Las resoluciones limpias/frías son ligeramente más rápidas con nuestro registro, y puede experimentar mejoras aún mayores si persiste en las dependencias resueltas a travéslo largo de las compilaciones de CI. Tenga en cuenta que, gracias al registro, el tamaño del directorio que necesitas almacenar y restaurar es mucho menor que sin el registro, tardando significativalo que reduce considerablemente menosel tiempo necesario. Para almacenar en caché las dependencias cuando se utiliza la integración de paquetes por defecto dpredeterminada del paquete Xcode, loa mejor manera es especificar una `clonedSourcePackagesDirPath` personalizada cuando seo al resuelvenolver las dependencias a través de `xcodebuild`. Esto se puede hacerse añadiendo lo siguiente a su archivo `Config.swift`:
01/22/2026
User avatar mt:deepl

Automatically translated
`tuist registry login` will then store the credentials in the default keychain. Ensure that your default keychain is created and unlocked _before_ `tuist registry login` is run.
`tuist registry login` almacenará las credenciales en el llavero por defectredeterminado. Asegúresate de que stu llavero predeterminado estáé creado y desbloqueado _antes de ejecutar_ `tuist registry login`.
01/22/2026
User avatar mt:deepl

Automatically translated
Since the registry credentials are stored in a keychain, you need to ensure the keychain can be accessed in the CI environment. Note some CI providers or automation tools like [Fastlane]{1} already create a temporary keychain or provide a built-in way how to create one. However, you can also create one by creating a custom step with the following code:
Dado que las credenciales del registro se almacenan en un llavero, es necesariodebes asegurarste de que el llavero se puedea acceder al llavero en el entorno de CI. Tenga en cuenta que algunos proveedores de CI o herramientas de automatización como [Fastlane]{1} ya crean un llavero temporal o proporcionan una forma integrada de crearl uno. Sin embargo, también puedes crear uno creando un paso personalizado con el siguiente código:
01/22/2026
User avatar mt:deepl

Automatically translated
To use the registry on your CI, you need to ensure that you have logged in to the registry by running `tuist registry login` as part of your workflow.
Para utilizar el registro en su CI, debe asegurarse de que hahaber iniciado sesión en el registro ejecutando `tuist registry login` como parte de su flujo de trabajo.
01/22/2026
User avatar mt:deepl

Automatically translated
For Swift packages and the XcodeProj-based integration, we can use the default `.build` directory located either in the root of the project or in the `Tuist` directory. Make sure the path is correct when setting up your pipeline.
Para los paquetes Swift y la integración basada en XcodeProj, podemos utilizar el directorio por defectredeterminado `.build`, ubicado en la raíz del proyecto o en el directorio `Tuist`. Asegúrate de que la ruta esea correcta cuandoal configuresar tu pipelinecanalización.
01/22/2026
User avatar mt:deepl

Automatically translated
Additionally, you need to ensure the `TUIST_TOKEN` environment variable is set. You can create one by following the documentation {1}here{2}.
Además, debes asegurarste de que la variable de entorno `TUIST_TOKEN` estáé configurada. Puedes crear una siguiendo la documentación {1}aquí{2}.
01/22/2026
Browse all translation changes