Change standalone debugger to no longer limit number of bundles

.github/workflows/build-test.yml

@@ -47,7 +47,6 @@ jobs:
           clean verify -B -V \
           -Dmaven.test.failure.ignore=true \
           -DexcludedGroups=flakyTest,slowTest \
-          -P build-standalone-debugger-rcp \
           -Ddsf.gdb.tests.timeout.multiplier=50 \
           -Ddsf-gdb.skip.tests=$(test ${{ steps.filter.outputs.dsf }} == 'false' && echo 'true' || echo 'false') \
           -Dindexer.timeout=300

BUILDING.md

@@ -38,11 +38,6 @@ Individual p2 repos can be turned on and off to allow building CDT, or parts of
 - test CDT against a pre-built CDT by using the cdtRepo profile.
 - build the standalone rcp debugger against the latest simrel `mvn verify -DuseSimrelRepo -f debug/org.eclipse.cdt.debug.application.product`
 
-#### build-standalone-debugger-rcp
-
-Using the `build-standalone-debugger-rcp` profile will include the standalone debugger, located
-in `debug/org.eclipse.cdt.debug.application.product`
-
 #### skip-all-tests, skip-tests-except-cdt-ui, skip-tests-except-dsf-gdb, skip-tests-except-cdt-other
 
 Using any of the above profiles can skip large sets of tests. The CI build uses this to parallelize tests. See https://ci.eclipse.org/cdt/view/Gerrit/

Jenkinsfile

@@ -48,7 +48,6 @@ pipeline {
                       -Ddsf.gdb.tests.timeout.multiplier=50 \
                       -Dindexer.timeout=300 \
                       -P production \
-                      -P build-standalone-debugger-rcp \
                       -Ddsf.gdb.tests.gdbPath=/shared/common/gdb/gdb-all/bin \
                       -Dcdt.tests.dsf.gdb.versions=gdb.10,gdbserver.10 \
                       -Dmaven.repo.local=/home/jenkins/.m2/repository \