-
Notifications
You must be signed in to change notification settings - Fork 26
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
(BOLT-1525) Zypper implementation #143
Conversation
|
@donoghuc Can you show me how to set up some SLES boxes for testing when you have some time? |
|
We can also add sles 11,12,15 to https://github.com/puppetlabs/puppetlabs-package/blob/master/metadata.json |
|
@m0dular I will have more time tomorrow to figure out the acceptance test stuff. I think all you have to do is add some sles template names from vmpooler to puppetlabs-package/provision.yaml Line 16 in 592e752
To make sure the tests pass. Also, I would make sure to rebase on master branch and |
4b20ef3
to
435726b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if we haven't done a release since we added files this should be a major version bump.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks ok to me.
|
@puppetlabs/modules I'm having a tough time understanding how this module is tested. When I attempt the following workflow locally: based based on https://github.com/puppetlabs/puppetlabs-package/blob/master/distelli-manifest.yml When I change to (here is an example of a windows failure) I'm not quite understanding why those are pending tests? Are those covered somewhere else (maybe appveyor?) NOW for the really weird part. If I run against a target that has failed with the I noticed this commit 7766e48#diff-34ca0d47d16a704538c4774f2cc60c0d (with no commit message) moving to the For this particular PR we would like to add a SLES target to the acceptance suite. I am not even seeing links to the puppet pipelines checks for recent merges to master. Is there something we can do to verify that adding a sles target to puppetlabs-package/provision.yaml Line 16 in 2b841a5
|
435726b
to
0d31de1
Compare
|
I ran some sles tests and they passed locally. Hopefully this is everything. We should definitely squash these commits before merging. |
|
@m0dular Yeah, please squash the commits and capture everything in commit message. We can do a final check and get this merged. You rock. |
|
@donoghuc Just an update.TP is working on updating the tests to execute them parallelly. (WIP PR is created for this) As a workaround to review the PR we can run them locally with parallel task and re-execute tests on failing nodes. Please let us know if you need help with running the job. |
|
Looks like all of the Windows tasks are failing, but obviously I didn't change anything there. In parallel I got this: I ran the non-Windows ones that failed manually and they were green: |
This commit adds support for the zypper package manager to the Linux package task. Move the helper functions for each manager to its own sourceable script under files/ Tweak the metadata for the Linux task to not use the implementations hash.
8c04eee
to
1f176ec
Compare
|
@m0dular We are working on creating an inventory file outside the test cases.I tried ur changes with the fixes we have. Attaching the screenshot. Windows failures are due to the warning from chocolatey module MODULES-8495 . Everything looks good. |
|
thanks for all your work @m0dular !!! Impressive Great job tracking this @donoghuc @sheenaajay |


No description provided.