Skip to content
Snippets Groups Projects
  1. Dec 08, 2019
    • Georges Racinet's avatar
      heptapod-ci: adding versions that pass the tests down to 4.3 · 9a29f59e
      Georges Racinet authored
      Currently, hg-git does not pass the tests for
      
      - Mercurial 4.6
      - the head of Mercurial default branch
      
      In order to start benefit of the CI and enforcing that contributions must
      pass it, we will therefore add jobs for these two versions in separate
      topics and Merge Requests.
      
      Also worth of note is that 5.2 can have new point releases that will be
      provided in the base Docker image. Hence we don't exclude it from nightly
      runs.
      9a29f59e
    • Georges Racinet's avatar
      heptapod-ci: tests for one fixed and one moving Mercurial version · 78523621
      Georges Racinet authored
      This Gitlab CI configuration launches the tests of the target hg-git revision
      against:
      
      - the current head of Mercurial `stable` branch
      - a fixed Mercurial version, assumed not to change anymore
      
      We'll add more versions in a follow-up.
      
      ## `image`
      
      All operations after cloning of the tested `hg-git` revision happen in a
      fresh container started on this Docker image.
      
      The ones we use are available on Docker Hub,
      with definitions in https://dev.heptapod.net/octobus/ci-dockerfiles
      
      ## `before_script`
      
      The `before_script` at toplevel will be executed for each job.
      
      In later GitLab versions, we'll also have a `default` toplevel key that will
      allow to specifiy a common value for `script` (and `before_script`, deprecating
      its use at toplevel).
      
      The installations performed by this `before_script` would be better provided
      by a dedicated series of base Docker images, saving resources and execution
      time. If that is done, we are able to remove this `before_script` altogether.
      
      ## `except`
      
      In a first installment, we'll add a nightly scheduler after landing of this
      configuration. We don't want it to relaunch tests against Mercurial versions
      that don't change
      
      ## `script`
      
      This form has the tests launcher build and use the appropriate Mercurial
      revision (information about it displayed first).
      78523621
  2. Nov 20, 2019
  3. Nov 18, 2019
  4. Sep 07, 2019
  5. Aug 07, 2019
  6. Aug 01, 2019
  7. May 19, 2019
  8. May 16, 2019
  9. May 03, 2019
  10. Nov 06, 2018
  11. Mar 18, 2019
  12. Mar 13, 2019
  13. Feb 23, 2019
Loading