environment:
    global:
        # This will be used as part of the zipfile name
        PROJECT_NAME: djb_hash
    matrix:
        # Stable channel
        -   TARGET: i686-pc-windows-gnu
            CHANNEL: stable
        -   TARGET: i686-pc-windows-msvc
            CHANNEL: stable
        -   TARGET: x86_64-pc-windows-gnu
            CHANNEL: stable
        -   TARGET: x86_64-pc-windows-msvc
            CHANNEL: stable
        # Beta channel
        -   TARGET: i686-pc-windows-gnu
            CHANNEL: beta
        -   TARGET: i686-pc-windows-msvc
            CHANNEL: beta
        -   TARGET: x86_64-pc-windows-gnu
            CHANNEL: beta
        -   TARGET: x86_64-pc-windows-msvc
            CHANNEL: beta
        # Nightly channel
        -   TARGET: i686-pc-windows-gnu
            CHANNEL: nightly
        -   TARGET: i686-pc-windows-msvc
            CHANNEL: nightly
        -   TARGET: x86_64-pc-windows-gnu
            CHANNEL: nightly
        -   TARGET: x86_64-pc-windows-msvc
            CHANNEL: nightly

    # Install Rust and Cargo
    # (Based on from https://github.com/rust-lang/libc/blob/master/appveyor.yml)
install:
    - curl -sSf -o rustup-init.exe https://win.rustup.rs
    - rustup-init.exe --default-host %TARGET% --default-toolchain %CHANNEL% -y
    - set PATH=%PATH%;C:\Users\appveyor\.cargo\bin
    - rustc -Vv
    - cargo -V

    # 'cargo test' takes care of building for us, so disable Appveyor's build stage. This prevents
    # the "directory does not contain a project or solution file" error.
    # source: https://github.com/starkat99/appveyor-rust/blob/master/appveyor.yml#L113
build: false

    # Equivalent to Travis' `script` phase
    # TODO modify this phase as you see fit
test_script:
    - cargo build --verbose
    - cargo test

    #before_deploy:
    #    # Generate artifacts for release
    #    - cargo build --release
    #    - mkdir staging
    #    # TODO update this part to copy the artifacts that make sense for your project
    #    - copy target\release\hello.exe staging
    #    - cd staging
    #    # release zipfile will look like 'rust-everywhere-v1.2.3-x86_64-pc-windows-msvc'
    #    - 7z a ../%PROJECT_NAME%-%APPVEYOR_REPO_TAG_NAME%-%TARGET%.zip *
    #    - appveyor PushArtifact ../%PROJECT_NAME%-%APPVEYOR_REPO_TAG_NAME%-%TARGET%.zip
    #
    #deploy:
    #    description: 'Windows release'
    #    # All the zipped artifacts will be deployed
    #    artifact: /.*\.zip/
    #    # TODO Regenerate this auth_token for your project, this one won't work for you. Here's how:
    #    # - Go to 'https://github.com/settings/tokens/new' and generate a Token with only the
    #    # `public_repo` scope enabled
    #    # - Then go to 'https://ci.appveyor.com/tools/encrypt' and enter the newly generated token.
    #    # - Enter the "encrypted value" below
    #    auth_token:
    #        secure: xv0gNKR4j8Zyr3yFkqBADMdkR/6CMOp5ixVFc1uf8SHOndhTXHns4dPpQJKS6MWx
    #    provider: GitHub
    #    # deploy when a new tag is pushed and only on the stable channel
    #    on:
    #        # channel to use to produce the release artifacts
    #        # NOTE make sure you only release *once* per target
    #        # TODO you may want to pick a different channel
    #        CHANNEL: stable
    #        appveyor_repo_tag: true
    #
branches:
    only:
        - master
        # IMPORTANT Regex to match tags. Required, or appveyor may not trigger deploys when a new tag
        # is pushed. This regex matches semantic versions like v1.2.3-rc4+2016.02.22
        - /^v?\d+\.\d+\.\d+.*$/