Commit graph

6 commits

Author SHA1 Message Date
e4df5bfb8e
ci: run junit report from branches
JUnit reports are useful for merge requests
so it is generate only from commits to branches
other than master.

This solves the issue where the code coverage was missing
from the badge and no testing logs are shown in the console
output.

Also fixed (hopefully) is the deployment of the coverage
report to my GitLab pages site.
2020-01-18 01:48:27 +00:00
5fd24b80df
test: improve testing suite and added reporting
* replace the table driven test with sub tests.
* create and publish code coverage reports via GitLab pages.
* use JUnit to view test results in the test tab in the pipeline view.
* upgrade Go to version 1.13.6.
2020-01-18 01:04:51 +00:00
0a86afbec3
chore: updated Go to version 1.13.4
As part of the Go update the flag.Parse()
function was moved out of init() and into
main() as the test was failing.
2019-12-01 20:30:20 +00:00
1ccf3b6302
chore: bump go to v1.12.9 2019-09-15 22:52:45 +01:00
0cd7dab556
ci: added release (semi)automation
- security: updated Golang version to 1.12.8 for CI builds
- added: configuration for build and release automation using GoReleaser
(https://goreleaser.com)
- (Releases will be semi-automatic for now due to the need of the access
token. When/if project specific access token is supported then I'll
complete the release stage of the pipeline.)
- added: version.go for printing out the versions
2019-08-14 01:10:28 +01:00
705566e74f
ci: set up CI/CD 2019-06-30 01:25:36 +01:00