So, I was trying to Manually Publishing the Extension using Helm Charts, when I add a repository from my personal github account, it lists the extension in the available section. But whenever I'm trying to add a repository from my organization, it doesn't show on the available list. note: both are public repos

can you shares both repos+branches?

https://github.com/SayedTahsin/kbd (worked for this one) https://github.com/appscode-cloud/rancher-ui-extension consider master branches.

which Rancher version are you using? in a

2.13-head

version I can see the extension coming from your organisation repo I can’t install any of those extensions (coming from any of those repos) which might suggest something is wrong with the generated assets of the publishing process

Using v2.11.3 Yes. I have made a different branch for Helm charts. Though there is not hard requirement for manual publishing, we wanted to do that, as it seems easy and straightforward.

yarn publish-pkgs -s "appscode-cloud/rancher-ui-extension" -b "charts"

This is the command I used to generate assets and charts. Then, I add a repository with that `charts`branch. Is anything wrong with my approach? note: It doesn't shows any error in this process.

please try the automatic approach @breezy-airplane-74201. That should fix any build problems. In the workflow, make sure to change the target branch where you want to publish the helm chart to https://github.com/rancher/elemental-ui/blob/main/.github/workflows/build-extension-charts.yml#L22

I have tried the automate approch. 1. created an gh-pages branches. 2. select

GitHub Actions

from pages 3. released with desired tag name Still the actions doesn't run. Is there anything I'm missing? https://github.com/SayedTahsin/rancher-ui-extension

It doesn’t run because you’ve changed the address for the reusable workflow here: https://github.com/SayedTahsin/rancher-ui-extension/blob/master/.github/workflows/build-extension-charts.yml#L15 it needs to be https://github.com/rancher/elemental-ui/blob/main/.github/workflows/build-extension-charts.yml#L15

We were actually trying some changes to fix things; in that process, we changed it. I reverted the change and set uses as it was. Still no actions are running. Do we have to align the master and gh-pages branches?

I dont’ see the update on https://github.com/SayedTahsin/rancher-ui-extension/blob/master/.github/workflows/build-extension-charts.yml#L15 also, make sure the release is targeting the

master

branch, which is where your pkg code exists (we want to build from that source)

updated master and set a release. please check now

I’ll have to assume that you’ve met every steps of https://extensions.rancher.io/extensions/next/publishing#release-prerequisites because I don’t have access to the settings of your repo, but if you failed any step here it doesn’t work. One thing that you did not do is: https://extensions.rancher.io/extensions/next/publishing#helm-chart-automated-approach Warning

WARNING: When using the provided Github workflows, the base skeleton application name (Found in the root level package.json) MUST be unique when compared with any extension packages found in ./pkg/*. If an extension package name matches the base skeleton name the workflow will fail due to the "Parse Extension Name" step found in the "Build and Release Extension Charts" workflow.

But that should not prevent the run of the workflow…. It should throw an error. I recommend renaming https://github.com/SayedTahsin/rancher-ui-extension/blob/master/package.json#L2 so it doesn’t match https://github.com/SayedTahsin/rancher-ui-extension/blob/master/pkg/kubedb/package.json#L2. The tag must match https://github.com/SayedTahsin/rancher-ui-extension/blob/master/pkg/kubedb/package.json#L2 which you seem to do Another thing is that I believe all of our repositories have a

main

and not a

master

branch…. Looking at the reusable workflow that your workflow calls https://github.com/rancher/dashboard/blob/master/.github/workflows/build-extension-charts.yml, I was expecting that

build-extension-artifact

job to run… You’ll probably run into problems in

release

job because of https://github.com/rancher/dashboard/blob/master/.github/workflows/build-extension-charts.yml#L116 When you re-triggered the release, did you delete the tag before doing the release again?

Thanks for clearing up these things. Now I made a fresh fork out of our original repo. And followed everything mentioned in the doc. Still no action is running. 1. made application name distinct from pkg name 2. used main as the default branch. 3. created gh-pages and selected GitHub Actions for build & deployment 4. Create a tag from the main branch with proper naming. 5. Set Release from that tag Is there anything I'm missing? link of my repo: https://github.com/SayedTahsin/rancher-ui-extension

Based on all your comments I had to test this from scratch, so I created a new repo on my org, added an extension and everything and try to publish it using the workflow and it worked from me (which kinda validates why no-one else complained). https://github.com/aalves08/test-ext-publish-flow This points to the fact that somewhere on the setup you must be doing something wrong, imho. Believing that the repo is setup properly, my theory is that on the actual tagging of the release there must be something wrong. Did you

tag

it correctly? is it targeting the

main

branch? Is it the

latest

release? (not pre-release) (check screenshot). I recommend you to retrace all your steps in search for something where you had doubts and kind of decided for a given path that may not be right. This will also highlight where in the documentation lies some flaws. I will create an issue to fix that part of the docs. Let me know your findings 🙏

@busy-ability-54059 Thanks a lot for your support. The issue I was facing while publishing the extension is fixed now. It looks like there was some issues on my package.json and yarn.lock of extension folder.