This repository has been archived by the owner on Jul 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 163
Add Continuous Integration #26
Comments
mlangbehn
added a commit
to mlangbehn/Kubernetes-container-service-GitLab-sample
that referenced
this issue
Aug 23, 2017
Previously, Travis CI installed software (some of which was not needed), and then ran `/bin/true`. Now, the Travis CI configuration has been cleaned up, and runs shellcheck and yamllint. In the process, several .sh and .yml files had to be updated so that they would pass linting. Related-Issue: IBM#26 Signed-off-by: Matt Langbehn <matthew.langbehn@gmail.com>
mlangbehn
added a commit
to mlangbehn/Kubernetes-container-service-GitLab-sample
that referenced
this issue
Aug 23, 2017
Previously, Travis CI installed software (some of which was not needed), and then ran `/bin/true`. Now, the Travis CI configuration has been cleaned up, and runs shellcheck and yamllint. In the process, several .sh and .yml files had to be updated so that they would pass linting. Related-Issue: IBM#26 Signed-off-by: Matt Langbehn <matthew.langbehn@gmail.com>
mlangbehn
added a commit
to mlangbehn/Kubernetes-container-service-GitLab-sample
that referenced
this issue
Aug 28, 2017
Now we run docker-compose and check that port 30080 is listening on every Travis CI run. Related-Issue: IBM#26 Signed-off-by: Matt Langbehn <matthew.langbehn@gmail.com>
#30 would be nice. |
Good725
added a commit
to Good725/rails-gitlab
that referenced
this issue
Feb 22, 2020
Previously, Travis CI installed software (some of which was not needed), and then ran `/bin/true`. Now, the Travis CI configuration has been cleaned up, and runs shellcheck and yamllint. In the process, several .sh and .yml files had to be updated so that they would pass linting. Related-Issue: IBM/Kubernetes-container-service-GitLab-sample#26 Signed-off-by: Matt Langbehn <matthew.langbehn@gmail.com>
Good725
added a commit
to Good725/rails-gitlab
that referenced
this issue
Feb 22, 2020
Now we run docker-compose and check that port 30080 is listening on every Travis CI run. Related-Issue: IBM/Kubernetes-container-service-GitLab-sample#26 Signed-off-by: Matt Langbehn <matthew.langbehn@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue description
Currently, Travis CI installs software, but does not run any tests
Acceptance criteria
Add linters to Travis CI configuration #27Add docker-compose test to Travis CI #29Kubernetes deploy should expose GitLab service #36The text was updated successfully, but these errors were encountered: