Skip to content

Emphasize on using the CI tagged image in GitLab example #35

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

Merged
merged 1 commit into from
Jul 4, 2023

Conversation

dnsmichi
Copy link
Contributor

@dnsmichi dnsmichi commented Jul 3, 2023

I did not recognize in my first tests that a specific CI tagged image needs to be used, and went with manually editing my configuration with the default image.

This led to some debugging because launching the container image in CI/CD always executed the script as entrypoint. I first suspected the after_script default config because this also invokes the script.

This PR

  1. Adds a comment that emphasizes on the CI tagged image
  2. Bumps the image tag to the latest 0.7.0-ci tag
  3. Adds a variable for debugging CI/CD jobs (CI_DEBUG_TRACE) which is disabled by default.

Tests and learning steps in https://gitlab.com/gitlab-de/use-cases/observability/devsecops-efficiency/slow-pipeline-for-analysis/-/merge_requests/1

Copy link
Owner

@agardnerIT agardnerIT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@agardnerIT agardnerIT merged commit 5d7c203 into agardnerIT:main Jul 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants