Search Unity

Build stopped working...

Discussion in 'Unity Build Automation' started by topXightJason, Nov 18, 2016.

  1. topXightJason

    topXightJason

    Joined:
    Feb 11, 2016
    Posts:
    3
    We've had stable CloudBuilds for a long time but something just popped up on project Mano that's preventing builds from completing.
    This also appears on the Alpha project, but it doesn't result in a failed build.

    4606: At revision 1326
    4607: Could not open a connection to your authentication agent.
    4608: Calculated Workspace Size: 160.04 MiB
    4609: PATH | SIZE
    4610: /Assets | 160.01 MiB
    4611: /ProjectSettings | 34.03 kiB
    4612: svn: E155036: Please see the 'svn upgrade' command
    4613: svn: E155036: The working copy at '/BUILD_PATH/xxxxremovedxxxx.mano-unity.default-android'
    4614: is too old (format 29) to work with client version '1.9.4 (r1740329)' (expects format 31). You need to upgrade the working copy first.
    4615: ! postcheckoutstatus failed. svn command failed
    4616: Build step 'Execute shell' marked build as failure
    4617: postbuildstatus finished successfully.


    The build simply stopped working at one point. Any suggestions?
     
    topXightJason, Nov 18, 2016
    #1
    bart_bender likes this.

  2. Mycroft

    Mycroft

    Joined:
    Aug 29, 2012
    Posts:
    160
    no one understands why a build will suddenly stop executing without an error msg?
     
    Mycroft, Nov 21, 2016
    #2
    bart_bender likes this.

  3. bart_bender

    bart_bender

    Joined:
    Mar 21, 2015
    Posts:
    20
    I have the same error

    3112: svn: E155036: Please see the 'svn upgrade' command
    3113: svn: E155036: The working copy at '/BUILD_PATH/jyjgames.demons-hunter-runner.default-ios'
    3114: is too old (format 29) to work with client version '1.9.4 (r1740329)' (expects format 31). You need to upgrade the working copy first.
    3115: ! postcheckoutstatus failed. svn command failed
    3116: Build step 'Execute shell' marked build as failure
    3117: postbuildstatus finished successfully.
    3118: Finished: FAILURE
    3119:

    Is the problem the version of SVN in cloud?
     
    bart_bender, Nov 22, 2016
    #3

  4. ritra

    ritra

    Joined:
    Oct 23, 2014
    Posts:
    1
    me too..
     
    ritra, Nov 24, 2016
    #4

  5. skudfisher1

    skudfisher1

    Joined:
    Jul 30, 2013
    Posts:
    5
    Having the same error as well.
     
    skudfisher1, Nov 28, 2016
    #5

  6. unitychrism

    unitychrism

    Joined:
    Sep 16, 2015
    Posts:
    122
    We are currently working to resolve this error, specifically that our updated version of SVN is incompatible with the workspace version being checked out by Cloud Build. I will update this thread with more information as soon as it's available.
     
    unitychrism, Nov 28, 2016
    #6
    bart_bender and skudfisher1 like this.

  7. skudfisher1

    skudfisher1

    Joined:
    Jul 30, 2013
    Posts:
    5
    Any word on the progress of this? Really need this to get working again for my current project/client. Thanks.
     
    skudfisher1, Nov 29, 2016
    #7
    bart_bender likes this.

  8. bart_bender

    bart_bender

    Joined:
    Mar 21, 2015
    Posts:
    20
    Hello,we are expecting to could build our version for IOS soon
     
    bart_bender, Nov 30, 2016
    #8

  9. skudfisher1

    skudfisher1

    Joined:
    Jul 30, 2013
    Posts:
    5
    This is still not working for me. Would love some kind of official update on this with an ETA. We rely pretty heavily on cloud builds now (and upgraded to pro specifically to have shorter queues) and this does not work at all for me right now. It's been quite a while since I've been able to make a build...
     
    skudfisher1, Dec 2, 2016
    #9

  10. bart_bender

    bart_bender

    Joined:
    Mar 21, 2015
    Posts:
    20
    Some progress with this issue?
     
    bart_bender, Dec 6, 2016
    #10

  11. unity-tuesday

    unity-tuesday

    Unity Technologies

    Joined:
    Aug 2, 2016
    Posts:
    42
    Sorry to hear this has been so frustrating and impactful for some of you while we were investigating and testing the solution! We're deploying a fix progressively over the next couple of days, aiming to eliminate this error completely by Friday for everyone. I'll update again here if anything changes.
     
    unity-tuesday, Dec 7, 2016
    #11

  12. Terry-K

    Terry-K

    Joined:
    Jun 23, 2013
    Posts:
    5
    Any updates? :D
     
    Terry-K, Dec 12, 2016
    #12
    bart_bender likes this.

  13. bart_bender

    bart_bender

    Joined:
    Mar 21, 2015
    Posts:
    20
    Any updates?
     
    bart_bender, Dec 13, 2016
    #13

  14. intermarum

    intermarum

    Joined:
    Feb 16, 2015
    Posts:
    7
    We need some news, guys....
     
    intermarum, Dec 14, 2016
    #14
    unity-tuesday likes this.

  15. unity-tuesday

    unity-tuesday

    Unity Technologies

    Joined:
    Aug 2, 2016
    Posts:
    42
    All builders have been updated, so this error shouldn't be coming up at all anymore. Please let us know if that isn't the case!
     
    unity-tuesday, Dec 14, 2016
    #15

  16. intermarum

    intermarum

    Joined:
    Feb 16, 2015
    Posts:
    7
    Still the same...

    iOS build & Android build

    8119: At revision 440
    8120: Could not open a connection to your authentication agent.
    8121: Agent pid 2025
    8122: Calculated Workspace Size: 491.73 MiB
    8123: PATH | SIZE
    8124: /.vs | 314.50 kiB
    8125: /Assets | 480.33 MiB
    8126: /Library | 10.66 MiB
    8127: /ProjectSettings | 106.63 kiB
    8128: /conf | 6.26 kiB
    8129: /db | 10.54 kiB
    8130: /hooks | 28.75 kiB
    8131: /locks | 284.00 B
    8132: svn: E155021: This client is too old to work with the working copy at
    8133: '/BUILD_PATH/(...) (format 31).
    8134: You need to get a newer Subversion client. For more details, see
    8135: http://subversion.apache.org/faq.html#working-copy-format-change
    8136: ! postcheckoutstatus failed. svn command failed
    8137: Build step 'Execute shell' marked build as failure
    8138: postbuildstatus finished successfully.
     
    intermarum, Dec 14, 2016
    #16

  17. unitychrism

    unitychrism

    Joined:
    Sep 16, 2015
    Posts:
    122
    Hey there @intermarum, can you please direct message me a link to your project? Thanks.
     
    unitychrism, Dec 14, 2016
    #17

  18. unitychrism

    unitychrism

    Joined:
    Sep 16, 2015
    Posts:
    122
    Hi all,

    As an update the error that @intermarum referenced is the opposite of the one that was being received originally. I'm actively looking into it and will update here as soon as it's resolved. Thanks for your patience.
     
    unitychrism, Dec 14, 2016
    #18
    bart_bender likes this.

  19. malek256

    malek256

    Joined:
    Dec 28, 2013
    Posts:
    27
    Sure would be nice to have builds function again. We've been waiting a month.
     
    malek256, Dec 14, 2016
    #19

  20. Terry-K

    Terry-K

    Joined:
    Jun 23, 2013
    Posts:
    5
    It works for me now! Thanks~!
     
    Terry-K, Dec 15, 2016
    #20
    unity-tuesday and bart_bender like this.

  21. bart_bender

    bart_bender

    Joined:
    Mar 21, 2015
    Posts:
    20
    It works for me now too
     
    bart_bender, Dec 15, 2016
    #21
    unity-tuesday likes this.

  22. narendra_mm

    narendra_mm

    Joined:
    Jun 2, 2016
    Posts:
    3
    Hi guys,

    svn upgrade error is back. Is Unity Cloud team working on this?

    30: svn: E155036: Please see the 'svn upgrade' command
    31: svn: E155036: The working copy at '/Volumes/extra-workspace/workspace/xxxx.default-android'
    32: is too old (format 29) to work with client version '1.9.4 (r1740329)' (expects format 31). You need to upgrade the working copy first.
    33: ! postcheckoutstatus failed. svn command failed
    34: Build step 'Execute shell' marked build as failure
    35: postbuildstatus finished successfully.


    Cheers!
     
    narendra_mm, Feb 16, 2017
    #22

  23. SophiaC

    SophiaC

    Joined:
    Sep 6, 2016
    Posts:
    238
    SophiaC, Feb 17, 2017
    #23

  24. narendra_mm

    narendra_mm

    Joined:
    Jun 2, 2016
    Posts:
    3
    Hey @SophiaC

    'Clean Build All' worked for me. I did upgrade my svn but that didn't help. A clean build did solve my issue.

    Cheers!
     
    narendra_mm, Feb 17, 2017
    #24
    SophiaC likes this.

  25. vshafran

    vshafran

    Joined:
    Jan 9, 2017
    Posts:
    2
    Hi guys. The same issue
    cloud build for ios on Unity 5.3.4f1 and Unity 5.3.4p6 but working on Unity 5.5.0

    Could not open a connection to your authentication agent.
    18279: Agent pid 1861
    18280: Calculated Workspace Size: 664.10 MiB
    18281: PATH | SIZE
    18282: /Assets | 664.07 MiB
    18283: /ProjectSettings | 32.87 kiB
    18284: svn: E155021: This client is too old to work with the working copy at
    18285: '/BUILD_PATH/?????????????????' (format 31).
    18286: You need to get a newer Subversion client. For more details, see
    18287: http://subversion.apache.org/faq.html#working-copy-format-change
    18288: ! postcheckoutstatus failed. svn command failed
    18289: Build step 'Execute shell' marked build as failure

    Can you fix it? Thanx
     
    vshafran, Mar 23, 2017
    #25

  26. SophiaC

    SophiaC

    Joined:
    Sep 6, 2016
    Posts:
    238
    @vshafran PM me a link to your project.

    - Sophia
     
    SophiaC, Mar 24, 2017
    #26