-
Notifications
You must be signed in to change notification settings - Fork 290
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
Add Windows support for Sensu Go agent #1108
Conversation
Added to travis and appveyor configs limit on what builds. Previously if I pushed to this repo a branch then open a PR there would be two sets of builds. Now PRs, master and tags are what build so if I open a PR there is only going to be one set of builds and not two. |
@ghoneycutt Was contemplating simplifying parameters and just have |
43ab8dc
to
781e806
Compare
I am working on adding acceptance tests for facts on Windows to ensure they work but not having much luck. It works with Vagrant image but having issues getting |
Got commit added that tests |
appveyor.yml
Outdated
matrix: | ||
- PUPPET_GEM_VERSION: '~>5.x' | ||
PUPPET_REPO: puppet5 | ||
PUPPET_VERSION: 5.5.14 |
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.
does this have to be hard coded? we can't just pull the latest minor version?
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.
Puppetlabs doesn't provide a latest
type MSI path so what we have are exact versions: https://downloads.puppetlabs.com/windows/puppet5/. We also can't use one installed via Gem, we are testing real Puppet install that gets installed into system locations like one would do when dealing with real Windows server. That value for PUPPET_VERSION
gets added to MSI download URL, not something coming from rubygems.org.
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.
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.
No idea how I missed that, I updated appveyor configs to use those latest URLs.
Vagrant is failing due to Puppet re-organizing their repo's. |
This is failing vagrant with
|
I used |
Removing
|
Try destroying and then re-running
|
Allow latest fixtures unit tests to fail
Modified windows provisioning for vagrant to use latest windows URL for 5.x of Puppet. |
Success with all the windows versions in vagrant. Waiting on Travis then good to merge. |
Pull Request Checklist
Description
Add Windows support for agent
Related Issue
Fixes #1106
Motivation and Context
Sensu Go 5.7 added better support for Windows, this PR adds that support.