Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

zuul, playbooks: CI optimizations #918

Closed
wants to merge 2 commits into from
Closed

zuul, playbooks: CI optimizations #918

wants to merge 2 commits into from

Conversation

HarryMichal
Copy link
Member

This is very much experimental and will most likely not work.

The CI is taking quite long time to run all jobs. This applies mainly to the Rawhide pipeline where some deeper problems with the container stack are (maybe because of btrfs). All the jobs could benefit from caching, though. And we don't need to run all the jobs for all changes (e.g., bash completion or documentation).

@HarryMichal HarryMichal added 3. Enhancement Improvement to an existing feature 5. Help Wanted Extra attention is needed 2. CI Automation of testing, analysis and other actions labels Nov 12, 2021
@softwarefactory-project-zuul
Copy link

Zuul encountered a syntax error while parsing its configuration in the
repo containers/toolbox on branch main. The error was:

unhashable type: 'list'

@softwarefactory-project-zuul
Copy link

Zuul encountered a syntax error while parsing its configuration in the
repo containers/toolbox on branch main. The error was:

while scanning an anchor
in "containers/toolbox/.zuul.yaml@main", line 2, column 21
did not find expected alphabetic or numeric character
in "containers/toolbox/.zuul.yaml@main", line 2, column 40

@softwarefactory-project-zuul
Copy link

Zuul encountered a syntax error while parsing its configuration in the
repo containers/toolbox on branch main. The error was:

unhashable type: 'list'

@softwarefactory-project-zuul
Copy link

Zuul encountered a syntax error while parsing its configuration in the
repo containers/toolbox on branch main. The error was:

Configuration item not recognized. Each zuul.yaml
configuration file must be a list of dictionaries, for
example:

  • job:
    name: foo

  • project:
    name: bar

The dictionary keys must match one of the configuration item
types recognized by zuul (for example, 'job' or 'project').

The incorrect values are around:

irrelevant-files:

  • .github/*
  • completion/*
  • doc/*
    ...

@HarryMichal
zuul: Run tests only for relevant files
2281457 
Not all file are equal when it comes to testing. Documentation, issue
templates or code completion are not worthwhile testing in the CI.
@softwarefactory-project-zuul
Copy link

Zuul encountered a syntax error while parsing its configuration in the
repo containers/toolbox on branch main. The error was:

Invalid Ansible variable name 'build-job' for dictionary value @ data['host-vars']['ci-node-33']

The error appears in the following job stanza:

job:
name: system-test-fedora-33
description: Run Toolbox's system tests in Fedora 33
timeout: 900
irrelevant-files: *excluded_locations
requires: build-f33
nodeset:
nodes:
- name: ci-node-33
label: cloud-fedora-33-small
host-vars:
ci-node-33:
build-job: "build-fedora-33"
pre-run: playbooks/setup-test-env.yaml
run: playbooks/system-test.yaml

in "containers/toolbox/.zuul.yaml@main", line 27, column 3

@softwarefactory-project-zuul
Copy link

Build failed.

@HarryMichal HarryMichal force-pushed the zuul/optimize-test-starting branch 3 times, most recently from 7c66da5 to 4aac2d9 Compare November 22, 2021 01:23
@softwarefactory-project-zuul
Copy link

Zuul encountered a syntax error while parsing its configuration in the
repo containers/toolbox on branch main. The error was:

extra keys not allowed @ data['periodic']['check']

The error appears in the following project stanza:

project:
periodic:
check:
jobs:
- build-fedora-33
- build-fedora-34
- build-fedora-rawhide
gate:
jobs:
- build-fedora-33
- build-fedora-34
- build-fedora-rawhide

in "containers/toolbox/.zuul.yaml@main", line 99, column 3

@softwarefactory-project-zuul
Copy link

Zuul encountered a syntax error while parsing its configuration in the
repo containers/toolbox on branch main. The error was:

extra keys not allowed @ data['periodic']['check']

The error appears in the following project stanza:

project:
name: Toolbx build
periodic:
check:
jobs:
- build-fedora-33
- build-fedora-34
- build-fedora-rawhide
gate:
jobs:
- build-fedora-33
- build-fedora-34
- build-fedora-rawhide

in "containers/toolbox/.zuul.yaml@main", line 99, column 3

@softwarefactory-project-zuul
Copy link

Zuul encountered a syntax error while parsing its configuration in the
repo containers/toolbox on branch main. The error was:

The project "Toolbx build" was not found. All projects referenced
within a Zuul configuration must first be added to the main
configuration file by the Zuul administrator.

The error appears in the following project stanza:

project:
name: Toolbx build
check:
jobs:
- build-fedora-33
- build-fedora-34
- build-fedora-rawhide
gate:
jobs:
- build-fedora-33
- build-fedora-34
- build-fedora-rawhide

in "containers/toolbox/.zuul.yaml@main", line 99, column 3

@HarryMichal HarryMichal force-pushed the zuul/optimize-test-starting branch 6 times, most recently from df4d7e0 to f02b007 Compare November 22, 2021 01:53
@softwarefactory-project-zuul
Copy link

Build failed.

@HarryMichal HarryMichal force-pushed the zuul/optimize-test-starting branch 2 times, most recently from a630ced to 17ef0ca Compare November 22, 2021 02:10
@softwarefactory-project-zuul
Copy link

Build failed.

@softwarefactory-project-zuul
Copy link

Build failed.

@HarryMichal HarryMichal mentioned this pull request Dec 4, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@debarshiray debarshiray Awaiting requested review from debarshiray debarshiray will be requested when the pull request is marked ready for review debarshiray is a code owner

Assignees
No one assigned
Labels
2. CI Automation of testing, analysis and other actions 3. Enhancement Improvement to an existing feature 5. Help Wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@HarryMichal