https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • v

    https://youtu.be/TzMCjcVzPcM?t=149▾

    best scene <3
  • v
    :)
  • v
    mhm
  • v
    I cannot set a working directory in a gitlab-ci cofig?
  • v
    bleh, so annoying that beaker-hostgenerator took centos64 as sort of the "default" OS in tests
  • b
    yeah 😞
  • s
    This message was deleted.
    c
    • 2
    • 1
  • b
    @Craig Gumbley https://github.com/puppetlabs/beaker-puppet_install_helper can you migrate to Vox Pupuli?
  • r
    is there a reason for this?
    Copy code
    Because voxpupuli-test >= 4.0.0 depends on rubocop ~> 1.22.3
  and Gemfile depends on rubocop ~> 1.48,
  voxpupuli-test >= 4.0.0 cannot be used.
So, because Gemfile depends on voxpupuli-test ~> 5.6,
  version solving has failed.
  • r
    so why does voxpupuli-test require a specific old rubocop version?
  • b
    because we support Puppet 6 which is ancient and ships ancient Ruby 2.5
  • b
    where do you see the error?
  • b
    I want to update it to a newer ruby/rubocop version when all the beaker gems are released
  • r
    in a company repo for a docker image with puppet tools. i wanted to update the gems
  • r
    in a company repo for a docker image with docker tools. i wanted to update the gems
  • r
    in a company repo for a docker image with puppet tools. i wanted to update the gems
  • b
    in our CI config we usually only install specific groups and that works at the moment, as far as I know
  • r
    okay, then i revert from using voxpupuli-test ftm and setup all gems it depends on on their own...
  • s
    This message was deleted.
    c
    b
    • 3
    • 12
  • b
    @Robert Waffen checkout https://github.com/voxpupuli/gha-puppet/blob/v1/.github/workflows/beaker.yml and watch for BUNDLE_WITHOUT
  • r
    does not help atm (or i dont understand it). i need/want to build a container image with certain tools for the customers gitlab-ci
  • r
    i'm fine. just wanted to ask why there is such an old rubocop
  • v
    ah softwarre... I've a CI pipeline that runs 
    bundle outdated
    , but that sets exit code 1 if gems are outdated
  • v
    and I was wondering why the pipeline doesn't continue
  • v
    ewoud: can I merge https://github.com/voxpupuli/beaker-hostgenerator/pull/275 and then fix rubocop
  • r
    in my Rakefile is it right: when i have 
    require 'voxpupuli/acceptance/rake'
    i don't need 
    require 'beaker/tasks/test'
    ?
  • v
    I think so, yes
  • v
  • v
    ah beaker-puppet has some requirements to beaker 4.x
  • v
    bastelfreak: I just fixed rubocop
1...389390391...648Latest