racket / racket/slideshow

Add travis CI

Open
#13 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
38
Forks
20
PR merge metrics
No merged PRs in 30d

Description

I think this .travis.yml (adapted from racket/rackunit) is close to what racket/slideshow should use:

language: c

sudo: false

cache:
  directories:
  - $HOME/.racket/download-cache

env:
- PATH=~/racket/bin:$PATH

before_install:
- export PKG=`echo $TRAVIS_REPO_SLUG | cut -d '/' -f 2`
- echo $PKG
- curl -L -o installer.sh http://plt.eecs.northwestern.edu/snapshots/current/installers/min-racket-current-x86_64-linux-precise.sh
- sh installer.sh --in-place --dest ~/racket/

install:
- racket -l- pkg/dirs-catalog --link --check-metadata pkgs-catalog .
- echo file://`pwd`/pkgs-catalog/ > catalog-config.txt
- raco pkg config catalogs >> catalog-config.txt
- raco pkg config --set catalogs `cat catalog-config.txt`
- raco pkg install --auto $PKG
- ls $HOME/.racket/download-cache

script:
- raco test --drdr -c $PKG

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the proposed .travis.yml configuration and the repository's package name before setting up the Travis job. Use the listed install commands and run raco test --drdr -c $PKG; the work is done when Travis can install the package and the test command passes.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, ci-cd
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.