Hi, Thanks Chris setting the code quality checking on Master branch in Jenkins Pipeline.
When I wanted to check how many vulnerabilities and code smells left after 2-days work, I found that only the master branch can trigger the code quality checking. The checking step is skipped on all other branch in the Jenkins Pipeline. As a result, I had to merge the modified codes into the master branch (though we have not finished all the vulnerabilities) in a rush for code quality checking, and then leaded to a build failure on the Master Branch... I think two long-term alive branches are needed: one is master, which always keeps stable; the other one is dev, which can ingest some in-progress PRs. And, both the two branches need UTs, ITs, Code Quality checking.. I have pushed a new branch called `dev`, can someone add a code quality checking step for it? By the way: After 2-days work, there are only ~1/3 vulnerabilities and code smells left now. Let's take all of them out quickly. :D Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
