apollo/pominal
apollo/pominal
1
0
Fork 0
Code Issues Pull requests Projects Releases Activity
pominal/.gitlab-ci.yml

54 lines
844 B
YAML
Raw Normal View History

ci: set up CI/CD
2019-06-30 01:25:36 +01:00
---
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
stages:
- test
- deploy
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
variables:
CGO_ENABLED: 0
ci: set up CI/CD
2019-06-30 01:25:36 +01:00
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
test:junit:
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
artifacts:
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
expire_in: 1 hour
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
reports:
junit:
report.xml
before_script:
- apk add --no-cache make
- go get -u github.com/jstemmer/go-junit-report
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
except:
- master
image: golang:1.13.6-alpine
script:
- make test_junit_report
stage: test
test:unit:
artifacts:
expire_in: 30 minutes
paths:
- code-coverage.html
before_script:
- apk add --no-cache make
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
image: golang:1.13.6-alpine
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
only:
- master@dananglin/pominal
ci: set up CI/CD
2019-06-30 01:25:36 +01:00
script:
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
- make test_cover_report
stage: test
ci: set up CI/CD
2019-06-30 01:25:36 +01:00
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
pages:
artifacts:
paths:
- public
expire_in: 30 days
dependencies:
- test:unit
only:
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
- master@dananglin/pominal
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
script:
- mkdir public
- mv code-coverage.html public
stage: deploy
variables:
GIT_STRATEGY: none
Reference in a new issue Copy permalink