wooga / atlas-unity

89%

master: 52%

LAST BUILD ON BRANCH PR-75

branch: PR-75

CHANGE BRANCH

x

Reset

• PR-75
• PR-100
• PR-101
• PR-102
• PR-104
• PR-106
• PR-107
• PR-108
• PR-109
• PR-110
• PR-111
• PR-112
• PR-113
• PR-115
• PR-116
• PR-118
• PR-119
• PR-121
• PR-122
• PR-123
• PR-124
• PR-125
• PR-126
• PR-127
• PR-128
• PR-129
• PR-131
• PR-132
• PR-133
• PR-134
• PR-135
• PR-136
• PR-137
• PR-138
• PR-139
• PR-140
• PR-141
• PR-142
• PR-143
• PR-144
• PR-146
• PR-147
• PR-148
• PR-150
• PR-151
• PR-35
• PR-37
• PR-40
• PR-41
• PR-42
• PR-43
• PR-45
• PR-46
• PR-47
• PR-48
• PR-49
• PR-52
• PR-53
• PR-54
• PR-55
• PR-59
• PR-60
• PR-61
• PR-62
• PR-64
• PR-65
• PR-66
• PR-67
• PR-69
• PR-72
• PR-73
• PR-74
• PR-76
• PR-77
• PR-79
• PR-80
• PR-81
• PR-82
• PR-83
• PR-84
• PR-86
• PR-87
• PR-91
• PR-92
• PR-93
• PR-94
• PR-95
• PR-96
• PR-97
• PR-98
• PR-99
• master
• release/2.x

Allow batchmode configuration for Test task

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

For years batchmode for edit and playmode tests was set to `true`
due to some issues with Unity when not running them with a full
Editor. We changed that to hardcode default to a `true` value when
the editor version used is newer than 2018.

Some teams would like to configure the plugin to run edit/playmode tests
without batchmode flag for some setups. This patch adds additional
properties for the plugin extension to easily set this for a range of
generated tasks.

```groove
unity {
    batchModeForEditModeTest = true
    batchModeForPlayModeTest = false
}
```

This extension variables can be set also via environment/gradle properties

`unity.batchModeForEditModeTest`
`UNITY_BATCH_MODE_FOR_EDIT_MODE_TEST=YES`
`unity.batchModeForPlayModeTest`
`UNITY_BATCH_MODE_FOR_PLAY_MODE_TEST=YES`

Changes
=======

* ![IMPROVE] allow batchmode configuration for `Test` task