No components found with Jenkins
See original GitHub issueHi, Anthony
In my company project, when I run yarn build
to build it in Local or Server, no problem.
But when I use CI / CD with Jenkins, It throw the log “[unplugin-vue-components] no components found”.
Although it doesn’t affect the building process, but these global components cannot be rendered.
I can’t found how to fix it, this is my config, can you help me?
// vite.config.ts
import components from 'unplugin-vue-components/vite'
// ...
export default defineConfig({
// ...
plugins: [
// ...
components({
dirs: [
'src/components',
'src/components/Admin',
'src/components/Admin/GroupPanel',
],
extensions: ['vue', 'ts'],
deep: false,
dts: false,
}),
// ...
],
})
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Uncaught Error: No component defined for type "jenkins.jobs" #3
Added extention using npm i mozaik-ext-jenkins --save and module if physically installed. In app.js, added mozaik.bus.registerApi('jenkins' ...
Read more >How to set component while creating new issue - Jenkins Jira
Hi Team,. Is there any way to add component while creating new issue using JIRA jenkins pipeline groovy script? We had tried to...
Read more >Ticket creation fails when no components in JIRA project exist ...
We've got another Jenkins job setup with the "Update relevant JIRA issues" option and this works correctly. But just can't get the 'Create...
Read more >[JENKINS-70250] Stapler Not Found - Jenkins Jira
Type: Bug. Status: Closed (View Workflow). Priority: Major. Resolution: Not A Defect. Component/s: pipeline. Labels: pipeline · stapler. Environment:.
Read more >Failure to load flow node: FlowNode was not found in storage ...
If these messages are not present, it means that Jenkins was unable to save the Pipeline, so the error is expected. If that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After a few days of investigation, the cause was finally located! The problem is caused by the mismatch between the Jenkins workspace and the real path of the file.
At that time, the DevOps engineer in charge of Jenkins had left, and the conversation with him could not be queried. I remember that the workspace was originally named using Chinese brackets, such as
project_name(测试服)
, he thought that the workspace name was just a reading identification, but it actually seemed to affect the path reading of the file during packaging,which was later changed toproject_name_dev
, it works fine. Hope it can help you! @Rokixy