-
Notifications
You must be signed in to change notification settings - Fork 690
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add Continuous Delivery #57
Comments
Is there a standardized way to do continuous delivery? As far as I know, each cloud provider has its own CD mechanisms. If so, this work item should be to document supported/known CD flows. |
I think for this, publishing a docker image (under latest/nightly tags) would satisfy the requirements. |
I'd like to follow NuGet Package Explorer's setup:
|
I've added Continuous Delivery to BaGet. You can:
I'll add support for Docker images in the future. |
Closing this issue as BaGet has continuous delivery. Please let me know if you have any other suggestions! |
Do you want to request a feature or report a bug?
Feature
What did you expect to see?
Currently there's no continuous delivery. In other words this means we have to manually deploy our build outputs produced in #56. We don't want to do manual stuff as we're programmers so why not automate it?
Blocked by
Expectations
The CD should be able to do:
This will gives us a place to download artifacts from per version and a place to download the nightly build from.
The text was updated successfully, but these errors were encountered: