search

quarkiverse / quarkus-argocd

An ArgoCD extension for Quarkus
https://docs.quarkiverse.io/quarkus-argocd/dev
Apache License 2.0
0 stars 2 forks source link

Creating a new workflow to build and test the plugin #38

Closed cmoulliard closed 1 day ago

cmoulliard commented 2 days ago
iocanel commented 1 day ago

I think that the issue has to do with the fact that you create one project inside an other (and one git repository inside another).

The Quarkus CLI store plugin information in the <project root>/.quarkus/cli/plugins/quarkus-cli-catalog.json. However, the root of the project is detected based on where .git is found.

What I see is that you first add the plugin and then do git init. And all this inside an other git repository. This means that initially the plugin information will be stored at the parent repo root (say workspace repo) and after the git init quarkus will be looking for the plugin in the code-with-quarkus repo.

A simple fix is to move the quarkus plug add command after you do git init.