Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

Question Error with cloud build using PlasticSCM. Error During Plastic Checkout

Discussion in 'Unity Build Automation' started by 265lutab, Feb 24, 2023.

  1. 265lutab

    265lutab

    Joined:
    Sep 15, 2014
    Posts:
    155
    I'm trying to use Unity Cloud Build for a project that I have uploaded to PlasticSCM from unity and I'm having errors. It seems like it's not being able to pull the changes down from plastic for the build.

    This is the compact error log:
    [error] [2023-02-22T23:09:06.107Z] - 7.2.7.2.4.2 - ERROR: Searching for changed items in the workspace...
    [error] ! checkout failed. Error During Plastic Checkout: Failed to Update
    [error] Finished: FAILURE


    Here is the full error log
     
  2. ZO5KmUG6R

    ZO5KmUG6R

    Joined:
    Jul 15, 2010
    Posts:
    490
    Also experiencing this x|
    upload_2023-2-26_18-28-51.png
     
  3. Benjamin-Gooding

    Benjamin-Gooding

    Unity Technologies

    Joined:
    Apr 12, 2022
    Posts:
    243
    It looks like you specified a specific changeset to checkout that isn't valid. A changeset for plastic is always a numerical value. "Test 001" is not a valid changeset.

    Try running a build without specifying the changeset id. This should run your build without the latest changes from the branch that was defined in your build target definition.
     
  4. ZO5KmUG6R

    ZO5KmUG6R

    Joined:
    Jul 15, 2010
    Posts:
    490
    I'm experiencing this without setting anything like that. Just using the build button from the dashboard.
     
  5. 265lutab

    265lutab

    Joined:
    Sep 15, 2014
    Posts:
    155
    Oh I was putting something into the changeset field. Leaving it blank fixed the error. (I thought that was an ID I was putting in to stay organized with which build it was)
     
    Benjamin-Gooding likes this.
  6. LazloBonin

    LazloBonin

    Joined:
    Mar 6, 2015
    Posts:
    795
    Just got the same error last night on an automated build and on all manually triggered builds since then. We've had the same build config since months, with no changeset specified (I wouldn't even know where that field is).

    Since this is suddenly now happening to multiple different users suddenly in the same week, maybe it's worth considering it's not a user error?

    Here is our full log just in case:
     
  7. Benjamin-Gooding

    Benjamin-Gooding

    Unity Technologies

    Joined:
    Apr 12, 2022
    Posts:
    243
    From what I can tell by looking at that log is that Plastic SCM failed to download all of the files during the checkout process. There are scattered 400 (Bad Requests) in the log you attached. The Plastic CLI exited with a non-zero exit code which failed the build.

    I'll pass this log along to the Plastic SCM team.