791 Search results for "runs-on"

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

$default-branch ] pull_request: branches: [ $default-branch ] jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Run a one-line

Actions workflow. Jenkins Directives GitHub Actions agent jobs.<job_id>.runs-on jobs.<job_id>.container post None stages jobs steps jobs.<job_id>

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

# set this to an array of override file paths on: [push] jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Azure Login uses:

on the runner. YAML name: App build on: push jobs: build_with_signing: runs-on: macos-latest steps: - name: Checkout repository uses: actions/checkout@v4

concurrency keyword at the job level: on: push: branches: - main jobs: job-1: runs-on: ubuntu-latest concurrency: group: example-group cancel-in-progress: true

demonstrates how to use cargo build and cargo test in a job: YAML jobs: build: runs-on: ubuntu-latest strategy: matrix: BUILD_TARGET: [release] # refers to a cargo

workflow. Example: Setting default run step options for a job jobs: job1: runs-on: ubuntu-latest defaults: run: shell: bash working-directory: ./scripts

<job_id>.needs keyword. Each job runs in a runner environment specified by runs-on. You can run an unlimited number of jobs as long as you are within the workflow