You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,7 +91,7 @@ jobs:
91
91
92
92
# Checks out your repository under $GITHUB_WORKSPACE, so that your job can access it.
93
93
- name: Checkout repository
94
-
uses: actions/checkout@v3
94
+
uses: actions/checkout@v4
95
95
96
96
# Generates the jtest.data.json input file.
97
97
- name: Create input for Jtest
@@ -100,7 +100,7 @@ jobs:
100
100
# Runs code analysis with Jtest.
101
101
- name: Run Jtest
102
102
id: jtest
103
-
uses: parasoft/run-jtest-action@2.0.0
103
+
uses: parasoft/run-jtest-action@2.0.2
104
104
with:
105
105
#Uses the jtest.data.json generated with the Gradle command in the previous step
106
106
input: build/jtest/jtest.data.json
@@ -115,7 +115,7 @@ jobs:
115
115
# Uploads an archive that includes all report files (.xml, .html, .sarif).
116
116
- name: Archive reports
117
117
if: always()
118
-
uses: actions/upload-artifact@v3
118
+
uses: actions/upload-artifact@v4
119
119
with:
120
120
name: Static analysis reports
121
121
path: reports/*.*
@@ -156,7 +156,7 @@ jobs:
156
156
157
157
# Checks out your repository under $GITHUB_WORKSPACE, so that your job can access it.
158
158
- name: Checkout repository
159
-
uses: actions/checkout@v3
159
+
uses: actions/checkout@v4
160
160
161
161
# Generates the jtest.data.json input file.
162
162
- name: Create input for Jtest
@@ -165,7 +165,7 @@ jobs:
165
165
# Runs code analysis with Jtest
166
166
- name: Run Jtest
167
167
id: jtest
168
-
uses: parasoft/run-jtest-action@2.0.0
168
+
uses: parasoft/run-jtest-action@2.0.2
169
169
with:
170
170
#Uses the jtest.data.json generated with the Maven command in the previous step
171
171
input: target/jtest/jtest.data.json
@@ -180,7 +180,7 @@ jobs:
180
180
# Uploads an archive that includes all report files (.xml, .html, .sarif).
181
181
- name: Archive reports
182
182
if: always()
183
-
uses: actions/upload-artifact@v3
183
+
uses: actions/upload-artifact@v4
184
184
with:
185
185
name: Static analysis reports
186
186
path: reports/*.*
@@ -200,7 +200,7 @@ If `jtestcli` executable is not on `PATH`, you can configure the path to the ins
200
200
201
201
```yaml
202
202
- name: Run Jtest
203
-
uses: parasoft/run-jtest-action@2.0.0
203
+
uses: parasoft/run-jtest-action@2.0.2
204
204
with:
205
205
installDir: '/opt/parasoft/jtest'
206
206
```
@@ -210,7 +210,7 @@ You can configure the `input` parameter to provide the path to a JSON file that
210
210
211
211
```yaml
212
212
- name: Run Jtest
213
-
uses: parasoft/run-jtest-action@2.0.0
213
+
uses: parasoft/run-jtest-action@2.0.2
214
214
with:
215
215
input: 'build/demo.data.json'
216
216
```
@@ -220,7 +220,7 @@ Code analysis with Jtest is performed by using a test configuration - a set of s
220
220
To specify a test configuration directly in your workflow, add the `testConfig` parameter to the `Run Jtest` action and specify the URL of the test configuration you want to use:
221
221
```yaml
222
222
- name: Run Jtest
223
-
uses: parasoft/run-jtest-action@2.0.0
223
+
uses: parasoft/run-jtest-action@2.0.2
224
224
with:
225
225
testConfig: 'builtin://Recommended Rules'
226
226
```
@@ -229,7 +229,7 @@ To specify a test configuration directly in your workflow, add the `testConfig`
229
229
Generating reports in the SARIF format is available in Jtest since version 2021.1. If you are using an earlier Jtest version, you need to customize the `Run Jtest` action to enable generating SARIF reports:
0 commit comments