Substitute curl with svn in gitHUb actions #11639
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Jenkins results:
|
amaltaro
approved these changes
Jul 5, 2023
|
@todor-ivanov we still have a problem with the github action workflows to create and upload docker images. Please have a look at this workflow log: I found this reference for the error message: Please deal with this with the highest priority, testbed upgrade must happen today. |
|
Hi @amaltaro thanks for merging this PR. Looking into the error in this very moment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #8797
Substitutes #11638 and dmwm/CMSKubernetes#1394
Status
ready
Description
With the current PR only the broken GitHub action is fixed. Which is - the lack of sub directory structure during the docker build process for all images in our CI?CD pipeline.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
None
External dependencies / deployment changes
None