[JIRA] [active-directory] (JENKINS-22830) Slow login w/ Active directory plugin
Jonathan Gowland commented on JENKINS-22830 Slow login w/ Active directory plugin Can you also remove 1.37? It's already caused a big problem in our organization, and may well do so in others. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [xvfb] (JENKINS-23155) Only run plugin under Linux
zregvart commented on JENKINS-23155 Only run plugin under Linux Hi, it's most likely the way the plugin uses Jenkins's functionally, will need to dig into it and try to reproduce on 1.564. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [urlscm] (JENKINS-21633) HTTP Proxy setting ignored?
Christian Wittwer commented on JENKINS-21633 HTTP Proxy setting ignored? We have the same issue. Neither JVM settings (-Dhttp.proxyHost) nor environment variables (http_proxy) work. Jenkins: 1.543 Git Client plugin: 1.4.6 Git Plugin: 2.0 Git version on slave: 1.9.0 Java: Oracle JDK 1.6.0_45 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [clearcase-ucm] (JENKINS-23245) Performance improvement, use catcs to create loadrules
Mads Nielsen created JENKINS-23245 Performance improvement, use catcs to create loadrules Issue Type: Improvement Affects Versions: current Assignee: Praqma Support Components: clearcase-ucm Created: 30/May/14 7:20 AM Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [clearcase-ucm] (JENKINS-23245) Performance improvement, use catcs to create loadrules (case 11385)
Mads Nielsen updated JENKINS-23245 Performance improvement, use catcs to create loadrules (case 11385) Change By: Mads Nielsen (30/May/14 7:23 AM) Summary: Performanceimprovement,usecatcstocreateloadrules (case11385) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [clearcase-ucm] (JENKINS-23246) Performance improvement, use generated load rule to swipe workspace
Mads Nielsen created JENKINS-23246 Performance improvement, use generated load rule to swipe workspace Issue Type: Improvement Assignee: Praqma Support Components: clearcase-ucm Created: 30/May/14 7:21 AM Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger] (JENKINS-23236) PatchSetCreatedEvent now has a kind field
rin_ne commented on JENKINS-23236 PatchSetCreatedEvent now has a kind field Does the below fix belong to this? https://github.com/jenkinsci/gerrit-trigger-plugin/pull/159 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [clearcase-ucm] (JENKINS-23246) Performance improvement, use generated load rule to swipe workspace (case 11387)
Mads Nielsen updated JENKINS-23246 Performance improvement, use generated load rule to swipe workspace (case 11387) Change By: Mads Nielsen (30/May/14 7:32 AM) Summary: Performanceimprovement,usegeneratedloadruletoswipeworkspace (case11387) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [prqa] (JENKINS-23166) PRQA - duplicated message from headers files (case 11364)
Michal Sobczak updated JENKINS-23166 PRQA - duplicated message from headers files (case 11364) Change By: Michal Sobczak (30/May/14 7:31 AM) Attachment: prqa.logging.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [prqa] (JENKINS-23166) PRQA - duplicated message from headers files (case 11364)
Michal Sobczak updated JENKINS-23166 PRQA - duplicated message from headers files (case 11364) Change By: Michal Sobczak (30/May/14 7:34 AM) Attachment: test_sum.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger] (JENKINS-23236) PatchSetCreatedEvent now has a kind field
Joshua Kugler commented on JENKINS-23236 PatchSetCreatedEvent now has a kind field Yes, it appears that there is already code in flight to resolve this issue. I was not aware of that. Thank you for pointing it out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [shell-script-scm] (JENKINS-22361) Execute Shell spawning infinite processes
Gergely Nagy commented on JENKINS-22361 Execute Shell spawning infinite processes I can confirm, the same happens to me. When the "Execute shell" step is executing then Jenkins goes insane and spawns sub-processes until all the memory is getting consumed. "$ /bin/sh -xe /tmp/hudson3122378043088995491.sh" I would rather consider this bug blocker or critical, since it basically halts the whole instance! Environment: Ubuntu 12.04.3 LTS (GNU/Linux 3.8.0-32-generic x86_64) Jenkins ver 1.549 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [shell-script-scm] (JENKINS-22361) Execute Shell spawning infinite processes
Gergely Nagy updated JENKINS-22361 Execute Shell spawning infinite processes System information attached Change By: Gergely Nagy (30/May/14 7:35 AM) Attachment: system-info This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [jobconfighistory] (JENKINS-19814) Job-Configuration - Updates on used plugins and their changes are logged under the last user, who changed the job-configuration
Stefan Brausch commented on JENKINS-19814 Job-Configuration - Updates on used plugins and their changes are logged under the last user, who changed the job-configuration You are right Daniel. This change wasn't saved before. Then I see no easy chance to report it correctly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [prqa] (JENKINS-23166) PRQA - duplicated message from headers files (case 11364)
Michal Sobczak commented on JENKINS-23166 PRQA - duplicated message from headers files (case 11364) Hi Mads, I added log file and report generated by QA C GUI. I observed this problem first time when I added headers files to QA C project. I have not tried contact with PRQA yet because I thought it is problem with qaw call parameters. Best Regards, Michal This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [cppcheck] (JENKINS-23247) Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin.
Senthil Nagarajan created JENKINS-23247 Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin. Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Attachments: Untitled.jpg Components: cppcheck Created: 30/May/14 9:08 AM Description: I have seen the trends as last sucessful builds say job#50 to the currrent failed builds say job#337. Instead of shows last successful and current failed builds. Its better to show only the recent 20/30 depends on configure eventhout all are failed/sucessful. Please find the attachement it not looks as the expected. Due Date: 02/Jun/14 12:00 AM Environment: software platform Project: Jenkins Labels: plugin Priority: Blocker Reporter: Senthil Nagarajan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [android-emulator] (JENKINS-23134) Mixed separators fail for Linux paths
Diego Costantini commented on JENKINS-23134 Mixed separators fail for Linux paths Hi, any word on this? I am currently stuck because latest won't work on my linux slaves without this regression fixed, while the old version doesn't work anymore since Google introduced brackets in their image names :/ id: 16 or "Google Inc.:Google APIs (x86 System Image):19" Name: Google APIs (x86 System Image) When creating a new image of course the file system doesn't allow brackets. Is new version able to cope with that btw? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
mwebber commented on JENKINS-22853 SEVERE: Trying to unexport an object thats already unexported I am also seeing this on 1.565 (Java 7u51). It might have been there earlier without me noticing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [cvs] (JENKINS-23234) cvs update hang when recursive symlink in directory
James Coleman
updated JENKINS-23234
cvs update hang when recursive symlink in directory
Change By:
James Coleman
(30/May/14 10:58 AM)
Description:
Jenkinsjobhangsforeverdoingcvsupdate.Arecursivedirectorycausesjobtohangforever.
Thecvscommandshowninconsolelogis:cvsupdate-d-P-rbranchtagmodApreviousbuildjobcreatedsymlinksto.insomedirectoriesincheckoutarea.
Usingstracecanseeprocessisrecursingintodirectorytomultiplelevels...
Apreviousbuildjobcreatedsymlinks
itishittinganerrorbutjustseems
to
takeforever
.
insomedirectoriesincheckoutarea
.
.notsureifjobswilleverendbyselves...postingstoptojenkinsjobdoesntwork,thejobremainsrunninguntiljenkinsitselfisrestartedORprocesskilled(whichbringsdownjenkins).
Theerror:ELOOP(Toomanylevelsofsymboliclinks)stracefragment:stat64(/var/lib/jenkins/jobs/buildjobname/workspace/work/projectname/module/something/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/python/python/misc/java/java/python/java/inc/misc/inc/call_id.py,{st_mode=S_IFREG|0664,st_size=3749,...})=0stat64(/var/lib/jenkins/jobs/buildjobname/workspace/work/projectname/module/something/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/python/python/misc/java/java/python/java/inc/misc/inc/Module.versions.release,{st_mode=S_IFREG|0644,st_size=345,...})=0stat64(/var/lib/jenkins/jobs/buildjobname/workspace/work/projectname/module/something/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/python/python/misc/java/java/python/java/inc/misc/inc/libims_call_id.exp,{st_mode=S_IFREG|0644,st_size=227,...})=0stat64(/var/lib/jenkins/jobs/buildjobname/workspace/work/projectname/module/something/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/python/python/misc/java/java/python/java/inc/misc/inc/misc,0x66b18060)=-1ELOOP(Toomanylevelsofsymboliclinks)
CVSPlugin2.11http://wiki.jenkins-ci.org/display/JENKINS/CVS+PluginJenkinsver.1.562Thisproblemwithgitpluginseemstohavebeenasimilarproblem:https://issues.jenkins-ci.org/browse/JENKINS-17186Linux:ifthereisarecursivedirectorywithinthegitrepoyourebuilding,theinitialcheckoutwillfailbadly
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [cvs] (JENKINS-23234) cvs update hang when recursive symlink in directory
James Coleman
updated JENKINS-23234
cvs update hang when recursive symlink in directory
Change By:
James Coleman
(30/May/14 11:00 AM)
Description:
Jenkinsjobhangsforeverdoingcvsupdate.Arecursivedirectorycausesjobtohangforever.Thecvscommandshowninconsolelogis:cvsupdate-d-P-rbranchtagmodApreviousbuildjobcreatedsymlinksto.insomedirectoriesincheckoutarea.Usingstracecanseeprocessisrecursingintodirectorytomultiplelevels...itishittinganerrorbutjustseemstotakeforever...notsureifjobswilleverendbyselves...postingstoptojenkinsjobdoesntwork,thejobremainsrunninguntiljenkinsitselfisrestartedORprocesskilled(whichbringsdownjenkins).Theerror:ELOOP(Toomanylevelsofsymboliclinks)stracefragment:
(miscisasymlinkto.)
stat64(/var/lib/jenkins/jobs/buildjobname/workspace/work/projectname/module/something/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/python/python/misc/java/java/python/java/inc/misc/inc/
call_id
something
.py,{st_mode=S_IFREG|0664,st_size=3749,...})=0stat64(/var/lib/jenkins/jobs/buildjobname/workspace/work/projectname/module/something/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/python/python/misc/java/java/python/java/inc/misc/inc/
Module.versions.release
something
,{st_mode=S_IFREG|0644,st_size=345,...})=0stat64(/var/lib/jenkins/jobs/buildjobname/workspace/work/projectname/module/something/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/python/python/misc/java/java/python/java/inc/misc/inc/
libims_call_id.exp
somethingelse
,{st_mode=S_IFREG|0644,st_size=227,...})=0stat64(/var/lib/jenkins/jobs/buildjobname/workspace/work/projectname/module/something/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/misc/python/python/misc/java/java/python/java/inc/misc/inc/misc,0x66b18060)=-1ELOOP(Toomanylevelsofsymboliclinks)CVSPlugin2.11http://wiki.jenkins-ci.org/display/JENKINS/CVS+PluginJenkinsver.1.562Thisproblemwithgitpluginseemstohavebeenasimilarproblem:https://issues.jenkins-ci.org/browse/JENKINS-17186Linux:ifthereisarecursivedirectorywithinthegitrepoyourebuilding,theinitialcheckoutwillfailbadly
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [cvs] (JENKINS-23234) cvs update hang when recursive symlink in directory
James Coleman commented on JENKINS-23234 cvs update hang when recursive symlink in directory Interesting to compare with behaviour of gnu cvs client. Regular cvs behaviour (generally but upon update in particular) is to ignore symlinks. See function special_file_mismatch in update.c (and function islink in filesubr.c) in cvs source code. http://cvs.savannah.gnu.org/viewvc/cvs/ccvs/src/update.c?revision=HEADview=markup Probably the same should be done by jenkins CVS Plugin. Otherwise would need to add intelligence on finding symlink loops. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [cli] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Craig Phillips created JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cli Created: 30/May/14 11:12 AM Description: I have a job that dynamically creates jobs using the CLI. I have noticed that since installing the job, which verifies the existing of jobs by calling 'get-job', Jenkins is leaking file descriptors. I am currently making around 40 calls per build, which runs on every CVS commit. I have a job setup to monitor the number of FD's in /proc/$jenkins_pid/fd. Calling garbage collection in the JVM doesn't release the FD's and thus the only cure is to restart Jenkins before the number of files reaches the Open file ulimit. I have set my ulimit to 65356 so I don't have to reboot so frequently. I restarted Jenkins at 7:49 this morning and the file descriptor count is currently at 6147 files; it's now 12:10 in the afternoon, so it's been steadily leaking FD's at approximately 1500 per hour. Project: Jenkins Labels: jenkins Priority: Major Reporter: Craig Phillips This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [delivery-pipeline] (JENKINS-23249) TokenMacro for POM_VERSION
Patrik Boström created JENKINS-23249 TokenMacro for POM_VERSION Issue Type: Improvement Assignee: Unassigned Components: delivery-pipeline Created: 30/May/14 11:24 AM Description: For Maven builds an environment variable POM_VERSION is present set to the version of the pom. This is useful to create a PIPELINE_VERSION from. But usually this is set to a SNAPSHOT version and in a pipeline SNAPSHOTS should not be used. So introduce a token macro which lookup the POM_VERSION and optionally remove the -SNAPSHOT part. Then it is possible to create PIPELINE_VERSION with $POM_VERSION.$BUILD_NUMBER. If the pom version is changed you dont need to change any configuration in Jenkins Project: Jenkins Priority: Major Reporter: Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [delivery-pipeline] (JENKINS-23249) TokenMacro for POM_VERSION
Patrik Boström updated JENKINS-23249 TokenMacro for POM_VERSION Change By: Patrik Boström (30/May/14 11:25 AM) Description: ForMavenbuildsanenvironmentvariablePOM_VERSIONispresentsettotheversionofthepom.ThisisusefultocreateaPIPELINE_VERSIONfrom.ButusuallythisissettoaSNAPSHOTversionandinapipelineSNAPSHOTSshouldnotbeused.SointroduceatokenmacrowhichlookupthePOM_VERSIONandoptionallyremovethe-SNAPSHOTpart.ThenitispossibletocreatePIPELINE_VERSIONwith$POM_VERSION.$BUILD_NUMBER. IfthepomversionischangedyoudontneedtochangeanyconfigurationinJenkins . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)
Harald Albers commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) I can confirm that the problem with push notification is resolved in 1.565. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [build-blocker] (JENKINS-23250) Failed to inspect ... build.xml warnings in jenkins log
Mohd Ali created JENKINS-23250 Failed to inspect ... build.xml warnings in jenkins log Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-blocker Created: 30/May/14 12:14 PM Description: We are getting a lot of warnings for failed to inspect build.xmls including old jobs. This also seems to be related to sudden memory consumption by jenkins which causes application to be unresponsive. Here a few details: Warning found in catalina.out log: This also seems to be related to warning like these: Failed to inspect /var/hudson/master/jobs/strucfin-core/modules/com.markit.strucfin$sf-core/builds/2011-04-09_22-30-21: /var/hudson/master/jobs/strucfin-core/modules/com.markit.strucfin$sf-core/builds/2011-04-09_22-30-21/build.xml doesn't exist Failed to inspect /var/hudson/master/jobs/strucfin-core/modules/com.markit.strucfin$sf-core/builds/2011-04-11_08-31-43: /var/hudson/master/jobs/strucfin-core/modules/com.markit.strucfin$sf-core/builds/2011-04-11_08-31-43/build.xml doesn't exist Failed to inspect /var/hudson/master/jobs/strucfin-core/modules/com.markit.strucfin$sf-core/builds/2011-04-10_17-24-25: /var/hudson/master/jobs/strucfin-core/modules/com.markit.strucfin$sf-core/builds/2011-04-10_17-24-25/build.xml doesn't exist Failed to inspect /var/hudson/master/jobs/strucfin-dcl/builds/1491: /var/hudson/master/jobs/strucfin-dcl/builds/1491/build.xml doesn't exist Failed to inspect /var/hudson/master/jobs/strucfin-dcl/builds/2011-12-08_11-45-02: /var/hudson/master/jobs/strucfin-dcl/builds/2011-12-08_11-45-02/build.xml doesn't exist Failed to inspect /var/hudson/master/jobs/strucfin-dcl/builds/2011-12-08_09-59-03: /var/hudson/master/jobs/strucfin-dcl/builds/2011-12-08_09-59-03/build.xml doesn't exist We have more people reporting this issue but no response has been received so far. http://jenkins-ci.361315.n4.nabble.com/What-is-those-quot-WARNING-Failed-to-inspect-quot-in-the-Jenkins-logs-td4689106.html Environment: OS: RHEL 5 Tomcat5/Tomcat6(DR) Jenkins 1.532.2 Project: Jenkins Priority: Critical Reporter: Mohd Ali This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [android-emulator] (JENKINS-23134) Mixed separators fail for Linux paths
Diego Costantini commented on JENKINS-23134 Mixed separators fail for Linux paths I think the problem has been introduced long ago (short after 2.10 release) in this commit: https://github.com/jenkinsci/android-emulator-plugin/commit/d49096f96884b9ac405c988afa32f467de750d82 Before, the slashes were hardcoded, now apparently somewhere File.separator returns backslashes, but I couldn't find where, and I don't have the environment to try to debug it myself. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [build-user-vars] (JENKINS-23251) BUILD_USER_ID is not set when the build is fired using the API
Carlos Becker created JENKINS-23251 BUILD_USER_ID is not set when the build is fired using the API Issue Type: Bug Assignee: Unassigned Components: build-user-vars Created: 30/May/14 1:30 PM Description: When I fire a job via API with something like: curl -v -u "$login:$token" -X POST $url -d token=$jobtoken The BUILD_USER_ID isn't set, and so my job don't work. Project: Jenkins Priority: Major Reporter: Carlos Becker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ant] (JENKINS-23207) Issue when saving/applying changes.
Mark Waite commented on JENKINS-23207 Issue when saving/applying changes. Can you provide more details so that others can duplicate the bug? For example: Jenkins version Git plugin version Git client plugin version Job type where you see the failure (and if the failure happens with other job types) Data in the job definition Cases where it does not fail, and the differences between failure and success This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-client] (JENKINS-21559) Default GIT to run 'git clone' instead of 'git fetch'
Mark Waite closed JENKINS-21559 as Wont Fix Default GIT to run git clone instead of git fetch Change By: Mark Waite (30/May/14 2:10 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-client] (JENKINS-21559) Default GIT to run 'git clone' instead of 'git fetch'
Mark Waite resolved JENKINS-21559 as Wont Fix Default GIT to run git clone instead of git fetch Because git clone has more ways in which it can block than git fetch, the plugin needs to continue to use git fetch for authenticated use cases. Change By: Mark Waite (30/May/14 2:09 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-20702) Delete old data fails with ConcurrentModificationException
Adam Hall reopened JENKINS-20702 Delete old data fails with ConcurrentModificationException This issue is happening in Jenkins 1.565 after migrating from Hudson. Here is my stack: javax.servlet.ServletException: java.util.ConcurrentModificationException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(Unknown Source) at java.util.HashMap$EntryIterator.next(Unknown Source) at java.util.HashMap$EntryIterator.next(Unknown Source) at hudson.diagnosis.OldDataMonitor.doDiscard(OldDataMonitor.java:297) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at
[JIRA] [ant] (JENKINS-23207) Issue when saving/applying changes.
Liam Newman commented on JENKINS-23207 Issue when saving/applying changes. Jenkins version: 1.565 git 2.2.1 git-client 1.9.1 Job type: Free-style software project This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [cli] (JENKINS-23248) CLI: get-job calls are causing file descriptor leaks.
Kohsuke Kawaguchi commented on JENKINS-23248 CLI: get-job calls are causing file descriptor leaks. When you look at ls -la /proc/$PID/fd output, can you tell which files are left open? Can you take a diff between two points of time and give us the delta? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [delivery-pipeline] (JENKINS-23249) TokenMacro for POM_VERSION
Kohsuke Kawaguchi commented on JENKINS-23249 TokenMacro for POM_VERSION Is this really an issue that belongs to the delivery-pipeline plugin? Is it not more about the maven-plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23244) Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master
Kohsuke Kawaguchi updated JENKINS-23244 Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master Adjusting the priority since it only affects relatively unvisited pages of large deployments. Change By: Kohsuke Kawaguchi (30/May/14 3:13 PM) Priority: Critical Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23244) Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master
Kohsuke Kawaguchi commented on JENKINS-23244 Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master Looking at the thread dump, the call stack indicates this call resulted in loading all the build records (via AbstractLazyLoadRunMap.all), which looks suspicious. I'd think this operation would only require walking newer build records. "Handling POST /computer/hadoop4/timeline/data/ : http-bio-8090-exec-895" Id=22685 Group=main RUNNABLE at java.io.UnixFileSystem.getBooleanAttributes0(Native Method) at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:242) at java.io.File.exists(File.java:813) at hudson.model.RunMap.retrieve(RunMap.java:219) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:687) - locked hudson.model.RunMap@3fa6ce65 at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:649) - locked hudson.model.RunMap@3fa6ce65 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:381) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:219) at hudson.tasks.Fingerprinter$FingerprintAction.compact(Fingerprinter.java:360) at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349) at hudson.model.Run.onLoad(Run.java:337) at hudson.model.RunMap.retrieve(RunMap.java:223) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:687) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:670) at jenkins.model.lazy.AbstractLazyLoadRunMap.all(AbstractLazyLoadRunMap.java:622) - locked hudson.model.RunMap@3fa6ce65 at jenkins.model.lazy.AbstractLazyLoadRunMap.entrySet(AbstractLazyLoadRunMap.java:277) at java.util.AbstractMap$2$1.init(AbstractMap.java:378) at java.util.AbstractMap$2.iterator(AbstractMap.java:377) at hudson.util.RunList.iterator(RunList.java:97) at com.google.common.collect.Iterables$15.apply(Iterables.java:1128) at com.google.common.collect.Iterables$15.apply(Iterables.java:1125) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at com.google.common.collect.Iterators$MergingIterator.init(Iterators.java:1306) at com.google.common.collect.Iterators.mergeSorted(Iterators.java:1274) at com.google.common.collect.Iterables$14.iterator(Iterables.java:1113) at com.google.common.collect.Iterables$UnmodifiableIterable.iterator(Iterables.java:94) at com.google.common.collect.Iterables$6.iterator(Iterables.java:585) at hudson.util.RunList$2.iterator(RunList.java:210) at hudson.util.RunList$2.iterator(RunList.java:210) at com.google.common.collect.Iterables$6.iterator(Iterables.java:585) at hudson.util.RunList.iterator(RunList.java:97) at hudson.model.BuildTimelineWidget.doData(BuildTimelineWidget.java:63) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [android-emulator] (JENKINS-23134) Mixed separators fail for Linux paths
Diego Costantini commented on JENKINS-23134 Mixed separators fail for Linux paths I worked around the issue by rolling back some line to hardcoded slashes, but before doing that, I saw that tests (on the plugin code) with slashes on Windows fail. I supposed they were performed only on Linux (or Mac), nevertheless, I don't know why on my Linux slaves I get backslashes... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [integrity-plugin] (JENKINS-22929) Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace
Martin Hohl assigned JENKINS-22929 to Unassigned Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace Change By: Martin Hohl (30/May/14 3:22 PM) Assignee: CletusDSouza This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [integrity-plugin] (JENKINS-22929) Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace
Martin Hohl updated JENKINS-22929 Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace Also occurs with Integrity plugin 1.24 and Jenkins 1.565. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [integrity-plugin] (JENKINS-22929) Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace
Martin Hohl reopened JENKINS-22929 Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace Change By: Martin Hohl (30/May/14 3:24 PM) Resolution: WontFix Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [android-emulator] (JENKINS-23252) Replace brackets for new Google APIs emulators
Diego Costantini created JENKINS-23252 Replace brackets for new Google APIs emulators Issue Type: Bug Assignee: Christopher Orr Components: android-emulator Created: 30/May/14 3:29 PM Description: Google just changed names for their system images: "Google Inc.:Google APIs (x86 System Image):19" The plugin fails because brackets are not allowed on creation as emulator name. Some replace should be used to cope with that. Project: Jenkins Priority: Major Reporter: Diego Costantini This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [integrity-plugin] (JENKINS-22929) Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace
Martin Hohl updated JENKINS-22929 Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace Change By: Martin Hohl (30/May/14 3:37 PM) Attachment: Jenkins_Integrity_1.24_Stacktrace.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23244) Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master
abayer commented on JENKINS-23244 Slave build history page has no data and spawns a ton of very long-lived blocking threads on the master fwiw, it's now looking a lot better - no blocked threads, build history's showing up for all slaves now, so far as I can tell. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22929) Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace
Cletus DSouza updated JENKINS-22929 Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace Change By: Cletus DSouza (30/May/14 3:46 PM) Component/s: core Component/s: integrity-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22929) Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace
Cletus DSouza commented on JENKINS-22929 Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace Setting component to core as I can't find anything in the stacktrace to target in the integrity-plugin code base This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [hockeyapp] (JENKINS-22848) Hockeyapp plugin can't publish from remote slaves
Jonathan Crooke commented on JENKINS-22848 Hockeyapp plugin cant publish from remote slaves Not seeing v1.1.0 on my Jenkins update list yet. Still says 1.0.6. Is this normal? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22929) Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace
Martin Hohl commented on JENKINS-22929 Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace Also can occur during "Wipe Out Current Workspace" operation. Seems not to be related to Integrity plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22929) Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace
Martin Hohl updated JENKINS-22929 Jenkins ends up with java.nio.file.DirectoryNotEmptyException while populating workspace Change By: Martin Hohl (30/May/14 3:48 PM) Attachment: Jenkins1.565SystemInformation.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [sidebar-link] (JENKINS-23253) View specific sidebar links
D Soa created JENKINS-23253 View specific sidebar links Issue Type: Improvement Assignee: Unassigned Components: sidebar-link Created: 30/May/14 4:19 PM Description: We group our Jenkins jobs by release using view tabs. It would be nice if the sidebar links could be specific to the current view, so we could add a link to, say, launch the application on a test machine for that specific release. Project: Jenkins Priority: Major Reporter: D Soa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven2] (JENKINS-23249) TokenMacro for POM_VERSION
Patrik Boström updated JENKINS-23249 TokenMacro for POM_VERSION Changing component Change By: Patrik Boström (30/May/14 4:20 PM) Priority: Major Minor Component/s: maven2 Component/s: delivery-pipeline This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ant] (JENKINS-23207) Issue when saving/applying changes.
Mark Waite commented on JENKINS-23207 Issue when saving/applying changes. That's good data, but not enough for anyone else to duplicate the problem. Can you investigate further to identify what about the specific changes you're making causes that failure, and if that failure is also visible on other versions. For example, does the same problem occur on the Jenkins Long Term Support (LTS) version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ant] (JENKINS-23207) Issue when saving/applying changes.
Mark Waite updated JENKINS-23207 Issue when saving/applying changes. Change By: Mark Waite (30/May/14 4:39 PM) Description: IgetthisstacktracewhenIclicksaveorapply:http://pastebin.com/cLjm9PuR
[JIRA] [ant] (JENKINS-23207) Issue when saving/applying changes.
Mark Waite commented on JENKINS-23207 Issue when saving/applying changes. Also, can you describe why you think that stack trace is related to the git plugin and the ant plugin? I don't see anything int he stake trace which would lead me to believe that the issue is with either of those two plugins. Are you using the git plugin in your job definition? What values are you providing to the git plugin fields? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [github-oauth] (JENKINS-23254) anonymous users can't view coverage reports of public project due to lack of workspace view privileges
Michael Crusoe created JENKINS-23254 anonymous users cant view coverage reports of public project due to lack of workspace view privileges Issue Type: Bug Assignee: Sam Kottler Components: github-oauth Created: 30/May/14 4:46 PM Description: I had to switch to the matrix-based security for authorization; I would have preferred an option to allow read access to the workspace for anonymous users. Project: Jenkins Priority: Major Reporter: Michael Crusoe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [master-slave] (JENKINS-23255) Minor network connectivity drop fails the build on slave
Devsh sharma created JENKINS-23255 Minor network connectivity drop fails the build on slave Issue Type: Bug Assignee: Unassigned Components: master-slave Created: 30/May/14 5:04 PM Description: I am trying to install a firewall based product using jenkins on my slave , product installation stops the network connectivity for fraction of second.As network goes down on slave for a fraction of second it breaks the build. is there any way to avoid build failure when this network disconnect happens ? Project: Jenkins Priority: Blocker Reporter: Devsh sharma This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
davyboyhayes created JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext, perforce Created: 30/May/14 5:04 PM Description: We upgraded from Jenkins 1.445 to 1.565, and we have a number of jobs configured for subversion, and some configured for perforce. This one job in particular, failed (after I had to kill the p4 executable on the build agent, and then ultimately the build agent itself) when it tried to generate an email list to send emails out. It appears to be attempting to get users emails from perforce, even though this one job in particular is in no way configured to use Perforce. ERROR: Publisher hudson.tasks.Mailer aborted due to exception java.lang.NullPointerException at hudson.model.Slave.createLauncher(Slave.java:359) at hudson.plugins.perforce.PerforceMailResolver.findPerforceMailAddressFor(PerforceMailResolver.java:74) at hudson.plugins.perforce.PerforceMailResolver.findMailAddressFor(PerforceMailResolver.java:25) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:112) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:547) at hudson.tasks.MailSender.buildCulpritList(MailSender.java:407) at hudson.tasks.MailSender.createEmptyMail(MailSender.java:367) at hudson.tasks.MailSender.createBackToNormalMail(MailSender.java:176) at hudson.tasks.MailSender.getMail(MailSender.java:167) at hudson.tasks.MailSender.execute(MailSender.java:101) at hudson.tasks.Mailer.perform(Mailer.java:137) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:709) at hudson.model.Build$BuildExecution.post2(Build.java:182) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:658) at hudson.model.Run.execute(Run.java:1731) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Only once I had disabled the Perforce plugin entirely, would the job complete without hanging. Environment: email-ext 2.38 perforce 1.3.27 jenkins 1.565 Project: Jenkins Labels: email-ext perforce Priority: Major Reporter: davyboyhayes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ant] (JENKINS-23207) Issue when saving/applying changes.
Liam Newman commented on JENKINS-23207 Issue when saving/applying changes. I didn't make any changes, I haven't tried any other version yet. I made it tag git and ant because I'm using them to produce the build, I'm trying to make it build a jar file whenever a change is pushed to the github project. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
davyboyhayes updated JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job Change By: davyboyhayes (30/May/14 5:07 PM) Environment: email-ext2.38perforce1.3.27jenkins1.565 mailer1.8 Component/s: mailer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
Alex Earl commented on JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job This is not a bug in email-ext. Email-ext uses the MailAddressResolver from the Mailer plugin to try and resolve email addresses. The perforce plugin implements a MailAddressResolver, it should probably check if Perforce is setup for the current job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven2] (JENKINS-23249) TokenMacro for POM_VERSION
Patrik Boström commented on JENKINS-23249 TokenMacro for POM_VERSION Create PR with a proposed implementation: https://github.com/jenkinsci/maven-plugin/pull/25 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
davyboyhayes commented on JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job Perforce is definitely not defined (I have checked the jobs config.xml for configuration) for this job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
Alex Earl commented on JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job Right, so the PerforceMailResolver should probably check that before trying to resolve the email address. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
Alex Earl assigned JENKINS-23256 to Rob Petti Job hangs trying to resolve Perforce emails, in a non-perforce job Change By: Alex Earl (30/May/14 5:15 PM) Assignee: AlexEarl RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
davyboyhayes commented on JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job Agreed, will forward on to Rob Petti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
davyboyhayes edited a comment on JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job Agreed, will forward on to Rob Petti (nvm, it already has been) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
Rob Petti assigned JENKINS-23256 to Unassigned Job hangs trying to resolve Perforce emails, in a non-perforce job Change By: Rob Petti (30/May/14 5:56 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
Rob Petti commented on JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job MailAddressResolvers are not given any indication what project they are resolving email addresses for. There's no way to skip it if the job running email-ext isn't configured for perforce, so it's forced to scan all of the projects configured for PerforceSCM objects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [jira] (JENKINS-23257) [JIRA plugin]
Adam Lane commented on JENKINS-23257 [JIRA plugin] I assume this is a bug in the jira soap api returning invalid xml to the plugin so I also created a ticket with JIRA. If you can provide the api call that is returning the bad data that might help them fix quicker: https://jira.atlassian.com/browse/JRA-38555 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
davyboyhayes edited a comment on JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job So what could have changed between these versions. I know that if I revert my snapshot of Jenkins prior to upgrading, everything builds fine, yet when I upgrade to these versions, everything goes grinds to a halt. Do you think this is an issue for the Mailer plugin then? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
davyboyhayes commented on JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job So what could have changed between these versions. I know that if I revert my snapshot of Jenkins prior to upgrading, everything builds fine, yet when I upgrade to these versions, everything goes grinds to a halt. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
Alex Earl commented on JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job The bundled mailer plugin might be a different version, can you verify if there are any updates available for Mailer in the update center? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
Rob Petti commented on JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job Can you revert, then upgrade each plugin one-by-one? That would seem to be the best way to tease out why it's hanging. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [sidebar-link] (JENKINS-23258) Complex sidebar link URL not saved
D Soa created JENKINS-23258 Complex sidebar link URL not saved Issue Type: Bug Assignee: Unassigned Components: sidebar-link Created: 30/May/14 8:01 PM Description: Tried to enter a URL like the following which resulted in an empty link (no href attr in the anchor tag) http://perforce.internal.com:5500/@md=dcd=/c=5FN@/?ac=107mx=100jsf=Jobjsf=Statusjsf=Codelinejsf=Descriptionjsf=Ownerjsf=Modifiedjsf=Defect_Refjsf=Job_controljsf=WorkItem_Refjsf=Job_Refjsf=Originatorft=%28Status=qaready%20|%20%28Status=open%20%26%20Job_control=requested%29%29%20%26%20codeline=main Environment: Jenkins 1.540 Sidebar Link 1.6 Project: Jenkins Priority: Major Reporter: D Soa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23259) userContent can been browsed by anoymous users when security is enabled and discovery is disabled
Joseph Hughes created JENKINS-23259 userContent can been browsed by anoymous users when security is enabled and discovery is disabled Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 30/May/14 8:09 PM Description: With security enabled and discovery disabled an unauthenticated user can browse any files in the userContent directory by going to http://server/userContent This can be a big security risk for those who use the copy_to_slave plugin and store sensitive files in the userContent directory. Environment: Ubuntu 14.04 Project: Jenkins Priority: Critical Reporter: Joseph Hughes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [sidebar-link] (JENKINS-23258) Complex sidebar link URL doesn't work
D Soa updated JENKINS-23258 Complex sidebar link URL doesnt work Change By: D Soa (30/May/14 8:12 PM) Summary: ComplexsidebarlinkURL notsaved doesntwork This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [sidebar-link] (JENKINS-23258) Complex sidebar link URL doesn't work
D Soa commented on JENKINS-23258 Complex sidebar link URL doesnt work Looks like it is the '|' that it doesn't like. Changing it to %7C worked. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [copyartifact] (JENKINS-23260) Copy Artifact plugin: job name not found when passed through a predefined parameter
Ivan Fetch created JENKINS-23260 Copy Artifact plugin: job name not found when passed through a predefined parameter Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 30/May/14 9:04 PM Description: When using a variable in the Project Name field of CopyArtifact, the project can not be found, although the correct project name is interpolated from the variable, as it shows up in the log (rpm.git, below): Building on master in workspace /build/jenkins/jobs/utils.rpmSign/workspace No emails were triggered. Unable to find project for artifact copy: rpm.git This may be due to incorrect project name or permission settings; see help for project name in job configuration. The "rpm.git" above, actually comes from a variable, yet the project could not be found. I have seen similar issues which were caused by project permissions - I do not think this applies to my issue, as project security is not enabled. More Background (XML snippets below also): The rpm.git project has a promotion, which triggers a built for the utils.rpmSign project. The promotion has a build parameter of it's own, for a pass phrase used with a GPG key. Any current build parameters are passed to utils.rpmSign There is a pre defined parameter: TRIGGERING_JOB=$PROMOTED_JOB_NAME - even if I set the variable directly to a string, TRIGGERING_JOB=rpm.git, I still receive the above error. The utils.rpmSign job uses CopyArtifact, and specifies a Project Name of: $TRIGGERING_JOB - while the log shows the contents of the variables, the project is still reported to not be found. Here is an XML snippet from the promotion which calls the utils.rpmSign job - in this case, I am setting TRIGGERING_JOB directly yto rpm.git, but that job name can still not be found: hudson.model.PasswordParameterDefinition namegpg_key_passphrase/name descriptionthe pass phrase for the GPG key used to sign RPMs/description defaultValueqHcBowhUDIvESDutbuVR0w==/defaultValue /hudson.model.PasswordParameterDefinition /parameterDefinitions /hudson.plugins.promoted__builds.conditions.ManualCondition /conditions iconstar-purple/icon buildSteps hudson.plugins.parameterizedtrigger.TriggerBuilder plugin="parameterized-trigger@2.22" configs hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig configs hudson.plugins.parameterizedtrigger.CurrentBuildParameters/ hudson.plugins.parameterizedtrigger.PredefinedBuildParameters propertiesTRIGGERING_JOB=rpm.git/properties /hudson.plugins.parameterizedtrigger.PredefinedBuildParameters /configs projectsutils.rpmSign/projects conditionALWAYS/condition Here is an XML snippet from the utils.rpmSign job: builders hudson.plugins.copyartifact.CopyArtifact plugin="copyartifact@1.29" project$TRIGGERING_JOB/project filter/filter target/target selector class="hudson.plugins.copyartifact.TriggeredBuildSelector"/ flattentrue/flatten doNotFingerprintArtifactstrue/doNotFingerprintArtifacts /hudson.plugins.copyartifact.CopyArtifact Environment: Jenkins ver. 1.550 Project: Jenkins Priority: Major Reporter: Ivan Fetch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you
[JIRA] [envinject] (JENKINS-19852) NPE during submission of EnvInject JobProperty configurations
recampbell reopened JENKINS-19852 NPE during submission of EnvInject JobProperty configurations Steven, I realizes this "fixes" the NPE, but I wonder if it breaks what Nicolas was trying to accomplish in 96a52696 in the first place to prevent users without RUN_SCRIPTS from editing the groovy script. Note that the groovy script is read-only without the RUN_SCRIPTS permission, but one could trivially edit the HTML to inject whatever groovy they like. So the server side check is still needed. My point is, I think we need to re-open JENKINS-19852 and let @ndeloof fix the NPE in a way which still prevents editing of the groovy in this case as desired in 96a52696. Change By: recampbell (30/May/14 9:30 PM) Resolution: Fixed Status: Resolved Reopened Assignee: GregoryBoissinot NicolasDeLoof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Clinton Barr commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted I am also seeing this issue with 1.561 and 1.565 (I updated recently), but after several reconnections on Windows Server 2008. I wrote a tool that makes the slave offline, shuts down and restarts the slave-agent.jnlp and makes the slave online again. After this project runs 6-7 times on all of my Win2008 Servers nodes, they refuse to connect, even after system reboots. Just as in previous comments, the console shows that the slave is connected and online, but the slave is not marked as online. No new builds are accepted by those nodes. I'm running as many as 75 slaves at a time and have previously been able to perform these slave-agent.jnlp restarts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [testlink] (JENKINS-18821) Jenkins-Plugin 3.5 working with Testlink 1.9.7 ?
Ashok Natarajan commented on JENKINS-18821 Jenkins-Plugin 3.5 working with Testlink 1.9.7 ? I am also running with the same issue with TestLink 1.9.8, Jenkins ver. 1.565 and TestLink Plugin 3.10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
