You can change default time limit in two ways job.<id>.timeout-minutes sets a timeout for a whole job job.<id>.steps.timeout-minutes sets a timeout for a single step Your scenario: my-job: runs-on: ubuntu-latest timeout-minutes: 30
I know you tried it with apt-get –allow-releaseinfo-change update but it worked for me. This is my command in the dockerfile: wget -q -O – https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add – \ && sh -c ‘echo “deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main” >> /etc/apt/sources.list.d/google.list’ \ && apt-get –allow-releaseinfo-change update \ && apt-get install -y google-chrome-unstable \ –no-install-recommends … Read more
As of July 7, 2020, you can now delete the results of individual workflow runs. To do this, navigate to your workflow, find the workflow run that you want to delete, and select the “…” menu. In this menu, select “Delete workflow run”. The workflow run and its logs will be removed. Currently, you must … Read more
Now it’s possible to have dependencies between workflows on Github Actions using workflow_run. Using this config, the Release workflow will work when the Run Tests workflow is completed. name: Release on: workflow_run: workflows: [“Run Tests”] branches: [main] types: – completed
I have a multi line command using backslash to separate the lines as follows: – name: Configure functions run: | firebase functions:config:set \ some.key1=”${{ secrets.SOME_KEY_1 }}” \ some.key2=”${{ secrets.SOME_KEY_2 }}” \ … Note the preceding ‘|’ character.
You can use the Github Actions upload-artifact and download-artifact to share data between jobs. In job1: steps: – uses: actions/checkout@v1 – run: mkdir -p path/to/artifact – run: echo hello > path/to/artifact/world.txt – uses: actions/upload-artifact@master with: name: my-artifact path: path/to/artifact And job2: steps: – uses: actions/checkout@master – uses: actions/download-artifact@master with: name: my-artifact path: path/to/artifact – run: … Read more
There are tools like the already-mentioned act, but they are not perfect. You are not alone with this issue. Similar problems are: how to test Jenkins builds locally how to test Circle CI builds locally how to test XXXX builds locally And my solution for these problems is: avoid functionalities provided by your CI tools … Read more
The original answer to this question used the Actions runner function set-env. Due to a security vulnerability set-env is being deprecated and should no longer be used. This is the new way to set environment variables. name: my workflow on: push jobs: build: runs-on: ubuntu-latest steps: – uses: actions/checkout@v2 – name: Set env run: echo … Read more
I’ve literally just come across this problem when trying to use IntelliJ to push to a branch that contains a GitHub Action workflow (YAML file in .github/workflows). I didn’t find existing resources on the Internet very helpful, so I hope this will help you fix it too. TL;DR: Update your Personal Access Token with the … Read more
You can add if: always() to your step to have it run even if a previous step fails https://docs.github.com/en/actions/learn-github-actions/expressions#status-check-functions so for a single step it would look like this: steps: – name: Build App run: ./build.sh – name: Archive Test Results if: always() uses: actions/upload-artifact@v1 with: name: test-results path: app/build Or you can add it … Read more