Use registry w/staging tag, not SHA, for tests

elastic · Jun 10, 2021 · d471ab3 · d471ab3
1 parent b35cde5
commit d471ab3
Showing 1 changed file with 1 addition and 2 deletions.
diff --git a/x-pack/test/fleet_api_integration/config.ts b/x-pack/test/fleet_api_integration/config.ts
@@ -14,8 +14,7 @@ import { defineDockerServersConfig } from '@kbn/test';
 // This hash comes from the latest successful build of the Snapshot Distribution of the Package Registry, for
 // example: https://beats-ci.elastic.co/blue/organizations/jenkins/Ingest-manager%2Fpackage-storage/detail/snapshot/74/pipeline/257#step-302-log-1.
 // It should be updated any time there is a new Docker image published for the Snapshot Distribution of the Package Registry.
-export const dockerImage =
-  'docker.elastic.co/package-registry/distribution:b6a53ac9300333a4a45f3f7d350c9aed72061a66';
+export const dockerImage = 'docker.elastic.co/package-registry/distribution:staging';
 
 export default async function ({ readConfigFile }: FtrConfigProviderContext) {
   const xPackAPITestsConfig = await readConfigFile(require.resolve('../api_integration/config.ts'));