-
Notifications
You must be signed in to change notification settings - Fork 28
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
Make travis upload new versions of both dunai and bearriver to hackage #61
Comments
Stupid question. Is it not a problem that the password is public then? Btw, if you want to avoid duplicating the list of subpackages every time, you can do the thing described in https://docs.travis-ci.com/user/languages/haskell/#Build-Matrix. |
It won't be public. It'll be encrypted by Travis. But it'll be visible by anyone with commit access to the repo, which is why it's best to have a different user for this. |
Adds username, encrypted password and deploy specifications. Refs #61.
Adds username, encrypted password and conditions for deploy. Refs #61.
I just took a quick look. It seems to me that, since packages need to be compiled with a range of GHC versions, the cleanest way to do this would be to specify a build matrix that provides all possible combinations:
Is there a simpler way? (yes, we can eliminate |
I'm not sure about this, but we could try the following or a variant of it:
I'm not sure whether the ghc variable needs language haskell. And I'm not sure whether it is good to let travis organise the installation of the ghc instead of doing it on our own. |
You're absolutely right. I didn't know the current haskell image on travis had other versions of GHC installed (it didn't use to be the case). This simplifies the build process a lot. Thanks! |
@chriz-keera 's approach seems the right one to me. I don't think we need all those directives listed after |
Using language 'haskell', the variable ghc, and the default cabal defined by travis. Refs #61.
In order to simplify our lives, we could make travis automatically publish stable versions of packages on hackage. A new user has been created for this ( #59 ).
Example of how to do this is are in https://github.com/ivanperez-keera/Yampa/blob/develop/.travis.yml#L31-L38, and https://github.com/keera-studios/keera-hails/blob/master/.travis.yml#L86-L109.
The text was updated successfully, but these errors were encountered: