Hi
I want to know if its possible to create a throwaway droplet to handle build and testing of our code (via jenkins slave) for then deploying to our production droplet?, I see it is possible to create a droplet, configure use, archive and destroy it and then later redeploy the archive, is this usable for my use case (and doing that via the API)?, perhaps with private IPs (when they are deployed) would be more useful and less resource straining (public IPs that we don’t really need).
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
There is a quite similar question in this forum <br>https://www.digitalocean.com/community/questions/jenkins-plugin .