About Intercept

Intercept is a middleware in the TYPO3 ecosystem that does coordination and communication jobs between various services used for core development and documentation management. This web interface allows interacting with intercept to show and trigger certain jobs.

You can login to Intercept with your typo3.org account. This enables various interfaces to trigger intercept jobs. Members of the documentation team have additional access right to manage the documentation server deployments.

Pre-Merge Testing

Active

If a core patch is pushed to the gerrit review system at review.typo3.org, intercept triggers the according "pre-merge" core test suite at bamboo.typo3.com and reports the result back to the review system by voting on the patch.

GitHub Pull-Requests

Active
If a pull request is opened on the github main core repository at github/typo3/typo3.cms, intercept creates an issue from that pull request at forge.typo3.org, transfers the pull reqeust to a gerrit review review.typo3.org and closes the pull request with a remark that it has been transferred.

Nightly Builds

Active
Bamboo executes a nightly test build of all active TYPO3 core development branches. Intercept re-triggers those nightlies once if they failed, and reports a failing nightly build to slack channel #typo3-cms-coredev if it continues to fail.

Subtree Splitting

Active
If a TYPO3 core patch is merged in the review system, intercept executes the sub tree splitting of the main repository into the single core extensions repositories and pushes them to github.

Version Tagging

Active
When a new TYPO3 core version is tagged an released in the main core repository, intercept creates the needed tags in the sub tree repositories.

Documentation Rendering

Active

Intercept is the endpoint for the documentation hook, triggers documentation rendering in bamboo and deploys it to the documentation server. Members of the documentation team can manage redirects on the documentation server and deployed documentation.