organic/.lighthouse/triggers.yaml

apiVersion: config.lighthouse.jenkins-x.io/v1alpha1
kind: TriggerConfig
spec:
  postsubmits:
    - name: rustfmt
      source: "pipeline-rustfmt.yaml"
      # Override https-based url from lighthouse events.
      clone_uri: "git@code.fizz.buzz:talexander/organic.git"
      branches:
        - ^main$
        - ^master$
    - name: rust-test
      source: "pipeline-rust-test.yaml"
      # Override https-based url from lighthouse events.
      clone_uri: "git@code.fizz.buzz:talexander/organic.git"
      skip_branches:
        # We already run on every commit, so running when the semver tags get pushed is causing needless double-processing.
        - "^v[0-9]+\\.[0-9]+\\.[0-9]+$"
    - name: rust-build
      source: "pipeline-rust-build.yaml"
      # Override https-based url from lighthouse events.
      clone_uri: "git@code.fizz.buzz:talexander/organic.git"
      skip_branches:
        # We already run on every commit, so running when the semver tags get pushed is causing needless double-processing.
        - "^v[0-9]+\\.[0-9]+\\.[0-9]+$"
Deploy an initial pipeline to assign semver tags to each commit to master. 2023-07-11 05:26:49 -04:00			`apiVersion: config.lighthouse.jenkins-x.io/v1alpha1`
			`kind: TriggerConfig`
			`spec:`
			`postsubmits:`
Switch to doing in-repo pipelines for lighthouse. Since the needs of each project will be different, this seems like a better solution than relying on configs defined in my kubernetes repo. 2023-07-13 20:30:25 -04:00			`- name: rustfmt`
			`source: "pipeline-rustfmt.yaml"`
Add a CI job to format the rust. 2023-07-11 06:49:08 -04:00			`# Override https-based url from lighthouse events.`
			`clone_uri: "git@code.fizz.buzz:talexander/organic.git"`
			`branches:`
Only run rustfmt on main/master. This way we don't end up trying to push to tags. 2023-07-14 00:27:26 -04:00			`- ^main$`
			`- ^master$`
Switch to doing in-repo pipelines for lighthouse. Since the needs of each project will be different, this seems like a better solution than relying on configs defined in my kubernetes repo. 2023-07-13 20:30:25 -04:00			`- name: rust-test`
			`source: "pipeline-rust-test.yaml"`
Add a CI job to format the rust. 2023-07-11 06:49:08 -04:00			`# Override https-based url from lighthouse events.`
			`clone_uri: "git@code.fizz.buzz:talexander/organic.git"`
Switch to doing in-repo pipelines for lighthouse. Since the needs of each project will be different, this seems like a better solution than relying on configs defined in my kubernetes repo. 2023-07-13 20:30:25 -04:00			`skip_branches:`
			`# We already run on every commit, so running when the semver tags get pushed is causing needless double-processing.`
Build a cargo test image. We need this because the build fails missing crti.o. 2023-07-12 23:14:22 -04:00			`- "^v[0-9]+\\.[0-9]+\\.[0-9]+$"`
Update tekton pipeline to build all the permutations of Organic. This is to catch regressions in feature-gating since I won't be building every possible permutation all the time. 2023-08-10 20:34:56 -04:00			`- name: rust-build`
			`source: "pipeline-rust-build.yaml"`
			`# Override https-based url from lighthouse events.`
			`clone_uri: "git@code.fizz.buzz:talexander/organic.git"`
			`skip_branches:`
			`# We already run on every commit, so running when the semver tags get pushed is causing needless double-processing.`
			`- "^v[0-9]+\\.[0-9]+\\.[0-9]+$"`