Dusty Mabe
Dusty Mabe
In https://github.com/coreos/fedora-coreos-pipeline/pull/750 we bumped the memory request because of https://github.com/coreos/fedora-coreos-tracker/issues/1339 but we're not really sure why it was needed. We need to investigate why we were seeing these errors that...
Right now if we want to give someone access to the pipeline we have to add them to the [openshift project](https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/fedora-coreos-pipeline.yml#_10). It would be nice if there was a way...
For our production and development streams the date stamp in the version string for each build reflects the time the yum repo was updated (i.e. a reflection of the freshness...
Let's make sure the jenkins build logs public so they can be shared and we can collaborate on issues.
Since 973bcf9 ("jobs/build: rerun `build-arch` if previous build is incomplete"), there is a race possible where the `build` job rerun logic could kick in before the `release` jobs initially triggered...
We're hitting a subtle issue here where newer x86_64 pipelines are running (and early uploading their builds.json) before the release job runs for the previous build. That release job then...
We'll experiment with this in `rawhide` to see what kind of real world gains we get from using zstd compression. Also see if there are any bugs that crop up....
For at least the `ext.config.extensions.package` test (there may be others): ``` Dec 08 16:50:29 qemu0 kola-runext-package[2091]: ++ jq -r '.deployments[0]["base-commit-meta"]["fedora-coreos.stream"]' Dec 08 16:50:29 qemu0 kola-runext-package[2088]: + rpm-ostree install --apply-live gdb...
The idea here is that we never want someone upgrading to have package downgrades (unless we explicitly decided to do that). In the period of time where `next` is on...
If the requested kernel arguments in the Ignition config already match the kernel arguments of the currently booted system then let's skip the reboot because the reboot won't change anything....