There is a broader plan, about having Hackage2 (in development) and scoutess (same) work together, but we're not there yet *at all*.
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. On Sun, Jul 8, 2012 at 1:21 PM, Dmitry Malikov <[email protected]>wrote: > *tldr*: is there a way to upload package to hackage from Travis > automatically and safely (hiding password to hackage account)? > > Several days ago I discovered Travis ( http://travis-ci.org/ ) - nice > open source build-service, easy to start and monitoring. > I've configured some github projects and add build status to it's readme. > It's usable to know how is your haskell package building on separate fresh > machine. > > Following git-flow developing model there is a develop branch for > snapshots and master branch for release. That why every commit in master > branch should produce new release build ⇒ every commit in master branch > should produce new hackage build upload. And also it will be nice to have > that routine process done automatically. > > It could be done using cabal-upload tool and --username and --password > options. But it means that .travis.yml file should contain my > hackage-password explicitly. > How can I avoid that? > > -- > Best regards, > dmitry malikov > ! > > > _______________________________________________ > Haskell-Cafe mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/haskell-cafe > > -- Alp Mestanogullari
_______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
