Deploy failing with "Unable to deploy; Only one deployment can be created at a time" after few deployments
See original GitHub issueExpected Behavior
On issuing command clasp deploy <version>
the deployment should go if no other deployment is happening.
Actual Behavior
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.
Steps to Reproduce the Problem
N/A
Specifications
- Node version v9.3.0
- Version @google/clasp@1.1.5
- OS Mac
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:13 (3 by maintainers)
Top Results From Across the Web
Deployment safety - GitLab Docs
Restrict write access to a critical environment · Ensure only one deployment job runs at a time · Prevent outdated deployment jobs ·...
Read more >Troubleshoot EC2/On-Premises deployment issues
Deployment fails with the message “Validation of PKCS7 signed message failed”. This error message indicates the instance is running a version of the...
Read more >Auto-deploy from failed deployments · Issue #3358 - GitHub
We're proposing we modify auto-deploy's logic to be able to query deployments that have "previously" successfully deployed (but are currently ...
Read more >Deployment pipelines troubleshooting - Power BI
When you create a workspace with a PPU, only other PPU users will be able to access the ... Why is my visual...
Read more >Troubleshooting your Deployment · Fly Docs - Fly.io
Unless you've not deployed successfully before. In which case it will just fail as there's nothing to roll back to. Port Checking. So...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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 😑 . I’m sad to say Microsoft has much better documentation, working environment and everything connected to addons than Google…
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
to clean up your deployments.
If this is still happening, can you provide some steps to reproduce the problem?