From 4eed6437808e23551016c38cba02c8b1e712b779 Mon Sep 17 00:00:00 2001 From: Sebastian Schuberth Date: Fri, 16 Oct 2020 17:44:57 +0200 Subject: [PATCH] README: Fix links to the Jenkinsfile This is a fixup for d1f23d8. Signed-off-by: Sebastian Schuberth --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 3b122e2a89524..c73f4afa900bb 100644 --- a/README.md +++ b/README.md @@ -147,9 +147,9 @@ or ## Running on CI A basic ORT pipeline (using the _analyzer_, _scanner_ and _reporter_) can easily be run on -[Jenkins CI](https://jenkins.io/) by using the [Jenkinsfile](./Jenkinsfile) in a (declarative) -[pipeline](https://jenkins.io/doc/book/pipeline/) job. Please see the [Jenkinsfile](./Jenkinsfile) itself for -documentation of the required Jenkins plugins. The job accepts various parameters that are translated to ORT command +[Jenkins CI](https://jenkins.io/) by using the [Jenkinsfile](./integrations/Jenkinsfile) in a (declarative) +[pipeline](https://jenkins.io/doc/book/pipeline/) job. Please see the [Jenkinsfile](./integrations/Jenkinsfile) itself +for documentation of the required Jenkins plugins. The job accepts various parameters that are translated to ORT command line arguments. Additionally, one can trigger a downstream job which e.g. further processes scan results. Note that it is the downstream job's responsibility to copy any artifacts it needs from the upstream job.