From 65ddc2f159470a1906bb8b464b4341a91fa36f81 Mon Sep 17 00:00:00 2001 From: donal <donalspring@gmail.com> Date: Wed, 16 May 2018 15:20:08 +0200 Subject: [PATCH] remove webhook for be --- 2-attack-of-the-pipelines/README.md | 8 -------- 1 files changed, 0 insertions(+), 8 deletions(-) diff --git a/2-attack-of-the-pipelines/README.md b/2-attack-of-the-pipelines/README.md index b263f12..3dfe53b 100644 --- a/2-attack-of-the-pipelines/README.md +++ b/2-attack-of-the-pipelines/README.md @@ -704,14 +704,6 @@ 7. We can now test this properly by heading into the `todolist-fe` repository through <YOUR_FAVOURITE_EDITOR>. Make a small change to your code, then commit and push it, ensuring you're on the develop branch. Then head over to Jenkins and wait until the `dev-todolist-fe-build` job has been triggered. -7. All that's left to do is to repeat the same steps for `todolist-api` (Starting from step 3): -Create Build Trigger: -`https://jenkins-<YOUR_NAME>-ci-cd.apps.some.domain.com/job/dev-todolist-api-build/configure` -Create GitLab Integration: -`https://gitlab-<YOUR_NAME>-ci-cd.apps.some.domain.com/donal/todolist-api/settings/integrations` -Check your build status and you should see something like this. With `Started by Gitlab push by <YOUR_NAME>`: - - 7. We now have a working GitLab webhook so any time we push code it will automatically build! Next up we'll show you how to add tests to your pipeline. _____ -- Gitblit v1.9.3