docs: add pipeline(s) to use for local dev

With e2e test data, we can simply reuse them. I added docs on how to
apply them, but I don't think we need more than that.

Additional changes:
* Fixed both github and gitlab pipeline definition

Closes #1850

Author: yitsushi

README.md

@@ -13,6 +13,19 @@ The pipeline-controller is a Kubernetes controller offering an API (in terms of
    make run
    ```
 
+## Create example pipeline
+
+To make it easier to develop on the controller, you can add example pipline
+resources:
+
+```bash
+# Github
+kubectl apply --recursive -f e2e/testdata/pipelines/github/
+
+# Gitlab
+kubectl apply --recursive -f e2e/testdata/pipelines/gitlab/
+```
+
 ## Contributing
 
 Check out [how to contribute](CONTRIBUTING.md) to the project.

e2e/testdata/pipelines/github/pipeline.yaml

@@ -16,8 +16,9 @@ spec:
       targets:
         - namespace: prod-github
   promotion:
-    pull-request:
-      type: "github"
-      url: "https://github.com/weaveworks/pipeline-controller-e2e"
-      secretRef:
-        name: "github-promotion-credentials"
+    strategy:
+      pull-request:
+        type: "github"
+        url: "https://github.com/weaveworks/pipeline-controller-e2e"
+        secretRef:
+          name: "github-promotion-credentials"

e2e/testdata/pipelines/gitlab/pipeline.yaml

@@ -16,8 +16,9 @@ spec:
       targets:
         - namespace: prod-gitlab
   promotion:
-    pull-request:
-      type: "gitlab"
-      url: "https://gitlab.git.dev.weave.works/pipeline-controller/pipeline-controller-e2e"
-      secretRef:
-        name: "gitlab-ee-promotion-credentials"
+    strategy:
+      pull-request:
+        type: "gitlab"
+        url: "https://gitlab.git.dev.weave.works/pipeline-controller/pipeline-controller-e2e"
+        secretRef:
+          name: "gitlab-ee-promotion-credentials"