On Thu, Aug 20, 2015 at 11:11:40PM +0300, Nikita Karetnikov wrote: > So I did some work on our "CI system": > > https://git.gnu.io/nkaretnikov/snowdrift-ci/commits/master
Neat! > <snip> > What surprised me is that I was unable to call it via stack exec even > when I stack-installed it. Locally, I can do it after running stack > build, but I have a different version and OS. Moreover, calling sdm > this way on the server seems to work. I'll investigate later. stack install (aka stack build --copy-bins) puts the binaries in ~/.local/bin. After a stack install, ensure that directory is on your $PATH and you should be able to run it directly. There's also a related stack issue[1]. Right now, stack ghci (and maybe stack exec?) don't fetch dependencies, so stack build needs to be run first. [1]: https://github.com/commercialhaskell/stack/issues/629 > So, what's next? > > * Create a dummy merge request and repeat the same procedure and try to > figure out why it fails. > > * Map port 8080 to 80 and add the server on git.gnu.io, so snowdrift-ci > could receive JSON data. This part hasn't been tested at all. We should use keter or nginx to proxy, incidentally. > * Again, the key needs to be added to ssh-agent before starting > snowdrift-ci. Otherwise, snowdrift-ci will halt waiting for your > input. I think this should be completely automated eventually, but let's not worry about it yet. > <snip> > * A system user must be able to use sudo without a password because it's > required by sdm. Yet another good reason to clean up sdm! > * Is it okay to put the full build log in a comment? If not, I'd > suggest to cut the first 80% when the build is successful. What do > you think? Would you like to cut it always? Like Aaron said, I think providing a link is best.
signature.asc
Description: Digital signature
_______________________________________________ Dev mailing list [email protected] https://lists.snowdrift.coop/mailman/listinfo/dev
