Issues
- Requests to delete data should be handled asynchronouslyJJI-628Resolved issue: JJI-628
- Use a custom permission for triggering buildsJJI-627Resolved issue: JJI-627Mark Rekveld
- Only exclude Jenkins sites from hourly sync if registration is completeJJI-626Resolved issue: JJI-626
- Upgrade error from 4.0.1 to 4.1.0 (Lite)JJI-620Resolved issue: JJI-620Mark Rekveld
1-4 of 4
1 of 4
Requests to delete data should be handled asynchronously
Fixed
Description
Environment
None
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Unassigned
UnassignedReporter
Mark Rekveld
Mark RekveldFix versions
Affects versions
Priority
MajorZoom
Open Zoom
Created January 4, 2020 at 11:41 AM
Updated January 4, 2020 at 11:06 PM
Resolved January 4, 2020 at 11:06 PM
Activity
Show:
Delete requests are currently handled synchronously within the http request thread. 9 out of 10 times the delete operation will complete before the http timeout hits, but in cases of large data set it can become an issue that the delete operation exceeds the http timeout window and the transaction is rolled back resulting in undeletable data.
Delete requests for sites, jobs and builds should be handled asynchronously to the http request to allow the database transaction to complete even if it takes longer than the http request timeout window allows.