darkkirb/harness-drone
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
No description
456 commits 17 branches 83 tags 29 MiB
Go 100%
Find a file
Brad 289312b678 persisting repository hostname to database
2014-06-05 16:02:54 -07:00
client fixed compile error in queue 2014-06-04 14:44:05 -07:00
debian/drone pushing my local branch 2014-06-04 14:25:38 -07:00
server persisting repository hostname to database 2014-06-05 16:02:54 -07:00
shared altered repo to track repo hostname (ie github.com) and multiple clone urls 2014-06-05 15:04:59 -07:00
.drone.yml updated yml 2014-06-05 15:04:28 -07:00
.gitignore updated info in authors 2014-06-04 14:27:29 -07:00
.gitmodules vendor all dependencies with Godep 2014-04-05 14:13:28 -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 pushing my local branch 2014-06-04 14:25:38 -07:00
README.md pushing my local branch 2014-06-04 14:25:38 -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!