WIP: Set up Drone CI (1.0.0-rc5) #19
No reviewers
Labels
No Label
bug
dev environment
docs
duplicate
enhancement
feature
idea
invalid
kredits-1
kredits-2
kredits-3
ops
question
security
ui/ux
wontfix
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/gitea.kosmos.org#19
Loading…
Reference in New Issue
No description provided.
Delete Branch "drone-ci"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This configures the latest release candidate of Drone CI 1.0.0 on the Kubernetes cluster. It is currently running on https://drone.kosmos.org
The new Drone has real Kubernetes support and creates native jobs/containers for running builds. However, that support is still experimental, and I already had a cluster node run out of memory and evicting the build pod in the middle of a run.
Also, Gitea has an open PR for OAuth, which hasn't been merged yet, and so you have to use your Gitea username and password with Drone right now. (But that's not obvious on the login page.)
closes #14
Set up Drone CI 1.0.0-rc5to Set up Drone CI (1.0.0-rc5)Just FYI: I think we may want to run this in a more traditional way on
andromeda
, until this stuff is stable enough. At least if we see that it breaks regularly on GKE.I just found this forums post, which explains how Kubernetes support works, where to find what, how to debug it, and how to contribute: https://discourse.drone.io/t/contributing-to-drone-for-kubernetes/3159
Also very interesting, and relevant to the issue I ran into: https://github.com/drone/drone-runtime/issues/44
Set up Drone CI (1.0.0-rc5)to WIP: Set up Drone CI (1.0.0-rc5)Just noticed that the old
/var/lib/drone
volume mount doesn't persist the data in 1.0 anymore. After creating new deployments, it's all gone.Marked as WIP.
For reference, I asked here about the volume mounts: https://discourse.drone.io/t/how-to-persist-data-in-1-0-0/3911
Lots of changes happening in Drone still. They now switched to the more common concept of having runners be separate from rest:
https://github.com/drone-runners
So now someone can go and build a k18s-specific runner. So far, there is none however.
(From https://github.com/drone/drone-runtime/issues/65)