1. 11 Jan, 2019 2 commits
  2. 04 Jan, 2019 1 commit
  3. 05 Dec, 2018 1 commit
  4. 29 Nov, 2018 1 commit
  5. 20 Nov, 2018 1 commit
    • Molly Waggett's avatar
      (RE-11578) Bump to ezbake 1.8.10 · 66a690b9
      Molly Waggett authored
      This commit bumps to the latest ezbake version. This version adds a Gemfile to
      the resulting package build and makes use of the packaging gem, rather than
      cloning the packaging repo.
      66a690b9
  6. 23 Oct, 2018 3 commits
    • Austin Blatt's avatar
      Bump version to 5.2.7-SNAPSHOT · 5a70d8d3
      Austin Blatt authored
      5a70d8d3
    • Zachary Kent's avatar
      Bump version to 5.2.6 · fa8a5eae
      Zachary Kent authored
      fa8a5eae
    • Rob Browning's avatar
      (PDB-4165) Duplicate dependency pins in :ezbake profile · 6b1f3692
      Rob Browning authored
      It looks like the use of ^:replace :dependencies in the ezbake profile
      causes all pins in the normal :dependencies section to be ignored.  So
      for now, just repeat the pins for the recent CVEs in the :ezbake
      profile, which does cause them to show up here:
      
        lein with-profiles ezbake deps :tree
      
      In addition, stop pinning hikaricp and clojure/jdbc so that we won't
      fall afoul of :pedantic, *and* so that we'll actually be testing the
      versions that we ship (verified by spot-checking the relevant
      META-INF/maven/ pom.xml versions in the 5.1.5 debian/stretch jar).
      6b1f3692
  7. 19 Oct, 2018 2 commits
  8. 18 Oct, 2018 2 commits
  9. 10 Oct, 2018 1 commit
  10. 30 Aug, 2018 2 commits
  11. 28 Aug, 2018 2 commits
    • Molly Waggett's avatar
      (maint) Bump to ezbake 1.8.7 · 61d0a969
      Molly Waggett authored
      This commit bumps to the latest ezbake version. This version adds a Gemfile to
      the resulting package build and makes use of the packaging gem, rather than
      cloning the packaging repo.
      61d0a969
    • Molly Waggett's avatar
      (maint) Bump to ezbake 1.8.7 · e40393c4
      Molly Waggett authored
      This commit bumps to the latest ezbake version. This version adds a Gemfile to
      the resulting package build and makes use of the packaging gem, rather than
      cloning the packaging repo.
      e40393c4
  12. 27 Aug, 2018 1 commit
    • Rob Browning's avatar
      (PDB-3993) Add ./test-config; add pgver/pgbin/pgport opts · e44e9492
      Rob Browning authored
      Move test config handling to ext/bin/test-config, which allows you to
      --set, --get, or --reset (undo any previous --set-ting for the source
      tree) various test config values including the previously existing
      puppet and puppetserver integration test refs, and new pgport, pgver,
      and pgbin settings.
      
      The general idea is that tests can use test-config --get to determine
      what default value to use for these settings, which can be adjusted
      for the local source tree via --set.
      
      By default, try to detect the pgbin directory automatically, based on
      the pgver value, which also allows "test-config --get pgbin" to
      replace the previously travis-specific pgbin-from-spec command.
      
      Always require the pgport to be specified somehow, either via a
      --pgport argument to a given test, or for the whole tree via
      "test-config --set pgport PORT".
      
      Record the tree's default pgver in ext ext/test-conf/pgver-default.
      e44e9492
  13. 16 Aug, 2018 2 commits
  14. 18 Jul, 2018 1 commit
  15. 15 Jul, 2018 1 commit
  16. 13 Jul, 2018 2 commits
  17. 12 Jul, 2018 1 commit
  18. 13 Jun, 2018 3 commits
    • Rob Browning's avatar
      (PDB-3917) Explicitly configure integration test versions · 60ae6cc4
      Rob Browning authored
      Instead of picking up the integration test subject versions from
      PUPPET_VERSION and PUPPETSERVER_VERSION, require them to be explicitly
      configured (and later changed) via ext/bin/config-puppet-test-ref and
      ext/bin/config-puppetserver-test-ref.
      
      Among other things, this makes the contents of ext/test-conf/ the
      single source of truth with respect to the versions.  It also avoids
      having to mangle the project.clj via sed for the integration tests,
      and it makes it much less likely that the project.clj, Gemfile, and
      whatever else might disagree (e.g. if you forgot to specify the
      environment variables identically across command invocations).
      60ae6cc4
    • Rob Browning's avatar
      (PDB-3917) Stop mangling project.clj via sed for integration tests · 9bd489e7
      Rob Browning authored
      Move the install-gems code to src-gems and manage it via an
      install-gems profile so that the puppetserver dependency doesn't
      always have to be known (install_gems.clj refers to puppetserver
      namespaces and so can't be compiled without a puppetserver
      dependency).
      
      Making the puppetserver dependency optional is important because until
      we actually check out the ./puppetserver tree, we don't know what the
      version is, i.e. for 5.3.x it might be 5.3.7-SNAPSHOT.
      
      Have configure-int-tests store the puppetserver test dependency
      version in ext/test-conf/puppetserver-dep, and adjust everything to
      read the version from there when the file exists, or behave reasonably
      when it doesn't.
      
      Previously, not knowing the real depdendency version hasn't been an
      issue because we've set puppetserver-version in the project.clj to
      some fixed version, and then mangled the project.clj via sed to adjust
      it during integration testing.
      9bd489e7
    • Rob Browning's avatar
      a34dfde9
  19. 19 Apr, 2018 2 commits
  20. 12 Apr, 2018 2 commits
  21. 02 Apr, 2018 1 commit
  22. 15 Mar, 2018 1 commit
  23. 08 Mar, 2018 1 commit
  24. 13 Feb, 2018 1 commit
  25. 09 Feb, 2018 1 commit
  26. 26 Jan, 2018 2 commits