Skip to content

Releases: HCL-TECH-SOFTWARE/appscan-issue-gateway

v0.0.11

23 Jan 20:07
Compare
Choose a tag to compare
v0.0.11 Pre-release
Pre-release

Adding extra null check for Issue #10

Fix for windows path in finding location issue

15 Jan 16:30
4bfaa23
Compare
Choose a tag to compare

Fix for this issue didn't make it into the last release's build for whatever reason

Fix for windows path in finding location issue

12 Dec 19:18
b54d102
Compare
Choose a tag to compare
Merge pull request #8 from hclproducts/packaging

update packaging to create zip file and update version number

Fix for ASoC Rest API issue

27 Nov 22:11
465d3cd
Compare
Choose a tag to compare
Pre-release

This release fixes Issue #3 where a change in the Application Security on Cloud REST API was preventing the the appscan issue gateway from pulling issues.

Fix for report generation issue (PolicyID bug)

18 Jul 13:12
Compare
Choose a tag to compare

This release fixes Issue #2 where a change in the Application Security on Cloud REST API was preventing the single-issue report generation from working.

Fix for report generation issue

21 Jun 21:18
Compare
Choose a tag to compare
Pre-release

This release fixes Issue #1 where a change in the Application Security on Cloud REST API was preventing the single-issue report generation from working

New VSTS Provider (thanks to Florin Coada!) and various fixes

30 Apr 07:15
9386f7b
Compare
Choose a tag to compare
0.0.5

Update README.md

Several fixes

29 Mar 18:46
Compare
Choose a tag to compare
Several fixes Pre-release
Pre-release

Changes:

  1. Fix for a NPE when "checkduplicates" not specified in JSON
  2. A better implementation for "severityfield" setting

New configuration options: severityfield and other (debug/demo)

28 Mar 18:56
Compare
Choose a tag to compare
0.0.3

Addition of "other" (debug/demo) and "severityfield" config

Update to fix issue with attached reports sometimes being blank

28 Mar 16:18
Compare
Choose a tag to compare

Changes:

  • Move from PDF to HTML reports. Also include the JIRA issue key in the attached report filename. This helps avoid confusion when developers download many of them.