Increase build timeout from 60 minutes

[DrBeak1]

Describe the solution you'd like
Don't automatically fail builds at 60 minutes.

Describe alternatives you've considered
Changing CI/CD platforms

Additional context
Our mobile iOS application has 50 UI tests. The application is fairly small and we're not doing anything unusual with our build process. We're at a point now where we cannot add new tests because doing so will cause us to fail builds specifically due to the time limit. I'm not sure how larger applications could ever make use of the platform with this limitation.

[Oddj0b]

Alternatively, if you are running UI test in App Center Test from Build, you can add a --async switch which do fire and forget of the test, so the build machines aren't waiting for it.

[DrBeak1]

@Oddj0b Thanks for your message. I'm not 100% I follow where the --async switch would go. I'm referring to App Center > Build web tab. From what I can tell this has a default script that is fired and UI tests are either on or off based on the config for that particular branch. Let me know if I'm missing something.

[vonovak]

same as #279

[diogoviannaaraujo]

60 minutes?? mines are failing with 30 minutes... No tests are made....

[dennispan]

@diogoviannaaraujo Are you on a paid plan? Free tier is 30 minutes and paid plan is 60 minutes. More details can be found here: https://docs.microsoft.com/en-us/appcenter/general/pricing#the-free-tier

[mnxamdev]

This is a huge problem for us in our UWP. We are paying customers and I've been dealing with inadequate App Center tech support for a month now giving information and repeating the same thing over and over. There is a big variance in build times for us on UWP while iOS and Android (using same Xamarin code) are pretty consistent in build times. UWP sometimes builds in 40 minutes, sometimes in 60 minutes. I can branch off the same branch in a newly cloned config and that will build in 38-48 minutes while the original branch/config builds closer to 50-60+ minutes. I've consolidated nuget feeds into 1 (this did not shave off much time) and even removed my UnitTest project from the solution (this did not shave off much time either) to no avail. This blocks us from testing and blocks us from releases. We have been limping along and just manually run builds but sometimes that doesn't even work. What does it take to get this problem solved for a paying customer? It's very frustrating when you can't get anyone to deep dive into the issue and just stall by asking for more information and give a paying customer the run around when there is clearly something wrong on the App Center side! On a local workstation building in release mode with ".Net Native tool chain" takes about 40 minutes.

[FadiAboMsalam]

Any solution for the 60 min timeout or should we switch to a different CI/CD tool

[cvergaray]

I'm in the same boat as @mnxamdev, this is really frustrating.
Our application isn't even running unit tests, there is just a lot of code to build. When trying to do a UWP build for ARM, x86, and x64, each build easily takes 20+ minutes and because it's building all three under the same 60-minute limit, it regularly times out. And then, when I reach out to AppCenter support about it, they confuse timeouts with out of memory exceptions.

[DrBeak1]

Wow, 2yrs old and still an issue. We switched to CircleCI shortly after I posted this because in talking with support it seemed clear it wasn't going to be resolved any time soon. CircleCI is great; a bit more to setup, but way more flexibility. Highly recommend.

[mnxamdev]

Yup @DrBeak1, 2 yrs old. Amazing. Realizing that paying customers weren't going to get the support they needed from a Microsoft service on a Microsoft framework we switched to Team City for our UWP builds. Haven't had a single issue and our build times are only 30 minutes tops!

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.