Go to file

bassrock c2ace53339 Update read me for the new status.png		2014-05-29 11:19:36 -07:00
src/main	Adding status png for commits sha1	2014-05-29 11:18:40 -07:00
.gitignore	Working on the base of the plugin some more.	2014-05-21 23:18:59 -07:00
.travis.yml	Adding in base starter files for a hello world.	2014-05-20 10:06:20 -07:00
LICENSE	Initial commit	2014-05-20 09:50:12 -07:00
README.md	Update read me for the new status.png	2014-05-29 11:19:36 -07:00
gitlab-jenkins.iml	Getting the status images to work.	2014-05-28 23:13:30 -07:00
pom.xml	Getting the status images to work.	2014-05-28 23:13:30 -07:00

README.md

gitlab-jenkins-plugin

This plugin emulates Jenkins as a GitlabCI Web Service to be used with GitlabHQ.

Current Supported GitLabCI Functions

/project/PROJECT_NAME/builds/COMMIT_SHA1/status.json
/project/PROJECT_NAME/builds/status.png?ref=BRANCH_NAME
/project/PROJECT_NAME/builds/status.png?sha1=COMMIT_SHA1

Planned GitLabCI Functions

/project/PROJECT_NAME/build

Help Needed

/projects/ - seems to be already used by Jenkins, A way to use this path would be awesome
?token=XYZ - Can not find a way to include a token parameter on an AbstractProject to security check without an extra plugin configuration
/PROJECT_NAME/ should really be /PROJECT_ID_NUMBER/ - Can not find a project id number on an AbstractProject to use here instead.

Contributing

Fork it ( https://github.com/[my-github-username]/gitlab-jenkins-plugin/fork )
Create your feature branch (git checkout -b my-new-feature)
Commit your changes (git commit -am 'Add some feature')
Push to the branch (git push origin my-new-feature)
Create a new Pull Request

Contributors

@bass_rock, base ground work.
@DABSquared, company sponsoring development.