Octomerger Bot
@@ -25,7 +25,7 @@ Para acceder a tu tablero personal una vez que has iniciado sesión, haz clic en
|
||||
|
||||
## Encontrar tu actividad reciente
|
||||
|
||||
En la sección "Recent activity" (Actividad reciente) de tus noticias, rápidamente puedes encontrar las propuestas y solicitudes de extracción recién actualizadas en las que estás trabajando y hacerles el seguimiento. En "Recent activity" (Actividad reciente), puedes previsualizar hasta 12 actualizaciones recientes, realizadas durante las últimas dos semanas.
|
||||
En la sección "Recent activity" (Actividad reciente) de tus noticias, rápidamente puedes encontrar las propuestas y solicitudes de extracción recién actualizadas en las que estás trabajando y hacerles el seguimiento. En "Recent activity" (Actividad reciente), puedes previsualizar hasta 4 actualizaciones recientes, realizadas durante las últimas dos semanas.
|
||||
|
||||
{% data reusables.dashboard.recent-activity-qualifying-events %}
|
||||
|
||||
|
||||
@@ -20,14 +20,6 @@ You may want to use a dark theme to reduce power consumption on certain devices,
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
|
||||
@@ -65,7 +65,7 @@ Los siguientes ejemplos demuestran el uso de la acción `fwal/setup-swift`.
|
||||
|
||||
### Utilizar versiones múltiples de Swift
|
||||
|
||||
Puedes configurar tu job para que utilice versiones múltiples de Swift en una matriz de compilación.
|
||||
You can configure your job to use multiple versions of Swift in a matrix.
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
@@ -23,7 +23,7 @@ miniTocMaxHeadingLevel: 3
|
||||
|
||||
Contexts are a way to access information about workflow runs, runner environments, jobs, and steps. Each context is an object that contains properties, which can be strings or other objects.
|
||||
|
||||
{% data reusables.actions.context-contents %} For example, the `matrix` context is only populated for jobs in a [build matrix](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
|
||||
{% data reusables.actions.context-contents %} For example, the `matrix` context is only populated for jobs in a [matrix](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
|
||||
|
||||
You can access contexts using the expression syntax. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
|
||||
|
||||
@@ -552,19 +552,19 @@ The following example contents of the `secrets` context shows the automatic `GIT
|
||||
|
||||
## `strategy` context
|
||||
|
||||
For workflows with a build matrix, the `strategy` context contains information about the matrix execution strategy for the current job.
|
||||
For workflows with a matrix, the `strategy` context contains information about the matrix execution strategy for the current job.
|
||||
|
||||
| Property name | Type | Description |
|
||||
|---------------|------|-------------|
|
||||
| `strategy` | `object` | This context changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains all the properties listed below. |
|
||||
| `strategy.fail-fast` | `string` | When `true`, all in-progress jobs are canceled if any job in a build matrix fails. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)." |
|
||||
| `strategy.job-index` | `string` | The index of the current job in the build matrix. **Note:** This number is a zero-based number. The first job's index in the build matrix is `0`. |
|
||||
| `strategy.job-total` | `string` | The total number of jobs in the build matrix. **Note:** This number **is not** a zero-based number. For example, for a build matrix with four jobs, the value of `job-total` is `4`. |
|
||||
| `strategy.fail-fast` | `string` | When `true`, all in-progress jobs are canceled if any job in a matrix fails. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)." |
|
||||
| `strategy.job-index` | `string` | The index of the current job in the matrix. **Note:** This number is a zero-based number. The first job's index in the matrix is `0`. |
|
||||
| `strategy.job-total` | `string` | The total number of jobs in the matrix. **Note:** This number **is not** a zero-based number. For example, for a matrix with four jobs, the value of `job-total` is `4`. |
|
||||
| `strategy.max-parallel` | `string` | The maximum number of jobs that can run simultaneously when using a `matrix` job strategy. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel)." |
|
||||
|
||||
### Example contents of the `strategy` context
|
||||
|
||||
The following example contents of the `strategy` context is from a build matrix with four jobs, and is taken from the final job. Note the difference between the zero-based `job-index` number, and `job-total` which is not zero-based.
|
||||
The following example contents of the `strategy` context is from a matrix with four jobs, and is taken from the final job. Note the difference between the zero-based `job-index` number, and `job-total` which is not zero-based.
|
||||
|
||||
```yaml
|
||||
{
|
||||
@@ -577,7 +577,7 @@ The following example contents of the `strategy` context is from a build matrix
|
||||
|
||||
### Example usage of the `strategy` context
|
||||
|
||||
This example workflow uses the `strategy.job-index` property to set a unique name for a log file for each job in a build matrix.
|
||||
This example workflow uses the `strategy.job-index` property to set a unique name for a log file for each job in a matrix.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Test matrix
|
||||
@@ -602,18 +602,18 @@ jobs:
|
||||
|
||||
## `matrix` context
|
||||
|
||||
For workflows with a build matrix, the `matrix` context contains the matrix properties defined in the workflow file that apply to the current job. For example, if you configure a build matrix with the `os` and `node` keys, the `matrix` context object includes the `os` and `node` properties with the values that are being used for the current job.
|
||||
For workflows with a matrix, the `matrix` context contains the matrix properties defined in the workflow file that apply to the current job. For example, if you configure a matrix with the `os` and `node` keys, the `matrix` context object includes the `os` and `node` properties with the values that are being used for the current job.
|
||||
|
||||
There are no standard properties in the `matrix` context, only those which are defined in the workflow file.
|
||||
|
||||
| Property name | Type | Description |
|
||||
|---------------|------|-------------|
|
||||
| `matrix` | `object` | This context is only available for jobs in a build matrix, and changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains the properties listed below. |
|
||||
| `matrix` | `object` | This context is only available for jobs in a matrix, and changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains the properties listed below. |
|
||||
| `matrix.<property_name>` | `string` | The value of a matrix property. |
|
||||
|
||||
### Example contents of the `matrix` context
|
||||
|
||||
The following example contents of the `matrix` context is from a job in a build matrix that has the `os` and `node` matrix properties defined in the workflow. The job is executing the matrix combination of an `ubuntu-latest` OS and Node.js version `16`.
|
||||
The following example contents of the `matrix` context is from a job in a matrix that has the `os` and `node` matrix properties defined in the workflow. The job is executing the matrix combination of an `ubuntu-latest` OS and Node.js version `16`.
|
||||
|
||||
```yaml
|
||||
{
|
||||
@@ -624,7 +624,7 @@ The following example contents of the `matrix` context is from a job in a build
|
||||
|
||||
### Example usage of the `matrix` context
|
||||
|
||||
This example workflow creates a build matrix with `os` and `node` keys. It uses the `matrix.os` property to set the runner type for each job, and uses the `matrix.node` property to set the Node.js version for each job.
|
||||
This example workflow creates a matrix with `os` and `node` keys. It uses the `matrix.os` property to set the runner type for each job, and uses the `matrix.node` property to set the Node.js version for each job.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Test matrix
|
||||
|
||||
@@ -50,7 +50,7 @@ Tanto CircleCI como {% data variables.product.prodname_actions %} configuran `jo
|
||||
|
||||
Tanto CircleCI como {% data variables.product.prodname_actions %} proporcionan un mecanismo para reutilizar y compartir tareas en un flujo de trabajo. CircleCi utiliza un concepto llamado orbes (orbs), escrito en YAML, que proporciona tareas que las personas pueden reutilizar en un flujo de trabajo. {% data variables.product.prodname_actions %} cuenta con componentes reutilizables poderosos y flexibles llamados acciones (actions), los cuales compilas ya sea con archivos de JavaScript o con imagenes de Docker. Puedes crear acciones si escribes tu código personalizado para que interactúe con tu repositorio en la forma que prefieras, lo cual incluye la integración con las API de {% data variables.product.product_name %} y con cualquier API de terceros disponible públicamente. Por ejemplo, una acción puede publicar módulos npm, enviar alertas por SMS cuando se crean propuestas urgentes o implementar un código listo para producción. Para obtener más información, consulta la sección "[Crear acciones](/actions/creating-actions)".
|
||||
|
||||
Circle CI puede reutilizar partes de los flujos de trabajo con anclas y alias. {% data variables.product.prodname_actions %} es compatible con las necesidades de reutilización más comunes utilizando matrices de compilación. Para obtener más información acerca de las matrices de compilación, consulta la sección "[Administrar flujos de trabajo complejos](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)".
|
||||
Circle CI puede reutilizar partes de los flujos de trabajo con anclas y alias. {% data variables.product.prodname_actions %} supports the most common need for reusability using matrices. For more information about matrices, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
## Utilizar imágenes de Docker
|
||||
|
||||
|
||||
@@ -83,9 +83,9 @@ Jenkins puede ejecutar las `stages` y `steps` en paralelo, mientras que, actualm
|
||||
| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [`parallel`](https://jenkins.io/doc/book/pipeline/syntax/#parallel) | [`jobs.<job_id>.strategy.max-parallel`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel) |
|
||||
|
||||
### Matriz de compilaciones
|
||||
### Matrix
|
||||
|
||||
Tanto {% data variables.product.prodname_actions %} como Jenkins te permiten utilizar una matriz de compilaciones para definir diversas combinaciones de sistema.
|
||||
Both {% data variables.product.prodname_actions %} and Jenkins let you use a matrix to define various system combinations.
|
||||
|
||||
| Jenkins | {% data variables.product.prodname_actions %}
|
||||
| ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
|
||||
@@ -59,9 +59,9 @@ Travis CI puede utilizar `stages` para ejecutar jobs en paralelo. De forma simil
|
||||
|
||||
Tanto Travis CI como {% data variables.product.prodname_actions %} son compatibles con las insignias de estado, lo cual te permite indicar si una compilación pasa o falla. Para obtener más información, consulta la sección "[Agregar una insignia de estado de un flujo de trabajo a tu repositorio](/actions/managing-workflow-runs/adding-a-workflow-status-badge)".
|
||||
|
||||
### Utilizar una matriz de compilaciones
|
||||
### Using a matrix
|
||||
|
||||
Tanto Travis CI como {% data variables.product.prodname_actions %} son compatibles con matrices de compilación, lo cual te permite realizar pruebas utilizando combinaciones de sistemas operativos y paquetes de software. Para obtener más información, consulta "[Utilizar una matriz de compilaciones](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)".
|
||||
Travis CI and {% data variables.product.prodname_actions %} both support a matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
A continuación podrás encontrar un ejemplo que compara la sintaxis para cada sistema:
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ children:
|
||||
- /using-jobs-in-a-workflow
|
||||
- /choosing-the-runner-for-a-job
|
||||
- /using-conditions-to-control-job-execution
|
||||
- /using-a-build-matrix-for-your-jobs
|
||||
- /using-a-matrix-for-your-jobs
|
||||
- /using-concurrency
|
||||
- /using-environments-for-jobs
|
||||
- /running-jobs-in-a-container
|
||||
|
||||
@@ -1,30 +0,0 @@
|
||||
---
|
||||
title: Utilizar una matriz de compilación para tus jobs
|
||||
shortTitle: Utilizar una matriz de compilación para tus jobs
|
||||
intro: Crear una matriz de compilación y definir las variaciones para cada job.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
miniTocMaxHeadingLevel: 4
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Resumen
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-strategy %}
|
||||
|
||||
## Crear una matriz de varias configuraciones de job diferentes
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-matrix %}
|
||||
|
||||
## Cncelar los jobs restantes si falla un job de `matrix`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-failfast %}
|
||||
|
||||
## Definir la cantidad máxima de jobs simultáneos en una `matrix`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-max-parallel %}
|
||||
@@ -0,0 +1,60 @@
|
||||
---
|
||||
title: Using a matrix for your jobs
|
||||
shortTitle: Using a matrix
|
||||
intro: Create a matrix to define variations for each job.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
miniTocMaxHeadingLevel: 4
|
||||
redirect_from:
|
||||
- /actions/using-jobs/using-a-build-matrix-for-your-jobs
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## About matrix strategies
|
||||
|
||||
{% data reusables.actions.jobs.about-matrix-strategy %}
|
||||
|
||||
## Using a matrix strategy
|
||||
|
||||
{% data reusables.actions.jobs.using-matrix-strategy %}
|
||||
|
||||
### Example: Using a single-dimension matrix
|
||||
|
||||
{% data reusables.actions.jobs.single-dimension-matrix %}
|
||||
|
||||
### Example: Using a multi-dimension matrix
|
||||
|
||||
{% data reusables.actions.jobs.multi-dimension-matrix %}
|
||||
|
||||
### Example: Using contexts to create matrices
|
||||
|
||||
{% data reusables.actions.jobs.matrix-from-context %}
|
||||
|
||||
## Expanding or adding matrix configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-include %}
|
||||
|
||||
### Example: Expanding configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-expand-with-include %}
|
||||
|
||||
### Example: Adding configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-add-with-include %}
|
||||
|
||||
## Excluding matrix configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-exclude %}
|
||||
|
||||
## Handling failures
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-failfast %}
|
||||
|
||||
## Defining the maximum number of concurrent jobs
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-max-parallel %}
|
||||
@@ -105,9 +105,9 @@ jobs:
|
||||
|
||||
Para obtener más información, consulta la sección "[Definir los jobs de prerrequisito](/actions/using-jobs/using-jobs-in-a-workflow#defining-prerequisite-jobs)".
|
||||
|
||||
### Utilizar una matriz de compilaciones
|
||||
### Using a matrix
|
||||
|
||||
You can use a build matrix if you want your workflow to run tests across multiple combinations of parameters, such as operating systems, platforms, and languages. La matriz de compilaciones se crea utilizando la palabra clave `strategy`, la cual recibe las opciones de compilación como un arreglo. Por ejemplo, esta matriz de compilaciones ejecutará el job varias veces, utilizando diferentes versiones de Node.js:
|
||||
{% data reusables.actions.jobs.about-matrix-strategy %} The matrix is created using the `strategy` keyword, which receives the build options as an array. For example, this matrix will run the job multiple times, using different versions of Node.js:
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
@@ -115,14 +115,14 @@ jobs:
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
node: [6, 8, 10]
|
||||
node: [12, 14, 16]
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.node }}{% endraw %}
|
||||
```
|
||||
|
||||
Para obtener más información, consulte la sección "[Utilizar una matriz de compilación para tus jobs](/actions/using-jobs/using-a-build-matrix-for-your-jobs)".
|
||||
For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### Almacenar dependencias en caché
|
||||
|
||||
@@ -745,11 +745,39 @@ If the timeout exceeds the job execution time limit for the runner, the job will
|
||||
|
||||
## `jobs.<job_id>.strategy`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-strategy %}
|
||||
Use `jobs.<job_id>.strategy` to use a matrix strategy for your jobs. {% data reusables.actions.jobs.about-matrix-strategy %} For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
### `jobs.<job_id>.strategy.matrix`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-matrix %}
|
||||
{% data reusables.actions.jobs.using-matrix-strategy %}
|
||||
|
||||
#### Example: Using a single-dimension matrix
|
||||
|
||||
{% data reusables.actions.jobs.single-dimension-matrix %}
|
||||
|
||||
#### Example: Using a multi-dimension matrix
|
||||
|
||||
{% data reusables.actions.jobs.multi-dimension-matrix %}
|
||||
|
||||
#### Example: Using contexts to create matrices
|
||||
|
||||
{% data reusables.actions.jobs.matrix-from-context %}
|
||||
|
||||
### `jobs.<job_id>.strategy.matrix.include`
|
||||
|
||||
{% data reusables.actions.jobs.matrix-include %}
|
||||
|
||||
#### Example: Expanding configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-expand-with-include %}
|
||||
|
||||
#### Example: Adding configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-add-with-include %}
|
||||
|
||||
### `jobs.<job_id>.strategy.matrix.exclude`
|
||||
|
||||
{% data reusables.actions.jobs.matrix-exclude %}
|
||||
|
||||
### `jobs.<job_id>.strategy.fail-fast`
|
||||
|
||||
|
||||
@@ -32,6 +32,12 @@ Antes de que puedas habilitar y configurar el {% data variables.product.prodname
|
||||
{% data reusables.package_registry.enable-enterprise-github-packages %}
|
||||
1. Debajo de "Almacenamiento de Packages", selecciona **Azure Blob Storage** e ingresa el nombre de tu contenedor de Azure para tu bucket de almacenamiento de paquetes y secuencia de conexión. 
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account. Usage of a SAS Token or SAS URL as connection string is not currently supported.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
## Pasos siguientes
|
||||
|
||||
@@ -208,7 +208,7 @@ If this parameter is not used, the {% data variables.product.prodname_codeql_wor
|
||||
|
||||
{% data reusables.code-scanning.codeql-languages-bullets %}
|
||||
|
||||
The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
|
||||
The default {% data variables.product.prodname_codeql_workflow %} file contains a matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about matrices, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
{% data reusables.code-scanning.specify-language-to-analyze %}
|
||||
|
||||
|
||||
@@ -68,7 +68,7 @@ Si una compilación automática de código para un lenguaje compilado dentro de
|
||||
|
||||
- Elimina el paso de `autobuild` de tu flujo de trabajo de {% data variables.product.prodname_code_scanning %} y agrega los pasos de compilación específicos. Para obtener información sobre cómo editar el flujo de trabajo, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)". Para obtener más información sobre cómo reemplazar el paso de `autobuild`, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)".
|
||||
|
||||
- Si tu flujo de trabajo no especifica explícitamente los lenguajes a analizar, {% data variables.product.prodname_codeql %} detectará implícitamente los lenguajes compatibles en tu código base. En esta configuración, fuera de los lenguajes compilados C/C++, C#, y Java, {% data variables.product.prodname_codeql %} solo analizará el lenguaje presente en la mayoría de los archivos de origen. Edita el flujo de trabajo y agrega una matriz de compilación que especifique los lenguajes que quieres analizar. El flujo de análisis predeterminado de CodeQL utiliza dicha matriz.
|
||||
- Si tu flujo de trabajo no especifica explícitamente los lenguajes a analizar, {% data variables.product.prodname_codeql %} detectará implícitamente los lenguajes compatibles en tu código base. En esta configuración, fuera de los lenguajes compilados C/C++, C#, y Java, {% data variables.product.prodname_codeql %} solo analizará el lenguaje presente en la mayoría de los archivos de origen. Edit the workflow and add a matrix specifying the languages you want to analyze. El flujo de análisis predeterminado de CodeQL utiliza dicha matriz.
|
||||
|
||||
Los siguientes extractos de un flujo de trabajo te muestran cómo puedes utilizar una matriz dentro de la estrategia del job para especificar lenguajes, y luego hace referencia a cada uno de ellos con el paso de "Inicializar {% data variables.product.prodname_codeql %}":
|
||||
|
||||
@@ -188,7 +188,7 @@ Si utilizas ejecutores auto-hospedados para ejecutar el análisis de {% data var
|
||||
|
||||
### Utilizar matrices de compilación para paralelizar el análisis
|
||||
|
||||
El {% data variables.product.prodname_codeql_workflow %} predeterminado utiliza una matriz de lenguajes, la cual causa que el análisis de cada uno de ellos se ejecute en paralelo. Si especificaste los lenguajes que quieres analizar directamente en el paso de "Inicializar CodeQL", el análisis de cada lenguaje ocurrirá de forma secuencial. Para agilizar el análisis de lenguajes múltiples, modifica tu flujo de trabajo para utilizar una matriz. Para obtener más información, consulta el extracto de flujo de trabajo en la sección "[Compilación automática para los fallos de un lenguaje compilado](#automatic-build-for-a-compiled-language-fails)" que se trata anteriormente.
|
||||
The default {% data variables.product.prodname_codeql_workflow %} uses a matrix of languages, which causes the analysis of each language to run in parallel. Si especificaste los lenguajes que quieres analizar directamente en el paso de "Inicializar CodeQL", el análisis de cada lenguaje ocurrirá de forma secuencial. Para agilizar el análisis de lenguajes múltiples, modifica tu flujo de trabajo para utilizar una matriz. Para obtener más información, consulta el extracto de flujo de trabajo en la sección "[Compilación automática para los fallos de un lenguaje compilado](#automatic-build-for-a-compiled-language-fails)" que se trata anteriormente.
|
||||
|
||||
### Reducir la cantidad de código que se está analizando en un solo flujo de trabajo
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ shortTitle: Learning resources
|
||||
---
|
||||
## Using Git
|
||||
|
||||
Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can review the [Git command list](https://git-scm.com/docs) or [Git command lookup reference](http://gitref.org) while using the [Try Git](https://try.github.com) simulator.
|
||||
Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can also review the [Git command list](https://git-scm.com/docs).
|
||||
|
||||
## Using {% data variables.product.product_name %}
|
||||
|
||||
|
||||
@@ -23,6 +23,7 @@ permissions: Organization owners can remove members from an organization.
|
||||
**Advertencia:** Cuando eliminas a algún miembro de una organización:
|
||||
- La cuenta de licencias pagadas no baja de categoría automáticamente. Para pagar por menos licencias después de eliminar usuarios de tu organización, sigue los pasos de la sección "[Bajar el cupo límite de plazas pagadas en tu organización](/articles/downgrading-your-organization-s-paid-seats)".
|
||||
- Los miembros eliminados perderán el acceso a las bifurcaciones privadas de los repositorios privados de tu organización, pero aún podrían tener copias locales de estas. Sin embargo, no pueden sincronizar las copias locales con tus repositorios de la organización. Se pueden restaurar las bifurcaciones privadas del usuario si se lo reinstala [como miembro de la organización](/articles/reinstating-a-former-member-of-your-organization) dentro de los tres meses posteriores a haber sido eliminado de la organización. En última instancia, tú eres el responsable de asegurar que las personas que perdieron acceso a un repositorio borren cualquier información confidencial o propiedad intelectual.
|
||||
- When private repositories are forked to other organizations, those organizations are able to control access to the fork network. This means users may retain access to the forks even after losing access to the original organization because they will still have explicit access via a fork.
|
||||
{%- ifversion ghec %}
|
||||
- Los miembros eliminados también perderán acceso a las bifurcaciones privadas de los repositorios internos de tu organización en caso de que el miembro eliminado no es miembro de alguna otra organización que le pertenezca a la misma cuenta empresarial. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)".
|
||||
{%- endif %}
|
||||
|
||||
@@ -13,7 +13,6 @@ sections:
|
||||
- 'Cuando conviertes una cuenta de usuario en una organización, si dicha cuenta fue propietaria de la cuenta empresarial de {% data variables.product.prodname_ghe_server %}, la organización convertida se mostró incorrectamente en la lista de propietarios de la empresa.'
|
||||
- 'The `/stafftools/users/ip_addresses/:address` page responded with a `500 Internal Server Error` when attempting to display the page for an IPv6 address.'
|
||||
- 'El crear un token de OAuth de personificación utilizando la API de REST de administración de empresas dio como resultado un error cuando una integración que coincidió con la ID de aplicación de OAuth ya existía.'
|
||||
- "Cuando utilizas las aserciones cifradas con {% data variables.product.prodname_ghe_server %} 3.4.0 y 3.4.1, un atributo nuevo de XML `WantAssertionsEncrypted` en el `SPSSODescriptor` contiene un atributo inválido para los metadatos de SAML. Los IdP que consumen esta terminal de metadatos de SAML podrían encontrar errores al validar el modelo XML de los metadatos de SAML. Habrá una corrección disponible en el siguiente lanzamiento de parche. [Actualizado: 2022-04-11]\n\nPara darle una solución a este problema, puedes tomar una de las dos acciones siguientes.\n- Reconfigurar el IdP cargando una copia estática de los metadatos de SAML sin el atributo `WantAssertionsEncrypted`.\n- Copiar los metadatos de SAML, eliminar el atributo `WantAssertionsEncrypted`, hospedarlo en un servidor web y reconfigurar el IdP para que apunte a esa URL.\n"
|
||||
changes:
|
||||
- 'Added support for replica domain names that are more than 63 characters.'
|
||||
- 'Los errores de configuración que detienen una ejecución de aplicación de configuraciones ahora son el producto de la terminal adicionalmente a la bitácora de configuración.'
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
A matrix strategy lets you use variables in a single job definition to automatically create multiple job runs that are based the combinations of the variables. For example, you can use a matrix strategy to test your code in multiple versions of a language or on multiple operating systems.
|
||||
@@ -0,0 +1,29 @@
|
||||
For example, this matrix will run 10 jobs, one for each combination of `os` and `version` in the matrix, plus a job for the `os` value of `windows-latest` and `version` value of `17`.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
os: [macos-latest, windows-latest, ubuntu-latest]
|
||||
version: [12, 14, 16]
|
||||
include:
|
||||
- os: windows-latest
|
||||
version: 17
|
||||
```
|
||||
|
||||
If you don't specify any matrix variables, all configurations under `include` will run. For example, the following workflow would run two jobs, one for each `include` entry. This lets you take advantage of the matrix strategy without having a fully populated matrix.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
includes_only:
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
include:
|
||||
- site: "production"
|
||||
datacenter: "site-a"
|
||||
- site: "staging"
|
||||
datacenter: "site-b"
|
||||
|
||||
```
|
||||
@@ -0,0 +1,22 @@
|
||||
To remove specific configurations defined in the matrix, use `jobs.<job_id>.strategy.matrix.exclude`. An excluded configuration only has to be a partial match for it to be excluded. For example, the following workflow will run nine jobs: one job for each of the 12 configurations, minus the one excluded job that matches `{os: macos-latest, version: 12, environment: production}`, and the two excluded jobs that match `{os: windows-latest, version: 16}`.
|
||||
|
||||
```yaml
|
||||
strategy:
|
||||
matrix:
|
||||
os: [macos-latest, windows-latest]
|
||||
version: [12, 14, 16]
|
||||
environment: [staging, production]
|
||||
exclude:
|
||||
- os: macos-latest
|
||||
version: 12
|
||||
environment: production
|
||||
- os: windows-latest
|
||||
version: 16
|
||||
runs-on: {% raw %}${{ matrix.os }}{% endraw %}
|
||||
```
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Todas las combinaciones de `include` se procesan después de `exclude`. Esto te permite utilizar `include` para volver a agregar combinaciones que se excluyeron previamente.
|
||||
|
||||
{% endnote %}
|
||||
@@ -0,0 +1,22 @@
|
||||
For example, the following workflow will run six jobs, one for each combination of `os` and `node`. When the job for the `os` value of `windows-latest` and `node` value of `16` runs, an additional variable called `npm` with the value of `6` will be included in the job.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
os: [windows-latest, ubuntu-latest]
|
||||
node: [12, 14, 16]
|
||||
include:
|
||||
- os: windows-latest
|
||||
node: 16
|
||||
npm: 6
|
||||
runs-on: {% raw %}${{ matrix.os }}{% endraw %}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.node }}{% endraw %}
|
||||
- if: {% raw %}${{ matrix.npm }}{% endraw %}
|
||||
run: npm install -g npm@{% raw %}${{ matrix.npm }}{% endraw %}
|
||||
- run: npm --version
|
||||
```
|
||||
@@ -0,0 +1,30 @@
|
||||
You can use contexts to create matrices. Para obtener más información sobre los contextos, consulta la sección "[Contextos](/actions/learn-github-actions/contexts)".
|
||||
|
||||
For example, the following workflow triggers on the `repository_dispatch` event and uses information from the event payload to build the matrix. When a repository dispatch event is created with a payload like the one below, the matrix `version` variable will have a value of `[12, 14, 16]`. For more information about the `repository_dispatch` trigger, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows#repository_dispatch)."
|
||||
|
||||
```json
|
||||
{
|
||||
"event_type": "test",
|
||||
"client_payload": {
|
||||
"versions": [12, 14, 16]
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
```yaml
|
||||
on:
|
||||
repository_dispatch:
|
||||
types:
|
||||
- test
|
||||
|
||||
jobs:
|
||||
example_matrix:
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
version: {% raw %}${{ github.event.client_payload.versions }}{% endraw %}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.version }}{% endraw %}
|
||||
```
|
||||
@@ -0,0 +1,38 @@
|
||||
Use `jobs.<job_id>.strategy.matrix.include` to expand existing matrix configurations or to add new configurations. The value of `include` is a list of objects.
|
||||
|
||||
For each object in the `include` list, the key:value pairs in the object will be added to each of the matrix combinations if none of the key:value pairs overwrite any of the original matrix values. If the object cannot be added to any of the matrix combinations, a new matrix combination will be created instead. Note that the original matrix values will not be overwritten, but added matrix values can be overwritten.
|
||||
|
||||
For example, this matrix:
|
||||
|
||||
```yaml
|
||||
strategy:
|
||||
matrix:
|
||||
fruit: [apple, pear]
|
||||
animal: [cat, dog]
|
||||
include:
|
||||
- color: green
|
||||
- color: pink
|
||||
animal: cat
|
||||
- fruit: apple
|
||||
shape: circle
|
||||
- fruit: banana
|
||||
- fruit: banana
|
||||
animal: cat
|
||||
```
|
||||
|
||||
will result in six jobs with the following matrix combinations:
|
||||
|
||||
- `{fruit: apple, animal: cat, color: pink, shape: circle}`
|
||||
- `{fruit: apple, animal: dog, color: green, shape: circle}`
|
||||
- `{fruit: pear, animal: cat, color: pink}`
|
||||
- `{fruit: pear, animal: dog, color: green}`
|
||||
- `{fruit: banana}`
|
||||
- `{fruit: banana, animal: cat}`
|
||||
|
||||
following this logic:
|
||||
|
||||
- `{color: green}` is added to all of the original matrix combinations because it can be added without overwriting any part of the original combinations.
|
||||
- `{color: pink, animal: cat}` adds `color:pink` only to the original matrix combinations that include `animal: cat`. This overwrites the `color: green` that was added by the previous `include` entry.
|
||||
- `{fruit: apple, shape: circle}` adds `shape: circle` only to the original matrix combinations that include `fruit: apple`.
|
||||
- `{fruit: banana}` cannot be added to any original matrix combination without overwriting a value, so it is added as an additional matrix combination.
|
||||
- `{fruit: banana, animal: cat}` cannot be added to any original matrix combination without overwriting a value, so it is added as an additional matrix combination. It does not add to the `{fruit: banana}` matrix combination because that combination was not one of the original matrix combinations.
|
||||
@@ -0,0 +1,22 @@
|
||||
You can specify multiple variables to create a multi-dimensional matrix. A job will run for each possible combination of the variables.
|
||||
|
||||
For example, the following workflow specifies two variables:
|
||||
|
||||
- Two operating systems specified in the `os` variable
|
||||
- Three Node.js versions specified in the `version` variable
|
||||
|
||||
The workflow will run six jobs, one for each combination of the `os` and `version` variables. Each job will set the `runs-on` value to the current `os` value and will pass the current `version` value to the `actions/setup-node` action.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
os: [ubuntu-18.04, ubuntu-20.04]
|
||||
version: [10, 12, 14]
|
||||
runs-on: {% raw %}${{ matrix.os }}{% endraw %}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.version }}{% endraw %}
|
||||
```
|
||||
@@ -1 +1,23 @@
|
||||
When `jobs.<job_id>.strategy.fail-fast` is set to `true`, {% data variables.product.prodname_dotcom %} cancels all in-progress jobs in the matrix if any `matrix` job fails. Predeterminado: `true`
|
||||
You can control how job failures are handled with `jobs.<job_id>.strategy.fail-fast` and `jobs.<job_id>.continue-on-error`.
|
||||
|
||||
`jobs.<job_id>.strategy.fail-fast` applies to the entire matrix. If `jobs.<job_id>.strategy.fail-fast` is set to `true`, {% data variables.product.product_name %} will cancel all in-progress and queued jobs in the matrix if any job in the matrix fails. This property defaults to `true`.
|
||||
|
||||
`jobs.<job_id>.continue-on-error` applies to a single job. If `jobs.<job_id>.continue-on-error` is `true`, other jobs in the matrix will continue running even if the job with `jobs.<job_id>.continue-on-error: true` fails.
|
||||
|
||||
You can use `jobs.<job_id>.strategy.fail-fast` and `jobs.<job_id>.continue-on-error` together. For example, the following workflow will start four jobs. For each job, `continue-on-error` is determined by the value of `matrix.experimental`. If any of the jobs with `continue-on-error: false` fail, all jobs that are in progress or queued will be cancelled. If the job with `continue-on-error: true` fails, the other jobs will not be affected.
|
||||
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
test:
|
||||
runs-on: ubuntu-latest
|
||||
continue-on-error: {% raw %}${{ matrix.experimental }}{% endraw %}
|
||||
strategy:
|
||||
fail-fast: true
|
||||
matrix:
|
||||
version: [6, 7, 8]
|
||||
experimental: [false]
|
||||
include:
|
||||
- version: 9
|
||||
experimental: true
|
||||
```
|
||||
|
||||
@@ -1,122 +0,0 @@
|
||||
|
||||
Utiliza `jobs.<job_id>.strategy.matrix` para definir una matriz de configuraciones de jobs diferentes. Una matriz te permite crear múltiples trabajos realizando la sustitución de variables en una definición de trabajo único. Por ejemplo, puedes usar una matriz para crear trabajos para más de una versión compatible de un lenguaje de programación, sistema operativo o herramienta. Una matriz reutiliza la configuración del trabajo y crea un trabajo para cada matriz que configuras.
|
||||
|
||||
{% data reusables.actions.usage-matrix-limits %}
|
||||
|
||||
Cada opción que definas en la `matriz` tiene una clave y un valor. Las claves que defines se convierten en propiedades en el contexto `matriz` y puedes hacer referencia a la propiedad en otras áreas de tu archivo de flujo de trabajo. Por ejemplo, si defines la clave `os` que contiene una matriz de sistemas operativos, puedes usar la propiedad `matrix.os` como el valor de la palabra clave `runs-on` para crear un trabajo para cada sistema operativo. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts)".
|
||||
|
||||
El orden en que defines una `matriz` importa. La primera opción que definas será el primer trabajo que se ejecuta en tu flujo de trabajo.
|
||||
|
||||
#### Ejemplo: Ejecutando versiones múltiples de Node.js
|
||||
|
||||
Puedes especificar una matriz proporcionando una variedad de opciones de configuración. Por ejemplo, si el ejecutor admite las versiones 10, 12 y 14 de Node.js, puedes especificar una matriz de esas versiones en la `matriz`.
|
||||
|
||||
Este ejemplo crea una matriz de tres trabajos estableciendo la clave `node` para una matriz de tres versiones de Node.js. Para usar la matriz, el ejemplo establece la propiedad de contexto `matrix.node` como el valor del parámetro `node-version` de la entrada de la acción `setup-node`. Como resultado, se ejecutarán tres trabajos, cada uno usando una versión diferente de Node.js.
|
||||
|
||||
```yaml
|
||||
strategy:
|
||||
matrix:
|
||||
node: [10, 12, 14]
|
||||
steps:
|
||||
# Configures the node version used on GitHub-hosted runners
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
# The Node.js version to configure
|
||||
node-version: {% raw %}${{ matrix.node }}{% endraw %}
|
||||
```
|
||||
|
||||
La acción `setup-node` es la forma recomendada de configurar una versión de Node.js cuando se usan ejecutores alojados {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la acción [`setup-node`](https://github.com/actions/setup-node).
|
||||
|
||||
#### Ejemplo: Ejecutando sistemas operativos múltiples
|
||||
|
||||
Puedes crear una matriz para ejecutar flujos de trabajo en más de un sistema operativo del ejecutor. También puedes especificar más de una configuración de matriz. Este ejemplo crea una matriz de 6 trabajos:
|
||||
|
||||
- 2 sistemas operativos especificados en la matriz `os`
|
||||
- 3 versiones de Node.js especificadas en la matriz `node`
|
||||
|
||||
{% data reusables.repositories.actions-matrix-builds-os %}
|
||||
|
||||
```yaml
|
||||
runs-on: {% raw %}${{ matrix.os }}{% endraw %}
|
||||
strategy:
|
||||
matrix:
|
||||
os: [ubuntu-18.04, ubuntu-20.04]
|
||||
node: [10, 12, 14]
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.node }}{% endraw %}
|
||||
```
|
||||
|
||||
{% ifversion ghae %}
|
||||
Para obtener más información acerca de la configuración de los ejecutores auto-hospedados, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)".
|
||||
{% else %}Para encontrar las opciones de la configuración compatible para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección "[Ambientes virtuales para los ejecutores hospedados en {% data variables.product.prodname_dotcom %}](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)".
|
||||
{% endif %}
|
||||
|
||||
#### Ejemplo: Incluir valores adicionales en las combinaciones
|
||||
|
||||
Puedes agregar más opciones de configuración a un trabajo de una matriz de construcción ya existente. Por ejemplo, si quieres usar una versión específica de `npm` cuando se ejecuta el trabajo que usa `windows-latest` y la versión 8 de `node`, puedes usar `incluir` para especificar esa opción adicional.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
runs-on: ${{ matrix.os }}
|
||||
strategy:
|
||||
matrix:
|
||||
os: [macos-latest, windows-latest, ubuntu-18.04]
|
||||
node: [8, 10, 12, 14]
|
||||
include:
|
||||
# includes a new variable of npm with a value of 6
|
||||
# for the matrix leg matching the os and version
|
||||
- os: windows-latest
|
||||
node: 8
|
||||
npm: 6
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
#### Ejemplo: Incluyendo combinaciones nuevas
|
||||
|
||||
Puedes utilizar `include` para agregar jobs nuevos a una matriz de compilaciones. Cualquier configuración de "include" sin coincidencia exacta e agregará a la matriz. Por ejemplo, si quieres utilizar `node` versión 14 para compilar en varios sistemas operativos, pero quieres un job experimental extra que utilice node versión 15 en Ubintu, puedes utilizar `include` para especificar este job adicional.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
runs-on: ${{ matrix.os }}
|
||||
strategy:
|
||||
matrix:
|
||||
node: [14]
|
||||
os: [macos-latest, windows-latest, ubuntu-18.04]
|
||||
include:
|
||||
- node: 15
|
||||
os: ubuntu-18.04
|
||||
experimental: true
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
#### Ejemplo: Excluyendo las configuraciones de una matriz
|
||||
|
||||
Puedes eliminar una configuración específica definida en la matriz de construcción mediante la opción `exclude`. Si usas `exclude`, se elimina un puesto definido por la matriz de construcción. El número de puestos es el producto cruzado de la cantidad de sistemas operativos (`os`) incluidos en las matrices que brindas, menos todas las sustracciones (`exclude`).
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
runs-on: ${{ matrix.os }}
|
||||
strategy:
|
||||
matrix:
|
||||
os: [macos-latest, windows-latest, ubuntu-18.04]
|
||||
node: [8, 10, 12, 14]
|
||||
exclude:
|
||||
# excludes node 8 on macOS
|
||||
- os: macos-latest
|
||||
node: 8
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Nota:** Todas las combinaciones de `include` se procesan después de `exclude`. Esto te permite utilizar `include` para volver a agregar combinaciones que se excluyeron previamente.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Utilizar variables de ambiente en una matriz
|
||||
|
||||
Puedes agregar variables de ambiente personalizadas para cada combinación de prueba si utilizas la clave `include`. Posteriormente, puedes referirte a las variables de ambiente personalizadas en un paso subsecuente.
|
||||
|
||||
{% data reusables.actions.matrix-variable-example %}
|
||||
@@ -1,6 +1,13 @@
|
||||
Use `jobs.<job_id>.strategy.max-parallel` to set the maximum number of jobs that can run simultaneously when using a `matrix` job strategy. De manera predeterminada, {% data variables.product.prodname_dotcom %} maximizará el número de trabajos ejecutados en paralelo dependiendo de los ejecutadores disponibles en las máquinas virtuales alojadas en {% data variables.product.prodname_dotcom %}.
|
||||
By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. To set the maximum number of jobs that can run simultaneously when using a `matrix` job strategy, use `jobs.<job_id>.strategy.max-parallel`.
|
||||
|
||||
For example, the following workflow will run a maximum of two jobs at a time, even if there are runners available to run all six jobs at once.
|
||||
|
||||
```yaml
|
||||
strategy:
|
||||
max-parallel: 2
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
max-parallel: 2
|
||||
matrix:
|
||||
version: [10, 12, 14]
|
||||
os: [ubuntu-latest, windows-latest]
|
||||
```
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
Utiliza `jobs.<job_id>.strategy` para crear una matriz de compilación para tus jobs. Puedes definir variaciones diferentes para que ejecuten cada job.
|
||||
@@ -0,0 +1,15 @@
|
||||
You can specify a single variable to create a single-dimension matrix.
|
||||
|
||||
For example, the following workflow defines the variable `version` with the values `[10, 12, 14]`. The workflow will run three jobs, one for each value in the variable. Each job will access the `version` value through the `matrix.version` context and pass the value as `node-version` to the `actions/setup-node` action.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
version: [10, 12, 14]
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.version }}{% endraw %}
|
||||
```
|
||||
@@ -0,0 +1,25 @@
|
||||
Utiliza `jobs.<job_id>.strategy.matrix` para definir una matriz de configuraciones de jobs diferentes. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a veriable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`:
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
version: [10, 12, 14]
|
||||
os: [ubuntu-latest, windows-latest]
|
||||
```
|
||||
|
||||
A job will run for each possible combination of the variables. In this example, the workflow will run six jobs, one for each combination of the `os` and `version` variables.
|
||||
|
||||
By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. The order of the variables in the matrix determines the order in which the jobs are created. The first variable you define will be the first job that is created in your workflow run. For example, the above matrix will create the jobs in the following order:
|
||||
|
||||
- `{version: 10, os: ubuntu-latest}`
|
||||
- `{version: 10, os: windows-latest}`
|
||||
- `{version: 12, os: ubuntu-latest}`
|
||||
- `{version: 12, os: windows-latest}`
|
||||
- `{version: 14, os: ubuntu-latest}`
|
||||
- `{version: 14, os: windows-latest}`
|
||||
|
||||
A matrix will generate a maximum of 256 jobs per workflow run. This limit applies to both {% data variables.product.product_name %}-hosted and self-hosted runners.
|
||||
|
||||
The variables that you define become properties in the `matrix` context, and you can reference the property in other areas of your workflow file. In this example, you can use `matrix.version` and `matrix.os` to access the current value of `version` and `os` that the job is using. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts)".
|
||||
@@ -1 +0,0 @@
|
||||
Cuando defines una matriz de sistemas operativos, debes modificar el valor de `runs-on` a la propiedad de contexto de `matrix.os` que definiste.
|
||||
@@ -9,9 +9,9 @@ Adobe | Token de Servicio de Adobe | adobe_service_token{% endif %}
|
||||
Adobe | Token de Acceso de Duración Corta de Adobe | adobe_short_lived_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Adobe | Token Web de JSON de Adobe | adobe_jwt{% endif %} Alibaba Cloud | ID de Clave de Acceso de Alibaba Cloud | alibaba_cloud_access_key_id Alibaba Cloud | Secreto de Clave de Acceso de Alibaba Cloud | alibaba_cloud_access_key_secret
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Amazon | ID de Cliente OAuth de Amazon | amazon_oauth_client_id{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Amazon | Secreto de Cliente OAuth de Amazon | amazon_oauth_client_secret{% endif %} Amazon Web Services (AWS) | ID de Llave de Acceso a Amazon AWS | aws_access_key_id Amazon Web Services (AWS) | Llave de Acceso al Secreto de Amazon AWS | aws_secret_access_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
Amazon Web Services (AWS) | Token de Sesión de Amazon AWS | aws_session_token{% endif %}
|
||||
@@ -21,9 +21,9 @@ Amazon Web Services (AWS) | ID de Llave de Acceso Temporal de Amazon AWS | aws_t
|
||||
Asana | Token de Acceso Personal de Asana | asana_personal_access_token{% endif %} Atlassian | Token de la API de Atlassian | atlassian_api_token Atlassian | Token Web JSON de Atlassian | atlassian_jwt
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Atlassian | Token de Acceso Personal de Bitbucket Server | bitbucket_server_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Azure | Secreto de la Aplicación de Azure Active Directory | azure_active_directory_application_secret{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Azure | Llave del Caché de Azure para Redis | azure_cache_for_redis_access_key{% endif %} Azure | Token de Acceso Personal de Azure DevOps | azure_devops_personal_access_token Azure | Token de SAS de Azure | azure_sas_token Azure | Certificado de Azure Service Management | azure_management_certificate
|
||||
{%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %}
|
||||
Azure | Secuencia de Conexión SQL de Azure | azure_sql_connection_string{% endif %} Azure | Llave de Cuenta de Almacenamiento de Azure | azure_storage_account_key
|
||||
@@ -63,7 +63,7 @@ GitHub | Token de Acceso de OAuth de GitHub | github_oauth_access_token{% endif
|
||||
GitHub | Token de Actualización de GitHub | github_refresh_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
GitHub | Token de Acceso a la Instalación de GitHub App | github_app_installation_access_token{% endif %} GitHub | Llave Privada SSH de GitHub | github_ssh_private_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
GitLab | Token de Acceso a GitLab | gitlab_access_token{% endif %} GoCardless | Toekn de Acceso en Vivo a GoCardless | gocardless_live_access_token GoCardless | Token de Acceso de Prueba a GoCardless | gocardless_sandbox_access_token
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
Google | Llave del Servidor de Mensajería de Firebase Cloud | firebase_cloud_messaging_server_key{% endif %} Google | Llave de la API de Google | google_api_key Google | ID de Llave Privada de Google Cloud | google_cloud_private_key_id
|
||||
@@ -73,13 +73,13 @@ Google | Secreto de la Llave de Acceso de Almacenamiento de Google Cloud | googl
|
||||
Google | ID de la Llave de Acceso de la Cuenta de Servicio de Almacenamiento de Google Cloud | google_cloud_storage_service_account_access_key_id{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
Google | ID de la Llave de Acceso de Usuario de Almacenamiento de Google Cloud | google_cloud_storage_user_access_key_id{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Google | Token de Acceso OAuth a Google | google_oauth_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Google | ID de Cliente OAuth de Google | google_oauth_client_id{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Google | Secreto de Cliente OAuth de Google | google_oauth_client_secret{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Google | Token de Actualización OAuth a Google | google_oauth_refresh_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Grafana | Llave de la API de Grafana | grafana_api_key{% endif %} HashiCorp | Token de la API de Terraform Cloud / Enterprise | terraform_api_token HashiCorp | Token de Lote de HashiCorp Vault | hashicorp_vault_batch_token HashiCorp | Toekn de Servicio de HashiCorp Vault | hashicorp_vault_service_token Hubspot | Llave de la API de Hubspot | hubspot_api_key
|
||||
@@ -89,7 +89,7 @@ Intercom | Token de Acceso a Intercom | intercom_access_token{% endif %}
|
||||
Ionic | Token de Acceso Personal de Ionic | ionic_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Ionic | Token de Actualización de Ionic | ionic_refresh_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
JD Cloud | Llave de Acceso de JD Cloud | jd_cloud_access_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
JFrog | Token de Acceso a la Plataforma de JFrog | jfrog_platform_access_token{% endif %}
|
||||
@@ -103,15 +103,15 @@ Linear | Token de Acceso Oauth de Linear | linear_oauth_access_token{% endif %}
|
||||
Lob | Llave de la API en Vivo de Lob | lob_live_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Lob | Llave de la API de Pruebas de Lob | lob_test_api_key{% endif %} Mailchimp | Llave de la API de Mailchimp | mailchimp_api_key Mailgun | Llave de la API de Mailgun | mailgun_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Mapbox | Token de Acceso Secreto a Mapbox | mapbox_secret_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
MessageBird | Llave de la API de MessageBird | messagebird_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Meta | Token de Acceso a Facebook | facebook_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Midtrans | Llave del Servidor Productivo de Midtrans | midtrans_production_server_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Midtrans | Llave del Servidor de Pruebas de Midtrans | midtrans_sandbox_server_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
New Relic | Llave Personal de la API de New Relic | new_relic_personal_api_key{% endif %}
|
||||
@@ -121,11 +121,11 @@ New Relic | Llave de la API de REST de New Relic | new_relic_rest_api_key{% endi
|
||||
New Relic | Llave de Consulta de Perspectivas de New Relic | new_relic_insights_query_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
New Relic | Llave de Licencia de New Relic | new_relic_license_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Notion | Token de Integración a Notion | notion_integration_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Notion | Secreto de Cliente OAuth a Notion | notion_oauth_client_secret{% endif %} npm | Token de Acceso a npm | npm_access_token NuGet | Llave de la API de NuGet | nuget_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Octopus Deploy | Llave de la API de Despliegue de Octopus | octopus_deploy_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Onfido | Token de la API de Onfido Live | onfido_live_api_token{% endif %}
|
||||
@@ -147,7 +147,7 @@ Plivo | Token de Autenticación a Plivo | plivo_auth_token{% endif %} Postman |
|
||||
PyPI | Token de la API de PyPI | pypi_api_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
RubyGems | Llave de la API de RubyGems | rubygems_api_key{% endif %} Samsara | Token de la API de Samsara | samsara_api_token Samsara | Token de Acceso OAuth a Samsara | samsara_oauth_access_token
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
Segment | Token de la API Público de Segment | segment_public_api_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
SendGrid | Llave de la API de SendGrid | sendgrid_api_key{% endif %}
|
||||
@@ -159,36 +159,36 @@ Sendinblue | Llave de SMTP de Sendinblue | sendinblue_smtp_key{% endif %}
|
||||
Shippo | Token de la API de Shippo Live | shippo_live_api_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Shippo | Token de la API de Pruebas de Shippo | shippo_test_api_token{% endif %} Shopify | Secreto Compartido de la App de Shopify | shopify_app_shared_secret Shopify | Token de Acceso a Shopify | shopify_access_token Shopify | Token de Acceso a la App Personalizada de Shopify | shopify_custom_app_access_token Shopify | Contraseña de la App Privada de Shopify | shopify_private_app_password Slack | Token de la API de Slack | slack_api_token Slack | URL del Webhook Entrante de Slack | slack_incoming_webhook_url Slack | URL del Webhook del Flujo de Trabajo de Slack | slack_workflow_webhook_url
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Square | Token de Acceso a Square | square_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Square | Secreto de la Aplicación de Producción de Square | square_production_application_secret{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Square | Secreto de Aplicación de Pruebas de Square | square_sandbox_application_secret{% endif %} SSLMate | Llave de la API de SSLMate | sslmate_api_key SSLMate | Secreto de Clúster de SSLMate | sslmate_cluster_secret Stripe | Llave de la API de Stripe | stripe_api_key Stripe | Llave del Secreto de la API en Vivo de Stripe | stripe_live_secret_key Stripe | Llave del Secreto de la API de Pruebas de Stripe | stripe_test_secret_key Stripe | Llave Restringida de la API en Vivo de Stripe | stripe_live_restricted_key Stripe | Llave Restringida de la API de Pruebas de Stripe | stripe_test_restricted_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Stripe | Secreto de Firmado de Webhook de Stripe | stripe_webhook_signing_secret{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Supabase | Llave de Servicio de Supabase | supabase_service_key{% endif %} Tableau | Token de Acceso Personal a Tableau | tableau_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Telegram | Token del Bot de Telegram | telegram_bot_token{% endif %} Tencent Cloud | ID Secreta de Tencent Cloud | tencent_cloud_secret_id
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Twilio | Token de Acceso a Twilio | twilio_access_token{% endif %} Twilio | Identificador de Secuencia de Cuenta de Twilio | twilio_account_sid Twilio | Llave de la API de Twilio | twilio_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Typeform | Token de Acceso Personal a Typeform | typeform_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
WorkOS | Llave de la API de Producción de WorkOS Production | workos_production_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
WorkOS | Llave de la API de Pruebas de WorkOS | workos_staging_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Llave de la API de Yandex.Cloud | yandex_cloud_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Cookie IAM de Yandex.Cloud | yandex_cloud_iam_cookie{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Token IAM de Yandex.Cloud | yandex_cloud_iam_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Llave de la API de Yandex.Dictionary | yandex_dictionary_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Llave de la API de Yandex.Predictor | yandex_predictor_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Llave de la API de Yandex.Translate | yandex_translate_api_key{% endif %}
|
||||
|
||||
@@ -24,7 +24,7 @@ To access your personal dashboard once you're signed in, click the {% octicon "m
|
||||
|
||||
## Finding your recent activity
|
||||
|
||||
In the "Recent activity" section of your news feed, you can quickly find and follow up with recently updated issues and pull requests you're working on. Under "Recent activity", you can preview up to 12 recent updates made in the last two weeks.
|
||||
In the "Recent activity" section of your news feed, you can quickly find and follow up with recently updated issues and pull requests you're working on. Under "Recent activity", you can preview up to 4 recent updates made in the last two weeks.
|
||||
|
||||
{% data reusables.dashboard.recent-activity-qualifying-events %}
|
||||
|
||||
|
||||
@@ -20,14 +20,6 @@ You may want to use a dark theme to reduce power consumption on certain devices,
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
|
||||
@@ -65,7 +65,7 @@ jobs:
|
||||
|
||||
### 複数の Swift バージョンを使用する
|
||||
|
||||
ビルドマトリックスで Swift の複数のバージョンを使用するようにジョブを設定できます。
|
||||
You can configure your job to use multiple versions of Swift in a matrix.
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
@@ -23,7 +23,7 @@ miniTocMaxHeadingLevel: 3
|
||||
|
||||
コンテキストは、ワークフローの実行、ランナーの環境、ジョブ、ステップに関する情報にアクセスする方法です。 Each context is an object that contains properties, which can be strings or other objects.
|
||||
|
||||
{% data reusables.actions.context-contents %} For example, the `matrix` context is only populated for jobs in a [build matrix](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
|
||||
{% data reusables.actions.context-contents %} For example, the `matrix` context is only populated for jobs in a [matrix](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
|
||||
|
||||
You can access contexts using the expression syntax. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
|
||||
|
||||
@@ -537,19 +537,19 @@ The following example contents of the `secrets` context shows the automatic `GIT
|
||||
|
||||
## `strategy` context
|
||||
|
||||
For workflows with a build matrix, the `strategy` context contains information about the matrix execution strategy for the current job.
|
||||
For workflows with a matrix, the `strategy` context contains information about the matrix execution strategy for the current job.
|
||||
|
||||
| プロパティ名 | 種類 | 説明 |
|
||||
| ----------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `strategy` | `オブジェクト` | このコンテキストは、実行しているジョブごとに異なります。 You can access this context from any job or step in a workflow. This object contains all the properties listed below. |
|
||||
| `strategy.fail-fast` | `string` | When `true`, all in-progress jobs are canceled if any job in a build matrix fails. 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)」を参照してください。 |
|
||||
| `strategy.job-index` | `string` | The index of the current job in the build matrix. **Note:** This number is a zero-based number. The first job's index in the build matrix is `0`. |
|
||||
| `strategy.job-total` | `string` | The total number of jobs in the build matrix. **Note:** This number **is not** a zero-based number. For example, for a build matrix with four jobs, the value of `job-total` is `4`. |
|
||||
| `strategy.max-parallel` | `string` | `matrix`ジョブ戦略を使用するとき、同時に実行できるジョブの最大数。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel)」を参照してください。 |
|
||||
| プロパティ名 | 種類 | 説明 |
|
||||
| ----------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `strategy` | `オブジェクト` | このコンテキストは、実行しているジョブごとに異なります。 You can access this context from any job or step in a workflow. This object contains all the properties listed below. |
|
||||
| `strategy.fail-fast` | `string` | When `true`, all in-progress jobs are canceled if any job in a matrix fails. 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)」を参照してください。 |
|
||||
| `strategy.job-index` | `string` | The index of the current job in the matrix. **Note:** This number is a zero-based number. The first job's index in the matrix is `0`. |
|
||||
| `strategy.job-total` | `string` | The total number of jobs in the matrix. **Note:** This number **is not** a zero-based number. For example, for a matrix with four jobs, the value of `job-total` is `4`. |
|
||||
| `strategy.max-parallel` | `string` | `matrix`ジョブ戦略を使用するとき、同時に実行できるジョブの最大数。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel)」を参照してください。 |
|
||||
|
||||
### Example contents of the `strategy` context
|
||||
|
||||
The following example contents of the `strategy` context is from a build matrix with four jobs, and is taken from the final job. Note the difference between the zero-based `job-index` number, and `job-total` which is not zero-based.
|
||||
The following example contents of the `strategy` context is from a matrix with four jobs, and is taken from the final job. Note the difference between the zero-based `job-index` number, and `job-total` which is not zero-based.
|
||||
|
||||
```yaml
|
||||
{
|
||||
@@ -562,7 +562,7 @@ The following example contents of the `strategy` context is from a build matrix
|
||||
|
||||
### Example usage of the `strategy` context
|
||||
|
||||
This example workflow uses the `strategy.job-index` property to set a unique name for a log file for each job in a build matrix.
|
||||
This example workflow uses the `strategy.job-index` property to set a unique name for a log file for each job in a matrix.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Test matrix
|
||||
@@ -587,18 +587,18 @@ jobs:
|
||||
|
||||
## `matrix` context
|
||||
|
||||
For workflows with a build matrix, the `matrix` context contains the matrix properties defined in the workflow file that apply to the current job. For example, if you configure a build matrix with the `os` and `node` keys, the `matrix` context object includes the `os` and `node` properties with the values that are being used for the current job.
|
||||
For workflows with a matrix, the `matrix` context contains the matrix properties defined in the workflow file that apply to the current job. For example, if you configure a matrix with the `os` and `node` keys, the `matrix` context object includes the `os` and `node` properties with the values that are being used for the current job.
|
||||
|
||||
There are no standard properties in the `matrix` context, only those which are defined in the workflow file.
|
||||
|
||||
| プロパティ名 | 種類 | 説明 |
|
||||
| ------------------------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| `matrix` | `オブジェクト` | This context is only available for jobs in a build matrix, and changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains the properties listed below. |
|
||||
| `matrix.<property_name>` | `string` | The value of a matrix property. |
|
||||
| プロパティ名 | 種類 | 説明 |
|
||||
| ------------------------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| `matrix` | `オブジェクト` | This context is only available for jobs in a matrix, and changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains the properties listed below. |
|
||||
| `matrix.<property_name>` | `string` | The value of a matrix property. |
|
||||
|
||||
### Example contents of the `matrix` context
|
||||
|
||||
The following example contents of the `matrix` context is from a job in a build matrix that has the `os` and `node` matrix properties defined in the workflow. The job is executing the matrix combination of an `ubuntu-latest` OS and Node.js version `16`.
|
||||
The following example contents of the `matrix` context is from a job in a matrix that has the `os` and `node` matrix properties defined in the workflow. The job is executing the matrix combination of an `ubuntu-latest` OS and Node.js version `16`.
|
||||
|
||||
```yaml
|
||||
{
|
||||
@@ -609,7 +609,7 @@ The following example contents of the `matrix` context is from a job in a build
|
||||
|
||||
### Example usage of the `matrix` context
|
||||
|
||||
This example workflow creates a build matrix with `os` and `node` keys. It uses the `matrix.os` property to set the runner type for each job, and uses the `matrix.node` property to set the Node.js version for each job.
|
||||
This example workflow creates a matrix with `os` and `node` keys. It uses the `matrix.os` property to set the runner type for each job, and uses the `matrix.node` property to set the Node.js version for each job.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Test matrix
|
||||
|
||||
@@ -50,7 +50,7 @@ CircleCIと{% data variables.product.prodname_actions %}は、どちらも似た
|
||||
|
||||
CircleCIと{% data variables.product.prodname_actions %}は、どちらもワークフロー中のタスクを再利用し、共有するための仕組みを提供しています。 CircleCIはorbsという概念を利用します。これはYAMLで書かれ、ワークフロー中で再利用できるタスクを提供します。 {% data variables.product.prodname_actions %}はアクションと呼ばれる強力で柔軟な再利用できるコンポーネントを持っており、これはJavaScriptファイルもしくはDockerイメージで構築できます。 {% data variables.product.product_name %} の API やパブリックに利用可能なサードパーティ API との統合など、リポジトリと相互作用するカスタムコードを書いてアクションを作成することができます。 たとえば、アクションでnpmモジュールを公開する、緊急のIssueが発生したときにSMSアラートを送信する、本番対応のコードをデプロイすることなどが可能です。 詳細については、「[アクションを作成する](/actions/creating-actions)」を参照してください。
|
||||
|
||||
CircleCIは、YAMLのアンカーとエイリアスでワークフローの部分を再利用できます。 {% data variables.product.prodname_actions %}はビルドマトリックスを使って、再利用性についての一般的な要求のほとんどをサポートします。 ビルドマトリックスに関する詳細な情報については「[複雑なワークフローを管理する](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix)」を参照してください。
|
||||
CircleCIは、YAMLのアンカーとエイリアスでワークフローの部分を再利用できます。 {% data variables.product.prodname_actions %} supports the most common need for reusability using matrices. For more information about matrices, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
## Dockerイメージの利用
|
||||
|
||||
|
||||
@@ -83,9 +83,9 @@ Jenkinsは`ステージ`と`ステップ`を並行して実行できますが、
|
||||
| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| [`parallel`](https://jenkins.io/doc/book/pipeline/syntax/#parallel) | [`jobs.<job_id>.strategy.max-parallel`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel) |
|
||||
|
||||
### ビルドマトリックス
|
||||
### Matrix
|
||||
|
||||
{% data variables.product.prodname_actions %}とJenkinsはどちらも、ビルドマトリックスを使って様々なシステムの組み合わせを定義できます。
|
||||
Both {% data variables.product.prodname_actions %} and Jenkins let you use a matrix to define various system combinations.
|
||||
|
||||
| Jenkins | {% data variables.product.prodname_actions %}
|
||||
| ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
|
||||
@@ -59,9 +59,9 @@ Travis CI は、`stages` を使用してジョブを並行して実行できま
|
||||
|
||||
Travis CI と {% data variables.product.prodname_actions %} はどちらもステータスバッジをサポートしており、ビルドが成功したか失敗したかを示すことができます。 詳しい情報については、「[リポジトリにワークフローステータスバッジを追加する](/actions/managing-workflow-runs/adding-a-workflow-status-badge)」を参照してください。
|
||||
|
||||
### ビルドマトリックスを使用する
|
||||
### Using a matrix
|
||||
|
||||
Travis CI と {% data variables.product.prodname_actions %} はどちらもビルドマトリックスをサポートしているため、オペレーティングシステムとソフトウェアパッケージの組み合わせを使用してテストを実行できます。 詳しい情報については、「[ビルドマトリックスを使用する](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)」を参照してください。
|
||||
Travis CI and {% data variables.product.prodname_actions %} both support a matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
以下は、各システムの構文を比較した例です。
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ children:
|
||||
- /using-jobs-in-a-workflow
|
||||
- /choosing-the-runner-for-a-job
|
||||
- /using-conditions-to-control-job-execution
|
||||
- /using-a-build-matrix-for-your-jobs
|
||||
- /using-a-matrix-for-your-jobs
|
||||
- /using-concurrency
|
||||
- /using-environments-for-jobs
|
||||
- /running-jobs-in-a-container
|
||||
|
||||
@@ -1,30 +0,0 @@
|
||||
---
|
||||
title: Using a build matrix for your jobs
|
||||
shortTitle: Using a build matrix for your jobs
|
||||
intro: Create a build matrix and define variations for each job.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
miniTocMaxHeadingLevel: 4
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## 概要
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-strategy %}
|
||||
|
||||
## Creating a matrix of different job configurations
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-matrix %}
|
||||
|
||||
## Canceling remaining jobs if a `matrix` job fails
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-failfast %}
|
||||
|
||||
## Defining the maximum number of concurrent jobs in a `matrix`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-max-parallel %}
|
||||
@@ -0,0 +1,60 @@
|
||||
---
|
||||
title: Using a matrix for your jobs
|
||||
shortTitle: Using a matrix
|
||||
intro: Create a matrix to define variations for each job.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
miniTocMaxHeadingLevel: 4
|
||||
redirect_from:
|
||||
- /actions/using-jobs/using-a-build-matrix-for-your-jobs
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## About matrix strategies
|
||||
|
||||
{% data reusables.actions.jobs.about-matrix-strategy %}
|
||||
|
||||
## Using a matrix strategy
|
||||
|
||||
{% data reusables.actions.jobs.using-matrix-strategy %}
|
||||
|
||||
### Example: Using a single-dimension matrix
|
||||
|
||||
{% data reusables.actions.jobs.single-dimension-matrix %}
|
||||
|
||||
### Example: Using a multi-dimension matrix
|
||||
|
||||
{% data reusables.actions.jobs.multi-dimension-matrix %}
|
||||
|
||||
### Example: Using contexts to create matrices
|
||||
|
||||
{% data reusables.actions.jobs.matrix-from-context %}
|
||||
|
||||
## Expanding or adding matrix configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-include %}
|
||||
|
||||
### Example: Expanding configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-expand-with-include %}
|
||||
|
||||
### Example: Adding configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-add-with-include %}
|
||||
|
||||
## Excluding matrix configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-exclude %}
|
||||
|
||||
## Handling failures
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-failfast %}
|
||||
|
||||
## Defining the maximum number of concurrent jobs
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-max-parallel %}
|
||||
@@ -105,9 +105,9 @@ jobs:
|
||||
|
||||
For more information, see "[Defining prerequisite jobs](/actions/using-jobs/using-jobs-in-a-workflow#defining-prerequisite-jobs)."
|
||||
|
||||
### ビルドマトリックスを使用する
|
||||
### Using a matrix
|
||||
|
||||
You can use a build matrix if you want your workflow to run tests across multiple combinations of parameters, such as operating systems, platforms, and languages. ビルドマトリックスは、ビルドオプションを配列として受け取る `strategy` キーワードを使用して作成されます。 たとえば、このビルドマトリックスは、異なるバージョンの Node.js を使用して、ジョブを複数回実行します。
|
||||
{% data reusables.actions.jobs.about-matrix-strategy %} The matrix is created using the `strategy` keyword, which receives the build options as an array. For example, this matrix will run the job multiple times, using different versions of Node.js:
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
@@ -115,14 +115,14 @@ jobs:
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
node: [6, 8, 10]
|
||||
node: [12, 14, 16]
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.node }}{% endraw %}
|
||||
```
|
||||
|
||||
For more information, see "[Using a build matrix for your jobs](/actions/using-jobs/using-a-build-matrix-for-your-jobs)."
|
||||
For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### 依存関係のキャッシング
|
||||
|
||||
@@ -745,11 +745,39 @@ If the timeout exceeds the job execution time limit for the runner, the job will
|
||||
|
||||
## `jobs.<job_id>.strategy`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-strategy %}
|
||||
Use `jobs.<job_id>.strategy` to use a matrix strategy for your jobs. {% data reusables.actions.jobs.about-matrix-strategy %} For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
### `jobs.<job_id>.strategy.matrix`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-matrix %}
|
||||
{% data reusables.actions.jobs.using-matrix-strategy %}
|
||||
|
||||
#### Example: Using a single-dimension matrix
|
||||
|
||||
{% data reusables.actions.jobs.single-dimension-matrix %}
|
||||
|
||||
#### Example: Using a multi-dimension matrix
|
||||
|
||||
{% data reusables.actions.jobs.multi-dimension-matrix %}
|
||||
|
||||
#### Example: Using contexts to create matrices
|
||||
|
||||
{% data reusables.actions.jobs.matrix-from-context %}
|
||||
|
||||
### `jobs.<job_id>.strategy.matrix.include`
|
||||
|
||||
{% data reusables.actions.jobs.matrix-include %}
|
||||
|
||||
#### Example: Expanding configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-expand-with-include %}
|
||||
|
||||
#### Example: Adding configurations
|
||||
|
||||
{% data reusables.actions.jobs.matrix-add-with-include %}
|
||||
|
||||
### `jobs.<job_id>.strategy.matrix.exclude`
|
||||
|
||||
{% data reusables.actions.jobs.matrix-exclude %}
|
||||
|
||||
### `jobs.<job_id>.strategy.fail-fast`
|
||||
|
||||
|
||||
@@ -33,6 +33,13 @@ Before you can enable and configure {% data variables.product.prodname_registry
|
||||
1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string.
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account.
|
||||
Usage of a SAS Token or SAS URL as connection string is not currently supported.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
## Next steps
|
||||
|
||||
@@ -208,7 +208,7 @@ If this parameter is not used, the {% data variables.product.prodname_codeql_wor
|
||||
|
||||
{% data reusables.code-scanning.codeql-languages-bullets %}
|
||||
|
||||
The default {% data variables.product.prodname_codeql_workflow %} file contains a build matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about build matrices, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix)."
|
||||
The default {% data variables.product.prodname_codeql_workflow %} file contains a matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about matrices, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
|
||||
|
||||
{% data reusables.code-scanning.specify-language-to-analyze %}
|
||||
|
||||
|
||||
@@ -68,7 +68,7 @@ topics:
|
||||
|
||||
- {% data variables.product.prodname_code_scanning %} ワークフローから `autobuild` ステップを削除し、特定のビルドステップを追加します。 ワークフローの編集に関する詳しい情報は、「[{% data variables.product.prodname_code_scanning %} を設定する](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)」を参照してください。 `autobuild` ステップの置き換えに関する詳細は、「[コンパイル型言語の {% data variables.product.prodname_codeql %} ワークフローを設定する](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)」を参照してください。
|
||||
|
||||
- ワークフローが解析する言語を明示的に指定していない場合、{% data variables.product.prodname_codeql %} はコードベースでサポートされている言語を暗黙的に検出します。 この設定では、コンパイル型言語である C/C++、C#、Java のうち、{% data variables.product.prodname_codeql %} はソースファイルの数が最も多い言語のみを解析します。 ワークフローを編集し、解析する言語を指定したビルドマトリクスを追加してください。 デフォルトの CodeQL 解析では、こうしたマトリクスを使用しています。
|
||||
- ワークフローが解析する言語を明示的に指定していない場合、{% data variables.product.prodname_codeql %} はコードベースでサポートされている言語を暗黙的に検出します。 この設定では、コンパイル型言語である C/C++、C#、Java のうち、{% data variables.product.prodname_codeql %} はソースファイルの数が最も多い言語のみを解析します。 Edit the workflow and add a matrix specifying the languages you want to analyze. デフォルトの CodeQL 解析では、こうしたマトリクスを使用しています。
|
||||
|
||||
以下はワークフローからの抜粋で、まず言語を指定するジョブ戦略におけるマトリクスの使用法を示し、次に「Initialize {% data variables.product.prodname_codeql %}」のステップで各言語を参照しています。
|
||||
|
||||
@@ -188,7 +188,7 @@ C/C++、C#、Go、Javaなどのコンパイル言語については、{% data va
|
||||
|
||||
### マトリックスビルドを使用して分析を並列化する
|
||||
|
||||
デフォルトの {% data variables.product.prodname_codeql_workflow %} は言語のビルドマトリクスを使用しており、これにより各言語の解析が並列で実行される場合があります。 「Initialize CodeQL」ステップで解析する言語を直接指定している場合、各言語の解析は順次行われます。 複数の言語で解析を高速化するには、マトリクスを使用するようワークフローを変更してください。 詳しい情報については、上記「[コンパイル言語の自動ビルドの失敗](#automatic-build-for-a-compiled-language-fails)」にあるワークフローの抜粋を参照してください。
|
||||
The default {% data variables.product.prodname_codeql_workflow %} uses a matrix of languages, which causes the analysis of each language to run in parallel. 「Initialize CodeQL」ステップで解析する言語を直接指定している場合、各言語の解析は順次行われます。 複数の言語で解析を高速化するには、マトリクスを使用するようワークフローを変更してください。 詳しい情報については、上記「[コンパイル言語の自動ビルドの失敗](#automatic-build-for-a-compiled-language-fails)」にあるワークフローの抜粋を参照してください。
|
||||
|
||||
### 1 つのワークフローで分析されるコードの量を減らす
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ shortTitle: Learning resources
|
||||
---
|
||||
## Using Git
|
||||
|
||||
Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can review the [Git command list](https://git-scm.com/docs) or [Git command lookup reference](http://gitref.org) while using the [Try Git](https://try.github.com) simulator.
|
||||
Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can also review the [Git command list](https://git-scm.com/docs).
|
||||
|
||||
## Using {% data variables.product.product_name %}
|
||||
|
||||
|
||||
@@ -23,6 +23,7 @@ permissions: Organization owners can remove members from an organization.
|
||||
**警告:** Organization からメンバーを削除する際は次の点にご注意ください:
|
||||
- 有料ライセンスのカウントは自動的にはダウングレードされません。 Organization からユーザを削除したあとに有料シートの数を減らすには、「[Organization の有料ライセンスをダウングレードする](/articles/downgrading-your-organization-s-paid-seats)」の手順に従ってください。
|
||||
- 削除されたメンバーは Organization のプライベートリポジトリのプライベートフォークへのアクセスは失いますが、ローカルコピーを自分で持っておくことは可能です。 ただし、ローカルコピーを Organization のリポジトリと同期させることはできません。 そのプライベートフォークは、そのユーザが Organization から削除されてから 3 か月以内に [Organization メンバーとして復帰した](/articles/reinstating-a-former-member-of-your-organization)場合、リストアできます。 最終的に、リポジトリへのアクセスを失った個人に、機密情報や知的財産を確実に削除してもらうのは、あなたの責任です。
|
||||
- When private repositories are forked to other organizations, those organizations are able to control access to the fork network. This means users may retain access to the forks even after losing access to the original organization because they will still have explicit access via a fork.
|
||||
{%- ifversion ghec %}
|
||||
- 削除されたメンバーは、同じEnterpriseアカウントが所有する他のOrganizationのメンバーではない場合、Organizationのインターナルリポジトリのプライベートフォークへのアクセスも失うことになります。 詳細は「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」を参照してください。
|
||||
{%- endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Secret Scanning
|
||||
intro: Use the Secret Scanning API to retrieve and update secret alerts from a repository.
|
||||
intro: Secret Scanning APIを使うと、リポジトリのシークレットアラートの取得と更新ができます。
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
@@ -14,10 +14,10 @@ redirect_from:
|
||||
|
||||
{% data reusables.secret-scanning.api-beta %}
|
||||
|
||||
The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae %}:
|
||||
{% data variables.product.prodname_secret_scanning %} APIを使うと{% ifversion fpt or ghec or ghes > 3.1 or ghae %}以下のことができます。
|
||||
|
||||
- Enable or disable {% data variables.product.prodname_secret_scanning %}{% if secret-scanning-push-protection %} and push protection{% endif %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" and expand the "Properties of the `security_and_analysis` object" section in the REST API documentation.
|
||||
- Retrieve and update {% data variables.product.prodname_secret_scanning_GHAS %} alerts from a repository. For further details, see the sections below.
|
||||
{%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a repository.{% endif %}
|
||||
- リポジトリの{% data variables.product.prodname_secret_scanning %}{% if secret-scanning-push-protection %}及びプッシュ保護{% endif %}の有効化あるいは無効化。 詳しい情報については「[リポジトリ](/rest/reference/repos#update-a-repository)」を参照し、REST APIドキュメンテーションの「`security_and_analysis`のプロパティ」セクションを展開してください。
|
||||
- リポジトリからの{% data variables.product.prodname_secret_scanning_GHAS %}アラートの取得と更新。 詳細については以下のセクションを参照してください。
|
||||
{%- else %}リポジトリからの{% data variables.product.prodname_secret_scanning %}アラートの取得と更新ができます。{% endif %}
|
||||
|
||||
{% data variables.product.prodname_secret_scanning %} の詳細については、「[{% data variables.product.prodname_secret_scanning %} について](/code-security/secret-security/about-secret-scanning)」を参照してください。
|
||||
|
||||
@@ -14,12 +14,6 @@ sections:
|
||||
- When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list.
|
||||
- The `/stafftools/users/ip_addresses/:address` page responded with a `500 Internal Server Error` when attempting to display the page for an IPv6 address.
|
||||
- Creating an impersonation OAuth token using the Enterprise Administration REST API resulted in an error when an integration matching the OAuth Application ID already existed.
|
||||
- |
|
||||
When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11]
|
||||
|
||||
To work around this problem, you can take one of the two following actions.
|
||||
- Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute.
|
||||
- Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL.
|
||||
changes:
|
||||
- Added support for replica domain names that are more than 63 characters.
|
||||
- Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log.
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
A matrix strategy lets you use variables in a single job definition to automatically create multiple job runs that are based the combinations of the variables. For example, you can use a matrix strategy to test your code in multiple versions of a language or on multiple operating systems.
|
||||
@@ -0,0 +1,29 @@
|
||||
For example, this matrix will run 10 jobs, one for each combination of `os` and `version` in the matrix, plus a job for the `os` value of `windows-latest` and `version` value of `17`.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
os: [macos-latest, windows-latest, ubuntu-latest]
|
||||
version: [12, 14, 16]
|
||||
include:
|
||||
- os: windows-latest
|
||||
version: 17
|
||||
```
|
||||
|
||||
If you don't specify any matrix variables, all configurations under `include` will run. For example, the following workflow would run two jobs, one for each `include` entry. This lets you take advantage of the matrix strategy without having a fully populated matrix.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
includes_only:
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
include:
|
||||
- site: "production"
|
||||
datacenter: "site-a"
|
||||
- site: "staging"
|
||||
datacenter: "site-b"
|
||||
|
||||
```
|
||||
@@ -0,0 +1,22 @@
|
||||
To remove specific configurations defined in the matrix, use `jobs.<job_id>.strategy.matrix.exclude`. An excluded configuration only has to be a partial match for it to be excluded. For example, the following workflow will run nine jobs: one job for each of the 12 configurations, minus the one excluded job that matches `{os: macos-latest, version: 12, environment: production}`, and the two excluded jobs that match `{os: windows-latest, version: 16}`.
|
||||
|
||||
```yaml
|
||||
strategy:
|
||||
matrix:
|
||||
os: [macos-latest, windows-latest]
|
||||
version: [12, 14, 16]
|
||||
environment: [staging, production]
|
||||
exclude:
|
||||
- os: macos-latest
|
||||
version: 12
|
||||
environment: production
|
||||
- os: windows-latest
|
||||
version: 16
|
||||
runs-on: {% raw %}${{ matrix.os }}{% endraw %}
|
||||
```
|
||||
|
||||
{% note %}
|
||||
|
||||
**ノート:** すべての`include`の組み合わせは、`exclude`の後に処理されます。 このため、`include`を使って以前に除外された組み合わせを追加し直すことができます。
|
||||
|
||||
{% endnote %}
|
||||
@@ -0,0 +1,22 @@
|
||||
For example, the following workflow will run six jobs, one for each combination of `os` and `node`. When the job for the `os` value of `windows-latest` and `node` value of `16` runs, an additional variable called `npm` with the value of `6` will be included in the job.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
os: [windows-latest, ubuntu-latest]
|
||||
node: [12, 14, 16]
|
||||
include:
|
||||
- os: windows-latest
|
||||
node: 16
|
||||
npm: 6
|
||||
runs-on: {% raw %}${{ matrix.os }}{% endraw %}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.node }}{% endraw %}
|
||||
- if: {% raw %}${{ matrix.npm }}{% endraw %}
|
||||
run: npm install -g npm@{% raw %}${{ matrix.npm }}{% endraw %}
|
||||
- run: npm --version
|
||||
```
|
||||
@@ -0,0 +1,30 @@
|
||||
You can use contexts to create matrices. For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)."
|
||||
|
||||
For example, the following workflow triggers on the `repository_dispatch` event and uses information from the event payload to build the matrix. When a repository dispatch event is created with a payload like the one below, the matrix `version` variable will have a value of `[12, 14, 16]`. For more information about the `repository_dispatch` trigger, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows#repository_dispatch)."
|
||||
|
||||
```json
|
||||
{
|
||||
"event_type": "test",
|
||||
"client_payload": {
|
||||
"versions": [12, 14, 16]
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
```yaml
|
||||
on:
|
||||
repository_dispatch:
|
||||
types:
|
||||
- test
|
||||
|
||||
jobs:
|
||||
example_matrix:
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
version: {% raw %}${{ github.event.client_payload.versions }}{% endraw %}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.version }}{% endraw %}
|
||||
```
|
||||
@@ -0,0 +1,38 @@
|
||||
Use `jobs.<job_id>.strategy.matrix.include` to expand existing matrix configurations or to add new configurations. The value of `include` is a list of objects.
|
||||
|
||||
For each object in the `include` list, the key:value pairs in the object will be added to each of the matrix combinations if none of the key:value pairs overwrite any of the original matrix values. If the object cannot be added to any of the matrix combinations, a new matrix combination will be created instead. Note that the original matrix values will not be overwritten, but added matrix values can be overwritten.
|
||||
|
||||
For example, this matrix:
|
||||
|
||||
```yaml
|
||||
strategy:
|
||||
matrix:
|
||||
fruit: [apple, pear]
|
||||
animal: [cat, dog]
|
||||
include:
|
||||
- color: green
|
||||
- color: pink
|
||||
animal: cat
|
||||
- fruit: apple
|
||||
shape: circle
|
||||
- fruit: banana
|
||||
- fruit: banana
|
||||
animal: cat
|
||||
```
|
||||
|
||||
will result in six jobs with the following matrix combinations:
|
||||
|
||||
- `{fruit: apple, animal: cat, color: pink, shape: circle}`
|
||||
- `{fruit: apple, animal: dog, color: green, shape: circle}`
|
||||
- `{fruit: pear, animal: cat, color: pink}`
|
||||
- `{fruit: pear, animal: dog, color: green}`
|
||||
- `{fruit: banana}`
|
||||
- `{fruit: banana, animal: cat}`
|
||||
|
||||
following this logic:
|
||||
|
||||
- `{color: green}` is added to all of the original matrix combinations because it can be added without overwriting any part of the original combinations.
|
||||
- `{color: pink, animal: cat}` adds `color:pink` only to the original matrix combinations that include `animal: cat`. This overwrites the `color: green` that was added by the previous `include` entry.
|
||||
- `{fruit: apple, shape: circle}` adds `shape: circle` only to the original matrix combinations that include `fruit: apple`.
|
||||
- `{fruit: banana}` cannot be added to any original matrix combination without overwriting a value, so it is added as an additional matrix combination.
|
||||
- `{fruit: banana, animal: cat}` cannot be added to any original matrix combination without overwriting a value, so it is added as an additional matrix combination. It does not add to the `{fruit: banana}` matrix combination because that combination was not one of the original matrix combinations.
|
||||
@@ -0,0 +1,22 @@
|
||||
You can specify multiple variables to create a multi-dimensional matrix. A job will run for each possible combination of the variables.
|
||||
|
||||
For example, the following workflow specifies two variables:
|
||||
|
||||
- Two operating systems specified in the `os` variable
|
||||
- Three Node.js versions specified in the `version` variable
|
||||
|
||||
The workflow will run six jobs, one for each combination of the `os` and `version` variables. Each job will set the `runs-on` value to the current `os` value and will pass the current `version` value to the `actions/setup-node` action.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
os: [ubuntu-18.04, ubuntu-20.04]
|
||||
version: [10, 12, 14]
|
||||
runs-on: {% raw %}${{ matrix.os }}{% endraw %}
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.version }}{% endraw %}
|
||||
```
|
||||
@@ -1 +1,23 @@
|
||||
When `jobs.<job_id>.strategy.fail-fast` is set to `true`, {% data variables.product.prodname_dotcom %} cancels all in-progress jobs in the matrix if any `matrix` job fails. デフォルト: `true`
|
||||
You can control how job failures are handled with `jobs.<job_id>.strategy.fail-fast` and `jobs.<job_id>.continue-on-error`.
|
||||
|
||||
`jobs.<job_id>.strategy.fail-fast` applies to the entire matrix. If `jobs.<job_id>.strategy.fail-fast` is set to `true`, {% data variables.product.product_name %} will cancel all in-progress and queued jobs in the matrix if any job in the matrix fails. This property defaults to `true`.
|
||||
|
||||
`jobs.<job_id>.continue-on-error` applies to a single job. If `jobs.<job_id>.continue-on-error` is `true`, other jobs in the matrix will continue running even if the job with `jobs.<job_id>.continue-on-error: true` fails.
|
||||
|
||||
You can use `jobs.<job_id>.strategy.fail-fast` and `jobs.<job_id>.continue-on-error` together. For example, the following workflow will start four jobs. For each job, `continue-on-error` is determined by the value of `matrix.experimental`. If any of the jobs with `continue-on-error: false` fail, all jobs that are in progress or queued will be cancelled. If the job with `continue-on-error: true` fails, the other jobs will not be affected.
|
||||
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
test:
|
||||
runs-on: ubuntu-latest
|
||||
continue-on-error: {% raw %}${{ matrix.experimental }}{% endraw %}
|
||||
strategy:
|
||||
fail-fast: true
|
||||
matrix:
|
||||
version: [6, 7, 8]
|
||||
experimental: [false]
|
||||
include:
|
||||
- version: 9
|
||||
experimental: true
|
||||
```
|
||||
|
||||
@@ -1,122 +0,0 @@
|
||||
|
||||
Use `jobs.<job_id>.strategy.matrix` to define a matrix of different job configurations. マトリックスによって、単一のジョブの定義内の変数の置き換えを行い、複数のジョブを作成できるようになります。 たとえば、マトリックスを使って複数のサポートされているバージョンのプログラミング言語、オペレーティングシステム、ツールに対するジョブを作成できます。 マトリックスは、ジョブの設定を再利用し、設定した各マトリクスに対してジョブを作成します。
|
||||
|
||||
{% data reusables.actions.usage-matrix-limits %}
|
||||
|
||||
`matrix`内で定義した各オプションは、キーと値を持ちます。 定義したキーは`matrix`コンテキスト中の属性となり、ワークフローファイルの他のエリア内のプロパティを参照できます。 たとえば、オペレーティングシステムの配列を含む`os`というキーを定義したなら、`matrix.os`属性を`runs-on`キーワードの値として使い、それぞれのオペレーティングシステムに対するジョブを作成できます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。
|
||||
|
||||
`matrix`を定義する順序は意味を持ちます。 最初に定義したオプションは、ワークフロー中で最初に実行されるジョブになります。
|
||||
|
||||
#### Example: Running multiple versions of Node.js
|
||||
|
||||
設定オプションに配列を指定すると、マトリクスを指定できます。 たとえばランナーがNode.jsのバージョン10、12、14,をサポートしている場合、これらのバージョンの配列を`matrix`で指定できます。
|
||||
|
||||
この例では、`node`キーにNode.jsの3つのバージョンの配列を設定することによって、3つのジョブのマトリクスを作成します。 このマトリックスを使用するために、この例では`matrix.node`コンテキスト属性を`setup-node`アクションの入力パラメータである`node-version`に設定しています。 その結果、3 つのジョブが実行され、それぞれが異なるバージョンのNode.js を使用します。
|
||||
|
||||
```yaml
|
||||
strategy:
|
||||
matrix:
|
||||
node: [10, 12, 14]
|
||||
steps:
|
||||
# Configures the node version used on GitHub-hosted runners
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
# The Node.js version to configure
|
||||
node-version: {% raw %}${{ matrix.node }}{% endraw %}
|
||||
```
|
||||
|
||||
{% data variables.product.prodname_dotcom %}ホストランナーを使う場合にNode.jsのバージョンを設定する方法としては、`setup-node`アクションをおすすめします。 詳しい情報については[`setup-node`](https://github.com/actions/setup-node)アクションを参照してください。
|
||||
|
||||
#### Example: Running with multiple operating systems
|
||||
|
||||
複数のランナーオペレーティングシステムでワークフローを実行するマトリックスを作成できます。 複数のマトリックス設定を指定することもできます。 この例では、6つのジョブのマトリックスを作成します。
|
||||
|
||||
- 配列`os`で指定された2つのオペレーティングシステム
|
||||
- 配列`node`で指定された3つのバージョンのNode.js
|
||||
|
||||
{% data reusables.repositories.actions-matrix-builds-os %}
|
||||
|
||||
```yaml
|
||||
runs-on: {% raw %}${{ matrix.os }}{% endraw %}
|
||||
strategy:
|
||||
matrix:
|
||||
os: [ubuntu-18.04, ubuntu-20.04]
|
||||
node: [10, 12, 14]
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.node }}{% endraw %}
|
||||
```
|
||||
|
||||
{% ifversion ghae %}
|
||||
For more information about the configuration of self-hosted runners, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
|
||||
{% else %}{% data variables.product.prodname_dotcom %} ホストランナーでサポートされている設定オプションについては、「[{% data variables.product.prodname_dotcom %} の仮想環境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)」を参照してください。
|
||||
{% endif %}
|
||||
|
||||
#### Example: Including additional values in combinations
|
||||
|
||||
既存のビルドマトリクスジョブに、設定オプションを追加できます。 たとえば、`windows-latest` を使うジョブで`node` のバージョン 8 を実行しているときに、`npm` の特定のバージョンを使いたい場合は、`include` を使って追加のオプションを指定できます。
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
runs-on: ${{ matrix.os }}
|
||||
strategy:
|
||||
matrix:
|
||||
os: [macos-latest, windows-latest, ubuntu-18.04]
|
||||
node: [8, 10, 12, 14]
|
||||
include:
|
||||
# osとバージョンに一致するマトリックスレッグの値が
|
||||
# 6 の npm の新しい変数を含む
|
||||
- os: windows-latest
|
||||
node: 8
|
||||
npm: 6
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
#### Example: Including new combinations
|
||||
|
||||
`include`を使って新しいジョブを追加し、マトリックスを構築できます。 マッチしなかったincludeの設定があれば、マトリックスに追加されます。 たとえば、`node`のバージョン14を使って複数のオペレーティングシステム上でビルドを行い、追加で実験的なジョブをUbuntu上でnodeバージョン15で行いたいなら、`include`を使ってこの追加のジョブを指定できます。
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
runs-on: ${{ matrix.os }}
|
||||
strategy:
|
||||
matrix:
|
||||
node: [14]
|
||||
os: [macos-latest, windows-latest, ubuntu-18.04]
|
||||
include:
|
||||
- node: 15
|
||||
os: ubuntu-18.04
|
||||
experimental: true
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
#### Example: Excluding configurations from a matrix
|
||||
|
||||
`exclude` オプションを使って、ビルドマトリクスに定義されている特定の設定を削除できます。 `exclude` を使うと、ビルドマトリクスにより定義されたジョブが削除されます。 ジョブの数は、指定する配列に含まれるオペレーティングシステム (`os`) の外積から、任意の減算 (`exclude`) で引いたものです。
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
runs-on: ${{ matrix.os }}
|
||||
strategy:
|
||||
matrix:
|
||||
os: [macos-latest, windows-latest, ubuntu-18.04]
|
||||
node: [8, 10, 12, 14]
|
||||
exclude:
|
||||
# macOS のノード 8 を除外する
|
||||
- os: macos-latest
|
||||
node: 8
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**ノート:** すべての`include`の組み合わせは、`exclude`の後に処理されます。 このため、`include`を使って以前に除外された組み合わせを追加し直すことができます。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### マトリックスで環境変数を使用する
|
||||
|
||||
それぞれのテストの組み合わせに、`include`キーを使ってカスタムの環境変数を追加できます。 そして、後のステップでそのカスタムの環境変数を参照できます。
|
||||
|
||||
{% data reusables.actions.matrix-variable-example %}
|
||||
@@ -1,6 +1,13 @@
|
||||
Use `jobs.<job_id>.strategy.max-parallel` to set the maximum number of jobs that can run simultaneously when using a `matrix` job strategy. デフォルトでは、{% data variables.product.prodname_dotcom %}は{% data variables.product.prodname_dotcom %}がホストしている仮想マシン上で利用できるrunnerに応じてできるかぎりの数のジョブを並列に実行します。
|
||||
By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. To set the maximum number of jobs that can run simultaneously when using a `matrix` job strategy, use `jobs.<job_id>.strategy.max-parallel`.
|
||||
|
||||
For example, the following workflow will run a maximum of two jobs at a time, even if there are runners available to run all six jobs at once.
|
||||
|
||||
```yaml
|
||||
strategy:
|
||||
max-parallel: 2
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
max-parallel: 2
|
||||
matrix:
|
||||
version: [10, 12, 14]
|
||||
os: [ubuntu-latest, windows-latest]
|
||||
```
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
Use `jobs.<job_id>.strategy` to create a build matrix for your jobs. それぞれのジョブを実行する様々なバリエーションを定義できます。
|
||||
@@ -0,0 +1,15 @@
|
||||
You can specify a single variable to create a single-dimension matrix.
|
||||
|
||||
For example, the following workflow defines the variable `version` with the values `[10, 12, 14]`. The workflow will run three jobs, one for each value in the variable. Each job will access the `version` value through the `matrix.version` context and pass the value as `node-version` to the `actions/setup-node` action.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
version: [10, 12, 14]
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-setup-node %}
|
||||
with:
|
||||
node-version: {% raw %}${{ matrix.version }}{% endraw %}
|
||||
```
|
||||
@@ -0,0 +1,25 @@
|
||||
Use `jobs.<job_id>.strategy.matrix` to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a veriable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`:
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
example_matrix:
|
||||
strategy:
|
||||
matrix:
|
||||
version: [10, 12, 14]
|
||||
os: [ubuntu-latest, windows-latest]
|
||||
```
|
||||
|
||||
A job will run for each possible combination of the variables. In this example, the workflow will run six jobs, one for each combination of the `os` and `version` variables.
|
||||
|
||||
By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. The order of the variables in the matrix determines the order in which the jobs are created. The first variable you define will be the first job that is created in your workflow run. For example, the above matrix will create the jobs in the following order:
|
||||
|
||||
- `{version: 10, os: ubuntu-latest}`
|
||||
- `{version: 10, os: windows-latest}`
|
||||
- `{version: 12, os: ubuntu-latest}`
|
||||
- `{version: 12, os: windows-latest}`
|
||||
- `{version: 14, os: ubuntu-latest}`
|
||||
- `{version: 14, os: windows-latest}`
|
||||
|
||||
A matrix will generate a maximum of 256 jobs per workflow run. This limit applies to both {% data variables.product.product_name %}-hosted and self-hosted runners.
|
||||
|
||||
The variables that you define become properties in the `matrix` context, and you can reference the property in other areas of your workflow file. In this example, you can use `matrix.version` and `matrix.os` to access the current value of `version` and `os` that the job is using. 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。
|
||||
@@ -1 +0,0 @@
|
||||
オペレーティングシステムのマトリックスを定義する際には、`runs-on`の値を、定義した`matrix.os`コンテキストのプロパティに設定しなければなりません。
|
||||
@@ -9,9 +9,9 @@ Adobe | Adobe Service Token | adobe_service_token{% endif %}
|
||||
Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Amazon | Amazon OAuth Client ID | amazon_oauth_client_id{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Amazon | Amazon OAuth Client Secret | amazon_oauth_client_secret{% endif %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %}
|
||||
@@ -21,9 +21,9 @@ Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_a
|
||||
Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} Atlassian | Atlassian API Token | atlassian_api_token Atlassian | Atlassian JSON Web Token | atlassian_jwt
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key{% endif %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token Azure | Azure SAS Token | azure_sas_token Azure | Azure Service Management Certificate | azure_management_certificate
|
||||
{%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %}
|
||||
Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} Azure | Azure Storage Account Key | azure_storage_account_key
|
||||
@@ -63,7 +63,7 @@ GitHub | GitHub OAuthアクセストークン | github_oauth_access_token{% endi
|
||||
GitHub | GitHubリフレッシュトークン | github_refresh_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} GitHub | GitHub SSH Private Key | github_ssh_private_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
GitLab | GitLab Access Token | gitlab_access_token{% endif %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} Google | Google API Key | google_api_key Google | Google Cloud Private Key ID | google_cloud_private_key_id
|
||||
@@ -73,13 +73,13 @@ Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_ke
|
||||
Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Google | Google OAuth Access Token | google_oauth_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Google | Google OAuth Client ID | google_oauth_client_id{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Google | Google OAuth Client Secret | google_oauth_client_secret{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Grafana | Grafana API Key | grafana_api_key{% endif %} HashiCorp | Terraform Cloud / Enterprise API Token | terraform_api_token HashiCorp | HashiCorp Vault Batch Token | hashicorp_vault_batch_token HashiCorp | HashiCorp Vault Service Token | hashicorp_vault_service_token Hubspot | Hubspot API Key | hubspot_api_key
|
||||
@@ -89,7 +89,7 @@ Intercom | Intercom Access Token | intercom_access_token{% endif %}
|
||||
Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
JD Cloud | JD Cloud Access Key | jd_cloud_access_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %}
|
||||
@@ -103,15 +103,15 @@ Linear | Linear OAuth Access Token | linear_oauth_access_token{% endif %}
|
||||
Lob | Lob Live API Key | lob_live_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Lob | Lob Test API Key | lob_test_api_key{% endif %} Mailchimp | Mailchimp API Key | mailchimp_api_key Mailgun | Mailgun API Key | mailgun_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Mapbox | Mapbox Secret Access Token | mapbox_secret_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
MessageBird | MessageBird API Key | messagebird_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Meta | Facebook Access Token | facebook_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Midtrans | Midtrans Production Server Key | midtrans_production_server_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %}
|
||||
@@ -121,11 +121,11 @@ New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %}
|
||||
New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %}
|
||||
New Relic | New Relic License Key | new_relic_license_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Notion | Notion Integration Token | notion_integration_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Notion | Notion OAuth Client Secret | notion_oauth_client_secret{% endif %} npm | npm Access Token | npm_access_token NuGet | NuGet API Key | nuget_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Octopus Deploy | Octopus Deploy API Key | octopus_deploy_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Onfido | Onfido Live API Token | onfido_live_api_token{% endif %}
|
||||
@@ -147,7 +147,7 @@ Plivo | Plivo Auth Token | plivo_auth_token{% endif %} Postman | Postman API Key
|
||||
PyPI | PyPI API Token | pypi_api_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
RubyGems | RubyGems API Key | rubygems_api_key{% endif %} Samsara | Samsara API Token | samsara_api_token Samsara | Samsara OAuth Access Token | samsara_oauth_access_token
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
Segment | Segment Public API Token | segment_public_api_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
SendGrid | SendGrid API Key | sendgrid_api_key{% endif %}
|
||||
@@ -159,36 +159,36 @@ Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %}
|
||||
Shippo | Shippo Live API Token | shippo_live_api_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Shippo | Shippo Test API Token | shippo_test_api_token{% endif %} Shopify | Shopify App Shared Secret | shopify_app_shared_secret Shopify | Shopify Access Token | shopify_access_token Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token Shopify | Shopify Private App Password | shopify_private_app_password Slack | Slack API Token | slack_api_token Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Square | Square Access Token | square_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Square | Square Production Application Secret | square_production_application_secret{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Square | Square Sandbox Application Secret | square_sandbox_application_secret{% endif %} SSLMate | SSLMate API Key | sslmate_api_key SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret Stripe | Stripe API Key | stripe_api_key Stripe | Stripe Live API Secret Key | stripe_live_secret_key Stripe | Stripe Test API Secret Key | stripe_test_secret_key Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Supabase | Supabase Service Key | supabase_service_key{% endif %} Tableau | Tableau Personal Access Token | tableau_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
Telegram | Telegram Bot Token | telegram_bot_token{% endif %} Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Twilio | Twilio Access Token | twilio_access_token{% endif %} Twilio | Twilio Account String Identifier | twilio_account_sid Twilio | Twilio API Key | twilio_api_key
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Typeform | Typeform Personal Access Token | typeform_personal_access_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
WorkOS | WorkOS Production API Key | workos_production_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %}
|
||||
WorkOS | WorkOS Staging API Key | workos_staging_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Yandex.Cloud API Key | yandex_cloud_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Yandex.Cloud IAM Cookie | yandex_cloud_iam_cookie{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Yandex.Cloud IAM Token | yandex_cloud_iam_token{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Yandex.Dictionary API Key | yandex_dictionary_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Yandex.Predictor API Key | yandex_predictor_api_key{% endif %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %}
|
||||
Yandex | Yandex.Translate API Key | yandex_translate_api_key{% endif %}
|
||||
|
||||
@@ -311,8 +311,8 @@ translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml,broken li
|
||||
translations/es-ES/data/reusables/actions/contacting-support.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,rendering error
|
||||
translations/es-ES/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error
|
||||
translations/es-ES/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/actions/settings-ui/settings-actions-runners.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/code-scanning/edit-workflow.md,broken liquid tags
|
||||
translations/es-ES/data/reusables/code-scanning/enabling-options.md,broken liquid tags
|
||||
|
||||
|
@@ -259,9 +259,9 @@ translations/ja-JP/data/reusables/dotcom_billing/lfs-remove-data.md,broken liqui
|
||||
translations/ja-JP/data/reusables/education/apply-for-team.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/actions-tab.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,Listed in localization-support#489
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,rendering error
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,Listed in localization-support#489
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,rendering error
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/pages-tab.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/enterprise_installation/upgrade-hardware-requirements.md,broken liquid tags
|
||||
|
||||
|
Reference in New Issue
Block a user