# Legacy Hudson Integration Reference # Legacy Hudson Integration Reference **Last reviewed:** September 21, 2026 Hudson integration content is retained only as a legacy reference. New CI/CD work should use current Jenkins, GitHub Actions, or supported command-line/API integrations. ## When to use this guidance - You are maintaining an old environment that still references Hudson. - You need to migrate historical CI jobs to a supported CI/CD tool. - You are deciding whether to archive or consolidate older integration content. ## Recommended approach 1. Inventory any Hudson jobs that still trigger AIQ tests. 2. Capture job parameters, credentials, triggers, and report locations. 3. Recreate the workflow in a supported CI/CD platform. 4. Validate the migrated job with a small AIQ execution. 5. Mark Hudson-specific instructions as legacy or remove them when no longer needed. **Note:** Hudson is obsolete for current AIQ documentation. Prefer Jenkins or another supported CI/CD platform. --- Last updated: September 21, 2026 If you have feedback on this topic, contact .