Go to file
bassrock ef08188b90 Added Help Plea to the readme 2014-06-11 10:21:27 -07:00
src/main Separating out the Build Causes. 2014-06-08 14:00:49 -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 Added Help Plea to the readme 2014-06-11 10:21:27 -07:00
gitlab-jenkins-1.0-SNAPSHOT.hpi Removing the Polling Log Page. 2014-06-08 13:58:18 -07:00
gitlab-jenkins.iml Making the build plugin build the SHA1 that was in the payload. 2014-06-08 13:53:26 -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.

Build Status

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

  • /project/PROJECT_NAME/builds/COMMIT_SHA1 redirects to build page.

  • /project/PROJECT_NAME/build In order for it to build properly on push you need to add this as a seperate web hook. For some reason GitLab is not sending the webhook.

Major Help Needed

I would like this project to be able to handle building merge requests and regular pushes. In order to do this I need a way to configure the git plugin via code to merge two branches together before a build. Much like the RevisionParameterAction.java in the git plugin, we need a class that takes to branches, a source and a target, and can be passed as a build action. I have started an issue for the Git plugin here: https://issues.jenkins-ci.org/browse/JENKINS-23362 If you know of a way to do this please PM on twitter at @bass_rock. All the other necessary code exists in this repo and works. We just need the merge requests to work and we can put a V1.0 on this thing!

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.

Known Issues

Contributing

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

Contributors

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