crappyrules
/
conduit
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Browse Source

CI: Make JUnit export run, even if sytest itself failed

merge-requests/130/head
Jonas Zohren 5 years ago
parent
e7ce642258
commit
3880a200c3
1 changed files with 4 additions and 3 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 7
      .gitlab-ci.yml

7
.gitlab-ci.yml
Unescape View File

@ -55,9 +55,10 @@ test:sytest:
- "mkdir -p /work/server-0/database/ && mkdir -p /work/server-1/database/ && mkdir -p /work/server-2/database/" - "mkdir -p /work/server-0/database/ && mkdir -p /work/server-1/database/ && mkdir -p /work/server-2/database/"
- "cd /" - "cd /"
script: script:
- "/bootstrap.sh conduit" - "SYTEST_EXIT_CODE=0"
after_script: - "/bootstrap.sh conduit || SYTEST_EXIT_CODE=1"
- "perl ./sytest/tap-to-junit-xml.pl --input /logs/results.tap --output /sytest.xml" - "perl /sytest/tap-to-junit-xml.pl --input /logs/results.tap --output /sytest.xml"
- "exit $SYTEST_EXIT_CODE"
artifacts: artifacts:
when: always when: always
paths: paths:

Write Preview
Loading…
Cancel
Save