I just got a notice that I’ve exceed my 500 build ...
# seed
g
I just got a notice that I’ve exceed my 500 build minutes for the month on seed. I was surprised because I thought that SST projects were free and didn’t count against the 500 minutes?
a
The SST builds should be free, but if you do (unit) testing using the seed.yml buildspec then these actions count. And it seems that it counts every "started" minute - my unit tests last about 3-4 seconds but it always claims that 1 build minute was used.
f
Thanks @Alfred Brose!
@Guy Shechter r u running custom commands in
seed.yml
?
g
@Frank
Copy code
before_compile:
  - n 14.19.0
  - npm install --unsafe-perm
Incidentally. the reason I need this in my seed.yml is because I have my frontend code in a subdirectory, and the frontend dependencies, e.g. react-scripts are only in frontend/package.json. In order to get them to install at the root level, I needed to add this to my root level /package.json
Copy code
"install:frontend": "cd frontend && npm install",
"postinstall": "npm run install:frontend",
which would only run with --unsafe-perm flag
Does “free” only apply to standard size build machines? I didn’t see that specified anywhere, but wondering if that’s a factor?
f
Ah yeah, for Medium and Large build machines, you are not charged for the time waiting for CloudFormation to update, but the time spent leading up to it. https://seed.run/docs/adding-a-cdk-app.html#pricing-limits