기술 자료

​
​

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
법률 정보개인정보 처리방침쿠키Documentation Terms of Use개인 정보 판매 또는 공유 금지개인정보 보호 선택(쿠키 설정)

'Unity', Unity 로고 및 기타 Unity 상표는 미국 및 기타 지역 내 Unity Technologies 또는 그 계열사의 상표 또는 등록상표입니다(자세한 내용은 여기에서 확인하세요). 기타 명칭 또는 브랜드는 해당 소유자의 상표입니다.

일부 페이지는 편의를 위해 기계 번역되었으며 부정확한 내용이 있을 수 있습니다. 정보가 상충되는 경우, 영어 버전을 우선으로 참조하세요.


    이 페이지의 문제 보고