Closed ralphcallaway closed 4 years ago
@ralphcallaway It will be interesting to see how fast we burn through the minutes as we transition more of the team over.
We are currently at 40% of our minutes (704/1797
) and roughly 75% through our build cycle.
Ideally I would like to avoid this It seems like a significant developer ergonomics sacrifice.... Unless maybe there is some way to configure the pipeline to automatically retry the checkDeploy
build step (although if minutes include virtual machine setup, this could really eat them as well).
I think that #3 actually has more potential reduce our usage, while also improving the developer experience by giving us faster builds.
also, I just looked it up and it's only 10$ for another 1000m.
Deployments can be pretty slow in some cases and we can spend a lot of build minutes waiting for salesforce to finish doing it's things.
One thought would be the deploy can just submit it and store the deployment id as an artifact, and prompts a user to visit the deployment status page to monitor status. Optionally they could run a follow up 'Check Status' step that would validate the current status of the deployment.
Not really an issue until we start using this enough that conversing build minutes might be worth it ...