Provision a dedicated Jenkins instance for ThreadX

Summary

The webdev team is working on a solution to publish ThreadX documentation to the threadx.io website. This effort is tracked in this issue: https://gitlab.eclipse.org/eclipsefdn/it/websites/threadx.io/-/issues/5

The documentation's source resides in a GitHub repository. From what I understand, the web dev team implemented a solution to publish the documentation through a Docker container controlled through Jenkins. @cguindon and @malowe can provide additional details if needed.

@heurtemattes recommended provisioning a dedicated Jenkins instance for ThreadX and moving existing jobs to that new instance. I would like to request that formally on behalf of the ThreadX project team.

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

The current setup works. However, it is unusual and, I suppose, introduces a certain level of risk since the container interacts with EF infrastructure. This is not urgent from my perspective, but your risk assessment could naturally incite you to proceed earlier rather than later.

I appreciate your support.