4ME code is hosted on Gitlab. We leverage the power of Gitlab-CI to have tests and validation code run after every commit.
This code depends on two things :
.gitlab-ci.ymlfile at the root of the repo
- secret variables defined in the repository configuration
Settings > CI/CD > Secret variables(read more in the Gitlab documentation )
When you fork the 4ME repository, the
.gitlab-ci.yml file follows. However, secret variables do not.
As you can see here,
.gitlab-ci.yml expect 3 variables to be set :
Those are used in
@4me/b2b.client package to access the Network Manager B2B interface. The point is to validate any change in the package against the NM B2B interface.
@4me/b2b.client run actual queries against the NM B2B in CI, it needs to access a valid NM client certificate.
This certificate is passed to the CI context through secret variables, placed in CI environment variables which is then placed in regular files in the ephemeral CI filesystem.
The certificate is then used by various tests.
Forking the 4ME repository would result in pipelines always failing without setting those secret variables
Simple, those tests won't run in CI unless explicitely specified.
Forking should now work flawlessly, at the cost of disabling CI tests for