331 Résultats de la recherche pour "runs-on"

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

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:

Définition d’options d’étape run par défaut pour un travail jobs: job1: runs-on: ubuntu-latest defaults: run: shell: bash working-directory: ./scripts

containerDefinitions section of your task definition jobs: deploy: name: Deploy runs-on: ubuntu-latest environment: production steps: - name: Checkout uses: actions/checkout@v4

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

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

Chaque travail s’exécute dans un environnement d’exécuteur spécifié par runs-on. Vous pouvez exécuter un nombre illimité de travaux tant que vous respectez

consultez « Creating a JavaScript action ». jobs: job: environment: Production runs-on: ubuntu-latest steps: - name: Install OIDC Client from Core Package run:

name: WireGuard example on: workflow_dispatch: jobs: wireguard_example: runs-on: ubuntu-latest steps: - run: sudo apt install wireguard - run: echo "${{

and GITHUB_REF (Git ref) of the original event that triggered the workflow run. The workflow will use the privileges of the actor who initially triggered