[JIRA] (JENKINS-59402) JobDsl should respect Job post-construction initialization
Title: Message Title Konstantin Bulanov created an issue Jenkins / JENKINS-59402 JobDsl should respect Job post-construction initialization Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2019-09-17 06:03 Environment: Jenkins 2.168/2.193 JobDsl plugin 1.72/1.77-SNAPSHOT Priority: Major Reporter: Konstantin Bulanov Hello! we currently faced the following issue. If we run the creation of job via jobDsl pipeline step (https://jenkins.io/doc/pipeline/steps/job-dsl/) with any parameters, we are getting a folder on our filesystem without "legacyIds" file in builds directory. examples are in the bottom of this post. The problem is that if there is no legacyIds file in builds directory, after restarting of jenkins server, we are facing long migrations for all jobs created after the previous reboot Examples: job created via jobDsl: [root@server]# ls -lah builds/jobDsl_job total 2.5K drwxr-xr-x 1 centos centos 808K Sep 12 07:23 . drwxr-xr-x 1 centos centos 3.1G Sep 12 07:21 .. drwxr-xr-x 1 centos centos 808K Sep 12 07:23 1 lrwxrwxrwx 1 centos centos 2 Sep 12 07:19 lastFailedBuild -> -1 lrwxrwxrwx 1 centos centos 1 Sep 12 07:23 lastStableBuild -> 1 lrwxrwxrwx 1 centos centos 1 Sep 12 07:23 lastSuccessfulBuild -> 1 lrwxrwxrwx 1 centos centos 2 Sep 12 07:19 lastUnstableBuild -> -1 lrwxrwxrwx 1 centos centos 2 Sep 12 07:19 lastUnsuccessfulBuild -> -1 job created via manual creation:
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Anda Sorina Laakso commented on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Can you also provide me the properties file? Thanks. 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.198392.1553542192000.4769.1568703300325%40Atlassian.JIRA.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Anda Sorina Laakso updated an issue Jenkins / JENKINS-56750 Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Change By: Anda Sorina Laakso Attachment: image-2019-09-17-10-11-01-078.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.198392.1553542192000.4779.1568704320664%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Maria Narcisa Galan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-59391 Micro Focus Application Automation Tools - Test is missing host name and execution fails to start Change By: Maria Narcisa Galan Assignee: Maria Narcisa Galan Anda Sorina Laakso 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.201948.1568640537000.4804.1568705760502%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Maria Narcisa Galan assigned an issue to Maria Narcisa Galan Jenkins / JENKINS-59391 Micro Focus Application Automation Tools - Test is missing host name and execution fails to start Change By: Maria Narcisa Galan Assignee: Roy Lu Maria Narcisa Galan 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.201948.1568640537000.4801.1568705760441%40Atlassian.JIRA.
[JIRA] (JENKINS-59403) agent fails immediately when started in a docker-compose cluster
Title: Message Title ravn created an issue Jenkins / JENKINS-59403 agent fails immediately when started in a docker-compose cluster Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2019-09-17 07:36 Priority: Minor Reporter: ravn I am trying to work with a master + some agents in a single docker cluster orchestrated by docker-compose with Jenkins ver. 2.176.3 under Windows 10 to experiment locally. Unfortunately the agents spin up much faster than the master, so they try to connect before the master is ready, which for a docker cluster results in a ConnectException (as the docker daemon handles the connect to the socket, but the instance is not ready yet). From my reading of the source the initial connect is not try-catch proctected for this, so the retry mechanism does not come into play. This means that in this case that all the agents fail at startup and has to be started manually afterwards. For my immediate purposes a "–wait" flag waiting X seconds when starting the agent will be fine (or similar), but perhaps the resilience mechanism needs to incoorporate this usecase too? ``` Sep 17, 2019 9:32:17 AM hudson.remoting.jnlp.Main$CuiListener statuscsr-jenkins-agent-base3_1 | INFO: Locating server among http://docker-images_csr-jenkins_1.local:8080csr-jenkins-agent-base3_1 | Sep 17, 2019 9:32:17 AM hudson.remoting.jnlp.Main$CuiListener errorcsr-jenkins-agent-base3_1 | SEVERE: Failed to connect to http://docker-images_csr-jenkins_1.local:8080/tcpSlaveAgentListener/: Connection refused (Connection refused) csr-jenkins-agent-base3_1 | java.io.IOException: Failed to connect to http://docker-images_csr-jenkins_1.local:8080/tcpSlaveAgentListener/: Connection refused (Connection refused) csr-jenkins-agent-base3_1 | at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:197) csr-jenkins-agent-base3_1 | at hudson.remoting.Engine.innerRun(Engine.java:523) csr-jenkins-agent-base3_1 | at
[JIRA] (JENKINS-59343) Trigger when changes in a specific directory
Title: Message Title
TJ Hoo updated an issue
Jenkins / JENKINS-59343
Trigger when changes in a specific directory
Change By:
TJ Hoo
I pushed the code changes directly to the master branch, by passing the code review.I have a repository which contains multiple directories.{code}dummy +- foo +- bar {code}I want to trigger the build only when there are changes in the foo directory, and here is how my trigger looks like in the Jenkinsfile:{code:groovy} triggers {gerrit( customUrl: '', gerritProjects: [[branches: [[ compareType: 'PLAIN', pattern: 'master']],filePaths: [[ compareType: 'ANT', pattern: "foo/**" ]],compareType: 'PLAIN',disableStrictForbiddenFileVerification: false,pattern: 'dummy' ]], serverName: 'dummy-gerrit', triggerOnEvents: [ changeMerged refUpdated () ]) }{code}Unfortunately the above doesn't work, the build is still triggered for all the files including the one changed in bar directory.Am I missing anything here?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59396) AWT initialized even with -Djava.awt.headless=true
Title: Message Title Julien Bréda updated an issue Jenkins / JENKINS-59396 AWT initialized even with -Djava.awt.headless=true Change By: Julien Bréda Summary: AWT initialized event even with -Djava.awt.headless=true 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.201953.1568647597000.4852.1568708400133%40Atlassian.JIRA.
[JIRA] (JENKINS-59404) High CPU usage in MapperBase.importFromFile in Benchmark Plugin
Title: Message Title Artalus S. created an issue Jenkins / JENKINS-59404 High CPU usage in MapperBase.importFromFile in Benchmark Plugin Issue Type: Bug Assignee: Daniel Mercier Attachments: cpu.png, Screenshot_2019-09-17_11-47-53.png Components: benchmark-plugin Created: 2019-09-17 08:53 Environment: Jenkins ver. 2.184 Benchmark 1.0.9 Priority: Major Reporter: Artalus S. Several days ago we've noticed that our Jenkins master had almost all its 12 core under 100% load. Apparently it's been that way for several days straight. Using Monitoring plugin we've figured out there was about 10 threads with tremendous amount of time spent in `java.util.TreeMap.put`. Killing those threads one by one didn't break anything, so we assumed it to be some strange jenkins quirk and went on. AFAIK stack traces weren't informative. Today I noticed there are 3 threads each eating 100% of core again. This time stack traces are more informative (see attachments). I cannot confirm that those two issues with CPU load are directly correlated, but the current one seems legit enough.
[JIRA] (JENKINS-59402) JobDsl should respect Job post-construction initialization
Title: Message Title
Konstantin Bulanov updated an issue
Jenkins / JENKINS-59402
JobDsl should respect Job post-construction initialization
Change By:
Konstantin Bulanov
Hello! we currently faced the following issue. If we run the creation of job via jobDsl pipeline step ([https://jenkins.io/doc/pipeline/steps/job-dsl/|https://www.google.com/url?q=https%3A%2F%2Fjenkins.io%2Fdoc%2Fpipeline%2Fsteps%2Fjob-dsl%2F=D=1=AFQjCNFphzzbQzcBk-KwGSGjshQxhQHIbw]) with any parameters, we are getting a folder on our filesystem without "*_legacyIds_*" file in builds directory. examples are in the bottom of this post. The problem is that if there is no *_legacyIds_* file in builds directory, after restarting of jenkins server, we are facing long migrations for all jobs created after the previous reboot Pull request with fix: [https://github.com/jenkinsci/job-dsl-plugin/pull/1203] *Examples*: job created via jobDsl:{code:java}[root@server]# ls -lah builds/jobDsl_jobtotal 2.5Kdrwxr-xr-x 1 centos centos 808K Sep 12 07:23 .drwxr-xr-x 1 centos centos 3.1G Sep 12 07:21 ..drwxr-xr-x 1 centos centos 808K Sep 12 07:23 1lrwxrwxrwx 1 centos centos 2 Sep 12 07:19 lastFailedBuild -> -1lrwxrwxrwx 1 centos centos 1 Sep 12 07:23 lastStableBuild -> 1lrwxrwxrwx 1 centos centos 1 Sep 12 07:23 lastSuccessfulBuild -> 1lrwxrwxrwx 1 centos centos 2 Sep 12 07:19 lastUnstableBuild -> -1lrwxrwxrwx 1 centos centos 2 Sep 12 07:19 lastUnsuccessfulBuild -> -1{code}job created via manual creation:{code:java}[root@server]# ls -lah builds/manual_jobtotal 0drwxr-xr-x 1 centos centos 0 Sep 12 07:21 .drwxr-xr-x 1 centos centos 3.1G Sep 12 07:21 ..-rw-r--r-- 1 centos centos 0 Sep 12 07:21 legacyIds{code}
Add Comment
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Anda Sorina Laakso commented on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Hi Jim, Since the patch solved the initial issue for this ticket, you should close this ticket and update the other ticket with all the details about the other issue. Thanks. 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.198392.1553542192000.4762.1568703180468%40Atlassian.JIRA.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Anda Sorina Laakso commented on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. As you can see in the attached image for the me the host name is present when selecting run on planed host option. Did you specify the host name in the "Advanced " section of the job configuration? Thanks. 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.198392.1553542192000.4793.1568704440377%40Atlassian.JIRA.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Anda Sorina Laakso commented on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. As you can see on the attach image for me the host name is not missing, Did you remember to add itin the "advanced" section? 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.198392.1553542192000.4786.1568704380267%40Atlassian.JIRA.
[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Wadeck Follonier commented on JENKINS-56578 Re: Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master Sorry Richard Bywater but I did not get any time to work on that issue, it's still in our backlog but not a priority yet. Avoiding using symlinks is a good strategy from my PoV. 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.198193.1552641703000.4840.1568707440221%40Atlassian.JIRA.
[JIRA] (JENKINS-58597) Additional Step error with message
Title: Message Title Paweł Cieślak commented on JENKINS-58597 Re: Additional Step error with message It would be helpful to have an option to print message directly to step log. 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.200755.1563785676000.4854.1568708760909%40Atlassian.JIRA.
[JIRA] (JENKINS-59393) Fix malformed XML in Atom and RSS 2.0 feeds
Title: Message Title Wadeck Follonier commented on JENKINS-59393 Re: Fix malformed XML in Atom and RSS 2.0 feeds Basil Crow very interesting piece of investigation, thank you very much for the contribution there Do you plan to provide a PR for this? We have a task in our backlog to work on the test coverage, so please, tell us if you are working on anything else in that area to avoid duplicate work 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.201950.1568644692000.4856.1568709120465%40Atlassian.JIRA.
[JIRA] (JENKINS-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline
Title: Message Title Jayshan Raghunandan commented on JENKINS-48897 Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline Could using personal access tokens help? https://confluence.atlassian.com/bitbucketserver/personal-access-tokens-939515499.html 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.187695.151567000.4868.1568710560786%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title cedric lecoz commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart ok tks, will try asap but that may not be before the WE, jenkins is slightly too busy during the week 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.199745.1559315049000.4829.1568706900844%40Atlassian.JIRA.
[JIRA] (JENKINS-59231) Improve test coverage on the RSS feature
Title: Message Title Wadeck Follonier commented on JENKINS-59231 Re: Improve test coverage on the RSS feature Please take into consideration job done by Basil Crow https://issues.jenkins-ci.org/browse/JENKINS-59393 as it seems he has discovered why the link tag was failing on the CI on the "temporary ignored new test case". 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.201688.1567615347000.4857.1568709180531%40Atlassian.JIRA.
[JIRA] (JENKINS-59402) JobDsl should respect Job post-construction initialization
Title: Message Title
Konstantin Bulanov updated an issue
Jenkins / JENKINS-59402
JobDsl should respect Job post-construction initialization
Change By:
Konstantin Bulanov
Hello! we currently faced the following issue. If we run the creation of job via jobDsl pipeline step ([https://jenkins.io/doc/pipeline/steps/job-dsl/|https://www.google.com/url?q=https%3A%2F%2Fjenkins.io%2Fdoc%2Fpipeline%2Fsteps%2Fjob-dsl%2F=D=1=AFQjCNFphzzbQzcBk-KwGSGjshQxhQHIbw]) with any parameters, we are getting a folder on our filesystem without "*_legacyIds_*" file in builds directory. examples are in the bottom of this post. The problem is that if there is no *_legacyIds_* file in builds directory, after restarting of jenkins server, we are facing long migrations for all jobs created after the previous reboot Pull request with fix: [https://github.com/jenkinsci/job-dsl-plugin/pull/ 1204|https://github.com/jenkinsci/job-dsl-plugin/pull/ 1203] *Examples*: job created via jobDsl:{code:java}[root@server]# ls -lah builds/jobDsl_jobtotal 2.5Kdrwxr-xr-x 1 centos centos 808K Sep 12 07:23 .drwxr-xr-x 1 centos centos 3.1G Sep 12 07:21 ..drwxr-xr-x 1 centos centos 808K Sep 12 07:23 1lrwxrwxrwx 1 centos centos 2 Sep 12 07:19 lastFailedBuild -> -1lrwxrwxrwx 1 centos centos 1 Sep 12 07:23 lastStableBuild -> 1lrwxrwxrwx 1 centos centos 1 Sep 12 07:23 lastSuccessfulBuild -> 1lrwxrwxrwx 1 centos centos 2 Sep 12 07:19 lastUnstableBuild -> -1lrwxrwxrwx 1 centos centos 2 Sep 12 07:19 lastUnsuccessfulBuild -> -1{code}job created via manual creation:{code:java}[root@server]# ls -lah builds/manual_jobtotal 0drwxr-xr-x 1 centos centos 0 Sep 12 07:21 .drwxr-xr-x 1 centos centos 3.1G Sep 12 07:21 ..-rw-r--r-- 1 centos centos 0 Sep 12 07:21 legacyIds{code}
Add Comment
[JIRA] (JENKINS-57123) Script Security Plugins latests version caused Jenkins 2.173 failed to start
Title: Message Title Vladimir Eremeev edited a comment on JENKINS-57123 Re: Script Security Plugins latests version caused Jenkins 2.173 failed to start Same situation here. Jenkins version 2.176.3Script Security plugin version 1.64 After routine plugin update Jenkins has started crashing on startup and showing exception, similar to one, provided in the bug description. I've searched for the errors and have found this bug report. Tried removing script-security plugin, and Jenkins has started.Then, I've tried installing script-security plugin version 1.64 and crashes appeared again. Update.Actually, crashes were caused by Active-choice plugin. It was recently updated from 2.1 to 2.2 I've found this by rolling back script-security plugin. All versions from 1.64 back to 1.50 have caused crash. That suggested that the cause was somewhere else. 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.198873.1555704698000.4746.1568700360340%40Atlassian.JIRA.
[JIRA] (JENKINS-59397) iOS upload timeout for large size of app
Title: Message Title Mez Pahlan commented on JENKINS-59397 Re: iOS upload timeout for large size of app Hi david huang What version of the plugin are you using? In version 0.3.1 we updated the write and connection timeouts to 60 seconds (which is the same as the old HockeyApp plugin). See JENKINS-58915. There are two other timeout values that we didn't change: read and call timeouts but we could update them to the same? If I get some time to do that would you be able to confirm on a pre-release build? 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.201954.1568661479000.4754.1568701920148%40Atlassian.JIRA.
[JIRA] (JENKINS-58292) Selenium is not getting referring
Title: Message Title balachandran mathialagan updated an issue Jenkins / JENKINS-58292 Selenium is not getting referring Change By: balachandran mathialagan URL: https://iam-mon.slb.nbndc.local/ in our prod env we are not able to execute the test cases post the selenium upgrade (not sure it automatically happen over weekend)E:\SSOAutomation\Testcases\SSO Health Check PSUP>pybot --exclude "Disabled" "SSO Health Check PSUP.txt"[ WARN ] Automatically parsing other than '*.robot' files is deprecated. Convert 'E:\SSOAutomation\Testcases\SSO Health Check PSUP\SSO Health Check PSUP.txt' to '*.robot' format or use '--extension' to explicitly configure which files to parse.[ ERROR ] Error in file 'E:\SSOAutomation\Testcases\SSO Health Check PSUP\resource.txt': Importing test library 'Selenium2Library' failed: ImportError: cannot import name PopenTraceback (most recent call last): File "build\bdist.win32\egg\Selenium2Library\__init__.py", line 19, in > File "build\bdist.win32\egg\SeleniumLibrary\__init__.py", line 27, in File "build\bdist.win32\egg\SeleniumLibrary\keywords\__init__.py", line 17, in File "build\bdist.win32\egg\SeleniumLibrary\keywords\alert.py", line 18, in odule> File "E:\SSOAutomation\Python27\lib\site-packages\selenium\webdriver\__init__.py", line 18, in from .firefox.webdriver import WebDriver as Firefox # noqa File "E:\SSOAutomation\Python27\lib\site-packages\selenium\webdriver\firefox\webdriver.py", line 31, in from .extension_connection import ExtensionConnection File "E:\SSOAutomation\Python27\lib\site-packages\selenium\webdriver\firefox\extension_connection.py", line 25, in from selenium.webdriver.firefox.firefox_binary import FirefoxBinary File "E:\SSOAutomation\Python27\lib\site-packages\selenium\webdriver\firefox\firefox_binary.py", line 21, in from subprocess import Popen, STDOUTPYTHONPATH: E:\SSOAutomation\Python27\lib\site-packages\robotframework_selenium2library-3.0.0-py2.7.egg E:\SSOAutomation\Python27\lib\site-packages\robotframework_seleniumlibrary-4.0.0a2.dev1-py2.7.egg E:\SSOAutomation\Python27\Lib\site-packages\robot C:\windows\system32\python27.zip E:\SSOAutomation\Python27\DLLs E:\SSOAutomation\Python27\lib E:\SSOAutomation\Python27\lib\plat-win E:\SSOAutomation\Python27\lib\lib-tk E:\SSOAutomation\Python27 E:\SSOAutomation\Python27\lib\site-packages E:\SSOAutomation\Python27\lib\site-packages\wx-3.0-msw
[JIRA] (JENKINS-58292) Selenium is not getting referring
Title: Message Title balachandran mathialagan updated an issue Jenkins / JENKINS-58292 Selenium is not getting referring Change By: balachandran mathialagan Comment: pfb the pip list o/pE:\SSOAutomation\Python27\Lib\site-packages>pip install robotframework_selenium2library-3.0.0You are using pip version 7.0.1, however version 19.1.1 is available.You should consider upgrading via the 'pip install --upgrade pip' command.Collecting robotframework-selenium2library-3.0.0 Could not find a version that satisfies the requirement robotframework-selenium2library-3.0.0 (from versions: )No matching distribution found for robotframework-selenium2library-3.0.0E:\SSOAutomation\Python27\Lib\site-packages>pip listYou are using pip version 7.0.1, however version 19.1.1 is available.You should consider upgrading via the 'pip install --upgrade pip' command.decorator (4.0.10)docutils (0.12)pip (7.0.1)robotframework (3.1.2)robotframework-selenium2library (3.0.0)robotframework-seleniumlibrary (4.0.0a2.dev1)selenium (3.141.0)setuptools (16.0)urllib3 (1.25.3) 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
[JIRA] (JENKINS-59397) iOS upload timeout for large size of app
Title: Message Title Mez Pahlan commented on JENKINS-59397 Re: iOS upload timeout for large size of app For reference the Fastlane AppCenter plugin (written by Microsoft) has a default of 60 seconds timeout - via the Faraday Ruby HTTP client. So I'm reasonably happy with the value we've chosen. But happy to apply it to the other two places as a first 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.201954.1568661479000.4760.1568702460225%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Maria Narcisa Galan assigned an issue to Roy Lu Jenkins / JENKINS-59391 Micro Focus Application Automation Tools - Test is missing host name and execution fails to start Change By: Maria Narcisa Galan Assignee: Maria Narcisa Galan Roy Lu 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.201948.1568640537000.4777.1568704200368%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title
Daniel Beck commented on JENKINS-59145
Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
No useful output in that part of the log. As a next step, reproduce the reported problem and look for errors in your browser's web developer console, or related messages in the Jenkins log. Also, make sure you have configured a Jenkins URL ("Jenkins Location") in the global configuration, and that you access Jenkins using that URL. Go to /manage and check whether there are admin monitors showing. The one about having no Jenkins URL configured, or the one about a broken reverse proxy would be interesting.
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.201579.156710687.4820.1568706421947%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Daniel Beck commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Please also provide a list of installed and enabled plugins and their versions. 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.201579.156710687.4822.1568706422015%40Atlassian.JIRA.
[JIRA] (JENKINS-59316) Bug - java.lang.NullPointerException
Title: Message Title
Wadeck Follonier updated an issue
Jenkins / JENKINS-59316
Bug - java.lang.NullPointerException
Change By:
Wadeck Follonier
Jenkins automatically turned on this morning and the following error message is showing.h2. Stack trace {code: java }java .lang.NullPointerExceptionat hudson.security.TokenBasedRememberMeServices2.autoLogin(TokenBasedRememberMeServices2.java:164) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) at
[JIRA] (JENKINS-59316) Bug - java.lang.NullPointerException
Title: Message Title Wadeck Follonier commented on JENKINS-59316 Re: Bug - java.lang.NullPointerException Sarfraaz Patel Thank you for the report, we will look at this. 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.201866.1568197807000.4847.1568707920299%40Atlassian.JIRA.
[JIRA] (JENKINS-59393) Fix malformed XML in Atom and RSS 2.0 feeds
Title: Message Title Wadeck Follonier edited a comment on JENKINS-59393 Re: Fix malformed XML in Atom and RSS 2.0 feeds [~basil] very interesting piece of investigation, thank you very much for the contribution there :) - Do you plan to provide a PR for this? - Thank you for the PR :) We have a task in our backlog to work on the test coverage, so please, tell us if you are working on anything else in that area to avoid duplicate work :) 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.201950.1568644692000.4861.1568709780170%40Atlassian.JIRA.
[JIRA] (JENKINS-59394) Veracode Plugin configuration error
Title: Message Title Adrian Prieto updated an issue Jenkins / JENKINS-59394 Veracode Plugin configuration error Change By: Adrian Prieto Attachment: config.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.201951.1568644774000.4892.1568713440256%40Atlassian.JIRA.
[JIRA] (JENKINS-59301) Crowd 2 plugin not compatible with JDK11
Title: Message Title Adrien Lecharpentier commented on JENKINS-59301 Re: Crowd 2 plugin not compatible with JDK11 The good news is that we can totally reproduce this with mvn -Djenkins.version=2.176.3 hpi:run. I'm trying to see how I can fix this with a minimum of changes. 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.201849.156813782.4929.1568715720352%40Atlassian.JIRA.
[JIRA] (JENKINS-59404) High CPU usage in MapperBase.importFromFile in Benchmark Plugin
Title: Message Title Daniel Mercier commented on JENKINS-59404 Re: High CPU usage in MapperBase.importFromFile in Benchmark Plugin Hi Artalus, How big is the history of builds maintained for jobs? When accessing the result page, the plugin loads the result files for all builds in a multithreaded fashion. At the time, it uses all available threads minus a few to maintain standard operations. This loading depending on the size of the history of builds can reduce CPU availability on the computer until loading is complete. It was implemented to speed load the result page. I could add an option to select the number of threads being used. I am currently traveling but I can look into implementing the change next week. Otherwise, if you have the time, you can create your own custom branch and submit your proposed change. Let me know, 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.201962.1568710397000.4936.1568715960340%40Atlassian.JIRA.
[JIRA] (JENKINS-58292) Selenium
Title: Message Title balachandran mathialagan updated an issue Jenkins / JENKINS-58292 Selenium Change By: balachandran mathialagan Summary: Selenium is not getting referring 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.200357.1562033127000.5041.1568719680092%40Atlassian.JIRA.
[JIRA] (JENKINS-59316) Bug - java.lang.NullPointerException
Title: Message Title Sarfraaz Patel commented on JENKINS-59316 Re: Bug - java.lang.NullPointerException sue seems to have been resolved now, it was cause by the server having no space, 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.201866.1568197807000.4895.1568713560259%40Atlassian.JIRA.
[JIRA] (JENKINS-58292) Selenium is not getting referring
Title: Message Title balachandran mathialagan closed an issue as Fixed Jenkins / JENKINS-58292 Selenium is not getting referring Change By: balachandran mathialagan Status: Open Closed Resolution: Fixed 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.200357.1562033127000.4961.1568717460288%40Atlassian.JIRA.
[JIRA] (JENKINS-59406) Unable to open view with emoji and then a space at beginning of name
Title: Message Title Jesse Houghton created an issue Jenkins / JENKINS-59406 Unable to open view with emoji and then a space at beginning of name Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-17 10:57 Priority: Major Reporter: Jesse Houghton This appears to be caused by JENKINS-23349 When trying to open a View that has a name that starts with an emoji followed by a space e.g. "⇪ View Name" Jenkins returns to the main page and a null pointer exception is thrown in the logs i.e. the view cannot be opened. Exception: java.lang.NullPointerException at hudson.Util.rawEncode(Util.java:883) at hudson.model.View.getViewUrl(View.java:537) at hudson.model.View.getUrl(View.java:529) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at
[JIRA] (JENKINS-58292) Selenium is not getting referring
Title: Message Title balachandran mathialagan updated JENKINS-58292 Jenkins / JENKINS-58292 Selenium is not getting referring Change By: balachandran mathialagan Status: Open Fixed but Unreleased Resolution: Fixed Released As: na 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.200357.1562033127000.5009.1568718420910%40Atlassian.JIRA.
[JIRA] (JENKINS-38609) Shared libraries root to be specified in the PATH field
Title: Message Title
Yizhuan Yu commented on JENKINS-38609
Re: Shared libraries root to be specified in the PATH field
I submitted a fix to this, and have made a pull request (checks passed, pending merge), https://github.com/jenkinsci/workflow-cps-global-lib-plugin/pull/84 In this attempted fix, I added a "Library base path" (libBasePath) to "Global Pipeline Libraries" configuration, which is a relative path, e.g. common/subprojects/sharedlibs/, that will be added to the library path so that the library will be loaded from "${libBasePath}/src/*/.groovy", "${libBasePath}/vars/.groovy", "${libBasePath}/vars/.txt", "${libBasePath}/resources/". If blank, the library will be loaded from default location under project root of code repository "src/*/.groovy", "vars/.groovy", "vars/.txt", "resources/".
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.174800.1475162118000.5011.1568718422580%40Atlassian.JIRA.
[JIRA] (JENKINS-58292) Selenium is not getting referring
Title: Message Title balachandran mathialagan updated JENKINS-58292 Jenkins / JENKINS-58292 Selenium is not getting referring Change By: balachandran mathialagan Status: Fixed but Unreleased Closed 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.200357.1562033127000.5024.1568718480256%40Atlassian.JIRA.
[JIRA] (JENKINS-59405) Max retries exceeded with url: /api/python?tree=jobs%5Bname%2Ccolor%2Curl%5D
Title: Message Title
Miguel Pacheco created an issue
Jenkins / JENKINS-59405
Max retries exceeded with url: /api/python?tree=jobs%5Bname%2Ccolor%2Curl%5D
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-09-17 09:47
Environment:
Jenkins ver. 2.138.1
Priority:
Minor
Reporter:
Miguel Pacheco
Hi all, I am getting "Max retries exceeded with URL" during weekends when our builds run automatically. It seems the HTTP service is overloaded, but I cannot find a way to increase its parameters. Have you any idea? Thanks! 14:03:13:[MainThread]: DEBUG: Starting new HTTP connection (1):msycmp504.int.veritas.com:808014:03:23:[MainThread]: ERROR: Following error was met and ignored:HTTPConnectionPool(host='msycmp504.int.veritas.com', port=8080): Max retries exceeded with url: /api/python?tree=jobs%5Bname%2Ccolor%2Curl%5D (Caused byReadTimeoutError("HTTPConnectionPool(host='msycmp504.int.veritas.com',port=8080): Read timed out. (read timeout=10)",))14:03:23:[MainThread]: ERROR: Could not auto-detect last ELM : None
[JIRA] (JENKINS-58292) Selenium is not getting referring
Title: Message Title balachandran mathialagan assigned an issue to balachandran mathialagan Jenkins / JENKINS-58292 Selenium is not getting referring Change By: balachandran mathialagan Assignee: Rouke Broersma balachandran mathialagan 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.200357.1562033127000.4963.1568717520346%40Atlassian.JIRA.
[JIRA] (JENKINS-58292) Selenium is not getting referring
Title: Message Title balachandran mathialagan updated JENKINS-58292 Jenkins / JENKINS-58292 Selenium is not getting referring Change By: balachandran mathialagan Resolution: Fixed Status: Closed In Review 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.200357.1562033127000.4964.1568717580124%40Atlassian.JIRA.
[JIRA] (JENKINS-59301) Crowd 2 plugin not compatible with JDK11
Title: Message Title Adrien Lecharpentier commented on JENKINS-59301 Re: Crowd 2 plugin not compatible with JDK11 So, I have a problem. The context is loaded from Crowd Integration sources, which I have no access. This got me into looking into the library license, and I'm not sure if we are supposed to use it. Opening a INFRA ticket to discuss this. 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.201849.156813782.4992.1568718242676%40Atlassian.JIRA.
[JIRA] (JENKINS-58292) Selenium is not getting referring
Title: Message Title balachandran mathialagan updated JENKINS-58292 Jenkins / JENKINS-58292 Selenium is not getting referring Change By: balachandran mathialagan Status: In Review Progress 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.200357.1562033127000.4997.1568718300188%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Anda Sorina Laakso commented on JENKINS-59391 Re: Micro Focus Application Automation Tools - Test is missing host name and execution fails to start I think you forgot to mention the host where the tests will run. This was the only scenario in which i was able to reproduce this error. 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.201948.1568640537000.5049.1568720040659%40Atlassian.JIRA.
[JIRA] (TEST-175) Selenium
Title: Message Title balachandran mathialagan moved an issue test / TEST-175 Selenium Change By: balachandran mathialagan Project: Jenkins test Key: JENKINS TEST - 58292 175 Workflow: JNJira + In-Review Component/s: foo10 Component/s: selenium-plugin 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
[JIRA] (JENKINS-59316) Bug - java.lang.NullPointerException
Title: Message Title Wadeck Follonier commented on JENKINS-59316 Re: Bug - java.lang.NullPointerException Sarfraaz Patel thank you for the feedback, so I close this ticket and in case you encounter the same issue again, please reopen it 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.201866.1568197807000.4946.1568716620628%40Atlassian.JIRA.
[JIRA] (JENKINS-59316) Bug - java.lang.NullPointerException
Title: Message Title Wadeck Follonier closed an issue as Not A Defect Jenkins / JENKINS-59316 Bug - java.lang.NullPointerException Change By: Wadeck Follonier Status: Open Closed Resolution: Not A Defect 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.201866.1568197807000.4948.1568716620689%40Atlassian.JIRA.
[JIRA] (JENKINS-58292) Selenium is not getting referring
Title: Message Title balachandran mathialagan stopped work on JENKINS-58292 Change By: balachandran mathialagan Status: In Progress Open 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.200357.1562033127000.5008.1568718360518%40Atlassian.JIRA.
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title Radek Antoniuk commented on JENKINS-50181 Re: ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile Matt Sicker I am still experiencing this issue with ssh-credentials-plugin 1.17.2 / Jenkins 2.176.2, can this be re-opened? When I paste an SSH key without a password and without a newline after END OPENSSH PRIVATE KEY, I am getting this: [EnvInject] - Loading node environment variables. Building in workspace /opt/jenkins/workspace/tests/testssh [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-LjVbJNMcagCy/agent.130927 SSH_AGENT_PID=130929 [ssh-agent] Started. Running ssh-add (command line suppressed) Enter passphrase for /opt/jenkins/workspace/tests/testssh@tmp/private_key_4661922093191141579.key: ERROR: Failed to run ssh-add Finished: FAILURE When I update the key and put a newline, it works fine: Building in workspace /opt/jenkins/workspace/tests/testssh [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-LHBjsdVD6N7X/agent.130956 SSH_AGENT_PID=130958 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /opt/jenkins/workspace/tests/testssh@tmp/private_key_1585458568929474760.key (SSH CI key) [ssh-agent] Using credentials jenkins (SSH key used for Tomcat restarts) [testssh] $ /bin/sh -xe /tmp/jenkins2172743275862346783.sh + hostname ci $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 130958 killed; [ssh-agent] Stopped. Finished: SUCCESS Add Comment
[JIRA] (JENKINS-58292) Selenium is not getting referring
Title: Message Title balachandran mathialagan updated an issue Jenkins / JENKINS-58292 Selenium is not getting referring Change By: balachandran mathialagan Environment: in our prod env we are not able to execute the test cases post the selenium upgrade (not sure it automatically happen over weekend). attached the error n the description field na 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.200357.1562033127000.4996.1568718300145%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Anda Sorina Laakso commented on JENKINS-59391 Re: Micro Focus Application Automation Tools - Test is missing host name and execution fails to start Hi Jim, I have uploaded the fix for the host name issue and deleted the previous patch. Please install this new version of the plugin and let me know if the problem got fixed or not. Thank you. 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.201948.1568640537000.5062.1568721540452%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Anda Sorina Laakso edited a comment on JENKINS-59391 Re: Micro Focus Application Automation Tools - Test is missing host name and execution fails to start Hi Jim,I have uploaded the fix for the host name issue in dropbox and deleted the previous patch. Please install this new version of the plugin and let me know if the problem got fixed or not.Thank you. 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.201948.1568640537000.5064.1568721540479%40Atlassian.JIRA.
[JIRA] (JENKINS-58725) Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending.
Title: Message Title fen zhou commented on JENKINS-58725 Re: Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending. Is there any comment about this? 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.201018.1564479331000.5065.1568721540490%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Jim Sears commented on JENKINS-59391 Re: Micro Focus Application Automation Tools - Test is missing host name and execution fails to start Hi, Does the beta release 5.8.7 contain the patch fix? Jim 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.201948.1568640537000.5088.1568722500219%40Atlassian.JIRA.
[JIRA] (JENKINS-59404) High CPU usage in MapperBase.importFromFile in Benchmark Plugin
Title: Message Title
Artalus S. commented on JENKINS-59404
Re: High CPU usage in MapperBase.importFromFile in Benchmark Plugin
Hi Daniel. I am unsure that the problem we are experiencing is related to multithreaded file loading. There are several jobs with up to 1000 builds in history, but the ones that use Benchmark store about 100 builds. It seems to me that there are some thread getting stuck constantly reloading files – either this, or some files causing for (enContent : jsonObject.entrySet()) { ... this.builds.add(build); in importFromFile() to loop much more times that it should.
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.201962.1568710397000.5104.1568723820114%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Thanks Daniel Beck. Did you need me to make a ticket or did you already? 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.199434.155810265.5107.1568724120400%40Atlassian.JIRA.
[JIRA] (JENKINS-46375) vSphere template definition doesn't allow environment variables to be defined
Title: Message Title Fredrik Bruzelius edited a comment on JENKINS-46375 Re: vSphere template definition doesn't allow environment variables to be defined Sorry for the late reply, I've been out of office for a few days.I deployed the pre-release to our staging environment, and successfully managed to set both the Ws Cleanup node property as well as environment variables and tool locations. So AFAICS the change works out well. 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.184639.1503478575000.5159.1568726280179%40Atlassian.JIRA.
[JIRA] (JENKINS-46375) vSphere template definition doesn't allow environment variables to be defined
Title: Message Title Fredrik Bruzelius commented on JENKINS-46375 Re: vSphere template definition doesn't allow environment variables to be defined Sorry for the late reply, I've been out of office for a few days. I deployed the pre-release to our staging environment, and successfully managed to set both the Ws Cleanup property as well as environment variables and tool locations. So AFAICS the change works out well. 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.184639.1503478575000.5155.1568726221122%40Atlassian.JIRA.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Jim Sears updated an issue Jenkins / JENKINS-56750 Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Change By: Jim Sears Attachment: RunTestOnHostName.pptx 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.198392.1553542192000.5068.1568722260687%40Atlassian.JIRA.
[JIRA] (JENKINS-59394) Veracode Plugin configuration error
Title: Message Title Adrian Prieto updated an issue Jenkins / JENKINS-59394 Veracode Plugin configuration error Change By: Adrian Prieto Priority: Minor Major 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.201951.1568644774000.5092.1568722980166%40Atlassian.JIRA.
[JIRA] (JENKINS-54517) Broken links to gitea web UI in Jenkins job sidebar
Title: Message Title Jan Breuer commented on JENKINS-54517 Re: Broken links to gitea web UI in Jenkins job sidebar It seems to work for me. Probably fixed by https://github.com/jenkinsci/gitea-plugin/pull/10 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.195288.154160667.5094.1568723340188%40Atlassian.JIRA.
[JIRA] (JENKINS-52112) Private Gitea repositories are not visible
Title: Message Title Jan Breuer commented on JENKINS-52112 Re: Private Gitea repositories are not visible Works for me. Probably fixed by https://github.com/jenkinsci/gitea-plugin/pull/11 but nobody updated this issue? 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.191709.1529592502000.5100.1568723760560%40Atlassian.JIRA.
[JIRA] (JENKINS-59394) Veracode Plugin configuration error
Title: Message Title Adrian Prieto assigned an issue to Adrian Prieto Jenkins / JENKINS-59394 Veracode Plugin configuration error Change By: Adrian Prieto Assignee: Mike Bockus Adrian Prieto 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.201951.1568644774000.5114.1568724780143%40Atlassian.JIRA.
[JIRA] (JENKINS-59394) Veracode Plugin configuration error
Title: Message Title Adrian Prieto commented on JENKINS-59394 Re: Veracode Plugin configuration error Wrong configuration 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.201951.1568644774000.5115.1568724780157%40Atlassian.JIRA.
[JIRA] (JENKINS-59397) iOS upload timeout for large size of app
Title: Message Title david huang commented on JENKINS-59397 Re: iOS upload timeout for large size of app Hi Mez Pahlan, I am using 0.4.0. I would love to try the pre-release build once it is available. BTW, is it possible to add some more logs so it is clear about when it starts the upload and when it failed? Thanks. 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.201954.1568661479000.5169.1568727000112%40Atlassian.JIRA.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Jim Sears commented on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Hi Anda Sorina Laakso Before I close this ticket, may I ask two things from you? 1) Repeat your exercise but add the same test "GUITest100" so that you have three instances, [1], [2], [3]. And set the "Another Host" to be Host1, Host2, Host3. When you look at the results, the test report should say what test ran on which PC. Your example is reversed because you use the same host. 2) You asked if I populated the HostName but if I did, that would be inefficient. One Jenkins job runs 10 tests, each test on a different PC. If I set the HostName in the Jenkins job then I would have to set it to one PC. That means I would need 10 jobs, 1 for each PC to run one test. Please see attached PPT. 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.198392.1553542192000.5081.1568722440230%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Anda Sorina Laakso commented on JENKINS-59391 Re: Micro Focus Application Automation Tools - Test is missing host name and execution fails to start No it doesn't. The fix will be included in the next oficial release. 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.201948.1568640537000.5090.1568722680244%40Atlassian.JIRA.
[JIRA] (JENKINS-59394) Veracode Plugin configuration error
Title: Message Title Adrian Prieto closed an issue as Fixed Jenkins / JENKINS-59394 Veracode Plugin configuration error Change By: Adrian Prieto Status: In Progress Closed Resolution: Fixed 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.201951.1568644774000.5121.1568724840813%40Atlassian.JIRA.
[JIRA] (JENKINS-59394) Veracode Plugin configuration error
Title: Message Title Adrian Prieto started work on JENKINS-59394 Change By: Adrian Prieto Status: Open In Progress 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.201951.1568644774000.5116.1568724840334%40Atlassian.JIRA.
[JIRA] (JENKINS-59409) Please support logging stages that are tasked to a node
Title: Message Title David Olorundare edited a comment on JENKINS-59409 Re: Please support logging stages that are tasked to a node Hi Josh, please reassign this issue/task to someone else as I am not currently actively working on this project at the moment. (reach out to [~jvz] for more info)Thanks. 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.201969.1568735833000.5415.1568736300099%40Atlassian.JIRA.
[JIRA] (JENKINS-59397) iOS upload timeout for large size of app
Title: Message Title david huang updated an issue Jenkins / JENKINS-59397 iOS upload timeout for large size of app Change By: david huang When I try to upload an iOS app about 400MB to App center, the plugin returns a timeout error and upload failed. Error: Creating an upload resource. Upload resource successful. Uploading app to resource. Upload app unsuccessful. java.net.SocketTimeoutException: timeout io.jenkins.plugins.appcenter.AppCenterException: java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: timeout Build step 'Upload app to AppCenter' changed build result to FAILURE expect the plugin can upload a large size app without timeout error Please check the attached screenshot for the plugin settings 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
[JIRA] (JENKINS-59397) iOS upload timeout for large size of app
Title: Message Title david huang updated an issue Jenkins / JENKINS-59397 iOS upload timeout for large size of app Change By: david huang Attachment: Screen Shot 2019-09-17 at 3.27.46 PM.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.201954.1568661479000.5658.1568748540249%40Atlassian.JIRA.
[JIRA] (JENKINS-59406) Unable to open view with emoji and then a space at beginning of name
Title: Message Title Jesse Houghton commented on JENKINS-59406 Re: Unable to open view with emoji and then a space at beginning of name See https://github.com/jenkinsci/jenkins/pull/4204 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.201964.1568717826000.5666.1568749020052%40Atlassian.JIRA.
[JIRA] (JENKINS-2776) Show SuppressWarnings directives of PMD report
Title: Message Title Riski Shop commented on JENKINS-2776 Re: Show SuppressWarnings directives of PMD report Distributor Resmi iMove Asli | Diskon 50%, Beli 2 Bonus 1 iMove | Jual iMove Asli | Pusat iMove | Harga iMove | Alamat iMove | Distributor iMove | Penjual iMove | Di Jual iMove | Cod iMove | Antar Gratis iMove | Obat iMove | Obat Nyeri Sendi | Obat Persendihan | Agen Obat iMove | Promo Obat iMove | Pusat Obat iMove | Alamat Obat iMove | Distributor Obat iMove | Jual iMove Obat Nyeri Sendi Asli adalah suplemen untuk menjaga kesehatan sendi yang bisa diperoleh konsumen di Indonesia. Pada dasarnya iMove adalah produk suplemen, bukan obat, yang banyak digunakan untuk mengatasi nyeri sendi atau artritis, khususnya osteoartritis (OA). Selain bisa mengurangi rasa sakit pada sendi yang dialami karena radang, iMove juga bisa mengatasi kekakuan sendi. Dokter tulang sering meresepkan suplemen semacam ini di samping fisioterapi. Tubuh kita tersusun dari banyak sekali sendi, lebih dari 200, dan semua sendi merupakan struktur yang rumit. Tidak mudah untuk selalu menjaga sendi-sendi itu dalam kondisi yang baik, dan faktor usia juga berpengaruh besar. Jika sendi kita tidak berfungsi sebagaimana mestinya, maka kita segera mengetahuinya karena sendi terasa kaku, tidak nyaman, dan terkadang nyeri. Nutrisi berperan penting dalam menjaga kesehatan semua sendi, dan iMove Supplement dibuat untuk menunjang kesehatannya dari berbagai tingkatan. iMove Joint Supplement adalah suplemen sendi yang berguna untuk membantu mengatasi radang pada persedian dan memperbaiki kesehatannya. iMove mampu meredakan rasa kaku dan sakit pada sendi, melumasi sendi untuk membantu mobilitas, serta menghambat kerusakan tulang rawan pada persendian. Jual IMove Obat Nyeri Sendi Asli / Apa Itu Kandungan IMove…? iMove – dasar tindakan Dasar tindakan pencegahan artritis yang biasa dianjurkan misalnya diet atau menurunkan berat tubuh, menjaga supaya daerah di sekitar sendi tidak mengalami cedera, dan melindungi bagian tubuh yang rentan mengalami artritis. Kaum wanita umumnya menderita osteoartritis pada lutut, sementara kaum pria banyak mengalaminya di bagian leher, paha, atau pergelangan tangan. Bila sudah terlanjur menderita artritis, dasar-dasar tindakan selanjutnya yang diresepkan oleh dokter spesialis ortopedi mengacu pada tingkat keparahan yang diderita pasien. Semua dokter ahli sepakat bahwa osteoartritis adalah penyakit degeneratif dan tidak ada obatnya, sama halnya dengan penuaan. Namun, selain berfungsi memelihara kondisi semua sendi tubuh, asupan makanan dan suplemen yang mengandung nutrisi tertentu bisa mempertahankan kondisi sendi yang rusak supaya tidak memburuk. Sambil mengikuti program terapi fisik yang disarankan dokter, konsumsi suplemen seperti iMove bisa banyak menolong penderita artritis. iMove dikatakan mampu secara efektif meredakan nyeri dan mengatasi rasa kaku pada sendi. Egi M. – umur 49 tahun Imove memang produk yang hebat dan saya merasakan manfaatnya. Beberapa tahun yang lalu, dokter saya mengatakan bahwa pinggul saya mungkin perlu diganti secepatnya. Sampai saat ini saya masih tetap bertahan dengan minum Imove setiap hari dan menyemprotkan minyak magnesium di pinggul saya, tidak lagi memikirkan untuk melakukan operasi. Produk yang luar biasa, terima kasih banyak. Desi – umur 58 tahun Setelah menderita sakit punggung bagian bawah dan sakit lutut kronis selama bertahun-tahun, saya mulai minum tablet I Move buatan perusahaan ini. Sebelumnya saya sudah mencoba bermacam macam cara pengobatan, tapi manfaat berarti hanya dirasakan setelah minum I Move. Sudah minum selama 3 minggu sekarang, dan rasanya keadaan saya lebih baik. Semoga semakin hari
[JIRA] (JENKINS-59288) Not able to connect to RobotFramework-SikuliLibrary
Title: Message Title Anthony Le updated an issue Jenkins / JENKINS-59288 Not able to connect to RobotFramework-SikuliLibrary Change By: Anthony Le Component/s: robot-plugin 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.201831.1568068192000.5240.1568734081585%40Atlassian.JIRA.
[JIRA] (JENKINS-42938) Agent build history does not show pipeline steps
Title: Message Title Josh Soref updated JENKINS-42938 Jenkins / JENKINS-42938 Agent build history does not show pipeline steps Change By: Josh Soref Resolution: Duplicate Status: Fixed but Unreleased Reopened 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.179949.1490017403000.5232.1568734022829%40Atlassian.JIRA.
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title Radek Antoniuk edited a comment on JENKINS-50181 Re: ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile OK, I debugged it a little and I think I know what the problem is: even though I modified the ssh-credentials plugin to save with a newline, it still didn't work for me. It turns out that the ssh-agent plugin that writes the private key to the file, strips it out of the newline. Then... ssh-add asks for a password. When I add a newline, it adds it to the agent fine. The question is now, what is stripping this private key newline ... I'll continue to debug but any hints appreciated. 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.189200.1521076967000.5321.1568735280276%40Atlassian.JIRA.
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title Radek Antoniuk commented on JENKINS-50181 Re: ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile OK, I debugged it a little and I think I know what the problem is: even though I modified the ssh-credentials plugin to save with a newline, it still didn't work for me. It turns out that the ssh-agent plugin that writes the private key to the file, strips it out of the newline. Then... ssh-add asks for a password. When I add a newline, it adds it to the agent fine. The question is now, what is stripping this private key... 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.189200.1521076967000.5311.1568735220461%40Atlassian.JIRA.
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title Matt Sicker commented on JENKINS-50181 Re: ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile Is that a separate issue? And can you reproduce this with a unit test? See the original PR for example. 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.189200.1521076967000.5293.1568734680360%40Atlassian.JIRA.
[JIRA] (JENKINS-59409) Please support logging stages that are tasked to a node
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59409 Please support logging stages that are tasked to a node Issue Type: Improvement Assignee: David Olorundare Components: audit-log-plugin Created: 2019-09-17 15:57 Priority: Minor Reporter: Josh Soref JENKINS-38877 notes that the integrated build history doesn't include information about when build stages in pipeline jobs are run on nodes. It would be very helpful if the audit-log-plugin could, for each stage, log: job run stage (probably a path, or link or something) start time status end time Add Comment
[JIRA] (JENKINS-59410) any transitive dependency to spring, causing version conflict between shared libraries and jdk-tools plugin
Title: Message Title
tigran mnatsakanyan created an issue
Jenkins / JENKINS-59410
any transitive dependency to spring, causing version conflict between shared libraries and jdk-tools plugin
Issue Type:
Bug
Assignee:
Devin Nusbaum
Components:
jdk-tool-plugin
Created:
2019-09-17 15:58
Labels:
jenkins shared-groovy-libraries conflict groovy
Priority:
Major
Reporter:
tigran mnatsakanyan
If the shared library, has a transitive dependency to spring core, it is conflicting with spring jars coming from `jdk-tool` plugin. Example. Imagine a custom jar has a dependency on any of spring core components, ex `spring-context` 'com.company.component:library:1.0' --> `org.springframework:spring-context:4.3.8.RELEASE` And lets Imagine a groovy function inside a shared library. `doSomething.groovy` ``` @Grab('com.company.component:library:1.0') import com.company.component.SomeClass def call() { return SomeClass.doSomething() } ``` When `doSomething()` is being called from `Jenkinsfile`, everything constantly crashes with `java.lang.NoSuchMethodError`. That is because, instead of loading transitive dependencies for spring `4.3.8.RELEASE`, a classloader is loading an old `2.5.6` version of spring classes from `jdk-tool` plugin under `$JENKINS_HOME/war/WEB_INF/lib/spring-*2.5.6.jar` Apparently, at the time of method execution, classloader is confused because `jdk-tool` plugin is loaded by default with old spring version. I do see grape downloading correct version of jars to $JENKINS_HOME/.groovy. However, after some debug prints ( with help of https://support.cloudbees.com/hc/en-us/articles/360004592631-What-Plugin-is-providing-this-class- ), it is visible that the classloader is ignoring the version there, and is loading from jdk-tools plugin's jars. Is there any known
[JIRA] (JENKINS-59386) Script Security 1.64 blocking Jenkins startup
Title: Message Title Devin Nusbaum commented on JENKINS-59386 Re: Script Security 1.64 blocking Jenkins startup Csaba Berta Neither of those exceptions seem related to script-security at a glance. Do you have any other reason to believe that the problem you are seeing is related to script-security? I am surprised that you were able to restart Jenkins after disabling script-security, I would have thought that Jenkins startup would fail because of unsatisfied dependencies. Do you see any other warnings in your Jenkins logs at startup, or are the screenshots you posted the only warnings you are seeing? 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.201942.1568622824000.5363.1568735941522%40Atlassian.JIRA.
[JIRA] (JENKINS-59410) any transitive dependency to spring, causing version conflict between shared libraries and jdk-tools plugin
Title: Message Title tigran mnatsakanyan updated an issue Jenkins / JENKINS-59410 any transitive dependency to spring, causing version conflict between shared libraries and jdk-tools plugin Change By: tigran mnatsakanyan Component/s: pipeline 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.201970.1568735892000.5360.1568735941488%40Atlassian.JIRA.
[JIRA] (JENKINS-59410) any transitive dependency to spring, causing version conflict between shared libraries and jdk-tools plugin
Title: Message Title
tigran mnatsakanyan updated an issue
Jenkins / JENKINS-59410
any transitive dependency to spring, causing version conflict between shared libraries and jdk-tools plugin
Change By:
tigran mnatsakanyan
If the shared library, has a transitive dependency to spring core, it is conflicting with spring jars coming from `jdk-tool` plugin.Example.Imagine a custom jar has a dependency on any of spring core components, ex `spring-context`{noformat}com.company.component:library:1.0' --> `org.springframework:spring-context:4.3.8.RELEASE{noformat} And let's Imagine a groovy function inside a shared library.{ noformat code:java } {code:title= doSomething.groovy {noformat |borderStyle=solid } {code:java} @Grab('com.company.component:library:1.0')import com.company.component.SomeClassdef call(){ return SomeClass.doSomething() }{code} When doSomething() is being called from Jenkinsfile, everything constantly crashes with java.lang.NoSuchMethodError. [cloud bees forum|[https://support.cloudbees.com/hc/en-us/articles/360004592631-What-Plugin-is-providing-this-class-]] That is because, instead of loading transitive dependencies for spring `4.3.8.RELEASE`, a classloader is loading an old `2.5.6` version of spring classes from `jdk-tool` plugin under{noformat}$JENKINS_HOME/war/WEB-INF/lib/spring-*2.5.6.jar{noformat} Apparently, at the time of method execution, classloader is confused because `jdk-tool` plugin is loaded by default with old spring version. I do see grape downloading correct version of jars to $JENKINS_HOME/.groovy. However, after some debug prints ( with help of [ cloud bees cloudbees- forum|[https://support.cloudbees.com/hc/en-us/articles/360004592631-What-Plugin-is-providing-this-class-]] ), it is visible that the classloader is ignoring the version there, and is loading from jdk-tools plugin's jars. Is there any known workaround, or possible fix to issue?
Add Comment
[JIRA] (JENKINS-59397) iOS upload timeout for large size of app
Title: Message Title david huang commented on JENKINS-59397 Re: iOS upload timeout for large size of app update stack trace: Creating an upload resource. io.jenkins.plugins.appcenter.AppCenterException: Create upload resource unsuccessful: at io.jenkins.plugins.appcenter.task.internal.CreateUploadResourceTask.lambda$execute$0(CreateUploadResourceTask.java:48) at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760) at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at retrofit2.CompletableFutureCallAdapterFactory$BodyCallAdapter$2.onFailure(CompletableFutureCallAdapterFactory.java:86) at retrofit2.OkHttpCall$1.callFailure(OkHttpCall.java:141) at retrofit2.OkHttpCall$1.onFailure(OkHttpCall.java:136) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:215) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.net.UnknownHostException: api.appcenter.ms: unknown error at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928) at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323) at java.net.InetAddress.getAllByName0(InetAddress.java:1276) at java.net.InetAddress.getAllByName(InetAddress.java:1192) at java.net.InetAddress.getAllByName(InetAddress.java:1126) at okhttp3.Dns$1.lookup(Dns.java:40) at okhttp3.internal.connection.RouteSelector.resetNextInetSocketAddress(RouteSelector.java:185) at okhttp3.internal.connection.RouteSelector.nextProxy(RouteSelector.java:149) at okhttp3.internal.connection.RouteSelector.next(RouteSelector.java:84) at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:214) at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:135) at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:114) at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:126) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at io.jenkins.plugins.appcenter.api.AppCenterServiceFactory.lambda$createAppCenterService$0(AppCenterServiceFactory.java:66) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.logging.HttpLoggingInterceptor.intercept(HttpLoggingInterceptor.java:225) at
[JIRA] (JENKINS-49121) Ability to skip stages and preserve build history
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-49121 Ability to skip stages and preserve build history Change By: Josh Soref It would be nice, when you can skip single stages in a pipeline withut loosing without losing the build history in the visualization.At the moment I have two choices:* Skip the complete stage: The whole build history in the visualization will be lost.* Execute the stage but not the content: The build history is preserved, but the stage color will be the same as the rest of the stage. It should be clear, that the stage content wasn't executed. Maybe there could be a step to set the stage status and so change the color of the stage (just an idea). 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
[JIRA] (JENKINS-59410) any transitive dependency to spring, causing version conflict between shared libraries and jdk-tools plugin
Title: Message Title
tigran mnatsakanyan updated an issue
Jenkins / JENKINS-59410
any transitive dependency to spring, causing version conflict between shared libraries and jdk-tools plugin
Change By:
tigran mnatsakanyan
If the shared library, has a transitive dependency to spring core, it is conflicting with spring jars coming from `jdk-tool` plugin.Example.Imagine a custom jar has a dependency on any of spring core components, ex `spring-context`{noformat}com.company.component:library:1.0' --> `org.springframework:spring-context:4.3.8.RELEASE{noformat} And let's Imagine a groovy function inside a shared library.{noformat}doSomething.groovy{noformat}{code:java}@Grab('com.company.component:library:1.0')import com.company.component.SomeClassdef call(){ return SomeClass.doSomething() }{code} When doSomething() is being called from Jenkinsfile, everything constantly crashes with java.lang.NoSuchMethodError. That is because, instead of loading transitive dependencies for spring `4.3.8.RELEASE`, a classloader is loading an old `2.5.6` version of spring classes from `jdk-tool` plugin under{noformat}$JENKINS_HOME/war/WEB-INF/lib/spring-*2.5.6.jar{noformat} [link title|http://example.com] Apparently, at the time of method execution, classloader is confused because `jdk-tool` plugin is loaded by default with old spring version. I do see grape downloading correct version of jars to $JENKINS_HOME/.groovy. However, after some debug prints ( with help of [cloudbees-forum|[https://support.cloudbees.com/hc/en-us/articles/360004592631-What-Plugin-is-providing-this-class-]] ), it is visible that the classloader is ignoring the version there, and is loading from jdk-tools plugin's jars. Is there any known workaround, or possible fix to issue?
Add Comment
[JIRA] (JENKINS-59410) any transitive dependency to spring, causing version conflict between shared libraries and jdk-tools plugin
Title: Message Title
tigran mnatsakanyan updated an issue
Jenkins / JENKINS-59410
any transitive dependency to spring, causing version conflict between shared libraries and jdk-tools plugin
Change By:
tigran mnatsakanyan
If the shared library, has a transitive dependency to spring core, it is conflicting with spring jars coming from `jdk-tool` plugin.Example.Imagine a custom jar has a dependency on any of spring core components, ex `spring-context` {noformat} ' com.company.component:library:1.0' --> `org.springframework:spring-context:4.3.8.RELEASE ` {noformat} And lets let's Imagine a groovy function inside a shared library. {noformat} ` doSomething.groovy ` {noformat} {code:java} ``` @Grab('com.company.component:library:1.0') import com.company.component.SomeClassdef call() { { return SomeClass.doSomething() } {code } ``` When ` doSomething() ` is being called from ` Jenkinsfile ` , everything constantly crashes with ` java.lang.NoSuchMethodError ` . That is because, instead of loading transitive dependencies for spring `4.3.8.RELEASE`, a classloader is loading an old `2.5.6` version of spring classes from `jdk-tool` plugin under ` {noformat} $JENKINS_HOME/war/ WEB_INF WEB-INF /lib/spring-*2.5.6.jar ` {noformat} Apparently, at the time of method execution, classloader is confused because `jdk-tool` plugin is loaded by default with old spring version. I do see grape downloading correct version of jars to $JENKINS_HOME/.groovy. However, after some debug prints ( with help of [ cloudbees-forum|[ https://support.cloudbees.com/hc/en-us/articles/360004592631-What-Plugin-is-providing-this-class-] ] ), it is visible that the classloader is ignoring the version there, and is loading from jdk-tools plugin's jars. Is there any known workaround, or possible fix to issue?
Add Comment
[JIRA] (JENKINS-59409) Please support logging stages that are tasked to a node
Title: Message Title David Olorundare commented on JENKINS-59409 Re: Please support logging stages that are tasked to a node Hi Josh, please reassign this issue/task to someone else as I am not currently working on this project at the moment. Thanks. 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.201969.1568735833000.5388.1568736180934%40Atlassian.JIRA.
[JIRA] (JENKINS-59411) Multibranch Pipeline job cannot be triggered on push with Deploy Key to GHE repo
Title: Message Title Tim Tippens created an issue Jenkins / JENKINS-59411 Multibranch Pipeline job cannot be triggered on push with Deploy Key to GHE repo Issue Type: Bug Assignee: Kanstantsin Shautsou Components: github-integration-plugin, pipeline Created: 2019-09-17 16:02 Environment: CentOS Linux release 7.6.1810 (Core) - Master OS jdk1.8.0_121 Jenkins ver. 2.150.3 Pipeline: Multibranch v 2.21 Github plugin 1.29.4 GitHub Enterprise Server 2.17 Priority: Trivial Reporter: Tim Tippens We configure a github repo with a webhook to trigger a multibranch pipeline build on push (github-webhook/ (push)) and connect using the "branch sources" git integration and deploy keys with access to the repo. The push event is seen in the jenkins logs, but the multibranch pipeline job is not triggered. Nothing appears in the Multibranch Pipeline Events log. Only a manual rescan of the of the pipeline picks up changes to the repo, no matter which branch we push to (and "All branches get the same properties" is set). Add
[JIRA] (JENKINS-59397) iOS upload timeout for large size of app
Title: Message Title Mez Pahlan commented on JENKINS-59397 Re: iOS upload timeout for large size of app Can you update to the latest version please and try again. I don't think that will help on its own but the stack trace on error is better. Please paste that here. 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.201954.1568661479000.5484.1568738580286%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title John Rocha commented on JENKINS-54472 Re: Pin build at Perforce Label does not support variable expansion Any update on this issue? 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.195237.154144342.5486.1568738820098%40Atlassian.JIRA.
[JIRA] (JENKINS-25822) No more connections to slaves - no log - truncated command
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-25822 No more connections to slaves - no log - truncated command Change By: Josh Soref Summary: No more connections to slaves - no log - troncated truncated command 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.159397.1417169004000.5250.1568734203277%40Atlassian.JIRA.
[JIRA] (JENKINS-59409) Please support logging stages that are tasked to a node
Title: Message Title David Olorundare edited a comment on JENKINS-59409 Re: Please support logging stages that are tasked to a node Hi Josh, please reassign this issue/task to someone else as I am not currently working on this project at the moment. (reach out to [~jvz] for more info) Thanks. 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.201969.1568735833000.5409.1568736241311%40Atlassian.JIRA.
[JIRA] (JENKINS-59410) any transitive dependency to spring, causing version conflict between shared libraries and jdk-tools plugin
Title: Message Title
tigran mnatsakanyan updated an issue
Jenkins / JENKINS-59410
any transitive dependency to spring, causing version conflict between shared libraries and jdk-tools plugin
Change By:
tigran mnatsakanyan
If the shared library, has a transitive dependency to spring core, it is conflicting with spring jars coming from `jdk-tool` plugin.Example.Imagine a custom jar has a dependency on any of spring core components, ex `spring-context`{noformat}com.company.component:library:1.0' --> `org.springframework:spring-context:4.3.8.RELEASE{noformat} And let's Imagine a groovy function inside a shared library.{noformat}doSomething.groovy{noformat}{code:java}@Grab('com.company.component:library:1.0')import com.company.component.SomeClassdef call(){ return SomeClass.doSomething() }{code} When doSomething() is being called from Jenkinsfile, everything constantly crashes with java.lang.NoSuchMethodError. That is because, instead of loading transitive dependencies for spring `4.3.8.RELEASE`, a classloader is loading an old `2.5.6` version of spring classes from `jdk-tool` plugin under{noformat}$JENKINS_HOME/war/WEB-INF/lib/spring-*2.5.6.jar{noformat} [link title|http://example.com] Apparently, at the time of method execution, classloader is confused because `jdk-tool` plugin is loaded by default with old spring version. I do see grape downloading correct version of jars to $JENKINS_HOME/.groovy. However, after some debug prints ( with help of [ cloudbees- cloud bees forum|[https://support.cloudbees.com/hc/en-us/articles/360004592631-What-Plugin-is-providing-this-class-]] ), it is visible that the classloader is ignoring the version there, and is loading from jdk-tools plugin's jars. Is there any known workaround, or possible fix to issue?
Add Comment
[JIRA] (JENKINS-56340) Build-Publisher does not work with CloudBees Folders
Title: Message Title John Rocha commented on JENKINS-56340 Re: Build-Publisher does not work with CloudBees Folders Any update for this issue? 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.197925.1551401236000.5488.1568738880235%40Atlassian.JIRA.
[JIRA] (JENKINS-57721) remote jobs view shows last known status when remote server is unreachable
Title: Message Title John Rocha commented on JENKINS-57721 Re: remote jobs view shows last known status when remote server is unreachable Any update for this issue? 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.199664.1559067622000.5494.1568738940121%40Atlassian.JIRA.
