Add option to use Nexus repository mirror to speed up e2e testing #2387
Assignees
Labels
area/continuous integration
Related to CI and automated testing
Comments
tadayosi
added
the
area/continuous integration
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jun 10, 2021
* Testing hook looks for 'nexus' service in 'nexus' ns and if available it's automatically assigned to camel-k platform as the maven mirror * Nexus mirroring can be explicitly disabled by TEST_DISABLE_NEXUS=true env variable.
|
Hmm it earns just 7mins for openshift-build on CI. But maybe still worth applying as it will also speed up local e2e testing as well and network friendly. before: after: |
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jun 10, 2021
* Testing hook looks for 'nexus' service in 'nexus' ns and if available it's automatically assigned to camel-k platform as the maven mirror * Nexus mirroring can be explicitly disabled by TEST_DISABLE_NEXUS=true env variable.
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jun 10, 2021
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jun 11, 2021
…2387 If env variable TEST_ENABLE_NEXUS=true is set, testing hook will look for 'nexus' service in 'nexus' ns and if available it's assigned to camel-k platform as the maven mirror during e2e testing.
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jun 11, 2021
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jun 11, 2021
…2387 If env variable TEST_ENABLE_NEXUS=true is set, testing hook will look for 'nexus' service in 'nexus' ns and if available it's assigned to camel-k platform as the maven mirror during e2e testing.
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jun 11, 2021
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jun 11, 2021
tadayosi
added a commit
to tadayosi/camel-k
that referenced
this issue
Jun 11, 2021
tadayosi
added a commit
that referenced
this issue
Jun 11, 2021
If env variable TEST_ENABLE_NEXUS=true is set, testing hook will look for 'nexus' service in 'nexus' ns and if available it's assigned to camel-k platform as the maven mirror during e2e testing.
tadayosi
added a commit
that referenced
this issue
Jun 11, 2021
|
Done with #2392 |
tadayosi
changed the title
orpiske
pushed a commit
to orpiske/camel-k
that referenced
this issue
Jun 11, 2021
…2387 If env variable TEST_ENABLE_NEXUS=true is set, testing hook will look for 'nexus' service in 'nexus' ns and if available it's assigned to camel-k platform as the maven mirror during e2e testing.
orpiske
pushed a commit
to orpiske/camel-k
that referenced
this issue
Jun 11, 2021
orpiske
pushed a commit
that referenced
this issue
Jun 11, 2021
If env variable TEST_ENABLE_NEXUS=true is set, testing hook will look for 'nexus' service in 'nexus' ns and if available it's assigned to camel-k platform as the maven mirror during e2e testing.
orpiske
pushed a commit
that referenced
this issue
Jun 11, 2021
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Each e2e test by design runs in a dedicated namespace with a new Camel K operator installation, which means no kit caches are available and every integration run fires downloading jars from maven central repeatedly. Introducing Nexus mirror for e2e testing would earn some amount of computing time for CI and local e2e runs.
The text was updated successfully, but these errors were encountered: