Skip to content

34324 implement api to retry bundles#34483

Draft
hassandotcms wants to merge 5 commits intomainfrom
34324-implement-api-to-retry-bundles
Draft

34324 implement api to retry bundles#34483
hassandotcms wants to merge 5 commits intomainfrom
34324-implement-api-to-retry-bundles

Conversation

@hassandotcms
Copy link
Contributor

@hassandotcms hassandotcms commented Feb 3, 2026 •
edited by github-actions bot
Loading

Proposed Changes

  • Add POST /v1/publishing/retry endpoint to replace legacy AJAX RemotePublishAjaxAction
  • Support bulk retry with configurable delivery strategy and force push option
  • Add integration tests for retry endpoint

Checklist

  • Tests
  • Translations
  • Security Implications Contemplated (add notes if applicable)

Additional Info

** any additional useful context or info **

Screenshots

Original Updated
** original screenshot ** ** updated screenshot **

This PR fixes: #34324

@hassandotcms
feat(publishing): add form and view classes for bundle retry endpoint #…
f275511 
…34324

Add request/response DTOs for POST /v1/publishing/retry:
- AbstractRetryBundlesForm: request body with bundleIds, forcePush, deliveryStrategy
- AbstractRetryBundleResultView: per-bundle result with success/failure details
- ResponseEntityRetryBundlesView: typed wrapper for Swagger documentation
- RetryResultDTO: internal DTO for helper-to-resource communication
@hassandotcms
feat(publishing): add PublishingRetryHelper for bundle retry business…
f99936d 
… logic #34324

Extract and modernize retry logic from RemotePublishAjaxAction.retry().

Supports:
- Push Publishing (remote dotCMS servers)
- Static Publishing (AWS S3 or file system)
- Delivery strategies: ALL_ENDPOINTS or FAILED_ENDPOINTS
- Force push for re-synchronization of successful bundles
@hassandotcms
feat(publishing): add POST /v1/publishing/retry endpoint #34324
1334e1e 
Bulk retry endpoint to replace legacy AJAX RemotePublishAjaxAction.

- Retry multiple bundles in single request
- Per-bundle success/failure results
- Configurable delivery strategy
- Force push option for content re-synchronization
@hassandotcms
test(publishing): add integration tests for bundle retry endpoint #34324
e51b48f 


Coverage includes:
- Successful single and bulk retry operations
- Error cases: invalid bundleId, non-existent bundle, non-retryable status
- Delivery strategy validation
- Force push behavior
- Mixed results in bulk operations
@hassandotcms
Merge branch 'main' of https://github.com/dotCMS/core into 34324-impl…
6251962 
…ement-api-to-retry-bundles
@hassandotcms hassandotcms linked an issue Feb 3, 2026 that may be closed by this pull request
[TASK] Implement POST /v1/publishing/retry - Retry failed/successful bundles #34324
Open
@github-actions github-actions bot mentioned this pull request Feb 3, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

dotCMS - Product Planning
Status: No status

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[TASK] Implement POST /v1/publishing/retry - Retry failed/successful bundles

1 participant

@hassandotcms