Revisando logs para debuggear errores con GitHub Actions

Curso de GitHub Actions

Conoce Github Actions

Qué aprenderás de GitHub Actions

Qué son GitHub Actions y qué es CI/CD

Conceptos básicos del flujo de trabajo con GitHub Actions

Quiz: Conoce Github Actions

Creación de Workflow Files

Creando tu primer workflow file con GitHub Actions

Cómo es la sintaxis de workflow files

Triggers: eventos que inician workflows en GitHub Actions

Expresiones para agregar lógica a un workflow

Uso de contexto para acceder a información sobre un workflow

Uso de variables para almacenar información para reutilizar en un workflow

Secrets: almacena información confidencial para reutilizar en un workflow

Quiz: Creación de Workflow Files

Como encontrar bugs en un workflow

Revisando logs para debuggear errores con GitHub Actions

Quiz: Como encontrar bugs en un workflow

Casos de Uso de GitHub Actions

Integración continua CI: Test

Integración continua CI: Compilación

Despliegue continuo CD: Desplegar apps

Automatización de procesos con GitHub Actions

Buenas prácticas al usar GitHub Actions

Costos y facturación en GitHub Actions

Quiz: Costos y facturación en GitHub Actions

Cierre

Recapitulación del curso: qué aprendiste de GitHub Actions

You don't have access to this class

Keep learning! Join and start boosting your career

If you already have an account,

Resources

To configure a Workflow File with an Action that requires a Secret, you must follow these steps:

Open the GitHub Marketplace and search for the Action you want to use. In this case, we will use the Action "Deploy Docker to AWS, EasyTo".
In the Action's documentation, look for the Workflow File example provided. This example shows how to configure the Workflow File to deploy a Docker application to an AWS S2 instance.
Review the configuration examples. In this case, the Workflow File has a name "Basic Deploy" and is configured to run every time a push to the main branch of the repository is performed.
The Workflow File has a job named "deploy" which is in charge of deploying to the EasyTo instance. This job uses the Action "GitHub Actions Deploy Docker to EasyTo" with version 0.5.0.
In the configuration step of the Action, the use of environment variables called "access key ID", "secret access key", "default region" and "default region" is indicated.

Contributions 3

Questions 0

Sort by:

Want to see more contributions, questions and answers from the community?

Julio César Cid

2 years ago

Cada job corre en un runner distinto, eso significa que son máquinas virtuales diferentes y una no tiene acceso a la otra

Haward Rafael Tillero Jimenez

2 years ago

Con Docker

name: Docker
on:
  push

jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      -
        name: Checkout
        uses: actions/checkout@v3
      -
        name: Set up QEMU
        uses: docker/setup-qemu-action@v2
      -
        name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v2
      -
        name: Login to Docker Hub
        uses: docker/login-action@v2
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}

Luis Eduardo

a year ago

hay actions para usar secrets con vault, que es una herramienta especializada de hashicorp, de los creadores de terraform, para hacer SingleResponsability de la administración de secrets.