We have updated our projects to Unity 2020.3.3f1 (from 2020.1.13f1) this week, and unfortunately all their respective build server jobs now fail; building same as lightmaps-baking.
They do not "fail" per se, but run endlessly after not finding the Articy-generated namespaces.
Here's the last part of Jenkins' output of building a project I set up for testing purposes:
- Code: Select all
(.. importing of all other assets except Articy content ..)
Assets\LeanTween\Framework\LeanTest.cs
Assets\LeanTween\Framework\LeanTween.cs
Assets\LeanTween\Framework\LeanTweenExt.cs
-----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/Assembly-CSharp.dll
Microsoft (R) Visual C# Compiler version 3.5.0-dev-20359-01 (8da8ba0c)
Copyright (C) Microsoft Corporation. All rights reserved.
Assets\Game\Scripts\Level\Articy\NPCRepository.cs(1,14): error CS0234: The type or namespace name 'Klib' does not exist in the namespace 'Articy' (are you missing an assembly reference?)
-----EndCompilerOutput---------------
- Finished script compilation in 7,407783 seconds
Assets\Game\Scripts\Level\Articy\NPCRepository.cs(1,14): error CS0234: The type or namespace name 'Klib' does not exist in the namespace 'Articy' (are you missing an assembly reference?)
AssetDatabase: script compilation time: 8.302238s
In this case I only accessed Articy content in one file (NPCRepository). In other projects there is a huge list of all other references to Articy namespaces not being found.
After these lines, building/baking is stuck and continues without progress until terminated manually.
This only happens after the upgrade to Unity 2020.3.3f1 and in fact if I go back to Unity 2020.1.13f1, everything works as expected, again.
Playing and building in the Unity editor itself works fine, as do build-server builds without Articy. But automated processes using
-articyImport (and
-articyQuit &
-articyPostImportMethod) appear to not work, anymore.
Articy Unity Importer is up do date (version 2.3.1).