github, jenkins, and releases

[al.niessner]

I cannot tell from the description, but I do not think the plugin release ( https://wiki.jenkins-ci.org/display/JENKINS/Release+Plugin ) is what I am looking for.

What I am looking for is to trigger a Jenkins build with a the github hook Release.

Jenkins 2
GitHub Enterprise (2.8 or so)

I see three options

1. Write a plugin (terrible option)
2. Tweak the current plugin (doubtful as I cannot see how to help)
3. Use the trigger by script ability in Jenkins then use a hook to call that URL (payload gets lost)

Any better ideas? Improve any of the ideas already listed?

Thanks and any and all help is appreciated.

Background: I just managed to get Jenkins working with pull requests -- triggers and talks back. It means I have decent working knowledge of the configuration required for Jenkins and GitHub. However, this is only the second time I have worked with Jenkins so very, very far from proficient let alone an expert.

[Indra Gunawan (ingunawa)]

Hi Al Niessner,

 

Are you building a maven project?  Release plugin is to customize the release of your pom and project.

It is not related to Github at all.

 

What are you looking for?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/52b0e4d8-fab8-41a9-8566-1a2787e067ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[al.niessner]

No maven.

In GitHub, I can select a commit to become a release. When I do this it churns the commit into a tarball with all of the git stuff removed. I then want to take this tarball and turn it into a docker image. Sounds strange, I know, but here is my workflow:

1. contributors use pull requests
2. Jenkins uses pull request plugin to run validation checks -- loads of them actually
3. Make a branch for release
4. Jenkins uses push to branch to run I&T tests
5. Use step 2 to fix problems.
6. Pull changes from merge to master from (2) into (3).
7. Back to step (4)
8. Rinse and repeat until clean.
9. With nod from I&T, make a release in github.
10. Jenkins should be notified of release and build related docker image from it
11. Jenkins deploys docker image

From this we can see that there are three interactions between Jenkins and GH. I have the first one working -- pull requests. I can see in the configuration how to trigger on push then I think I can use refspec and branch to limit which builds are actually done in the push trigger. However, my I&T team is not quite ready to start integrating yet so I am jumping to the third, which is the trigger build on GH release. I do not see any configuration buttons for such a nice feature.

Now I am fishing for help. If plugins are not too horrible, I would like simply extend the existing one to include trigger on release hook. Then I though I could do it by using the trigger from script -- for me that is github hook. However I need the payload information. I found this forum and thought I would ask for help before plunging into a swamp filled with dread.