fedora-docs-l10n/rawhide-gating/master/pages/optin — Spanish @ Fedora Weblate: --- !Policy product_versions: - fedora-* decision_context: bodhi_update_push_testing subject_type: koji

Translation

English type: delimited block -

Spanish

Needs editing

Skip

	English	Spanish	Actions
	How to Opt in to Gating?	¿Cómo optar en Gating?
	There are two steps to do in order to opt in to Rawhide Gating:	Hay dos pasos a seguir con el objetivo de optar a Rawhide Gating:
	Add tests to your package.	Añadir pruebas a su paquete.
	Configure gating, so that your package is gated on those tests.	Configurar la activación, para que su paquete esté controlado en esas pruebas.
	Add Tests to Your Package	Añada Pruebas a Su Paquete
	You can add tests by following the xref:ci::tests.adoc#_writing[documentation on how to write tests].	Puede añadir pruebas siguiendo la xref:ci::tests.adoc#_writing[documentación sobre como escribir pruebas].
	The gist of it is: Add a `tests/` folder in the git repository of your package and place a file called `tests.yml` in it. This file should be an link:http://docs.ansible.com/ansible/latest/playbooks.html[Ansible playbook] with all the steps required to test your package.	La esencia es: Añadir una carpeta `tests/` en el repositorio git de su paquete y colocar un archivo llamado `tests.yml` en ellat. Este archivo debería ser un link:http://docs.ansible.com/ansible/latest/playbooks.html[Ansible playbook] con todos los pasos requeridos para probar su paquete.
	You need to “tag” the playbook with any or all of the following tags so the tests can be called in the different environments: `classic`, `container`, `atomic`.	Usted necesita “etiquetar” el manual con alguno o todos de los siguientes indicadores de modo que se pueda llamar a las pruebas en diferentes entornos: `classic`, `container`, `atomic`.
	Once you have added a `tests/tests.yml` file, for every update that is subsequently created for that package, the tests will be run and will be shown in the update page under the test results tab.	Una vez que usted ha añadido un archivo `tests/tests.yml`, para cada actualización que se creen seguidamente para este paquete, se ejecutarán las pruebas y se m ostrarán el la página de actualización baja la pestaña de resultado de pruebas.
	For these tests to have an effect, you need to configure the system to gate on them.	Para que estas pruebas tengan efecto, usted necesita configurar el sistema para que las controle.
	Configure Gating	Configurar Gating
	To configure the system to gate your package on tests, you need to add a file called `gating.yaml` to the git repository of the package(s) you want gated.	Para configurar el sistema para controlar su paquete en las pruebas, usted necesita añadir un archivo llamado `gating.yaml` al repositorio git del paquete(s) que desea controlar.
	A simple example for `gating.yaml` would look like this:	Un sencillo ejemplo para `gating.yaml` se vería como esto:
	--- !Policy product_versions: - fedora-* decision_context: bodhi_update_push_testing subject_type: koji_build rules: - !PassingTestCaseRule {test_case_name: fedora-ci.koji-build.tier0.functional} --- !Policy product_versions: - fedora-* decision_context: bodhi_update_push_stable subject_type: koji_build rules: - !PassingTestCaseRule {test_case_name: fedora-ci.koji-build.tier0.functional}	--- !Policy product_versions: - fedora-* decision_context: bodhi_update_push_testing subject_type: koji_build rules: - !PassingTestCaseRule {test_case_name: fedora-ci.koji-build.tier0.functional} --- !Policy product_versions: - fedora-* decision_context: bodhi_update_push_stable subject_type: koji_build rules: - !PassingTestCaseRule {test_case_name: fedora-ci.koji-build.tier0.functional}
	Basically, it contains two policies, one to push a build to testing and one to push a build to stable and for both of these situations, it asks that the test named `org.centos.prod.ci.pipeline.allpackages-build.complete` passes.	Básicamente, contiene dos políticas, una para enviar una compilación a prueba y otra para enviar una compilación a estable y, para ambas situaciones, solicita que se pase la prueba `org.centos.prod.ci.pipeline.allpackages-build.complete`.
	For gating rawhide itself, you only need the `decision_context: bodhi_update_push_stable`, while for stable branches, you will need both.	Para gating rawhide mismo, usted necesita `decision_context: bodhi_update_push_stable`, mientras que para las ramas estable, necesitará ambas.
	If gating on your package-level tests is all you are interested in, you can use this example as is.	Si lo único que le interesa es controlas sus pruebas a nivel paquete, puede usar este ejemplo tal como está.
	If you are also interested in some of the Taskotron checks, such as `dist.python-versions` or `dist.python-versions.py3_support`, you could amend the file so it looks like:	Si usted está interesado en algunas de las verificaciones Taskotron, como `dist.python-versions` o `dist.python-versions.py3_support`, usted podría modificar el archivo para que se vea así:
	--- !Policy product_versions: - fedora-* decision_context: bodhi_update_push_testing subject_type: koji_build rules: - !PassingTestCaseRule {test_case_name: fedora-ci.koji-build.tier0.functional} - !PassingTestCaseRule {test_case_name: dist.python-versions} - !PassingTestCaseRule {test_case_name: dist.python-versions.py3_support} --- !Policy product_versions: - fedora-* decision_context: bodhi_update_push_stable subject_type: koji_build rules: - !PassingTestCaseRule {test_case_name: fedora-ci.koji-build.tier0.functional} - !PassingTestCaseRule {test_case_name: dist.python-versions} - !PassingTestCaseRule {test_case_name: dist.python-versions.py3_support}	--- !Policy product_versions: - fedora-* decision_context: bodhi_update_push_testing subject_type: koji_build rules: - !PassingTestCaseRule {test_case_name: fedora-ci.koji-build.tier0.functional} - !PassingTestCaseRule {test_case_name: dist.python-versions} - !PassingTestCaseRule {test_case_name: dist.python-versions.py3_support} --- !Policy product_versions: - fedora-* decision_context: bodhi_update_push_stable subject_type: koji_build rules: - !PassingTestCaseRule {test_case_name: fedora-ci.koji-build.tier0.functional} - !PassingTestCaseRule {test_case_name: dist.python-versions} - !PassingTestCaseRule {test_case_name: dist.python-versions.py3_support}
	You can find more about this file in Greenwave’s documentation about link:https://docs.pagure.org/greenwave/package-specific-policies.html[package specific policies].	Puede encontrar más información sobre este archivo en la documentación de Greenwave sobre https://docs.pagure.org/greenwave/package-specific-policies.html[políticas específicas de paquete].

Loading…

vareli

Translation added

English

Spanish 399 characters edited Current translation Translated

3 months ago

None

String updated in the repository

English

Spanish 0 characters edited Empty

9 months ago

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Spanish
No related strings found in the glossary.

String information

Source string description

type: delimited block -

Flags

no-wrap

Source string location

./pages/optin.adoc:56

String age

9 months ago

Last updated

3 months ago

Source string age

4 years ago

Translation file

po/es/master/pages/optin.po, string 14

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.