From 8e3d4cdc90bd10654386c733143a39629b742e7a Mon Sep 17 00:00:00 2001 From: wang yan Date: Tue, 3 Sep 2019 14:46:21 +0800 Subject: [PATCH] add harbor components version and gosec checking in drone ci Signed-off-by: wang yan --- CONTRIBUTING.md | 2 +- docs/installation_guide.md | 14 ++++++++++++++ 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 94a76591a..32073195a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -283,7 +283,7 @@ Once your pull request has been opened, harbor will run two CI pipelines against 1. In the travis CI, your source code will be checked via `golint`, `go vet` and `go race` that makes sure the code is readable, safe and correct. Also all of unit tests will be triggered via `go test` against the pull request. What you need to pay attention to is the travis result and the coverage report. * If any failure in travis, you need to figure out whether it is introduced by your commits. * If the coverage dramatic decline, you need to commit unit test to coverage your code. -2. In the drone CI, the E2E test will be triggered against the pull request. The pipeline is about to build and install harbor from source code, then to run four very basic E2E tests to validate the basic functionalities of harbor, like: +2. In the drone CI, the E2E test will be triggered against the pull request. Also, the source code will be checked via `gosec`, and the result is stored in google storage for later analysis. The pipeline is about to build and install harbor from source code, then to run four very basic E2E tests to validate the basic functionalities of harbor, like: * Registry Basic Verification, to validate the image can be pulled and pushed successful. * Clair Basic Verification, to validate the image can be scanned successful. * Notary Basic Verification, to validate the image can be signed successful. diff --git a/docs/installation_guide.md b/docs/installation_guide.md index 33587d763..6bc190a71 100644 --- a/docs/installation_guide.md +++ b/docs/installation_guide.md @@ -14,6 +14,20 @@ If you run a previous version of Harbor, you may need to update ```harbor.yml``` In addition, the deployment instructions on Kubernetes has been created by the community. Refer to [Harbor on Kubernetes](kubernetes_deployment.md) for details. +## Harbor Components + +|Component|Version| +|---|---| +|Postgresql|9.6.10-1.ph2| +|Redis|4.0.10-1.ph2| +|Clair|2.0.8| +|Beego|1.9.0| +|Chartmuseum|0.9.0| +|Docker/distribution|2.7.1| +|Docker/notary|0.6.1| +|Helm|2.9.1| +|Swagger-ui|3.22.1| + ## Prerequisites for the target host Harbor is deployed as several Docker containers, and, therefore, can be deployed on any Linux distribution that supports Docker. The target host requires Docker, and Docker Compose to be installed.