Skip to content
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

tag-latest: true not working #41

Closed
felipecrs opened this issue Feb 2, 2021 · 8 comments · Fixed by #50
Closed

tag-latest: true not working #41

felipecrs opened this issue Feb 2, 2021 · 8 comments · Fixed by #50

Comments

@felipecrs
Copy link
Contributor

Please see this build as example:

https://github.com/felipecrs/jenkins-agent-dind/runs/1812044006

Despite docker-meta receives "tag-latest: true" as input, the only tags generated are "master".

Also reported it #40 apparently.

@crazy-max
Copy link
Member

@felipecrs
Copy link
Contributor Author

felipecrs commented Feb 2, 2021

Got it. The docs says the tag-latest can be disabled if needed, but not deliberately enabled. Is that right?

Any tip on how I can achieve the same behavior as the Docker Hub Automated Build, pushing master branch to latest?

felipecrs added a commit to felipecrs/docker-images that referenced this issue Feb 2, 2021
@felipecrs
Copy link
Contributor Author

I believe the tag-latest input should be respected if provided by the user no matter what. To implement that, its default value must not be true anymore, then we treat the undefined cases.

This is very similar to an old PR I made to the legacy docker action: docker/github-actions#20

@crazy-max
Copy link
Member

@felipecrs I think you could specify a custom tag as latest in this case with tag-custom input. Or maybe we could handle 3 states for tag-latest: auto|true|false.

@felipecrs
Copy link
Contributor Author

@crazy-max Awesome. May I send a PR?

@beevelop
Copy link

I experienced the same issue and am actually trying to build the master branch as latest. If you have a dedicated repository for the Docker builds, you can work around this limitation by renaming the master branch to latest 🎩

@felipecrs
Copy link
Contributor Author

felipecrs commented Feb 12, 2021

As an alternative workaround you can do what I did at felipecrs/docker-images@1900c95.

@stale
Copy link

stale bot commented Mar 15, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants