Flavors
To improve run performances, we generate Flavored MegaLinter images containing only the list of linters related to a project type
- When using default MegaLinter, if a MegaLinter Flavor would cover all your project requirements, a message is added in the logs
- If your project uses a MegaLinter Flavor not covering linter requirements, an error message will be thrown with instructions about how to solve the issue
The following table does not display docker pulls from MegaLinter v4 images.
Flavor | Description | Embedded linters | Info | |
---|---|---|---|---|
all | Default MegaLinter Flavor | 97 | ||
ci_light | Optimized for CI items (Dockerfile, Jenkinsfile, JSON/YAML schemas,XML | 16 | ||
dart | Optimized for DART based projects | 42 | ||
documentation | MegaLinter for documentation projects | 41 | ||
dotnet | Optimized for C, C++, C# or VB based projects | 49 | ||
go | Optimized for GO based projects | 43 | ||
java | Optimized for JAVA based projects | 43 | ||
javascript | Optimized for JAVASCRIPT or TYPESCRIPT based projects | 50 | ||
php | Optimized for PHP based projects | 46 | ||
python | Optimized for PYTHON based projects | 49 | ||
ruby | Optimized for RUBY based projects | 42 | ||
rust | Optimized for RUST based projects | 42 | ||
salesforce | Optimized for Salesforce based projects | 44 | ||
scala | Optimized for SCALA based projects | 42 | ||
swift | Optimized for SWIFT based projects | 42 | ||
terraform | Optimized for TERRAFORM based projects | 47 |
If you need a new flavor, post an issue