self-hosted/woodpecker
1
0
Fork 0
mirror of https://github.com/woodpecker-ci/woodpecker.git synced 2024-12-24 10:07:21 +02:00
Code Issues Releases Activity
Woodpecker is a simple yet powerful CI/CD engine with great extensibility.
500 Commits 36 Branches 78 Tags 160 MiB
Go 86.6%
Vue 8.8%
TypeScript 3.4%
Makefile 0.6%
CSS 0.4%
Other 0.1%
7acf92e754
Go to file
Brad Rydzewski 7acf92e754 hooked up websockets & added setup karma+jasmine
2014-06-21 17:41:40 -07:00
client fixed compile error in queue 2014-06-04 14:44:05 -07:00
debian/drone hooked the build queue back up 2014-06-11 17:42:49 -07:00
plugin Refactored to use Model and Database folders 2014-06-12 16:41:04 -07:00
server hooked up websockets & added setup karma+jasmine 2014-06-21 17:41:40 -07:00
shared removed css files. designers will be providing 2014-06-21 14:22:38 -07:00
.drone.yml using make build in .drone.yml since we only need to compile 2014-06-12 13:06:34 -07:00
.gitignore removed css files. designers will be providing 2014-06-21 14:22:38 -07:00
AUTHORS updated info in authors 2014-06-04 14:27:29 -07:00
LICENSE initial public commit 2014-02-07 03:10:01 -07:00
Makefile hooked up websockets & added setup karma+jasmine 2014-06-21 17:41:40 -07:00
README.md added message to indicate empty feed on user and repo dashboard screens 2014-06-05 16:48:45 -07:00

README.md

Experimental version of Drone.IO with deep GitHub, GitHub Enterprise and Bitbucket integration.

I am currently copy / pasting functionality into this branch. So if you see something that is missing it probably because I haven't gotten to that section yet. The initial focus has been on the API and UI, which means builds are not hooked up yet. Help is of course welcome.

Some of the fundamental changes include

  1. modification to project structure
  2. api-driven design
  3. interface to abstract github, bitbucket, gitlab code (see /shared/remote)
  4. handlers are structures with service providers "injected"
  5. github, bitbucket, etc native permissions are used. No more teams or permissions in Drone
  6. github, bitbucket, etc authentication is used. No more drone password
  7. github, bitbucket, etc repository data is cached upon login (and subsequent logins)
  8. configuration is driven by a file (~/.drone/drone.toml) and not the database

... probably more that I'm forgetting

Normally I wouldn't post experimental code in such disarray, but given the amount of activity around the project I wanted to give the community visibility into these changes. I could also use the help!

I'm tracking my TODO list here: https://gist.github.com/bradrydzewski/85b7720c276a70a1bed5