#80 | US1735231 - Added support for encoded tokens | | |
---|
#79 | Use `jenkins.baseline` to reduce bom update mistakes | | |
---|
#77 | Enable Jenkins Security Scan | | |
---|
#76 | Unable to add Fortify CI Token - Unable choose Kind as -' credential of the type Fortify Connection Token.' | | |
---|
#75 | after installed the latest plugin we observe that the plugin is sending connection to ssc even there is no scanning job | | |
---|
JENKINS-71303 | Remove usages of Prototype from Fortify | | |
---|
#63 | Proxy settings in JVM and in Jenkins does not allow the plugin to reach SSC server | | |
---|
#60 | fortifyUpload : : Allow overriding of SSC URL and Authentication Token | | |
---|
#59 | Plugin executes commands in a wrong container in case of k8s pod agent | | |
---|
#51 | Specify Issue Template on FortifyUpload | | |
---|
#45 | Questions around missing functionality | | |
---|
#9 | Question about auto creation of SSC project version while using fortify-plugin | | |
---|
JENKINS-60425 | Fortify plugin in pipeline executes on master (k8s) | | |
---|