-
Notifications
You must be signed in to change notification settings - Fork 42
Not working with Jenkins 2.0 Pipeline plugin #31
Comments
What are the repro steps and expected behavior? |
I can confirm that the plugin does not work with Jenkins 2.0 Pipeline. Steps to reproduce:
Expected behavior:
Actual behavior:
To verify that the plugin works otherwise I also created a freestyle job in Jenkins using the same git repo and a dummy shell step just echoing some text. Having both jobs (pipeline and freestyle) in Jenkins and pushing changes to the git repo (or clicking on the test hook link in GitLab) leads to the result that the freestyle project build kicks off, but the pipeline one doesn't. In the logs I could see that Jenkins found only one matching project, the freestyle one. I hope this helps to pinpoint the cause of this issue. |
Unable to trigger Pipeline Project build on Jenkins 2.7, Pipeline Plugin 2.2, GitLab 7.7. Tried these URLs, but in vain:
Freestyle project builds fine though. Note: Disabled Cross Site Forgery security on Jenkins to make it working. Unchecked |
I used this URL and it works: http://jenkins host:port/project/my job name |
I'm still having this issue:
I have two jobs |
@singh-abhijeet is this hook working with pipelines if you disable Cross Site Forgery security as you said? |
@vkotovv Yes Vadim, the 403 error was due to Cross Site (Domain) request to the Web Hook. Disabling the security option helped. This solution is advisable if you're running Jenkins, Git within your org's Firewall; as disabling it can invite False/Forgery request to the Web Hook if your Jenkins instance is exposed publicly via Internet. |
I'm having the same problem originally reported.. the web hook works fine on a freestyle project but does not work in pipeline project.. Has anyone found a workaround for this? |
It is still not working with Pipeline-Projekts. |
Is this issue fixed with the previous PR ? |
My commit should fix it, but I also don't understand @colinlabs comment. |
@bmaehr it works, but there is a problem, must success run a job before trigger hook |
@colinlabs You mean: a job must run successfully to make the web hook work ? |
@ikus060 yes, otherwise, it will raise an "Template not find" error |
I think it is enough that the template has run once. |
he, any update on this? looks like the PR was never merged.... for me it is not working even when the pipeline ran once |
It looks like I didn't notice the notification about #55. I need to arrange it to execute tests to ensure that it does not break something, as happened with javiplx#100 |
@javiplx so we can expect to get a new version with this feature? |
Log says "WARNING: no project references the given repo url and commit branch"
However, I get all the normal spew leading up to the warning, such as..
INFO: gitlab web hook triggered for
{
"object_kind": "push",
"before": "2bd4bdf47f9752f7a178488554f06cc2682e8ff0",
"after": "89ab9882dbe33e6e51336d7ecd63b66e94427a64",
"ref": "refs/heads/master",
etc etc..
So the web hook is triggered and it finds all the commits. It just fails at the end.
Running Jenkins 2.0
The text was updated successfully, but these errors were encountered: