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

Skip sync SLE channels in github actions #7658

Merged
merged 1 commit into from
Oct 9, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions testsuite/features/core/srv_create_activationkey.feature
Original file line number Diff line number Diff line change
Expand Up @@ -116,6 +116,7 @@ Feature: Create activation keys
And I click on "Create Activation Key"
Then I should see a "Activation key Build host Key x86_64 has been created" text

@scc_credentials
Scenario: Create an activation key for the terminal
When I follow the left menu "Systems > Activation Keys"
And I follow "Create Key"
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -190,6 +190,7 @@ Feature: Update activation keys
Then I should see a "Activation key Terminal Key x86_64 has been modified" text

@susemanager
@scc_credentials
Scenario: Update terminal key with normal SUSE fake channel
When I follow the left menu "Systems > Activation Keys"
And I follow "Terminal Key x86_64" in the content area
Expand All @@ -199,6 +200,7 @@ Feature: Update activation keys
Then I should see a "Activation key Terminal Key x86_64 has been modified" text

@uyuni
@scc_credentials
Scenario: Update terminal key with specific fake channel
When I follow the left menu "Systems > Activation Keys"
And I follow "Terminal Key x86_64" in the content area
Expand Down
4 changes: 4 additions & 0 deletions testsuite/features/reposync/srv_sync_fake_channels.feature
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,7 @@ Feature: Prepare fake SUSE channels
And solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm"

@uyuni
@scc_credentials
Scenario: Add the terminal child channel to the base product channel
When I follow the left menu "Software > Manage > Channels"
And I follow "Create Channel"
Expand All @@ -62,6 +63,7 @@ Feature: Prepare fake SUSE channels
Then I should see a "Channel Fake-RPM-Terminal-Channel created." text

@uyuni
@scc_credentials
Scenario: Add the repository to the terminal child channel
When I follow the left menu "Software > Manage > Channels"
And I follow "Fake-RPM-Terminal-Channel"
Expand All @@ -74,6 +76,7 @@ Feature: Prepare fake SUSE channels
Then I should see a "Fake-RPM-Terminal-Channel repository information was successfully updated" text

@uyuni
@scc_credentials
Scenario: Synchronize the repository in the terminal channel
When I enable source package syncing
And I follow the left menu "Software > Manage > Channels"
Expand All @@ -87,6 +90,7 @@ Feature: Prepare fake SUSE channels
And I disable source package syncing

@uyuni
@scc_credentials
Scenario: Verify state of Fake-RPM-Terminal-Channel custom channel
Then "orion-dummy-1.1-1.1.x86_64.rpm" package should have been stored
And solver file for "fake-rpm-terminal-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm"