![]() As application developers, we are told we should always update libraries to the latest version as they contain bug fixes, security improvements, and increased compatibility with more devices. With a major iOS and Android update happening every year along with new build and development tools being released all the time, mobile developers are constantly making updates to their codebase to support the changing requirements, often resulting in quicker development cycles while reducing the amount of code necessary to accomplish a task.īeyond the official tools and frameworks used to build an application there exists numerous libraries for handling in-app data storage, networking, serialization, threading, or in the case of the Nimbus SDK, rendering ads each with their own release cycles and dependencies that are included in a build. Dsonar.One of the fun challenges about working in mobile development is keeping up with the rapidly evolving landscape. My workaround was to disable SCM explicitly when trigger SonarCloud from workflow, here it is: name: build ![]() I used Travis CI before and it didn’t have this problem. It gives me a warning and it’s annoying for me. This may lead to missing/broken features in SonarCloud Missing blame information for the following files: SCM Publisher 0/3 source files have been analyzed (done) | time=1ms ![]() You can convert to non-shallow with 'git fetch -unshallow'. Shallow clone detected, no blame information will be provided. SCM Publisher 3 source files to be analyzed The problem is, SCM id disabled in my project settings on SonarCloud, but when I push a new change to the Repo, SCM runs and gives me warning, here it is: SCM Publisher SCM provider for this project is: git I use GitHub actions to automate build process for simple Kotlin Repo, and when build and tests are finished, I trigger SonarCloud analysis.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |