[JIRA] (JENKINS-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title
Bruno Meneguello edited a comment on JENKINS-39952
Re: "Registry credentials" is not working with a private docker registry
Nearly 2020 and still having I'm using this issue with Kubernetes cloud and a docker-dind image .I just succeeded by adding a shell step with {{docker login ... before the step . }}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176574.1479864408000.5696.1576085820303%40Atlassian.JIRA.
[JIRA] (JENKINS-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title Bruno Meneguello commented on JENKINS-39952 Re: "Registry credentials" is not working with a private docker registry Nearly 2020 and still having this issue. I just succeeded by adding a shell step with docker login ... before the step Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176574.1479864408000.5583.1576075560270%40Atlassian.JIRA.
[JIRA] (JENKINS-60227) Users other than admin but with job configure privileges are unable to configure jobs
Title: Message Title Bruno Meneguello commented on JENKINS-60227 Re: Users other than admin but with job configure privileges are unable to configure jobs I'm having the same issue. How was this fixed? Something will be updated? There is a workaround? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203202.1574249655000.9076.1574963040165%40Atlassian.JIRA.
[JIRA] (JENKINS-60087) Kubernetes nodes failed not removed
Title: Message Title
Bruno Meneguello updated an issue
Jenkins / JENKINS-60087
Kubernetes nodes failed not removed
Change By:
Bruno Meneguello
When my pods are killed by OOM, the nodes aren't removed, this pollutes the interface and causes the job stay running but zombie.!image-2019-11-07-12-18-14-069.png! If I click to abort the job it prints "Are you sure you want to abort null?" !image-2019-11-07-12-07-52-341.png! And on This message come from [executors.jelly|https://github.com/jenkinsci/jenkins/blob/0af98fe7163a821710f8be0dbc11086d4acd8bf2/core/src/main/resources/lib/hudson/executors.jelly#L113] when {{executor.currentExecutable.fullDisplayName}} is {{null.}}On proceed it deletes the node, as expected.In the logs I found these entries:{code:java}INFO o.c.j.p.k.pod.retention.Reaper#eventReceived: default/infra-mf3jg was just deleted, so removing corresponding Jenkins agentINFO j.s.DefaultJnlpSlaveReceiver#channelClosed: IOHub#1: Worker[channel:java.nio.channels.SocketChannel[connected local=/172.17.0.2:5 remote=ip-172-16-29-221.ec2.internal/172.16.29.221:39454]] / Computer.threadPoolForRemoting [#12347] for infra-mf3jg terminated: java.nio.channels.ClosedChannelException{code}I think it's related to Reaper class, when DELETED event is received ([here|https://github.com/jenkinsci/kubernetes-plugin/blob/5ce0693a00699fec026acfd8952f98d4bd8ac309/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pod/retention/Reaper.java#L122]) which calls [Node#removeNode| [https://github.com/jenkinsci/jenkins/blob/41a13dffc612ca3b5c48ab3710500562a3b40bf7/core/src/main/java/jenkins/model/Nodes.java #L270].] There I found this comment "If the node instance is not in the list of nodes, then this will be a no-op, even if there is another instance with the same".I think by some reason the instance passed by Reaper is different from Node, which causes it to be ignored.The OfflineCause for the node is "Node is being removed"!image-2019-11-07-12-15-35-071.png!
Add Comment
[JIRA] (JENKINS-60087) Kubernetes nodes failed not removed
Title: Message Title
Bruno Meneguello updated an issue
Jenkins / JENKINS-60087
Kubernetes nodes failed not removed
Change By:
Bruno Meneguello
When my pods are killed by OOM, the nodes aren't removed, this pollutes the interface and causes the job stay running but zombie. !image-2019-11-07-12-18-14-069.png! If I click to abort the job it prints "Are you sure you want to abort null?"!image-2019-11-07-12-07-52-341.png!And on proceed it deletes the node, as expected.In the logs I found these entries:{code:java}INFO o.c.j.p.k.pod.retention.Reaper#eventReceived: default/infra-mf3jg was just deleted, so removing corresponding Jenkins agent INFO j.s.DefaultJnlpSlaveReceiver#channelClosed: IOHub#1: Worker[channel:java.nio.channels.SocketChannel[connected local=/172.17.0.2:5 remote=ip-172-16-29-221.ec2.internal/172.16.29.221:39454]] / Computer.threadPoolForRemoting [#12347] for infra-mf3jg terminated: java.nio.channels.ClosedChannelException {code} I think it's related to Reaper class, when DELETED event is received ([here|https://github.com/jenkinsci/kubernetes-plugin/blob/5ce0693a00699fec026acfd8952f98d4bd8ac309/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pod/retention/Reaper.java#L122]) which calls [Node#removeNode|[https://github.com/jenkinsci/jenkins/blob/41a13dffc612ca3b5c48ab3710500562a3b40bf7/core/src/main/java/jenkins/model/Nodes.java#L270].] There I found this comment "If the node instance is not in the list of nodes, then this will be a no-op, even if there is another instance with the same".I think by some reason the instance passed by Reaper is different from Node, which causes it to be ignored.The OfflineCause for the node is "Node is being removed"!image-2019-11-07-12-15-35-071.png!
Add Comment
[JIRA] (JENKINS-60087) Kubernetes nodes failed not removed
Title: Message Title Bruno Meneguello updated an issue Jenkins / JENKINS-60087 Kubernetes nodes failed not removed Change By: Bruno Meneguello Attachment: image-2019-11-07-12-18-14-069.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202931.1573139366000.10607.1573139940106%40Atlassian.JIRA.
[JIRA] (JENKINS-60087) Kubernetes nodes failed not removed
Title: Message Title Bruno Meneguello updated an issue Jenkins / JENKINS-60087 Kubernetes nodes failed not removed Change By: Bruno Meneguello Attachment: image-2019-11-07-12-15-35-071.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202931.1573139366000.10606.1573139760075%40Atlassian.JIRA.
[JIRA] (JENKINS-60087) Kubernetes nodes failed not removed
Title: Message Title Bruno Meneguello created an issue Jenkins / JENKINS-60087 Kubernetes nodes failed not removed Issue Type: Bug Assignee: Unassigned Attachments: image-2019-11-07-12-07-52-341.png Components: core, kubernetes-plugin Created: 2019-11-07 15:09 Environment: Jenkins LTS 2.190.2 Kubernetes Plugin 1.20.2 Priority: Minor Reporter: Bruno Meneguello When my pods are killed by OOM, the nodes aren't removed, this pollutes the interface and causes the job stay running but zombie. If I click to abort the job it prints "Are you sure you want to abort null?" And on proceed it deletes the node, as expected. In the logs I found these entries: INFO o.c.j.p.k.pod.retention.Reaper#eventReceived: default/infra-mf3jg was just deleted, so removing corresponding Jenkins agent
[JIRA] (JENKINS-59796) Item names with U+00E7 (Cedilla) raise errors
Title: Message Title Bruno Meneguello closed an issue as Cannot Reproduce I'm closing this issue since I've tested with a pristine jenkins installation and the error doesn't happens. I think this could be caused by some old data format and some migration issue. Jenkins / JENKINS-59796 Item names with U+00E7 (Cedilla) raise errors Change By: Bruno Meneguello Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe
[JIRA] (JENKINS-23349) Item names containing an emoji are not accessible
Title: Message Title Bruno Meneguello commented on JENKINS-23349 Re: Item names containing an emoji are not accessible I've created and linked a ticket detailing the problem Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155495.1402054331000.8467.1571197320331%40Atlassian.JIRA.
[JIRA] (JENKINS-59796) Item names with U+00E7 (Cedilla) raise errors
Title: Message Title Bruno Meneguello created an issue Jenkins / JENKINS-59796 Item names with U+00E7 (Cedilla) raise errors Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-10-15 21:11 Labels: url-encoding views jobs Priority: Critical Reporter: Bruno Meneguello Version 2.190.1 How to reproduce: Create a view or job having "ç" (not in display name) Try to build a pipeline or open API view Workaround: Rename job/view to remove cedilla character (it's ok to have cedilla in display name) Stack trace: With a job named /Test/Çedilla: WARNING h.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: job.shortUrl in /job/Test/. Reason: java.lang.reflect.InvocationTargetException java.lang.NullPointerException Caused: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor363.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at
[JIRA] (JENKINS-23349) Item names containing an emoji are not accessible
Title: Message Title Bruno Meneguello commented on JENKINS-23349 Re: Item names containing an emoji are not accessible I've upgraded jenkins to latest LTS today and noticed problem with "ç" (cedilla) char U+00E7. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155495.1402054331000.8320.1571173440333%40Atlassian.JIRA.
[JIRA] (JENKINS-56483) Limit local storage utilization
Title: Message Title Bruno Meneguello commented on JENKINS-56483 Re: Limit local storage utilization https://kubernetes.io/docs/concepts/policy/limit-range/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198084.1552057119000.11398.1565364600124%40Atlassian.JIRA.
[JIRA] (JENKINS-56483) Limit local storage utilization
Title: Message Title Bruno Meneguello commented on JENKINS-56483 Re: Limit local storage utilization It's possible to use "Raw yaml for the Pod" with "Yaml merge strategy" = "Merge" and something like: spec: containers: - name: jnlp resources: limits: ephemeral-storage: "90Gi" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198084.1552057119000.11295.1565352420143%40Atlassian.JIRA.
[JIRA] (JENKINS-56673) Better handling of ChannelClosedException in Declarative pipeline
Title: Message Title Bruno Meneguello commented on JENKINS-56673 Re: Better handling of ChannelClosedException in Declarative pipeline Carlos Sanchez I don't think this is the same case. I've opened a ticket with the same problem (sorry). What I've tracked is when my pods are killed (by OOMKiller, usually) the job doesn't get aborted, it hangs indefinitely. The node label gets an "offline" and node log displays the OP message. If I click the abort button, the job is aborted immediately. So, why this don't occur when the node is detected to be offline? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198308.1553221694000.20624.1559647860187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57675) Pipeline steps running forever when executor fails
Title: Message Title Bruno Meneguello created an issue Jenkins / JENKINS-57675 Pipeline steps running forever when executor fails Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin, pipeline Created: 2019-05-24 18:29 Environment: Jenkins 2.164.3 Kubernetes Plugin 1.15.4 Priority: Minor Reporter: Bruno Meneguello I've been using Pipelines with EC2, ECS and now Kubernetes dynamic executors for some time. I always noted an strange behavior but never found more information: When, by any reason, my agent dies, some Pipeline steps don't fail and keep running forever, unless I use timeout steps. I just need to abort the job and it goes away. Another strange thing is the executor stay present with the "offline" label, even the log displaying the failed connection. And it goes away with the job, when aborted. Add Comment
[JIRA] (JENKINS-52160) nodes are launched even when in shutdown mode
Title: Message Title Bruno Meneguello edited a comment on JENKINS-52160 Re: nodes are launched even when in shutdown mode I think the *Jenkins.getInstance().isQuietingDown()* status should be checked here [NodeProvisioner.java#L302| [ https://github.com/jenkinsci/jenkins/blob/jenkins-2.177/core/src/main/java/hudson/slaves/NodeProvisioner.java#L302 |https://github.com/jenkinsci/jenkins/blob/jenkins-2.177/core/src/main/java/hudson/slaves/NodeProvisioner.java#L302[ ] ] to avoid provisioning new slaves. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191912.1529951353000.4817.1558214100087%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52160) nodes are launched even when in shutdown mode
Title: Message Title Bruno Meneguello edited a comment on JENKINS-52160 Re: nodes are launched even when in shutdown mode I think the ` * Jenkins.getInstance().isQuietingDown() ` * status should be checked here ( [NodeProvisioner.java#L302|[ https://github.com/jenkinsci/jenkins/blob/jenkins-2.177/core/src/main/java/hudson/slaves/NodeProvisioner.java#L302 [) |https://github.com/jenkinsci/jenkins/blob/jenkins-2.177/core/src/main/java/hudson/slaves/NodeProvisioner.java#L302 [ ] ] to avoid provisioning new slaves. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191912.1529951353000.4815.1558214040152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52160) nodes are launched even when in shutdown mode
Title: Message Title Bruno Meneguello commented on JENKINS-52160 Re: nodes are launched even when in shutdown mode I think the `Jenkins.getInstance().isQuietingDown()` status should be checked here (https://github.com/jenkinsci/jenkins/blob/jenkins-2.177/core/src/main/java/hudson/slaves/NodeProvisioner.java#L302[)|https://github.com/jenkinsci/jenkins/blob/jenkins-2.177/core/src/main/java/hudson/slaves/NodeProvisioner.java#L302] to avoid provisioning new slaves. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191912.1529951353000.4813.1558213980155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56757) podAffinity is ignored in YAML definition
Title: Message Title Bruno Meneguello created an issue Jenkins / JENKINS-56757 podAffinity is ignored in YAML definition Issue Type: New Feature Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-03-26 12:23 Priority: Minor Reporter: Bruno Meneguello I'm trying to define my pod template as spec: affinity: podAffinity: preferredDuringSchedulingIgnoredDuringExecution: - labelSelector: matchLabels: jenkins: slave But the podAffinity is ignored. I noticed the source in PodTemplateUtils.java#L252 only merges nodeSelector Add Comment
[JIRA] (JENKINS-29654) java not found starting the slave if java is installed with a user-data/cloud-init manifest
Title: Message Title Bruno Meneguello commented on JENKINS-29654 Re: java not found starting the slave if java is installed with a user-data/cloud-init manifest Cloud-Init runs as service, but init script is run as soon ssh becomes available. You need something that waits the initialization to be completed. I suggest to check if /run/cloud-init/result.json exists then proceed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26881) Doesn't send any notifications to webhook
Title: Message Title Bruno Meneguello resolved as Fixed Jenkins / JENKINS-26881 Doesn't send any notifications to webhook Change By: Bruno Meneguello Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title Bruno Meneguello commented on JENKINS-40484 Re: Unable to use withMaven step inside docker container Yes, it does Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title
Bruno Meneguello commented on JENKINS-40484
Re: Unable to use withMaven step inside docker container
Same here, with this simple use case:
node('master') {
docker.image('maven').inside {
withMaven {
sh 'mvn -version'
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28892) Parts of workflow not cancelable after crash
Title: Message Title Bruno Meneguello created an issue Jenkins / JENKINS-28892 Parts of workflow not cancelable after crash Issue Type: Bug Assignee: Jesse Glick Attachments: jenkins.png Components: workflow-plugin Created: 12/Jun/15 9:41 PM Priority: Minor Reporter: Bruno Meneguello After crashing (I think it's because have overloaded the server with 60 parallel file transfers of 2.3Gb), I nedded to reboot (the service, then the machine) but those parts of unknow step don't go off. Add Comment
