[JIRA] [tfs-plugin] (JENKINS-30241) Path length exception on long paths (less 260)
Title: Message Title Manfred Moser updated an issue Jenkins / JENKINS-30241 Path length exception on long paths (less 260) Change By: Manfred Moser Summary: Path lenght length exception on long paths (less 260) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view-plugin] (JENKINS-29730) MSBuild compile warnings jobs showing up in Pylint and JSLint lists
Title: Message Title Shannon Kerr commented on JENKINS-29730 Re: MSBuild compile warnings jobs showing up in Pylint and JSLint lists Any update? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-30699) ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception
Title: Message Title Ulli Hafner closed an issue as Duplicate Jenkins / JENKINS-30699 ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception Change By: Ulli Hafner Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-30699) ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception
Title: Message Title Ulli Hafner commented on JENKINS-30699 Re: ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception Seems that someone needs to improve the Doxygen parser, the regexp is even in JDK 8 not working. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Kanstantsin Shautsou commented on JENKINS-27664 Re: Job hanging, killing not possible And in the end it prints Parsing warnings in console log with parser Java Compiler (javac) null Expected Java Warnings: 0 warnings. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-30241) Path lenght exception on long paths (less 260)
Title: Message Title Manfred Moser commented on JENKINS-30241 Re: Path lenght exception on long paths (less 260) It might have NOT actually been successful with earlier versions. There was a bug that I fixed with https://github.com/jenkinsci/tfs-plugin/pull/34. With 3.2.0 and earlier TFS would checkout longer file system paths and if a longer path than the limit was found just flag the checkout as partial success and proceed. That means that it actually did NOT get all the files and continued the build anyway. At least with 4.0.0 it is now explicit and fails the build as expected rather than shadowing a problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title
Kanstantsin Shautsou edited a comment on JENKINS-27664
Re: Job hanging, killing not possible
Jenkins 1.609.3, Warnings Plug-in 4.50. Unable to abort job, only jenkins restart. {code}Parsing warnings in console log with parser Java Compiler (javac){code}Log size: 33,645 KB{code}Id=34558 Group=main RUNNABLE at java.util.regex.Pattern$Curly.match0(Pattern.java:4260) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4658) at java.util.regex.Pattern$Curly.match0(Pattern.java:4279) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$Curly.match0(Pattern.java:4279) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$BranchConn.match(Pattern.java:4568) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4717) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3798) at java.util.regex.Pattern$Curly.match0(Pattern.java:4272) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3798) at java.util.regex.Pattern$Curly.match0(Pattern.java:4272) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4658) at java.util.regex.Pattern$Branch.match(Pattern.java:4604) at java.util.regex.Pattern$Begin.match(Pattern.java:3525) at java.util.regex.Pattern$Branch.match(Pattern.java:4604) at java.util.regex.Pattern$Start.match(Pattern.java:3461) at java.util.regex.Matcher.search(Matcher.java:1248) at java.util.regex.Matcher.find(Matcher.java:637) at hudson.plugins.warnings.parser.RegexpParser.findAnnotations(RegexpParser.java:86) at hudson.plugins.warnings.parser.RegexpLineParser.parse(RegexpLineParser.java:87) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:281) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:260) at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:324) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:266) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:68) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:259) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:776) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1053) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1763) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:537) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381){code}
Add Comment
[JIRA] [tfs-plugin] (JENKINS-30451) Creating label no longer support build parameters
Title: Message Title Manfred Moser commented on JENKINS-30451 Re: Creating label no longer support build parameters Should be closed as duplicate of https://issues.jenkins-ci.org/browse/JENKINS-30442 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-20811) TFS Plugin fails ClassCastException: com.ctc.wstx.stax.WstxInputFactory cannot be cast to javax.xml.stream.XMLInputFactory
Title: Message Title Manfred Moser commented on JENKINS-20811 Re: TFS Plugin fails ClassCastException: com.ctc.wstx.stax.WstxInputFactory cannot be cast to javax.xml.stream.XMLInputFactory This should be retested and is probably resolved with 4.0.0 since it uses the Java SDK only now. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Kanstantsin Shautsou commented on JENKINS-27664 Re: Job hanging, killing not possible Ulli Hafner is it possible to run this algorithm against log? I can download log to my laptop, but i don't know plugin internals atm Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30470) User interface is really slow
Title: Message Title Christian Duchesneau closed an issue as Fixed Jenkins / JENKINS-30470 User interface is really slow Change By: Christian Duchesneau Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30470) User interface is really slow
Title: Message Title Christian Duchesneau commented on JENKINS-30470 Re: User interface is really slow Hello, sorry if I did not stick log in point. My problem was solved. I was bound to Java 1.8 32-bit on a 64-bit machine Changes: The master uses Java 1.7.9 64-bit and apply this configuration for the memory -Xms1024m -Xmx2048m -XX: PermSize 512M = -XX: MaxPermSize = 2048M Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Kanstantsin Shautsou commented on JENKINS-27664 Re: Job hanging, killing not possible Parsing warnings in console log with parser Java Compiler (javac) Log size: 33,645 KB Id=34558 Group=main RUNNABLE at java.util.regex.Pattern$Curly.match0(Pattern.java:4260) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4658) at java.util.regex.Pattern$Curly.match0(Pattern.java:4279) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$Curly.match0(Pattern.java:4279) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$BranchConn.match(Pattern.java:4568) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4717) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3798) at java.util.regex.Pattern$Curly.match0(Pattern.java:4272) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3798) at java.util.regex.Pattern$Curly.match0(Pattern.java:4272) at java.util.regex.Pattern$Curly.match(Pattern.java:4234) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4658) at java.util.regex.Pattern$Branch.match(Pattern.java:4604) at java.util.regex.Pattern$Begin.match(Pattern.java:3525) at java.util.regex.Pattern$Branch.match(Pattern.java:4604) at java.util.regex.Pattern$Start.match(Pattern.java:3461) at java.util.regex.Matcher.search(Matcher.java:1248) at java.util.regex.Matcher.find(Matcher.java:637) at hudson.plugins.warnings.parser.RegexpParser.findAnnotations(RegexpParser.java:86) at hudson.plugins.warnings.parser.RegexpLineParser.parse(RegexpLineParser.java:87) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:281) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:260) at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:324) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:266) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:68) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:259) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:776) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1053) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1763) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:537) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381)
[JIRA] [ssh-plugin] (JENKINS-30511) Enject variable into the ssh username
Title: Message Title Daniel Alejandro Hernández commented on JENKINS-30511 Re: Enject variable into the ssh username Sure, I am thinking to buld a .sh script to take some "Secret Text" password from the credentials plugin and pass it to the script as parammeter, and be sure to get this masked by Mask Plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-22251) Executing tf using the TFS Plugin throws an IO exception
Title: Message Title Manfred Moser commented on JENKINS-22251 Re: Executing tf using the TFS Plugin throws an IO exception This can probably be closed since the 4.0.0 version of the plugin uses the Java SDK only. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-27547) Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException
Title: Message Title Yayati Patil commented on JENKINS-27547 Re: Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException I am getting this issue and it is very critical. Please update when this will be fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap So sounds like something in 2.12 caused a regression. Change By: Jesse Glick Priority: Major Blocker Labels: regression Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-30726) Multiple checks on PR page if "Commit Status Context" is configured
Title: Message Title Zihao Yu created an issue Jenkins / JENKINS-30726 Multiple checks on PR page if "Commit Status Context" is configured Issue Type: Bug Assignee: Honza Brázdil Attachments: github-pr-page.png, jenkins-config.png Components: ghprb-plugin Created: 30/Sep/15 7:31 PM Environment: Jenkins 1.631 ghprb 1.29 Priority: Major Reporter: Zihao Yu I configured the "Commit Status Context" field, and on PR page, there are two checks: default, and the value I specified. The latter never finishes, while the former shows the correct test stats. Please see attached screenshots.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title
Kanstantsin Shautsou updated an issue
Jenkins / JENKINS-27664
Job hanging, killing not possible
Change By:
Kanstantsin Shautsou
I have a job that keeps hanging everytime it builds. The job ran fine in the past. No changes happend and suddenly it started hanging. ThradDump: {code} Executor #0 for Slave_rlx-v121 : executing m_techlog_reporting/zk.mtr.build #945"Executor #0 for Slave_rlx-v121 : executing m_techlog_reporting/zk.mtr.build #945" Id=79 Group=main RUNNABLE at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4692) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at
[JIRA] [jenkinslint-plugin] (JENKINS-30725) BuildTimeOut check
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-30725 BuildTimeOut check Change By: Victor Martinez Labels: 0. 3 5 .0 check Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkinslint-plugin] (JENKINS-30725) BuildTimeOut check
Title: Message Title Victor Martinez created an issue Jenkins / JENKINS-30725 BuildTimeOut check Issue Type: Task Assignee: Victor Martinez Components: jenkinslint-plugin Created: 30/Sep/15 6:10 PM Labels: 0.3.0 check Priority: Minor Reporter: Victor Martinez When using gradle plugin it is worth using Gradle Wrapper configuration and avoid using standalone installations since gradle does support wrappers within the source code. https://docs.gradle.org/current/userguide/gradle_wrapper.html Add Comment
[JIRA] [git-plugin] (JENKINS-26587) Checkout fails with Multiple SCMs plugin on commit notification
Title: Message Title Vasili Kvockin commented on JENKINS-26587 Re: Checkout fails with Multiple SCMs plugin on commit notification updated pull request with latest master Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Ulli Hafner commented on JENKINS-27664 Re: Job hanging, killing not possible How long did you wait? 22 MByte is quite a large log file but should be manageable. One problem could be the number of warnings that are generated. How many did you expect? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Kanstantsin Shautsou commented on JENKINS-27664 Re: Job hanging, killing not possible 4 hours, and can't abort, only jenkins restart helps. Usually build takes 30 min where scan for warnings takes < 1 min. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-30712) Target phrase and skip build phrase could search pull request titles too
Title: Message Title Scott MacGregor created an issue Jenkins / JENKINS-30712 Target phrase and skip build phrase could search pull request titles too Issue Type: Improvement Assignee: Honza Brázdil Components: ghprb-plugin Created: 30/Sep/15 7:20 AM Environment: running version 1.29 Labels: workflow Priority: Minor Reporter: Scott MacGregor It would be useful if skip build phrase and target phrase searched the pull request title in addition to the pull request body. For background we have a single git repository that contains an IOS and Android application. Our PR titles look like: [Android]Here's a cool bug fix that does great things or [iOS]Here's an iOS bug fix that is also awesome. We use git pull requester builder to kick off an IOS unit test job on Jenkins when a pull request is open. I'd love to be able to skip the job if the PR title contained [Android] . Thanks for
[JIRA] [remoting] (JENKINS-26855) Unreachable objects "remoting.Channel" can not garbage collect
Title: Message Title stephenconnolly commented on JENKINS-26855 Re: Unreachable objects "remoting.Channel" can not garbage collect Looks exactly like JENKINS-28844 to me Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-29079) Externals With(out) additional credentials is not clear
Title: Message Title Rene Affourtit commented on JENKINS-29079 Re: Externals With(out) additional credentials is not clear Emil Styrke As far as I understand it this is exactly what the credentials system is for. Server A asking for authentication is different credentials then server B. I'm not deep enough into the details to know if it is possible to fake the server id on which the credentials are chosen . So when someone adds an external to EvilServer with the intention to intercept your password you get the failure 'no credential to try' without the credentials for server A and B being tried. When you DO need a repository over multiple servers, this is where the additional credentials option is intended for. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-30241) Path lenght exception on long paths (less 260)
Title: Message Title Alexey Larsky commented on JENKINS-30241 Re: Path lenght exception on long paths (less 260) For example lenght 252: D:\jenkins-slave\workspace\zzz zzz\src\Modules\ResourceLibrary\Desktop\zzz.zzz.zzz\Service References\ResourceLibraryProxy\aaa.aaa.WcfRepositories.ResourceLibraryProxy.ResourceInfo.datasource Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-29079) Externals With(out) additional credentials is not clear
Title: Message Title Emil Styrke commented on JENKINS-29079 Re: Externals With(out) additional credentials is not clear I don't ever want to send any credentials to a server other than the one I've specified for the main repository, while still automatically fetching externals from that same server. Is there some technical limitation preventing this, or is there another security problem there that I don't see? Basically, what I propose is the same as "1: remove the need for additional credentials when all items in a project require the same credentials.", but with the added restriction that all items must originate from the same subversion server: 3: remove the need for additional credentials when all items in a project are served by the same server and require the same credentials. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves-plugin] (JENKINS-24323) Could not copy slave.jar into '/users/ccfw73' on slave
Title: Message Title Asmund Ostvold commented on JENKINS-24323 Re: Could not copy slave.jar into '/users/ccfw73' on slave From the comments this looks like it should be closed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Title: Message Title Jesse Glick started work on JENKINS-22252 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Title: Message Title Jesse Glick commented on JENKINS-22252 Re: Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap git bisect indicates the fix of JENKINS-26947 as the culprit. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Ulli Hafner commented on JENKINS-27664 Re: Job hanging, killing not possible Yes, clone the plug-in and start JavacParserTest and replace the file issue14043.txt with your log file content. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Title: Message Title Jesse Glick updated JENKINS-22252 Jenkins / JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Change By: Jesse Glick Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27664) Job hanging, killing not possible
Title: Message Title Ulli Hafner commented on JENKINS-27664 Re: Job hanging, killing not possible Or use the test ParserSpeed to see the speed of each parser. Here you need to fill all.txt with your log file content. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-30727) Workspace corrupt after cancelling build during svn switch
Title: Message Title Shannon Kerr created an issue Jenkins / JENKINS-30727 Workspace corrupt after cancelling build during svn switch Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 30/Sep/15 9:01 PM Environment: Slave is Windows 7 x64 Master is Ubuntu 12.04 Priority: Minor Reporter: Shannon Kerr Process: My last build was for branch1. I start a build for branch2. I cancel my build during the svn switch to the new branch on the Windows 7 slave leaving me with a workspace of partial branch1 and partial branch2. I start my branch2 build again. Jenkins svn plugin thinks I have branch2 in my workspace so it does an update for the current timestamp. I still have a mix of branch1 and branch2, just updated. My build is a mix of two different branches. At first, it's not easy to see what's going on. It wasn't until I went into two different directory trees within that workspace that I did "svn info" and found that I was in two different branches.
[JIRA] [tfs-plugin] (JENKINS-26676) Global TFS configuration does not account for different OS Paths
Title: Message Title Manfred Moser closed an issue as Fixed Jenkins / JENKINS-26676 Global TFS configuration does not account for different OS Paths Change By: Manfred Moser Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-30714) Changing product bundle identifier is not it in all the places.
Title: Message Title Luca Torella closed an issue as Not A Defect Actually I had another issue, I just needed to add "CODE_SIGN_RESOURCE_RULES_PATH=$(SDKROOT)/ResourceRules.plist" Jenkins / JENKINS-30714 Changing product bundle identifier is not it in all the places. Change By: Luca Torella Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage-plugin] (JENKINS-30715) Disk Usage Plugin Crashes Java, Crashes WebSphere Server
Title: Message Title Bruce Coveny updated an issue Jenkins / JENKINS-30715 Disk Usage Plugin Crashes Java, Crashes WebSphere Server Change By: Bruce Coveny Environment: JENKINS WAR VERSION 1.626 WINDOWS SERVER 2008 R2 ENTERPRISE AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS) 6.0 GB RAM 64-BIT OPERATION SYSTEM WEBSPHERE APPLICATION SERVER 8.5.5.6 JAVA 1.7.1 disk-usage-plugin 0.27 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-6856) Git builds with detached head no matter what
Title: Message Title cedd burge commented on JENKINS-6856 Re: Git builds with detached head no matter what I agree, this doesn't seem to have been fixed, and it would help me if it was. It seems like an easy change too. I wonder if there is a complication that we aren't aware of? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-30064) Optionally retry Sauce Connect failures when not related to credentials
Title: Message Title Val Redchenko commented on JENKINS-30064 Re: Optionally retry Sauce Connect failures when not related to credentials This would be a great improvement in my opinion. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30713) FAILED status reported for interrupted build
Title: Message Title Yoann Dubreuil updated an issue Jenkins / JENKINS-30713 FAILED status reported for interrupted build Change By: Yoann Dubreuil Component/s: core Component/s: copy-to-slave-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage-plugin] (JENKINS-30715) Disk Usage Plugin Crashes Java, Crashes WebSphere Server
Title: Message Title Bruce Coveny created an issue Jenkins / JENKINS-30715 Disk Usage Plugin Crashes Java, Crashes WebSphere Server Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage-plugin Created: 30/Sep/15 10:56 AM Environment: JENKINS WAR VERSION 1.626 WINDOWS SERVER 2008 R2 ENTERPRISE AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (2 PROCESSORS) 6.0 GB RAM 64-BIT OPERATION SYSTEM WEBSPHERE APPLICATION SERVER 8.5.5.6 JAVA 1.7.1 Priority: Critical Reporter: Bruce Coveny Since the last plugin up the server has crashed 3 out 6 days. The crash is shown as a prompt on the server saying that Java has stopped running. The disk-usage plugin was the only update that has been done to the server. Log Name: Application Source: Application Error Date: 9/29/2015 11:16:55 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: [COMPUTERNAME] Description: Faulting application name: java.exe, version: 7.0.0.0, time stamp: 0x552cec04 Faulting module name: ntdll.dll, version: 6.1.7601.18933, time stamp: 0x55a6a196 Exception code: 0xc0fd Fault offset: 0x000510a1 Faulting process id: 0x36c Faulting application start time: 0x01d0fb244f4c8870 Faulting application path: %WEBSPHERE_DIR%\AppServer\java_1.7.1_64\bin\java.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id:
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-30512) using ifconfig docker0 cannot get the IP address of the host for the docker command
Title: Message Title Yoann Dubreuil closed an issue as Fixed Fixed released in 1.6.1 Jenkins / JENKINS-30512 using ifconfig docker0 cannot get the IP address of the host for the docker command Change By: Yoann Dubreuil Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-30708) Don't crawl bintray to compute packer and groovy catalogs
Title: Message Title Yoann Dubreuil updated an issue Jenkins / JENKINS-30708 Don't crawl bintray to compute packer and groovy catalogs Change By: Yoann Dubreuil +underlined text+ In the end of [august|https://github.com/jenkinsci/backend-crawler/pull/36] the catalog to download packer binaries was broken because the recorded URL was something likehttp://dl.bintray.com/mitchellh/packer/#packer_VERSION_linux_amd64.zip instead ofhttp://dl.bintray.com/mitchellh/packer/%packer_VERSION_linux_amd64.zipIt is now again broken because it ishttp://dl.bintray.com/mitchellh/packer/:packer_VERSION_linux_amd64.zipthis change (# -> % -> : ->) is regularly done by Bintray to avoid web crawlersAfter discussing with JFrog team the solution is to avoid to do HTML scraping and to use bintray APIs3 tools installers catalogs are using bintray nowadays:* https://github.com/jenkinsci/backend-crawler/blob/master/groovy.groovy* https://github.com/jenkinsci/backend-crawler/blob/master/packer.groovy* https://github.com/jenkinsci/backend-crawler/blob/master/sbt.groovyOnly SBT script is using bintray APIs. groovy and packer are using HTML scraping and should be updated to use Bintray APIs to be sure to not hardcode any URL pattern.Note that it won't fully solve the problem of the inability to download packer (and groovy) installers because:* Our catalog is updated every 4h thus we may have a delay where URLs in catalog are broken because they changed on bintray side* AFAIK users don't have the ability to force the update of catalogs on a jenkins instance. It occurs when Jenkins is restarted (and maybe periodically ?). Thus they'll have to wait for a restart (or scheduled update) to retrieve the fixed version of a catalog Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [groovy-plugin] (JENKINS-30708) Don't crawl bintray to compute packer and groovy catalogs
Title: Message Title Yoann Dubreuil updated an issue Jenkins / JENKINS-30708 Don't crawl bintray to compute packer and groovy catalogs Change By: Yoann Dubreuil +underlined text+ In the end of [august|https://github.com/jenkinsci/backend-crawler/pull/36] the catalog to download packer binaries was broken because the recorded URL was something likehttp://dl.bintray.com/mitchellh/packer/#packer_VERSION_linux_amd64.zip instead ofhttp://dl.bintray.com/mitchellh/packer/%packer_VERSION_linux_amd64.zipIt is now again broken because it ishttp://dl.bintray.com/mitchellh/packer/:packer_VERSION_linux_amd64.zipthis change (# -> % -> : ->) is regularly done by Bintray to avoid web crawlersAfter discussing with JFrog team the solution is to avoid to do HTML scraping and to use bintray APIs3 tools installers catalogs are using bintray nowadays:* https://github.com/jenkinsci/backend-crawler/blob/master/groovy.groovy* https://github.com/jenkinsci/backend-crawler/blob/master/packer.groovy* https://github.com/jenkinsci/backend-crawler/blob/master/sbt.groovyOnly SBT script is using bintray APIs. groovy and packer are using HTML scraping and should be updated to use Bintray APIs to be sure to not hardcode any URL pattern.Note that it won't fully solve the problem of the inability to download packer (and groovy) installers because:* Our catalog is updated every 4h thus we may have a delay where URLs in catalog are broken because they changed on bintray side* AFAIK users don't have the ability to force the update of catalogs on a jenkins instance. It occurs when Jenkins is restarted (and maybe periodically ?). Thus they'll have to wait for a restart (or scheduled update) to retrieve the fixed version of a catalog Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [copy-to-slave-plugin] (JENKINS-30713) FAILED status reported for interrupted build
Title: Message Title Yoann Dubreuil created an issue Jenkins / JENKINS-30713 FAILED status reported for interrupted build Issue Type: Bug Assignee: Vivekanand SV Components: copy-to-slave-plugin Created: 30/Sep/15 9:30 AM Environment: core 1.596 Priority: Major Reporter: Yoann Dubreuil Aborting a build while artifacts are being copied through the remoting channel results in a FAILED status instead of an ABORTED status. After discussing this with Jesse Glick, he provided me hints on how to fix that, I quote him: FastPipedInputStream.read could be made to throw InterruptedIOException rather than a generic IOException. Then FilePath.readFromTar could rethrow either InterruptedIOException or another InterruptedException as an InterruptedException with details about the tar entry (the signatures of its callers allow InterruptedException). Proving this all works in a test could be tricky, since you would need to have a special remoting channel that deliberately hangs at a specific point (the code in the mock-slave plugin could perhaps be ported to a test utility). Stack trace on build log: java.io.IOException:
[JIRA] [log-parser-plugin] (JENKINS-27208) Make Log Parser Plugin compatible with Workflow
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27208 Re: Make Log Parser Plugin compatible with Workflow Nigel Harniman The main source code modifications were done. I'm waiting the maintainer so that this PR can be merged. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30365) I'm getting an error message when opening Jenkins
Title: Message Title Patrick Laurent updated an issue Jenkins / JENKINS-30365 I'm getting an error message when opening Jenkins Change By: Patrick Laurent Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-30714) Changing product bundle identifier is not it in all the places.
Title: Message Title Luca Torella created an issue Jenkins / JENKINS-30714 Changing product bundle identifier is not it in all the places. Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2015-09-30 at 10.36.14.png, Screen Shot 2015-09-30 at 10.41.34.png Components: xcode-plugin Created: 30/Sep/15 9:41 AM Environment: Jenkins ver. 1.629 Xcode integration 1.4.9 Priority: Critical Reporter: Luca Torella I'm setting up Jenkins to automate the build process. In particular, for my needs, I'd like to be able to set different bundle identifiers. I'm using the Xcode Jenkins plugin to set the bundle identifier: The problem is that this will change the bundle identifier in the Info.plist file and in MyTarget > General > Bundle Identifier. But it won't change the bundle identifier in Build Settings > Packaging > Product Bundle Identifier.
[JIRA] [sauce-ondemand-plugin] (JENKINS-30064) Optionally retry Sauce Connect failures when not related to credentials
Title: Message Title Leo Gallucci commented on JENKINS-30064 Re: Optionally retry Sauce Connect failures when not related to credentials For now I'm no longer using the plugin and connecting through shell scripting inside my docker container. How to install it: https://github.com/elgalu/docker-selenium/blob/95bd73db/Dockerfile#L498 How to retry via `$SAUCE_TUNNEL_MAX_RETRY_ATTEMPTS`: https://github.com/elgalu/docker-selenium/blob/95bd73db/saucelabs/bin/start-saucelabs.sh#L41 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-30064) Optionally retry Sauce Connect failures when not related to credentials
Title: Message Title Val Redchenko commented on JENKINS-30064 Re: Optionally retry Sauce Connect failures when not related to credentials Ditching the plugin in favor of shell scripting is our plan B, but it would still be nice to get the plugin retry connection out of the box. Looking through Sauce on Demand sources - if I can get it working I'll share it here. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29807) NullPointerException when triggering dependent builds
Title: Message Title Sverre Moe edited a comment on JENKINS-29807 Re: NullPointerException when triggering dependent builds Actually It is semantics, but actually JENKINS-29876 is the duplicate, since this issue was reported 5 days before. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [summary_report-plugin] (JENKINS-30717) summary report injects href not working when choosing "show on project page"
Title: Message Title ronen hoffer created an issue Jenkins / JENKINS-30717 summary report injects href not working when choosing "show on project page" Issue Type: Improvement Assignee: Unassigned Components: summary_report-plugin Created: 30/Sep/15 1:07 PM Environment: Linux Jenkins 3.13.0-57-generic #95~precise1-Ubuntu x86_64 x86_64 x86_64 GNU/Linux java version "1.8.0_40" chrome 45 installed form deb file Priority: Major Reporter: ronen hoffer I'm creating an xml with href section the sends to another job on my jenkins server. The problem accrues when I'm checking the "show on project page" option. When I click on the link in the project page it sends me to the wrong path... For example, my href address is /view/SECTION/job/JOB_NAME/ Normally it works fine and I'm getting the right page, but on project page it looks like this: /BUILD_NUM/view/SECTION/job/JOB_NAME/ And this path doesn't exists... It looks like the plugin auto injects the build number in the project page...
[JIRA] [core] (JENKINS-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov updated an issue
Jenkins / JENKINS-30719
cannot specify ${something} string in parameters
Change By:
akostadinov
Not sure I've got correct component. Anyway, when I try to put a parameter value of containing literal `${something}` then exception is thrown. If I escape it like `\${something}`, then it works but value is passed down with the `\` character instead of having it removed. So AFAIU there is no way to pass down literal `${}` as a parameter with jenkins.Here's an exception: {code} javax.servlet.ServletException: java.lang.IllegalArgumentException: Illegal choice for parameter IMAGE_PRE: registry.access.redhat.com/openshift3/ose-${component}:${version} {code:java} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java: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:123) at com.sonymobile.jenkins.plugins.kerberossso.KerberosSSOFilter.doFilter(KerberosSSOFilter.java:208) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:85) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [exclusion-plugin] (JENKINS-30720) Log text should be updated when waiting for another task than the one mentioned
Title: Message Title Kim Nyhjem created an issue Jenkins / JENKINS-30720 Log text should be updated when waiting for another task than the one mentioned Issue Type: New Feature Assignee: Unassigned Components: exclusion-plugin Created: 30/Sep/15 1:31 PM Priority: Minor Reporter: Kim Nyhjem It is frustrating for the users, when they see that the "Waiting for" job has finished, but they are still locked (because another job got the resource first), only now they can't see why, or who is the blocker. Suggestion is that the log for jobs waiting for the same resource should be updated every time the resource is passed to another job. (would be nice to be able to see the whole queue if possible) Add Comment
[JIRA] [core] (JENKINS-29807) NullPointerException when triggering dependent builds
Title: Message Title Sverre Moe commented on JENKINS-29807 Re: NullPointerException when triggering dependent builds Actually JENKINS-29876 is the duplicate, since this issue was reported 5 days before. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [summary_report-plugin] (JENKINS-30717) summary report href not working properly when choosing "show on project page"
Title: Message Title ronen hoffer updated an issue Jenkins / JENKINS-30717 summary report href not working properly when choosing "show on project page" Change By: ronen hoffer Summary: summary report injects href not working properly when choosing "show on project page" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29807) NullPointerException when triggering dependent builds
Title: Message Title Daniel Beck commented on JENKINS-29807 Re: NullPointerException when triggering dependent builds True. I decided to resolve this way because that other issue has a similar number of watchers/votes, but the attention of Kostya. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-30716) Gerrit plugin quiet period
Title: Message Title Jan Lutenko created an issue Jenkins / JENKINS-30716 Gerrit plugin quiet period Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger-plugin Created: 30/Sep/15 12:33 PM Environment: Jenkins 1580.3, gerrit trigger plugin 2.14.0 Labels: configuration workflow Priority: Minor Reporter: Jan Lutenko Add posibility to turn on the quiet period to group changes in batches: if a new change is merge within quiet period - reset the quiet period instead of adding another build to the queue. Would that be possible? The situation in which I currently am is that I'm using gerrit plugin to trigger builds for gerrit's awesome replication event feature which lets me to wait for the change to be replicated to mirror repository. The problem is that when multiple changes come in a batch - all of them are reflected as instances of a build. Now with SCM trigger it is possible to overcome this by adding a quiet period, but with gerrit trigger this doesn't
[JIRA] [build-pipeline-plugin] (JENKINS-25427) Build Pipleline Plugin no longer allows starting build with parameters
Title: Message Title Fabricio Leotti commented on JENKINS-25427 Re: Build Pipleline Plugin no longer allows starting build with parameters Hello! I was facing the same issue using 1.4.8 and Jenkins 1.609.1. I changed the fancybox version to the patched version above and to official version 2.1.5 (http://fancyapps.com/fancybox/). Worked fine in both cases. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-30714) Changing product bundle identifier is not it in all the places.
Title: Message Title Luca Torella reopened an issue actually bug is still there Jenkins / JENKINS-30714 Changing product bundle identifier is not it in all the places. Change By: Luca Torella Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [summary_report-plugin] (JENKINS-30717) summary report href not working properly when choosing "show on project page"
Title: Message Title ronen hoffer updated an issue Jenkins / JENKINS-30717 summary report href not working properly when choosing "show on project page" Change By: ronen hoffer Environment: Linux Jenkins 3.13.0-57-generic #95~precise1-Ubuntu x86_64 x86_64 x86_64 GNU/Linuxjava version "1.8.0_40"chrome 45installed form deb file Summary Display Plugin 1.13 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov created an issue
Jenkins / JENKINS-30719
cannot specify ${something} string in parameters
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
30/Sep/15 1:19 PM
Priority:
Major
Reporter:
akostadinov
Not sure I've got correct component. Anyway, when I try to put a parameter value of containing literal `$ {something}` then exception is thrown. If I escape it like `\${something}
`, then it works but value is passed down with the `\` character instead of having it removed. So AFAIU there is no way to pass down literal `${}` as a parameter with jenkins.
Here's an exception: javax.servlet.ServletException: java.lang.IllegalArgumentException: Illegal choice for parameter IMAGE_PRE: registry.access.redhat.com/openshift3/ose-$ {component}:${version}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at
[JIRA] [disk-usage-plugin] (JENKINS-30718) Jenkins log filled with disk-usage status
Title: Message Title
John Flynn created an issue
Jenkins / JENKINS-30718
Jenkins log filled with disk-usage status
Issue Type:
Improvement
Assignee:
Lucie Votypkova
Components:
disk-usage-plugin
Created:
30/Sep/15 1:19 PM
Priority:
Minor
Reporter:
John Flynn
Can there be a global option or just remove the output that is going to the jenkins.log file. The log is filled with this output and makes it hard to locate real issues. Also seeing this multiple times for each build as it is running. The more builds a project contains, the worse the problem.
Ex: System.out.println("create build disk usage for build " + build + " of project " + build.getProject().getDisplayName()); System.out.println("information is null"); System.out.println("information " + information);
Add Comment
[JIRA] [jira-plugin] (JENKINS-13436) Message logged by JIRA plugin should mention that the message relates to a Jenkins job.
Title: Message Title Radek Antoniuk resolved as Fixed Will be released in v. 2.1. Jenkins / JENKINS-13436 Message logged by JIRA plugin should mention that the message relates to a Jenkins job. Change By: Radek Antoniuk Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-13436) Message logged by JIRA plugin should mention that the message relates to a Jenkins job.
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-13436 Message logged by JIRA plugin should mention that the message relates to a Jenkins job. Change By: Radek Antoniuk Labels: jira-plugin-2.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29876) NPE when triggering downstream job
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-29876 NPE when triggering downstream job Change By: Kanstantsin Shautsou Summary: NPE when triggering downstream job (again) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clover-plugin] (JENKINS-27302) Make CloverPublisher a SimpleBuildStep
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27302 Re: Make CloverPublisher a SimpleBuildStep owenmehegan I hope getting results soon. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-30682) JIRA ticket creation failing with java.lang.NullPointerException
Title: Message Title Radek Antoniuk commented on JENKINS-30682 Re: JIRA ticket creation failing with java.lang.NullPointerException Yeap, sorry, I meant component. You're also right about the Validate Settings button, AFAIR I fixed this in master already but it's not there yet in 2.0.2. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-28453) No known JIRA project corresponding to id: 'RCFOPS-112'
Title: Message Title Radek Antoniuk resolved as Not A Defect Thanks! Jenkins / JENKINS-28453 No known JIRA project corresponding to id: 'RCFOPS-112' Change By: Radek Antoniuk Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-26385) Jira Plugin: "Generate release notes" not work
Title: Message Title Radek Antoniuk resolved as Cannot Reproduce Jenkins / JENKINS-26385 Jira Plugin: "Generate release notes" not work Change By: Radek Antoniuk Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clover-plugin] (JENKINS-27302) Make CloverPublisher a SimpleBuildStep
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-27302 Make CloverPublisher a SimpleBuildStep Change By: Manuel Jesús Recena Soto Assignee: stephenconnolly Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-28733) Performance Plugin not showing URI's details in Graph
Title: Message Title Sargon Benjamin commented on JENKINS-28733 Re: Performance Plugin not showing URI's details in Graph I am also unable to see the URI's details in the graph when using the jtl file Report format is: Response Assertion false false Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-30682) JIRA ticket creation failing with java.lang.NullPointerException
Title: Message Title Radek Antoniuk commented on JENKINS-30682 Re: JIRA ticket creation failing with java.lang.NullPointerException I was able to replicate NPE like yours when the assignee field had a non-existent entry. Other than that I got a different error. does the JIRA connection validate in configuration and JIRA connection is working fine for other things? can you try doing curl with exact the same data? (e.g. with category included) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-30682) JIRA ticket creation failing with java.lang.NullPointerException
Title: Message Title Thom Wilhelm edited a comment on JENKINS-30682 Re: JIRA ticket creation failing with java.lang.NullPointerException Hi [~warden] the "Validate Settings" button I've found to be almost useless, if I change the URL to something completely random https://fjjfs.sdggdsdgssdg.xyz , or fill out the username/password to deliberately invalid credentials I still receive "Success". It's almost like this check doesn't actually connect to the server, it just validates the fields are filled out.I'll experiment with entering an assignee, although I had already tried this I believe. I'll get back to you after I've conducted some more CURL tests. What do you mean "with category included", is this similar to project key or component? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-30682) JIRA ticket creation failing with java.lang.NullPointerException
Title: Message Title Thom Wilhelm commented on JENKINS-30682 Re: JIRA ticket creation failing with java.lang.NullPointerException Hi Radek Antoniuk the "Validate Settings" button I've found to be almost useless, if I change the URL to something completely random https://fjjfs.sdggdsdgssdg.xyz I still receive "Success". It's almost like this check doesn't actually connect to the server, it just validates the fields are filled out. I'll experiment with entering an assignee, although I had already tried this I believe. I'll get back to you after I've conducted some more CURL tests. What do you mean "with category included", is this similar to project key or component? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Radek Antoniuk commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin I've just tested with Jenkins 1.609.3, git-plugin 2.4.0, jira-plugin 2.0.2 and it works for me. Also tried downgrading the plugins, still was unable to replicate. To note, I don't have "Safe HTML" option, AFAIR this is an old naming, now I have "Escaped HTML" and "Raw HTML". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-plugin-gateway] (JENKINS-30728) cloudbees-plugin-gateway JIRA component naming
Title: Message Title
Ben Walding created an issue
Jenkins / JENKINS-30728
cloudbees-plugin-gateway JIRA component naming
Issue Type:
Task
Assignee:
Unassigned
Components:
cloudbees-plugin-gateway
Created:
01/Oct/15 12:16 AM
Priority:
Minor
Reporter:
Ben Walding
The Jenkins wiki plugin for jenkins-plugin-info automatically suffixes a -plugin onto the jiraComponent setting.
e.g.
{jenkins-plugin-info:cloudbees-plugin-gateway|jiraComponent=cloudbees-plugin-gateway|sourceDir=cloudbees-plugin-gateway}
Creates a link to Open Issues - i.e. it is searching for a component "cloudbees-plugin-gateway-plugin"
This is a problem - as the component in JIRA is only "cloudbees-plugin-gateway"
The most expeditious way to fix this is to rename the component in JIRA to "cloudbees-plugin-gateway-plugin" - other solutions are possible but would entail rewriting a lot of pages in the wiki to have the full names of the plugin (i.e. change jiraComponent to be the full name, and then change every other plugin to have -plugin suffix included).
A keen script writer could use the Confluence API to do this if it was deemed appropriate. The jenkins-plugin-info macro would need to be updated prior.
[JIRA] [junit-plugin] (JENKINS-30729) Malformed xml prevents junit file from being closed.
Title: Message Title Evan Benn created an issue Jenkins / JENKINS-30729 Malformed xml prevents junit file from being closed. Issue Type: Bug Assignee: Unassigned Attachments: munit.xml Components: junit-plugin Created: 01/Oct/15 4:47 AM Environment: Jenkins 1.628 Junit 1.9 Priority: Critical Reporter: Evan Benn Our unit test suite occasionally dumps a malformed XML file. The file fails to be parsed and causes the build to fail, however on the next job on the agent the junit xml file cannot be deleted: 13:32:23 [***-unit] $ p4 -d C:\jenkins\***-unit -x- have 13:32:29 Could not remove file: C:\jenkins\***-unit\results\***\munit.xml caused by 13:32:29 C:\jenkins\***-unit\***\munit.xml: The process cannot access the file because it is being used by another process. 13:32:29 13:32:29 WARNING: Problem deleting file during
[JIRA] [gerrit-trigger-plugin] (JENKINS-30620) Enforcing Forbidden File path to take priority over File path shall be a configurable
Title: Message Title Scott Hebert started work on JENKINS-30620 Change By: Scott Hebert Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-30620) Enforcing Forbidden File path to take priority over File path shall be a configurable
Title: Message Title Scott Hebert assigned an issue to Scott Hebert Jenkins / JENKINS-30620 Enforcing Forbidden File path to take priority over File path shall be a configurable Change By: Scott Hebert Assignee: rsandell Scott Hebert Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-30729) Malformed xml prevents junit file from being closed.
Title: Message Title
Evan Benn commented on JENKINS-30729
Re: Malformed xml prevents junit file from being closed.
This is the junit report: {expand}
munit.xml.
Stack Trace
Failed to read test report file /var/lib/jenkins/workspace/junit_debug/munit.xml
org.dom4j.DocumentException: Error on line 2 of document file:///var/lib/jenkins/workspace/junit_debug/munit.xml : Element type "testcase" must be followed by either attribute specifications, ">" or "/>". Nested exception: Element type "testcase" must be followed by either attribute specifications, ">" or "/>".
at org.dom4j.io.SAXReader.read(SAXReader.java:482)
at org.dom4j.io.SAXReader.read(SAXReader.java:264)
at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:123)
at hudson.tasks.junit.TestResult.parse(TestResult.java:282)
at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:228)
at hudson.tasks.junit.TestResult.parse(TestResult.java:163)
at hudson.tasks.junit.TestResult.parse(TestResult.java:146)
at hudson.tasks.junit.TestResult.(TestResult.java:122)
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:119)
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:93)
at hudson.FilePath.act(FilePath.java:991)
at hudson.FilePath.act(FilePath.java:969)
at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:90)
at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:120)
at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:137)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:75)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)
at hudson.model.Build$BuildExecution.post2(Build.java:185)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671)
at hudson.model.Run.execute(Run.java:1766)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:408)
Caused by: org.xml.sax.SAXParseException; systemId: file:///var/lib/jenkins/workspace/junit_debug/munit.xml; lineNumber: 2; columnNumber: 47; Element type "testcase" must be followed by either attribute specifications, ">" or "/>".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1436)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.seekCloseOfStartTag(XMLDocumentFragmentScannerImpl.java:1395)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:264)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2786)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:117)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at
[JIRA] [android-emulator-plugin] (JENKINS-27456) Emulator can't connect to adb server!?
Title: Message Title Jonathan Strickland commented on JENKINS-27456 Re: Emulator can't connect to adb server!? Related to https://issues.jenkins-ci.org/browse/JENKINS-11952 ... I see this is where a change took place to fix some instability but as noted here with the latest version downloaded from the job (Downloading and installing Android SDK from http://dl.google.com/android/android-sdk_r24.0.2-linux.tgz) the syntax localhost: doesn't appear to be valid: /android_gradle_integration_matrix/label/trust-reg-3.cisco.com $ /home/testuser/tools/android-sdk/tools/android list target [android] Using Android SDK: /home/testuser/tools/android-sdk $ /home/testuser/tools/android-sdk/platform-tools/adb start-server * daemon not running. starting it now on port 8711 * * daemon started successfully * $ /home/testuser/tools/android-sdk/platform-tools/adb start-server [android] Starting Android emulator $ /home/testuser/tools/android-sdk/tools/emulator -ports 8709,8710 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_160_HVGA_android-16_armeabi-v7a -no-snapshot-load -no-snapshot-save -no-window -noaudio $ /home/testuser/tools/android-sdk/platform-tools/adb connect localhost:8710 unable to connect to localhost:8710: Connection refused [android] Waiting for emulator to finish booting... $ /home/testuser/tools/android-sdk/platform-tools/adb -s localhost:8710 shell getprop init.svc.bootanim error: device 'localhost:8710' not found $ /home/testuser/tools/android-sdk/platform-tools/adb connect localhost:8710 $ /home/testuser/tools/android-sdk/platform-tools/adb -s localhost:8710 shell getprop init.svc.bootanim error: device 'localhost:8710' not found $ /home/testuser/tools/android-sdk/platform-tools/adb connect localhost:8710 $ /home/testuser/tools/android-sdk/platform-tools/adb -s localhost:8710 shell getprop init.svc.bootanim error: device 'localhost:8710' not found $ /home/testuser/tools/android-sdk/platform-tools/adb disconnect localhost:8710 error: no such device 'localhost:8710' $ /home/testuser/tools/android-sdk/platform-tools/adb connect localhost:8710 $ /home/testuser/tools/android-sdk/platform-tools/adb -s localhost:8710 shell getprop init.svc.bootanim error: device 'localhost:8710' not found $ /home/testuser/tools/android-sdk/platform-tools/adb connect localhost:8710 $ /home/testuser/tools/android-sdk/platform-tools/adb -s localhost:8710 shell getprop init.svc.bootanim error: device 'localhost:8710' not found $ /home/testuser/tools/android-sdk/platform-tools/adb connect localhost:8710 $ /home/testuser/tools/android-sdk/platform-tools/adb -s localhost:8710 shell getprop init.svc.bootanim error: device 'localhost:8710' not found Run it manually on the same box with the notes from above: [testuser@trust-reg-3 ~]$ /home/testuser/tools/android-sdk/platform-tools/adb devices List of devices attached emulator-5035 device [testuser@trust-reg-3 ~]$ /home/testuser/tools/android-sdk/platform-tools/adb -s emulator-5035 shell root@android:/ # exit The fix looks as simple as the below diff; but seems we would need to either make a decision of push the throttle down to keep the train going with the latest release or add different contextes to support the older versions for those where localhost: is a more valid stable way to connect to the
[JIRA] [copyartifact-plugin] (JENKINS-30655) Copy artifact hangs the job when the slave disconnects during copy
Title: Message Title JY Hsu updated an issue Jenkins / JENKINS-30655 Copy artifact hangs the job when the slave disconnects during copy This is happening again even after I upgraded to LTS build 1.609.3. Attached is the thread dump. The slave that is having problem is IC_Mac_01. The job name is LCMI_UnitTest. Change By: JY Hsu Attachment: Jenkins-ThreadDump.txt Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkinslint-plugin] (JENKINS-30725) BuildTimeOut check
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-30725 BuildTimeOut check Change By: Victor Martinez When using gradle plugin it is creating Jobs its worth using Gradle Wrapper to define some build timeout configuration and in order to avoid using standalone installations since gradle does support wrappers within the source code inaction . - https:// docs wiki . gradle jenkins-ci .org/ current display / userguide JENKINS / gradle_wrapper.html Build-timeout+Plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-30443) Creating label no longer support build parameters
Title: Message Title Manfred Moser commented on JENKINS-30443 Re: Creating label no longer support build parameters Should be closed as duplicate of https://issues.jenkins-ci.org/browse/JENKINS-30442 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-30447) Creating label no longer support build parameters
Title: Message Title Manfred Moser commented on JENKINS-30447 Re: Creating label no longer support build parameters Should be closed as duplicate of https://issues.jenkins-ci.org/browse/JENKINS-30442 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-30449) Creating label no longer support build parameters
Title: Message Title Manfred Moser commented on JENKINS-30449 Re: Creating label no longer support build parameters Should be closed as duplicate of https://issues.jenkins-ci.org/browse/JENKINS-30442 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-30450) Creating label no longer support build parameters
Title: Message Title Manfred Moser commented on JENKINS-30450 Re: Creating label no longer support build parameters Should be closed as duplicate of https://issues.jenkins-ci.org/browse/JENKINS-30442 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-30452) Creating label no longer support build parameters
Title: Message Title Manfred Moser commented on JENKINS-30452 Re: Creating label no longer support build parameters Should be closed as duplicate fo https://issues.jenkins-ci.org/browse/JENKINS-30442 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-30448) Creating label no longer support build parameters
Title: Message Title Manfred Moser commented on JENKINS-30448 Re: Creating label no longer support build parameters Should be closed as duplicate of https://issues.jenkins-ci.org/browse/JENKINS-30442 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-30729) Malformed xml prevents junit file from being closed.
Title: Message Title Evan Benn commented on JENKINS-30729 Re: Malformed xml prevents junit file from being closed. Here is lsof: $ sudo lsof /var/lib/jenkins/workspace/junit_debug/munit.xml lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. COMMAND PIDUSER FD TYPE DEVICE SIZE/OFFNODE NAME java16990 jenkins 465r REG 252,0 202 3938632 /var/lib/jenkins/workspace/junit_debug/munit.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-30729) Malformed xml prevents junit file from being closed.
Title: Message Title
Evan Benn edited a comment on JENKINS-30729
Re: Malformed xml prevents junit file from being closed.
Here is lsof well after the job had completed :{code}$ sudo lsof /var/lib/jenkins/workspace/junit_debug/munit.xml lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete.COMMAND PIDUSER FD TYPE DEVICE SIZE/OFFNODE NAMEjava16990 jenkins 465r REG 252,0 202 3938632 /var/lib/jenkins/workspace/junit_debug/munit.xml{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-30729) Malformed xml prevents junit file from being closed.
Title: Message Title Evan Benn commented on JENKINS-30729 Re: Malformed xml prevents junit file from being closed. Annoyingly @ hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:123) the file does not seem to have been opened, so I am stuck for finding a solution myself sorry. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-30729) Malformed xml prevents junit file from being closed.
Title: Message Title Evan Benn updated an issue Jenkins / JENKINS-30729 Malformed xml prevents junit file from being closed. Change By: Evan Benn Attachment: config.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title Guillaume Bailleul assigned an issue to stephenconnolly Jenkins / JENKINS-30700 Make Cobertura plug-in support the workflow plugin Change By: Guillaume Bailleul Assignee: Guillaume Bailleul stephenconnolly Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30721) Filesets on Windows shall be case insensitive
Title: Message Title Vasili Galka created an issue Jenkins / JENKINS-30721 Filesets on Windows shall be case insensitive Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Sep/15 2:15 PM Priority: Major Reporter: Vasili Galka For historical reasons Windows filesystem is case insensitive (unfortunately). Although the filesystem does store case, frequently the users don't have control over the case of created file/folder names. Windows users expect all tools to be case agnostic. However, this is not the current situation with Jenkins. For example, for ArtifactDeployer Plugin on Windows, setting "Artifacts to deploy" to "Foo/**" will deploy nothing if the filesystem folder is called "foo". This is clearly not a behaviour Windows user would expect. Similar issue happens with JUnit Plugin. The problem root is in the usage of Ant FileSet class which is by default case sensitive (although it can be set to ignore case). Add Comment
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-30722) The command is not correct when invoke ANT
Title: Message Title Rory Gao created an issue Jenkins / JENKINS-30722 The command is not correct when invoke ANT Issue Type: Bug Assignee: Nicolas De Loof Attachments: ant configuration.png, console output.png Components: docker-custom-build-environment-plugin Created: 30/Sep/15 2:26 PM Environment: docker-custom-build-environment 1.6.1,Docker 1.7.1 Priority: Major Reporter: Rory Gao I want to invoke the ANT script inside docker, but I found it seems the executing command is not correct. The ANT scripts in the scriptsForUnittests directory and my ANT configuration(Build file) was scriptsForUnittests/unittest-build.xml. But when the job running, it seems the plugin will enter into the scriptsForUnittests directory, then run docker exec . ant -file unittest-build.xml This is not correct as the scripts are not existed, the relative path of the scripts should be scriptsForUnittests/unittest-build.xml. Please check the
