Skip to content

ci: Update yamato templates #401

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Dec 11, 2020
Merged

ci: Update yamato templates #401

merged 8 commits into from
Dec 11, 2020

Conversation

JesseOlmer
Copy link
Contributor

  • Replaces our custom CI configuration with the standard Yamato configuration for multi-package repos
  • Introduces an (empty) Unity project where people can add functionality/tests they want to run as part of CI
  • Configures our tests to run against more platforms than previously (win, osx, ubuntu) with 2020.1 and trunk editors
  • Enables automatic test pass of the MLAPI package on pull request to develop branch

Other jobs (e.g. tests for other packages, package standards validation tests, publish to package registry) are still completely manually triggered.

Jesse Olmer added 5 commits December 9, 2020 15:53
Our custom CI configuration started failing after a change in the upm-ci tool. This change updates the CI configuration to use the standard templates for multi-package repositories. As a side effect, it also introduces a test/sample project where we can exercise the packages and put tests we don't want to ship with the packages themselves. Tests run against 2020.1 and trunk, on windows, mac, and ubuntu
The root gitignore removed all "packages" directories globally as a nuget-related ignore, but this has the unintended side-effect of ignoring a Unity project Packages folder, which is integral to how CI discovers the packages we build.

This change adds a targeted exception for the testproject Packages folder.
MLAPI package tests now trigger on pull request commits targeting develop
Added package tests to the "All Tests" job. Previous behavior was only project tests (which are currently empty)
Templating code was commented out incorrectly and so was still being executed. This caused a UI bug on the Yamato website displaying duplicates of the same jobs.

This change also removes the direct package test dependencies from the "all tests" job, as they're pulled in through the "badges test trigger" dependency on that job.
ci: Fixing some validation issues

ci: Fixed issues with description and exception

ci: Fixed error
…lates-fixes

ci: Fixes some validation issues
This change enables package validation (for the MLAPI package only) on pull request changes targeting develop branch.
@JesseOlmer JesseOlmer merged commit 726b77f into develop Dec 11, 2020
@JesseOlmer JesseOlmer deleted the ci/update-yamato-templates branch February 10, 2021 21:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants