文档

​
​

Development

User Acquisition

Monetization

工业

Unity Version Control

DevOps

On-prem

Gluon

Editor plug-in

Open Unity Dashboard

Unity Version Control

此页面不支持所选语言。
​
​
Unity Version Control
  • Overview
  • Cloud Repositories organization update
  • Installation
  • Use UVCS with the Unity Editor
  • Unity Version Control plugins
  • Concepts
    • Organizations
    • Repositories
    • Workflows and partial replicas
    • Security
    • Dynamic workspaces (Windows)
    • File explorer
    • Code reviews
    • Branches
    • Merge conflicts
    • Mergebots
    • Xlinks
    • Smart Locks
    • Symlink Support
    • Triggers
      • Types of trigger
      • List of available triggers
      • Detailed trigger reference
      • Input communication
      • Output communication
      • Common environment variables
      • server.conf variables
      • Client side variables
      • Filters
      • Web triggers
  • Tutorials
  • On-Prem
  • Gluon
  • CLI and shortcut references
  • Release Notes
  1. Unity Version Control (previously Plastic SCM)

Output

Understand output variables for triggers in Unity Version Control.
阅读时间1 分钟
最后更新于 10 个月前

The trigger script uses the result code to communicate the result of its execution. UVCS interprets these result codes as one of the following:
  • Zero (0): Trigger finished correctly. Operation can continue.
  • Non-zero (>0): Trigger failed. Operation cannot continue.
When a trigger fails, UVCS sends the standard output of the trigger to the client as an error message:
  • If the result is non-zero for a
    before
    trigger, the operation cancels, and the client displays the error.
  • If the result is non-zero for an
    after
    trigger, the operation has been already performed and can't undo. The client displays the exception.
When a server-side trigger fails because the executable is missing, the server treats it as a non-zero exit code.
However, starting on UVCS (previously Plastic SCM) version 8.0.16.3388, when a client-side trigger fails because the executable is missing, the client treats it as a zero exit code.
The error registers as a zero exit code in case you want to distribute your client-side triggers through your repository.
注意
If triggers such as
before-mkworkspace
,
after-mkworkspace
,
before-setselector
,
after-setselector
, and
before-update
fail with a non-zero exit code because the trigger executable isn't downloaded to your workspace, you need to remove the trigger configuration, run the operation, and configure the trigger again.

Copyright © 2026 Unity Technologies
法律信息隐私政策CookiesDocumentation Terms of Use请勿出售或分享我的个人信息您的隐私选择(Cookie 设置)

“Unity”、Unity 徽标及其他 Unity 商标是 Unity Technologies 或其附属公司在美国和其他地方的商标或注册商标(此处查看更多信息)。其他名称或品牌是其各自所有者的商标。

为方便起见,一些页面是机器翻译的,可能包含不准确的内容。如有信息不一致的情况,以英文版本为准。


    报告此页面的问题