If there are gitlab users here that would be interested in using the private Maven repositories provided by gitlab, then please check out this patch and provide feedback. https://clojure.atlassian.net/browse/TDEPS-140

Gitlab uses a token in a http header for authentication instead of the normal username/password method, this patch adds support for that.

is it possible to resolve a pom type dep (rather than a jar) in my deps.edn file?

I think in lein, one could specify :type "pom" and it would resolve the pom alone without requiring a jar at the end...

oh.. nevermind - I just found the :extension "pom" attribute - did the trick perfectly!

Hi I am playing with Github actions and tools.deps, seems there is an issue with installing deps from private github repositories Did anyone also experienced it? Do I need to install my ssh key?

Yes, you would need to do that

k, thanks

I believe there is a special env var for it automatically in the action

But you’d need to add it to the ssh-agent

I haven’t done this yet myself so don’t have a recipe for you

thanks, will try to install ssh key and add it to agent

adding ssh key didnt help much

name: CI

on: [push]

jobs:
  build:

    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v1
    - name: Install Clojure
      run: curl -O  && chmod +x linux-install-1.10.1.469.sh && sudo ./linux-install-1.10.1.469.sh
    - name: Setup ssh
      env:
        KEY: ${{ secrets.KEY }}
      run: mkdir -p ~/.ssh && echo "$KEY" > ~/.ssh/id_rsa && chmod 600 ~/.ssh/id_rsa && eval $(ssh-agent -s) && ssh-add -k ~/.ssh/id_rsa && ssh-keygen -F  || ssh-keyscan  >>~/.ssh/known_hosts
    - name: Run tests
      run: ./bin/run-tests-ci.sh

Error building classpath. connector is not available: 
com.jcraft.jsch.agentproxy.AgentProxyException: connector is not available: 
	at com.jcraft.jsch.agentproxy.ConnectorFactory.createConnector(ConnectorFactory.java:120)

please advice what can be wrong?

@kirill.salykin in Github Actions, do processes persist between steps?

You can find out by running - run: ssh-add -l in a subsequent step

I have github actions building private git deps, but I'm doing it all within a container

i am able to clone that repo via just git

but tools.deps isn't using git

yeah, just to ensure that I can clone it

My guess is eval $(ssh-agent -s) dies at the end of that step? @kirill.salykin

oh just saw the thread

you should probably pin the http://github.com host key statically in source code

otherwise it will accept any known host key -- MITM attack

true, thanks