[JIRA] (JENKINS-49719) Unable to save the settings in Manage Jenkins System configuration
Title: Message Title Oleg Nenashev commented on JENKINS-49719 Re: Unable to save the settings in Manage Jenkins System configuration I am not sure what is "com.wwpass.wwpassauth.WwpassLoginService", but it does not come from the Jenkins organization: https://github.com/search?utf8=%E2%9C%93&q=org%3Ajenkinsci+%22com.wwpass.wwpassauth%22&type= Is it your internal plugin? 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-49720) NVM wrapper hard-coded path
Title: Message Title Pavel Novak updated an issue Jenkins / JENKINS-49720 NVM wrapper hard-coded path Change By: Pavel Novak Once there is nvm installed on the machine, plugin dont inherit and dont respect NVM settings.Our case: * having NVM at _/data/jenkins-misc/nvm/_ (same as *NVM_DIR* system property targets) * when using and configure wrapper plugin, all data are generated at jenkins user home- in our case _/var/lib/jenkins.nvm (default path)__Problem is over at following file line (NvmWrapperUtil.java), because there is hardcoded path_[https://github.com/jenkinsci/nvm-wrapper-plugin/blob/97093d1b19467b015565512317d065dc5e752ef7/src/main/java/org/jenkinsci/plugins/nvm/NvmWrapperUtil.java#L21] Note- because path is hardcoded, it is not possible to override it anyway Kindly, please, any possibility to fix this?We are started to having serious problem with the free space, because when _*.*nvm_ directory is symlink-ed, than plugin also dont works.Thanks in advance - Otherwise, if there is any way to solve that, or info who and how to contact, I will appreciate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49669) readJSON returns non serializable JSON object
Title: Message Title Oleg Nenashev commented on JENKINS-49669 Re: readJSON returns non serializable JSON object It is AFAICT. You are on Jenkins 2.102+, right? 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-49720) NVM wrapper hard-coded path
Title: Message Title Pavel Novak updated an issue Jenkins / JENKINS-49720 NVM wrapper hard-coded path Change By: Pavel Novak Once there is nvm installed on the machine, plugin dont inherit and dont respect NVM settings.Our case: * having NVM at _/data/jenkins-misc/nvm/_ (same as *NVM_DIR* system property targets) * when using and configure wrapper plugin, all data are generated at jenkins user home- in our case _/var/lib/jenkins.nvm (default path)__Problem is over at following file line (NvmWrapperUtil.java), because there is hardcoded path_[https://github.com/jenkinsci/nvm-wrapper-plugin/blob/97093d1b19467b015565512317d065dc5e752ef7/src/main/java/org/jenkinsci/plugins/nvm/NvmWrapperUtil.java#L21]Kindly, please, any possibility to fix this?We are started to having serious problem with the free space, because when _*.*nvm_ directory is symlink-ed, than plugin also dont works.Thanks in advance - Otherwise, if there is any way to solve that, or info who and how to contact, I will appreciate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48050) Replace Declarative Docker agent directive with new implementation
Title: Message Title Nicolas De Loof commented on JENKINS-48050 Re: Replace Declarative Docker agent directive with new implementation Some update on this issue: we'd like to introduce some "version:2" in declarative pipeline so changing behaviour to this new agent design would be opt-in only and we wouldn't break existing pipelines. docker-plugin do support `dockerNode` pipeline DSL keyword to provision a full jenkins node within a pipeline. This sounds like a nice candidate for docker agent implementation in declarative, as we would then get a full agent to fully honour Jenkins APIs and expectations (wrappers, env, path, etc). A major issue to remain is the way docker.inside to let one access workspace from higher level agent. This introduce filesystem permission issues, so forced user to run in container. To get rid of this, safer option seems imho to not keep this behaviour for nested agents, and only support use of `stash` to share files between agents. 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-49720) NVM wrapper hard-coded path
Title: Message Title Pavel Novak updated an issue Jenkins / JENKINS-49720 NVM wrapper hard-coded path Change By: Pavel Novak Once there is nvm installed on the machine, plugin dont inherit and dont respect NVM settings.Our case: * having NVM at _/data/jenkins-misc/nvm/_ (same as * NVM_DIR * system property targets) * when using and configure wrapper plugin, all data are generated at jenkins user home- in our case _/var/lib/jenkins.nvm (default path)__Problem is over at following file line (NvmWrapperUtil.java), because there is hardcoded path_[https://github.com/jenkinsci/nvm-wrapper-plugin/blob/97093d1b19467b015565512317d065dc5e752ef7/src/main/java/org/jenkinsci/plugins/nvm/NvmWrapperUtil.java#L21]Kindly, please, any possibility to fix this?We are started to having serious problem with the free space, because when _*.*nvm_ directory is symlink-ed, than plugin also dont works.Thanks in advance Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because
[JIRA] (JENKINS-49720) NVM wrapper hard-coded path
Title: Message Title Pavel Novak created an issue Jenkins / JENKINS-49720 NVM wrapper hard-coded path Issue Type: Bug Assignee: Tomas Salazar Components: nvm-wrapper-plugin Created: 2018-02-23 13:04 Environment: irelevant Jenkins ver. 2.89.3 NVM wrapper 0.1.4 Priority: Minor Reporter: Pavel Novak Once there is nvm installed on the machine, plugin dont inherit and dont respect NVM settings. Our case: having NVM at /data/jenkins-misc/nvm/ (same as NVM_DIR system property targets) when using and configure wrapper plugin, all data are generated at jenkins user home- in our case /var/lib/jenkins.nvm (default path) Problem is over at following file line (NvmWrapperUtil.java), because there is hardcoded path https://github.com/jenkinsci/nvm-wrapper-plugin/blob/97093d1b19467b015565512317d065dc5e752ef7/src/main/java/org/jenkinsci/plugins/nvm/NvmWrapperUtil.java#L21 Kindly, please, any possibility to fix this? We are started to having serious problem with the free space, because when *.*nvm directory is symlink-ed, than plugin also dont works. Thanks in advance
[JIRA] (JENKINS-49718) Adding Artifactory server to conan client fails and PRINTS PASSWORD!!
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-49718 Re: Adding Artifactory server to conan client fails and PRINTS PASSWORD!! If credentials for Artifactory aren't set in any way, it does something and it crashes Conan: Remote '11836215-a959-46e2-829d-ab8c0cddb688' username: Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/conans/client/command.py", line 1099, in run method(args[0][1:]) File "/usr/local/lib/python3.6/site-packages/conans/client/command.py", line 730, in user password=args.password) File "/usr/local/lib/python3.6/site-packages/conans/client/conan_api.py", line 63, in wrapper return f(*args, **kwargs) File "/usr/local/lib/python3.6/site-packages/conans/client/conan_api.py", line 563, in user self._manager.user(remote, name, password) File "/usr/local/lib/python3.6/site-packages/conans/client/manager.py", line 549, in user name, password = self._user_io.request_login(remote_name=remote, username=name) File "/usr/local/lib/python3.6/site-packages/conans/client/userio.py", line 30, in request_login user_input = self.get_username(remote_name) File "/usr/local/lib/python3.6/site-packages/conans/client/userio.py", line 44, in get_username return self._get_env_username(remote_name) or raw_input() EOFError: EOF when reading a line ERROR: EOF when reading a line Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49718) Adding Artifactory server to conan client fails and PRINTS PASSWORD!!
Title: Message Title
Ovidiu-Florin Bogdan commented on JENKINS-49718
Re: Adding Artifactory server to conan client fails and PRINTS PASSWORD!!
The exact same thing happens if not using the Credentials plugin and provided the user and password in the corresponding fiends of the Artifactory server settings.
ERROR: HTTPSConnectionPool(host='conan.bintray.com', port=443): Max retries exceeded with url: /v1/users/authenticate (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 110] Connection timed out',))
Unable to connect to conan-center=https://conan.bintray.com
sh: : No such file or directory
1. It should not show the password. 2. it should not try to connect to conan-center, especially since the Enable push to Bintray is disabled.
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-49719) Unable to save the settings in Manage Jenkins System configuration
Title: Message Title Adithya Maniyala commented on JENKINS-49719 Re: Unable to save the settings in Manage Jenkins System configuration When trying open the Config system in Manage settings and without doing anything if i save it throuws an exception for which i have placed the trace report 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-49719) Unable to save the settings in Manage Jenkins System configuration
Title: Message Title Adithya Maniyala assigned an issue to Oleg Nenashev Jenkins / JENKINS-49719 Unable to save the settings in Manage Jenkins System configuration Change By: Adithya Maniyala Assignee: Adithya Maniyala Oleg Nenashev 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-49719) Unable to save the settings in Manage Jenkins System configuration
Title: Message Title Adithya Maniyala created an issue Jenkins / JENKINS-49719 Unable to save the settings in Manage Jenkins System configuration Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2018-02-23 12:50 Environment: Windows Priority: Critical Reporter: Adithya Maniyala net.sf.json.JSONException: JSONObject["name"] not found. at net.sf.json.JSONObject.getString(JSONObject.java:2040) at com.wwpass.wwpassauth.WwpassLoginService$DescriptorImpl.configure(WwpassLoginService.java:201) at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:3681) at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:3645) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.
[JIRA] (JENKINS-49719) Unable to save the settings in Manage Jenkins System configuration
Title: Message Title Adithya Maniyala assigned an issue to Adithya Maniyala Jenkins / JENKINS-49719 Unable to save the settings in Manage Jenkins System configuration Change By: Adithya Maniyala Assignee: Oleg Nenashev Adithya Maniyala 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-49718) Adding Artifactory server to conan client fails and PRINTS PASSWORD!!
Title: Message Title
Ovidiu-Florin Bogdan created an issue
Jenkins / JENKINS-49718
Adding Artifactory server to conan client fails and PRINTS PASSWORD!!
Issue Type:
Bug
Assignee:
Eyal Ben Moshe
Components:
artifactory-plugin
Created:
2018-02-23 12:47
Environment:
Jenkins 2.89.3 from the Docker image jenkins/jenkins:2.89.3 The build is running inside a Docker container.
Labels:
plugin jenkins pipeline security
Priority:
Critical
Reporter:
Ovidiu-Florin Bogdan
When adding the Artifactory server to Conan as a remote, it fails with rejecting the username and password for conan-center (the default conan remote) and then prints the credential password on the screen by saying that it's an unknown command. Jenkinsfile follows:
def LINUX_DOCKER_IMAGE = ""
def ARTIFACTORY_NAME = ""
def ARTIFACTORY_REPO = ""
String setup_conan = "config install "
node('linux') {
stage("Get Sources"){
checkout scm
}
docker.image(LINUX_DOCKER_IMAGE) {
def server = Artifactory.server ARTIFACTORY_NAME
def client = Artifactory.newConanClient userHome: "/tmp/conan_home"
def serverName = client.remote.add server: server, repo: ARTIFACTORY_REPO
stage("Setup Conan") {
client.run(command: setup_conan)
}
stage("Build package") {
client.run(comnand: "create --profile Linux-Release . foo/bar")
}
stage("Upload package") {
String command = "upload -r ${serve
[JIRA] (JENKINS-49717) no token field in Openshift OAuth token credential type
Title: Message Title Bernat Bautista updated an issue Jenkins / JENKINS-49717 no token field in Openshift OAuth token credential type Change By: Bernat Bautista Hello, I'm using a Jenkins 2.89 master docker image based on openshift/jenkins-2-centos7 I want to add a Openshift OAuth token credential (to configure then slaves) , but there is no token, ID neither description field. Only the Scope field is showed. What can I check to see what is happening? Thanks! 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-49717) no token field in Openshift OAuth token credential type
Title: Message Title Bernat Bautista updated an issue Jenkins / JENKINS-49717 no token field in Openshift OAuth token credential type Change By: Bernat Bautista Hello, I'm using a Jenkins 2.89 master docker image based on openshift/jenkins-2-centos7 I want to add a Openshift OAuth token credential, but there is no token, ID neither description field. Only the Scope field is showed. What can I check to see what is happening? Thanks! 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-49669) readJSON returns non serializable JSON object
Title: Message Title Thomas Mair commented on JENKINS-49669 Re: readJSON returns non serializable JSON object We are using version 1.4.1 I also guess the bug is part of the library from the beginning 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-49717) no token field in Openshift OAuth token credential type
Title: Message Title Bernat Bautista created an issue Jenkins / JENKINS-49717 no token field in Openshift OAuth token credential type Issue Type: Bug Assignee: Stephen Connolly Components: credentials-plugin Created: 2018-02-23 12:37 Priority: Major Reporter: Bernat Bautista Hello, I'm using a Jenkins master docker image based on openshift/jenkins-2-centos7 I want to add a Openshift OAuth token credential, but there is no token, ID neither description field. Only the Scope field is showed. What can I check to see what is happening? Thanks! Add Comment
[JIRA] (JENKINS-49576) Failure creating provisioned agent after successful provisioning
Title: Message Title Henti Smith commented on JENKINS-49576 Re: Failure creating provisioned agent after successful provisioning Hi Chenyang Liu We run only a single instance of Jenkins. We cannot reproduce this issue, I've attached full logs including details in azure-jenkins.log for one VM and then date/info for each VM it's happened on azure-jenkins-log jenkins-linux-build-slaveb448a0.jenkins.log jenkins-linux-8-core-build-slave90ae40.jenkins.log jenkins-linux-build-slaveead5a0.jenkins.log jenkins-linux-8-core-build-slavef95190.jenkins.log jenkins-linux-8-core-build-slave3349a0.jenkins.log jenkins-linux-8-core-build-slaveaaff00.jenkins.log jenkins-linux-8-core-build-slaveb0c9f0.jenkins.log Please let me know if you need more detail. Regards Henti 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-49576) Failure creating provisioned agent after successful provisioning
Title: Message Title Henti Smith updated an issue Jenkins / JENKINS-49576 Failure creating provisioned agent after successful provisioning Change By: Henti Smith Attachment: jenkins-linux-8-core-build-slaveb0c9f0.jenkins.log Attachment: jenkins-linux-8-core-build-slaveaaff00.jenkins.log Attachment: jenkins-linux-8-core-build-slave3349a0.jenkins.log Attachment: jenkins-linux-8-core-build-slavef95190.jenkins.log Attachment: jenkins-linux-build-slaveead5a0.jenkins.log Attachment: jenkins-linux-8-core-build-slave90ae40.jenkins.log Attachment: jenkins-linux-build-slaveb448a0.jenkins.log Add Comment
[JIRA] (JENKINS-49576) Failure creating provisioned agent after successful provisioning
Title: Message Title Henti Smith updated an issue Jenkins / JENKINS-49576 Failure creating provisioned agent after successful provisioning Change By: Henti Smith Attachment: azure-jenkins-log 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-19465) Slave hangs while being launched
Title: Message Title Oleg Nenashev commented on JENKINS-19465 Re: Slave hangs while being launched Well, generally you need to dump stacktraces during the connection hanging somehow. https://forums.docker.com/t/how-to-dump-heap-from-a-java-program-running-in-container/3217 . Your mileage may vary. For master side you can also use https://wiki.jenkins.io/display/JENKINS/Support+Core+Plugin 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-19465) Slave hangs while being launched
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-19465 Re: Slave hangs while being launched I'd love to. How do I get them? can you point me to some docs on this? I have both Jenkins Master and Slave running in Docker containers. Now it works because I've changed the slave IP, triggered a connection that failed, then switched back the IP and it worked. For the moment I've used Sergii Ovcharenko's solution and linked /dev/urandom to /dev/random, but I can change it back if you tell me how to get the stacktraces from a running Jenkins. Remember I don't have any errors, no messages in the node connection log. Just the spinning gif thingy. 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-49715) Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject
Title: Message Title Oleg Nenashev commented on JENKINS-49715 Re: Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject Björn Becker Note that JSONObjects are Blacklisted in Remoting. Usage of such workarounds is generally a bad idea 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-49715) Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject
Title: Message Title Oleg Nenashev commented on JENKINS-49715 Re: Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject The plugin has some test automation which could reproduce the issue. The problem is that it's baseline is 1.554.1, which makes the PCT Compatibility facelift a bit tough. Changes to be done: Stop serializing JSON objects over the channel Plugin facelift & PCT 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-49716) Publish Over SSH Pipeline Failure
Title: Message Title Stephan Watermeyer updated an issue Jenkins / JENKINS-49716 Publish Over SSH Pipeline Failure Change By: Stephan Watermeyer Attachment: screencapture.png 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-49715) Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49715 Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject Change By: Oleg Nenashev Component/s: packer-plugin Component/s: _unsorted 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-49716) Publish Over SSH Pipeline Failure
Title: Message Title Stephan Watermeyer updated an issue Jenkins / JENKINS-49716 Publish Over SSH Pipeline Failure Change By: Stephan Watermeyer Attachment: screencapture-swpsci06-8080-view-NORDICATM-job-nordicatm-deploy-swpsws28-feature-pipeline-syntax-1519386385301.png 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-49716) Publish Over SSH Pipeline Failure
Title: Message Title Stephan Watermeyer created an issue Jenkins / JENKINS-49716 Publish Over SSH Pipeline Failure Issue Type: Task Assignee: Alex Earl Attachments: screencapture-swpsci06-8080-view-NORDICATM-job-nordicatm-deploy-swpsws28-feature-pipeline-syntax-1519386385301.png Components: publish-over-ssh-plugin Created: 2018-02-23 11:48 Environment: Jenkins ver. 2.89.4 Publish Over SSH Plugin 1.18 Labels: plugin pipeline Priority: Major Reporter: Stephan Watermeyer I would like to use the Plugin in my Pipeline but it fails with the issue mentioned below: Feb 23, 2018 11:03:42 AM org.jenkinsci.plugins.structs.describable.DescribableParameter uncoerce WARNING: failed to uncoerce BapSshPublisherPlugin[consolePrefix=SSH: ,delegate=BPInstanceConfig[publishers=[BapSshPublisher[configName=swpsws28,verbose=false,transfers=[BapSshTransfer[sourceFiles=x,excludes=,removePrefix=,remoteDirectory=,remoteDirectorySDF=false,flatten=false,cleanRemote=false,noDefaultExcludes=false,makeEmptyDirs=false,patternSeparator=[, ]+,execCommand=y,execTimeout=12,pseudoTty=false,agentForwarding=false]],useWorkspaceInPromotion=false,usePromotionTimestamp=false,retry=,label= ,credentials=
[JIRA] (JENKINS-49715) Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject
Title: Message Title Oleg Nenashev commented on JENKINS-49715 Re: Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject I confirm the JEP-200 side of the issue, at least 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-19465) Slave hangs while being launched
Title: Message Title Oleg Nenashev commented on JENKINS-19465 Re: Slave hangs while being launched Ovidiu-Florin Bogdan would it be possible to get stacktraces from agent/master? 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-49715) Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject
Title: Message Title Björn Becker created an issue Jenkins / JENKINS-49715 Packer Plugin Nullpointer Exception and SecurityException: Rejected: net.sf.json.JSONObject Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2018-02-23 11:42 Labels: JEP-200 Priority: Minor Reporter: Björn Becker I'm not sure if this is related to JEP-200, but after Upgrade I receive these Exceptions when using the Packer Plugin: Feb 23, 2018 12:39:25 PM hudson.model.Run execute INFO: packer-centos7 #361 main build action completed: SUCCESS Feb 23, 2018 12:39:25 PM biz.neustar.jenkins.plugins.packer.PackerPublisher getRemotePackerExec SEVERE: java.lang.NullPointerException at biz.neustar.jenkins.plugins.packer.PackerPublisher.getRemotePackerExec(PackerPublisher.java:217) at biz.neustar.jenkins.plugins.packer.PackerPublisher.perform(PackerPublisher.java:301) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1752) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Feb 23, 2018 12:39:25 PM biz.neustar.jenkins.plugins.packer.PackerPublisher perform SEV
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Nicolas De Loof commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Chisel Wright no, this just means docker runtime has some issues, and some are fixed in recent releases. docker-workflow-plugin uses docker CLI and expect it to run by the reference documentation. 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-19465) Slave hangs while being launched
Title: Message Title Ovidiu-Florin Bogdan reopened an issue This issue is still happening on SSH slaves 1.25.1 with Jenkins 2.89.3. The curious thing is that I only see it on one of our slaves. Jenkins / JENKINS-19465 Slave hangs while being launched Change By: Ovidiu-Florin Bogdan Resolution: Fixed Status: Resolved Reopened 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+uns
[JIRA] (JENKINS-19465) Slave hangs while being launched
Title: Message Title Ovidiu-Florin Bogdan commented on JENKINS-19465 Re: Slave hangs while being launched I"m still seeing this issue in SSh slaves plugin 1.25.1 with Jenkins 2.89.3. 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-49714) Set skipDefaultCheckout to false when using lightweight checkout for Jenkinsfile
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-49714 Set skipDefaultCheckout to false when using lightweight checkout for Jenkinsfile Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2018-02-23 11:16 Environment: Jenkins ver. 2.89.3 Priority: Minor Reporter: Karl Wirth If 'skipDefaultCheckout' option is not included in Jenkinsfile pipeline definition then pipeline job will trigger a full SCM checkout. This makes no sense when lightweight checkout has been ticked because the user only wants the Jenkinsfile(s). Would be good if 'skipDefaultCheckout(false)' is the default when using lightweight checkout or provide a tick box on the job configuration page to set it (under 'Lightweight checkout' tick-box). Add Comment
[JIRA] (JENKINS-46253) Support subPath for volumes in the slave PodTemplates
Title: Message Title Daniel Majano commented on JENKINS-46253 Re: Support subPath for volumes in the slave PodTemplates I'm facing to the same issue. It would be very top! 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-49278) cat command in docker agents not detected correctly
Title: Message Title Chisel Wright commented on JENKINS-49278 Re: cat command in docker agents not detected correctly My earlier comment was missing the version and OS - sorry. 17.12.0-ce on Centos/AWS (2017.09) 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-49502) trigger properties in scripted pipeline require 2 builds to get registered
Title: Message Title valentina armenise commented on JENKINS-49502 Re: trigger properties in scripted pipeline require 2 builds to get registered Andrew Bayer sorry for the late. core 2.89 workflow-job 2.17 workflow-multibranch NA (not installed in my tests) 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-49278) cat command in docker agents not detected correctly
Title: Message Title Thomas Johansen commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Chisel Wright: The problem seems to be isolated to Docker for Windows. I don't have the problem on 17.12 on Ubuntu. 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-49278) cat command in docker agents not detected correctly
Title: Message Title Chisel Wright commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Does this mean the docker-workflow-plugin has been updated to (silently?) require non-Stable versions of Docker? 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-45572) GitBlamer does not work if git workspace is in subfolder
Title: Message Title
Christian Häussler reopened an issue
The issue is not resolved. Job-Log: 23.02.2018 10:54:36 Using GitBlamer to create author and commit information for all warnings. 23.02.2018 10:54:36 Getting blame results for all files in E:\SCM/WKS/hus/HUS GEVO Glas. 23.02.2018 10:54:36 > E:\Software\Git-2.9.2\cmd\git.exe rev-parse "1ff17b3847091fe15639bda58069530615ecdad1^{commit}" # timeout=10 23.02.2018 10:54:36 ERROR: Build step failed with exception 23.02.2018 10:54:36 hudson.plugins.git.GitException: Command "E:\Software\Git-2.9.2\cmd\git.exe rev-parse "1ff17b3847091fe15639bda58069530615ecdad1^{commit}"" returned status code 128: {{23.02.2018 10:54:36 stdout: }} 23.02.2018 10:54:36 stderr: fatal: Not a git repository (or any of the parent directories): .git {{23.02.2018 10:54:36 }} 23.02.2018 10:54:36 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1903) 23.02.2018 10:54:36 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1871) 23.02.2018 10:54:36 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1867) 23.02.2018 10:54:36 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1512) 23.02.2018 10:54:36 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1524) 23.02.2018 10:54:36 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:718) 23.02.2018 10:54:36 at hudson.plugins.git.GitAPI.revParse(GitAPI.java:316) 23.02.2018 10:54:36 at hudson.plugins.analysis.util.GitBlamer.getHead(GitBlamer.java:70) 23.02.2018 10:54:36 at hudson.plugins.analysis.util.GitBlamer.loadBlameResultsForFiles(GitBlamer.java:58) 23.02.2018 10:54:36 at hudson.plugins.analysis.util.GitBlamer.blame(GitBlamer.java:52) 23.02.2018 10:54:36 at hudson.plugins.analysis.util.AbstractBlamer$1.invoke(AbstractBlamer.java:66) 23.02.2018 10:54:36 at hudson.plugins.analysis.util.AbstractBlamer$1.invoke(AbstractBlamer.java:63) 23.02.2018 10:54:36 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2731) 23.02.2018 10:54:36 at hudson.remoting.UserRequest.perform(UserRequest.java:153) 23.02.2018 10:54:36 at hudson.remoting.UserRequest.perform(UserRequest.java:50) 23.02.2018 10:54:36 at hudson.remoting.Request$2.run(Request.java:336) 23.02.2018 10:54:36 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 23.02.2018 10:54:36 at java.util.concurrent.FutureTask.run(Unknown Source) 23.02.2018 10:54:36 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 23.02.2018 10:54:36 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 23.02.2018 10:54:36 at hudson.remoting.Engine$1$1.run(Engine.java:94) 23.02.2018 10:54:36 at java.lang.Thread.run(Unknown Source) 23.02.2018 10:54:36 at ..remote call to JNLP4-connect connection from 10.131.142.143/10.131.142.143:50738(Native Method) 23.02.2018 10:54:36 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1545) 23.02.2018 10:54:36 at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) 23.02.2018 10:54:36 at hudson.remoting.Channel.call(Channel.java:830) 23.02.2018 10:54:36 at hudson.FilePath.act(FilePath.java:985) 23.02.2018 10:54:36 at hudson.FilePath.act(FilePath.java:974) 23.02.2018 10:54:36 at hudson.plugins.analysis.util.AbstractBlamer.invokeBlamer(AbstractBlamer.java:63) 23.02.2018 10:54:36 at hudson.plugins.analysis.util.AbstractBlamer.blame(AbstractBlamer.java:49) 23.02.2018 10:54:36 at hudson.plugins.analysis.core.HealthAwarePublisher.blame(HealthAwarePublisher.java:109) 23.02.2018 10:54:36 at hudson.plugins.tasks.TasksPublisher.perform(TasksPublisher.java:187) 23.02.2018 10:54:36 at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:69) 23.02.2018 10:54:36 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:298) 23.02.2018 10:54:36 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) 23.02.2018 10:54:36 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonito
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Thomas Johansen commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Chisel Wright: It's from the edge channel (https://download.docker.com/linux/static/edge/x86_64/). 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-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-49713 gerrit-plugin exposes change-requests as normal branches instead of pull-requests Issue Type: Bug Assignee: lucamilanesio Attachments: multibranch-github.png, mutibranch-gerrit.png Components: gerrit-plugin Created: 2018-02-23 10:24 Priority: Major Reporter: Sorin Sbarnea It seems that when using gerrit-plugin in combination with multibranch-pipelines, we get all discovered branches as normal branches instead of having them split between real-branches and temporary ones (pull-requests). I am attaching screenshots of a sample github repository and a gerrit sample repository, so it is clearly visible that multibranch-pipeline does treat CRs as branches instead of PRs (they are not displayed in their separated tab). This is also likely to affect the Blue Ocean gui too and it may be a real deal for users that do have lots of production branches and open pull requests. I know for sure that having 5-10 production branches and 5-50 open CRs is not uncommon.
[JIRA] (JENKINS-49712) Allow separate selection of categories for Failure thershold and Error threshold
Title: Message Title Jonathan Delizy created an issue Jenkins / JENKINS-49712 Allow separate selection of categories for Failure thershold and Error threshold Issue Type: Improvement Assignee: Marco Steffan Components: cppcheck-plugin Created: 2018-02-23 10:14 Priority: Minor Reporter: Jonathan Delizy Current version of plugin allow to set separate thresholds values to determine build status (Failure or Error) but this thresholds are computed against a unique set of categories. My proposal is to have separate sets of categories for Failure evaluation and Error evaluation. Add Comment
[JIRA] (JENKINS-49700) nested pod template in library doesn't work as documented
Title: Message Title Thorsten Kunz commented on JENKINS-49700 Re: nested pod template in library doesn't work as documented Are there any plans to fix the support for nested templates again? Specifically for the use in shared libraries this is an incredibly useful feature. You can just create a "standard" set of templates and then mix/match them easily in the Jenkinsfiles. 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-49278) cat command in docker agents not detected correctly
Title: Message Title Chisel Wright commented on JENKINS-49278 Re: cat command in docker agents not detected correctly 18.02? https://download.docker.com/linux/static/stable/x86_64/ has: Index of /linux/static/stable/x86_64/ ../ docker-17.03.0-ce.tgz 2017-03-01 11:11 27M docker-17.03.1-ce.tgz 2017-03-28 04:46 27M docker-17.03.2-ce.tgz 2017-06-28 03:35 27M docker-17.06.0-ce.tgz 2017-06-28 05:17 29M docker-17.06.1-ce.tgz 2017-08-18 02:35 29M docker-17.06.2-ce.tgz 2017-09-05 10:39 29M docker-17.09.0-ce.tgz 2017-09-27 01:47 29M docker-17.09.1-ce.tgz 2017-12-08 12:22 29M docker-17.12.0-ce.tgz 2017-12-27 09:52 33M 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-47855) Multiple parameterized builds at the same time
Title: Message Title
Eugeniu Z edited a comment on JENKINS-47855
Re: Multiple parameterized builds at the same time
The bug can be reproduced if the schedules are partially overlapping, e.g. {code} * * * * * % param=one*/2 * * * * % param=two {code} The job with param 'two' will not be executed.
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-47855) Multiple parameterized builds at the same time
Title: Message Title Eugeniu Z commented on JENKINS-47855 Re: Multiple parameterized builds at the same time The bug can be reproduced if the schedules are partially overlapping, e.g. * * * % param=one */2 * * * * % param=two The job with param 'two' will not be executed. 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-49278) cat command in docker agents not detected correctly
Title: Message Title Thomas Johansen commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Nicolas De Loof: Yep, I upgraded Docker for Windows to 18.02, and the problem is gone. Thanks! 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-49022) Performance plugin. Allow choosing percentiles to track
Title: Message Title Oleg Nenashev commented on JENKINS-49022 Re: Performance plugin. Allow choosing percentiles to track Hi all. If you see the serialization rejecting messages, please read https://jenkins.io/blog/2018/01/13/jep-200/ (linked from the stacktrace) There are reporting guidelines and the list of affected plugins 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-49669) readJSON returns non serializable JSON object
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49669 readJSON returns non serializable JSON object Change By: Oleg Nenashev Labels: JEP-200 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-49669) readJSON returns non serializable JSON object
Title: Message Title Oleg Nenashev commented on JENKINS-49669 Re: readJSON returns non serializable JSON object Thomas Mair Which version do you use? 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-49669) readJSON returns non serializable JSON object
Title: Message Title Oleg Nenashev edited a comment on JENKINS-49669 Re: readJSON returns non serializable JSON object IIUC it has been introduced by 2.102 as a part of the blacklist hardening: https://github.com/jenkinsci/remoting/pull/208Although it is not exactly JEP-200, I will mark it with this label so that people know about regressions **UPD**: Or maybe not 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-49669) readJSON returns non serializable JSON object
Title: Message Title Oleg Nenashev commented on JENKINS-49669 Re: readJSON returns non serializable JSON object IIUC it has been introduced by 2.102 as a part of the blacklist hardening: https://github.com/jenkinsci/remoting/pull/208 Although it is not exactly JEP-200, I will mark it with this label so that people know about regressions 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-49278) cat command in docker agents not detected correctly
Title: Message Title Nicolas De Loof commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Thomas Johansen sounds like a docker bug, maybe watch https://github.com/moby/moby/issues/34282 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-49711) EC2 Plugin: command prefix not stored
Title: Message Title Carles Amigó created an issue Jenkins / JENKINS-49711 EC2 Plugin: command prefix not stored Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2018-02-23 09:36 Environment: Jenkins 2.89.2 (inside docker container) Amazon EC2 plugin 1.38 Priority: Minor Reporter: Carles Amigó In Jenkins EC2 plugin, when setting the Root command prefix and Slave command prefix configuration, it works properly but it doesn't seem to be written in the config.xml file. After a while, this configuration disappears and it has to be set up again. I think this happens when Jenkins is restarted, but I haven't been able to confirm this. Add Comment
[JIRA] (JENKINS-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title Nicolas De Loof updated an issue Jenkins / JENKINS-49710 Pipelines run under heavy load sometimes hang running Docker Change By: Nicolas De Loof Component/s: docker-workflow-plugin Component/s: docker Component/s: pipeline 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-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title Nicolas De Loof assigned an issue to Unassigned Jenkins / JENKINS-49710 Pipelines run under heavy load sometimes hang running Docker Change By: Nicolas De Loof Assignee: Nicolas De Loof 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-49699) Doktor plugin affected by JEP-200
Title: Message Title Oleg Nenashev commented on JENKINS-49699 Re: Doktor plugin affected by JEP-200 The plugin is based on Gradle, so I cannot run PCT against it. It's also hard to say how many Kotlin libs we will need to whitelist in order to make it working. Currently there are 44 installations of the plugin, so for JEP-200 maintainers it has a low priority being compared to other affected plugins. For now I will leave it to Siarhei Krukau, happy to advice if needed. 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-49699) Doktor plugin affected by JEP-200
Title: Message Title Oleg Nenashev commented on JENKINS-49699 Re: Doktor plugin affected by JEP-200 My proposal would be to integrate the plugin with the new Kotlin STL Library plugin and to whitelist the required Kotlin classes on its side 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-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title malcolm crum created an issue Jenkins / JENKINS-49710 Pipelines run under heavy load sometimes hang running Docker Issue Type: Bug Assignee: Nicolas De Loof Components: docker, pipeline Created: 2018-02-23 09:02 Environment: Jenkins ver. 2.89.3 and 2.89.4, docker commons 1.11, docker pipeline 1.15.1 Priority: Minor Reporter: malcolm crum We have some load tests that run ~50 tests at a time overnight, in loops - so thousands of tests in a night. About 1% of them hang forever and must be manually killed. Jenkins log: Started by upstream project "tools/release-validator" build number 92 originally caused by: Started by timer Obtained Jenkinsfile from git [...] Running in Durability level: MAX_SURVIVABILITY Loading library TestRunner@master Attempting to resolve master from remote references... > git --version # timeout=10 > git ls-remote -h -t [...] # timeout=10 Found match: refs/heads/master revision 4f9f1287a87cedcccbe456d96176084fbfb2500c > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url [...] # timeout=10 Fetching without tags Fetching upstream changes from [...] > git --version # timeout=10 > git fetch --no-tags --progress [...] +refs/heads/*:refs/remotes/origin/* Checking out Revision 4f9f1287a87cedcccbe456d96176084fbfb2500c (master) > git config core.sparsecheckout # timeout=10 > git checkout -f 4f9f1287a87cedcccbe456d96176084fbfb2500c Commit message: "[...]" > git rev-list --no-walk 4f9f1287a87cedcccbe456d96176084fbfb2500c # timeout=10 [Pipeline] node Running on Jenkins i
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Thomas Johansen edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
[~ndeloof]: After upgrading to 1.15.1 I get this error in declarative pipeline:{noformat}java.io.IOException: Failed to run top '788913bdd127e9689e54cf2c699b0d99cc17e7469575bd4d541b4c61394c5ce4'. Error: Error response from daemon: Unexpected pid '111969kworker/u256:2': strconv.Atoi: parsing "111969kworker/u256:2": invalid syntax at org.jenkinsci.plugins.docker.workflow.client.DockerClient.listProcess(DockerClient.java:140) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:185){noformat} This happens on Docker for Windows 17.12.0-ce (Git commit c97c6d6).
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-49709) Proxy Config broken in Bitbucket Branch Source Plugin
Title: Message Title Thomas Kalmár updated an issue Jenkins / JENKINS-49709 Proxy Config broken in Bitbucket Branch Source Plugin Change By: Thomas Kalmár When getting the proxy config (for an Bitbucket server) the protocoll and port should be ignored.As a workaround i have to put the full host URL of the Server in the Proxy Exclusion list 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-49709) Proxy Config broken in Bitbucket Branch Source Plugin
Title: Message Title Thomas Kalmár commented on JENKINS-49709 Re: Proxy Config broken in Bitbucket Branch Source Plugin https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/112 should fix this 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-49709) Proxy Config broken in Bitbucket Branch Source Plugin
Title: Message Title Thomas Kalmár created an issue Jenkins / JENKINS-49709 Proxy Config broken in Bitbucket Branch Source Plugin Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-02-23 08:45 Priority: Minor Reporter: Thomas Kalmár When getting the proxy config the protocoll and port should be ignored. As a workaround i have to put the full host URL of the Server in the Proxy Exclusion list Add Comment This message was sent by Atlassian JIRA (v7.3.0#7
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Thomas Johansen commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Nicolas De Loof: After upgrading to 1.15.1 I get this error in declarative pipeline: java.io.IOException: Failed to run top '788913bdd127e9689e54cf2c699b0d99cc17e7469575bd4d541b4c61394c5ce4'. Error: Error response from daemon: Unexpected pid '111969kworker/u256:2': strconv.Atoi: parsing "111969kworker/u256:2": invalid syntax at org.jenkinsci.plugins.docker.workflow.client.DockerClient.listProcess(DockerClient.java:140) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:185) 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-49278) cat command in docker agents not detected correctly
Title: Message Title Michal Matyjek commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Seeing same as Chisel Wright and Danny Guinther - the original error message from the issue description. 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-49700) nested pod template in library doesn't work as documented
Title: Message Title Carlos Sanchez commented on JENKINS-49700 Re: nested pod template in library doesn't work as documented This started happening in 1.1.4 based on JENKINS-49366. The agreement seems to be that templates are not related to each other unless using inheritFrom Docs need to be updated 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.
