[JIRA] (JENKINS-54508) The false changes to true in config.xml if the value of the tag has been changed explicitly.
Title: Message Title Daniel Beck commented on JENKINS-54508 Re: The false changes to true in config.xml if the value of the tag has been changed explicitly. As I explained above, this file is not generally expected to be edited manually. You're changing internal data storage. There is no defined behavior here. If Jenkins still works after you edit this file, great. If it doesn't, you did something wrong. This file is not considered user API. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54508) The false changes to true in config.xml if the value of the tag has been changed explicitly.
Title: Message Title Kharad Variyava commented on JENKINS-54508 Re: The false changes to true in config.xml if the value of the tag has been changed explicitly. So Daniel Beck, are you trying to imply that this is an expected behavior??? Request a bit more clarity please!! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46938) Duplicate 'Reply' and 'Pipeline steps' links on side panel
Title: Message Title Wilm Schomburg commented on JENKINS-46938 Re: Duplicate 'Reply' and 'Pipeline steps' links on side panel I'm also dealing with that problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54508) The false changes to true in config.xml if the value of the tag has been changed explicitly.
Title: Message Title Daniel Beck updated JENKINS-54508 Please leave this issue closed. This is not a bug. Jenkins / JENKINS-54508 The false changes to true in config.xml if the value of the tag has been changed explicitly. Change By: Daniel Beck Status: In Review Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54508) The false changes to true in config.xml if the value of the tag has been changed explicitly.
Title: Message Title Daniel Beck commented on JENKINS-54508 Re: The false changes to true in config.xml if the value of the tag has been changed explicitly. can you please share the link to the documentation explaining how to unlock a Jenkins you can no longer access You describe how to do that in steps 1-4. it needs a re-look, as this might lead to a security breach going forward Which can be done through the UI after following the steps you describe. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54508) The false changes to true in config.xml if the value of the tag has been changed explicitly.
Title: Message Title Kharad Variyava commented on JENKINS-54508 Re: The false changes to true in config.xml if the value of the tag has been changed explicitly. Daniel Beck - can you please share the link to the documentation explaining how to unlock a Jenkins you can no longer access?? However, the steps mentioned above are widely mentioned across all the major forums as well..so I guess, it needs a re-look, as this might lead to a security breach going forward!! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54508) The false changes to true in config.xml if the value of the tag has been changed explicitly.
Title: Message Title Kharad Variyava updated JENKINS-54508 Jenkins / JENKINS-54508 The false changes to true in config.xml if the value of the tag has been changed explicitly. Change By: Kharad Variyava Status: Closed In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54508) The false changes to true in config.xml if the value of the tag has been changed explicitly.
Title: Message Title Daniel Beck closed an issue as Not A Defect While we have documentation explaining how to unlock a Jenkins you can no longer access due to invalid security setup in an emergency, this file is not generally expected to be edited manually. You're changing internal data storage. Jenkins / JENKINS-54508 The false changes to true in config.xml if the value of the tag has been changed explicitly. Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54508) The false changes to true in config.xml if the value of the tag has been changed explicitly.
Title: Message Title Oleg Nenashev moved an issue Jenkins / JENKINS-54508 The false changes to true in config.xml if the value of the tag has been changed explicitly. Change By: Oleg Nenashev Project: Infrastructure Jenkins Key: INFRA JENKINS - 1842 54508 Workflow: classic default workflow JNJira + In-Review Component/s: core Component/s: account Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54507) pipeline_data is not pushing to influxdb
Title: Message Title Mohamed Nazeer Mohamed Ibrahim created an issue Jenkins / JENKINS-54507 pipeline_data is not pushing to influxdb Issue Type: Bug Assignee: Aleksi Simell Components: influxdb-plugin Created: 2018-11-07 06:25 Environment: Jenkins Version 2.107 InfluxDB Plugin version 1.20 Priority: Major Reporter: Mohamed Nazeer Mohamed Ibrahim We are not able to get the Pipeline data such as "stage durations", "steps executed"... Influxdb plug in not collecting and pushing these data. We are using influxdb plugin as step execution in our pipeline as below step([$class: 'InfluxDbPublisher', customData: myDataMap, customDataMap: mycustomdatamap, customPrefix: null, target: 'My Target', jenkinsEnvParameterTag: 'build_number=' + env.BUILD_NUMBER]) Add Comment
[JIRA] (JENKINS-54486) Jira create issue to created for last completed build result in jenkins job not created according to last build failed
Title: Message Title Betul Aslan assigned an issue to Unassigned Jenkins / JENKINS-54486 Jira create issue to created for last completed build result in jenkins job not created according to last build failed Change By: Betul Aslan Assignee: Kalyanram Adiraju Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54466) HPIs should be renamed JPIs after download
Title: Message Title Baptiste Mathus commented on JENKINS-54466 Re: HPIs should be renamed JPIs after download Almost there FTR. Fixing a few tests here and there that were expecting .hpi. Slightly more than just replaceAll, since we actually want to detect if someone put an hpi by hand for instance, and not just ignore these files when reporting versions for example. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54466) HPIs should be renamed JPIs after download
Title: Message Title Baptiste Mathus commented on JENKINS-54466 Re: HPIs should be renamed JPIs after download Also TODO: check that the core issues a warning if both .jpi and .hpi are present for a given plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53858) Deadlock on EC2 resources
Title: Message Title Perrin Morrow commented on JENKINS-53858 Re: Deadlock on EC2 resources Using that snapshot causes a NullPointerException to be thrown as soon as the plugin tries to launch an instance: SEVERE: Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@6d31793d failed java.lang.NullPointerException at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:587) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:598) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) I think that's because slaveCountingLock is transient, so I added this line to readResolve() to reinitialise it after deserialisation: slaveCountingLock = new ReentrantLock(); It's now launching slaves OK in our staging environment but I wasn't able to reproduce the original deadlock problem there anyway. I'm going to try my build of the plugin in our live server (where we were seeing it many times a day) as soon as it's quiet enough to restart. Add Comment
[JIRA] (JENKINS-54382) Lightweight Checkout failure to find jenkinsfile when jenkinsfile is in a subfolder
Title: Message Title Alisdair Robertson commented on JENKINS-54382 Re: Lightweight Checkout failure to find jenkinsfile when jenkinsfile is in a subfolder Tested the snapshot build and the behaviour is now what I'd expect! Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54506) Some compiler warnings are misidentified as Javadoc warnings
Title: Message Title trejkaz created an issue Jenkins / JENKINS-54506 Some compiler warnings are misidentified as Javadoc warnings Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-11-07 02:12 Environment: Jenkins 2.149 Warnings Plugin 4.66 Priority: Minor Reporter: trejkaz We had warnings showing up still on Jenkins after changing our build over to treat all Javadoc warnings as errors. In investigating how that was possible, we found the following warning: [ImmutableEnumChecker] enums should be immutable: 'Type' has field 'mime' of type 'com.acme.MyEnumType', the declaration of type 'com.acme.MyEnumType' is not annotated with @com.google.errorprone.annotations.Immutable But that is coming from the Java compiler, or specifically from Error Prone, not from Javadoc. I assume it's because it happens to mention an annotation, which contains the @ typically also seen in Javadoc.
[JIRA] (JENKINS-48556) timestamps() randomly not recognized as a valid option
Title: Message Title Andrew Bayer commented on JENKINS-48556 Re: timestamps() randomly not recognized as a valid option That is a great catch - I'll get a pr up first thing tomorrow. Thank you very much for nailing that down! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46892) [pipeline] echo is spamming console logs - redundant
Title: Message Title Wolfgang Steiner commented on JENKINS-46892 Re: [pipeline] echo is spamming console logs - redundant I have the same problem ... I am reading streamed output from a long running HTTP request and want to print it line-by-line to the jenkins job console (in realtime). If I do it via println / echo then I end up with 3 lines printed by jenkins where it was originally one in the HTTP output, e.g.: [Pipeline] echo HELLO0 -> 2018-11-07 00:45:11.427218 [Pipeline] echo HELLO1 -> 2018-11-07 00:45:11.530216 [Pipeline] echo HELLO2 -> 2018-11-07 00:45:11.632216 [Pipeline] echo HELLO3 -> 2018-11-07 00:45:11.734223 [Pipeline] echo HELLO4 -> 2018-11-07 00:45:11.836223 [Pipeline] echo HELLO5 -> 2018-11-07 00:45:11.938223 [Pipeline] echo HELLO6 -> 2018-11-07 00:45:12.040216 whereas the server HTTP wrote: HELLO0 -> 2018-11-07 00:45:11.427218 HELLO1 -> 2018-11-07 00:45:11.530216 HELLO2 -> 2018-11-07 00:45:11.632216 HELLO3 -> 2018-11-07 00:45:11.734223 HELLO4 -> 2018-11-07 00:45:11.836223 HELLO5 -> 2018-11-07 00:45:11.938223 HELLO6 -> 2018-11-07 00:45:12.040216 How can I write to the jenkins job log without any echoing / extraneous lines being inserted??! Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-54505) Expose plugin manager to groovy
Title: Message Title Alon Bar-Lev created an issue Jenkins / JENKINS-54505 Expose plugin manager to groovy Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-11-06 23:28 Priority: Minor Reporter: Alon Bar-Lev I am sorry if this is not the right component. It is important for a generic groovy script to detect installed plugins so it can operate based on the availability of plugins. I could not find any option to do so, even the binding.hasVariable and getMetaClass are blocked, so detection of symbols in current scope is probably blocked. It will be nice if this.hasVariable can be enabled to detect steps/methods/variables, or at least have a way to query what plugins are installed, for example getPlugins which return a dictionary of plugin with its version. I found some references of people require the same, however, I could not see if/where a bug was opened, so I am sorry if this is a duplicate. Thanks! Add Comment
[JIRA] (JENKINS-54249) GitHub Commit Status Setter - Cannot retrieve Git metadata
Title: Message Title Felipe Lopes commented on JENKINS-54249 Re: GitHub Commit Status Setter - Cannot retrieve Git metadata +1 here... Downgrading the Github Plugin to 1.29.2 solved the issue here too... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48556) timestamps() randomly not recognized as a valid option
Title: Message Title
Mike Balfour commented on JENKINS-48556
Re: timestamps() randomly not recognized as a valid option
Andrew Bayer : The fix for this bug is to change pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Options.groovy getAllowedOptionTypes() from this: static Map getAllowedOptionTypes() { *Map c = propertyTypeCache.get(CACHE_KEY)* c.putAll(getEligibleDeclarativeOptionTypeClasses()) c.putAll(getEligibleWrapperStepClasses()) return c.sort() } To this: static Map getAllowedOptionTypes() { *Map c = [:]* *c.putAll(propertyTypeCache.get(CACHE_KEY))* c.putAll(getEligibleDeclarativeOptionTypeClasses()) c.putAll(getEligibleWrapperStepClasses()) return c.sort() } The problem is that the initial assignment is assigning c to a reference of propertyTypeCache instead of making a copy, which causes the rest of the function to modify propertyTypeCache. If one job is modifying propertyTypeCache while a second job is refreshing the LoadingCache, the resultant Map gets corrupted and produces incorrect results. (In extremely rare cases, it's also possible to hit a multiple thread exception instead of a corrupted Map.) To validate both the problem and the fix, print the contents of propertyTypeCache at the start and the end of the function. The first time through after a cache refresh, propertyTypeCache will end up with different contents. Subsequent calls prior to the next cache refresh will have the same result at the start and the end, which will be identical to c. With the fix, the contents of propertyTypeCache will remain consistent through all function calls. Note that the getEligibleWrapperStepClasses() and getEligibleDeclarativeOptionTypeClasses() may have a similar bug, as they are likely returning references to the Map instead of copies. This doesn't currently cause problems because their only uses are as inputs to putAll(), which makes a copy, but they ought to be validated and fixed to ensure they don't cause problems in the future.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54504) Performance issue with promoted builds and Git branch parameter
Title: Message Title Josh Schreuder created an issue Jenkins / JENKINS-54504 Performance issue with promoted builds and Git branch parameter Issue Type: Bug Assignee: Devin Nusbaum Components: promoted-builds-plugin Created: 2018-11-06 23:02 Priority: Major Reporter: Josh Schreuder When accessing any page featuring a build with promotions (eg. job page, but also job list where promotion icon column is enabled), we are experiencing extremely poor performance. I had a look at the stack while this was going on and it seems to be because of something related to having a build parameter tied to Git branches: Handling GET /job/MyJob/ from 127.0.0.1 : qtp19448387-247861 Job/index.jelly AbstractProject/sidepanel.jelly HistoryWidget/index.jelly HistoryPageFilter/entries.jelly HistoryPageFilter/entries.jelly HistoryPageFilter/entry.jelly PromotedBuildAction/badge.jelly java.lang.ProcessImpl.waitForInterruptibly(Native Method) java.lang.ProcessImpl.waitFor(Unknown Source) hudson.Proc$LocalProc.join(Proc.java:324) hudson.Proc.joinWithTimeout(Proc.java:170) org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2012) org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1735) org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1640) org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1631) org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteReferences(CliGitAPIImpl.java:2851) net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.getBranch(GitParameterDefinition.java:392) net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.generateContents(GitParameterDefinition.java:315)
[JIRA] (JENKINS-54233) Pipeline Script textarea missing
Title: Message Title Andrew Gray commented on JENKINS-54233 Re: Pipeline Script textarea missing Reinstalling Jenkins is not an option. I am more interested in whether the issue occurs on the LTS release (2.138.2) as that is what we are using at work and I can't afford to test it as it is the only instance we currently have. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54071) EC2-plugin not spooling up stopped nodes
Title: Message Title Paul Bovbel commented on JENKINS-54071 Re: EC2-plugin not spooling up stopped nodes That sounds about right Fabrizio, I'll keep an eye on https://issues.jenkins-ci.org/browse/JENKINS-53920. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54503) Ansible tower plugin 0.9.0 issue with Tower 3.3.1
Title: Message Title
James McShane created an issue
Jenkins / JENKINS-54503
Ansible tower plugin 0.9.0 issue with Tower 3.3.1
Issue Type:
Bug
Assignee:
John Westcott
Components:
ansible-tower-plugin
Created:
2018-11-06 22:15
Environment:
ansible-tower-plugin: 0.9 Tower: 3.3.1
Priority:
Minor
Reporter:
James McShane
When we run a tower job from jenkins, we are seeing this error message: ERROR: Unable to request job template invocation Tower received a bad request (400 response code) {"credential":["Incorrect type. Expected pk value, received unicode."],"credentials":["Incorrect type. Expected pk value, received unicode."]} we are running the job with the following: ansibleTower towerServer: 'tower', jobTemplate: '55', inventory: '14', credential: '12', importTowerLogs: true Does the credential need to be an integer? It seems like it is sending the credential the wrong way over the API.
Add Comment
[JIRA] (JENKINS-54502) Jenkins crashed when a build was aborted due to timeout.
Title: Message Title Scott Jiang created an issue Jenkins / JENKINS-54502 Jenkins crashed when a build was aborted due to timeout. Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-11-06 21:27 Labels: jenkins Priority: Major Reporter: Scott Jiang After recently updating to version 2.149 or 2.150, Jenkins crashed if a job tried to abort due to configured time out for the job. From Windows Task Manager we saw the Jenkins processes were gone, but the program being executed by the job was still running (instead that the program should be stopped by Jenkins abort action). The below shows Jenkins job log: C:\FitNesseForAppian>start /b /wait java -jar fitnesse-standalone.jar -p 8980 -c "TransponderNewLeaseTestSuite.IntegrationTestSuite.WebServiceInitUnauthNewOopPlateNameMatchPacFulfill?test=text" Nov 06, 2018 3:45:59 PM fitnesse.ConfigurationParameter loadProperties INFO: No configuration file found (C:\FitNesseForAppian\plugins.properties) Bootstrapping FitNesse, the fully integrated standalone wiki and acceptance testing framework. root page: fitnesse.wiki.fs.FileSystemPage at .\FitNesseRoot#latest logger: none authenticator: fitnesse.authentication.PromiscuousAuthenticator page factory: fitnesse.html.template.PageFactory page theme: bootstrap Executing command: Etr407AppianTest.TransponderManagement.TransponderNewLeaseTestSuite.IntegrationTestSuite.WebServiceInitUnauthNewOopPlateNameMatchPacFulfill?test=textStarting Test System: slim:fitnesse.slim.SlimService. Build timed out (after 3 minutes). Marking the build as aborted.
[JIRA] (JENKINS-54501) ClassCastException in SonarUtils getPersistentActions
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-54501 ClassCastException in SonarUtils getPersistentActions Issue Type: Bug Assignee: Sonar Team Attachments: build.xml Components: sonar Created: 2018-11-06 21:22 Priority: Minor Reporter: Alex Taylor Issue: When iterating over all the actions within a Jenkins job using this code I hit a ClassCastException because getActions() does not necessarily return a class that can be converted to Action. This happened in particular with hudson.model.ParametersDefinitionProperty when I had a parameter in my build process. This issue is easily reproducible with the attached build.xml Steps to Reproduce: 1. Open up the Sonar plugin code in IDE of your choice 2. Do a mvn hpi:run and create a freestyle job 3. Build said freestyle job 2 times 4. Stop the run and then modify build #2's build.xml file with the attached 5. Restart the hpi:run 6. Observe the class cast error in the logs and the build #2 not show in the UI Expected results: The build.xml would throw other errors(like the sonar not existing) but be able to parse the build.xml Other Notes: I would normally expect the return for getActions() to be actionable items but apparently since it is deprecated the process has changed for what that will return. Additionally the getAllActions() method can not be used since it calls the overwritten createFor() which ends up causing a stackoverflow. There needs to either be a better checking on the getActions or the getActions needs to be replaced and the createFor() method needs to be fixed
[JIRA] (JENKINS-54500) Charset not respected in parallel sync
Title: Message Title Sean Sutherland updated an issue Jenkins / JENKINS-54500 Charset not respected in parallel sync Change By: Sean Sutherland We have noticed that when syncing a unicode file from a utf8 server, the sync will fail when parallel sync is enabled. With identical other settings but parallel disabled, the sync will succeed. P4 Task: attempt: 1ERROR: P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s):C:\Program Files (x86)\Jenkins\workspace\test\main\Tools\perl\strawberry-perl-5.26.0.2-64bit-portable\perl\vendor\lib\Unicode\LineBreak.pod - encoding error. Repro steps:Create freestyle job with p4 scm step. Configure to sync from a utf8 server with at least one file with unicode characters in the clientspec. Enable parallel sync. Run job. Sample error log:P4 Task: attempt: 1ERROR: P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s):C:\Program Files (x86)\Jenkins\workspace\test\main\Tools\perl\strawberry-perl-5.26.0.2-64bit-portable\perl\vendor\lib\Unicode\LineBreak.pod - encoding error. Additional Info:If the charset is specified in the environment, the sync will succeed. This suggests that the configured charset and the environment charset are read in at different points, and only the latter is implemented correctly for parallel sync. As a note, since p4 java will run as part of the slave JVM, this environment needs to be applied to the slave process itself (as opposed to in-jenkins configured environments which only apply to subprocesses). We noticed that the same bug with the command line p4 client as well. Running a parallel sync with p4 -C utf8 will fail but setting it externally (any of environment, p4 set, or p4 config file) will succeed. As an aside, how would I go about filing a bug to Perforce for the p4 client? Add Comment
[JIRA] (JENKINS-54500) Charset not respected in parallel sync
Title: Message Title Sean Sutherland created an issue Jenkins / JENKINS-54500 Charset not respected in parallel sync Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2018-11-06 21:13 Environment: Jenkins 2.89.1 P4 Plugin 1.9.4 Priority: Minor Reporter: Sean Sutherland We have noticed that when syncing a unicode file from a utf8 server, the sync will fail when parallel sync is enabled. With identical other settings but parallel disabled, the sync will succeed. P4 Task: attempt: 1 ERROR: P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s): C:\Program Files (x86)\Jenkins\workspace\test\main\Tools\perl\strawberry-perl-5.26.0.2-64bit-portable\perl\vendor\lib\Unicode\LineBreak.pod - encoding error. Repro steps: Create freestyle job with p4 scm step. Configure to sync from a utf8 server with at least one file with unicode characters in the clientspec. Enable parallel sync. Run job. Sample error log: P4 Task: attempt: 1 ERROR: P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s): C:\Program Files (x86)\Jenkins\workspace\test\main\Tools\perl\strawberry-perl-5.26.0.2-64bit-portable\perl\vendor\lib\Unicode\LineBreak.pod - encoding error. Additional Info: If the charset is specified in the environment, the sync will succeed. This suggests that the configured charset and the environment charset are read in at different points, and only the latter is implemented correctly for parallel sync. As a note, since p4 java will run as part of the slave JVM, this environment needs to be applied to the slave process itself (as opposed to in-jenkins configured
[JIRA] (JENKINS-54475) p4sync hangs at "p4 sync -f -q"
Title: Message Title Bing Shiao updated an issue Jenkins / JENKINS-54475 p4sync hangs at "p4 sync -f -q" Change By: Bing Shiao Labels: p4 p4-plugin p4plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53858) Deadlock on EC2 resources
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-53858 Re: Deadlock on EC2 resources Can you try this snapshot : https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/ec2/1.42-SNAPSHOT/ec2-1.42-20181106.195515-1.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54041) EC2 Plugin no longer able to start build slaves
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-54041 Re: EC2 Plugin no longer able to start build slaves The problem is related to the CAP calculation that counts the stopped node as running. I am preparing the fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54392) EC2 Plugin Does Not Start Stopped Nodes
Title: Message Title FABRIZIO MANFREDI closed an issue as Fixed Jenkins / JENKINS-54392 EC2 Plugin Does Not Start Stopped Nodes Change By: FABRIZIO MANFREDI Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54392) EC2 Plugin Does Not Start Stopped Nodes
Title: Message Title FABRIZIO MANFREDI started work on JENKINS-54392 Change By: FABRIZIO MANFREDI Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54071) EC2-plugin not spooling up stopped nodes
Title: Message Title FABRIZIO MANFREDI closed an issue as Fixed Jenkins / JENKINS-54071 EC2-plugin not spooling up stopped nodes Change By: FABRIZIO MANFREDI Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54071) EC2-plugin not spooling up stopped nodes
Title: Message Title FABRIZIO MANFREDI edited a comment on JENKINS-54071 Re: EC2-plugin not spooling up stopped nodes [~paulbovbel] can you check if you didn't reach the cap ? there is a bug in the EC2 that is counting the stopped instances as running, that means when you reach the CAP is not able to restart the instance in the stop state . (duplication of the JENKINS-53920) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54071) EC2-plugin not spooling up stopped nodes
Title: Message Title FABRIZIO MANFREDI started work on JENKINS-54071 Change By: FABRIZIO MANFREDI Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54499) Loosing connection to Docker container
Title: Message Title Samuel Lopez updated an issue Jenkins / JENKINS-54499 Loosing connection to Docker container Change By: Samuel Lopez Environment: Jenkins 2.138.1 Running on Ubuntu 16.04Docker Plugin: 1.1.5 Docker version: 17.09.0-ce, build afdb6d4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54315) Instances sometimes stay disconnected
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-54315 Re: Instances sometimes stay disconnected Can you test this snapshot that contains a fix ?: https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/ec2/1.42-SNAPSHOT/ec2-1.42-20181106.195515-1.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54187) EC2 Plugin deadlock leaving Jenkins unresponsive
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-54187 Re: EC2 Plugin deadlock leaving Jenkins unresponsive Can you test this snapshot that contains a fix for the deadlock? : https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/ec2/1.42-SNAPSHOT/ec2-1.42-20181106.195515-1.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54499) Loosing connection to Docker container
Title: Message Title
Samuel Lopez created an issue
Jenkins / JENKINS-54499
Loosing connection to Docker container
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
docker-plugin
Created:
2018-11-06 20:34
Environment:
Jenkins 2.138.1 Running on Ubuntu 16.04 Docker Plugin: 1.1.5
Priority:
Critical
Reporter:
Samuel Lopez
Hello We are seeing the following issue: ERROR: Build step failed with exception java.lang.NullPointerException: no workspace from node io.jenkins.docker.DockerTransientNode[1604-JDK8-1uywz3thf] which is computer DockerComputer{name=1604-JDK8-1uywz3thf, slave=io.jenkins.docker.DockerTransientNode[1604-JDK8-1uywz3thf]} and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:88) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:945) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:896) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1815) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Execute shell' marked build as failure ERROR: Failed to parse POMs java.io.IOException: Backing channel '1604-JDK8-1uywz3thf' is disconnected. at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214) at
[JIRA] (JENKINS-54496) Node monitoring should not log exceptions for disconnected nodes
Title: Message Title pjdarton commented on JENKINS-54496 Re: Node monitoring should not log exceptions for disconnected nodes The node existed when the method started its work, but the node is removed during execution (causing the exception). It's a race condition, but one that's very common with high-throughout dynamic slaves. I strongly suspect that, if the code checked again "does this node exist" before logging the exception, it would discover that the node does not exist anymore. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54498) Version Creation now requires version code which breaks binary compatibility
Title: Message Title Mez Pahlan commented on JENKINS-54498 Re: Version Creation now requires version code which breaks binary compatibility Some good discussion on the plugin documentation. https://jenkins.io/doc/developer/plugin-development/pipeline-integration/#constructor-vs-setters Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Jesse Glick commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile just accept the extra message in the Jenkins log and hope for a fix from the groovy post build plugin This. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Mark Waite edited a comment on JENKINS-54128 Re: Deprecated calls to Run.getLogFile [~jglick] I don't quite understand the comment where you said:bq. The call from WarningsPublisher.parseConsoleLog is unrelated.bq. bq. As are calls from GroovyPostbuildRecorder.I believe I'm using the GroovyPostbuildRecorder when I use the manage object provided by the groovy post build plugin to call [logContains()|https://github.com/MarkEWaite/jenkins-pipeline-utils/blob/fa3266f738f735e40581abfd9b6a226b3dac0ab6/src/com/markwaite/Assert.groovy#L13]. Should I be using something else, or just accept the extra message in the Jenkins log and hope for a fix from the groovy post build plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Mark Waite commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile Jesse Glick I don't quite understand the comment where you said: The call from WarningsPublisher.parseConsoleLog is unrelated. As are calls from GroovyPostbuildRecorder. I believe I'm using the GroovyPostbuildRecorder when I use the manage object provided by the groovy post build plugin to call logContains(). Should I be using something else, or just accept the extra message in the Jenkins log and hope for a fix from the groovy post build plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54498) Version Creation now requires version code which breaks binary compatibility
Title: Message Title Mez Pahlan created an issue Jenkins / JENKINS-54498 Version Creation now requires version code which breaks binary compatibility Issue Type: Bug Assignee: Mez Pahlan Components: hockeyapp-plugin Created: 2018-11-06 19:35 Priority: Major Reporter: Mez Pahlan PR#52 deprecated the DataBoundContructor and introduced a new one that specifies a versionCode to be supplied. Unfortunately this breaks pipelines for some uses as the old deprecated constructor is no longer DataBound anymore. See: https://github.com/jenkinsci/hockeyapp-plugin/pull/52#issuecomment-436344872 Add Comment
[JIRA] (JENKINS-54027) ID analysis is already used by another action
Title: Message Title Brian J Murrell commented on JENKINS-54027 Re: ID analysis is already used by another action Still not really seeing any improvement on the exclusion list: Static Analysis - Messages Error Messages Can't resolve absolute paths for some files: topology-linux.c topology-linux.c topology-linux.c topology-linux.c topology-linux.c ... skipped logging of 758 additional errors ... Can't create fingerprints for some files: 'topology-linux.c', IO exception has been thrown: java.nio.file.NoSuchFileException: topology-linux.c 'topology-linux.c', IO exception has been thrown: java.nio.file.NoSuchFileException: topology-linux.c 'topology-linux.c', IO exception has been thrown: java.nio.file.NoSuchFileException: topology-linux.c 'topology-linux.c', IO exception has been thrown: java.nio.file.NoSuchFileException: topology-linux.c 'topology-linux.c', IO exception has been thrown: java.nio.file.NoSuchFileException: topology-linux.c ... skipped logging of 758 additional errors ... Can't create blame requests for some affected files: Skipping non-workspace file topology-linux.c Skipping non-workspace file topology-linux.c Skipping non-workspace file topology-linux.c Skipping non-workspace file topology-linux.c Skipping non-workspace file topology-linux.c ... skipped logging of 758 additional errors ... Created no blame requests - Git blame will be skipped Information Messages Parsing console log (workspace: '/var/lib/jenkins/workspace/daos-stack-org_daos_PR-13-XSYVVAKVRRCIRZBUBQLEPYMVXQHYAQV52HHPQR55EURLM5NXUHMA') Post processing issues on 'wolf-53vm12' with encoding 'UTF-8' Resolving absolute file names for all issues -> 0 resolved, 763 unresolved, 14 already absolute Copying affected files to Jenkins' build folder /var/lib/jenkins/jobs/daos-stack-org/jobs/daos/branches/PR-13/builds/523 -> 0 copied, 9 not in workspace, 172 not-found, 0 with I/O error Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files) -> resolved module names for 777 issues Resolving package names (or namespaces) by parsing the affected files -> resolved package names of 181 affected files Applying 2 filters on the set of 777 issues (14 issues have been removed, 763 issues will be published) Creating fingerprints for all affected code blocks to track issues over different builds -> created fingerprints for 0 issues Invoking Git blamer to create author and commit information for all affected files GIT_COMMIT env = 'HEAD' Git working tree = '/var/lib/jenkins/workspace/daos-stack-org_daos_PR-13-XSYVVAKVRRCIRZBUBQLEPYMVXQHYAQV52HHPQR55EURLM5NXUHMA' Git commit ID = 'd9b0fbf7e62d89604238f786b6955e74f759325d' Job workspace =
[JIRA] (JENKINS-54496) Node monitoring should not log exceptions for disconnected nodes
Title: Message Title Jeff Thompson commented on JENKINS-54496 Re: Node monitoring should not log exceptions for disconnected nodes I'm not really sure what the desired behavior here is. It seems like the ask is that Jenkins would be better able to distinguish between an ephemeral and a permanent agent and then react or log differently in the two situations. It seems like these log messages might be important for permanent agents but excessive for ephemeral ones. Maybe this type of monitoring should not be enabled for ephemeral agents. Alternatively, the ask might be to improve the detection of when an agent no longer exists. Looking at the stack trace and the code, this operation is only called if Jenkins thinks the node exists. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54475) p4sync hangs at "p4 sync -f -q"
Title: Message Title
Bing Shiao updated an issue
Jenkins / JENKINS-54475
p4sync hangs at "p4 sync -f -q"
Change By:
Bing Shiao
p4sync hangs at com "p4 sync -f -q" . perforce.p4java.impl.mapbased.rpc.stream.RpcSocketOutputStream.write() = Build Log ={code}Running on windows2018-00 in D:\views\jenkins\stg\workspace\art/art/art[Pipeline] {[Pipeline] p4sync... p4 client -o p4service-stg-windows2018-00-art-art-art +... p4 info +... p4 client -o p4service-stg-windows2018-00-art-art-art +... p4 info +... p4 info +... p4 client -i +... client: p4service-stg-windows2018-00-art-art-art... p4 client -o p4service-stg-windows2018-00-art-art-art +... p4 info +... p4 counter change +... p4 changes -m1 -ssubmitted //p4service-stg-windows2018-00-art-art-art/... +Building on Node: windows2018-00... p4 client -o p4service-stg-windows2018-00-art-art-art -p4 client -o p4service-stg-windows2018-00-art-art-art... p4 info -p4 infoP4 Task: establishing connection server: p4.art.com:1666... node: windows2018-00P4 Task: reverting all pending and shelved revisions p4 revert D:\views\jenkins\stg\workspace\art/art/art/... -p4 revert D:\views\jenkins\stg\workspace\art/art/art/...D:\views\jenkins\stg\workspace\art/art/art/... - file(s) not opened on this client rm [abandoned files]duration: (101ms)... p4 sync -q D:\views\jenkins\stg\workspace\art/art/art/...#none -p4 sync -q D:\views\jenkins\stg\workspace\art/art/art/...#none... rm -rf D:\views\jenkins\stg\workspace\art/art/artP4 Task: syncing files at change: 791149... p4 sync -f -q D:\views\jenkins\stg\workspace\art/art/art/...@791149 -p4 sync -f -q D:\views\jenkins\stg\workspace\art/art/art/...@791149... totalFileSize 49136103... totalFileCount 6880Aborted by Shiao, Bing{code}= Jenkinsfile ={code}stage("checkout") { agent \{ label 'WINDOWS'} steps { p4checkout() } }}def p4checkout() { p4sync charset: 'none', credential: '00a0b008----01fa', format: 'p4service-stg-${NODE_NAME}-${JOB_NAME}', populate: forceClean(have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, replace: true, tidy: false), source: depotSource('//p4depot/ART/art/main/...')}{code}= Thread dump of Jenkins Agent windows2018-00 = https://gist.github.com/bingshiao/3fe801d2c2ed7d701d90e0741422e398
[JIRA] (JENKINS-54475) p4sync hangs at "p4 sync -f -q"
Title: Message Title Bing Shiao updated an issue Jenkins / JENKINS-54475 p4sync hangs at "p4 sync -f -q" Change By: Bing Shiao Summary: p4sync hangs at com.perforce.p4java.impl.mapbased.rpc.stream.RpcSocketOutputStream.write "p4 sync -f -q" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50591) Files and paths with ampersand cause exception
Title: Message Title Jon Tancer commented on JENKINS-50591 Re: Files and paths with ampersand cause exception Jesse Glick Thank you for the quick turn around time releasing the update. I installed the update and everything is working well Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54071) EC2-plugin not spooling up stopped nodes
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-54071 Re: EC2-plugin not spooling up stopped nodes Paul Bovbel can you check if you didn't reach the cap ? there is a bug in the EC2 that is counting the stopped instances as running, that means when you reach the CAP is not able to restart the instance in the stop state. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54071) EC2-plugin not spooling up stopped nodes
Title: Message Title Paul Bovbel commented on JENKINS-54071 Re: EC2-plugin not spooling up stopped nodes I believe I see the same issue as Tobias in 1.41 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54497) Too many Bitbucket git checkouts on Master at the same time
Title: Message Title Will Freeman created an issue Jenkins / JENKINS-54497 Too many Bitbucket git checkouts on Master at the same time Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-11-06 18:38 Environment: Jenkins 2.149 bitbucket branch source 2.2.14 Priority: Major Reporter: Will Freeman When configured to trigger PR builds when an upstream branch changes, if there is hundreds of PRs open, the Jenkins Master fires the initial checkout to get the Jenkinsfile all at the same time on the master. This means literally, that several hundred git operations get called at the same time, stressing out the file system on the master to the point that the master stops responding. Especially when that repository is very large. It also puts tremendous load on the upstream Bitbucket server, which starts throttling at a certain point. Even with reference repositories in use. It seems that there needs to be a configuration option to control how many of these git operations are allowed to fire on the master at the same time. This effectively brings down our Jenkins master daily.
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Peter Kolínek commented on JENKINS-53266 Re: Legacy token for user "unknown" keeps reappearing I have the same issue. The "unknown" token reappears after every restart of Jenkins. I've created the list of plugins that are present on my instance AND in list provided by Peter Lieverdink: plugins-merged.txt. Hopefully this will help to narrow the search. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Peter Kolínek updated an issue Jenkins / JENKINS-53266 Legacy token for user "unknown" keeps reappearing Change By: Peter Kolínek Attachment: plugins-merged.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39107) expose "Stream Codeline" as an environment variable
Title: Message Title Karl Wirth commented on JENKINS-39107 Re: expose "Stream Codeline" as an environment variable Confirmation that the workaround is not valid when using scripted pipeline. Scripted pipeline does not do the implicit sync so P4CLIENT is either null or if using global libraries the temporary client for the global library. However as P4CLIENT is not set it's questionable if 'P4_STREAM' (if it existed) would be availble until 'p4sync' is invoked which would need to know the STREAM name to run. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39107) expose "Stream Codeline" as an environment variable
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-39107 expose "Stream Codeline" as an environment variable Change By: Karl Wirth Labels: P4_SUPPORT P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54410) Compatibility of Blue Ocean ATH with pre- and post-2.128 login screens from classic
Title: Message Title Karl Shultz updated JENKINS-54410 Jenkins / JENKINS-54410 Compatibility of Blue Ocean ATH with pre- and post-2.128 login screens from classic Change By: Karl Shultz Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54410) Compatibility of Blue Ocean ATH with pre- and post-2.128 login screens from classic
Title: Message Title Karl Shultz commented on JENKINS-54410 Re: Compatibility of Blue Ocean ATH with pre- and post-2.128 login screens from classic Approved and merged. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Jesse Glick commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile As are calls from GroovyPostbuildRecorder. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54128 Deprecated calls to Run.getLogFile Change By: Jesse Glick Component/s: groovy-postbuild-plugin Component/s: timestamper-plugin Component/s: warnings-plugin Component/s: workflow-job-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54128 Deprecated calls to Run.getLogFile Change By: Jesse Glick Summary: Timestamper causes lots of WARNING messages in the log ( Deprecated calls to Run. getLogFile call) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Jesse Glick assigned an issue to Stefan Wolf Jenkins / JENKINS-54128 Deprecated calls to Run.getLogFile Change By: Jesse Glick Assignee: Steven G Brown Stefan Wolf Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Timestamper causes lots of WARNING messages in the log (getLogFile call)
Title: Message Title Jesse Glick commented on JENKINS-54128 Re: Timestamper causes lots of WARNING messages in the log (getLogFile call) For the timestamper case, this warning is displayed only if you use the View as plain text link—which AFAIK never worked for Pipeline builds anyway. I checked whether it was straightforward to suppress this link in the patch for JENKINS-48344, but unfortunately it is not, due to the _javascript_ tricks involved. The call from WarningsPublisher.parseConsoleLog is unrelated. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-53920 Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again Yes, that is a bug in the instance cap with the Stopped instances that are counted as a running machine. I will try to put the fix in the 1.42 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54089) Create an audit log destination global configuration
Title: Message Title Matt Sicker commented on JENKINS-54089 Re: Create an audit log destination global configuration Hello! This task is part of an Outreachy project. Today was the deadline to apply for this round, so I think it's too late for this project. Come check out the jenkinsci/outreachy gitter channel for more info. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44860) Disable masking of usernames
Title: Message Title Jesse Glick commented on JENKINS-44860 Re: Disable masking of usernames Trivially worked around FWIW: sh 'echo $USER_ENV_VAR | od -a' Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54496) Node monitoring should not log exceptions for disconnected nodes
Title: Message Title pjdarton created an issue Jenkins / JENKINS-54496 Node monitoring should not log exceptions for disconnected nodes Issue Type: Improvement Assignee: Jeff Thompson Components: core, remoting Created: 2018-11-06 17:11 Priority: Minor Reporter: pjdarton In an environment in which Jenkins nodes are being created and removed a lot, e.g. when using the docker-plugin to create single-use containers as slave nodes, the node monitoring functionality can fill the logs full of spurious exceptions, e.g. Oct 13, 2018 10:18:14 PM io.jenkins.docker.DockerTransientNode$1 println INFO: Disconnected computer for node 'docker-hst02-00030qwaqtu3g'. Oct 13, 2018 10:18:14 PM io.jenkins.docker.DockerTransientNode$1 println INFO: Removed Node for node 'docker-hst02-00030qwaqtu3g'. Oct 13, 2018 10:18:14 PM hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitorDetailed WARNING: Failed to monitor docker-hst02-00030qwaqtu3g for Clock Difference java.util.concurrent.ExecutionException: java.io.IOException: Cannot locate RemoteClassLoader.ClassLoaderProxy(2) in the channel exported table at hudson.remoting.Channel$2.adapt(Channel.java:992) at hudson.remoting.Channel$2.adapt(Channel.java:986) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:76) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:305) Caused by: java.io.IOException: Cannot locate RemoteClassLoader.ClassLoaderProxy(2) in the channel exported table at
[JIRA] (JENKINS-54347) SchemaDVFactoryImpl NoClassDefFoundError with xUnit 2.3.1
Title: Message Title Éric Gillet commented on JENKINS-54347 Re: SchemaDVFactoryImpl NoClassDefFoundError with xUnit 2.3.1 I think I could do it. Will keep you posted. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40606) Add ability to perform actions on branch removal
Title: Message Title Jesse Glick commented on JENKINS-40606 Re: Add ability to perform actions on branch removal Something along the lines of JENKINS-37220 could be useful for this sort of specialized use case. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Devin Nusbaum commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException For now, I went ahead and filed https://github.com/jenkinsci/workflow-durable-task-step-plugin/pull/90 to allow the timeout to be configured by system property. Feel free to pull down the incremental build of that PR once it is complete for testing if you are already running workflow-durable-task-step 2.26, or review/comment on the PR. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Ian Cotton commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Andrew a I am not able to build the plugin at the moment. My Jenkins server doesn't have the required plugins. We are setting up some new server and hopefully I can use one of them. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Devin Nusbaum assigned an issue to Devin Nusbaum Jenkins / JENKINS-46507 Parallel Pipeline random java.lang.InterruptedException Change By: Devin Nusbaum Assignee: Jose Blas Camacho Taboada Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50989) The sourceFiles property is ignored. This causes an error when uses in combination of removePrefix
Title: Message Title Alex Earl commented on JENKINS-50989 Re: The sourceFiles property is ignored. This causes an error when uses in combination of removePrefix Ilya Tretyakov it3xl You can try the HPI file from here: https://ci.jenkins.io/job/Plugins/job/publish-over-cifs-plugin/job/master/lastSuccessfulBuild/artifact/target/publish-over-cifs.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Andrew a edited a comment on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException [~dnusbaum] I'll recompile the plugin with a 60 second timeout and fire up the next regression tomorrow, expect results somewhere by friday/saturday. A facility to override this timeout would be very useful, because (according to zabbix) the iowait fluctuations were barely noticeable during backup. At higher loads things will get waaay worse, so I'd also put a note somewhere in README/TROUBLESHOOTING section. [~icotton64] No problem, I fully understand. Can you still recompile it yourself with a 30 second timeout (see my patch above) and give it a try? This way we'll provide [~dnusbaum] some results about a suitable timeout faster. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Andrew a edited a comment on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException [~dnusbaum] I'll recompile the plugin with a 60 second timeout and fire up the next regression tomorrow, expect results somewhere by friday/saturday. A facility to override this timeout would be very useful, because (according to zabbix) the iowait fluctuations were barely noticeable during backup. At higher loads things will get waaay worse, so I'd also put a note somewhere in README/TROUBLESHOOTING section. [~icotton64] No problem, I fully understand. Can you still recompile it with a 30 second timeout (see my patch above) and give it a try? This way we'll provide [~dnusbaum] some results about a suitable timeout faster. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Andrew a edited a comment on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException [~dnusbaum] I'll recompile the plugin with a 60 second timeout and fire up the next regression tomorrow, expect results somewhere by friday/saturday. A facility to override this timeout would be very useful, because (according to zabbix) the iowait fluctuations were barely noticeable during backup. At higher loads things will get waaay worse, so I'd also put a note somewhere in README/TROUBLESHOOTING section. [~icotton64] No problem, I fully understand. Can you recompile it with a 30 second timeout (see my patch above) and give it a try? This way we'll provide [~dnusbaum] some results about a suitable timeout faster. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50989) The sourceFiles property is ignored. This causes an error when uses in combination of removePrefix
Title: Message Title Ilya Tretyakov it3xl commented on JENKINS-50989 Re: The sourceFiles property is ignored. This causes an error when uses in combination of removePrefix Alex Earl, contact me if you need any testing. I just updated my Jenkins and installed the plugin. Newer used it before. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Andrew a commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Devin Nusbaum I'll recompile the plugin with a 60 second timeout and fire up the next regression tomorrow, expect results somewhere by friday/saturday. A facility to override this timeout would be very useful, because (according to zabbix) the iowait fluctuations were barely noticeable during backup. At higher loads things will get waaay worse, so I'd also put a note somewhere in README/TROUBLESHOOTING section. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Ian Cotton commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Sorry Andrew a the system we are seeing the issue on is our production system and I really don't want to risk installing a pre-compiled plugin on it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50989) The sourceFiles property is ignored. This causes an error when uses in combination of removePrefix
Title: Message Title Alex Earl commented on JENKINS-50989 Re: The sourceFiles property is ignored. This causes an error when uses in combination of removePrefix I believe I have a fix for this so that the "workaround" isn't needed, but I need to do more testing to be sure. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54492) checkout scm information no longer injected into environment in pipeline job
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-54492 checkout scm information no longer injected into environment in pipeline job Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42450) Efficiently add a single repo to a github org without requiring a full scan
Title: Message Title Vivek Pandey commented on JENKINS-42450 Re: Efficiently add a single repo to a github org without requiring a full scan This was fixed long time back. PR https://github.com/jenkinsci/blueocean-plugin/pull/893. However, pipeline creation using GitHub org folder was removed in later version of blue ocean. Basically, there is no pipeline creation using Github org folder in blueocean now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Samuel Lopez commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Hello Folks, We are also observing this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50989) The sourceFiles property is ignored. This causes an error when uses in combination of removePrefix
Title: Message Title
Ilya Tretyakov it3xl edited a comment on JENKINS-50989
Re: The sourceFiles property is ignored. This causes an error when uses in combination of removePrefix
Jenkins Freestyle jobs workaround: # Under "Send build artifacts to a windows share" click "Advanced". # Insert the comma{code:java}, {code}into the "Pattern separator" field.(tested on Jenkins 2.138.2, Publish Over CIFS 0.11, Windows) I'll say more. You can't even use Publish Over CIFS plugin without this workaround, at all. Even with the empty "Remove prefix" field.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50989) The sourceFiles property is ignored. This causes an error when uses in combination of removePrefix
Title: Message Title
Ilya Tretyakov it3xl edited a comment on JENKINS-50989
Re: The sourceFiles property is ignored. This causes an error when uses in combination of removePrefix
Jenkins Freestyle jobs workaround: # Under "Send build artifacts to a windows share" click "Advanced". # Insert the comma{code:java}, {code}into the "Pattern separator" field. (tested on Jenkins 2.138.2, Publish Over CIFS 0.11, Windows)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50989) The sourceFiles property is ignored. This causes an error when uses in combination of removePrefix
Title: Message Title Ilya Tretyakov it3xl commented on JENKINS-50989 Re: The sourceFiles property is ignored. This causes an error when uses in combination of removePrefix Jenkins Freestyle jobs workaround: Under "Send build artifacts to a windows share" click "Advanced". Insert the comma , into the "Pattern separator" field. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50591) Files and paths with ampersand cause exception
Title: Message Title Jesse Glick updated JENKINS-50591 Sorry, this fell between the cracks! Jenkins / JENKINS-50591 Files and paths with ampersand cause exception Change By: Jesse Glick Status: Fixed but Unreleased Resolved Released As: 1.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Timestamper causes lots of WARNING messages in the log (getLogFile call)
Title: Message Title Devin Nusbaum commented on JENKINS-54128 Re: Timestamper causes lots of WARNING messages in the log (getLogFile call) That message was added to workflow-job-plugin 2 years ago it seems to have first appeared in workflow-job-plugin 2.26, not in any of the preceding plugin releases. Mark Waite The message was added in this PR sometime in its 2-year lifespan, but only recently merged and released in workflow-job 2.26. The log-handling rewrite for JEP-210 has changed the nature of various log-related methods. Previously, `getLogFile` always returned a reference to a file that already existed on disk, but now with external logging, that call has to read the entire log (which may involve network calls) and write it to a temporary file which is then returned. The best alternative that I know of would be to call WorkflowRun#getLogText and then handle it directly, but depending on your use case, maybe WorkflowRun#getLogReader or WorkflowRun#getLog(int) would be useful as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50730) NoClassDefFound errors in Cloud Slaves
Title: Message Title Jeff Thompson commented on JENKINS-50730 Re: NoClassDefFound errors in Cloud Slaves Thomas COAN, if you have a GitHub account, you would be welcome to add your comment directly to the PR. At this point, though, I hope to merge that today so no need to bother. I think the question of rarity was on the order of minutes or less. If the occurrence was that frequent these log messages could still be annoying. At 5-10 per day the disconnects are very annoying but the log messages may be helpful. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title
Michel Zanini commented on JENKINS-53920
Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
I also tested with 1.41 released version. I had the same problem:
Cannot provision - no capacity for instances: 0
This is happening due to the fact I have instance cap of 2 and already 2 slaves are created and at STOPPED state. It still tries to create another instead of starting the ones STOPPED. Increasing the cap to 3 make a new box be created. I am not sure what I am doing wrong since same thing works on 1.39. This is my role permissions:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor",
"Effect": "Allow",
"Action": [
"ec2:DescribeSpotInstanceRequests",
"ec2:CancelSpotInstanceRequests",
"ec2:GetConsoleOutput",
"ec2:RequestSpotInstances",
"ec2:RunInstances",
"ec2:StartInstances",
"ec2:StopInstances",
"ec2:TerminateInstances",
"ec2:CreateTags",
"ec2:DeleteTags",
"ec2:DescribeInstances",
"ec2:DescribeKeyPairs",
"ec2:DescribeRegions",
"ec2:DescribeImages",
"ec2:DescribeAvailabilityZones",
"ec2:DescribeSecurityGroups",
"ec2:DescribeSubnets",
"iam:PassRole",
"iam:ListInstanceProfilesForRole"
],
"Resource": "*"
}
]
}
Add Comment
[JIRA] (JENKINS-54495) Better handling of GitHub Organization folder scan to avoid API quota
Title: Message Title Leandro Lucarella created an issue Jenkins / JENKINS-54495 Better handling of GitHub Organization folder scan to avoid API quota Issue Type: Improvement Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-11-06 15:32 Environment: Jenkins ver. 2.138.2 GitHub Branch Source Plugin 2.4.1 Labels: performance user-experience github api quota Priority: Major Reporter: Leandro Lucarella When having a big GitHub organization, with hundreds of repos, each with hundreds of branches and tags, refreshing the whole organization is not possible (or it takes ages) due to GitHub API quota being hit. This is particularly bad when trying to add a new repo, it could take days, which is completely impractical. There are several solutions to this issue that I can think of: Use GitHub GraphQL API to query the whole thing in one (or very few) request(s) Make a "shallow scan", that only discovers repos. Then each repo can be refreshed separately, which can 1. enable the quick addition of new repos and 2. distribute the refresh API bursts in time making hitting the API quota less likely Add a separate function to only discover one repo specified by the user
[JIRA] (JENKINS-54474) Variables not resolving in SSH Steps plugin
Title: Message Title
Naresh Rayapati edited a comment on JENKINS-54474
Re: Variables not resolving in SSH Steps plugin
I think you need to put that under node block: {code}node {sshCommand remote: remote, command: "${ ssh_cmd }" }{code}May be, I would use either: {code}sshCommand remote: remote, command: ssh_cmd{code}or this one when you need to actually resolve the strings outside the node block. {code}def actualCommand = "/bash ${ssh_cmd}"sshCommand remote: remote, command: ssh_cmd{code}Not much we can do anything in plugin to fix this, this is basic behavior of Jenkins while resolving Jenkins.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54474) Variables not resolving in SSH Steps plugin
Title: Message Title
Naresh Rayapati commented on JENKINS-54474
Re: Variables not resolving in SSH Steps plugin
I think you need to put that under node block:
node {
sshCommand remote: remote, command: ssh_cmd
}
May be, I would use either:
sshCommand remote: remote, command: ssh_cmd
or this one when you need to actually resolve the strings outside the node block.
def actualCommand = "/bash ${ssh_cmd}"
sshCommand remote: remote, command: ssh_cmd
Not much we can do anything in plugin to fix this, this is basic behavior of Jenkins while resolving Jenkins.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50323) PullRequestSCMHead and PullRequestSCMRevision external use
Title: Message Title Steven Foster resolved as Fixed Jenkins / JENKINS-50323 PullRequestSCMHead and PullRequestSCMRevision external use Change By: Steven Foster Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42450) Efficiently add a single repo to a github org without requiring a full scan
Title: Message Title Leandro Lucarella commented on JENKINS-42450 Re: Efficiently add a single repo to a github org without requiring a full scan BTW, this is marked as resolved but I can't find what's the solution and how to use it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40606) Add ability to perform actions on branch removal
Title: Message Title Giorgio Sironi commented on JENKINS-40606 Re: Add ability to perform actions on branch removal I have an idea for a workaround for this that I want to try out: write a Groovy script that is executed periodically as part of a pipeline (through the Jenkins CLI to get the necessary permissions) and scans the deleted pull requests/branches that are in the grace period in which they have not been deleted yet from the Jenkins multiproject folder. If I can get that list, it would be easy to then idempotently run cleanup jobs. They won't run as soon as the pull request/branch is gone, but the frequency of this cleanup can be tuned. I use a similar approach to clean up old agents: https://github.com/elifesciences/elife-alfred-formula/blob/master/jenkinsfiles/ec2-plugin-nodes-retirement.groovy although here it's more difficult to understand the API to traverse and whether it's possible to list all of these. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42450) Efficiently add a single repo to a github org without requiring a full scan
Title: Message Title Leandro Lucarella commented on JENKINS-42450 Re: Efficiently add a single repo to a github org without requiring a full scan Any news on this one? I'm bumping into this problem, specially because scanning the full org will make Jenkins hit the API quota limit. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
