action #37447
closed
coordination #34102: [functional][y][epic] improve openqa/scripts
[functional][y][medium] improve openqa/scripts - Replace openqa/scripts by an open source solution (or open source itself)
Added by okurz almost 6 years ago.
Updated over 4 years ago.
Category:
Enhancement to existing tests
Description
Acceptance criteria¶
- AC1: openSUSE contributors that do not have access to any SUSE internal repos have access to all scripts being used to trigger any tests on openqa.opensuse.org
Suggestions¶
- Ask main stakeholders in this repo about their opinion, e.g. lnussel, coolo, qa-tools-team
- Create github project e.g. on os-autoinst/scripts, as replacement for parts of it or all
- Proper license (again, check with contributors)
- Replace previous location with redirect notice
- Ensure all references to old location - if changed - are updated
- Copied from action #35766: [functional][y][medium] improve openqa/scripts - Feasibility: Make openqa/scripts open source if possible, feasible and beneficial added
- Copied from deleted (action #35766: [functional][y][medium] improve openqa/scripts - Feasibility: Make openqa/scripts open source if possible, feasible and beneficial)
- Parent task set to #34102
- Due date set to 2018-12-31
Setting due date to update due date in the parent ticket.
- Priority changed from Low to Normal
- Target version changed from future to Milestone 21
IMHO we have seen with guillaume_g and michel_mno who care about openSUSE aarch64 and ppc64le that we would save time if they could create pull requests to change the openqa/scripts repo content.
- Subject changed from [functional][medium] improve openqa/scripts - Replace openqa/scripts by an open source solution (or open source itself) to [functional][y][medium] improve openqa/scripts - Replace openqa/scripts by an open source solution (or open source itself)
Discussed with coolo.
My proposal is to create a repo within https://github.com/os-autoinst used for "administration" of o3, e.g. just https://github.com/os-autoinst/o3 . The repo should store salt recipes which might include configuration files which are managed by salt. This can also include files from http://gitlab.suse.de/openqa/scripts/ e.g. rsync.pl and rsync_opensuse.pm but not the password and rsync_sle.pm and such. The internal repo should reference the external one e.g. as git submodule then.
coolo mentions the repo is too complicated/embarrasing/complicated for outside contributors to be able to contribute but my assessment is that the internal competence is not much better ;)
I'm not sure if we should invest time in this one instead of improving integration with OBS so we can get rid of it instead. WDYT?
- Description updated (diff)
- Due date deleted (
2018-12-31)
- Target version changed from Milestone 21 to Milestone 22
Shortly discussed in the QSF-y sprint planning and we agreed that the current description is not clear enough to everyone. We could see that AC1 is actually already covered as is of now so we should update that as well.
- Description updated (diff)
Updated acceptance criteria.
With this I suggest to
any objections?
- Status changed from New to Feedback
- Assignee set to okurz
Main issue from riafarov: "by splitting the repo we will help external contributors by making it worse for us"
- Due date set to 2019-01-15
- Blocks coordination #36778: [functional][u][y][epic] improve openqa triggering mechanisms, standardize OBS/IBS deliverables structure, trigger jobs using other means added
- Due date changed from 2019-01-15 to 2019-01-29
Waiting for the feedback from coolo.
- Status changed from Feedback to Workable
- Assignee deleted (
okurz)
- Priority changed from Normal to Low
- Target version changed from Milestone 22 to future
haven't received any feedback. I assume this means silent consensus and we should be able move forward. However, as the team does not see that much value in this we reduce priority.
- Due date deleted (
2019-01-29)
- Due date set to 2020-12-31
setting a later due-date so that the parent ticket is also scheduled until then and does not remind me of over-due tasks.
Andrii Nikitin is actively working on the solution which will allow us having openSUSE part in the github project (potentially as git module, so in general ticket can be rejected.
- Status changed from Workable to Rejected
- Assignee set to riafarov
yep, agreed. However the parts that are not covered by the obs-rsync plugin, e.g. helper scripts, are now already partially living in http://github.com/os-autoinst/scripts/ so that part is covered as well :)
Also available in: Atom
PDF