pipeline for testing changes

containers / initoverlayfs

GNU General Public License v2.0

35 stars 9 forks source link

pipeline for testing changes #5

Closed dougsland closed 6 months ago

dougsland commented 8 months ago

This is not trivial software for testing as it would require a full boot process but let's create a minimal CI/CD pipeline to run before merges.

dougsland commented 8 months ago

Some ideas:

tools to validate the code
sync2jira (generate a jira as soon the project has a new issue)
if possible generate initramfs images before and after the change and compare sizes

@ericcurtin feel free to add more tests.

ericcurtin commented 8 months ago

These are good ideas.

We should also do a podman container with krun runtime that tests this end to end. The reason you want a hypervisor is this messes around with low-level details within an OS and you probably want that isolated in a VM as well as a container, otherwise you could mount and unmount partitions in your base os.

Yarboa commented 8 months ago

@dougsland I would suggest packit infrastructure, with tmt basic scenario over c9s. Should it be on different issues?

One more thing here, packit rpm build, Shall I open a ticket for that also?

dougsland commented 8 months ago

@dougsland I would suggest packit infrastructure, with tmt basic scenario over c9s. Should it be on different issues?

One more thing here, packit rpm build, Shall I open a ticket for that also?

Hey @Yarboa, glad to see you around here too. Lets open an exclusive ticket for tmt infrastructure as it's used downstream/upstream in others auto projects.

Yarboa commented 6 months ago

Closing this https://github.com/containers/initoverlayfs/pull/28 already test the minimum scenario and reboot