<?xml version="1.0" encoding="UTF-8"?>
  <testsuites tests="154" disabled="119" errors="0" failures="0" time="1013.078628067">
      <testsuite name="Build Service E2E" package="/workspace/source/integration-tests/e2e" tests="154" disabled="7" skipped="112" errors="0" failures="0" time="1013.078628067" timestamp="2026-05-04T11:46:37">
          <properties>
              <property name="SuiteSucceeded" value="true"></property>
              <property name="SuiteHasProgrammaticFocus" value="false"></property>
              <property name="SpecialSuiteFailureReason" value=""></property>
              <property name="SuiteLabels" value="[]"></property>
              <property name="SuiteSemVerConstraints" value="[]"></property>
              <property name="SuiteComponentSemVerConstraints" value="[]"></property>
              <property name="RandomSeed" value="1777894920"></property>
              <property name="RandomizeAllSpecs" value="false"></property>
              <property name="LabelFilter" value="build-service &amp;&amp; github &amp;&amp; !github-webhook"></property>
              <property name="SemVerFilter" value=""></property>
              <property name="FocusStrings" value=""></property>
              <property name="SkipStrings" value=""></property>
              <property name="FocusFiles" value=""></property>
              <property name="SkipFiles" value=""></property>
              <property name="FailOnPending" value="false"></property>
              <property name="FailOnEmpty" value="true"></property>
              <property name="FailFast" value="false"></property>
              <property name="FlakeAttempts" value="0"></property>
              <property name="DryRun" value="false"></property>
              <property name="ParallelTotal" value="5"></property>
              <property name="OutputInterceptorMode" value="none"></property>
          </properties>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named &#39;main&#39;) with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the PaC init branch is merged retriggered pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl PaC component build when the component is removed and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, gitlab, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace triggers a PipelineRun for parent component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gl component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, gitlab]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named &#39;main&#39;) with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the PaC init branch is merged retriggered pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj PaC component build when the component is removed and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, forgejo, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace triggers a PipelineRun for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider fj component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, forgejo]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build annotations when component is created with invalid build request annotations handles invalid request annotation [build-service, github, annotations]" classname="Build Service E2E" status="passed" time="72.392402838">
              <system-err>&gt; Enter [BeforeAll] test build annotations - /workspace/source/integration-tests/e2e/annotations.go:35 @ 05/04/26 11:46:37.633&#xA;&lt; Exit [BeforeAll] test build annotations - /workspace/source/integration-tests/e2e/annotations.go:35 @ 05/04/26 11:46:39.298 (1.665s)&#xA;&gt; Enter [BeforeAll] when component is created with invalid build request annotations - /workspace/source/integration-tests/e2e/annotations.go:69 @ 05/04/26 11:46:39.298&#xA;Image repository for component test-annotations-qrolrt in namespace build-e2e-ufdx do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [BeforeAll] when component is created with invalid build request annotations - /workspace/source/integration-tests/e2e/annotations.go:69 @ 05/04/26 11:46:49.42 (10.121s)&#xA;&gt; Enter [It] handles invalid request annotation - /workspace/source/integration-tests/e2e/annotations.go:89 @ 05/04/26 11:46:49.42&#xA;build status annotation value: {&#34;message&#34;:&#34;unexpected build request: foo&#34;}&#xA;&lt; Exit [It] handles invalid request annotation - /workspace/source/integration-tests/e2e/annotations.go:89 @ 05/04/26 11:47:49.479 (1m0.059s)&#xA;&gt; Enter [AfterAll] test build annotations - /workspace/source/integration-tests/e2e/annotations.go:51 @ 05/04/26 11:47:49.479&#xA;&lt; Exit [AfterAll] test build annotations - /workspace/source/integration-tests/e2e/annotations.go:51 @ 05/04/26 11:47:50.025 (546ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/annotations.go:24 @ 05/04/26 11:47:50.025&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/annotations.go:24 @ 05/04/26 11:47:50.025 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created creates first component [build-service, github, pac-build, secret-lookup]" classname="Build Service E2E" status="passed" time="14.240810299">
              <system-err>&gt; Enter [BeforeAll] test build secret lookup - /workspace/source/integration-tests/e2e/secret_lookup.go:32 @ 05/04/26 11:46:37.622&#xA;&lt; Exit [BeforeAll] test build secret lookup - /workspace/source/integration-tests/e2e/secret_lookup.go:32 @ 05/04/26 11:46:41.606 (3.984s)&#xA;&gt; Enter [BeforeAll] when two secrets are created - /workspace/source/integration-tests/e2e/secret_lookup.go:100 @ 05/04/26 11:46:41.606&#xA;&lt; Exit [BeforeAll] when two secrets are created - /workspace/source/integration-tests/e2e/secret_lookup.go:100 @ 05/04/26 11:46:41.734 (127ms)&#xA;&gt; Enter [It] creates first component - /workspace/source/integration-tests/e2e/secret_lookup.go:123 @ 05/04/26 11:46:41.734&#xA;Image repository for component component-one-amiu in namespace build-e2e-ridz do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates first component - /workspace/source/integration-tests/e2e/secret_lookup.go:123 @ 05/04/26 11:46:51.862 (10.128s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/secret_lookup.go:25 @ 05/04/26 11:46:51.863&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/secret_lookup.go:25 @ 05/04/26 11:46:51.863 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created creates second component [build-service, github, pac-build, secret-lookup]" classname="Build Service E2E" status="passed" time="10.125243876">
              <system-err>&gt; Enter [It] creates second component - /workspace/source/integration-tests/e2e/secret_lookup.go:140 @ 05/04/26 11:46:51.863&#xA;Image repository for component component-two-gkmj in namespace build-e2e-ridz do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates second component - /workspace/source/integration-tests/e2e/secret_lookup.go:140 @ 05/04/26 11:47:01.988 (10.125s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/secret_lookup.go:25 @ 05/04/26 11:47:01.988&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/secret_lookup.go:25 @ 05/04/26 11:47:01.989 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created check first component annotation has errors [build-service, github, pac-build, secret-lookup]" classname="Build Service E2E" status="passed" time="0.066233801">
              <system-err>&gt; Enter [It] check first component annotation has errors - /workspace/source/integration-tests/e2e/secret_lookup.go:158 @ 05/04/26 11:47:01.989&#xA;build status annotation value: {&#34;pac&#34;:{&#34;state&#34;:&#34;error&#34;,&#34;error-id&#34;:74,&#34;error-message&#34;:&#34;74: Access token is unrecognizable by GitHub&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;&lt; Exit [It] check first component annotation has errors - /workspace/source/integration-tests/e2e/secret_lookup.go:158 @ 05/04/26 11:47:02.055 (66ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/secret_lookup.go:25 @ 05/04/26 11:47:02.055&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/secret_lookup.go:25 @ 05/04/26 11:47:02.055 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created triggered PipelineRun is for component  [build-service, github, pac-build, secret-lookup]" classname="Build Service E2E" status="passed" time="20.182724775">
              <system-err>&gt; Enter [It] triggered PipelineRun is for component  - /workspace/source/integration-tests/e2e/secret_lookup.go:178 @ 05/04/26 11:47:02.056&#xA;PipelineRun has not been created yet for the component build-e2e-ridz/component-two-gkmj&#xA;&lt; Exit [It] triggered PipelineRun is for component  - /workspace/source/integration-tests/e2e/secret_lookup.go:178 @ 05/04/26 11:47:22.238 (20.182s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/secret_lookup.go:25 @ 05/04/26 11:47:22.238&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/secret_lookup.go:25 @ 05/04/26 11:47:22.238 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created check only one pipelinerun should be triggered [build-service, github, pac-build, secret-lookup]" classname="Build Service E2E" status="passed" time="122.854650762">
              <system-err>&gt; Enter [It] check only one pipelinerun should be triggered - /workspace/source/integration-tests/e2e/secret_lookup.go:193 @ 05/04/26 11:47:22.239&#xA;&lt; Exit [It] check only one pipelinerun should be triggered - /workspace/source/integration-tests/e2e/secret_lookup.go:193 @ 05/04/26 11:49:22.24 (2m0.001s)&#xA;&gt; Enter [AfterAll] test build secret lookup - /workspace/source/integration-tests/e2e/secret_lookup.go:61 @ 05/04/26 11:49:22.24&#xA;&lt; Exit [AfterAll] test build secret lookup - /workspace/source/integration-tests/e2e/secret_lookup.go:61 @ 05/04/26 11:49:25.093 (2.853s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/secret_lookup.go:25 @ 05/04/26 11:49:25.094&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/secret_lookup.go:25 @ 05/04/26 11:49:25.094 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test build secret lookup when two secrets are created when second component is deleted, pac pr branch should not exist in the repo [build-service, github, pac-build, secret-lookup]" classname="Build Service E2E" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private correctly targets the default branch (that is not named &#39;main&#39;) with PaC [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private workspace parameter is set correctly in PaC repository CR [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private build pipeline uses the correct serviceAccount [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private component build status is set correctly [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private created image repo is private [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private a related PipelineRun should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private PR branch should not exist in the repo [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new component without specified branch is created and with visibility private related image repo and the robot account should be deleted after deleting the component [build-service, github-webhook, pac-build, pipeline, image-controller, github, pac-custom-default-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created triggers a PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created should lead to a PaC init PR creation [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created the PipelineRun should eventually finish successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created image repo and robot account created successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created created image repo is public [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created image tag is updated successfully [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created should ensure pruning labels are set [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when a new Component with specified custom branch is created eventually leads to the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated should lead to a PaC init PR update [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated PipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is updated eventually leads to another update of a PR about the PipelineRun status report at Checks tab [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged eventually leads to triggering another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged does not have expiration set [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged After updating image visibility to private, it should not trigger another PipelineRun [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged image repo is updated to private [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged retrigger the pipeline manually [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the PaC init branch is merged retriggered pipelineRun should eventually finish [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="pending" time="0">
              <skipped message="pending"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh PaC component build when the component is removed and recreated (with the same name in the same namespace) should no longer lead to a creation of a PaC PR [build-service, github-webhook, pac-build, pipeline, image-controller, github, build-custom-branch]" classname="Build Service E2E" status="skipped" time="0">
              <skipped message="skipped"></skipped>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace creates component with nudges [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="37.413135935">
              <system-err>&gt; Enter [BeforeAll] component update with renovate - /workspace/source/integration-tests/e2e/renovate.go:72 @ 05/04/26 11:46:37.631&#xA;ReleaseAdmissionPlan data: {&#34;Mapping&#34;:{&#34;Components&#34;:[{&#34;Name&#34;:&#34;gh-multi-component-parent-jwwq&#34;,&#34;Repository&#34;:&#34;quay.io/redhat-appstudio-qe/release-repository&#34;}]}}&#xA;&lt; Exit [BeforeAll] component update with renovate - /workspace/source/integration-tests/e2e/renovate.go:72 @ 05/04/26 11:46:54.788 (17.158s)&#xA;&gt; Enter [It] creates component with nudges - /workspace/source/integration-tests/e2e/renovate.go:235 @ 05/04/26 11:46:54.789&#xA;Image repository for component gh-multi-component-child-jwwq in namespace build-e2e-obnt do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;Image repository for component gh-multi-component-parent-jwwq in namespace build-e2e-obnt do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates component with nudges - /workspace/source/integration-tests/e2e/renovate.go:235 @ 05/04/26 11:47:15.043 (20.255s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:47:15.043&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:47:15.043 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace triggers a PipelineRun for parent component  [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="20.410646693">
              <system-err>&gt; Enter [It] triggers a PipelineRun for parent component  - /workspace/source/integration-tests/e2e/renovate.go:259 @ 05/04/26 11:47:15.044&#xA;PipelineRun has not been created yet for the component build-e2e-obnt/gh-multi-component-parent-jwwq&#xA;&lt; Exit [It] triggers a PipelineRun for parent component  - /workspace/source/integration-tests/e2e/renovate.go:259 @ 05/04/26 11:47:35.454 (20.41s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:47:35.455&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:47:35.455 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for parent component  [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="400.173282815">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for parent component  - /workspace/source/integration-tests/e2e/renovate.go:274 @ 05/04/26 11:47:35.455&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z found for Component build-e2e-obnt/gh-multi-component-parent-jwwq&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-pull-request-2b82z reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for parent component  - /workspace/source/integration-tests/e2e/renovate.go:274 @ 05/04/26 11:54:15.628 (6m40.173s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:15.628&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:15.628 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace the PipelineRun should eventually finish successfully for child component  [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="0.060778204">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for child component  - /workspace/source/integration-tests/e2e/renovate.go:285 @ 05/04/26 11:54:15.629&#xA;PipelineRun gh-multi-component-child-jwwq-on-pull-request-srw6s found for Component build-e2e-obnt/gh-multi-component-child-jwwq&#xA;PipelineRun gh-multi-component-child-jwwq-on-pull-request-srw6s reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for child component  - /workspace/source/integration-tests/e2e/renovate.go:285 @ 05/04/26 11:54:15.69 (60ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:15.69&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:15.69 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a PaC PR creation for child component  [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="0.214803502">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for child component  - /workspace/source/integration-tests/e2e/renovate.go:289 @ 05/04/26 11:54:15.69&#xA;&lt; Exit [It] should lead to a PaC PR creation for child component  - /workspace/source/integration-tests/e2e/renovate.go:289 @ 05/04/26 11:54:15.905 (214ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:15.905&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:15.905 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Merging the PaC PR should be successful for child component  [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="1.795812409">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for child component  - /workspace/source/integration-tests/e2e/renovate.go:307 @ 05/04/26 11:54:15.906&#xA;merged result sha: a3bfefe80e09655b4da3b25e3d4a14cb13b3e4c2 for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for child component  - /workspace/source/integration-tests/e2e/renovate.go:307 @ 05/04/26 11:54:17.701 (1.795s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:17.701&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:17.701 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace create dockerfile and yaml manifest that references build and distribution repositories [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="4.994427321">
              <system-err>&gt; Enter [It] create dockerfile and yaml manifest that references build and distribution repositories - /workspace/source/integration-tests/e2e/renovate.go:318 @ 05/04/26 11:54:17.702&#xA;&lt; Exit [It] create dockerfile and yaml manifest that references build and distribution repositories - /workspace/source/integration-tests/e2e/renovate.go:318 @ 05/04/26 11:54:22.696 (4.994s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:22.696&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:22.696 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a PaC PR creation for parent component  [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="0.137076957">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for parent component  - /workspace/source/integration-tests/e2e/renovate.go:358 @ 05/04/26 11:54:22.697&#xA;&lt; Exit [It] should lead to a PaC PR creation for parent component  - /workspace/source/integration-tests/e2e/renovate.go:358 @ 05/04/26 11:54:22.834 (137ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:22.834&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:22.834 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Merging the PaC PR should be successful for parent component  [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="1.676265414">
              <system-err>&gt; Enter [It] Merging the PaC PR should be successful for parent component  - /workspace/source/integration-tests/e2e/renovate.go:375 @ 05/04/26 11:54:22.834&#xA;merged result sha: af90bb543ca9b630d3b5fd088749c09c7aefd6a3 for PR #1&#xA;&lt; Exit [It] Merging the PaC PR should be successful for parent component  - /workspace/source/integration-tests/e2e/renovate.go:375 @ 05/04/26 11:54:24.51 (1.676s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:24.511&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:24.511 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace PR merge triggers PAC PipelineRun for parent component  [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="20.182709536">
              <system-err>&gt; Enter [It] PR merge triggers PAC PipelineRun for parent component  - /workspace/source/integration-tests/e2e/renovate.go:385 @ 05/04/26 11:54:24.511&#xA;Push PipelineRun has not been created yet for the component build-e2e-obnt/gh-multi-component-parent-jwwq&#xA;&lt; Exit [It] PR merge triggers PAC PipelineRun for parent component  - /workspace/source/integration-tests/e2e/renovate.go:385 @ 05/04/26 11:54:44.694 (20.182s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:44.694&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:54:44.694 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace PAC PipelineRun for parent component  is successful [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="240.174995918">
              <system-err>&gt; Enter [It] PAC PipelineRun for parent component  is successful - /workspace/source/integration-tests/e2e/renovate.go:401 @ 05/04/26 11:54:44.694&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 found for Component build-e2e-obnt/gh-multi-component-parent-jwwq&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: ResolvingTaskRef&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: Running&#xA;PipelineRun gh-multi-component-parent-jwwq-on-push-sgpr9 reason: Completed&#xA;&lt; Exit [It] PAC PipelineRun for parent component  is successful - /workspace/source/integration-tests/e2e/renovate.go:401 @ 05/04/26 11:58:44.869 (4m0.175s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:58:44.869&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 11:58:44.869 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace should lead to a nudge PR creation for child component  [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="166.723531668">
              <system-err>&gt; Enter [It] should lead to a nudge PR creation for child component  - /workspace/source/integration-tests/e2e/renovate.go:412 @ 05/04/26 11:58:44.87&#xA;&lt; Exit [It] should lead to a nudge PR creation for child component  - /workspace/source/integration-tests/e2e/renovate.go:412 @ 05/04/26 12:01:31.593 (2m46.723s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 12:01:31.593&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 12:01:31.594 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace merging the PR should be successful for child component  [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="2.29202482">
              <system-err>&gt; Enter [It] merging the PR should be successful for child component  - /workspace/source/integration-tests/e2e/renovate.go:429 @ 05/04/26 12:01:31.594&#xA;merged result sha: 57ecc4952bf7a436d6cba52f21168fef2616a1a7 for PR #3&#xA;&lt; Exit [It] merging the PR should be successful for child component  - /workspace/source/integration-tests/e2e/renovate.go:429 @ 05/04/26 12:01:33.886 (2.292s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 12:01:33.886&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 12:01:33.886 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test git provider gh component update with renovate when components are created in same namespace Verify the nudge updated the contents [build-service, renovate, multi-component, github]" classname="Build Service E2E" status="passed" time="16.534663288">
              <system-err>&gt; Enter [It] Verify the nudge updated the contents - /workspace/source/integration-tests/e2e/renovate.go:440 @ 05/04/26 12:01:33.887&#xA;Verifying Dockerfile.tmp updated to sha sha256:56b4fdb0074ef25c7c553210737719ecc37877570459cdb0e80fa472207dd23dcontent: FROM quay.io/redhat-appstudio-qe/build-e2e-obnt/gh-multi-component-parent-jwwq@sha256:56b4fdb0074ef25c7c553210737719ecc37877570459cdb0e80fa472207dd23d&#xA;RUN echo hello&#xA;&#xA;&lt; Exit [It] Verify the nudge updated the contents - /workspace/source/integration-tests/e2e/renovate.go:440 @ 05/04/26 12:01:34.061 (174ms)&#xA;&gt; Enter [AfterAll] component update with renovate - /workspace/source/integration-tests/e2e/renovate.go:214 @ 05/04/26 12:01:34.061&#xA;&lt; Exit [AfterAll] component update with renovate - /workspace/source/integration-tests/e2e/renovate.go:214 @ 05/04/26 12:01:50.421 (16.36s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 12:01:50.421&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/renovate.go:28 @ 05/04/26 12:01:50.421 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory go-component [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="13.671400037">
              <system-err>&gt; Enter [BeforeAll] test pac with multiple components using same repository - /workspace/source/integration-tests/e2e/multi_component.go:40 @ 05/04/26 11:46:37.627&#xA;&lt; Exit [BeforeAll] test pac with multiple components using same repository - /workspace/source/integration-tests/e2e/multi_component.go:40 @ 05/04/26 11:46:41.164 (3.536s)&#xA;&gt; Enter [It] creates component with context directory go-component - /workspace/source/integration-tests/e2e/multi_component.go:106 @ 05/04/26 11:46:41.164&#xA;Image repository for component go-component-wgsgzy in namespace build-e2e-ijuk do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates component with context directory go-component - /workspace/source/integration-tests/e2e/multi_component.go:106 @ 05/04/26 11:46:51.298 (10.134s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:46:51.298&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:46:51.299 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace triggers a PipelineRun for component go-component-wgsgzy [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="20.237610662">
              <system-err>&gt; Enter [It] triggers a PipelineRun for component go-component-wgsgzy - /workspace/source/integration-tests/e2e/multi_component.go:125 @ 05/04/26 11:46:51.299&#xA;PipelineRun has not been created yet for the component build-e2e-ijuk/go-component-wgsgzy&#xA;&lt; Exit [It] triggers a PipelineRun for component go-component-wgsgzy - /workspace/source/integration-tests/e2e/multi_component.go:125 @ 05/04/26 11:47:11.537 (20.237s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:47:11.537&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:47:11.537 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace should lead to a PaC PR creation for component go-component-wgsgzy [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="0.42359938">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for component go-component-wgsgzy - /workspace/source/integration-tests/e2e/multi_component.go:140 @ 05/04/26 11:47:11.538&#xA;&lt; Exit [It] should lead to a PaC PR creation for component go-component-wgsgzy - /workspace/source/integration-tests/e2e/multi_component.go:140 @ 05/04/26 11:47:11.961 (423ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:47:11.961&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:47:11.961 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace the PipelineRun should eventually finish successfully for component go-component-wgsgzy [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="460.192502071">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for component go-component-wgsgzy - /workspace/source/integration-tests/e2e/multi_component.go:159 @ 05/04/26 11:47:11.962&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f found for Component build-e2e-ijuk/go-component-wgsgzy&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: ResolvingTaskRef&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Running&#xA;PipelineRun go-component-wgsgzy-on-pull-request-wpb8f reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for component go-component-wgsgzy - /workspace/source/integration-tests/e2e/multi_component.go:159 @ 05/04/26 11:54:52.154 (7m40.192s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:54:52.154&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:54:52.154 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace merging the PR should be successful [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="1.958889737">
              <system-err>&gt; Enter [It] merging the PR should be successful - /workspace/source/integration-tests/e2e/multi_component.go:164 @ 05/04/26 11:54:52.155&#xA;merged result sha: b28fa013894b58541ad6bcb3927bcaf1024a1e8a for PR #32829&#xA;&lt; Exit [It] merging the PR should be successful - /workspace/source/integration-tests/e2e/multi_component.go:164 @ 05/04/26 11:54:54.113 (1.958s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:54:54.113&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:54:54.113 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace leads to triggering on push PipelineRun [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="20.195424745">
              <system-err>&gt; Enter [It] leads to triggering on push PipelineRun - /workspace/source/integration-tests/e2e/multi_component.go:174 @ 05/04/26 11:54:54.114&#xA;Push PipelineRun has not been created yet for the component build-e2e-ijuk/go-component-wgsgzy&#xA;&lt; Exit [It] leads to triggering on push PipelineRun - /workspace/source/integration-tests/e2e/multi_component.go:174 @ 05/04/26 11:55:14.309 (20.195s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:55:14.309&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:55:14.31 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace creates component with context directory python-component [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="10.134715632">
              <system-err>&gt; Enter [It] creates component with context directory python-component - /workspace/source/integration-tests/e2e/multi_component.go:106 @ 05/04/26 11:55:14.31&#xA;Image repository for component python-component-zdlobg in namespace build-e2e-ijuk do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [It] creates component with context directory python-component - /workspace/source/integration-tests/e2e/multi_component.go:106 @ 05/04/26 11:55:24.444 (10.134s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:55:24.445&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:55:24.445 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace triggers a PipelineRun for component python-component-zdlobg [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="20.195912952">
              <system-err>&gt; Enter [It] triggers a PipelineRun for component python-component-zdlobg - /workspace/source/integration-tests/e2e/multi_component.go:125 @ 05/04/26 11:55:24.446&#xA;PipelineRun has not been created yet for the component build-e2e-ijuk/python-component-zdlobg&#xA;&lt; Exit [It] triggers a PipelineRun for component python-component-zdlobg - /workspace/source/integration-tests/e2e/multi_component.go:125 @ 05/04/26 11:55:44.641 (20.196s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:55:44.641&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:55:44.641 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace should lead to a PaC PR creation for component python-component-zdlobg [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="0.393433428">
              <system-err>&gt; Enter [It] should lead to a PaC PR creation for component python-component-zdlobg - /workspace/source/integration-tests/e2e/multi_component.go:140 @ 05/04/26 11:55:44.642&#xA;&lt; Exit [It] should lead to a PaC PR creation for component python-component-zdlobg - /workspace/source/integration-tests/e2e/multi_component.go:140 @ 05/04/26 11:55:45.035 (393ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:55:45.035&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 11:55:45.035 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace the PipelineRun should eventually finish successfully for component python-component-zdlobg [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="420.193517206">
              <system-err>&gt; Enter [It] the PipelineRun should eventually finish successfully for component python-component-zdlobg - /workspace/source/integration-tests/e2e/multi_component.go:159 @ 05/04/26 11:55:45.036&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc found for Component build-e2e-ijuk/python-component-zdlobg&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: ResolvingTaskRef&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: ResolvingTaskRef&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Running&#xA;PipelineRun python-component-zdlobg-on-pull-request-hgvrc reason: Completed&#xA;&lt; Exit [It] the PipelineRun should eventually finish successfully for component python-component-zdlobg - /workspace/source/integration-tests/e2e/multi_component.go:159 @ 05/04/26 12:02:45.229 (7m0.193s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 12:02:45.229&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 12:02:45.229 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace merging the PR should be successful [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="2.121169405">
              <system-err>&gt; Enter [It] merging the PR should be successful - /workspace/source/integration-tests/e2e/multi_component.go:164 @ 05/04/26 12:02:45.23&#xA;merged result sha: e83b2da2423575b4cd4ebb3daab1090aa9513b10 for PR #32831&#xA;&lt; Exit [It] merging the PR should be successful - /workspace/source/integration-tests/e2e/multi_component.go:164 @ 05/04/26 12:02:47.351 (2.121s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 12:02:47.351&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 12:02:47.351 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace leads to triggering on push PipelineRun [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="20.197483194">
              <system-err>&gt; Enter [It] leads to triggering on push PipelineRun - /workspace/source/integration-tests/e2e/multi_component.go:174 @ 05/04/26 12:02:47.352&#xA;Push PipelineRun has not been created yet for the component build-e2e-ijuk/python-component-zdlobg&#xA;&lt; Exit [It] leads to triggering on push PipelineRun - /workspace/source/integration-tests/e2e/multi_component.go:174 @ 05/04/26 12:03:07.549 (20.197s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 12:03:07.549&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 12:03:07.549 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace only one component is changed [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="3.458463558">
              <system-err>&gt; Enter [It] only one component is changed - /workspace/source/integration-tests/e2e/multi_component.go:190 @ 05/04/26 12:03:07.55&#xA;PR #32833 got created with sha e71dee323e6c16d3cfaf49cd6de5b851b1e456db&#xA;&lt; Exit [It] only one component is changed - /workspace/source/integration-tests/e2e/multi_component.go:190 @ 05/04/26 12:03:11.008 (3.458s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 12:03:11.008&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 12:03:11.008 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when components are created in same namespace only related pipelinerun should be triggered [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="0.191792906">
              <system-err>&gt; Enter [It] only related pipelinerun should be triggered - /workspace/source/integration-tests/e2e/multi_component.go:205 @ 05/04/26 12:03:11.009&#xA;&lt; Exit [It] only related pipelinerun should be triggered - /workspace/source/integration-tests/e2e/multi_component.go:205 @ 05/04/26 12:03:11.2 (191ms)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 12:03:11.2&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 12:03:11.2 (0s)&#xA;</system-err>
          </testcase>
          <testcase name="[It] [build-service-suite Build service E2E tests] test pac with multiple components using same repository when a components is created with same git url in different namespace should fail to configure PaC for the component [build-service, github, pac-build, multi-component]" classname="Build Service E2E" status="passed" time="19.494153428">
              <system-err>&gt; Enter [BeforeAll] when a components is created with same git url in different namespace - /workspace/source/integration-tests/e2e/multi_component.go:223 @ 05/04/26 12:03:11.201&#xA;Image repository for component go-component-davguj in namespace build-e2e-gezk do not have right state (&#39;&#39; != &#39;ready&#39;) yet but it has status {  { } {&lt;nil&gt;      } []}.&#xA;&lt; Exit [BeforeAll] when a components is created with same git url in different namespace - /workspace/source/integration-tests/e2e/multi_component.go:223 @ 05/04/26 12:03:22.668 (11.468s)&#xA;&gt; Enter [It] should fail to configure PaC for the component - /workspace/source/integration-tests/e2e/multi_component.go:264 @ 05/04/26 12:03:22.669&#xA;build status annotation value: {&#34;pac&#34;:{&#34;state&#34;:&#34;error&#34;,&#34;error-id&#34;:53,&#34;error-message&#34;:&#34;53: Git repository is already handled by Pipelines as Code&#34;},&#34;message&#34;:&#34;done&#34;}&#xA;build status: &amp;{State:error MergeUrl: ConfigurationTime: ErrorInfo:{ErrId:53 ErrMessage:53: Git repository is already handled by Pipelines as Code}}&#xA;&lt; Exit [It] should fail to configure PaC for the component - /workspace/source/integration-tests/e2e/multi_component.go:264 @ 05/04/26 12:03:22.734 (65ms)&#xA;&gt; Enter [AfterAll] when a components is created with same git url in different namespace - /workspace/source/integration-tests/e2e/multi_component.go:253 @ 05/04/26 12:03:22.734&#xA;&lt; Exit [AfterAll] when a components is created with same git url in different namespace - /workspace/source/integration-tests/e2e/multi_component.go:253 @ 05/04/26 12:03:23.065 (331ms)&#xA;&gt; Enter [AfterAll] test pac with multiple components using same repository - /workspace/source/integration-tests/e2e/multi_component.go:68 @ 05/04/26 12:03:23.065&#xA;&lt; Exit [AfterAll] test pac with multiple components using same repository - /workspace/source/integration-tests/e2e/multi_component.go:68 @ 05/04/26 12:03:30.695 (7.63s)&#xA;&gt; Enter [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 12:03:30.695&#xA;&lt; Exit [AfterEach] [build-service-suite Build service E2E tests] - /workspace/source/integration-tests/e2e/multi_component.go:28 @ 05/04/26 12:03:30.695 (0s)&#xA;</system-err>
          </testcase>
      </testsuite>
  </testsuites>