#10 adding quay.io secret in job
Closed by lrossett. Opened by lrossett.
kube-sig/ lrossett/koji-operator zuul-quay  into  main

Download 10.patch

adding quay.io secret in image push job

Zuul encountered a syntax error while parsing its configuration in the
repo kube-sig/koji-operator on branch main. The error was:

The secret "quay-push-bot" was not found.

The error appears in the following job stanza:

job:
name: operator-image-push
description: Build and push the operator image if needed
run: ci/operator-image-push.yaml
secrets:
- name: quay_push_bot
secret: quay-push-bot

in "kube-sig/koji-operator/.zuul.yaml@main", line 6, column 3

You should:
- create a zuul.d directory at the root of the repo.
- mv .zuul.yaml into zuul.d/ci.yaml
- add the generated publish-secret.yaml file into zuul.d/ (and ensure the name defined in publish-secret.yaml is "quay-push-bot"

1 new commit added

  • moving content to zuul.d

Unable to freeze job graph: Pre-review pipeline check does not allow post-review job operator-image-push

Should I move run: ci/operator-test.yaml to run: ../ci/operator-test.yaml (relative path)?

@fbo are you familiar with the above error? I can't say I've run into it and I'm not entirely sure what it wants. :)

The zuul error is happening because the system does not let you use a secret in a check pipeline. You need to move the operator-image-push to the post pipeline. Here is a blog post that explains the details: https://www.softwarefactory-project.io/zuul-hands-on-part-5-job-secrets.html

1 new commit added

  • zuul fix

3 new commits added

  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

3 new commits added

  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Unable to freeze job graph: Pre-review pipeline check does not allow post-review job operator-image-push

this needs to be post

also adds back the check:

check:
jobs:
- operator-test

3 new commits added

  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Zuul encountered a syntax error while parsing its configuration in the
repo kube-sig/koji-operator on branch main. The error was:

Configuration item has more than one key. Each zuul.yaml
configuration file must be a list of dictionaries with a
single key, for example:

  • job:
    name: foo

  • project:
    name: bar

Ensure that every item in the list is a dictionary with only
one key (in this example, 'job' and 'project'). This error
may be caused by insufficient indentation of the keys under
the configuration item ('name' in this example).

The incorrect values are around:

project: null
jobs:
- operator-image-push

3 new commits added

  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Zuul encountered a syntax error while parsing its configuration in the
repo kube-sig/koji-operator on branch main. The error was:

expected a dictionary for dictionary value @ data['jobs']

The error appears in the following project stanza:

project:
jobs:
- operator-image-push

in "kube-sig/koji-operator/zuul.d/project.yaml@main", line 1, column 3

3 new commits added

  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

3 new commits added

  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Zuul encountered a syntax error while parsing its configuration in the
repo kube-sig/koji-operator on branch main. The error was:

expected a list for dictionary value @ data['check']['jobs']

The error appears in the following project stanza:

project:
check:
jobs:
operator-test
release:
jobs:
- operator-image-push

in "kube-sig/koji-operator/zuul.d/project.yaml@main", line 1, column 3

3 new commits added

  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Zuul encountered a syntax error while parsing its configuration in the
repo kube-sig/koji-operator on branch main. The error was:

Job operator-test not defined

The error appears in the following project stanza:

project:
check:
jobs:
- operator-test
release:
jobs:
- operator-image-push

in "kube-sig/koji-operator/zuul.d/project.yaml@main", line 1, column 3

3 new commits added

  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Zuul encountered a syntax error while parsing its configuration in the
repo kube-sig/koji-operator on branch main. The error was:

Job operator-test not defined

The error appears in the following project stanza:

project:
check:
jobs:
- operator-test
release:
jobs:
- operator-image-push

in "kube-sig/koji-operator/zuul.d/project.yaml@main", line 1, column 3

3 new commits added

  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

3 new commits added

  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Zuul encountered a syntax error while parsing its configuration in the
repo kube-sig/koji-operator on branch main. The error was:

Job opetator-test not defined

The error appears in the following project stanza:

project:
check:
jobs:
- opetator-test
post:
jobs:
- operator-image-push

in "kube-sig/koji-operator/zuul.d/project.yaml@main", line 1, column 3

3 new commits added

  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Build succeeded.

1 new commit added

  • adding docker role

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

4 new commits added

  • adding docker role
  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

4 new commits added

  • adding docker role
  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

4 new commits added

  • adding docker role
  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

4 new commits added

  • adding docker role
  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

4 new commits added

  • adding docker role
  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

recheck

4 new commits added

  • adding docker role
  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

4 new commits added

  • adding docker role
  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

4 new commits added

  • adding docker role
  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

4 new commits added

  • adding docker role
  • zuul fix
  • moving content to zuul.d
  • adding quay.io secret in job

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

Pull-Request has been closed by lrossett

Metadata