https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# extensions
a
This message was deleted.
c
On the build step in your GitHub action are there any errors? I noticed the build step would pass but there would be some type of build error.
r
c
The step will still pass despite a compile error I've noticed
👀 1
r
Sad.
I fix.
c
You can also use 
yarn build-pkg <extension-name>
to test the build locally so you don't have to wait on Github
r
Locally worked well for me.
I had it loaded in local Rancher using dev mode.
I didn't try the 
build-pkg
locally though and load it that way.
Sweet. Updated build/release works! Thank you kindly. One of my favorite things are CI/CD jobs that are green but actually errored. Right up there with HTTP 200 and an error message in the body.
😂 2
😅 1
🚀 1
w
woo!
congrats!
🙌🏼 1
b
Thanks @cuddly-van-73431 for the assist!
@rapid-eye-61308 was it your code or SUSE code that failed but showed green?
r
I mean I pulled it in so it's technically my responsibility now but it's the default GitHub Actions workflows that come with the Rancher UI Extensions npm init stuff.
w
it's a mix. The github actions workflows were provided by the examples, but the workflows themselves weren't failing on errors - and you could blame the javascript bundler
💯 1
i've hit the same thing before
r
My code didn't compile correctly but the action that ran the compilation didn't error on failure either.
b
Noted. @busy-ability-54059 check to see if there's anything we can do about this in the workflow examples. I am an npm neophyte.
❤️ 1
w
@blue-agency-84818 @busy-ability-54059 hoping it's helpful: https://github.com/rancher/dashboard/issues/13648
⭐ 1
4 Views
Open in Slack
PreviousNext
Powered by