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
- The Deployment Environment Parser incorrectly assumes the environment exported object is created by the Jenkins counterpart add-onJJI-625Resolved issue: JJI-625
- Add build filtering options to build panelsJJI-623Resolved issue: JJI-623
1-5 of 5
1 of 5
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.