On issuing command clasp deploy <version> the deployment should go if no other deployment is happening.
Instead it fails with Unable to deploy; Only one deployment can be created at a time whereas I am able to deploy using the script editor.
N/A
Hey @designgrill is there any other output when you run clasp deploy? Something like Created version xx. There is an error if you have more than 20 deployments. We are working on fixing that.
Hi @campionfellin, no I don't see anything like that. May be because I have so far created the versions manually using clasp version <description> before doing a deploy.
And you are right, the issue first appeared with my 20th version.
$ clasp deploy 19
- A...VSns0s @19.
$ clasp deploy 20
Unable to deploy; Only one deployment can be created at a time
I've made a PR: https://github.com/google/clasp/pull/149 to make that error message more clear. Please let me know if that issue appears again below version 20.
Thanks. Do you have workaround for this? I am not sure if I am using the versions and deployment right as I don't really need the old versions but they are still around.
Hey @designgrill for now, you could try clasp open and then File->Manage versions... and then hit the X next to the old versions you want to remove.
Does clasp undeploy work? We should suggest that instead of just saying
Unable to deploy; Only one deployment can be created at a time
I believe the message now is from ERROR.DEPLOYMENT_COUNT : Unable to deploy; Scripts may only have up to 20 versioned deployments at a time.. Located here: https://github.com/google/clasp/blob/73765e073ed8571bc7bbd97dae400fffd3b477b3/src/utils.ts#L86
We can update that if needed.
This happens to me already with 3 versions, later removing old versions doesn't help. How a guy can develop something for addons when it's not possible to develop locally :expressionless: . I'm sad to say Microsoft has much better documentation, working environment and everything connected to addons than Google...
What is the intended workflow to create and deploy versions over time?
Are folks still experiencing this issue?
It looks like the API limits to 20 concurrent deployments of a script. (I think it used to be 1.)
This is like having 20 deployments of a website being hosted on the web. For most cases, it's not needed.
Please use
clasp deployments
# and
clasp undeploy <id>
If this is still happening, can you provide some steps to reproduce the problem?
I need more specific instructions to reproduce the issue. I think it may have been fixed since reported in April.
Closing.
I have same issues.when using clasp deploy -d "xxx"