• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

wooga / atlas-unity / 4 / 2
90%
master: 52%

Build:
Build:
LAST BUILD BRANCH: PR-148
DEFAULT BRANCH: master
Ran 20 Mar 2019 08:06AM UTC
Files 28
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

20 Mar 2019 08:06AM UTC coverage: 87.352% (-2.4%) from 89.723%
4.2

push

jenkins

Fix unity 2019 logfile handling

Description
===========

Unity 2019 changed the behavior of the `-logFile` switch. To print to
`stdout` we must provide `-` as the file path which signals Unity to
print the log to `stdout`. This behavior works also on windows now so I
enabled the logoutput on windows when the Unity version is >= 2019.

Most of the test setup is very brittle at the moment. The tests don't
run with a real Unity installation because of setup and runtime
considerations. The way I path the unity version for tests is not
optimal and will change in the future.

To execute the version check for all batchmode actions, I added a
`protected` getter to fetch the Unity version beeing executed. I still
use the `ArtifactVersion` object but I have plans to change this in the
future and make this part of the public API.

Changes
=======

![FIX] ![UNITY] 2019 logfile handling
![ADD] [unity-version-manager-jni] as dependency to fetch the Unity version

[unity-version-manager-jni]:    https://github.com/wooga/unity-version-manager-jni

663 of 759 relevant lines covered (87.35%)

0.87 hits per line

Source Files on job 4.2
  • Tree
  • List 0
  • Changed 28
  • Source Changed 28
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 4
  • f82e739d on github
  • Prev Job for on PR-52 (#3.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc