169 Resultados de la búsqueda para "runs-on"

nombres. YAML name: CI on: pull_request: branches: [ main ] jobs: build: runs-on: ubuntu-latest steps: - name: Checkout repository uses: actions/checkout@v4

schedule: - cron: 20 07 * * 1 jobs: create_issue: name: Create team sync issue runs-on: ubuntu-latest permissions: issues: write steps: - name: Create team sync

review". on: pull_request: types: - ready_for_review jobs: track_pr: runs-on: ubuntu-latest steps: # Uses the [actions/create-github-app-token](https://github

[push] permissions: id-token: write contents: read jobs: build-and-deploy: runs-on: ubuntu-latest steps: - name: 'Az CLI login' uses: azure/login@a1b2c3d4

Thursday at 15:45 UTC. on: push: schedule: - cron: '45 15 * * 4' jobs: build: runs-on: ubuntu-latest permissions: # required for all workflows security-events:

branches: [main] schedule: - cron: '15 5 * * 3' jobs: analyze: name: Analyze runs-on: ubuntu-latest permissions: security-events: write actions: read strategy:

las opciones predeterminadas de los pasos run para un trabajo jobs: job1: runs-on: ubuntu-latest defaults: run: shell: bash working-directory: ./scripts

read # This is required for actions/checkout jobs: S3PackageUpload: runs-on: ubuntu-latest steps: - name: Git clone the repository uses: actions/checkout@v4

needs. Cada trabajo se ejecuta en un entorno de ejecutor especificado por runs-on. Puedes ejecutar una cantidad ilimitada de trabajos siempre que estés dentro

jobs: setup-build-publish-deploy: name: Setup, Build, Publish, and Deploy runs-on: ubuntu-latest environment: production steps: - name: Checkout uses: actions/checkout@v4