-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix credentials not passed or configured the CI workflow #286
Commits on Jul 2, 2024
-
Replace the old
setup-git-user
step withgh-action-setup-git
The new actions is also able to set credentials, and we add an example on how to set credentials for projects that have private dependencies. We also move the step to the beginning, in case the submodule dependencies are private. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Configuration menu - View commit details
-
Copy full SHA for 3ff7691 - Browse repository at this point
Copy the full SHA 3ff7691View commit details -
Add a
gh-action-setup-git
step to every job doing a checkoutIf we do a Git checkout, there is the chance that we also need to fetch some private submodule we need credentials for. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com> # ------------------------ >8 ------------------------ # Do not modify or remove the line above. # Everything below it will be ignored. # # Conflicts: # tests_golden/integration/test_cookiecutter_generation/model/frequenz-model-test/.github/workflows/ci.yaml
Configuration menu - View commit details
-
Copy full SHA for 42fd90e - Browse repository at this point
Copy the full SHA 42fd90eView commit details -
Pass git credentials to the
test-installation
jobCredentials were not being passed to the docker build process, and the installation test runs as part of the image builting, so it fails when some `pip` dependency needs git credentials to be fetched. This commit fixes this by passing the `.git-credentials` file generated by the `frequenz-floss/gh-action-setup-git` action to the docker build process. Even when the produced docker image doesn't leave the GitHub runner, this is not ideal because we are storing credentials in the docker image, so eventually this job should be changed so the tests is done in a running container instead of a docker image building process, but for now is a good-enough workaround. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Configuration menu - View commit details
-
Copy full SHA for 5089837 - Browse repository at this point
Copy the full SHA 5089837View commit details -
Improve spacing of the test-installation job
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Configuration menu - View commit details
-
Copy full SHA for 655bb25 - Browse repository at this point
Copy the full SHA 655bb25View commit details -
Add migration steps to the migration script
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Configuration menu - View commit details
-
Copy full SHA for 1907521 - Browse repository at this point
Copy the full SHA 1907521View commit details -
Apply the migration script to this repository
We'll remove the TODOs in the next commit. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Configuration menu - View commit details
-
Copy full SHA for 55922d4 - Browse repository at this point
Copy the full SHA 55922d4View commit details -
Remove the TODOs from the migration
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Configuration menu - View commit details
-
Copy full SHA for bef233c - Browse repository at this point
Copy the full SHA bef233cView commit details -
Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
Configuration menu - View commit details
-
Copy full SHA for 6195bc7 - Browse repository at this point
Copy the full SHA 6195bc7View commit details