vscode-azurefunctions/.travis.yml

language: node_js

node_js:
  - 'stable'

addons:
  apt:
    packages:
    - gettext
    - libcurl4-openssl-dev
    - libicu-dev
    - libssl-dev
    - libunwind8
    - zlib1g

before_install:
  - if [ $TRAVIS_OS_NAME == "linux" ]; then
      export CXX="g++-4.9" CC="gcc-4.9" DISPLAY=:99.0;
      sh -e /etc/init.d/xvfb start;
      sleep 3;
    fi

  # Install dotnet cli and add to path
  - export DOTNET_INSTALL_DIR="$HOME/.dotnet"
  - curl -sSL https://dot.net/v1/dotnet-install.sh | bash /dev/stdin --version 2.0.0 --install-dir "$DOTNET_INSTALL_DIR"
  - export PATH="$DOTNET_INSTALL_DIR:$PATH"

install:
  - npm install

script:
  - gulp package
  - gulp upload-vsix
  - npm run lint
  - gulp test

notifications:
  email:
    on_success: never
    on_failure: always
Add functions explorer Refresh command and display subscriptions 2017-09-22 02:20:07 +03:00			`language: node_js`

			`node_js:`
			`- 'stable'`

Add support for C# Class library projects (#161) This supports project/function creation and local debugging. It does not include deploy logic. A brief summary: 1. We default C# projects to beta runtime and class library (instead of C# script) 1. We use dotnet templates for project/function creation. We will automatically install the templates for the user if they are not on their machine (I don't prompt at all - let me know if you think we should prompt). 1. We use the parameter information from the functions portal (Aka C# Script templates) since it's easier to parse than the dotnet cli and it gives us more information (like validation). This requires us to assume that parameters for C# Scripts are the same as the parameters for the C# Class libraries. Since that might not always be the case, I mitigated this with unit tests and hard-coding the version of the dotnet templates. 1. Unlike JavaScript debugging, we have to attach to a specific process instead of attaching with a port. I implemented a 'pickProcess' command to search for the functions host process. 1. This only works on Windows. There's a few issues on a Mac I still need to iron out. 2018-01-12 04:37:52 +03:00			`addons:`
			`apt:`
			`packages:`
			`- gettext`
			`- libcurl4-openssl-dev`
			`- libicu-dev`
			`- libssl-dev`
			`- libunwind8`
			`- zlib1g`

Refactor error handling and add unit tests for the first time 2017-10-12 23:51:13 +03:00			`before_install:`
			`- if [ $TRAVIS_OS_NAME == "linux" ]; then`
			`export CXX="g++-4.9" CC="gcc-4.9" DISPLAY=:99.0;`
			`sh -e /etc/init.d/xvfb start;`
			`sleep 3;`
			`fi`

Add support for C# Class library projects (#161) This supports project/function creation and local debugging. It does not include deploy logic. A brief summary: 1. We default C# projects to beta runtime and class library (instead of C# script) 1. We use dotnet templates for project/function creation. We will automatically install the templates for the user if they are not on their machine (I don't prompt at all - let me know if you think we should prompt). 1. We use the parameter information from the functions portal (Aka C# Script templates) since it's easier to parse than the dotnet cli and it gives us more information (like validation). This requires us to assume that parameters for C# Scripts are the same as the parameters for the C# Class libraries. Since that might not always be the case, I mitigated this with unit tests and hard-coding the version of the dotnet templates. 1. Unlike JavaScript debugging, we have to attach to a specific process instead of attaching with a port. I implemented a 'pickProcess' command to search for the functions host process. 1. This only works on Windows. There's a few issues on a Mac I still need to iron out. 2018-01-12 04:37:52 +03:00			`# Install dotnet cli and add to path`
			`- export DOTNET_INSTALL_DIR="$HOME/.dotnet"`
			`- curl -sSL https://dot.net/v1/dotnet-install.sh \| bash /dev/stdin --version 2.0.0 --install-dir "$DOTNET_INSTALL_DIR"`
			`- export PATH="$DOTNET_INSTALL_DIR:$PATH"`

Add functions explorer Refresh command and display subscriptions 2017-09-22 02:20:07 +03:00			`install:`
			`- npm install`

			`script:`
Generate and upload vsix to storage (#271) 2018-03-12 21:07:46 +03:00			`- gulp package`
			`- gulp upload-vsix`
Refactor error handling and add unit tests for the first time 2017-10-12 23:51:13 +03:00			`- npm run lint`
Move test to gulp instead of npm 2018-01-11 22:07:59 +03:00			`- gulp test`
Add functions explorer Refresh command and display subscriptions 2017-09-22 02:20:07 +03:00
			`notifications:`
			`email:`
			`on_success: never`
Move test to gulp instead of npm 2018-01-11 22:07:59 +03:00			`on_failure: always`