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

gcc-trunk build daily? #68

Closed
marehr opened this issue May 22, 2020 · 1 comment
Closed

gcc-trunk build daily? #68

marehr opened this issue May 22, 2020 · 1 comment
Labels

Comments

@marehr
Copy link

marehr commented May 22, 2020

Can you add a version for the current trunk which builds from source (https://github.com/gcc-mirror/gcc)?

And rebuild gcc-trunk every night?

We would like to be able to see regressions before a new release happens and in my experience they get fixed the fastest if you report them early.

@wglambert
Copy link

docker-library/julia#25 (comment)

Similar issues: docker-library/official-images#1281, rust-lang/docker-rust#5, docker-library/docker#125

Any nightly or dev image in the official images would still need to maintain the repeatability aspect. All builds make heavy use of docker build cache so if the RUN line does not change, the image would not change. Base images get updates and cause dependent images to rebuild and we don't want those situations to cause a version bump to the main software of the image. The only other time an image gets built is via a commit in official-images that changes the respective library/ file. eggdrop is one image that has a develop build that they update once in a while (like docker-library/official-images#3051).

docker-library/php#825 (comment)
Nightly builds aren't something we can feasibly maintain so I'm going to close this though since there's nothing actionable right now given that we really can't do proper nightly builds effectively. That being said, it shouldn't be too hard for someone to take our Dockerfile and create an image that mirrors ours but builds directly from a specific commit from upstream and publish/maintain it under a separate organization for users to consume.

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

No branches or pull requests

2 participants