Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-30861

Ignore 'Polling ignores commits from certain users' on GitLab WebHooks

    XMLWordPrintable

Details

    Description

      Excluded users are ignored when a webhook is fired from GitLab, e.g. to:
      `https://jenkins.example.com/project/my_project_folder/my_project_master`

      Attachments

        1. screenshot-1.png
          screenshot-1.png
          81 kB
        2. screenshot-2.png
          screenshot-2.png
          36 kB
        3. screenshot-3.png
          screenshot-3.png
          15 kB
        4. screenshot-4.png
          screenshot-4.png
          27 kB

        Activity

          markewaite Mark Waite added a comment -

          Can you provide more description of the conditions required to show the problem, the details of what you observe, and what you expect to observe instead? The description portion seems to contradict the summary of the bug or enhancement request. I don't understand which you want.

          Please refer to how to report an issue for the types of details which are needed.

          markewaite Mark Waite added a comment - Can you provide more description of the conditions required to show the problem, the details of what you observe, and what you expect to observe instead? The description portion seems to contradict the summary of the bug or enhancement request. I don't understand which you want. Please refer to how to report an issue for the types of details which are needed.
          manuel4y Manuel added a comment -

          This is the jenkins git config that works:

          with this config for gitlab hook:

          The build-job commited the new versions and the gitlab webhook is fired:

          BUT:
          When the behavior 'Polling ignores commits from certain users' configured, the jenkins-job triggered:

          I tried many usernames, but nothing works.

          manuel4y Manuel added a comment - This is the jenkins git config that works: with this config for gitlab hook: The build-job commited the new versions and the gitlab webhook is fired: BUT: When the behavior 'Polling ignores commits from certain users' configured, the jenkins-job triggered: I tried many usernames, but nothing works.
          markewaite Mark Waite added a comment -

          If you use a github.com public repository or a locally hosted git repository, do you see the same behavior?

          If you install the "Poll Now" plugin and click the "Poll Now" link, do you see the same behavior?

          markewaite Mark Waite added a comment - If you use a github.com public repository or a locally hosted git repository, do you see the same behavior? If you install the "Poll Now" plugin and click the "Poll Now" link, do you see the same behavior?
          manuel4y Manuel added a comment -

          I use and test it with my local GitLab Server and a GitHub Repo.
          When i POST/Execute the polling manual with
          https://jenkins.example.com/project/my_project_folder/my_project_master/polling
          i see the same behavior.

          manuel4y Manuel added a comment - I use and test it with my local GitLab Server and a GitHub Repo. When i POST/Execute the polling manual with https://jenkins.example.com/project/my_project_folder/my_project_master/polling i see the same behavior.

          This is actually an issue with gitlab-hook design. It searchs for projects with matching repository url, and apart for the branch and refspec checks, no other configuration item from git-plugin is considered. Neither ignored users, nor ignored paths nor anything else.

          The reason behind is that is implemented on ruby, and there is no actual triggers on jruby-jenkins, so the plugin is actually a jenkins RootAction. I've done some steps toward it, but it's not yet ready, so this will take some time to get fixed.

          javiplx Javier Palacios added a comment - This is actually an issue with gitlab-hook design. It searchs for projects with matching repository url, and apart for the branch and refspec checks, no other configuration item from git-plugin is considered. Neither ignored users, nor ignored paths nor anything else. The reason behind is that is implemented on ruby, and there is no actual triggers on jruby-jenkins, so the plugin is actually a jenkins RootAction. I've done some steps toward it, but it's not yet ready, so this will take some time to get fixed.
          javiplx Javier Palacios added a comment - Reopened in response to https://github.com/jenkinsci/gitlab-hook-plugin/pull/27/files
          basil Basil Crow added a comment - See Deprecating non-Java plugins .
          basil Basil Crow added a comment - See Deprecating non-Java plugins .

          People

            javiplx Javier Palacios
            manuel4y Manuel
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: