Search Unity

UCB Team - build delays (15 March 2017)

Discussion in 'Unity Build Automation' started by PhilMcJ, Mar 15, 2017.

  1. PhilMcJ

    PhilMcJ

    Unity Technologies

    Joined:
    May 29, 2014
    Posts:
    187
    Hello -
    part of the production build system is experiencing delays right now (due to an internal puppet server issue), so build attempts from the past approximately 30 minutes have a chance of being queued. The environment should be caught up shortly, and those builds will then be processed.
     
    PhilMcJ, Mar 15, 2017
    #1

  2. PhilMcJ

    PhilMcJ

    Unity Technologies

    Joined:
    May 29, 2014
    Posts:
    187
    Hello -
    Quick update: builds are making it through, but there are still delays for a number of some build attempts as everything catches up while trying to service the queued builds.
     
    PhilMcJ, Mar 15, 2017
    #2

  3. PhilMcJ

    PhilMcJ

    Unity Technologies

    Joined:
    May 29, 2014
    Posts:
    187
    Hello -
    Cloud Build's queues have (almost completely) caught up. It turns out that in one of the build system environments, the load (demand for builds!) had grown to the place where the puppet tools could keep up under normal load, but could no longer catch up reasonably if it got behind. Puppet is now running with more CPU than before and seems to be much happier now.
     
    PhilMcJ, Mar 16, 2017
    #3
    LiterallyJeff likes this.

  4. coly_sugai

    coly_sugai

    Joined:
    May 14, 2016
    Posts:
    15
    Hello
    from March 15th, iOS Build has been failed with internal error.

    An internal Unity Cloud Build error has occurred (Unexpected termination of the channel). The Unity Cloud Build team is addressing this issue, and this build can be restarted if needed.

    Does this build error have anything to do with this topic?
     
    coly_sugai, Mar 16, 2017
    #4

  5. PhilMcJ

    PhilMcJ

    Unity Technologies

    Joined:
    May 29, 2014
    Posts:
    187
    Hi coly_sugai -
    That error is unrelated - on occasion an internal network connection between Cloud Build systems drops (for one of a few reasons), resulting in that error. If you see it, the affected build can just be restarted if needed. If you see it repeatedly in succession on a project, please post about it here or open a support ticket!
     
    PhilMcJ, Mar 16, 2017
    #5