Add Docker context path to docker/build-push-action@v1

[todor-ivanov]

Fixes #11641

Status

ready

Description

Adding a context path to the predefined docker/build-push-action@v1 GHAction.

NOTE: the so added option named path here differes between the module's versions. In v2 and beyond it is called context instead. I currently use v1. I did not update the version, because of the following WARING: we get:

Warning: Input 'repository' has been deprecated with message: v2 is now available through docker/build-push-action@v2

Which basically tells us, the repository option we use to tag those images is about to be deprecated in v2 and later. Which means it will affect how we are about to be setting our tags. This is something that did not want to get into in this very moment, so did not upgrade the module version we are using for this GHAction.

Is it backward compatible (if not, which system it affects?)

YES

Related PRs

None

External dependencies / deployment changes

None

[todor-ivanov]

Hi @amaltaro,
Could you please take a look. This is supposed to fix the changed working area for the docker/build-push-action. Unfortunately there is no other way to test it, but actually merge it and restart the ACtions.

[cmsdmwmbot]

Jenkins results:

• Python3 Unit tests: failed
  • 1 new failures
  • 1 tests no longer failing
  • 2 changes in unstable tests
• Python3 Pylint check: succeeded
• Pylint py3k check: succeeded
• Pycodestyle check: succeeded

Details at https://cmssdt.cern.ch/dmwm-jenkins/view/All/job/DMWM-WMCore-PR-test/14301/artifact/artifacts/PullRequestReport.html

[amaltaro]

Let us give it a try! Thanks

[todor-ivanov]

thanks @amaltaro