Skip to content

Commit

Permalink
CI: disable trilinos dev image for faster testing
Browse files Browse the repository at this point in the history
  • Loading branch information
ppraegla committed Jan 28, 2025
1 parent 9655712 commit effd310
Showing 1 changed file with 41 additions and 41 deletions.
82 changes: 41 additions & 41 deletions .github/workflows/trilinos-develop.yml
Original file line number Diff line number Diff line change
Expand Up @@ -22,49 +22,49 @@ concurrency:
cancel-in-progress: true

jobs:
build-and-push-trilinos-image:
runs-on: ubuntu-latest
# Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
permissions:
contents: read
packages: write
attestations: write
id-token: write
steps:
- name: Checkout repository
uses: actions/checkout@v4
# Uses the `docker/login-action` action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
- name: Log in to the Container registry
uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567 # v3.3.0
with:
registry: ghcr.io
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
# This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels.
- name: Extract metadata (tags, labels) for Docker
id: meta
uses: docker/metadata-action@8e5442c4ef9f78752691e2d8f8d19755c6f78e81 # v5.5.1
with:
images: ${{ env.IMAGE_NAME }}
labels: |
org.opencontainers.image.description=Image containing all the dependencies required for building and testing 4C based on the specified Trilinos commit ref
# This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
# It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
# It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
- name: Build and push Docker image
id: push
uses: docker/build-push-action@4f58ea79222b3b9dc2c8bbdd6debcef730109a75 # v6.9.0
with:
context: .
file: docker/trilinos_develop/Dockerfile
build-args: |
TRILINOS_VERSION=develop
push: true
tags: ${{ env.IMAGE_NAME }}:develop
labels: ${{ steps.meta.outputs.labels }}
# build-and-push-trilinos-image:
# runs-on: ubuntu-latest
# # Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
# permissions:
# contents: read
# packages: write
# attestations: write
# id-token: write
# steps:
# - name: Checkout repository
# uses: actions/checkout@v4
# # Uses the `docker/login-action` action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
# - name: Log in to the Container registry
# uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567 # v3.3.0
# with:
# registry: ghcr.io
# username: ${{ github.actor }}
# password: ${{ secrets.GITHUB_TOKEN }}
# # This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels.
# - name: Extract metadata (tags, labels) for Docker
# id: meta
# uses: docker/metadata-action@8e5442c4ef9f78752691e2d8f8d19755c6f78e81 # v5.5.1
# with:
# images: ${{ env.IMAGE_NAME }}
# labels: |
# org.opencontainers.image.description=Image containing all the dependencies required for building and testing 4C based on the specified Trilinos commit ref
# # This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
# # It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
# # It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
# - name: Build and push Docker image
# id: push
# uses: docker/build-push-action@4f58ea79222b3b9dc2c8bbdd6debcef730109a75 # v6.9.0
# with:
# context: .
# file: docker/trilinos_develop/Dockerfile
# build-args: |
# TRILINOS_VERSION=develop
# push: true
# tags: ${{ env.IMAGE_NAME }}:develop
# labels: ${{ steps.meta.outputs.labels }}

build:
needs: build-and-push-trilinos-image
# needs: build-and-push-trilinos-image
runs-on: ubuntu-latest
container:
image: ghcr.io/ppraegla/4c-dependencies-trilinos:develop
Expand Down

0 comments on commit effd310

Please sign in to comment.