SLLS-279 populate sonar.java.source analyzer property when possible #412
Parsing Results
There are some issues found during config evaluation and/or parsing!
Details
DEBUG|lib::load_features|{"features": ["aws", "vault", "dockerhub", "only_if", "build_number", "repox"], "kwargs": {"only_if": None}}|{}
INFO |lib::load_features|loading feature 'aws'|{}
INFO |lib::load_features|loading feature 'vault'|{}
INFO |lib::load_features|loading feature 'dockerhub'|{}
INFO |lib::load_features|unloading feature 'only_if'|{}
INFO |lib::load_features|loading feature 'build_number'|{}
INFO |build_number::generate_build_number|metadata store value: '75672'|{"output_environment_variable_name": "CI_BUILD_NUMBER"}
INFO |build_number::generate_build_number|new build_number: '75673'|{"build_number_raw": "75672", "output_environment_variable_name": "CI_BUILD_NUMBER"}
INFO |build_number::generate_build_number|set_metadata return value: '75673'|{"output_environment_variable_name": "CI_BUILD_NUMBER"}
INFO |lib::load_features|loading feature 'repox'|{}
Annotations
Check warning on line 77 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L77
task "qa_linux" depends on task "build", but their only_if conditions are different
Check warning on line 99 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L99
task "qa_windows" depends on task "build", but their only_if conditions are different
Check warning on line 77 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L77
task "qa_linux" depends on task "build", but their only_if conditions are different
Check warning on line 99 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L99
task "qa_windows" depends on task "build", but their only_if conditions are different
Check warning on line 77 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L77
task "qa_linux" depends on task "build", but their only_if conditions are different
Check warning on line 99 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L99
task "qa_windows" depends on task "build", but their only_if conditions are different
Check warning on line 77 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L77
task "qa_linux" depends on task "build", but their only_if conditions are different
Check warning on line 99 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L99
task "qa_windows" depends on task "build", but their only_if conditions are different
Check warning on line 77 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L77
task "qa_linux" depends on task "build", but their only_if conditions are different
Check warning on line 77 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L77
task "qa_linux" depends on task "build", but their only_if conditions are different
Check warning on line 99 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L99
task "qa_windows" depends on task "build", but their only_if conditions are different
Check warning on line 99 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L99
task "qa_windows" depends on task "build", but their only_if conditions are different
Check warning on line 77 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L77
task "qa_linux" depends on task "build", but their only_if conditions are different
Check warning on line 99 in .cirrus.yml
cirrus-ci / Build Parsing Results
.cirrus.yml#L99
task "qa_windows" depends on task "build", but their only_if conditions are different