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

Automated Releases #487

Closed
HorayNarea opened this issue Jun 3, 2018 · 3 comments
Closed

Automated Releases #487

HorayNarea opened this issue Jun 3, 2018 · 3 comments

Comments

@HorayNarea
Copy link
Member

It would be great if images from master and current release branches would be build and released on hub.docker.com automatically… other projects use TravisCI for this.

This would remove the delay between commiting fixes and receiving fixes AND would allow easier testing of master (one could imagine setting up a mailu-master on a server that pulls updates every few hours and sends/receives test mails -> alerting goes off if mails don't work)

@kaiyou what do you think about this, if you like the idea I could try to supply a rudimentary .travis.yml where you just have to add credentials for hub.docker.com

@kaiyou
Copy link
Member

kaiyou commented Jun 3, 2018

Actually all images for all branches are built automatically on Docker hub already. The (short) delay is mostly due to the build queue.

@HorayNarea
Copy link
Member Author

Oh, I didn't know that… sorry for the confusion :D

And what about automated testing? Currently one can not see if a PR will break something because TravisCI only builds the documention

@kaiyou
Copy link
Member

kaiyou commented Jun 28, 2018

For automated testing we still need a proper testing system. I believe #47 is one of the oldest issues on the matter, that we need to close first.

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

No branches or pull requests

2 participants