-
Notifications
You must be signed in to change notification settings - Fork 329
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
fix(suse): Fix support to install compose from PackageHub on SLES 15 #296
base: master
Are you sure you want to change the base?
Conversation
Thanks, very much @ypid-geberit Two Suse checks are failing.
On SUSE this should be Can you update https://github.com/saltstack-formulas/docker-formula/blob/master/test/integration/archive/controls/archive_spec.rb and can be merged afterwards. |
Thanks looking at this! I am new to Test Kitchen and tried to see how to do this now. I found https://kitchen.ci/docs/getting-started/writing-test/ and https://github.com/ssplatt/filebeat-formula/blob/master/test/integration/helpers/serverspec/spec_helper.rb I am not sure how to best test for the openSUSE version. I found https://docs.chef.io/inspec/resources/os/. Can you give me a hint? |
I can never remember syntax. I looked at prometheus-formula as reference and suggest this example is probably close to what is needed. Hopefully 'suse' is valid.
|
8401b2f
to
56b4080
Compare
My mistake, I see
|
Hi @ypid-geberit
|
Try disabling Suse in .gitlab-ci due to #313 |
To actually install the packages, you need to set the following in your pillar because the PackageHub repos are not enabled by default on SLES. ```YAML docker: pkg: docker: use_upstream: 'package' compose: use_upstream: 'package' ```
c03220a
to
01b6fa2
Compare
01b6fa2
to
0734586
Compare
All right.
I tried that. PS: Note that I switched jobs and archived this account. I might be slow to respond and it might be quicker when you make those changes directly. |
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]
Changes related to the build system[chore]
Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]
Changes to the continuous integration configuration[feat]
A new feature[fix]
A bug fix[perf]
A code change that improves performance[refactor]
A code change that neither fixes a bug nor adds a feature[revert]
A change used to revert a previous commit[style]
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]
Documentation changes[test]
Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE
?No.
Related issues and/or pull requests
Describe the changes you're proposing
Pillar / config required to test the proposed changes
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context
To actually install the packages, you need to set the following in your pillar because the PackageHub repos are not enabled by default on SLES.