Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Cannot Reproduce
-
Jenkins Version: 2.176.1
Atlassian Bitbucket v5.16.2
Bitbucket Server Integration 1.0.4
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
Sean Lyons
created issue -
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. |
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. |
Sean Lyons
made changes -
| Attachment | installed_plugins.txt [ 50395 ] |
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.
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. | Assignee | Kristy Hughes [ khughes ] |
B Plump
made changes -
| Labels | tracked-by-atlassian |
closing this issue due to inactivity. please reopen if the issue persist
Naj
added a comment - - edited closing this issue due to inactivity. please reopen if the issue persist Naj
made changes -
| Resolution | Cannot Reproduce [ 5 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
Naj
made changes -
| Labels | tracked-by-atlassian | tracked-by-atlassian triaged |
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.)?