-
Notifications
You must be signed in to change notification settings - Fork 182
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
Automated generation of new Dockerfiles and images #55
Comments
Any tutorials on how to do this ? |
no tutorials... i think a while ago we figured that we could get some sort of notification from swift build releases...i think ppl on swift mailing list liked the idea, but i don't think we got a follow up on it |
We should get this going :) |
Docker’s guidelines for official images advise against creating images from CI builds:
https://github.com/docker-library/official-images#library-definition-files Nevertheless, it’d be great to test current development snapshots of a specific version branch, e.g. Swift 4.2. Maybe these builds could be considered “release candidates”. Can someone check this with the official images maintainers? |
FYI, my repository(norionomura/swift) has been automated for Dockerfile update and image creation by using CircleCI 's scheduled workflow. |
@florianreinhart If I understand that document correctly, regular schedules aren't appropriate. How about some sort of automated script that checks whether a new version was released (not new commits, but full-fledged releases) and builds a new docker image? |
It's OK to automatically generate a new image whenever a new Swift version is released. I am just not sure about the Swift development releases generated from a development branch like swift-4.2-branch. These are generated by Swift CI almost every day. |
@swizzlr We are moving Swift Docker issues to https://bugs.swift.org Component: Docker. Can you please file your issue on bugs.swift.org? We are planning on closing GitHub swift-docker issues on Dec 20th, 2018 (PST). |
Currently every new release requires manual generation of new Dockerfiles and images.
Continuous integration using Travis CI, the RSS feed from the releases page and the nightly snapshots would allow this to happen.
Anybody want to take this on?
The text was updated successfully, but these errors were encountered: