As we reevaluate how to best support and maintain Staging Ref in the future, we encourage development teams using this environment to highlight their use cases in the following issue: https://gitlab.com/gitlab-com/gl-infra/software-delivery/framework/software-delivery-framework-issue-tracker/-/issues/36.

Skip to content
Snippets Groups Projects
  1. Sep 09, 2024
  2. Jan 19, 2024
  3. Jul 10, 2023
  4. Jun 20, 2023
  5. Jan 23, 2023
  6. Jul 05, 2022
    • Patrick Steinhardt's avatar
      go: Bump major version to v14 · 822e49b3
      Patrick Steinhardt authored
      While gitlab-shell currently has a major version of v14, the module path
      it exposes is not using that major version like it is required by the Go
      standard. This makes it impossible for dependents to import gitlab-shell
      as a dependency without using a commit as version.
      
      Fix this by changing the module path of gitlab-shell to instead be
      `gitlab.com/gitlab-org/gitlab-shell/v14` and adjust all imports
      accordingly.
      
      Changelog: fixed
      822e49b3
  7. May 19, 2022
  8. Mar 07, 2022
    • Igor Drozdov's avatar
      Reuse Gitaly conns and Sidechannel · e1ddbdd1
      Igor Drozdov authored
      When gitlab-sshd has been introduced we've started running our
      own SSH server. In this case we're able to cache and reuse
      Gitaly connections and Registry.
      
      It helps to reduce memory usage.
      e1ddbdd1
  9. Sep 15, 2021
  10. Aug 04, 2021
    • Nick Thomas's avatar
      Switch to labkit for logging system setup · 1274858f
      Nick Thomas authored
      - We start supporting the "color" format for logs.
      - We now respond to SIGHUP by reopening the log file.
      - We now respect the log format when no log filename is specified.
      
      Output to syslog in the event of logging system setup is preserved in
      OpenSSH mode.
      
      Changelog: added
      1274858f
  11. Jul 27, 2021
  12. Jul 26, 2021
  13. Jul 22, 2021
  14. Jul 19, 2021
  15. Jul 15, 2021
    • Igor Drozdov's avatar
      Shutdown sshd gracefully · 569a0197
      Igor Drozdov authored
      When interruption signal is sent, we are closing ssh listener to
      prevent it from accepting new connections
      
      Then after configured grace period, we cancel the context to
      cancel all ongoing operations
      569a0197
  16. May 17, 2021
    • Nick Thomas's avatar
      Fix opentracing setup for gitlab-sshd · de13980f
      Nick Thomas authored
      Previously, opentracing (if configured) was initialized late in the
      gitlab-shell process's lifespan, coming just before making a gRPC
      call to Gitaly.
      
      By moving the opentracing initialization to be at process startup, we
      make it available for the whole process lifecycle, which is very useful
      to gitlab-sshd, as it means we'll only call tracing.Initialize() once
      on process startup, rather than once per SSH connection.
      
      To get this working, we need to introduce a context to gitlab-sshd.
      This carries the client/service name, but also carries an initial
      correlation ID. The main outcome of this is that all calls to the
      authorized_keys endpoint from a given gitlab-sshd process will now
      share a correlation ID. I don't have a strong opinion about this either
      way.
      
      Changelog: fixed
      de13980f
  17. Apr 30, 2021
  18. Feb 16, 2021
  19. Jan 18, 2021
Loading