"no published release discovered for X" #432

New Issue

decentral1se · 2023-03-06T14:52:46Z

decentral1se commented

2023-03-06 14:52:46 +00:00

If a new version is released and in the catalogue but abra hasn't updated local tags, it reports that no versions are available. We should be updating tags when doing deploy. Thought this was the case.

If a new version is released and in the catalogue but `abra` hasn't updated local tags, it reports that no versions are available. We should be updating tags when doing deploy. Thought this was the case.

decentral1se added the

bug

label 2023-03-06 14:52:46 +00:00

kawaiipunk commented

2023-03-16 12:34:25 +00:00

I experienced this too.

The error is FATA[0002] no published release discovered for nextcloud

Nextcloud recipe was recently updated.

In order to fix I had to run cd ~/.abra/recipes/nextcloud && git checkout main && git fetch -a to update the recipe.

I experienced this too. The error is `FATA[0002] no published release discovered for nextcloud` Nextcloud recipe was recently updated. In order to fix I had to run `cd ~/.abra/recipes/nextcloud && git checkout main && git fetch -a` to update the recipe.

decentral1se added this to the (deleted) project 2023-05-08 09:45:52 +00:00

decentral1se added the

abra

label 2023-06-08 09:19:24 +00:00

decentral1se changed title from ~~abra reports no versions available when can't match catalogue tag with local git repo tag~~ to "no published release discovered for X"

2023-07-25 13:28:27 +00:00

decentral1se referenced this issue

2023-07-25 13:28:55 +00:00

--force on deploy cannot find published versions #414

decentral1se self-assigned this 2023-07-25 13:29:15 +00:00

decentral1se commented

2023-07-25 13:37:26 +00:00

We are indeed pulling in tags when doing deploy logic 2518e65e3e/pkg/recipe/recipe.go (L634-L644) 🤔

However, I think there is a bug in it, was able to reproduce:

abra app deploy nc.foo.com
FATA[0001] the local copy of nextcloud doesn't seem to have version 5.0.0+27.0.0-fpm available?
cd ~/.abra/recipes/nextcloud
🌻 git fetch -a
From https://git.coopcloud.tech/coop-cloud/nextcloud
 * [new tag]         4.0.7+26.0.2-fpm -> 4.0.7+26.0.2-fpm
 * [new tag]         5.0.0+27.0.0-fpm -> 5.0.0+27.0.0-fpm

git for-each-ref refs/tags reports everything is annotated. I'm gonna try track this down.

(FYI coop-cloud/abra#329 improves the error message)

We are indeed pulling in tags when doing deploy logic https://git.coopcloud.tech/coop-cloud/abra/src/commit/2518e65e3eb3cb85499d07026ea9614810ad9cfc/pkg/recipe/recipe.go#L634-L644 🤔 However, I think there is a bug in it, was able to reproduce: ``` abra app deploy nc.foo.com FATA[0001] the local copy of nextcloud doesn't seem to have version 5.0.0+27.0.0-fpm available? cd ~/.abra/recipes/nextcloud 🌻 git fetch -a From https://git.coopcloud.tech/coop-cloud/nextcloud * [new tag] 4.0.7+26.0.2-fpm -> 4.0.7+26.0.2-fpm * [new tag] 5.0.0+27.0.0-fpm -> 5.0.0+27.0.0-fpm ``` `git for-each-ref refs/tags` reports everything is annotated. I'm gonna try track this down. (FYI https://git.coopcloud.tech/coop-cloud/abra/pulls/329 improves the error message)

decentral1se referenced this issue

2023-07-25 15:00:42 +00:00

Offline support needs more work #471

decentral1se referenced this issue from a commit

2023-07-25 15:03:16 +00:00

revert: always clone latest recipe changes

decentral1se closed this issue

2023-07-25 15:03:16 +00:00

decentral1se added spent time 1 hour 20 minutes

2023-07-25 15:03:31 +00:00

decentral1se referenced this issue from toolshed/abra

2023-07-25 15:03:49 +00:00