You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Changelog
Combined AIFix and Confidence Score docker containers
Removed Ollama and replaced it with Gemini for Code Generation
Made server IP dynamic and not hard coded
Setup
Download the following files:
zip archive: secai-for-exist-sq if you already have a SonarQube server, secai-for-new-sq if you intend to create a new one
SecAI plugin jar
Unzip the archive on the intended host machine in a location that all administrators can access.
In the file Flaskapp/aifix/.env:
Replace the placeholders for the API keys of the LLMs you intend to use.
Unless you are hosting all components including the projects to analyse on the same machine, change the FLASK_IP to the IP address of the host machine
Run docker compose up -d --build within the unzipped directory. You may have to use sudo for admin permissions.
Configure SonarQube:
For a new SonarQube server: The server configuration in the docker-compose.yml is not meant for production use. Please adjust the configuration to your needs using the official SonarQube documentation
If you are extending an existing SonarQube server: Add the file Flaskapp/aifix/.env through the env-file attribute of your docker compose file or docker run command, or, if not using docker, define the environment variables on your host machine
Add the plugin jar to the plugin folder:
In docker: Use docker container cp to move the file to /opt/sonarqube/extensions/plugins (on the running container). Alternatively, if you used our docker compose file for your server there should be a plugins folder in the base directory that is connected directly to the mentioned location inside the container.
With SonarQube installed from a zip file: Locate the extensions/plugins folder inside your SonarQube distribution and move the jar into it.
Restart the SonarQube instance for the changes to take effect. You should receive a warning about third-party plugins and the plugin should be listed under Administration > Marketplace > Plugins > Installed.
Refer to the documentation on how to set up the analysis using the SecAI plugin.