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

Support versioning #10

Open
eine opened this issue Aug 19, 2019 · 0 comments
Open

Support versioning #10

eine opened this issue Aug 19, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@eine
Copy link
Collaborator

eine commented Aug 19, 2019

Currently, all images are rolling releases, i.e. all of them are automatically updated if the corresponding travis job succeeds.

On the one hand, the 'buildtest' branches (mcode, mcodegpl, llvm and gcc) run the default testsuite before pushing the images. This ensures that fundamentally broken images are not pushed to dockerhub. Still, uncaught regressions might find their way.

On the other hand, most of the images created in branches master, synth and ext are unversioned. Some of them are very experimental (most of synth), but some other are expected to be used in "production" (i.e. vunit job in ext, see ghdl/ghdl#883).

Therefore, even though users can use digests to fix their scripts to specific images, it would be desirable to include some kind of versioning. We need to think it thoroughly, tho; supporting images for simulation, synthesis and/or LSP is starting to get complex!

@eine eine added the enhancement New feature or request label Jan 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant