.appveyor.yml

branches:
  only:
    - master

environment:

  matrix:

    # For Python versions available on Appveyor, see
    # http://www.appveyor.com/docs/installed-software#python
    # The list here is complete at the time of writing.

    #- PYTHON_VERSION: 2.7
    #  PYTHON: "C:\\Miniconda-x64"
    #  CATEGORY: "nightly"

    #- PYTHON_VERSION: 3.4
    #  PYTHON: "C:\\Miniconda34-x64"
    #  CATEGORY: "nightly"

    #- PYTHON_VERSION: 3.5
    #  PYTHON: "C:\\Miniconda35-x64"
    #  CATEGORY: "nightly"

    #- PYTHON_VERSION: 3.6
    #  PYTHON: "C:\\Miniconda36-x64"
    #  CATEGORY: "nightly"

    - PYTHON_VERSION: 2.7
      PYTHON: "C:\\Miniconda"
      CATEGORY: "nightly"
      EXTRAS: YES

    #- PYTHON_VERSION: 3.4
    #  PYTHON: "C:\\Miniconda34-x64"
    #  CATEGORY: "nightly"
    #  EXTRAS: YES

    - PYTHON_VERSION: 3.5
      PYTHON: "C:\\Miniconda35"
      CATEGORY: "nightly"
      EXTRAS: YES

    - PYTHON_VERSION: 3.6
      PYTHON: "C:\\Miniconda36"
      CATEGORY: "nightly"
      EXTRAS: YES

    - PYTHON_VERSION: 3.7
      PYTHON: "C:\\Miniconda37"
      CATEGORY: "nightly"
      # [191115]: disable extras because of installation dependency 
      # issues with Miniconda 3.7 on appveyor
      #EXTRAS: YES


install:
  - "SET PATH=%PYTHON%;%PYTHON%\\Scripts;%PYTHON%\\Library\\bin;%PATH%"
  - "where python"
  - "where pip"
  - python --version
  - "SET PIP=%PYTHON%\\Scripts\\pip"
  - "%PIP% --version"
  #
  # Set standardized ways to invoke conda for the various channels.  We
  # are seeing strange issues where conda-forge and cachemeorg are
  # fighting with anaconda over the version of core packages (notably,
  # conda).  The following prevents conda-forge and cacheme.org from
  # overriding anaconda.
  #
  - SET CONDA_INSTALL=conda install -q -y
  - "SET ANACONDA=%CONDA_INSTALL% -c anaconda"
  - "SET CONDAFORGE=%CONDA_INSTALL% -c conda-forge --no-update-deps"
  #
  # Determine if we will use Appveyor's Miniconda or install Anaconda
  # (intermittently one or the other suffers from NumPy failing to load the
  # MKL DLL; See #542, #577
  #
  - SET USING_MINICONDA=1
  #
  # Update conda, then force it to NOT update itself again
  #
  # Somehow, the update from anaconda stalls for Python 3.4. So we're not specifying the channel here.
  #
  - conda config --set always_yes yes
  #- conda update -q -y conda
  - conda config --set auto_update_conda false
  #
  # If we are using full Anaconda instead of Appveyor's MiniConda,
  # install it
  #
  - IF NOT DEFINED USING_MINICONDA (conda install anaconda)
  #
  # Create a virtual environment for this build
  #
  #- conda create -n pyomo_test_env python=%PYTHON_VERSION%
  #- activate pyomo_test_env
  #- "SET CONDAENV=%PYTHON%\\envs\\pyomo_test_env"
  - "echo %PATH%"
  #
  - "SET ADDITIONAL_CF_PKGS=setuptools coverage sphinx_rtd_theme"
  #
  # Install extra packages (formerly pyomo.extras)
  #
  #   If we are using Miniconda, we need to install additional packages
  #   that usually come with the full Anaconda distribution
  #
  - SET MINICONDA_EXTRAS=""
  - IF DEFINED USING_MINICONDA (SET MINICONDA_EXTRAS=numpy scipy ipython openpyxl sympy pyodbc pyyaml networkx xlrd pandas matplotlib dill seaborn)
  #
  - "IF DEFINED EXTRAS (SET ADDITIONAL_CF_PKGS=%ADDITIONAL_CF_PKGS% pymysql pyro4 pint pathos %MINICONDA_EXTRAS%)"
  #- "IF DEFINED EXTRAS (%CONDAFORGE% mkl)"
  #
  # Finally, add any solvers we want to the list
  #
  - "SET ADDITIONAL_CF_PKGS=%ADDITIONAL_CF_PKGS% glpk ipopt"
  #
  # ...and install everything from conda-force in one go
  #
  - "%CONDAFORGE% %ADDITIONAL_CF_PKGS%"
  #
  # While we would like to install codecov using conda (for
  # consistency), there are cases (most recently, in Python 3.5) where
  # the installation is not reliable and codecov is not available after
  # being installed.
  #
  - "python -m pip install --upgrade pip"
  - "%PIP% --version"
  - "%PIP% install codecov"
  #
  # Install GAMS
  #
  - ps: Start-FileDownload 'https://d37drm4t2jghv5.cloudfront.net/distributions/24.8.5/windows/windows_x64_64.exe'
  - windows_x64_64.exe /SP- /VERYSILENT /NORESTART /DIR=.\gams /NOICONS
  - "SET PATH=%cd%\\gams;%PATH%"
  #
  # Clone but don't install pyomo-model-libraries
  #
  - "git clone https://github.com/Pyomo/pyomo-model-libraries.git"
  - "%PIP% install git+https://github.com/PyUtilib/pyutilib"
  - "python setup.py develop"

  # Set up python's coverage for covering subprocesses (important to do
  # here because we want coverage of the download scripts below)
  #
  - "SET BUILD_DIR=%cd%"
  - "SET COVERAGE_PROCESS_START=%BUILD_DIR%\\coveragerc"
  - "copy %BUILD_DIR%\\.coveragerc %COVERAGE_PROCESS_START%"
  - "echo data_file=%BUILD_DIR%\\.coverage >> %COVERAGE_PROCESS_START%"
  - python -c "from distutils.sysconfig import get_python_lib; import os; FILE=open(os.path.join(get_python_lib(),'run_coverage_at_startup.pth'), 'w'); FILE.write('import coverage; coverage.process_startup()'); FILE.close()"

  # Configure Pyomo to put the configuration directory here (so that it
  # is both writable, and will be cleared between test runs
  - "SET PYOMO_CONFIG_DIR=%BUILD_DIR%\\config"

  # Fetch additional solvers
  #
  - "pyomo download-extensions"

  # Report relevant package versions
  #
  - "glpsol -v"
  - "ipopt -v"
  - python --version

build: off


test_script:
  # Put your test command here.
  # If you don't need to build C extensions on 64-bit Python 3.3 or 3.4,
  # you can remove "build.cmd" from the front of the command, as it's
  # only needed to support those cases.
  # Note that you must use the environment variable %PYTHON% to refer to
  # the interpreter you're using - Appveyor does not do anything special
  # to put the Python evrsion you want to use on PATH.
  #
  # This block of commands enable tracking of coverage for any
  # subprocesses launched by tests
  - "SET BUILD_DIR=%cd%"
  - "SET COVERAGE_PROCESS_START=%BUILD_DIR%\\coveragerc"
  # Configure Pyomo to put the configuration directory here (so that it
  # is both writable, and will be cleared between test runs
  - "SET PYOMO_CONFIG_DIR=%BUILD_DIR%\\config"

  # Run Pyomo tests
  - "test.pyomo -v --cat=%CATEGORY% pyomo %BUILD_DIR%\\pyomo-model-libraries"

  # Run documentation tests
  #- "nosetests -v --with-doctest --doctest-extension=.rst doc\\OnlineDocs"


#after_test:
  # This step builds your wheels.
  # Again, you only need build.cmd if you're building C extensions for
  # 64-bit Python 3.3/3.4. And you need to use %PYTHON% to get the correct
  # interpreter
  #- "build.cmd %PYTHON%\\python.exe setup.py bdist_wheel"


#artifacts:
  # bdist_wheel puts your built wheel in the dist directory
  #- path: dist\*


on_success:
  #  You can use this step to upload your artifacts to a public website.
  #  See Appveyor's documentation for more details. Or you can simply
  #  access your wheels from the Appveyor "artifacts" tab for your build.
  #
  # Combine coverage reports over all subprocesses
  - "cd %BUILD_DIR%"
  - dir .cov*
  - "coverage combine %BUILD_DIR%"
  # On some appveyor platforms, the codecov script does not appear to be
  # in the PATH.  We will directly import the module (installed above)
  - python -m codecov -X gcov