Popular New Releases in Jenkin
dokku
v0.27.0
jenkins
2.332.3 RC
onedev
7.0.6
spug
v3.1.1（2022/04/20)
metersphere
v1.20.0-rc2
Popular Libraries in Jenkin
by dokku 
shell
22648 MIT
A docker-powered PaaS that helps you build and manage the lifecycle of applications
by bregman-arie python
22045 NOASSERTION
Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP, DNS, Elastic, Network, Virtualization. DevOps Interview Questions
by jenkinsci java
18753 MIT
Jenkins automation server
by meolu python
11031 Apache-2.0
walle - 瓦力 Devops开源项目代码部署平台
by openshift go
8070 Apache-2.0
Conformance test suite for OpenShift
by theonedev java
7325 MIT
Self-hosted Git Server with Kanban and CI/CD
by openspug javascript
7266 AGPL-3.0
开源运维平台：面向中小型企业设计的轻量级无Agent的自动化运维平台，整合了主机管理、主机批量执行、主机在线终端、文件在线上传下载、应用发布部署、在线任务计划、配置中心、监控、报警等一系列功能。
by metersphere java
7173 GPL-3.0
MeterSphere 是一站式开源持续测试平台，覆盖测试管理、接口测试、性能测试等。搞测试，就选 MeterSphere！
by chef ruby
6865 Apache-2.0
Chef Infra, a powerful automation platform that transforms infrastructure into code automating how infrastructure is configured, deployed and managed across any environment, at any scale
Trending New libraries in Jenkin
by metersphere java
7173 GPL-3.0
MeterSphere 是一站式开源持续测试平台，覆盖测试管理、接口测试、性能测试等。搞测试，就选 MeterSphere！
by phodal typescript
1606 MPL-2.0
Ledge —— DevOps knowledge learning platform. DevOps、研发效能知识和工具平台，是我们基于在 ThoughtWorks 进行的一系列 DevOps 实践、敏捷实践、软件开发与测试、精益实践提炼出来的知识体系。它包含了各种最佳实践、操作手册、原则与模式、度量、工具，用于帮助您的企业在数字化时代更好地前进，还有 DevOps 转型。
by ben1234560 shell
881 MIT
如何基于K8s(Kubernetes)部署成PaaS/DevOps(一套完整的软件研发和部署平台)--教程/学习(实战代码/欢迎讨论/大量注释/操作配图)，你将习得部署如：K8S(Kubernetes)、dashboard、Harbor、Jenkins、本地gitlab、Apollo框架、promtheus、grafana、spinnaker等。
by hashicorp go
668 MPL-2.0
Terraform Language Server
by srillia shell
502 GPL-3.0
let devops for docker, dockerswarm ,k8s easy
by mdubourg001 javascript
501
🦊 Test your Gitlab CI Pipelines changes locally using Docker.
by firecow typescript
429 MIT
Tired of pushing to test your .gitlab-ci.yml?
by in28minutes java
402
Devops Tutorial for Beginners - Learn Docker, Kubernetes, Terraform, Ansible, Jenkins and Azure Devops
by metersphere javascript
320 GPL-3.0
MeterSphere 录制浏览器请求的插件，记录浏览器中的网络请求并导出为 Jmeter 或 Json 格式的文件
Top Authors in Jenkin
1
325 Libraries
49653
2
16 Libraries
1003
3
15 Libraries
828
4
14 Libraries
747
5
13 Libraries
4273
6
13 Libraries
220
7
10 Libraries
144
8
10 Libraries
861
9
9 Libraries
8707
10
8 Libraries
121
1
325 Libraries
49653
2
16 Libraries
1003
3
15 Libraries
828
4
14 Libraries
747
5
13 Libraries
4273
6
13 Libraries
220
7
10 Libraries
144
8
10 Libraries
861
9
9 Libraries
8707
10
8 Libraries
121
Trending Kits in Jenkin
No Trending Kits are available at this moment for Jenkin
Trending Discussions on Jenkin
Jenkins - getting "No type prefix:" when assigning roles
Jenkins Ambiguous Permission
C# WASM without Blazor
Jenkins with Kubernetes Client Plugin - NoSuchMethodError
Jenkins log4j vulnerability testing from pipeline job
Unable to install Jenkins on Ubuntu 20.04
Pylint integration with Jenkins build running on dynamic kubernetes pods as agents
On Debian 11 (Bullseye) /proc/self/cgroup inside a docker container does not show docker infos
When should you use single curly braces vs double curly braces for variable reference in github actions?
Vaadin production mode builds broken in v20?
QUESTION
Jenkins - getting "No type prefix:" when assigning roles
Asked 2022-Feb-25 at 10:29I am trying to assign roles to users in Jenkins using the 'role based strategy' plugin. When I do that, I am getting a red text that says "No type prefix:" in front of every user that I am assigning a role to. Please advise how this can be removed.:
I am very new to Jenkins so any suggestions will be very helpful.
Regards Ramesh
ANSWER
Answered 2022-Feb-16 at 22:58use "USER:" for user and "GROUP:" for group .. eg "USER:ABC" ..this changed with the recent plug in update ..
QUESTION
Jenkins Ambiguous Permission
Asked 2022-Feb-01 at 14:15After updating Jenkins, it is sending a warning for ambiguous permission for project base permission. I can migrate the entry to user or group manually, was wondering if there's an automate or batch way to do so?
Warning Messages
Some permission assignments are ambiguous. It is recommended to update affected configurations to be unambiguous. See this overview page for a list of affected configurations.
This table contains rows with ambiguous entries. This means that they apply to both users and groups of the specified name. If the current security realm does not distinguish between user names and group names unambiguously, and if users can either choose their own user name or create new groups, this configuration may allow them to obtain greater permissions. It is recommended that all ambiguous entries are replaced with ones that are either explicitly a user or group.
ANSWER
Answered 2021-Dec-29 at 23:41I have deleted old entries and added them again, warning disappeared.
QUESTION
C# WASM without Blazor
Asked 2022-Jan-30 at 14:27I want to be able to call C# code from JavaScript. The mono project used to have a WASM SDK that you could download from their old Jenkins server, but that is no longer public. Existing docs tend to point toward those builds. The Azure Devops builds do not include this SDK. A few messages I've seen on their Github account indicate that they are now focusing on the .NET 6 for WASM. I do not wish to use the Blazor components. Is there a way in .NET 6 to build a minimally sized WASM binary without the Blazor UI?
ANSWER
Answered 2021-Aug-26 at 01:25Yes it's absolutely possible. Blazor does not have a monopoly on C#/WASM and it's far from clear that it's going to wind up being the best long term option (and a lot of evidence it's not).
I recommend starting with the Uno WASM Bootstrap. https://github.com/unoplatform/Uno.Wasm.Bootstrap
QUESTION
Jenkins with Kubernetes Client Plugin - NoSuchMethodError
Asked 2022-Jan-08 at 09:06After upgrading the jenkins plugin Kubernetes Client to version 1.30.3 (also for 1.31.1) I get the following exceptions in the logs of jenkins when I start a build:
1Timer task org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider$UpdateConnectionCount@2c16d367 failed
2java.lang.NoSuchMethodError: 'okhttp3.OkHttpClient io.fabric8.kubernetes.client.HttpClientAware.getHttpClient()'
3 at org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider$UpdateConnectionCount.doRun(KubernetesClientProvider.java:150)
4 at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:90)
5 at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:67)
6 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
7 at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
8 at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
9 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
10 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
11 at java.base/java.lang.Thread.run(Thread.java:829)
12After some of these eceptions the build itself is cancelled with this error:
1Timer task org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider$UpdateConnectionCount@2c16d367 failed
2java.lang.NoSuchMethodError: 'okhttp3.OkHttpClient io.fabric8.kubernetes.client.HttpClientAware.getHttpClient()'
3 at org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider$UpdateConnectionCount.doRun(KubernetesClientProvider.java:150)
4 at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:90)
5 at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:67)
6 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
7 at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
8 at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
9 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
10 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
11 at java.base/java.lang.Thread.run(Thread.java:829)
12java.io.IOException: Timed out waiting for websocket connection. You should increase the value of system property org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator.websocketConnectionTimeout currently set at 30 seconds
13at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:451)
14at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:338)
15at hudson.Launcher$ProcStarter.start(Launcher.java:507)
16at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:176)
17at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:132)
18at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:324)
19at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:319)
20Do you have an idea what can be done?
ANSWER
Answered 2022-Jan-05 at 11:55Downgrade the plugin to kubernetes-client-api:5.10.1-171.vaa0774fb8c20. The latest one has the compatibility issue as of now.
new info: The issue is now solved with upgrading the Kubernetes plugin to version: 1.31.2 https://issues.jenkins.io/browse/JENKINS-67483
QUESTION
Jenkins log4j vulnerability testing from pipeline job
Asked 2021-Dec-27 at 20:39I am trying to make sure my Jenkins instance is not exploitable with the latest log4j exploit.
I have a pipeline script that runs, I tried following this instruction :
https://community.jenkins.io/t/apache-log4j-2-vulnerability-cve-2021-44228/990
This is one of my stages of my pipeline script:
1stage('Building image aaa') {
2 steps{
3 script {
4 sh "echo executing"
5 org.apache.logging.log4j.core.lookup.JndiLookup.class.protectionDomain.codeSource
6 sh "docker build --build-arg SCRIPT_ENVIRONMENT=staging -t $IMAGE_REPO_NAME:$IMAGE_TAG ."
7 }
8 }
9 }
10But I get a different error than what's described here and I'm unsure if I'm checking this correctly. This is the error:
1stage('Building image aaa') {
2 steps{
3 script {
4 sh "echo executing"
5 org.apache.logging.log4j.core.lookup.JndiLookup.class.protectionDomain.codeSource
6 sh "docker build --build-arg SCRIPT_ENVIRONMENT=staging -t $IMAGE_REPO_NAME:$IMAGE_TAG ."
7 }
8 }
9 }
10groovy.lang.MissingPropertyException: No such property: org for class: groovy.lang.Binding
11 at groovy.lang.Binding.getVariable(Binding.java:63)
12 at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:271)
13 at org.kohsuke.groovy.sandbox.impl.Checker$7.call(Checker.java:353)
14 at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:357)
15 at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:333)
16 at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:333)
17 at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:333)
18 at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:29)
19 at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)
20 at WorkflowScript.run(WorkflowScript:31)
21 at ___cps.transform___(Native Method)
22 at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74)
23 at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
24....etc
25ANSWER
Answered 2021-Dec-27 at 20:39I don't think a class name would be directly interpreted as a groovy codeSource argument in a declarative pipeline (as opposed to a scripted one)
Try the approach of "How to import a file of classes in a Jenkins Pipeline?", with:
1stage('Building image aaa') {
2 steps{
3 script {
4 sh "echo executing"
5 org.apache.logging.log4j.core.lookup.JndiLookup.class.protectionDomain.codeSource
6 sh "docker build --build-arg SCRIPT_ENVIRONMENT=staging -t $IMAGE_REPO_NAME:$IMAGE_TAG ."
7 }
8 }
9 }
10groovy.lang.MissingPropertyException: No such property: org for class: groovy.lang.Binding
11 at groovy.lang.Binding.getVariable(Binding.java:63)
12 at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:271)
13 at org.kohsuke.groovy.sandbox.impl.Checker$7.call(Checker.java:353)
14 at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:357)
15 at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:333)
16 at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:333)
17 at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:333)
18 at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:29)
19 at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)
20 at WorkflowScript.run(WorkflowScript:31)
21 at ___cps.transform___(Native Method)
22 at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74)
23 at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
24....etc
25node{
26 def cl = load 'Classes.groovy'
27 def a = cl.getProperty("org.apache.logging.log4j.core.lookup.JndiLookup").protectionDomain.codeSource
28 ...
29}
30Note that getCLassLoader() is by default disallowed, and should require from an Jenkins administrator In-process Script Approval.
QUESTION
Unable to install Jenkins on Ubuntu 20.04
Asked 2021-Dec-08 at 05:56I am trying to install Jenkins on my Ubuntu EC2 instance and I performed the following steps to install but couldn't install it.
$sudo apt update $sudo apt install openjdk-8-jdk $wget -q -O - https://pkg.jenkins.io/debian-stable/jenkins.io.key | sudo apt-key add - $sudo sh -c 'echo deb http://pkg.jenkins.io/debian-stable binary/ > /etc/apt/sources.list.d/jenkins.list' $sudo apt update <--------- (Here I am getting below error)
root@ip-172-31-44-187:~# sudo apt update Ign:1 https://pkg.jenkins.io/debian-stable binary/ InRelease Err:2 https://pkg.jenkins.io/debian-stable binary/ Release Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 151.101.154.133 443] Hit:3 http://ap-south-1.ec2.archive.ubuntu.com/ubuntu focal InRelease Get:4 http://ap-south-1.ec2.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Get:5 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB] Get:6 http://ap-south-1.ec2.archive.ubuntu.com/ubuntu focal-backports InRelease [101 kB] Reading package lists... Done E: The repository 'http://pkg.jenkins.io/debian-stable binary/ Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.
ANSWER
Answered 2021-Oct-09 at 07:17Yeah , I had same problem with this from yesterday , I think this is after yesterday's new update in jenkins 2.303.2 Lts .
Just do , apt upgrade , apt update, apt get install jenkins -y .
It worked for me .
QUESTION
Pylint integration with Jenkins build running on dynamic kubernetes pods as agents
Asked 2021-Nov-01 at 23:32We have a Jenkins setup on Google Kubernetes Engine with dynamic kubernetes pods serving as build agents. I want to integrate Pylint as a build step. Python version running on kubernetes pod is 2.7.16. Any idea how to install Pylint and integrate it into Jenkins build?
Edit:
Jenkins is running on a Google Kubernetes Engine cluster.
Kubernetes Cloud is configured in Jenkins as given below:
List of plugins installed are as follows:
1Analysis Model API Plugin
2Ant Plugin
3Apache HttpComponents Client 4.x API Plugin
4Bundles Apache HttpComponents Client 4.x and allows it to be used by Jenkins plugins.
5Authentication Tokens API Plugin
6Bootstrap 4 API Plugin
7Bootstrap 5 API Plugin
8bouncycastle API Plugin
9Branch API Plugin
10Caffeine API Plugin
11Checks API plugin
12Command Agent Launcher Plugin
13Credentials Binding Plugin
14Credentials Plugin
15DataTables.net API Plugin
16Display URL API
17Docker API Plugin
18Docker Commons Plugin
19Docker Pipeline
20Docker plugin
21Durable Task Plugin
22ECharts API Plugin
23Provides ECharts for Jenkins plugins.
24Folders Plugin
25Font Awesome API Plugin
26Forensics API Plugin
27Git
28Git client plugin
29GIT server Plugin
30GitHub API Plugin
31GitHub plugin
32Google Authenticated Source plugin
33Google Cloud Storage plugin
34Google Compute Engine Plugin
35Google Kubernetes Engine Plugin
36Google Metadata plugin
37Google OAuth Credentials plugin
38Jackson 2 API Plugin
39JavaScript GUI Lib: ACE Editor bundle plugin
40JavaScript GUI Lib: Handlebars bundle plugin
41JavaScript GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin
42JavaScript GUI Lib: Moment.js bundle plugin
43JQuery3 API Plugin
44JSch dependency plugin
45JUnit Plugin
46Kubernetes Client API Plugin
47Kubernetes Credentials Plugin
48Kubernetes plugin
49LDAP Plugin
50Lockable Resources plugin
51Mailer Plugin
52Matrix Project Plugin
53Metrics Plugin
54Monitoring
55OAuth Credentials plugin
56OkHttp
57Oracle Java SE Development Kit Installer Plugin
58OWASP Markup Formatter Plugin
59Pipeline
60Pipeline Graph Analysis Plugin
61Pipeline: API
62Pipeline: Basic Steps
63Pipeline: Build Step
64Pipeline: Declarative
65Pipeline: Declarative Extension Points API
66Pipeline: Groovy
67Pipeline: Input Step
68Pipeline: Job
69Pipeline: Milestone Step
70Pipeline: Model API
71Pipeline: Multibranch
72Pipeline: Nodes and Processes
73Pipeline: REST API Plugin
74Pipeline: SCM Step
75Pipeline: Shared Groovy Libraries
76Pipeline: Stage Step
77Pipeline: Stage Tags Metadata
78Pipeline: Stage View Plugin
79Pipeline: Step API
80Pipeline: Supporting APIs
81Plain Credentials Plugin
82Plugin Utilities API Plugin
83Popper.js 2 API Plugin
84Popper.js API Plugin
85SCM API Plugin
86Script Security Plugin
87Snakeyaml API Plugin
88SSH Agent Plugin
89SSH Build Agents plugin
90SSH Credentials Plugin
91SSH plugin
92SSH server
93Structs Plugin
94Token Macro Plugin
95Trilead API Plugin
96Variant Plugin
97Warnings Next Generation Plugin
98Jankins version is Jenkins 2.303.2, and all plugins are up-to-date to latest version.
ANSWER
Answered 2021-Nov-01 at 23:32I think you probably can achieve the desired behavior by adding a convenient container to your pod template: this container will include the necessary Pylint dependencies and will be used in addition to the default Jenkins agent image in your pod.
As you can see in your screenshot, you can add this container when configuring your pod template and Kubernetes in the Jenkins Web console.
In addition, you can provide the necessary information when defining your pipeline. Consider for instance the example provided in the Jenkins Kubernetes plugin documentation:
1Analysis Model API Plugin
2Ant Plugin
3Apache HttpComponents Client 4.x API Plugin
4Bundles Apache HttpComponents Client 4.x and allows it to be used by Jenkins plugins.
5Authentication Tokens API Plugin
6Bootstrap 4 API Plugin
7Bootstrap 5 API Plugin
8bouncycastle API Plugin
9Branch API Plugin
10Caffeine API Plugin
11Checks API plugin
12Command Agent Launcher Plugin
13Credentials Binding Plugin
14Credentials Plugin
15DataTables.net API Plugin
16Display URL API
17Docker API Plugin
18Docker Commons Plugin
19Docker Pipeline
20Docker plugin
21Durable Task Plugin
22ECharts API Plugin
23Provides ECharts for Jenkins plugins.
24Folders Plugin
25Font Awesome API Plugin
26Forensics API Plugin
27Git
28Git client plugin
29GIT server Plugin
30GitHub API Plugin
31GitHub plugin
32Google Authenticated Source plugin
33Google Cloud Storage plugin
34Google Compute Engine Plugin
35Google Kubernetes Engine Plugin
36Google Metadata plugin
37Google OAuth Credentials plugin
38Jackson 2 API Plugin
39JavaScript GUI Lib: ACE Editor bundle plugin
40JavaScript GUI Lib: Handlebars bundle plugin
41JavaScript GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin
42JavaScript GUI Lib: Moment.js bundle plugin
43JQuery3 API Plugin
44JSch dependency plugin
45JUnit Plugin
46Kubernetes Client API Plugin
47Kubernetes Credentials Plugin
48Kubernetes plugin
49LDAP Plugin
50Lockable Resources plugin
51Mailer Plugin
52Matrix Project Plugin
53Metrics Plugin
54Monitoring
55OAuth Credentials plugin
56OkHttp
57Oracle Java SE Development Kit Installer Plugin
58OWASP Markup Formatter Plugin
59Pipeline
60Pipeline Graph Analysis Plugin
61Pipeline: API
62Pipeline: Basic Steps
63Pipeline: Build Step
64Pipeline: Declarative
65Pipeline: Declarative Extension Points API
66Pipeline: Groovy
67Pipeline: Input Step
68Pipeline: Job
69Pipeline: Milestone Step
70Pipeline: Model API
71Pipeline: Multibranch
72Pipeline: Nodes and Processes
73Pipeline: REST API Plugin
74Pipeline: SCM Step
75Pipeline: Shared Groovy Libraries
76Pipeline: Stage Step
77Pipeline: Stage Tags Metadata
78Pipeline: Stage View Plugin
79Pipeline: Step API
80Pipeline: Supporting APIs
81Plain Credentials Plugin
82Plugin Utilities API Plugin
83Popper.js 2 API Plugin
84Popper.js API Plugin
85SCM API Plugin
86Script Security Plugin
87Snakeyaml API Plugin
88SSH Agent Plugin
89SSH Build Agents plugin
90SSH Credentials Plugin
91SSH plugin
92SSH server
93Structs Plugin
94Token Macro Plugin
95Trilead API Plugin
96Variant Plugin
97Warnings Next Generation Plugin
98podTemplate(containers: [
99 containerTemplate(name: 'maven', image: 'maven:3.8.1-jdk-8', command: 'sleep', args: '99d'),
100 containerTemplate(name: 'golang', image: 'golang:1.16.5', command: 'sleep', args: '99d')
101 ]) {
102
103 node(POD_LABEL) {
104 stage('Get a Maven project') {
105 git 'https://github.com/jenkinsci/kubernetes-plugin.git'
106 container('maven') {
107 stage('Build a Maven project') {
108 sh 'mvn -B -ntp clean install'
109 }
110 }
111 }
112
113 stage('Get a Golang project') {
114 git url: 'https://github.com/hashicorp/terraform.git', branch: 'main'
115 container('golang') {
116 stage('Build a Go project') {
117 sh '''
118 mkdir -p /go/src/github.com/hashicorp
119 ln -s `pwd` /go/src/github.com/hashicorp/terraform
120 cd /go/src/github.com/hashicorp/terraform && make
121 '''
122 }
123 }
124 }
125
126 }
127}
128Please, note the definition of the required containers and how everyone of them is used in the pipeline.
You can review additional examples in the plugin Github repository.
This Jenkins blog post, is plenty of information about how to use these custom containers as well.
For your Pylint container template you can provide your own image although there are different ones already available in Docker hub, for instance.
I am not an expert in the use of Pylint, but I came across these related resources:
- Declarative Jenkins pipeline syntax for pylint or flake8
- Jenkins pipeline - skip next stage on conditional failure of pylint
- Use PyLint on Jenkins with Warnings Plugin and Pipeline
- Is there any Jenkins plugin for pylint results?
- Jenkins and Python
- Jenkins Python template
I hope some of them will be of help in your pipeline definition.
QUESTION
On Debian 11 (Bullseye) /proc/self/cgroup inside a docker container does not show docker infos
Asked 2021-Aug-31 at 22:01I recently updated from Debian 10 (Buster) to 11 (Bullseye) and since then my Jenkins setup inside Docker is not working anymore, as Jenkins tries to find out if it is running in a docker container by checking /proc/self/cgroup.
Normally /proc/self/cgroup inside a docker container would look something like this:
112:rdma:/
211:perf_event:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
310:freezer:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
49:memory:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
58:cpuset:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
67:devices:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
76:net_cls,net_prio:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
85:hugetlb:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
94:pids:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
103:cpu,cpuacct:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
112:blkio:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
121:name=systemd:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
130::/system.slice/containerd.service
14but since I updated to Debian 11 it looks pretty small:
112:rdma:/
211:perf_event:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
310:freezer:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
49:memory:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
58:cpuset:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
67:devices:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
76:net_cls,net_prio:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
85:hugetlb:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
94:pids:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
103:cpu,cpuacct:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
112:blkio:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
121:name=systemd:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
130::/system.slice/containerd.service
140::/
15As Jenkins is not recognizing anymore that it is running inside a docker container itself, it starts other build containers with the wrong arguments.
QuestionThe simple question would be: Is this a bug?
But the real question might be what am I doing wrong? I cannot find anyone else with this problem, so it might be a misconfiguration or anything similar.
I reinstalled Docker, removed any configuration and I even tried downgrading Docker to 20.10.6 as this is the last version I know was working under Debian 10, but none of that changed anything.
I don't have a clue on how to approach this problem any further. It already took me a full day to find out that the problem was not Jenkins itself (nearly got crazy reading Jenkins logs). I am hitting bedrock right now, so any help and any input is really appreciated!
Jenkins stuff
For those interested in the Jenkins part, here Jenkins checks if it is running inside a container: https://github.com/jenkinsci/docker-workflow-plugin/blob/b174d46226ef1095903f2e789355a3b216b46dda/src/main/java/org/jenkinsci/plugins/docker/workflow/client/DockerClient.java#L347
Jenkins thinking it is not running inside a container will log something like this:
112:rdma:/
211:perf_event:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
310:freezer:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
49:memory:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
58:cpuset:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
67:devices:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
76:net_cls,net_prio:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
85:hugetlb:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
94:pids:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
103:cpu,cpuacct:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
112:blkio:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
121:name=systemd:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
130::/system.slice/containerd.service
140::/
15Jenkins does not seem to be running inside a container
16$ docker run -t -d -u 0:0
17-w /var/jenkins_home/workspace/myrepo_master
18-v /var/jenkins_home/workspace/myrepo_master:/var/jenkins_home/workspace/myrepo_master:rw,z
19-v /var/jenkins_home/workspace/myrepo_master@tmp:/var/jenkins_home/workspace/myrepo_master@tmp:rw,z
20-e ******** ... my-awesome-build-container cat
21And thus mounting /var/jenkins_home from the host system, where Jenkins has no access to from inside its container.
While the log output on Debian 10 (and Ubuntu 20.04) looks something like this:
112:rdma:/
211:perf_event:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
310:freezer:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
49:memory:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
58:cpuset:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
67:devices:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
76:net_cls,net_prio:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
85:hugetlb:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
94:pids:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
103:cpu,cpuacct:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
112:blkio:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
121:name=systemd:/docker/a2ffe0e97ac22657a2a023ad628e9df837c38a03b1ebc904d3f6d644eb1a1a81
130::/system.slice/containerd.service
140::/
15Jenkins does not seem to be running inside a container
16$ docker run -t -d -u 0:0
17-w /var/jenkins_home/workspace/myrepo_master
18-v /var/jenkins_home/workspace/myrepo_master:/var/jenkins_home/workspace/myrepo_master:rw,z
19-v /var/jenkins_home/workspace/myrepo_master@tmp:/var/jenkins_home/workspace/myrepo_master@tmp:rw,z
20-e ******** ... my-awesome-build-container cat
21Jenkins seems to be running inside container 7814083762a1bed51dec2f468c6ee07c978a0b6377e347c3ed7dc23393feac11
22$ docker run -t -d -u 0:0
23-w /var/jenkins_home/workspace/myrepo_master
24--volumes-from 7814083762a1bed51dec2f468c6ee07c978a0b6377e347c3ed7dc23393feac11
25-e ******** ... my-awesome-build-container cat
26and starting the build container with the correct volume using --volumes-from.
ANSWER
Answered 2021-Aug-31 at 22:01The change in behavior is due to that debian uses cgroups v2 starting with Debian 11/Bullseye. The docker engine itself supports cgroups v2 since v20.10.x.
This means, as soon as you have a distribution that uses cgroups v2 and a recent version of the Docker engine, you cannot get the container id with your method.
I've opened a similar question to find an alternative method: How to get docker container ID from within the container with cgroup v2
The only way I know to get the id is by using the docker api, but that is not an elegant solution if you just want to know if the process runs inside a container. (And may pose a security risk if you expose the docker socket inside the container)
For now as a workaround you could manually signal the process that it is run inside a container environment, e.g. by specifying an environment variable on container creation.
QUESTION
When should you use single curly braces vs double curly braces for variable reference in github actions?
Asked 2021-Aug-31 at 20:05I'm starting to learn github actions (converting from jenkins piplines). I am not super familiar with yaml.
I cannot figure out when or why variables should be referenced using double curly braces vs single curly braces. I have a feeling there is an important distinction here.... Can you clue me in?
1name: sample
2on:
3 workflow_dispatch
4env:
5 MY_VAR: "something"
6
7jobs:
8 do_things:
9 runs-on: ubuntu-latest
10 steps:
11 - name: "Step 1"
12 run: echo "${MY_VAR}"
13 - name: "Step 2"
14 run: echo "${{env.MY_VAR}}"
15
16
ANSWER
Answered 2021-Aug-31 at 20:05This line:
1name: sample
2on:
3 workflow_dispatch
4env:
5 MY_VAR: "something"
6
7jobs:
8 do_things:
9 runs-on: ubuntu-latest
10 steps:
11 - name: "Step 1"
12 run: echo "${MY_VAR}"
13 - name: "Step 2"
14 run: echo "${{env.MY_VAR}}"
15
16run: echo "${MY_VAR}"
17is literally running a bash script that says:
1name: sample
2on:
3 workflow_dispatch
4env:
5 MY_VAR: "something"
6
7jobs:
8 do_things:
9 runs-on: ubuntu-latest
10 steps:
11 - name: "Step 1"
12 run: echo "${MY_VAR}"
13 - name: "Step 2"
14 run: echo "${{env.MY_VAR}}"
15
16run: echo "${MY_VAR}"
17echo "${MY_VAR}"
18so in this case, ${MY_VAR} is expanded according to bash's rules; in this case it will just print the environment variable MY_VAR, but you can do all sorts of crazy things with bash's parameter expansion.
On the other hand, this line:
1name: sample
2on:
3 workflow_dispatch
4env:
5 MY_VAR: "something"
6
7jobs:
8 do_things:
9 runs-on: ubuntu-latest
10 steps:
11 - name: "Step 1"
12 run: echo "${MY_VAR}"
13 - name: "Step 2"
14 run: echo "${{env.MY_VAR}}"
15
16run: echo "${MY_VAR}"
17echo "${MY_VAR}"
18run: echo "${{env.MY_VAR}}"
19is expression syntax for GitHub Actions and will be expanded by the GitHub Actions runner. In this case, the variable MY_VAR that is in your environment context will be replaced in the shell script.
The literal shell script that will executed will have the environment variable value in it. So if MY_VAR=foo, then the literal bash script that will be run is:
1name: sample
2on:
3 workflow_dispatch
4env:
5 MY_VAR: "something"
6
7jobs:
8 do_things:
9 runs-on: ubuntu-latest
10 steps:
11 - name: "Step 1"
12 run: echo "${MY_VAR}"
13 - name: "Step 2"
14 run: echo "${{env.MY_VAR}}"
15
16run: echo "${MY_VAR}"
17echo "${MY_VAR}"
18run: echo "${{env.MY_VAR}}"
19echo "foo"
20So although the outcome is similar at the end, the means of getting there is very different, based on when the substitution happens.
QUESTION
Vaadin production mode builds broken in v20?
Asked 2021-Aug-17 at 18:36Recently our vaadin production build has started failing and I'm too much of a node noob to figure out if this is a local problem or if it is related to vaadin 20.
When I switch back to vaadin 19 the problem goes away and I can reproduce the problem with an application generated on https://start.vaadin.com/app/
When running: ./mvnw package -P production I get the following error:
1[INFO] -------------------< com.example.application:myapp >--------------------
2[INFO] Building Project base for Spring Boot and Vaadin Flow 1.0-SNAPSHOT
3[INFO] --------------------------------[ jar ]---------------------------------
4[INFO]
5[INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @ myapp ---
6[INFO] Using 'UTF-8' encoding to copy filtered resources.
7[INFO] Using 'UTF-8' encoding to copy filtered properties files.
8[INFO] Copying 1 resource
9[INFO] Copying 3 resources
10[INFO]
11[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ myapp ---
12[INFO] Nothing to compile - all classes are up to date
13[INFO]
14[INFO] --- vaadin-maven-plugin:20.0.5:prepare-frontend (default) @ myapp ---
15[INFO] Copying frontend resources from jar files ...
16[INFO] Visited 163 resources. Took 88 ms.
17[INFO]
18[INFO] --- vaadin-maven-plugin:20.0.5:build-frontend (default) @ myapp ---
19[INFO] Scanning classes to find frontend configurations and dependencies...
20[INFO] Visited 1876 classes. Took 1089 ms.
21[INFO] Visited 108 classes. Took 31 ms.
22[INFO] Skipping `pnpm install` because the frontend packages are already installed in the folder '/home/me/devel/my-app/node_modules' and the hash in the file '/home/me/devel/my-app/node_modules/.vaadin/vaadin.json' is the same as in 'package.json'
23[INFO] Copying frontend resources from jar files ...
24[INFO] Visited 163 resources. Took 45 ms.
25[INFO] Running webpack ...
26[INFO] ------------------------------------------------------------------------
27[INFO] BUILD FAILURE
28[INFO] ------------------------------------------------------------------------
29[INFO] Total time: 6.769 s
30[INFO] Finished at: 2021-08-06T13:40:23+02:00
31[INFO] ------------------------------------------------------------------------
32[ERROR] Failed to execute goal com.vaadin:vaadin-maven-plugin:20.0.5:build-frontend (default) on project myapp: Execution default of goal com.vaadin:vaadin-maven-plugin:20.0.5:build-frontend failed: Webpack process exited with non-zero exit code.
33[ERROR] Stderr: '/home/me/devel/my-app/node_modules/.pnpm/webpack-cli@3.3.11_webpack@4.46.0/node_modules/webpack-cli/bin/cli.js:93
34[ERROR] throw err;
35[ERROR] ^
36[ERROR]
37[ERROR] Error: Cannot find module 'workbox-build/build/options/schema/webpack-generate-sw'
38[ERROR] Require stack:
39[ERROR] - /home/me/devel/my-app/node_modules/.pnpm/workbox-webpack-plugin@6.1.0_webpack@4.46.0/node_modules/workbox-webpack-plugin/build/generate-sw.js
40[ERROR] - /home/me/devel/my-app/node_modules/.pnpm/workbox-webpack-plugin@6.1.0_webpack@4.46.0/node_modules/workbox-webpack-plugin/build/index.js
41[ERROR] - /home/me/devel/my-app/webpack.generated.js
42[ERROR] - /home/me/devel/my-app/webpack.config.js
43[ERROR] - /home/me/devel/my-app/node_modules/.pnpm/webpack-cli@3.3.11_webpack@4.46.0/node_modules/webpack-cli/bin/utils/convert-argv.js
44[ERROR] - /home/me/devel/my-app/node_modules/.pnpm/webpack-cli@3.3.11_webpack@4.46.0/node_modules/webpack-cli/bin/cli.js
45[ERROR] - /home/me/devel/my-app/node_modules/.pnpm/webpack@4.46.0_webpack-cli@3.3.11/node_modules/webpack/bin/webpack.js
46[ERROR] at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
47[ERROR] at Function.Module._load (node:internal/modules/cjs/loader:778:27)
48[ERROR] at Module.require (node:internal/modules/cjs/loader:1005:19)
49[ERROR] at require (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
50[ERROR] at Object.<anonymous> (/home/me/devel/my-app/node_modules/.pnpm/workbox-webpack-plugin@6.1.0_webpack@4.46.0/node_modules/workbox-webpack-plugin/build/generate-sw.js:20:33)
51[ERROR] at Module._compile (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
52[ERROR] at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
53[ERROR] at Module.load (node:internal/modules/cjs/loader:981:32)
54[ERROR] at Function.Module._load (node:internal/modules/cjs/loader:822:12)
55[ERROR] at Module.require (node:internal/modules/cjs/loader:1005:19)
56[ERROR] at require (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
57[ERROR] at Object.<anonymous> (/home/me/devel/my-app/node_modules/.pnpm/workbox-webpack-plugin@6.1.0_webpack@4.46.0/node_modules/workbox-webpack-plugin/build/index.js:10:20)
58[ERROR] at Module._compile (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
59[ERROR] at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
60[ERROR] at Module.load (node:internal/modules/cjs/loader:981:32)
61[ERROR] at Function.Module._load (node:internal/modules/cjs/loader:822:12)
62[ERROR] at Module.require (node:internal/modules/cjs/loader:1005:19)
63[ERROR] at require (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
64[ERROR] at Object.<anonymous> (/home/me/devel/my-app/webpack.generated.js:10:28)
65[ERROR] at Module._compile (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
66[ERROR] at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
67[ERROR] at Module.load (node:internal/modules/cjs/loader:981:32)
68[ERROR] at Function.Module._load (node:internal/modules/cjs/loader:822:12)
69[ERROR] at Module.require (node:internal/modules/cjs/loader:1005:19)
70[ERROR] at require (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
71[ERROR] at Object.<anonymous> (/home/me/devel/my-app/webpack.config.js:10:22)
72[ERROR] at Module._compile (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
73[ERROR] at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
74[ERROR] at Module.load (node:internal/modules/cjs/loader:981:32)
75[ERROR] at Function.Module._load (node:internal/modules/cjs/loader:822:12) {
76[ERROR] code: 'MODULE_NOT_FOUND',
77[ERROR] requireStack: [
78[ERROR] '/home/me/devel/my-app/node_modules/.pnpm/workbox-webpack-plugin@6.1.0_webpack@4.46.0/node_modules/workbox-webpack-plugin/build/generate-sw.js',
79[ERROR] '/home/me/devel/my-app/node_modules/.pnpm/workbox-webpack-plugin@6.1.0_webpack@4.46.0/node_modules/workbox-webpack-plugin/build/index.js',
80[ERROR] '/home/me/devel/my-app/webpack.generated.js',
81[ERROR] '/home/me/devel/my-app/webpack.config.js',
82[ERROR] '/home/me/devel/my-app/node_modules/.pnpm/webpack-cli@3.3.11_webpack@4.46.0/node_modules/webpack-cli/bin/utils/convert-argv.js',
83[ERROR] '/home/me/devel/my-app/node_modules/.pnpm/webpack-cli@3.3.11_webpack@4.46.0/node_modules/webpack-cli/bin/cli.js',
84[ERROR] '/home/me/devel/my-app/node_modules/.pnpm/webpack@4.46.0_webpack-cli@3.3.11/node_modules/webpack/bin/webpack.js'
85[ERROR] ]
86[ERROR] }
87[ERROR] ': Unexpected exit value: 1, allowed exit values: [0], executed command [/usr/local/bin/node, /home/me/devel/my-app/node_modules/webpack/bin/webpack.js] in directory /home/me/devel/my-app with environment { redacted }, output was 5013 bytes (truncated):
88[ERROR] /home/me/devel/my-app/node_modules/.pnpm/webpack-cli@3.3.11_webpack@4.46.0/node_modules/webpack-cli/bin/cli.js:93
89[ERROR] throw err;
90[ERROR] ^
91[ERROR]
92[ERROR] Error: Cannot find module 'workbox-build/build/options/schema/webpack-generate-sw'
93[ERROR] Require stack:
94[ERROR] - /home/me/devel/my-app/node_modules/.pnpm/workbox-webpack-plugin@6.1.0_webpack@4.46.0/node_modules/workbox-webpack-plugin/build/generate-sw.js
95[ERROR] - /home/me/devel/my-app/node_modules/.pnpm/workbox-webpack-plugin@6.1.0_webpack@4.46.0/node_modules/workbox-webpack-plugin/build/index.js
96[ERROR] - /home/me/devel/my-app/webpack.generated.js
97[ERROR] - /home/me/devel/my-app/webpack.config.js
98[ERROR] - /home/me/devel/my-app/node_modules/.pnpm/webpack-cli@3.3.11_webpack@4.46.0/node_modules/webpack-cli/bin/utils/convert-argv.js
99[ERROR] - /home/me/devel/my-app/node_modules/.pnpm/webpack-cli@3.3.11_webpack@4.46.0/node_modules/webpack-cli/bin/cli.js
100[ERROR] - /home/me/devel/my-app/node_modules/.pnpm/webpack@4.46.0_webpack-cli@3.3.11/node_modules/webpack/bin/webpack.js
101[ERROR] at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
102[ERROR] at Function.Module._load (node:internal/modules/cjs/loader:778:27)
103[ERROR] at Module.require (node:internal/modules/cjs/loader:1005:19)
104[ERROR] at require (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
105[ERROR] at Object.<anonymous> (/home/me/devel/my-app/node_modules/.pnpm/workbox-webpack-plugin@6.1.0_webpack@4.46.0/node_modules/workbox-webpack-plugin/build/generate-sw.js:20:33)
106[ERROR] at Module._compile (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
107[ERROR] at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
108[ERROR] at Module.load (node:internal/modules/cjs/loader:981:32)
109[ERROR] at Function.Module._load (node:internal/modules/cjs/loader:822:12)
110[ERROR] at Module.require (node:internal/modules/cjs/loader:1005:19)
111[ERROR] at require (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
112[ERROR] at Object.<anonymous> (/home/me/devel/my-app/node_modules/.pnpm/workbox-webpack-plugin@6.1.0_webpack@4.46.0/node_modules/workbox-webpack-plugin/build/index.js:10:20)
113[ERROR] at Module._compile (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modul
114[ERROR] ...
115[ERROR] -cache/v8-compile-cache.js:192:30)
116[ERROR] at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
117[ERROR] at Module.load (node:internal/modules/cjs/loader:981:32)
118[ERROR] at Function.Module._load (node:internal/modules/cjs/loader:822:12)
119[ERROR] at Module.require (node:internal/modules/cjs/loader:1005:19)
120[ERROR] at require (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
121[ERROR] at Object.<anonymous> (/home/me/devel/my-app/webpack.generated.js:10:28)
122[ERROR] at Module._compile (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
123[ERROR] at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
124[ERROR] at Module.load (node:internal/modules/cjs/loader:981:32)
125[ERROR] at Function.Module._load (node:internal/modules/cjs/loader:822:12)
126[ERROR] at Module.require (node:internal/modules/cjs/loader:1005:19)
127[ERROR] at require (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
128[ERROR] at Object.<anonymous> (/home/me/devel/my-app/webpack.config.js:10:22)
129[ERROR] at Module._compile (/home/me/devel/my-app/node_modules/.pnpm/v8-compile-cache@2.0.3/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
130[ERROR] at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
131[ERROR] at Module.load (node:internal/modules/cjs/loader:981:32)
132[ERROR] at Function.Module._load (node:internal/modules/cjs/loader:822:12) {
133[ERROR] code: 'MODULE_NOT_FOUND',
134[ERROR] requireStack: [
135[ERROR] '/home/me/devel/my-app/node_modules/.pnpm/workbox-webpack-plugin@6.1.0_webpack@4.46.0/node_modules/workbox-webpack-plugin/build/generate-sw.js',
136[ERROR] '/home/me/devel/my-app/node_modules/.pnpm/workbox-webpack-plugin@6.1.0_webpack@4.46.0/node_modules/workbox-webpack-plugin/build/index.js',
137[ERROR] '/home/me/devel/my-app/webpack.generated.js',
138[ERROR] '/home/me/devel/my-app/webpack.config.js',
139[ERROR] '/home/me/devel/my-app/node_modules/.pnpm/webpack-cli@3.3.11_webpack@4.46.0/node_modules/webpack-cli/bin/utils/convert-argv.js',
140[ERROR] '/home/me/devel/my-app/node_modules/.pnpm/webpack-cli@3.3.11_webpack@4.46.0/node_modules/webpack-cli/bin/cli.js',
141[ERROR] '/home/me/devel/my-app/node_modules/.pnpm/webpack@4.46.0_webpack-cli@3.3.11/node_modules/webpack/bin/webpack.js'
142[ERROR] ]
143[ERROR] }
144On my local machine (macOs 11.4) I have node v16.6.1 installed, but it also fails on our jenkins server where node is not installed.
Best regards Jens
ANSWER
Answered 2021-Aug-09 at 09:41This is a webpack problem and is being currently addressed via https://github.com/vaadin/flow/pull/11527
Edit: The fix is included in the latest Vaadin 20.0.6 release via Vaadin Flow 7.0.6.
Community Discussions contain sources that include Stack Exchange Network
Tutorials and Learning Resources in Jenkin
Tutorials and Learning Resources are not available at this moment for Jenkin
Share this Page
Get latest updates on Jenkin