-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for multiple tags? #29
Comments
@andmos This seems to be a good feature request 👍 |
From what I can see here, it might be that the tagging must be a separate tag step. Not sure if Line 38 in 4b558c7
|
Here is an example of this done in Bash from a custom Action I've used: set -e
if [ "$5" = "" ]; then
echo "Skipping login for image pull - username not set."
else
echo "Credentials for builder image registry detected - logging in."
# echo "$6" | docker login "$4" --username "$5" --password-stdin
fi
# We will always need to login to the registry we intend to push to
#echo "$9" | docker login "$7" --username "$8" --password-stdin
# Grab builder image
docker pull "$2"
# Build
s2i build "$1" "$2" "$3"
TAGS="${10}"
if [ "$TAGS" = "" ]; then
echo "Skipping custom tagging, using latest - tags not set."
else
for TAG in ${TAGS//,/ }
do
echo "Tagging image ${3} with ${TAG}"
docker tag "${3}" "${3}:${TAG}"
done
fi
# Push to output registry
docker push "$3" |
Yeah, we did the same way in buildah-build action. |
I am going to use |
Also added outputs |
@andmos you should be able to use this feature in |
Question
Not sure if this is a bug or a feature request, so I'm doing it as a question 😄
I want to use the
s2i-build
action, but we need to tag the image with multiple tags. So far as I can see, this action does not support it?My initial thought was to use the
push-to-registry
action to do all the tagging (sincepush-to-registry
support a list of tags), but it looks likepush-to-registry
needs a 1 to 1 mapping between tags to push.Anything I'm missing here, or does this go as a feature request to support multiple tags? 😄
The text was updated successfully, but these errors were encountered: