Home → Problems →

Paid account using CTP5 takes about twice as long as using windows server 2012 R2

• Edit

codecutter

06 Feb, 2015 07:29 AM

With exactly the same build script.

Is it possible the CTP5 stuff is running on Azure rather than dedicated hardware?

Thanks

Kevin

1. Support Staff 1 Posted by Feodor Fitsner on 06 Feb, 2015 07:33 AM

   

   That's right, any custom image is running on Azure. There is currently only one image supported on Pro environment.

   • Edit

2. 2 Posted by codecutter on 06 Feb, 2015 09:38 AM

   

   When will that get addressed, for us it is essential that validation is done against VS2015? It kind of makes a paid account pointless for us.

   • Edit

3. 3 Posted by codecutter on 06 Feb, 2015 09:38 AM

   

   And thank you for your super quick response.

   Kevin

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on 06 Feb, 2015 07:01 PM

   

   Hi Kevin,

   Yeah, I think it's time to offer VS 2015 testing on Pro plan. We'll add that next week.

   • Edit

5. 5 Posted by codecutter on 06 Feb, 2015 07:50 PM

   

   Thank you, that is great news.

   Kevin

   • Edit

6. 6 Posted by Wilhelm Berg on 11 Feb, 2015 07:06 PM

   

   Hi Feodor,

   still planning on adding VS2015 CTP5 to HyperV soon?

   Would be really great, if we could move Mapbox's tools to a fast C++11 environment in the foreseeable future.

   Cheers,
   Willy

   • Edit

7. Support Staff 7 Posted by Feodor Fitsner on 11 Feb, 2015 07:09 PM

   

   Absolutely, will be deployed today.

   • Edit

8. 8 Posted by Wilhelm Berg on 11 Feb, 2015 07:13 PM

   

   That absolutely fabulous!
   :-) :-) :-)

   • Edit

9. Support Staff 9 Posted by Feodor Fitsner on 12 Feb, 2015 05:23 AM

   

   OK, guys, Visual Studio 2015 CTP 5 (+SDK) is part of "Pro" image now.

   • Edit

10. 10 Posted by Wilhelm Berg on 12 Feb, 2015 06:39 AM

    

    YES!

    Thank you!

    • Edit

11. Support Staff 11 Posted by Feodor Fitsner on 12 Feb, 2015 08:54 PM

    

    I'm sorry to say, but we've reverted Pro environment back to the original image, without Visual Studio 2015 CTP. We made an attempt to do VS 2015 side-by-side with VS 2013 and below, but it failed. Seems it was too soon, too quick.

    Despite our main tests were passing on the image with VS 2015 there were other issues identified by customers with ReSharper, Azure SDK, TypeScript to name a few causing their builds failing. Sorry guys for such a dirty A/B testing!

    For now, please use Visual Studio 2015 CTP image for running your VS 2015 builds. It's on Azure and it's slower. At the moment Pro environment has a limitation of running a single image only. We will be working to overcome this limitation and allow running VS 2015 projects on faster environment.

    • Edit

12. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:54 AM.