rpcs3/.travis/travis.env

# Variables set by Travis CI
TRAVIS_PULL_REQUEST
TRAVIS_BRANCH
TRAVIS_COMMIT
# Variables set by Azure Pipelines
BUILD_REASON
BUILD_SOURCEVERSION
BUILD_ARTIFACTSTAGINGDIRECTORY
BUILD_REPOSITORY_NAME
BUILD_SOURCEBRANCHNAME
# Variables for Travis build matrix
COMPILER
DEPLOY_APPIMAGE
# Private Travis CI variables
GITHUB_TOKEN
Migrate to seperate file for environmental variables 2018-12-30 16:37:43 -08:00			`# Variables set by Travis CI`
			`TRAVIS_PULL_REQUEST`
			`TRAVIS_BRANCH`
			`TRAVIS_COMMIT`
Properly setup Azure Pipelines using current system Also sets up Azure artifacts (including for PRs) for AppImages 2020-03-02 18:42:28 -08:00			`# Variables set by Azure Pipelines`
			`BUILD_REASON`
			`BUILD_SOURCEVERSION`
			`BUILD_ARTIFACTSTAGINGDIRECTORY`
CI: Port Windows build to Azure Pipelines (#7757) * CI: Port Windows build to Azure Pipelines from Appveyor * CI: Split Windows build into scripts * CI: Remove Appveyor * CI: Add GitHub Release deployment to Azure Windows Build * VCS: Add full branch name function to rpcs3_version The STRINGIZE macro was a little awkward, and difficult to control at configure time. Since other version information is already included, the full branch name is now added as a function. It's runtime instead of compile-time checking, but it seems worth it. * CI: Overhaul Windows setup script Previously, there was no way of forcing a re-download of cached dependencies when they were replaced by new ones. In addition, there was really no verification of downloads or cache. Now, changing a few lines at the top of the file will automagically force a cache update. 2020-03-27 06:37:27 -07:00			`BUILD_REPOSITORY_NAME`
			`BUILD_SOURCEBRANCHNAME`
Migrate to seperate file for environmental variables 2018-12-30 16:37:43 -08:00			`# Variables for Travis build matrix`
			`COMPILER`
			`DEPLOY_APPIMAGE`
			`# Private Travis CI variables`
			`GITHUB_TOKEN`