action #168379
open
coordination #58184: [saga][epic][use case] full version control awareness within openQA
coordination #152847: [epic] version control awareness within openQA for test distributions
Enable automatic openQA git clone by default size:S
Added by okurz about 1 month ago.
Updated 6 days ago.
Category:
Feature requests
Description
Motivation¶
After #164898 and stabilization on o3 we should make automatic git cloning the default
Acceptance criteria¶
- AC1: Instead of the fetchneedles cronjob test/needle repos are updated via a minion job when tests are started on instances based on default config
Suggestions¶
- Switch the default in the openQA Setup.pm file
- Update the comment in etc/openqa.ini
- Monitor impact on OSD (or have we already enabled it there?) --> That is part of #168376, so this ticket should be worked on after that
- Announce the change? Consider impact on instances that don't set this
- Copied from action #168376: Enable automatic openQA git clone instead of fetchneedles on OSD size:S added
- Project changed from openQA Infrastructure to openQA Project
- Category changed from Feature requests to Feature requests
- Target version changed from Tools - Next to Ready
- Subject changed from Enable automatic openQA git clone by default to Enable automatic openQA git clone by default size:S
- Description updated (diff)
- Status changed from New to Workable
- Description updated (diff)
- Status changed from Workable to Blocked
- Assignee set to mkittler
- Status changed from Blocked to In Progress
- Status changed from In Progress to Feedback
Based on results from #168376 please revert the default for now as well
- Blocked by action #169342: Fix scheduling parallel clusters with `PARALLEL_ONE_HOST_ONLY=1` when the openQA jobs depend on Minion jobs e.g. `git_clone` tasks started for the `git_auto_update` feature size:M added
- Status changed from Feedback to Blocked
- Blocked by action #169510: Improve non-transactional creation of Minion jobs for Git updates when restarting jobs added
This is still blocked by #169510 which is not on the backlog. We can discuss whether we want to enable the auto update feature on OSD despite this flaw (and thus consider this ticket no longer blocked).
Also available in: Atom
PDF