Download to read offline
![▪
▪
name: CI
on:
push:
branches: [ main ]
jobs:
container-test-job:
runs-on: ubuntu-latest
container:
image: node:14.16
env:
NODE_ENV: development
ports:
- 80
volumes:
- my_docker_volume:/volume_mount
options: --cpus 1
steps:
- name: Check for dockerenv file
run: (ls /.dockerenv && echo Found
dockerenv) || (echo No dockerenv)](https://image.slidesharecdn.com/githubactions-221018062121-48ad3b02/85/BASTA-2022-GitHub-Actions-fur-Nutzer-der-Azure-DevOps-Pipelines-24-320.jpg)
Uploaded byMarc Müller
BASTA! 2022 - GitHub Actions für Nutzer der Azure DevOps Pipelines
The document outlines various aspects of integrating Microsoft Azure DevOps with GitHub, detailing project management features, continuous integration processes, and the use of reusable workflows in GitHub Actions. It explains how to set up GitHub runners, manage containers, and link work items between GitHub and Azure boards. Additionally, it discusses the security practices associated with DevSecOps in the context of Azure and GitHub integration.
More Related Content
Similar to BASTA! 2022 - GitHub Actions für Nutzer der Azure DevOps Pipelines
BASTA! 2022 - GitHub Actions für Nutzer der Azure DevOps Pipelines
- 3.
- 6.
- 7.
- 8.
- 9.
- 12.
- 13. Azure DevOps GitHub ProjectManagement Azure Boards Projects, Discussions, Issues Burndown Analytics Azure Boards GitHub Analytics Code Editing n/a Codespaces and github.dev Continuous Integration Azure Pipelines GitHub Actions Deploy & Release Azure Pipelines / Azure Artifacts GitHub Actions / GitHub Packages Manual testing Azure Test Plans n/a Code security n/a Advanced Security Analytics Analytics Service Insights
- 14.
- 16.
- 17. Workflow Event ▪ branch_protection_rule ▪ check_run ▪check_suite ▪ create ▪ delete ▪ deployment ▪ deployment_status ▪ discussion ▪ discussion_comment ▪ fork ▪ gollum ▪ issue_comment ▪ issues ▪ label ▪ milestone ▪ page_build ▪ project ▪ project_card ▪ project_column ▪ public ▪ pull_request ▪ pull_request_comment (use issue_comment) ▪ pull_request_review ▪ pull_request_review_comment ▪ pull_request_target ▪ push ▪ registry_package ▪ release ▪ repository_dispatch ▪ schedule ▪ status ▪ watch ▪ workflow_call ▪ workflow_dispatch ▪ workflow_run Job Step 1: Run action Step 2: Run script Step 3: Run action Step 4: Run action Job Step 1: Run action Step 2: Run script Step 3: Run script Step 4: Run action Runner Run actions Log results Runner Run actions Log results
- 18. Action Docker Container Action JavaScript ActionComposite Action
- 19.
- 20. Source: https://docs.github.com/en/actions/using-workflows/reusing-workflows name: Reusableworkflow example on: workflow_call: inputs: username: required: true type: string secrets: token: required: true jobs: example_job: name: Pass input and secrets to my-action runs-on: ubuntu-latest steps: - uses: ./.github/workflows/my-action with: username: ${{ inputs.username }} token: ${{ secrets.token }} jobs: call-workflow-1-in-local-repo: uses: octo-org/this-repo/.github/workflows/workflow-1.yml@172239021f7ba04fe7327647b213799853a9eb89 call-workflow-2-in-local-repo: uses: ./.github/workflows/workflow-2.yml call-workflow-in-another-repo: uses: octo-org/another-repo/.github/workflows/workflow.yml@v1
- 21. Reusable workflows Compositeactions Cannot call another reusable workflow Can be nested to have up to 10 composite actions in one workflow Can use secrets Cannot use secrets Can use if: conditionals Cannot use if: conditionals Can be stored as normal YAML files in your project Requires individual folders for each composite action Can use multiple jobs Cannot use multiple jobs Each step is logged in real-time Logged as one step even if it contains multiple steps Source: https://github.blog/2022-02-10-using-reusable-workflows-github-actions/
- 22. ▪ ▪ ▪ ▪ ▪ ▪ ▪ → Source: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners andhttps://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners
- 23. ▪ ▪ ▪ ▪ ▪ ▪ Virtual environment YAMLworkflow label Notes Windows Server 2022 windows- latest or windows- 2022 The windows-latest label currently uses the Windows Server 2022 runner image. Windows Server 2019 windows-2019 Ubuntu 22.04 ubuntu-22.04 Ubuntu 22.04 is currently in public beta. Ubuntu 20.04 ubuntu- latest or ubuntu- 20.04 Ubuntu 18.04 ubuntu-18.04 macOS Monterey 12 macos-12 macOS Big Sur 11 macos- latest or macos-11 The macos-latest label currently uses the macOS 11 runner image. macOS Catalina 10.15 macos-10.15 Source: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources
- 24. ▪ ▪ name: CI on: push: branches: [main ] jobs: container-test-job: runs-on: ubuntu-latest container: image: node:14.16 env: NODE_ENV: development ports: - 80 volumes: - my_docker_volume:/volume_mount options: --cpus 1 steps: - name: Check for dockerenv file run: (ls /.dockerenv && echo Found dockerenv) || (echo No dockerenv)
- 25.
- 26.
- 27.
- 30. Build Test Merge Automaticallyrelease to repository Automatically deploy to production
- 37.
- 38. Commit message Action FixedAB#123 Links and transitions the work item to the "done" state. Adds a new feature, fixes AB#123. Links and transitions the work item to the "done" state. Fixes AB#123, AB#124, and AB#126 Links to Azure Boards work items 123, 124, and 126. Transitions only the first item, 123 to the "done" state. Fixes AB#123, Fixes AB#124, Fixes AB#125 Links to Azure Boards work items 123, 124, and 126. Transitions all items to the "done" state. Fixing multiple bugs: issue #123 and user story AB#234 Links to GitHub issue 123 and Azure Source: https://docs.microsoft.com/en-us/azure/devops/boards/github/link-to-from-github?view=azure-devops
- 39.
- 41.
- 42.
- 43.
- 45.