-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Using nightly builds on Travis CI is broken #5836
Comments
@matiasgarciaisaia @bcardiff 1 week l8r... ping? |
Ping again... 🕦 🌙 💤 |
The former nightly packages were kept by @jhass and probably that process had a hiccup. It is not yet using the nightly automated build from circle ci. We are looking forward to try some service for hosting the distro repo. Or if that timeout integrate something manually in S3 as it's done in the former release packages. Meanwhile, wither @jhass jumps in the discussing, or docker nightlies need to be used. |
The spare machine I could use is actually gone, sorry. |
It's fine, so the nightly.crystal-lang.org domain should be redirected something else, right @jhass? The packages there were unsigned or it was using some key? |
Yeah. They were signed by a subkey of the one used for the main APT repo. I can check later this evening if I can still find it, if needed. |
Regarding hosting debian packages on S3, I've found some resources which could help with that: |
We already host debian packages on s3 for the releases. We should just ask travis to change how the |
That is ask Travis just means sending a pull request to travis-build |
Yes, and to do that we need to have an |
Actually if you'd keep the same domain and gpg key, the PR to |
@jhass if you had chance to find the certificate for nightly send it to me / follow up by email. I was waiting for news from https://bintray.com/ for OSS projects and use nightlies there and see if it could be used to automate publishing of all releases. @Sija the options you send only support .deb packages. |
@bcardiff yes, and what else is needed? |
For travis nothing else. But if we aim for nightlies in the same platforms as the official packages then, they are not enough as a complete solution. Worst case we host them in S3 but we want to check if a services may come handy. |
@bcardiff my personal grief is stated in the original post, that is, using nightlies on travis, I also believe that would cover majority of use-cases for nightly builds. On my local machine I have no problem with compiling crystal myself, I don't need packaged nightlies for that. Of course that would be neat and all, but is it worth the hassle? |
Just a note: For the time being, you can also use this script to install Crystal nightly from circle ci artifacts: https://gist.github.com/straight-shoota/a2f4b29203936c04c578d6f6a1ad5f9b |
@bcardiff Anything going on with this? |
@Sija Not yet. The workaround for now is to use docker nightly images or the script, but in travis would be easier to use docker nightly |
Any guide on how to run a shard build on Travis with crystal nightly docker image? Should I include a |
https://bintray.com supports OSS now, as seen on their website |
@vladfaust Just follow the guides to using docker images in your build: https://docs.travis-ci.com/user/docker/ and use image |
There are difficulties if need to test against databases with docker approach. I wonder why |
Bintray looks promising, especially with free OSS package... Perhaps it's the time to re-evaluate the situation? 🏓 @bcardiff |
Nightly builds are currently broken. See: - https://travis-ci.community/t/crystal-and-shards-commands-are-not-installed-properly-in-crystal-nightly/2502 - crystal-lang/crystal#5836
Any update on this? |
- Nightly build is currently not working. See crystal-lang/crystal#5836
Using nightly builds on Travis CI has been advertised in docs for Crystal language for some time now, yet ATM it doesn't work.
Refs: https://github.com/travis-ci/travis-build/blob/b2a89dad8e7020c4c28b396639b36d87e5b1d4f6/lib/travis/build/script/crystal.rb#L80
Without nightly releases users caring about having their codebase tested on Travis CI against current Crystal are left with 3 less-than-optimal-options:
but!—fixed in Use crystallang/crystal:nightly tag for nightly releases on docker #5837nightly
is 11 days old as of now, and new builds are tagged withnightly-YYYYMMDD
scheme, making it hard to point at just that last releaseSince nightly releases are being build as of #5182, the only thing missing would be hooking this up to apt package index, which is used by Travis CI.
With that in place we'd be able to use nice'n'simple
.travis.yml
:Howgh! Thanks for reading!
The text was updated successfully, but these errors were encountered: