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.

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

Adding tmt packit automation #28

Merged
merged 2 commits into from
Dec 14, 2023
Merged

Conversation

Yarboa
Copy link
Collaborator

@Yarboa Yarboa commented Nov 30, 2023

Tests are run by packit through tmt in testsing-farm Adding integration plan and tier-0 test verifying
initoverlayfs setup

resolve #23

@Yarboa Yarboa marked this pull request as draft November 30, 2023 17:20
@ericcurtin
Copy link
Collaborator

This is really neat @Yarboa

@Yarboa Yarboa changed the title Adding tmt tier-0 test Adding tmt packit automation Nov 30, 2023
@dougsland
Copy link
Collaborator

LGTM

@ericcurtin
Copy link
Collaborator

This should work after we merge this I think:

#30

we need PR number 30 anyway for unaccounted devices.

@ericcurtin ericcurtin marked this pull request as ready for review December 1, 2023 21:21
@ericcurtin
Copy link
Collaborator

I think a rebase should fix this @Yarboa

.packit.yaml Outdated Show resolved Hide resolved
.packit.yaml Show resolved Hide resolved
@Yarboa Yarboa force-pushed the add-packit-app branch 2 times, most recently from 4336f0b to df6f9d4 Compare December 4, 2023 13:24
@lsm5
Copy link
Member

lsm5 commented Dec 4, 2023

LGTM as far as packit changes are concerned.

You might wanna also switch to autospec to get rid of the changelog burden in rpm spec (doesn't concern this PR).

@Yarboa Yarboa force-pushed the add-packit-app branch 2 times, most recently from 96ce364 to d22a531 Compare December 7, 2023 13:03
Copy link
Collaborator

@mwperina mwperina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mwperina
Copy link
Collaborator

mwperina commented Dec 7, 2023

/packit test

Copy link

Account mwperina has no write access nor is author of PR!

@Yarboa
Copy link
Collaborator Author

Yarboa commented Dec 7, 2023

LGTM

I suspect there is new issue with F39. checking manually
I will add f38 also, i verified it manually.
I thing it is the latest updates from eric.

Verified manually with 6.5.6-300.fc39.x86_64
public runch is down i think
https://status.testing-farm.io/affected/public-ranch/

I will try to trigger later

@ericcurtin
Copy link
Collaborator

On this @mwperina

"ccount mwperina has no write access nor is author of PR!"

I added you as a member with write access, I think you just have to accept.

@mwperina
Copy link
Collaborator

mwperina commented Dec 8, 2023

/packit test

Copy link

Account mwperina has no write access nor is author of PR!

@mwperina
Copy link
Collaborator

mwperina commented Dec 8, 2023

/packit test

@mwperina
Copy link
Collaborator

mwperina commented Dec 8, 2023

On this @mwperina

"ccount mwperina has no write access nor is author of PR!"

I added you as a member with write access, I think you just have to accept.

I probably missed some email, but I was able to find out the invite in my organizations and it works fine.
Thanks Eric.

@Yarboa
Copy link
Collaborator Author

Yarboa commented Dec 8, 2023

There is an issue with reboot

            00:00:25 /integration/tests/boot-validation [1/1]
            00:00:25 errr /integration/tests/boot-validation (on default-0) (reboot timeout) [1/1]
        fail: Failed to pull workdir from the guest. This usually means that login as 'root' to the guest does not work

I will have to reserve AWS and debug

@Yarboa
Copy link
Collaborator Author

Yarboa commented Dec 11, 2023

Ok i was running it manually on testing farm
https://artifacts.dev.testing-farm.io/a933c23c-ec8d-45b0-9002-cc75814415ae/
It seems to be TF issue, lets wait to this PR to pass all tests

Interesting with packit and generated rpms it is failing
so on AWS 0.98 is failing while 0.96 is passing.

https://pastebin.com/esSjVz9a

@ericcurtin
Copy link
Collaborator

If we rebase this it might just work @Yarboa

@mwperina
Copy link
Collaborator

I just noticed that RPMs are generated as they would be a stable release (initoverlayfs-0.98-1.el9.src.rpm) and not as a snapshot build (initoverlayfs-0.98-0.202312131810.gitefcc221.el9.src.rpm). That should be fixed, if we want to include those RPMs into some snaphot builds repo (for example under centos-automotive-sig group) and make them consumable for other testers

@Yarboa
Copy link
Collaborator Author

Yarboa commented Dec 14, 2023

I just noticed that RPMs are generated as they would be a stable release (initoverlayfs-0.98-1.el9.src.rpm) and not as a snapshot build (initoverlayfs-0.98-0.202312131810.gitefcc221.el9.src.rpm). That should be fixed, if we want to include those RPMs into some snaphot builds repo (for example under centos-automotive-sig group) and make them consumable for other testers

@mwperina thanks
do you refer running to something like this ? build-scripts/version.sh

@mwperina
Copy link
Collaborator

mwperina commented Dec 14, 2023

I just noticed that RPMs are generated as they would be a stable release (initoverlayfs-0.98-1.el9.src.rpm) and not as a snapshot build (initoverlayfs-0.98-0.202312131810.gitefcc221.el9.src.rpm). That should be fixed, if we want to include those RPMs into some snaphot builds repo (for example under centos-automotive-sig group) and make them consumable for other testers

@mwperina thanks do you refer running to something like this ? build-scripts/version.sh

So BlueChi has that support, so if you want to inspire, please take a look at those files:

https://github.com/eclipse-bluechi/bluechi/blob/main/build-scripts/build-rpm.sh
https://github.com/eclipse-bluechi/bluechi/blob/main/build-scripts/build-srpm.sh

Above 2 files are not needed for packit, they are here for previous GH build/test integration and for local command line convenience.

Below files are required for packit integration:
https://github.com/eclipse-bluechi/bluechi/blob/main/build-scripts/create-archive.sh
https://github.com/eclipse-bluechi/bluechi/blob/main/build-scripts/create-spec.sh
https://github.com/eclipse-bluechi/bluechi/blob/main/build-scripts/version.sh
https://github.com/eclipse-bluechi/bluechi/blob/main/.packit.yml#L20

But maybe it can be simplifed for initoverlayfs, which is much smaller project

@Yarboa
Copy link
Collaborator Author

Yarboa commented Dec 14, 2023

I just noticed that RPMs are generated as they would be a stable release (initoverlayfs-0.98-1.el9.src.rpm) and not as a snapshot build (initoverlayfs-0.98-0.202312131810.gitefcc221.el9.src.rpm). That should be fixed, if we want to include those RPMs into some snaphot builds repo (for example under centos-automotive-sig group) and make them consumable for other testers

@mwperina thanks do you refer running to something like this ? build-scripts/version.sh

So BlueChi has that support, so if you want to inspire, please take a look at those files:

https://github.com/eclipse-bluechi/bluechi/blob/main/build-scripts/build-rpm.sh https://github.com/eclipse-bluechi/bluechi/blob/main/build-scripts/build-srpm.sh

Above 2 files are not needed for packit, they are here for previous GH build/test integration and for local command line convenience.

Below files are required for packit integration: https://github.com/eclipse-bluechi/bluechi/blob/main/build-scripts/create-archive.sh https://github.com/eclipse-bluechi/bluechi/blob/main/build-scripts/create-spec.sh https://github.com/eclipse-bluechi/bluechi/blob/main/build-scripts/version.sh https://github.com/eclipse-bluechi/bluechi/blob/main/.packit.yml#L20

But maybe it can be simplifed for initoverlayfs, which is much smaller project

Thanks, much appreciated

Tests are run by packit through tmt in testsing-farm
Adding integration plan and tier-0 test verifying
initoverlayfs setup
Adding packit package builds for tests

Signed-off-by: Yariv Rachmani <[email protected]>
@mwperina
Copy link
Collaborator

Unfortunately it's not enough, you still need to convert spec file to a template and replace version/release in this template per build:
https://github.com/eclipse-bluechi/bluechi/blob/main/build-scripts/create-spec.sh

Copy link
Collaborator

@ericcurtin ericcurtin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, we can do follow on work in the next PR if this is green

@ericcurtin
Copy link
Collaborator

I wish there was a auto-merge if build is green button here like we have in gitlab, it's useful...

@ericcurtin
Copy link
Collaborator

I found it in settings and turned it on, maybe the next PR will have the option

@Yarboa
Copy link
Collaborator Author

Yarboa commented Dec 14, 2023

Unfortunately it's not enough, you still need to convert spec file to a template and replace version/release in this template per build: https://github.com/eclipse-bluechi/bluechi/blob/main/build-scripts/create-spec.sh

Noticed that. yes, lets wait

Now it looks good
'package_version': '0.98-0.202312141231.git4c998f9',

@Yarboa Yarboa merged commit 4495423 into containers:main Dec 14, 2023
5 checks passed
@Yarboa Yarboa mentioned this pull request Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI
5 participants