[JIRA] [repository-connector] (JENKINS-24896) Repoistory Connector plugin fails to resolve LATEST version
redsolo created JENKINS-24896 Repoistory Connector plugin fails to resolve LATEST version Issue Type: Bug Assignee: Unassigned Components: repository-connector Created: 28/Sep/14 6:26 AM Description: I upgraded to version 1.0.1 from 0.8.2, and now it will not resolve LATEST version anymore. Instead of downloading the latest version it throws an exception Here is the plugin section of the config.xml: org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver plugin="repository-connector@1.0.1" targetDirectorytarget/targetDirectory artifacts org.jvnet.hudson.plugins.repositoryconnector.Artifact groupIdcom.flexlink.fucd/groupId artifactIdfucd-console/artifactId classifier/classifier versionLATEST/version extensionjar/extension targetFileNameconsole.jar/targetFileName /org.jvnet.hudson.plugins.repositoryconnector.Artifact /artifacts failOnErrortrue/failOnError enableRepoLoggingfalse/enableRepoLogging snapshotUpdatePolicyalways/snapshotUpdatePolicy releaseUpdatePolicyalways/releaseUpdatePolicy snapshotChecksumPolicywarn/snapshotChecksumPolicy releaseChecksumPolicywarn/releaseChecksumPolicy /org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver Here is the exception: INFO: define repo: [Repository id=central, type=default, url="" class="code-comment">//repo1.maven.org/maven2, isRepositoryManager=false] failed collecting dependency info for [Artifact com.flexlink.fucd:fucd-console:jar::LATEST] org.sonatype.aether.collection.DependencyCollectionException: Failed to collect dependencies for com.flexlink.fucd:fucd-console:jar:LATEST (provided) at org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:197) at org.sonatype.aether.impl.internal.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:308) at org.jvnet.hudson.plugins.repositoryconnector.aether.Aether.resolve(Aether.java:154) at org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.download(ArtifactResolver.java:129) at org.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.perform(ArtifactResolver.java:101) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for com.flexlink.fucd:fucd-console:jar:LATEST at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:243) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:172) at org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:191) ... 13 more Caused by: org.sonatype.aether.resolution.VersionResolutionException: Failed to resolve version for com.flexlink.fucd:fucd-console:jar:LATEST: Could not find metadata com.flexlink.fucd:fucd-console/maven-metadata.xml in local (C:\Windows\TEMP\repositoryconnector-repo) at org.apache.maven.repository.internal.DefaultVersionResolver.resolveVersion(DefaultVersionResolver.java:273) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:236) ... 15 more Caused by: org.sonatype.aether.transfer.MetadataNotFoundException: Could not find metadata com.flexlink.fucd:fucd-console/maven-metadata.xml in local (C:\Windows\TEMP\repositoryconnector-repo) at
[JIRA] [xcode] (JENKINS-24897) Build fails with jenkins XCode Integration Plugin with XCode 6.0.1
Sangjoon Park created JENKINS-24897 Build fails with jenkins XCode Integration Plugin with XCode 6.0.1 Issue Type: Bug Assignee: Unassigned Components: xcode Created: 28/Sep/14 7:08 AM Description: Build fails with XCode Integration Plugin only. (it builds fine with direct build on Mac with XCode.) Error message is as below. Please refer to the URL link for similar error with other projects. (not using Jenkins) == 2014-09-28 15:46:30.057 xcodebuild27399:4007 error: InputFile/Users/Builder/Documents/jenkins/jenkins_slave/workspace/PRJ_Client/iOS/GameClient/Output/Unity-iPhone Tests/Unity-iPhone Tests-Prefix.pch 0 1407485124 204 33204... malformed line 10; 'InputFile' should have exactly five arguments CompileC build/Unity-iPhone.build/Release-iphoneos/Unity-iPhone\ Tests.build/Objects-normal/armv7/Unity_iPhone_Tests.o Unity-iPhone\ Tests/Unity_iPhone_Tests.m normal armv7 objective-c com.apple.compilers.llvm.clang.1_0.compiler cd /Users/Builder/Documents/jenkins/jenkins_slave/workspace/PRJ_Client/iOS/GameClient/Output export LANG=en_US.US-ASCII export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin" /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch armv7 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=gnu99 -fobjc-arc -fmodules -fmodules-prune-interval=86400 -fmodules-prune-after=345600 -Wnon-modular-include-in-framework-module -Werror=non-modular-include-in-framework-module -Wno-trigraphs -fpascal-strings -Os -Wno-missing-field-initializers -Wno-missing-prototypes -Werror=return-type -Wno-implicit-atomic-properties -Werror=deprecated-objc-isa-usage -Werror=objc-root-class -Wno-receiver-is-weak -Wno-arc-repeated-use-of-weak -Wduplicate-method-match -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wuninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wshorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wundeclared-selector -Wno-deprecated-implementations -DNS_BLOCK_ASSERTIONS=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS8.0.sdk -fno-objc-exceptions -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -g -Wno-sign-conversion -miphoneos-version-min=4.3 -iquote /Users/Builder/Documents/jenkins/jenkins_slave/workspace/PRJ_Client/iOS/GameClient/Output/build/Unity-iPhone.build/Release-iphoneos/Unity-iPhone\ Tests.build/prj4kr-generated-files.hmap -I/Users/Builder/Documents/jenkins/jenkins_slave/workspace/PRJ_Client/iOS/GameClient/Output/build/Unity-iPhone.build/Release-iphoneos/Unity-iPhone\ Tests.build/prj4kr-own-target-headers.hmap -I/Users/Builder/Documents/jenkins/jenkins_slave/workspace/PRJ_Client/iOS/GameClient/Output/build/Unity-iPhone.build/Release-iphoneos/Unity-iPhone\ Tests.build/prj4kr-all-target-headers.hmap -iquote /Users/Builder/Documents/jenkins/jenkins_slave/workspace/PRJ_Client/iOS/GameClient/Output/build/Unity-iPhone.build/Release-iphoneos/Unity-iPhone\ Tests.build/prj4kr-project-headers.hmap -I/Users/Builder/Documents/jenkins/jenkins_slave/workspace/PRJ_Client/iOS/GameClient/Output/build/include -I/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include -I/Users/Builder/Documents/jenkins/jenkins_slave/workspace/PRJ_Client/iOS/GameClient/Output/build/Unity-iPhone.build/Release-iphoneos/Unity-iPhone\ Tests.build/DerivedSources/armv7 -I/Users/Builder/Documents/jenkins/jenkins_slave/workspace/PRJ_Client/iOS/GameClient/Output/build/Unity-iPhone.build/Release-iphoneos/Unity-iPhone\ Tests.build/DerivedSources
[JIRA] [core] (JENKINS-9173) Adding a parameterized parameter to a jenkins job does not work
Stefan Thurnherr commented on JENKINS-9173 Adding a parameterized parameter to a jenkins job does not work Thanks, I agree This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18799) Jenkins serves workspace files as ISO-8859-1 instead of UTF-8
Marius Gedminas commented on JENKINS-18799 Jenkins serves workspace files as ISO-8859-1 instead of UTF-8 When I tested this back in 2012 (when Jenkins was Hudson) by wgetting http://localhost:8080/..., I saw 'Content-Type: text/plain;charset=ISO-8859-1'. I added a workaround in my reverse proxy (Apache): Location "/hudson/job/ivija-update-translations/lastSuccessfulBuild/artifact/diff.txt" Header set Content-Type "text/plain; charset=UTF-8" /Location When I switched from Hudson to Jenkins, I removed the workaround, tried it again, got garbage again, reinstalled the workaround. When I do the same test today against Jenkins 1.581, wget shows me 'Content-Type: text/plain'. So, good news: Jenkins is not adding an incorrect ISO-8859-1 charset. Bad news: Jenkins is not adding the correct UTF-8 charset. The HTTP/1.1 standard says that When no explicit charset parameter is provided by the sender, media subtypes of the "text" type are defined to have a default charset value of "ISO-8859-1" when received via HTTP. Data in character sets other than "ISO-8859-1" or its subsets MUST be labeled with an appropriate charset value. So by not providing the correct charset Jenkins is implying the data is in ISO-8859-1. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24898) Job is reported as aborted while it actually fails
Yoram Michaeli created JENKINS-24898 Job is reported as aborted while it actually fails Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Sep/14 10:42 AM Description: We have a build is reported as aborted even that the build fails for compilation error in the maven build (see below build output) and has a 'Finished: FAILURE' as its final output: 00:18:17.412 ERROR Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project reports-generator: Compilation failure 00:18:17.416 ERROR /home/builder/workspace/5/reports-generator/src/main/java/com/taboola/reportsv4/monetization/publishers/rpmminguaranteev4/GuaranteeReportRunner.java:44,52 cannot find symbol 00:18:17.418 ERROR symbol : class PublisherMinGuaranteeReportMonthlyV4Test 00:18:17.420 ERROR location: package com.taboola.reportsv4.monetization.publishers 00:18:17.422 ERROR - Help 1 00:18:17.427 ERROR 00:18:17.429 ERROR To see the full stack trace of the errors, re-run Maven with the -e switch. 00:18:17.430 ERROR Re-run Maven using the -X switch to enable full debug logging. 00:18:17.432 ERROR 00:18:17.434 ERROR For more information about the errors and possible solutions, please read the following articles: 00:18:17.436 ERROR Help 1 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException 00:18:17.438 ERROR 00:18:17.439 ERROR After correcting the problems, you can resume the build with the command 00:18:17.442 ERROR mvn goals -rf :reports-generator ... 00:18:20.105 channel stopped 00:18:21.543 Starting to tag 00:18:21.543 No Subversion tagging for unsuccessful build. 00:18:21.543 Email was triggered for: Aborted 00:18:21.544 Sending email for trigger: Aborted 00:18:22.337 Sending email to: ta...@taboola.com michae...@taboola.com nitza...@taboola.com davi...@taboola.com ila...@taboola.com ro...@taboola.com develop...@taboola.com 00:18:22.433 Notifying upstream projects of job completion 00:18:22.433 Finished: FAILURE Environment: Jenkins ver. 1.565.2 Centos Maven 3.0.4 Project: Jenkins Priority: Major Reporter: Yoram Michaeli This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18799) Jenkins serves workspace files as ISO-8859-1 instead of UTF-8
Daniel Beck commented on JENKINS-18799 Jenkins serves workspace files as ISO-8859-1 instead of UTF-8 The problem is that Jenkins just has no way to determine what charset any given file is. Serving any arbitrary file created by user-controlled means cannot work AFAICT, so I guess this is something we need to live with. When there's no explicit encoding, client may do some autodetection though, so the current state seems to be the best possible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18799) Jenkins serves workspace files as ISO-8859-1 instead of UTF-8
Daniel Beck edited a comment on JENKINS-18799 Jenkins serves workspace files as ISO-8859-1 instead of UTF-8 The problem is that Jenkins just has no way to determine what charset any given file is. Serving any arbitrary file created by user-controlled means cannot work AFAICT, so I guess this is something we need to live with. When there's no explicit encoding, client may do some autodetection though, so the current state seems to be the best possible. Given these limitations, I'm tempted to resolve as Won't Fix. Any opposing views? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21747) Artifact archiving fails with java.lang.NoClassDefFoundError
Daniel Beck commented on JENKINS-21747 Artifact archiving fails with java.lang.NoClassDefFoundError If you have the chance, try running Jenkins on an Oracle JDK. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24899) oops when trying to access project configure
Abdoulaye Walsimou GAYE created JENKINS-24899 oops when trying to access project configure Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Sep/14 11:30 AM Description: The following oops message is shown when trying to access configure of a project. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/usr/local/jenkins/war/WEB-INF/lib/jenkins-core-1.581.jar!/hudson/model/Job/configure.jelly:61:54: st:include hudson/maven/MavenModuleSet at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:91) 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 org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at
[JIRA] [core] (JENKINS-24899) oops when trying to access project configure
Abdoulaye Walsimou GAYE commented on JENKINS-24899 oops when trying to access project configure The issue occurs when Maven Integration plugin is installed but not enabled This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19017) Jenkins merges queued builds with the different file parameters
Oleg Nenashev commented on JENKINS-19017 Jenkins merges queued builds with the different file parameters New PR: https://github.com/jenkinsci/jenkins/pull/1411 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [timestamper] (JENKINS-24900) Show the duration per build step / post-build action
Steve Mokris created JENKINS-24900 Show the duration per build step / post-build action Issue Type: New Feature Assignee: stevengbrown Components: timestamper Created: 28/Sep/14 3:35 PM Description: Timestamper makes it easy to see details about how long individual commands take (thanks!). But some of my projects have many build steps, each with many commands that generate a ton of console log output, so it's time-consuming to wade through the console output to answer the big-picture question "why does this job take so long to build?". It would be handy if Timestamper could provide a summary table (maybe on the build overview page) showing the total duration of each build step and post-build action, so it's easy to see which steps to focus on when I need to improve the build speed. The table could link to the first console line of each build step. Project: Jenkins Labels: performance Priority: Major Reporter: Steve Mokris This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24898) Job is reported as aborted while it actually fails
Daniel Beck commented on JENKINS-24898 Job is reported as aborted while it actually fails Are you building this project in parallel? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24732) file parameter eats up disk space quickly
Daniel Beck commented on JENKINS-24732 file parameter eats up disk space quickly This is deliberate, as Jenkins makes all parameter values of past builds available. In the case of file parameters, the parameter value is the file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24895) An existing connection was forcibly closed by the remote host
Daniel Beck updated JENKINS-24895 An existing connection was forcibly closed by the remote host Change By: Daniel Beck (28/Sep/14 4:31 PM) Labels: connection remoting Component/s: remoting This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24899) oops when trying to access project configure
Daniel Beck resolved JENKINS-24899 as Not A Defect oops when trying to access project configure Not a bug: You have a plugin enabled that has a dependency on Maven plugin (Release Plugin according to the stack trace), which is invalid plugin configuration. Either enable Maven plugin, or disable everything with a dependency on it. There are issues about indicating or prohibiting such misconfiguration, but they haven't been implemented yet. Change By: Daniel Beck (28/Sep/14 4:33 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24898) Job is reported as aborted while it actually fails
Daniel Beck commented on JENKINS-24898 Job is reported as aborted while it actually fails If so, this duplicates JENKINS-24832. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24732) file parameter eats up disk space quickly
Daniel Beck resolved JENKINS-24732 as Wont Fix file parameter eats up disk space quickly The solution here is to not have file parameters as large, or discard builds more aggressively. In that, this is no different than e.g. complaining about Jenkins eating disk space because it retains the logs of past builds, and you're logging very verbose. Change By: Daniel Beck (28/Sep/14 4:36 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24469) Update notification should link to stable changelog when running a stable release
Daniel Beck commented on JENKINS-24469 Update notification should link to stable changelog when running a stable release There was a PR for this, but a solution without adjusting this for every new .1 is needed: https://github.com/jenkinsci/jenkins/pull/1045 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24469) Update notification should link to stable changelog when running a stable release
Daniel Beck edited a comment on JENKINS-24469 Update notification should link to stable changelog when running a stable release There was a PR for something similar, but a solution without adjusting this for every new .1 (like you suggest) is needed, and the PR rejected: https://github.com/jenkinsci/jenkins/pull/1045 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24732) file parameter eats up disk space quickly
Oleg Nenashev commented on JENKINS-24732 file parameter eats up disk space quickly BTW, there're two possible improvements, which may reduce the issue's impact Improvement - ParameterizedTrigger stores fileParameter in upstream builds = double space usage New feature - FileParameters can be compressed in order to reduce the disk usage (same thing has been done by Jesse for build logs) @Jerry, feel free to create issues to cases above if they can help for your installation This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-24894) LDAP : Cannot change displayname once user account is created
Laurent TOURREAU commented on JENKINS-24894 LDAP : Cannot change displayname once user account is created Here is the use case: 1/ Enable security in "Configure Global Security" 2/ Select LDAP as Security Realm 3/ Enter LDAP settings. Enter"CN" as displayname. 4/ Save the config. 5/ Log as a new LDAP registered user. On the top right you see your First Name + Full Name (depending the CN field content on LDAP user record). -- Until that it's ok. 6/ Unlog from Jenkins. 7/ Go back in "Configure Global Security" 8/ In LDAP settings, change displayname by "mail" 9/ Save the config 10 / Log as previous LDAP registered user. On the top right you should see user's mail, but it's not the case, instead you get First Name + Full Name as "CN" was again the displayname. 11/ The workaround : Delete the user from Jenkins and relog as it again, this will recreate it and this time you will get user's mail displayed as expected on the top right. Regards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-24894) LDAP : Cannot change displayname once user account is created
Laurent TOURREAU edited a comment on JENKINS-24894 LDAP : Cannot change displayname once user account is created Here is the use case: 1/ Enable security in "Configure Global Security" 2/ Select LDAP as Security Realm 3/ Enter LDAP settings. Enter"CN" as displayname. 4/ Save the config. 5/ Log as a new LDAP registered user. On the top right you see your First Name + Full Name (depending the CN field content on LDAP user record). -- Until that it's ok. 6/ Unlog from Jenkins. 7/ Go back in "Configure Global Security" 8/ In LDAP settings, change displayname by "mail" 9/ Save the config 10 / Log as previous LDAP registered user. On the top right you should see user's mail, but it's not the case, instead you get First Name + Full Name as "CN" was again the displayname. The workaround : Delete the user from Jenkins and relog as it again, this will recreate it and this time you will get user's mail displayed as expected on the top right. N.B. I tried to stop and restart Jenkins server after changing displayname at step 8, it doesn't solve the problem Regards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-24894) Users' display names should be synchronized with LDAP
Daniel Beck updated JENKINS-24894 Users display names should be synchronized with LDAP Right, this is only for the initial creation of a user record in Jenkins. Afterwards, it can be changed in Jenkins (/user/USERNAME/configure) only. Reclassifying this as a feature request. One possible problem here is that an out of date display name set by the realm (which should probably be replaced) is indistinguishable from a completely custom display name set in Jenkins. Change By: Daniel Beck (28/Sep/14 6:09 PM) Summary: Usersdisplaynamesshouldbesynchronizedwith LDAP :Cannotchangedisplaynameonceuseraccountiscreated Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [embeddable-build-status] (JENKINS-23062) Use shields.io-style badges
Marius Gedminas resolved JENKINS-23062 as Fixed Use shields.io-style badges Change By: Marius Gedminas (28/Sep/14 6:36 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18799) Jenkins serves workspace files as ISO-8859-1 instead of UTF-8
Marius Gedminas commented on JENKINS-18799 Jenkins serves workspace files as ISO-8859-1 instead of UTF-8 Let me try to disable my workaround again and check if Chrome attempts charset autodetection (which would be a violation of the HTTP standard, but whatever, sometimes software sacrifices standards for better user experience). checks Nope, there's no autodetection. I see gibberish. Why not serve the files from the workspace using the locale charset, which Jenkin already knows? /systemInfo: file.encoding: UTF-8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24901) Automatic tool installation of maven does not use settings from Maven Configuration section
David Karlsen created JENKINS-24901 Automatic tool installation of maven does not use settings from Maven Configuration section Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Sep/14 6:46 PM Description: When installing maven with the automatic tool install option (as well as having the actual JDK installed automatically) there is no way to point to a common settings.xml, either through MAVEN_OPTS or through the "Maven Configuration" section in the main setup. It will create a commandline like: /var/jenkins_home/tools/hudson.model.JDK/jdk8oracle/bin/java -s /var/jenkins_home/settings.xml -cp /var/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.5.jar:/var/jenkins_home/tools/hudson.tasks.Maven_MavenInstallation/maven/boot/plexus-classworlds-2.5.1.jar:/var/jenkins_home/tools/hudson.tasks.Maven_MavenInstallation/maven/conf/logging jenkins.maven3.agent.Maven31Main /var/jenkins_home/tools/hudson.tasks.Maven_MavenInstallation/maven /var/jenkins_home/war/WEB-INF/lib/remoting-2.43.jar /var/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.5.jar /var/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.5.jar 48582 Unrecognized option: -s Project: Jenkins Priority: Minor Reporter: David Karlsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18799) Jenkins serves workspace files as ISO-8859-1 instead of UTF-8
Daniel Beck commented on JENKINS-18799 Jenkins serves workspace files as ISO-8859-1 instead of UTF-8 This may work for some situations, but as basically no file in the workspace is actually written by the Jenkins process (Maven Projects come to mind, but that's basically it), that's likely of very limited use. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-24894) Users' display names should be synchronized with LDAP
Laurent TOURREAU commented on JENKINS-24894 Users display names should be synchronized with LDAP Thanks for the reply. Concerning the distinction between out of date display name and custom name, we should deal that as it: On user configuration screen we have a ratio button choice -Allow display name synchronization with LDAP - This will make the custom name text box read only, leaving it in grey background color. -Custom display name - This will enable the custom name text box for edition. So we take account that custom display name instead of this from realm. What's your opinion? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-24894) Users' display names should be synchronized with LDAP
Daniel Beck commented on JENKINS-24894 Users display names should be synchronized with LDAP This will make no sense for authentication realms that do not provide a display name. And the user screen isn't extensible that way (remember, LDAP auth realm is a plugin that depends on available extension points; and core extension points need to make sense for multiple implementations). One possibility that could be solved in the plugin would be to store the last know display name from LDAP in the user record, and always compare it to the one reported by LDAP; if it changes, check if the display name of the user is the same if it is, update it, else don't. Then update the stored known LDAP display name. Besides that, I think the more common use case is when a user's field in LDAP is changed rather than reconfiguration of Jenkins. Same problem, but cannot be solved by manually fixing things, as e.g. changing teams/departments (if part of the display name field) of some user likely happens without the Jenkins admin knowing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging] (JENKINS-24902) Global authorization matrix should not be ignored
Fabrice Daugan created JENKINS-24902 Global authorization matrix should not be ignored Issue Type: Bug Assignee: kutzi Components: instant-messaging Created: 28/Sep/14 7:04 PM Description: In Global authorization matrix (https://ci.gfi.fr/jenkins/configureSecurity/), the "Authorization" option is "Project-based Matrix Authorization Strategy". I have a user will all rights in the security matrix. In the tested project, "Enable project-based security" is checked, no authorization is provided and "Block inheritance of global authorization matrix" is unchecked. This user can do everything from the UI in Jenkins, CLI, REST,..., but nothing with "instant-messaging plugin" : Adding this user to the project's security resolves this issue, but I have many users and groups in this situation. Before the workaround : (8:41:17 PM) fdaugan: !h (8:41:17 PM) Jenkins CI: fdaugan: no job found After explicitly adding the user in the project's security scope : (8:42:26 PM) fdaugan: !h (8:42:26 PM) Jenkins CI: health of all projects: Forge: Health [Build stability: 1 out of the last 5 builds failed.(80%), Test Result: 0 tests failing out of a total of 2 tests.(100%): https://xx/jenkins/job/xx/398/ Environment: Jenkins 1.581 instant-messaging plugin 1.30 Project: Jenkins Priority: Major Reporter: Fabrice Daugan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18799) Jenkins serves workspace files as ISO-8859-1 instead of UTF-8
Marius Gedminas commented on JENKINS-18799 Jenkins serves workspace files as ISO-8859-1 instead of UTF-8 Perhaps my perspective has been warped by constant exposure to Linux systems, where everyone uses the locale charset, which is in 99% of the cases UTF-8, but is it really that common for random projects to use random different charsets that do not match the system locale? How is defaulting to ISO-8859-1 better than defaulting to the system locale (which at least can be changed by the sysadmin)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-18166) Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7
Stefan Thurnherr commented on JENKINS-18166 Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7 @Ben: Still interested, but sadly had no time during the past months. Feel free to continue on my cloned git repo if you have some spare time. I needed some jenkins/jira interaction last spring and the current SOAP-based plugin didn't feel very future-proof, but a simple python script calling the JIRA REST API did the trick for me This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging] (JENKINS-24902) Jenkins's security is not applied for IM user
Fabrice Daugan updated JENKINS-24902 Jenkinss security is not applied for IM user Change By: Fabrice Daugan (28/Sep/14 7:38 PM) Summary: Globalauthorizationmatrixshould Jenkinsssecurityis not beignored appliedforIMuser Description: InGlobalauthorizationmatrix(https://ci.gfi.fr/jenkins/configureSecurity/),theAuthorizationoptionisProject-basedMatrixAuthorizationStrategy . : jenkins-imuserhasallauthorizations,andistheoneIvemappedtoJenkinsUsernameparameterofinstant-messagingplugin Ihaveauserwill norightat all rights in Jenkinsbutallowedtoconnectto the securitymatrix.Inthetestedproject, conferenceusedby Enableproject jenkins - basedsecurity im ischecked,noauthorizationisprovidedandBlockinheritanceofglobalauthorizationmatrixisunchecked .Thisusercan doeverythingfrom sendanybotcommandsandthisisreallyweird.Thesameistrueforaregisteredjenkinsuserhavingonlyread/viewrights.Ifhecanonlyseebuildsusing the UIinJenkins, Web/REST/ CLI interfaces , REST, thispluginactslikeasudo . ..,butnothingwith JenkinsUsernameparameterof instant-messagingplugin :Addingthisuserto shouldberemovedormergedwith the projectssecurityresolvesthisissue,butIhavemanyusersandgroupsinthissituation rightsofconnectedIMuser . Beforetheworkaround:(8:41:17PM)fdaugan:!h(8:41:17PM) The Jenkins CI:fdaugan:nojobfoundAfterexplicitlyaddingthe user in correspondingto the projectssecurityscope:(8:42:26PM)fdaugan:!h(8:42:26PM)JenkinsCI:health author of allprojects:Forge:Health[Buildstability:1outof the last5buildsfailed botcommandmustbeused . (80%),TestResult:0testsfailingoutofatotalof2tests.(100%):https://xx/jenkins/job/xx/398/ Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18799) Jenkins serves workspace files as ISO-8859-1 instead of UTF-8
Daniel Beck commented on JENKINS-18799 Jenkins serves workspace files as ISO-8859-1 instead of UTF-8 but is it really that common for random projects to use random different charsets that do not match the system locale? Build systems can create tons of different artifacts. One of mine converts UTF-8 into about 30 different local char sets. And of course the files are in the workspace and viewable by me. How is defaulting to ISO-8859-1 better than defaulting to the system locale (which at least can be changed by the sysadmin)? It's not. Just saying it's not a really good solution either. The correct charset may well depend on the specific project you're building, and sometimes on the specific file. Note that non-UTF-* default charsets seem to be fairly common on Windows, while OS X moved to UTF-8 (from MacRoman) only around 10.8 or so AFAIK. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator] (JENKINS-24903) Unkillable builds due to catastrophic backtracking regular expression
recampbell created JENKINS-24903 Unkillable builds due to catastrophic backtracking regular _expression_ Issue Type: Bug Assignee: Nicolas De Loof Attachments: config.xml Components: naginator Created: 28/Sep/14 8:24 PM Description: If the user enters a regular _expression_ which results in catastrophic backtracking(http://www.rexegg.com/regex-explosive-quantifiers.html), the regular _expression_ will run "forever" and the user will not be able to kill the build. The attached config.xml demonstrates the issue. The solution is to use an [interruptible character sequence[(http://ocpsoft.org/regex/how-to-interrupt-a-long-running-infinite-java-regular-_expression_/). Project: Jenkins Priority: Minor Reporter: recampbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24904) Add option to archive artifacts in the background
Steve Mokris created JENKINS-24904 Add option to archive artifacts in the background Issue Type: Improvement Assignee: Unassigned Components: core Created: 28/Sep/14 8:33 PM Description: I have a job that takes about 2 hours to run — 15 minutes to build, 1 hour to run automated tests, and 45 minutes to archive the artifacts (the node's upstream internet connection isn't very fast). Would it make sense to add the option to start archiving the artifacts right after a certain build step completes, and archive in parallel with the remaining build steps? In a case like this, it could reduce the job from 2 hours to 1 hour 15 minutes. Project: Jenkins Labels: performance Priority: Major Reporter: Steve Mokris This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator] (JENKINS-24903) Unkillable builds due to catastrophic backtracking regular expression
recampbell updated JENKINS-24903 Unkillable builds due to catastrophic backtracking regular _expression_ Change By: recampbell (28/Sep/14 9:05 PM) Description: Iftheuserentersaregular_expression_whichresultsin[catastrophicbacktracking ]( | http://www.rexegg.com/regex-explosive-quantifiers.html ) ] ,theregular_expression_willrunforeverandtheuserwillnotbeabletokillthebuild.Theattachedconfig.xmldemonstratestheissue.Thesolutionistousean[interruptiblecharactersequence [( | http://ocpsoft.org/regex/how-to-interrupt-a-long-running-infinite-java-regular-_expression_/ ) ] . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24469) Update notification should link to stable changelog when running a stable release
aldaris commented on JENKINS-24469 Update notification should link to stable changelog when running a stable release Thanks for the pointer, didn't realize I was raising a duplicate, sorry about that. I've created a PR based on the comments on #1045 from Oliver Gondža: https://github.com/jenkinsci/jenkins/pull/1412 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24469) Update notification should link to stable changelog when running a stable release
Daniel Beck commented on JENKINS-24469 Update notification should link to stable changelog when running a stable release Not a duplicate, as the other is about the Debian changelog. They're just related This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator] (JENKINS-24903) Unabortable builds due to catastrophic backtracking regular expression
recampbell updated JENKINS-24903 Unabortable builds due to catastrophic backtracking regular _expression_ Change By: recampbell (28/Sep/14 9:20 PM) Summary: Unkillable Unabortable buildsduetocatastrophicbacktrackingregular_expression_ Description: Iftheuserentersaregular_expression_whichresultsin[catastrophicbacktracking|http://www.rexegg.com/regex-explosive-quantifiers.html],theregular_expression_willrunforeverandtheuserwillnotbeableto kill abort thebuild.Theattachedconfig.xmldemonstratestheissue.Thesolutionistousean[interruptiblecharactersequence|http://ocpsoft.org/regex/how-to-interrupt-a-long-running-infinite-java-regular-_expression_/]. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-24905) Layout broken in after Jenkins UI improvements
Ulli Hafner created JENKINS-24905 Layout broken in after Jenkins UI improvements Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core Created: 28/Sep/14 10:00 PM Description: After Jenkins UI improvement pull requests the layout of the YUI tabs (https://github.com/jenkinsci/analysis-core-plugin/blob/master/src/main/resources/result/main.jelly) and the source code view is somewhat broken. Seems that some of the new CSS styles conflict with the style of the analysis plugins. Moreover, the highlighting of the current source code line is missing now. Project: Jenkins Labels: user-experience Priority: Major Reporter: Ulli Hafner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-24905) Tab and source layout broken after Jenkins UI improvements
Ulli Hafner updated JENKINS-24905 Tab and source layout broken after Jenkins UI improvements Change By: Ulli Hafner (28/Sep/14 10:02 PM) Summary: Layout Tabandsourcelayout broken in afterJenkinsUIimprovements This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-24905) Tab and source layout broken after Jenkins UI improvements
Ulli Hafner updated JENKINS-24905 Tab and source layout broken after Jenkins UI improvements Change By: Ulli Hafner (28/Sep/14 10:03 PM) Description: AfterJenkinsUIimprovementpullrequeststhelayoutoftheYUItabs(https://github.com/jenkinsci/analysis-core-plugin/blob/master/src/main/resources/result/main.jelly)andthesourcecodeviewissomewhatbroken.SeemsthatsomeofthenewCSSstylesconflictwiththestyleoftheanalysisplugins. Thetabsandtablesinsidethetabslookweird. Moreover,thehighlightingofthecurrentsourcecodelineismissingnow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-21544) Copy Artifact Plugin: support fallback to unstable builds when using Upstream build that triggered this job
ikedam resolved JENKINS-21544 as Duplicate Copy Artifact Plugin: support fallback to unstable builds when using Upstream build that triggered this job Duplicates JENKINS-16108 Change By: ikedam (28/Sep/14 10:31 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand] (JENKINS-24816) deviceName attribute missing on JSON for Android platforms
apgray updated JENKINS-24816 deviceName attribute missing on JSON for Android platforms Change By: apgray (29/Sep/14 1:00 AM) Assignee: KohsukeKawaguchi RossRowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-22004) JIRA does NOT create new ticket for build failure for a new build project.(Create new issue plugin bug). Occurs when the new job build results are all failures
Patrice Matignon commented on JENKINS-22004 JIRA does NOT create new ticket for build failure for a new build project.(Create new issue plugin bug). Occurs when the new job build results are all failures Is it more like a feature where the JIRA plugin will not create additional JIRA tickets for a consecutive failures of a build ? IF so, it probably would have been good to provide an option, but this is probably a decent default behavior if you must have one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [debian-package-builder] (JENKINS-24906) Debian package LTS v1.565.2 has corrupt jenkins.war
Sam Gleske created JENKINS-24906 Debian package LTS v1.565.2 has corrupt jenkins.war Issue Type: Bug Assignee: Unassigned Components: debian-package-builder Created: 29/Sep/14 3:35 AM Description: Here's the checksum difference. From the Jenkins website. md5sum jenkins.war e53d793e42d1686ab103960dbd17979a jenkins.war From the package. grep 'jenkins.war' /var/lib/dpkg/info/jenkins*.md5sums /var/lib/dpkg/info/jenkins-common.md5sums:2cc48f1f0341b8c54659e0af73cc3115 usr/share/jenkins/jenkins.war I troubleshooted this for a few hours and thought there was something wrong with my Jenkins instance. After I downloaded the LTS from the website and moved it into /usr/share/jenkins/jenkins.war and restarted the service; my Jenkins instance started behaving correctly again. Environment: # head -n1 /etc/issue Debian GNU/Linux jessie/sid \n \l # uname -rms Linux 3.14-2-amd64 x86_64 # java -version java version 1.7.0_65 OpenJDK Runtime Environment (IcedTea 2.5.2) (7u65-2.5.2-4) OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) # apt-cache show jenkins Package: jenkins Version: 1.565.2-2 Installed-Size: 106 Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Architecture: all Depends: adduser, default-jre-headless | java6-runtime-headless, jenkins-common (= 1.565.2-2), daemon, psmisc, net-tools, procps Conflicts: jenkins-tomcat, tomcat6 Description-en: Continuous Integration and Job Scheduling Server Jenkins monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Jenkins focuses on the following two jobs: . * Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Jenkins provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases productivity. * Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Jenkins keeps those outputs and makes it easy for you to notice when something is wrong. . This package supports using Jenkins in standalone mode utilising the embedded winstone servlet container. Description-md5: d4b314ee3431ba663d8c5b45429ff25f Homepage: http://jenkins-ci.org Section: java Priority: optional Filename: pool/main/j/jenkins/jenkins_1.565.2-2_all.deb Size: 20614 MD5sum: 08b47d8b966b5683969701fa63778d1c SHA1: b301f55ed8a7de59c71c141ea9700152df9b8be4 SHA256: 32f907c1ddeacdc31ef8b66cd1755217f9362d1cc6d0f0958c151e55ea4d6116 Package: jenkins Priority: extra Section: devel Installed-Size: 66640 Maintainer: Kohsuke Kawaguchi k...@kohsuke.org Architecture: all Version: 1.565.2 Replaces: hudson Depends: daemon, adduser, psmisc, default-jre-headless | java-runtime-headless Conflicts: hudson Filename: binary/jenkins_1.565.2_all.deb Size: 62082472 MD5sum: 81f6ca7726635b2685fdf8f4401bdc4f SHA1: 6dc131581923374a1dbcdc0b92447184a472e06d SHA256: ebe2c87f1130f9bbe5de46088d98241bf397a53931a521a9befaf0a3e697aaea SHA512: decdcb66a0360d80a89c8524c0adac8980157b34683b87da56c1170a9c3bfb562ffec0d0fda2277ce085a0dacfc7d2f7fc62e829f2c028c0b393f8dfea633a11 Description: continuous integration system Jenkins is an application that monitors executions of repeated jobs, such as building a software project or jobs run by cron. Description-md5: 483e336ea11484aaa0d84b76602263f7 Homepage: https://jenkins-ci.org/ Project: Jenkins Labels: jenkins debian corruption
