Builds cancel automatically: "Status Code: 404 - Exception: Stacktrace: (none)"

Unity Services
1

My project’s builds have been automatically canceling for approximately the past 4 hours. In the Full Build Log for each canceled build is the following:

1: <html><head><title>Error 404</title></head><body bgcolor="#ffffff"><h1>Status Code: 404</h1>Exception: 
Stacktrace: <pre>(none)
2: </pre>
<hr size="1" width="90%"><i>Generated by Winstone Servlet Engine v0.9.10 at Wed Jul 15 18:16:41 UTC 2015</i></body></html>
Status: CANCELED

This looks like a Hudson/Jenkins 404 message (see also: windows - Triggering builds remotely in Jenkins - Stack Overflow), so I’m wondering if the build server for my project might be experiencing issues. If this is the case, when will it resume normal function?

My subversion host is up and running and I’m pretty sure my Unity project should not cause 404’s in a Java servlet :), but if there could be anything in my project setup or in its Unity Cloud Build settings that could be causing this issue, I’d be interested to know.

2

I’m also having the same issue, just started today.

3

The issue remains today as well. All our projects have the same problem on Cloud Build.
They all worked up until yesterday.

4

Service Malfunction

We have become aware that several Unity Cloud Build users run into Error 404 building their projects via SVN right now. Git and P4 are not affected as far as we know. We already work on the solution of the malfunction and I will let you know as soon as we have found and hot-fixed the issue. Currently there is no workaround available. We apologise for the inconvenience.

-db

5

Thanks for your reply, David. Good luck on creating the fix.

I do wonder, wouldn’t temporarily moving my project to a Git repo constitute a satisfactory workaround?

6

@broersma It would, though I’ve just gone the other way and it was a day-long pain the backside (and then, this! Will karma ever been even?? :))…I think it’s just swapping one hassle for another.

7

Moving to Git does indeed work in a pinch, but I can see how it’s not a realistic workaround for every affected project.

8

Yep. Git’s smooth, but SVN is cranky when creating a new repo from an existing (and huge) project. You have to do it bit by bit, very tiresome.

I was considering git-svn (Git - git-svn Documentation) at one point, but I’m not that brave (or foolish, pending viewpoints).

9

It could be a possible workaround, but involves a lot of work. It does not affect all svn repositories and we still work on a fix. Please stay tuned! :slight_smile:

10

Ah that’s interesting. We’re using Assembla, if host matters at all (we’re broken too).

1 Like
11

We are using Assembla as well, actually.

1 Like
12

And so are we.

1 Like
13

Also broken, also using Assembla.

2 Likes
14

Hi everyone,

We’re continuing to see issues with connecting to and building from Assembla-hosted SVN repositories since last week. Other SVN hosts do not appear to be affected, and we’re continuing to test possible workarounds.

We’ve applied a patch to Unity Cloud Build, but the results with Assembla SVN repos are still inconsistent (at best) so far. We’ll update this thread further when we have more information.

4 Likes
15

Is there any progress on this? We haven’t been able to do a build for over a week now and the support ticket I opened hasn’t gotten any reply from you guys. We are still paying for this service.

2 Likes
16

Hello and welcome to the forums!

We tested some fixes already and there might be 1/3 chance that a project builds right now. We are in contact with Assembla now to fix the issue asap. I’ll let you know as soon as we have more information available.

1 Like
17

Thanks for the update. Good to know you guys are in contact with Assembla about it.

18

I managed to get our app to (start to build) from the Assembla SVN repo, but it fails with:

Our git repo was ~1.2GB at it’s height and built no problem, and I actually removed a lot of deprecated stuff before transferring to SVN. Our SVN repo is currently 945MB.

Is something up still?

19

Incidentally… could cancelled operations not set the lock-down timer?

You say 1 in 3 builds work, but I have to wait 30 minutes between failures…you can see where my head is at :wink:

20

@Pix10 that means you managed to check out from Assembla (at least on that try), and what gets checked out is larger than you might thing it is. Did it work properly before the builds started to fail due the Assembla checkout issue? But yes we work on a solution.