Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • heptapod heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 195
    • Issues 195
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

In order to prepare the next update of Heptapod based on Gitlab 16.0. The instance will be unavailable on 2023-10-06 between 19:00 and 23:00 UTC+2

  • heptapodheptapod
  • heptapodheptapod
  • Merge requests
  • !29

Provide Mercurial SHA to CI runners

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Georges Racinet requested to merge topic/heptapod/ci_hg_sha into branch/heptapod Sep 24, 2019
  • Overview 1
  • Commits 1
  • Pipelines 0
  • Changes 1

This is the field in the job GitInfo that the non-yet-official Heptapod runner expects to test the proper revision.

As the commit message says, I'd prefer in the absolute something more transparent, so that the runner could be Git and Mercurial capable and ready for the time we won't have also a Git SHA.

But for the time being, this is a tiny change on an API point that's not even called if there's no runner around. It can very well be improved, is probably a bit slow, but we can have it right now (for 0.6.1), and even maybe start using it on the present instance.

This can be considered to solve #69 (closed)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: topic/heptapod/ci_hg_sha