代码之家  ›  专栏  ›  技术社区  ›  Bao Thai

SCA和gradle包装器集成

  •  1
  • Bao Thai  · 技术社区  · 7 年前

    注意到我可以在文档中使用gradle和SCA

    sourceanalyzer -b build gradle clean build
    

    >>>>>>>sourceanalyzer -b buildxyz ./gradlew clean build
    starting init script
    TaskListener registered.
    Configuration on demand is an incubating feature.
    > Task :clean
    
    
    FAILURE: Build failed with an exception.
    
    * Where:
    Initialization script '/Users/.../.fortify/sca17.2/build/buildxyz/init-script4841163810233991317.gradle' line: 203
    
    * What went wrong:
    java.io.IOException: Cannot run program "sourceanalyzer": error=2, No such file or directory
    > Cannot run program "sourceanalyzer": error=2, No such file or directory
    
    * Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
    
    * Get more help at https://help.gradle.org
    
    Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
    See https://docs.gradle.org/4.8.1/userguide/command_line_interface.html#sec:command_line_warnings
    

    即使只使用gradle,我也会得到一个不同的错误。。。

    >>>>>>>sourceanalyzer -b buildxyz gradle clean build
    [warning]: File clean not found
    
    2 回复  |  直到 6 年前
        1
  •  0
  •   Vineeth Sai    6 年前

    我对Fortify&gradle采用三步流程:

    1. 干净的

      sourceanalyzer -b ${SEC_REPORT_NAME} -verbose -clean

    2. sourceanalyzer -b ${SEC_REPORT_NAME} -gradle -verbose gradle -Dorg.gradle.java.home=/opt/jdk8 ${SEC_BUILD_TARGETS}
    3. 扫描

      sourceanalyzer -b ${SEC_REPORT_NAME} -verbose -scan -f ${SEC_TARGET}/${SEC_REPORT_NAME}.fpr

    哪里 ${SEC_REPORT_NAME} 是应用程序报告id-每个步骤都应相同 ${SEC_BUILD_TARGETS} 是gradle的标准构建目标(“干净构建”) ${SEC_TARGET}

        2
  •  0
  •   k0retek    6 年前

    “sourceanalyzer”似乎不在路径中,因为基于以下消息,在系统上找不到它:

    • 出了什么问题: java.io.IOException:无法运行程序“sourceanalyzer”:error=2,没有这样的文件或目录

      无法运行程序“sourceanalyzer”:错误=2,没有这样的文件或目录

    推荐文章