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

Cannot delete job after using webhook to bitbucket

    XMLWordPrintable

Details

    Description

      After setting up a test job with the webhook functionality, and running a build, the job can no longer be deleted. A log is attached.

      The project is a declarative pipeline.

       

       

      Attachments

        Activity

          slyons22 Sean Lyons created issue -
          slyons22 Sean Lyons made changes -
          Field Original Value New Value
          Description After setting up a test project with the webhook functionality, the project can no longer be deleted, a log is attached.

           

          The project is a declarative pipeline.

           

           
          After setting up a test project with the webhook functionality, the project can no longer be deleted, a log is attached.

           The project is a declarative pipeline.

           

           
          slyons22 Sean Lyons made changes -
          Description After setting up a test project with the webhook functionality, the project can no longer be deleted, a log is attached.

           The project is a declarative pipeline.

           

           
          After setting up a test job with the webhook functionality, and running a build, the job can no longer be deleted. A log is attached.

          The project is a declarative pipeline.

           

           

          Hi Sean,

          The issue seems to be that the webhook log at `C:\Jenkins\jobs\FW-TestJob-01\bitbucket-webhook-trigger.log` is read-only. Changing the permissions (or deleting this file manually) should resolve the issue in this instance.

          I wasn't able to replicate this issue locally. Are you able to provide steps to reproduce, and some more information about your environment (operating system, other plugins etc.)?

          mhenschke_atlassian Martin Henschke added a comment - Hi Sean, The issue seems to be that the webhook log at `C:\Jenkins\jobs\FW-TestJob-01\bitbucket-webhook-trigger.log` is read-only. Changing the permissions (or deleting this file manually) should resolve the issue in this instance. I wasn't able to replicate this issue locally. Are you able to provide steps to reproduce, and some more information about your environment (operating system, other plugins etc.)?
          slyons22 Sean Lyons made changes -
          Attachment installed_plugins.txt [ 50395 ]
          slyons22 Sean Lyons added a comment -

          Hi mhenschke_atlassian, thanks for looking into this!

          Here is some more information about the Jenkins master node:

          os.arch x86
          os.name Windows Server 2016
          os.version 10.0

           

          Attached is the list of installed plugins (installed plugins.txt)

          The slave node has the following specs:

          os.arch x86
          os.name Windows 10
          os.version 10.0

           

          The way I reproduced this was 

          1. Setup a test job on the master, this test job was a declarative pipeline
          2. Build triggers: Bitbucket server trigger build after push
          3. Pipeline: Pipeline script from SCM
            1. SCM: Bitbucket server
            2. Pointed to project name and repo on Bitbucket
            3. Clone from: primary server
            4. Branches to build **

           

          After a successful build, I disabled the project and wished to delete but could not, because of the error above.

          Thanks for helping, please let me know if there is more information you need.

          slyons22 Sean Lyons added a comment - Hi mhenschke_atlassian , thanks for looking into this! Here is some more information about the Jenkins master node: os.arch x86 os.name Windows Server 2016 os.version 10.0   Attached is the list of installed plugins (installed plugins.txt) The slave node has the following specs: os.arch x86 os.name Windows 10 os.version 10.0   The way I reproduced this was  Setup a test job on the master, this test job was a declarative pipeline Build triggers: Bitbucket server trigger build after push Pipeline: Pipeline script from SCM SCM: Bitbucket server Pointed to project name and repo on Bitbucket Clone from: primary server Branches to build **   After a successful build, I disabled the project and wished to delete but could not, because of the error above. Thanks for helping, please let me know if there is more information you need.
          dkjellin Daniel Kjellin made changes -
          Assignee Kristy Hughes [ khughes ]
          bplump B Plump made changes -
          Labels tracked-by-atlassian
          nkagaoan Naj added a comment - - edited

          closing this issue due to inactivity. please reopen if the issue persist

          nkagaoan Naj added a comment - - edited closing this issue due to inactivity. please reopen if the issue persist
          nkagaoan Naj made changes -
          Resolution Cannot Reproduce [ 5 ]
          Status Open [ 1 ] Closed [ 6 ]
          nkagaoan Naj made changes -
          Labels tracked-by-atlassian tracked-by-atlassian triaged

          People

            Unassigned Unassigned
            slyons22 Sean Lyons
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: