I want to set up a GitLab CI Pipeline to perform static code analysis on a number of GitLab project repos, each containing several Python scripts. So far the proof of concept that I've set up and run, works perfectly by analysing and generating a score report.........but Pylint analyses Python files in my current GitLab Pipeline working directory.
What I'd however like to do is set up the Pipeline to have the flexibility of allowing me redirect Pylint to analyse Python files that exist in other locations other than my working directory, in other words, one or more external GitLab repositories.
In my existing GitLab pipeline, below is the command that executes the Pylint analysis:
pylint --exit-zero --output-format=text $(find -type f -name "*.py" ! -path "**/.venv/**")
What I'm therefore wondering is whether we could modify it to something like the below:
pylint --exit-zero --output-format=text $(find -type f -name "{External GitLab Project Repo}\*.py" ! -path "**/.venv/**")
Is this possible as illustrated above, or in the .pylintrc configuration file for example?
