DevFW-CICD/backstage-edp
12
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

workflow cleanup

Browse source 
Signed-off-by: Omri Shiv <327609+OmriShiv@users.noreply.github.com>
This commit is contained in:
Omri Shiv 2024-05-13 10:08:53 -07:00
parent 8b4a3e67c8
commit 2b3f056857
1 changed files with 3 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
.github/workflows/build-and-push.yaml vendored
View file

@ -9,7 +9,7 @@ on:
# Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds.
env:
REGISTRY: ghcr.io
IMAGE_NAME: ${{ github.repository }}
IMAGE_NAME: ${{ github.repository }}:${{ github.sha }}
# There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
jobs:
@ -36,10 +36,8 @@ jobs:
id: meta
uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7
with:
images: |
${{ env.REGISTRY }}
tags: |
${{ env.IMAGE_NAME }}:${{ github.sha }}
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
# 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.