[JIRA] (JENKINS-54677) Switching container does not switch filesystem
Title: Message Title Timothy Clarke commented on JENKINS-54677 Re: Switching container does not switch filesystem Why would you expect a different file system? You're switching container after all, not pod 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42136) shared-library abstraction causing RejectedExecutionException when running sh() commands
Title: Message Title Timothy Clarke updated an issue Jenkins / JENKINS-42136 shared-library abstraction causing RejectedExecutionException when running sh() commands Change By: Timothy Clarke Comment: Looks to still be happening with [1.13.7|https://jenkins.manage.bpip.co/pluginManager/plugin/kubernetes/thirdPartyLicenses] 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42136) shared-library abstraction causing RejectedExecutionException when running sh() commands
Title: Message Title Timothy Clarke commented on JENKINS-42136 Re: shared-library abstraction causing RejectedExecutionException when running sh() commands Looks to still be happening with 1.13.7 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Timothy Clarke commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Hans Schulz Can you a point for me please? Were you using the 1.16 version of the plugin, or a more recent build? The reason I ask is the snippet generator http://jenkins:8080/pipeline-syntax/ (or similar depending on your environment) do not include the toolName or explicitly the registry: Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title
Timothy Clarke commented on JENKINS-38018
Re: withDockerRegistry fails to authenticate with DockerHub
Same as Yasuo Nakanishi here, but using k8s in AWS with a artifactory / jfrog repo. I current workaround is
docker.withRegistry('url', 'credential') {
However that is undesirable as it exposes the username and password in the build log eg
Executing shell script inside container [dind] of pod [jenkins-slave-mxj9x-12m9q]
Executing command: "docker" "login" "-u" "username" "-p" "password" "https://repo.example.com"
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-47488) PortMapping does not work when configured in pipeline
Title: Message Title
Timothy Clarke edited a comment on JENKINS-47488
Re: PortMapping does not work when configured in pipeline
I think your expectation here is wrong.{code:java}sh 'curl http://localhost:9000' // works only with 10080{code}When you're in a container you're in a different routed environment than the host you're on.The command above is being run within the container so "localhost" (I assume you mean 127.0.0.1) is the loopback address of the POD, not the loopback address of the nodeThe thing I have noticed (not sure if it's related) is that DNS names in the cluster are not being registered. I assume this may have been taken care of by k8s's now deprecated pod hostname. I think when you register a portMapping the name should be registered as a k8s svc name To get to the hostport you would need to go through the node name
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-47488) PortMapping does not work when configured in pipeline
Title: Message Title Timothy Clarke commented on JENKINS-47488 Re: PortMapping does not work when configured in pipeline I think your expectation here is wrong. sh 'curl http://localhost:9000' // works only with 10080 When you're in a container you're in a different routed environment than the host you're on. The command above is being run within the container so "localhost" (I assume you mean 127.0.0.1) is the loopback address of the POD, not the loopback address of the node The thing I have noticed (not sure if it's related) is that DNS names in the cluster are not being registered. I assume this may have been taken care of by k8s's now deprecated pod hostname. I think when you register a portMapping the name should be registered as a k8s svc name Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-25548) StageStep should reject duplicate stage names
Title: Message Title Timothy Clarke commented on JENKINS-25548 Re: StageStep should reject duplicate stage names While stage "Dev" may be bad as a duplicate, stage "Restarting Services" would be entirely valid. I have long complex pipelines where people want to see detail in the stages (Yes for some there are too many stages). We often have the same steps repeat in each environment as a build progresses. 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-36570) Implement pipeline compatibility
Title: Message Title
Timothy Clarke edited a comment on JENKINS-36570
Re: Implement pipeline compatibility
A little digging through logs, and taking a "how to get it working with, even if not fully supported" approach. It looks like flyweight tasks are getting prioritised as per rules in http://jenkins_host:8080/jenkins/advanced-build-queue/Heavy weight tasks on the other hand (where prioritisation would be really useful) look to be hitting [PriorityConfiguration.java#L211 -L216 |https://github.com/jenkinsci/priority-sorter-plugin/blob/master/src/main/java/jenkins/advancedqueue/PriorityConfiguration.java#L211 -L216 ] and so getting assigned a default value. Can we ease {code}if (!(item.task instanceof Job)) {{code}That way we could atleast add filters to re-prioritise
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-36570) Implement pipeline compatibility
Title: Message Title
Timothy Clarke edited a comment on JENKINS-36570
Re: Implement pipeline compatibility
A little digging through logs, and taking a "how to get it working with, even if not fully supported" approach. It looks like flyweight tasks are getting prioritised as per rules in http://jenkins_host:8080/jenkins/advanced-build-queue/Heavy weight tasks on the other hand (where prioritisation would be really useful) look to be hitting [PriorityConfiguration.java#L211|https://github.com/jenkinsci/priority-sorter-plugin/blob/master/src/main/java/jenkins/advancedqueue/PriorityConfiguration.java#L211] and so getting assigned a default value. Can we ease {code}if (!(item.task instanceof Job)) {{code}That way we could atleast add filters to re- prioritize prioritise
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-36570) Implement pipeline compatibility
Title: Message Title
Timothy Clarke commented on JENKINS-36570
Re: Implement pipeline compatibility
A little digging through logs, and taking a "how to get it working with, even if not fully supported" approach. It looks like flyweight tasks are getting prioritised as per rules in http://jenkins_host:8080/jenkins/advanced-build-queue/ Heavy weight tasks on the other hand (where prioritisation would be really useful) look to be hitting PriorityConfiguration.java#L211 and so getting assigned a default value. Can we ease
if (!(item.task instanceof Job)) {
That way we could atleast add filters to re-prioritize
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] [matrix-reloaded-plugin] (JENKINS-16229) Breaks "CopyArtifact" Plugin, case 8266
Title: Message Title Timothy Clarke commented on JENKINS-16229 Re: Breaks "CopyArtifact" Plugin, case 8266 I'm getting this one too, only difference is in step 2 instead of using "last successful build" I'm using build number Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ssh-slaves-plugin] (JENKINS-30561) Unable to launch slave using SSH
Title: Message Title Timothy Clarke edited a comment on JENKINS-30561 Re: Unable to launch slave using SSH Some feedback / defence / update I don't think this is a generic slave issue, not just SSH (but SSH could handle it better)If I change a slave to JNLP I get the same issue To all those who have posted, and to the maintainer, after looking a little further. I think this issue should be closed / rejected Ref https://jenkins.io/blog/2015/04/06/good-bye-java6/Some detail is in JENKINS-29412 and linked off that http://shahjapan.blogspot.co.uk/2015/09/jenkins-unable-to-launch-slave-machine.html pointing to the blog above Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ssh-slaves-plugin] (JENKINS-30561) Unable to launch slave using SSH
Title: Message Title Timothy Clarke commented on JENKINS-30561 Re: Unable to launch slave using SSH Some feedback / defence / update I don't think this is a generic slave issue, not just SSH (but SSH could handle it better) If I change a slave to JNLP I get the same issue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [parameterized-remote-trigger-plugin] (JENKINS-23895) does not respect http_proxy variables
Title: Message Title Timothy Clarke commented on JENKINS-23895 Re: does not respect http_proxy variables This one is blocking me as well I'd love to use the plugin, but I'm within an environment where I have to go through proxies between the jenkins hosts. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
