Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
I Have Noticed That For Some People The Repository Discovery Stores Github Repo In The Form:

I have noticed that for some people the repository discovery stores github repo in the form: https://github.com/ ... while for others git@github.com:...
Interestingly in the former case the ssh config is ignored and cloning repository breaks on the worker (it does not know which ssh key to use apparently), while in the latter case everything works smoothly. Did you see this before?

  
  
Posted 2 years ago
Votes Newest

Answers 5


ok, I solved the problem,
agent.force_git_ssh_protocol = truedid the trick

  
  
Posted 2 years ago

just put ssh config with the proper key marked

  
  
Posted 2 years ago

I did not configure user/pass for git

  
  
Posted 2 years ago

Hi UpsetTurkey67

repository discovery stores github repo in the form:

...

while for others

git@github.com:...

Yes that depends on how they locally cloned the repo (via SSH or user/pass/token)

Interestingly in the former case the ssh config is ignored and cloning repository breaks on the worker

If you have passed git user/pass to the agent it should use them not SSH, how did you configure the agent ?

  
  
Posted 2 years ago

Exactly! nice 🎉

  
  
Posted 2 years ago
981 Views
5 Answers
2 years ago
one year ago
Tags