-
-
Notifications
You must be signed in to change notification settings - Fork 54
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 Github CI builds and modulesync #104
Conversation
8e7721d
to
3b09d45
Compare
@trevor-vaughan Hi! Any chance you could spare some beaker docker expertise? Our github workflow has a 'gitlab' service started, but the beaker container doesn't seen to have any network connectivity with it. Feel free to push any commits BTW ;) |
I tried to debug this a little bit further. Some things I've learned:
|
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.
Thanks for looking into this! I guess I was trying to be too ambitious by using native GHA.
.msync.yml
Outdated
@@ -1 +1,2 @@ | |||
modulesync_config_version: '3.0.0' | |||
--- | |||
modulesync_config_version: '4.0.0' |
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.
Can we update to 4.1.0? :)
Let's see if I broke it again with my latest change. Feel free to drop that commit if it doesn't. |
@@ -1,66 +1,7 @@ | |||
require 'voxpupuli/acceptance/spec_helper_acceptance' | |||
|
|||
ENV['BEAKER_FACTER_GITLAB_IP'] = File.read(File.expand_path('~/GITLAB_IP')).chomp |
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.
https://github.com/voxpupuli/voxpupuli-acceptance/#environment-variables-to-facts
I also thought about doing it in the workflow file but I think this is better for users who want to run it outside of GHA.
@@ -0,0 +1,48 @@ | |||
# The omnibus installer use the following algorithm to know what to do. |
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.
See https://github.com/voxpupuli/voxpupuli-acceptance/#per-host-configuration for how this file is used.
The docker module fails on EL7 so the tests started to fail on this.
The latest docker module hard fails on this since it's detected as Red Hat < 7.
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.
I rebased it to modulesync 4.1.0 and also squashed some commits. I think this is now ready to merge if it's green.
This uses features from voxpupuli-acceptance to reduce spec_helper_acceptance's size. Another benefit is that editors recognize the .pp extension and you get syntax highlighting.
This module still has support for Puppet 5 which ships Ruby 2.4. This allows it to install there.
We shouldn't forget to create issues that we've dropped Amazon Linux and EL6 for the changelog. |
I think the next release will have a substantial release summary. I'm hoping to get PR together based on https://github.com/syseleven/puppet-gitlab_ci_runner/tree/clean-move-to-concat-deferred At the moment, the config file is only written when registering a runner, and any subsequent config changes you make have no effect. There are also plenty of more exotic configurations you can't make whilst registering. |
For completeness (and mainly because I pinged Trevor and don't want to waste his time!), in #105 I managed to get the docker networking working in the way we originally wanted. Might revisit this at a later date. |
Done via #118 |
This PR is a continuation of #93 (which I accidentally got into a closed state I couldn't reopen).