[Haskell-cafe] Connecting Travis CI and hackage

Alessandro Vermeulen a.vermeulen at students.uu.nl
Tue Jul 10 11:41:05 CEST 2012

You have full internet access on the Travis machines. The problem is that
you only have the data from your public repo. So you could upload the
package through the command line with cabal. But that means storing your
credentials in the public repository, which is a bad idea obviously.

In short: contact the people from Travis and they will be happy to help
you. Maybe you can store some environment variables in your account that
are made available for the build script.

- Alessandro
On Jul 8, 2012 7:28 PM, "Dmitry Malikov" <malikov.d.y at gmail.com> wrote:

> > But in the meantime, regarding what you suggest here, couldn't be done
> through tags rather than branches? Tagging a release version could trigger
> testing and, if testing runs fine, upload to hackage.
> Testing should be done on travis virtual machine. So this question is not
> about `when' or `where from' new release should be generated. It's about
> how uploading the new package to hackage could be done from the travis
> machine.
> --
> Best regards,
> dmitry malikov
> !
> ______________________________**_________________
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
> http://www.haskell.org/**mailman/listinfo/haskell-cafe<http://www.haskell.org/mailman/listinfo/haskell-cafe>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/haskell-cafe/attachments/20120710/32f00628/attachment.htm>

More information about the Haskell-Cafe mailing list