Resolved DevOps Pricing??

Hello, I have been trying to find out what's the pricing after the free tier in the DevsOps page but I can't seem to find it. It keeps asking me to sign up with pay as you go without letting me know how much I could be charged per extra seats, GBs or builds (not looking to use the last one, only interested in plastic to be honest).

Can you please throw some light?
How much would 4 seats cost?

Regards

 

I was looking for a version control system that works well for Unity games - for 2 seats, 3 maybe max just to work on a small project with friends. I have some questions I need answering if you could please help:

Question 1?
Lets start with the basic premise that our game will store 1GB on a source server as Unity Dev Ops offers and we don't have to worry about the library folder etc.

Naturally as a hobbyist I want to avoid getting charged so I will try to avoid the 5GB limit but I can pay if necessary especially if the project becomes larger - I just don't want to be overcharged because I don't understand something.

Then there's the issues about quality - I found comments only 5 months ago that still talk about how this solution or its former have had bugs and commit conflicts.

Unity has changed itself so many times from Collab, Teams and then DevOps....I fear commit issue bugs and lack of future security and so despite this "seeming to be a solution" all these concerns have me considering Git and its LFS feature which I know nothing about but people seem to recommend.

Even if this is the solution and it's the cheaper one my fears is the bugs - one commit conflict bug could be really bad but if I don't use the library folder then I should be good to go right?

Question 2: Will we actually need to create (5 version backups) 5Gb+ of branches if we are just 2 people and only want to work on the latest version and a previous backup version we backup every week to revert to if something goes wrong?

Sorry that's probably a lot more than 2 questions but someone answering this will help A LOT OF PEOPLE.

Feedback: I certainly didn't know the compute minutes was an optional feature - the way it is advertised on the page makes it seem like you get charged for every commit and branch as its using computer power haha - so it seems like a mandatory feature to the layman that will run out very quickly it should be listed as optional expense because I was deterred by it big time because 200 minutes seems like nothing.

Feedback: What in the world do you mean by concurrent machines - that's not explained and again deters me from going forward.

 

Does storage apply to VCS only or also to builds / artifacts?

 

Yes, please expand on SilverStorm's questions. The pricing page here isn't detailed enough. For example, it makes it sound like Free tier gives 5GB and Standard Tier you don't get that 5GB, but instead are billed for all storage. Same for the "machine" concurrency costs.

I'd like more details on the following:
1. What is considered and billed as using storage (that would end up affecting the cost)?

• Does it include all Plastic repos and all ChangeSets?
• Does it include Builds in Build History? Where are "Builds" stored?
• Does it include the entire work-space for making a build (the library, caches, etc, which can be gigabytes and gigabytes of data!)
• Is there any advantage to us going through all our past Build histories and deleting old builds?

2. Does standard tier get 1 machine concurrency free or not?

3. Does Standard get 200 free minutes or not? And when do those free minutes reset?

4. Compute time:

• Doesn't charging for build time incentivize Unity to use slow machines so that they can charge more?
• Where is the cost calculator? Usage based services like Microsoft Azure, Amazon's AWS, etc provide detailed calculator tools to estimate pay-as-you-go costs. You're going to have a hard time getting buy-in if these parts of a project's budget can't be projected ahead of time.

 

Thank you for replying. I wanted to clarify that I eventually found the usage pages for DevOps where you have actual graphs and usage costs, etc. This is accessed from the DevOps main overview Dashboard and through "Usage Reporting" under the Version Control sidebar menu.

Your sales page could include some screenshots of the graphs and other data you provide through the Dashboard, as an example.

Since the service isn't active for us yet, I can't really estimate, so yes, a calculator page like AWS and MS Azure provides would be helpful for cost projections. Of course I expect once Devops is up and running for our account and a billing cycle has passed we will have the info we need to see if we should reduce usage or not worry about it at all.

I realize this service transition isn't easy nor simple on your end and you must be dealing with many people who dont like change, so thanks again for taking the time to reply.

 

Also, today I found the "Budget Alerts" sections which is found under "Cost and Usage" where we can set up email alerts for different usage costs. Fantastic!

 

Will we get billed for failed builds? Sometimes Cloud Build fails due to our mistakes, but sometimes it fails because of something on your end. Who pays for that build time?

Another suggestion: We pay for 2 concurrent machines. I started a third build (something I do all the time) and although I think it queued up, it also triggered a warning at the top of the dashboard page, saying it canceled the build. I think it actually cancelled an existing in-progress build rather than just wait for a free machine. Any tips or insight into this?

 

This was covered in an announcement thread on the UCB forum a few months back. From my understanding, we pay.

https://forum.unity.com/threads/announcement-unity-teams-and-devops-vision.1277462/#post-8193093

But the process that Unity determines if a build fail is their issue (or not) is unclear. As is the process for attempting to reclaim the costs of failed builds.

I suspect they're hoping that a dollar here and a dollar there isn't worth peoples time and effort to try and reclaim, but it all adds up.

It's a huge step back imho and just adds to the costs and burden for indies and smaller studios. The complete opposite of what Cloud Build was supposed to achieve.

Of course if this is outdated\wrong or Unity have better plans in the works, we would all love to hear about it.

 

So i get:

• Your first 5 GB of storage in the cloud = free

But when i look at the dashboard for a few builds I see this - no clue if this means I am over the 5GB storage limit or not. Is this 60GB or do i have to divide it by a bunch of hours per week?

This whole thing is too confusing and feels a bit shifty...

 

Thanks for the reply @wrossmck-unity - very useful, yes getting this information on the dashboard would help a lot of confusion, either by having a tool tip to show the way you calculate GB hours or by converting this into some kind of "this means you are paying for 100mb of storage this month" kind of thing - I think it is useful to bring it back to real file size numbers so people can know how much they need to free up.

 

After reading all this, I still don't understand if builds contribute to storage costs (@wrossmck-unity seems to suggest so above) or not ("does not include anything that our build machines use" - @JGasimov). DevOps says my builds average 1.5GB - does that mean that if I have 4 builds (6GB) I'll pay for 1GB per month of storage?