Hi Stefan I just had a look and noticed the following:
Your current configuration looks like this: whitelist.bundles.regexp="^org\.apache\.sling\.junit(\..*)?$" Inside target/slingstart.txt this becomes: whitelist.bundles.regexp="^org.apache.sling.junit(..*)?$" Note: all slashes have disappeared. When I escape the slashes, i.e. whitelist.bundles.regexp="^org\\.apache\\.sling\\.junit(\\..*)?$" target/slingstart.txt remains the same: whitelist.bundles.regexp="^org\\.apache\\.sling\\.junit(\\..*)?$" I believe there may be a bug in the escaping of provisioning models. Unless someone can advise how to preserve the single back-slashes from the original configuration. Note that if I set the regexp to "junit" the tests pass. Regards Julian On Mon, Nov 28, 2016 at 11:40 AM, Stefan Seifert <[email protected]> wrote: > for some time the caconfig integration tests are failing because the > org.apache.sling.junit.core is not whitelisted in LoginAdminWhitelist (see > [1]). > > but it is whitelisted via regexp (using the same merge-fix as robert for the > launchpad tests - see [2]). > > the resulting slingstart.txt in the build does contain the correct whitelist > information see [3] > > on my local machine the integration tests are running fine. on Jenkins they > fail. has anyone an idea what is going wrong? can someone reproduce the > failure locally? > > stefan > > [1] > https://builds.apache.org/job/sling-contrib-extensions-contextaware-config-integration-tests-1.8/201/console > > [2] > https://github.com/apache/sling/blob/trunk/contrib/extensions/contextaware-config/integration-tests/src/main/provisioning/sling.txt > > [3] > https://builds.apache.org/job/sling-contrib-extensions-contextaware-config-integration-tests-1.8/ws/target/slingstart.txt > >
