[JIRA] (JENKINS-13285) customtools-plugin does not delegate the Launcher.isUnix() call in DecoratedLauncher
[
https://issues.jenkins-ci.org/browse/JENKINS-13285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Smith updated JENKINS-13285:
Environment: customtools-plugin version 0.1 (was: customtools-plugin
version 1.0)
> customtools-plugin does not delegate the Launcher.isUnix() call in
> DecoratedLauncher
>
>
> Key: JENKINS-13285
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13285
> Project: Jenkins
> Issue Type: Bug
> Components: customtools-plugin
> Environment: customtools-plugin version 0.1
>Reporter: Tim Smith
>Assignee: recampbell
>Priority: Critical
>
> When launching a Maven build from a Jenkins Unix master to a remote Windows
> slave the command line is incorrectly built because the customtools-plugin
> decorates the Launcher and fails to pass through the Launcher.isUnix() call
> to the decoratee. The result is that the classpath uses a path separator of
> ':' rather than ';' and Maven fails to load with a NoClassDefFoundError.
> The fix is simple. In
> {{com.cloudbees.jenkins.plugins.customtools.DecoratedLauncher}} just override
> the isUnix() call:
> {code:title=com.cloudbees.jenkins.plugins.customtools.DecoratedLauncher}
> @Override
> public boolean isUnix() {
> return inner.isUnix();
> }
> {code}
> I'm not sure if there is a better way to do this in Jenkins. Decorating
> Launcher by subclassing in this way looks prone to this error if plugins fail
> to decorate all public methods. Perhaps Jenkins core offers a better approach?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13285) customtools-plugin does not delegate the Launcher.isUnix() call in DecoratedLauncher
Tim Smith created JENKINS-13285:
---
Summary: customtools-plugin does not delegate the
Launcher.isUnix() call in DecoratedLauncher
Key: JENKINS-13285
URL: https://issues.jenkins-ci.org/browse/JENKINS-13285
Project: Jenkins
Issue Type: Bug
Components: customtools-plugin
Environment: customtools-plugin version 1.0
Reporter: Tim Smith
Assignee: recampbell
Priority: Critical
When launching a Maven build from a Jenkins Unix master to a remote Windows
slave the command line is incorrectly built because the customtools-plugin
decorates the Launcher and fails to pass through the Launcher.isUnix() call to
the decoratee. The result is that the classpath uses a path separator of ':'
rather than ';' and Maven fails to load with a NoClassDefFoundError.
The fix is simple. In
{{com.cloudbees.jenkins.plugins.customtools.DecoratedLauncher}} just override
the isUnix() call:
{code:title=com.cloudbees.jenkins.plugins.customtools.DecoratedLauncher}
@Override
public boolean isUnix() {
return inner.isUnix();
}
{code}
I'm not sure if there is a better way to do this in Jenkins. Decorating
Launcher by subclassing in this way looks prone to this error if plugins fail
to decorate all public methods. Perhaps Jenkins core offers a better approach?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13264) fail checkout 2 modules with different path
[ https://issues.jenkins-ci.org/browse/JENKINS-13264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161000#comment-161000 ] Michael Clarke commented on JENKINS-13264: -- The issue is being caused by the CVS plugin trying to check out the files into a folder that matches the remote location name, but not creating the intermediate directories. If the module is called 'path/to/module' then the CVS plugin should create a directory called 'path' then another directory in there called 'to' before issuing the checkout command which will create 'module' inside these newly created directory. > fail checkout 2 modules with different path > --- > > Key: JENKINS-13264 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13264 > Project: Jenkins > Issue Type: Bug > Components: cvs > Environment: linux >Reporter: Eric Co > > I create two cvs modules with the path > lib/flac-1.2.1 > drv/linux/fuse > when it check out, got the error: > cvs checkout -P -D 29 Mar 2012 11:40:15 +0800 -d lib/flac-1.2.1 > lib/flac-1.2.1 > cvs [checkout aborted]: could not change directory to requested checkout > directory `lib': No such file or directory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12037) CLI - I/O error in channel Chunked connection/Unexpected termination of the channel - still occurring in Jenkins 1.449
[ https://issues.jenkins-ci.org/browse/JENKINS-12037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161001#comment-161001 ] Richard Mortimer commented on JENKINS-12037: A snapshot build of 1.459 with the fix can be downloaded from [cli-1.459-SNAPSHOT-jar-with-dependencies.jar|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1624/artifact/cli/target/cli-1.459-SNAPSHOT-jar-with-dependencies.jar] this should allow testing against recent version of Jenkins. > CLI - I/O error in channel Chunked connection/Unexpected termination of the > channel - still occurring in Jenkins 1.449 > -- > > Key: JENKINS-12037 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12037 > Project: Jenkins > Issue Type: Bug > Components: cli > Environment: * Running on SLES9 Linux server with 4 CPUs and plenty > of diskspace. > * Tomcat 7.0.22 > * JDK 1.6.0_14 > * Only ONE Master configuration - no slaves are configured > * 3 Executors - (one less than the max number of CPUs) >Reporter: mark streit >Priority: Critical > Attachments: jenkins-timeout, Tomcat7_Jenkins1449_logs.zip > > > We reported an issue some time back that was also listed as fixed in Jenkins > 1.441: > Log: > [FIXED JENKINS-11130] SEVERE: I/O error in channel Chunked connection when > using jenkins-cli.jar > Perhaps another bug should NOT be submitted so I have added the following > comments below the line to the original defect 11130 comments section in case > it can be reviewed/re-opened. > We did NOT try to make any adjustments to the Tomcat configuration: > Tomcat Connector connectionUploadTimeout > but we are also now seeing the same problem with Winstone when at this same > 1.441 level. We did revert to the 1.438 version of the CLI (leaving the WAR > at 1.441 running in Winstone) and that is serving asthe current workaround. > > We have downloaded and installed the LATEST 1.441 release that lists the fix > for this problem. Currently we were running 1.438 on Winstone only (since > with Tomcat 6 or 7, we had experienced the error HOWEVER yet under Winstone, > it worked OK so that was our workaround - while running 1.438). > Now with Jenkins 1.441 - we are getting the ERROR again and NOW WITH BOTH > Winstone and the Tomcat configurations). We have left the Jenkins 1.441 WAR > file in place running on Winstone, and reverted the CLI jar file back to the > 1.438 version for now and that appears to work again with Winstone. > Checked Manifest of CLI jar downloaded with the 1.441 WAR installation: > Manifest-Version: 1.0 > Archiver-Version: Plexus Archiver > Created-By: Apache Maven > Built-By: kohsuke > Build-Jdk: 1.6.0_26 > Main-Class: hudson.cli.CLI > Jenkins-CLI-Version: 1.441 > Under Tomcat 7, we get this stacktrace: > Started by command line > [workspace] $ /bin/bash -xe > /opt/apache-tomcat-7.0.22_jenkins/temp/hudson3281734817830.sh > + /opt/Sun/jdk1.6.0_14/bin/java -jar /opt/Sun/jdk1.6.0_14/lib/jenkins-cli.jar > -s http://11.22.33.44:8082/jenkins/ build XYZ_Project-SharedLibs -s -p > SVN_PATH=trunk > Dec 5, 2011 12:59:11 PM hudson.remoting.Channel$ReaderThread run > SEVERE: I/O error in channel Chunked connection to > http://11.22.33.44:8082/jenkins/cli > java.io.IOException: Unexpected termination of the channel > at hudson.remoting.Channel$ReaderThread.run(Channel.java:1115) > Caused by: java.io.EOFException > at > java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2554) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) > at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109) > Exception in thread "main" hudson.remoting.RequestAbortedException: > hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected > termination of the channel > at hudson.remoting.Request.call(Request.java:149) > at hudson.remoting.Channel.call(Channel.java:681) > at > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) > at $Proxy2.main(Unknown Source) > at hudson.cli.CLI.execute(CLI.java:200) > at hudson.cli.CLI._main(CLI.java:330) > at hudson.cli.CLI.main(CLI.java:245) > Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: > Unexpected termination of the channel > at hudson.remoting.Request.abort(Request.java:273) > at hudson.remoting.Channel.terminate(Channel.java:732) > at hudson.remoting.Channel$ReaderThread.run(Channel.java:1139) > Caused by: java.io.IOException: Unexpected termination of the channel > at hudson.remoting.Channel$ReaderThread.run
[JIRA] (JENKINS-13286) Builds retried twice even when succeeds on first retry
David Riley created JENKINS-13286: - Summary: Builds retried twice even when succeeds on first retry Key: JENKINS-13286 URL: https://issues.jenkins-ci.org/browse/JENKINS-13286 Project: Jenkins Issue Type: Bug Components: schedule-failed-builds Reporter: David Riley Assignee: sfritz I am combining this plugin with the build timeout plugin (https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin) and also the log parser plugin (https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin). Both of these plugins can cause the build to fail, however I dont consider this to be the fault of those plugins, if a build has failed, it is the job of this plugin to setup the retry. When it does, the build is retried correctly, but if the retry succeeds, they get built once more! If it helps, the second build has "Started due to previous failed build" printed twice on the build summary page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13273) cannot launch Jenkins on a Windows 7
[ https://issues.jenkins-ci.org/browse/JENKINS-13273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Bagnack updated JENKINS-13273: -- Summary: cannot launch Jenkins on a Windows 7 (was: cannot run Jenkins as a Windows Service on a Windows 7) Description: I'm trying to get started with Jenkins and cannot launch Jenkins by following the instructions for installation of Jenkins as a Windows Service. I've downloaded the latest jenkins.war and run the "java -jar jenkins.war" on the command prompt. While loading the dependencies, following warning came up: "WARNING: Non-XML-Schema-compliant parser detected. Servlet spec <= 2.3 supported". However I ran "http://localhost:8080"; on Firefox 11 and an 500 error code came up with the following stack trace: java.lang.NoSuchMethodError: org.dom4j.io.OutputFormat.setXHTML(Z)V at org.kohsuke.stapler.jelly.HTMLWriterOutput.createFormat(HTMLWriterOutput.java:56) at org.kohsuke.stapler.jelly.HTMLWriterOutput.create(HTMLWriterOutput.java:45) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.createXMLOutput(DefaultScriptInvoker.java:68) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:51) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:560) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:622) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:485) at org.kohsuke.stapler.Stapler.service(Stapler.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) A part from java is there any prerequisites I need to get Jenkins properly run on a windows 7 system. Thx for your suggestions. was: I'm trying to get startet with Jenkins and cannot run Jenkins as a Windows Service on a Windows 7 System. I've downloaded the latest jenkins.war and run the "java -jar jenkins.war" on the command prompt. While loading the dependencies, Jenkins has thrown following warning: "WARNING: Non-XML-Schema-compliant parser detected. Servlet spec <= 2.3 supported" However I ran "http://localhost:8080"; on Firefox 11 and the an 500 error code came out with the following stack trace: java.lang.NoSuchMethodError: org.dom4j.io.OutputFormat.setXHTML(Z)V at org.kohsuke.stapler.jelly.HTMLWriterOutput.createFormat(HTMLWriterOutput.java:56) at org.kohsuke.stapler.jelly.HTMLWriterO
[JIRA] (JENKINS-8854) Loading overlay does not go away
[
https://issues.jenkins-ci.org/browse/JENKINS-8854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161002#comment-161002
]
Steven Zhu commented on JENKINS-8854:
-
Hi, I got the following error on 1.456. Could you please help to resolve this
problem ?
Caused by: java.lang.VerifyError: (class:
hudson/plugins/reviewboard/ReviewboardPublisher, method:
submitChangeToReviewBoard signature:
(Ljava/lang/Long;Ljava/lang/String;Ljava/lang/Long;Ljava/lang/String;Ljava/lang/String;Ljava/util/Collection;Lhudson/model/AbstractBuild;Lhudson/Launcher;Lhudson/model/BuildListener;)Lhudson/plugins/reviewboard/ReviewInfoAction;)
Incompatible argument to function
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
at java.lang.Class.privateGetPublicFields(Class.java:2324)
at java.lang.Class.getFields(Class.java:1359)
at org.kohsuke.stapler.ClassDescriptor.(ClassDescriptor.java:69)
at org.kohsuke.stapler.MetaClass.buildDispatchers(MetaClass.java:96)
at org.kohsuke.stapler.MetaClass.(MetaClass.java:84)
at org.kohsuke.stapler.WebApp.getMetaClass(WebApp.java:182)
at
org.kohsuke.stapler.jelly.groovy.GroovyFacet.createRequestDispatcher(GroovyFacet.java:104)
at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:164)
at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:159)
at hudson.model.Descriptor.getHelpFile(Descriptor.java:644)
at hudson.model.Descriptor.getHelpFile(Descriptor.java:626)
at hudson.model.Descriptor.getHelpFile(Descriptor.java:615)
... 118 more
> Loading overlay does not go away
>
>
> Key: JENKINS-8854
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8854
> Project: Jenkins
> Issue Type: Bug
> Components: reviewboard
>Affects Versions: current
> Environment: Jenkins 1.396 and 1.398
> Google Chrome 8.0.552.237 (Official Build 70801) and FF 3.6.13
> Ubuntu 10.04, Jetty 6.1.20-2 (Ubuntu)
>Reporter: Mark Walling
>Assignee: rshelley
>
> Chrome dev tools says:
> {noformat}
> Uncaught TypeError: Cannot read property 'previousSibling' of null
> {noformat}
> on {{/hudson/static/98ea1a16/scripts/hudson-behavior.js:490}}
> Impacts my job configs and /manage configs, started with update to 398 today.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13242) Email Extension plugin - groovy and jelly do not update $rooturl after Jenkins URL updated
[ https://issues.jenkins-ci.org/browse/JENKINS-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161003#comment-161003 ] shinsato commented on JENKINS-13242: Pull request submitted. > Email Extension plugin - groovy and jelly do not update $rooturl after > Jenkins URL updated > -- > > Key: JENKINS-13242 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13242 > Project: Jenkins > Issue Type: Bug > Components: email-ext >Affects Versions: current > Environment: Windows 2008 R2 >Reporter: shinsato > > Running the Email Extension plugin - version 2.14.1 with Jenkins 1.424.6 - I > had the Jenkins URL set incorrectly which was causing broken images and the > wrong rooturl in my email-ext status message after a job built (using the > HTML and the included templates). Fixing the Jenkins URL did not fix it. I > then upgraded to Email-ext version 2.19 with Jenkins 1.457. This also did not > fix it. I'm confused because if I "echo %rooturl%" as a Windows Batch script > as a build step - it gives the right response. I can't see any place that the > plugin could be caching this info. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13287) Error on apply configuration when changing job name
Alexis Morelle created JENKINS-13287: Summary: Error on apply configuration when changing job name Key: JENKINS-13287 URL: https://issues.jenkins-ci.org/browse/JENKINS-13287 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: Alexis Morelle Jenkins shows an empty error panel when applying the configuration of a job if the job name was changed in the configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13281) Import jQuery for ui-changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161004#comment-161004 ] OHTAKE Tomohiro commented on JENKINS-13281: --- All tests in tests-harness passed. I could not find any problems while using jQuery-bundled Jenkins for half a day. I'll push to ui-changes branch. > Import jQuery for ui-changes > > > Key: JENKINS-13281 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13281 > Project: Jenkins > Issue Type: New Feature > Components: ui-changes >Reporter: OHTAKE Tomohiro >Assignee: OHTAKE Tomohiro > > Bootstrap provides useful jQuery plugins. > http://twitter.github.com/bootstrap/javascript.html > In order to use them, we should import jQuery. > Note 1: Jenkins uses prototype.js already. We have to handle conflicts. > Note 2: We have to consider about compatibility with [jQuery UI > Plugin|https://wiki.jenkins-ci.org/display/JENKINS/jQuery+Plugin] and [jQuery > Plugin|https://wiki.jenkins-ci.org/display/JENKINS/jQuery+UI+Plugin]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13281) Import jQuery for ui-changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161005#comment-161005 ] SCM/JIRA link daemon commented on JENKINS-13281: Code changed in jenkins User: OHTAKE Tomohiro Path: core/src/main/resources/lib/layout/layout.jelly war/src/main/webapp/scripts/jquery.min.js http://jenkins-ci.org/commit/jenkins/de7ba25d24894e3a4a5514f78a8837e3e9a18b7e Log: [FIXED JENKINS-13281] Add jQuery 1.7.2 min Compare: https://github.com/jenkinsci/jenkins/compare/f2b5ed2...de7ba25 > Import jQuery for ui-changes > > > Key: JENKINS-13281 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13281 > Project: Jenkins > Issue Type: New Feature > Components: ui-changes >Reporter: OHTAKE Tomohiro >Assignee: OHTAKE Tomohiro > > Bootstrap provides useful jQuery plugins. > http://twitter.github.com/bootstrap/javascript.html > In order to use them, we should import jQuery. > Note 1: Jenkins uses prototype.js already. We have to handle conflicts. > Note 2: We have to consider about compatibility with [jQuery UI > Plugin|https://wiki.jenkins-ci.org/display/JENKINS/jQuery+Plugin] and [jQuery > Plugin|https://wiki.jenkins-ci.org/display/JENKINS/jQuery+UI+Plugin]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13281) Import jQuery for ui-changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13281. Resolution: Fixed > Import jQuery for ui-changes > > > Key: JENKINS-13281 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13281 > Project: Jenkins > Issue Type: New Feature > Components: ui-changes >Reporter: OHTAKE Tomohiro >Assignee: OHTAKE Tomohiro > > Bootstrap provides useful jQuery plugins. > http://twitter.github.com/bootstrap/javascript.html > In order to use them, we should import jQuery. > Note 1: Jenkins uses prototype.js already. We have to handle conflicts. > Note 2: We have to consider about compatibility with [jQuery UI > Plugin|https://wiki.jenkins-ci.org/display/JENKINS/jQuery+Plugin] and [jQuery > Plugin|https://wiki.jenkins-ci.org/display/JENKINS/jQuery+UI+Plugin]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13281) Import jQuery for ui-changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161006#comment-161006 ] dogfood commented on JENKINS-13281: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_ui-changes_branch #10|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/10/] [FIXED JENKINS-13281] Add jQuery 1.7.2 min (Revision de7ba25d24894e3a4a5514f78a8837e3e9a18b7e) Result = SUCCESS ohtake.tomohiro : [de7ba25d24894e3a4a5514f78a8837e3e9a18b7e|https://github.com/jenkinsci/jenkins/commit/de7ba25d24894e3a4a5514f78a8837e3e9a18b7e] Files : * core/src/main/resources/lib/layout/layout.jelly * war/src/main/webapp/scripts/jquery.min.js > Import jQuery for ui-changes > > > Key: JENKINS-13281 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13281 > Project: Jenkins > Issue Type: New Feature > Components: ui-changes >Reporter: OHTAKE Tomohiro >Assignee: OHTAKE Tomohiro > > Bootstrap provides useful jQuery plugins. > http://twitter.github.com/bootstrap/javascript.html > In order to use them, we should import jQuery. > Note 1: Jenkins uses prototype.js already. We have to handle conflicts. > Note 2: We have to consider about compatibility with [jQuery UI > Plugin|https://wiki.jenkins-ci.org/display/JENKINS/jQuery+Plugin] and [jQuery > Plugin|https://wiki.jenkins-ci.org/display/JENKINS/jQuery+UI+Plugin]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13288) Config history does not appear for certain jobs
David Riley created JENKINS-13288: - Summary: Config history does not appear for certain jobs Key: JENKINS-13288 URL: https://issues.jenkins-ci.org/browse/JENKINS-13288 Project: Jenkins Issue Type: Bug Components: jobconfighistory Reporter: David Riley Assignee: Mirko Friedenhagen The job config history link is not appearing for some jobs in my setup. I can see the files under the job directory and changes appear in the overall history page (at /jobConfigHistory), but no link to the specific job. I thought it may be related to nested views/list views but created a view jobs to test this but it doesn't appear to be the case. I'm finding it difficult to tell why it doesnt work for this particular job... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13288) Config history does not appear for certain jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-13288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161007#comment-161007 ] David Riley commented on JENKINS-13288: --- I created a copy of the job in question and deleted the original, then renamed which fixed it - there's a bug there somewhere :) > Config history does not appear for certain jobs > --- > > Key: JENKINS-13288 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13288 > Project: Jenkins > Issue Type: Bug > Components: jobconfighistory >Reporter: David Riley >Assignee: Mirko Friedenhagen > > The job config history link is not appearing for some jobs in my setup. I can > see the files under the job directory and changes appear in the overall > history page (at /jobConfigHistory), but no link to the specific > job. I thought it may be related to nested views/list views but created a > view jobs to test this but it doesn't appear to be the case. I'm finding it > difficult to tell why it doesnt work for this particular job... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13289) Make 'Advanced' button collapsible
domi created JENKINS-13289: -- Summary: Make 'Advanced' button collapsible Key: JENKINS-13289 URL: https://issues.jenkins-ci.org/browse/JENKINS-13289 Project: Jenkins Issue Type: Improvement Components: ui-changes Reporter: domi Assignee: OHTAKE Tomohiro The 'Advanced' button in a configuration screen (jenkins/job/...) should be collapsible again. This would save space and make the UI more clean and intuitive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13284) ui-changes: Cannot load stylesheets during hudson-dev:run
[ https://issues.jenkins-ci.org/browse/JENKINS-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161008#comment-161008 ] domi commented on JENKINS-13284: from what I see, Kohsuke added this feature to the new jenkins-dev plugin starting jenkins with $> mvn jenkins-dev:run will set the environment variable 'hudson.Main.development' which gets used in Functions.inJenkinsDevRunMode() - which then gets used in the 'layout.jelly' to load 'less.js' in dev mode ...but it still does not work for me > ui-changes: Cannot load stylesheets during hudson-dev:run > - > > Key: JENKINS-13284 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13284 > Project: Jenkins > Issue Type: Bug > Components: ui-changes >Reporter: OHTAKE Tomohiro >Priority: Critical > > See > https://github.com/jenkinsci/jenkins/commit/c4ab05d80fd2e2fb633143421517522c42538f7b#L1R432 > Approaches: > - Modify > [maven-hudson-dev-plugin|https://github.com/jenkinsci/maven-hudson-dev-plugin] > - Use [less.js|http://lesscss.org/#-client-side-usage] if Jenkins is running > in developement mode -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13283) Unable to check workspace against depot in jenkins configuration on ubuntu
[ https://issues.jenkins-ci.org/browse/JENKINS-13283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Petti resolved JENKINS-13283. - Resolution: Incomplete Resolving as incomplete, since there's no bug description. Based on the log, this simply looks like a configuration issue. Either add p4 to your path on the system, or set up an absolute path for your perforce installation in the global jenkins configuration. > Unable to check workspace against depot in jenkins configuration on ubuntu > -- > > Key: JENKINS-13283 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13283 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: ubuntu 11.10 >Reporter: uday yatham >Assignee: Rob Petti > Labels: plugin > Fix For: current > > Attachments: bug > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12032) Include SCM changes in environment variables
[ https://issues.jenkins-ci.org/browse/JENKINS-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161010#comment-161010 ] Daniel Jones commented on JENKINS-12032: I concur that this would be useful to have. > Include SCM changes in environment variables > > > Key: JENKINS-12032 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12032 > Project: Jenkins > Issue Type: Improvement > Components: core >Affects Versions: current > Environment: All >Reporter: Jacob Jennings >Priority: Minor > Labels: envinronment-variables > Fix For: current > > > I would like to have the contents of the Changes section in an environment > variable. The application for me is that I am uploading an iOS build to > HockeyApp and want to include release notes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12032) Include SCM changes in environment variables
[ https://issues.jenkins-ci.org/browse/JENKINS-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161011#comment-161011 ] Laurent Mascherpa edited comment on JENKINS-12032 at 3/30/12 2:52 PM: -- I was sure an environment variable $CHANGE_LOG did exist but nope. It would be super useful. was (Author: sanx): I was sur an environment variable $CHANGE_LOG did exist but nope. It would be super useful. > Include SCM changes in environment variables > > > Key: JENKINS-12032 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12032 > Project: Jenkins > Issue Type: Improvement > Components: core >Affects Versions: current > Environment: All >Reporter: Jacob Jennings >Priority: Minor > Labels: envinronment-variables > Fix For: current > > > I would like to have the contents of the Changes section in an environment > variable. The application for me is that I am uploading an iOS build to > HockeyApp and want to include release notes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12032) Include SCM changes in environment variables
[ https://issues.jenkins-ci.org/browse/JENKINS-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161011#comment-161011 ] Laurent Mascherpa commented on JENKINS-12032: - I was sur an environment variable $CHANGE_LOG did exist but nope. It would be super useful. > Include SCM changes in environment variables > > > Key: JENKINS-12032 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12032 > Project: Jenkins > Issue Type: Improvement > Components: core >Affects Versions: current > Environment: All >Reporter: Jacob Jennings >Priority: Minor > Labels: envinronment-variables > Fix For: current > > > I would like to have the contents of the Changes section in an environment > variable. The application for me is that I am uploading an iOS build to > HockeyApp and want to include release notes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13290) MS Test plugin does not correctly wrap it's call to the command line in quotation marks.
Logan Daigle created JENKINS-13290: -- Summary: MS Test plugin does not correctly wrap it's call to the command line in quotation marks. Key: JENKINS-13290 URL: https://issues.jenkins-ci.org/browse/JENKINS-13290 Project: Jenkins Issue Type: Bug Components: mstest Environment: windows server 2003, Visual Studio 2008 Reporter: Logan Daigle When attempting to run MSTEST from the mstest plugin the plugin does not correctly wrap files in quotation marks. The problem occurs if the file being run after the /testcontainer switch requires quotation marks because it contains spaces in its path. The help for cmd.exe specifically has requirements for calling cmd.exe /c that cause issues when both the executable for mstest and the test container have spaces in their paths. The work around is to use the functionality in Jenkins that allows batch files to run mstest instead of the plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13289) Make 'Advanced' button collapsible
[ https://issues.jenkins-ci.org/browse/JENKINS-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13289. Resolution: Fixed > Make 'Advanced' button collapsible > -- > > Key: JENKINS-13289 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13289 > Project: Jenkins > Issue Type: Improvement > Components: ui-changes >Reporter: domi >Assignee: OHTAKE Tomohiro > > The 'Advanced' button in a configuration screen (jenkins/job/...) should be > collapsible again. > This would save space and make the UI more clean and intuitive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13289) Make 'Advanced' button collapsible
[ https://issues.jenkins-ci.org/browse/JENKINS-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161012#comment-161012 ] SCM/JIRA link daemon commented on JENKINS-13289: Code changed in jenkins User: OHTAKE Tomohiro Path: core/src/main/resources/jenkins/security/ApiTokenProperty/config.groovy core/src/main/resources/lib/form/advanced.jelly war/src/main/webapp/scripts/hudson-behavior.js http://jenkins-ci.org/commit/jenkins/2e1a0f670cb0837616338ce550a4c39cb2bf2f2c Log: [FIXED JENKINS-13289] "Advanced" button can collapse its body - Advanced body is now placed inside the same tbody, there is no need to handle nameref any more. - A lot of people miss advanced buttons. It's better to change color. > Make 'Advanced' button collapsible > -- > > Key: JENKINS-13289 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13289 > Project: Jenkins > Issue Type: Improvement > Components: ui-changes >Reporter: domi >Assignee: OHTAKE Tomohiro > > The 'Advanced' button in a configuration screen (jenkins/job/...) should be > collapsible again. > This would save space and make the UI more clean and intuitive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13260) Can't hide advanced configuration
[ https://issues.jenkins-ci.org/browse/JENKINS-13260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13260. --- Resolution: Duplicate > Can't hide advanced configuration > - > > Key: JENKINS-13260 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13260 > Project: Jenkins > Issue Type: Improvement > Components: ui-changes >Reporter: Tom Bevers >Priority: Minor > > After clicking on the advanced button in the configuration form, you can't > hide the advanced configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13289) Make 'Advanced' button collapsible
[ https://issues.jenkins-ci.org/browse/JENKINS-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161013#comment-161013 ] dogfood commented on JENKINS-13289: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_ui-changes_branch #11|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/11/] [FIXED JENKINS-13289] "Advanced" button can collapse its body (Revision 2e1a0f670cb0837616338ce550a4c39cb2bf2f2c) Result = SUCCESS ohtake.tomohiro : [2e1a0f670cb0837616338ce550a4c39cb2bf2f2c|https://github.com/jenkinsci/jenkins/commit/2e1a0f670cb0837616338ce550a4c39cb2bf2f2c] Files : * core/src/main/resources/jenkins/security/ApiTokenProperty/config.groovy * war/src/main/webapp/scripts/hudson-behavior.js * core/src/main/resources/lib/form/advanced.jelly > Make 'Advanced' button collapsible > -- > > Key: JENKINS-13289 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13289 > Project: Jenkins > Issue Type: Improvement > Components: ui-changes >Reporter: domi >Assignee: OHTAKE Tomohiro > > The 'Advanced' button in a configuration screen (jenkins/job/...) should be > collapsible again. > This would save space and make the UI more clean and intuitive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11097) Jobs get aborted with "Command close created" as cause in the stacktrace
[ https://issues.jenkins-ci.org/browse/JENKINS-11097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161014#comment-161014 ] Richard Mortimer commented on JENKINS-11097: For reference the remoting changes above (at https://github.com/jenkinsci/remoting/compare/01a6df7...d94bb55 ) have been contributing to JENKINS-12037 My proposed fix is at https://github.com/jenkinsci/remoting/pull/3 > Jobs get aborted with "Command close created" as cause in the stacktrace > > > Key: JENKINS-11097 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11097 > Project: Jenkins > Issue Type: Bug > Components: core > Environment: 1.429 >Reporter: Cees Bos >Priority: Critical > > We random see jobs getting aborted with the stacktraces below. > We see this for long running jobs, which execute a large set of JUnit tests. > Windows 2008 machine (x64) > FATAL: Unable to delete script file > C:\Windows\TEMP\hudson7878511792654741097.bat > hudson.util.IOException2: remote file operation failed: > C:\Windows\TEMP\hudson7878511792654741097.bat at > hudson.remoting.Channel@5a171ae3:srv-nl-crd05 > at hudson.FilePath.act(FilePath.java:754) > at hudson.FilePath.act(FilePath.java:740) > at hudson.FilePath.delete(FilePath.java:995) > at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:92) > at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:693) > at hudson.model.Build$RunnerImpl.build(Build.java:178) > at hudson.model.Build$RunnerImpl.doRun(Build.java:139) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:459) > at hudson.model.Run.run(Run.java:1376) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:230) > Caused by: hudson.remoting.ChannelClosedException: channel is already closed > at hudson.remoting.Channel.send(Channel.java:492) > at hudson.remoting.Request.call(Request.java:110) > at hudson.remoting.Channel.call(Channel.java:674) > at hudson.FilePath.act(FilePath.java:747) > ... 13 more > Caused by: hudson.remoting.Channel$OrderlyShutdown > at hudson.remoting.Channel$CloseCommand.execute(Channel.java:819) > at hudson.remoting.Channel$ReaderThread.run(Channel.java:1071) > Caused by: Command close created at > at hudson.remoting.Command.(Command.java:62) > at hudson.remoting.Command.(Command.java:47) > at hudson.remoting.Channel$CloseCommand.(Channel.java:815) > at hudson.remoting.Channel$CloseCommand.(Channel.java:815) > at hudson.remoting.Channel.close(Channel.java:860) > at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:112) > at hudson.remoting.PingThread.ping(PingThread.java:107) > at hudson.remoting.PingThread.run(PingThread.java:81) > FATAL: hudson.remoting.RequestAbortedException: > hudson.remoting.Channel$OrderlyShutdown > hudson.remoting.RequestAbortedException: > hudson.remoting.RequestAbortedException: > hudson.remoting.Channel$OrderlyShutdown > at hudson.remoting.Request.call(Request.java:149) > at hudson.remoting.Channel.call(Channel.java:674) > at > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) > at $Proxy35.join(Unknown Source) > at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:850) > at hudson.Launcher$ProcStarter.join(Launcher.java:336) > at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82) > at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:693) > at hudson.model.Build$RunnerImpl.build(Build.java:178) > at hudson.model.Build$RunnerImpl.doRun(Build.java:139) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:459) > at hudson.model.Run.run(Run.java:1376) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:230) > Caused by: hudson.remoting.RequestAbortedException: > hudson.remoting.Channel$OrderlyShutdown > at hudson.remoting.Request.abort(Request.java:273) > at hudson.remoting.Channel.terminate(Channel.java:725) > at hudson.remoting.Channel$
[JIRA] (JENKINS-13291) Code with javadoc doesnt perform maven release
Lucio Camilo created JENKINS-13291: -- Summary: Code with javadoc doesnt perform maven release Key: JENKINS-13291 URL: https://issues.jenkins-ci.org/browse/JENKINS-13291 Project: Jenkins Issue Type: Bug Components: maven2 Affects Versions: current Environment: Red Hat Linux 5. Reporter: Lucio Camilo Attachments: jenkins.txt If I try to perform maven release to one code with javadoc like @param, @description and others, it output some messages like: Tag @author cannot be used in method documentation @description is an unknown tag. Entire log error was attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12911) Clearecase Plugin Not Detecting Changes
[
https://issues.jenkins-ci.org/browse/JENKINS-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161015#comment-161015
]
jfigler commented on JENKINS-12911:
---
We're seeing this too... did you ever figure it out?
> Clearecase Plugin Not Detecting Changes
> ---
>
> Key: JENKINS-12911
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12911
> Project: Jenkins
> Issue Type: Bug
> Components: clearcase
> Environment: Windows 7
>Reporter: Justin Bailey
>Assignee: Vincent Latombe
>
> I am using the Clearcase plugin to poll for changes and trigger a build.
> However, even when changes are clearly present, no build is triggered. Here's
> the log from a poll showing a change:
> {quote}
> Started on Feb 27, 2012 5:05:09 PM
> [baileyj_master_Build_OF012_hudson] $ "c:\Program
> Files\IBM\RationalSDLC\ClearCase\bin\cleartool" pwv -root
> C:\Users\baileyj\.jenkins\jobs\Build
> OF012\workspace\baileyj_master_Build_OF012_hudson
> [workspace] $ "c:\Program Files\IBM\RationalSDLC\ClearCase\bin\cleartool"
> lsview baileyj_master_Build_OF012_hudson
> baileyj_master_Build_OF012_hudson
> \\ds-wccreg2.ds.ad.foo.com\viewstore\DS\baileyj\baileyj_master_Build_OF012_hudson.vws
> [baileyj_master_Build_OF012_hudson] $ "c:\Program
> Files\IBM\RationalSDLC\ClearCase\bin\cleartool" lshistory -all -since
> 28-feb-12.00:46:58utc+ -fmt '\"%Nd\" \"%u\" \"%En\" \"%Vn\" \"%e\" \"%o\"
> \n%c\n' -branch brtype:of012 -nco web2000/of_app/of
> "20120227.170348" "baileyj" "C:\Users\baileyj\.jenkins\jobs\Build
> OF012\workspace\baileyj_master_Build_OF012_hudson\web2000\mm_app\we\sdk\test\autoload\ofadmin.ppk"
> "\main\of012\4" "create version" "checkin"
> Done. Took 0.93 sec
> No changes
> {quote}
> As should be clear, the file "ofadmin.ppk" shows a change, but the plugin did
> not detect it.
> I'm running Jenkins v1.451 and ClearCase Plug-in v1.3.7.
> If there is a mailing list where I can ask this question, please let me know.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13284) ui-changes: Cannot load stylesheets during hudson-dev:run
[ https://issues.jenkins-ci.org/browse/JENKINS-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161016#comment-161016 ] Kohsuke Kawaguchi commented on JENKINS-13284: - Yes, in my environment this resulted in "Calling the charAt method on undefined" or something. Unfortunately, less.js is minimized and I couldn't find a full version to debug this issue further, but I committed it nonetheless so that folks who are more familiar with less.js can take a look at what's going on. > ui-changes: Cannot load stylesheets during hudson-dev:run > - > > Key: JENKINS-13284 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13284 > Project: Jenkins > Issue Type: Bug > Components: ui-changes >Reporter: OHTAKE Tomohiro >Priority: Critical > > See > https://github.com/jenkinsci/jenkins/commit/c4ab05d80fd2e2fb633143421517522c42538f7b#L1R432 > Approaches: > - Modify > [maven-hudson-dev-plugin|https://github.com/jenkinsci/maven-hudson-dev-plugin] > - Use [less.js|http://lesscss.org/#-client-side-usage] if Jenkins is running > in developement mode -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13292) Problem to update to a tagged revision
Helen Her created JENKINS-13292: --- Summary: Problem to update to a tagged revision Key: JENKINS-13292 URL: https://issues.jenkins-ci.org/browse/JENKINS-13292 Project: Jenkins Issue Type: Bug Components: mercurial Affects Versions: current Reporter: Helen Her Assignee: Kohsuke Kawaguchi In the previous version we were able to clone the remote repository and update it to a tagged revision as you can see the log here, v4.6.0.118 it's the tag of the branch r4.6.0.118 $ hg clone --rev v4.6.0.118 remote_repository_url local_repository adding changesets adding manifests adding file changes added 199 changesets with 13401 changes to 6466 files updating to branch r4.6.0.118 But when we updated the plugin to the version 1.38, we couldn't clone the remote repository and update it to a tagged revision $ hg clone --rev v4.6.0.118 --noupdate remote_repository_url local_repository adding changesets adding manifests adding file changes added 199 changesets with 13401 changes to 6466 files [v4.6.0.118] $ hg update --rev v4.6.0.118 abort: unknown revision 'v4.6.0.118'! So we had to downgrade the mercurial plugin to 1.37 for the time being. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12032) Include SCM changes in environment variables
[ https://issues.jenkins-ci.org/browse/JENKINS-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161017#comment-161017 ] Oliver H commented on JENKINS-12032: If you are interested in uploading your build to HockeyApp (with release notes and some other stuff) You may try my plugin at: https://github.com/ohoeltke/hockeyapp-plugin Will try to update the binary this weekend, master branch is current > Include SCM changes in environment variables > > > Key: JENKINS-12032 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12032 > Project: Jenkins > Issue Type: Improvement > Components: core >Affects Versions: current > Environment: All >Reporter: Jacob Jennings >Priority: Minor > Labels: envinronment-variables > Fix For: current > > > I would like to have the contents of the Changes section in an environment > variable. The application for me is that I am uploading an iOS build to > HockeyApp and want to include release notes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13112) Adding any post-build step as a build step causes exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161018#comment-161018 ] Anthony Hartwig commented on JENKINS-13112: --- Domi, My correct Jenkins version is as I stated before, 1.424.6. I attempted installing the m2-extra-steps plugin and was still receiving the null pointer with the multiple steps. I've attached the single step as requested. > Adding any post-build step as a build step causes exception > --- > > Key: JENKINS-13112 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13112 > Project: Jenkins > Issue Type: Bug > Components: conditional-buildstep > Environment: Windows Server 2008 >Reporter: Anthony Hartwig >Assignee: domi > Attachments: screenshot.jpg, Single step.jpg, stacktrace.txt > > > When attempting to add a post build step as a build step, then click save, an > exception is thrown. Stack trace attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13112) Adding any post-build step as a build step causes exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Hartwig updated JENKINS-13112: -- Attachment: Single step.jpg > Adding any post-build step as a build step causes exception > --- > > Key: JENKINS-13112 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13112 > Project: Jenkins > Issue Type: Bug > Components: conditional-buildstep > Environment: Windows Server 2008 >Reporter: Anthony Hartwig >Assignee: domi > Attachments: screenshot.jpg, Single step.jpg, stacktrace.txt > > > When attempting to add a post build step as a build step, then click save, an > exception is thrown. Stack trace attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12037) CLI - I/O error in channel Chunked connection/Unexpected termination of the channel - still occurring in Jenkins 1.449
[ https://issues.jenkins-ci.org/browse/JENKINS-12037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161019#comment-161019 ] mark streit commented on JENKINS-12037: --- Richard THANK YOU for this... it appears to be WORKING NOW :-). We are using your snapshot build below and the GA Jenkins 1.457 version (WAR) and running on Tomcat 7.0.22. (not Winstone anymore). The connection is not dropped and the jobs sequence runs to completion. Is it safe to assume the fixed version will be part of the official 1.459 release? We really appreciate your time and help with getting this fixed. > CLI - I/O error in channel Chunked connection/Unexpected termination of the > channel - still occurring in Jenkins 1.449 > -- > > Key: JENKINS-12037 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12037 > Project: Jenkins > Issue Type: Bug > Components: cli > Environment: * Running on SLES9 Linux server with 4 CPUs and plenty > of diskspace. > * Tomcat 7.0.22 > * JDK 1.6.0_14 > * Only ONE Master configuration - no slaves are configured > * 3 Executors - (one less than the max number of CPUs) >Reporter: mark streit >Priority: Critical > Attachments: jenkins-timeout, Tomcat7_Jenkins1449_logs.zip > > > We reported an issue some time back that was also listed as fixed in Jenkins > 1.441: > Log: > [FIXED JENKINS-11130] SEVERE: I/O error in channel Chunked connection when > using jenkins-cli.jar > Perhaps another bug should NOT be submitted so I have added the following > comments below the line to the original defect 11130 comments section in case > it can be reviewed/re-opened. > We did NOT try to make any adjustments to the Tomcat configuration: > Tomcat Connector connectionUploadTimeout > but we are also now seeing the same problem with Winstone when at this same > 1.441 level. We did revert to the 1.438 version of the CLI (leaving the WAR > at 1.441 running in Winstone) and that is serving asthe current workaround. > > We have downloaded and installed the LATEST 1.441 release that lists the fix > for this problem. Currently we were running 1.438 on Winstone only (since > with Tomcat 6 or 7, we had experienced the error HOWEVER yet under Winstone, > it worked OK so that was our workaround - while running 1.438). > Now with Jenkins 1.441 - we are getting the ERROR again and NOW WITH BOTH > Winstone and the Tomcat configurations). We have left the Jenkins 1.441 WAR > file in place running on Winstone, and reverted the CLI jar file back to the > 1.438 version for now and that appears to work again with Winstone. > Checked Manifest of CLI jar downloaded with the 1.441 WAR installation: > Manifest-Version: 1.0 > Archiver-Version: Plexus Archiver > Created-By: Apache Maven > Built-By: kohsuke > Build-Jdk: 1.6.0_26 > Main-Class: hudson.cli.CLI > Jenkins-CLI-Version: 1.441 > Under Tomcat 7, we get this stacktrace: > Started by command line > [workspace] $ /bin/bash -xe > /opt/apache-tomcat-7.0.22_jenkins/temp/hudson3281734817830.sh > + /opt/Sun/jdk1.6.0_14/bin/java -jar /opt/Sun/jdk1.6.0_14/lib/jenkins-cli.jar > -s http://11.22.33.44:8082/jenkins/ build XYZ_Project-SharedLibs -s -p > SVN_PATH=trunk > Dec 5, 2011 12:59:11 PM hudson.remoting.Channel$ReaderThread run > SEVERE: I/O error in channel Chunked connection to > http://11.22.33.44:8082/jenkins/cli > java.io.IOException: Unexpected termination of the channel > at hudson.remoting.Channel$ReaderThread.run(Channel.java:1115) > Caused by: java.io.EOFException > at > java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2554) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) > at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109) > Exception in thread "main" hudson.remoting.RequestAbortedException: > hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected > termination of the channel > at hudson.remoting.Request.call(Request.java:149) > at hudson.remoting.Channel.call(Channel.java:681) > at > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) > at $Proxy2.main(Unknown Source) > at hudson.cli.CLI.execute(CLI.java:200) > at hudson.cli.CLI._main(CLI.java:330) > at hudson.cli.CLI.main(CLI.java:245) > Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: > Unexpected termination of the channel > at hudson.remoting.Request.abort(Request.java:273) > at hudson.remoting.Channel.terminate(Channel.java:732) > at hudson.remoting.Channel$ReaderThread.run(Channel.j
[JIRA] (JENKINS-9223) cmake plugin swallows additional arguments containing = characters
[
https://issues.jenkins-ci.org/browse/JENKINS-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
evernat updated JENKINS-9223:
-
Component/s: cmakebuilder
(was: plugin)
fixing the component in this issue
> cmake plugin swallows additional arguments containing = characters
> --
>
> Key: JENKINS-9223
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9223
> Project: Jenkins
> Issue Type: Bug
> Components: cmakebuilder
> Environment: Linux host and guests, cmake plugin version 1.8
>Reporter: Johannes Wienke
>
> The cmake plugin swallows additional cmake arguments given with a -D option
> if the value of the argument contains a = character. For instance this works
> perfectly:
> -DRSC_DIR=${WORKSPACE}/RSC/labelfoo
> but:
> -DRSC_DIR=${WORKSPACE}/RSC/label=foo
> is not passed to the called cmake. On a normal command line in linux this is
> not a problem for cmake. I've also tried to quote the path with no success.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13293) Add cron syntax to set Time Zone
Michael Haderman created JENKINS-13293: -- Summary: Add cron syntax to set Time Zone Key: JENKINS-13293 URL: https://issues.jenkins-ci.org/browse/JENKINS-13293 Project: Jenkins Issue Type: Improvement Components: buildresult-trigger Reporter: Michael Haderman It would be nice to have the ability to set what time zone scheduled builds should run in. Common crontab syntax is TZ=GMT 30 11 * * * -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13294) Automatically release failed builds after the job begins passing
C Girard created JENKINS-13294: -- Summary: Automatically release failed builds after the job begins passing Key: JENKINS-13294 URL: https://issues.jenkins-ci.org/browse/JENKINS-13294 Project: Jenkins Issue Type: New Feature Components: build-keeper-plugin Reporter: C Girard Assignee: bap Priority: Minor It would be nice if under the "Keep the first failed build in a run of failures" there was a checkbox for "Release this build once the project is fixed". I really only need the failing build info (svn revision, console log) for debugging the cause of the failure, but want it to be released after the job has been fixed so it will be discarded automatically like the other builds. In our setup we have over 30 jobs and it is very common throughout the day for a job to switch to red briefly because of a typo or some other minor error and then go green (blue) again. The number of kept failing builds in the system would grow large fairly quickly without an option like this (or somebody doing a daily/weekly sweep to manually purge them). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12037) CLI - I/O error in channel Chunked connection/Unexpected termination of the channel - still occurring in Jenkins 1.449
[ https://issues.jenkins-ci.org/browse/JENKINS-12037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161021#comment-161021 ] Richard Mortimer commented on JENKINS-12037: Yes it will be part of 1.459. The snapshot build that you tested is direct from Jenkins on Jenkins builds. I mentioned it earlier but the current fix actually busy-waits during the ping cycle so you may see high cpu usage from the cli command. The busy-wait is fixed by the change that I have submitted to the underlying "remoting" library. That might take a release or two to filter through. Finally we should really say thank you to George who managed to get a packet trace with the failure so that we could work out what was going on. > CLI - I/O error in channel Chunked connection/Unexpected termination of the > channel - still occurring in Jenkins 1.449 > -- > > Key: JENKINS-12037 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12037 > Project: Jenkins > Issue Type: Bug > Components: cli > Environment: * Running on SLES9 Linux server with 4 CPUs and plenty > of diskspace. > * Tomcat 7.0.22 > * JDK 1.6.0_14 > * Only ONE Master configuration - no slaves are configured > * 3 Executors - (one less than the max number of CPUs) >Reporter: mark streit >Priority: Critical > Attachments: jenkins-timeout, Tomcat7_Jenkins1449_logs.zip > > > We reported an issue some time back that was also listed as fixed in Jenkins > 1.441: > Log: > [FIXED JENKINS-11130] SEVERE: I/O error in channel Chunked connection when > using jenkins-cli.jar > Perhaps another bug should NOT be submitted so I have added the following > comments below the line to the original defect 11130 comments section in case > it can be reviewed/re-opened. > We did NOT try to make any adjustments to the Tomcat configuration: > Tomcat Connector connectionUploadTimeout > but we are also now seeing the same problem with Winstone when at this same > 1.441 level. We did revert to the 1.438 version of the CLI (leaving the WAR > at 1.441 running in Winstone) and that is serving asthe current workaround. > > We have downloaded and installed the LATEST 1.441 release that lists the fix > for this problem. Currently we were running 1.438 on Winstone only (since > with Tomcat 6 or 7, we had experienced the error HOWEVER yet under Winstone, > it worked OK so that was our workaround - while running 1.438). > Now with Jenkins 1.441 - we are getting the ERROR again and NOW WITH BOTH > Winstone and the Tomcat configurations). We have left the Jenkins 1.441 WAR > file in place running on Winstone, and reverted the CLI jar file back to the > 1.438 version for now and that appears to work again with Winstone. > Checked Manifest of CLI jar downloaded with the 1.441 WAR installation: > Manifest-Version: 1.0 > Archiver-Version: Plexus Archiver > Created-By: Apache Maven > Built-By: kohsuke > Build-Jdk: 1.6.0_26 > Main-Class: hudson.cli.CLI > Jenkins-CLI-Version: 1.441 > Under Tomcat 7, we get this stacktrace: > Started by command line > [workspace] $ /bin/bash -xe > /opt/apache-tomcat-7.0.22_jenkins/temp/hudson3281734817830.sh > + /opt/Sun/jdk1.6.0_14/bin/java -jar /opt/Sun/jdk1.6.0_14/lib/jenkins-cli.jar > -s http://11.22.33.44:8082/jenkins/ build XYZ_Project-SharedLibs -s -p > SVN_PATH=trunk > Dec 5, 2011 12:59:11 PM hudson.remoting.Channel$ReaderThread run > SEVERE: I/O error in channel Chunked connection to > http://11.22.33.44:8082/jenkins/cli > java.io.IOException: Unexpected termination of the channel > at hudson.remoting.Channel$ReaderThread.run(Channel.java:1115) > Caused by: java.io.EOFException > at > java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2554) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) > at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109) > Exception in thread "main" hudson.remoting.RequestAbortedException: > hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected > termination of the channel > at hudson.remoting.Request.call(Request.java:149) > at hudson.remoting.Channel.call(Channel.java:681) > at > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) > at $Proxy2.main(Unknown Source) > at hudson.cli.CLI.execute(CLI.java:200) > at hudson.cli.CLI._main(CLI.java:330) > at hudson.cli.CLI.main(CLI.java:245) > Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: > Unexpected termination of the channel > at hudson.remoting.Request.abort(R
[JIRA] (JENKINS-13242) Email Extension plugin - groovy and jelly do not update $rooturl after Jenkins URL updated
[ https://issues.jenkins-ci.org/browse/JENKINS-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161023#comment-161023 ] SCM/JIRA link daemon commented on JENKINS-13242: Code changed in jenkins User: slide Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java http://jenkins-ci.org/commit/email-ext-plugin/bb8616fa7e143c3e850dade97f09288b4afe5c3a Log: Merge pull request #34 from hajush/master Fix JENKINS-13242 - global settings always overriding husdonUrl Compare: https://github.com/jenkinsci/email-ext-plugin/compare/6077a78...bb8616f > Email Extension plugin - groovy and jelly do not update $rooturl after > Jenkins URL updated > -- > > Key: JENKINS-13242 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13242 > Project: Jenkins > Issue Type: Bug > Components: email-ext >Affects Versions: current > Environment: Windows 2008 R2 >Reporter: shinsato > > Running the Email Extension plugin - version 2.14.1 with Jenkins 1.424.6 - I > had the Jenkins URL set incorrectly which was causing broken images and the > wrong rooturl in my email-ext status message after a job built (using the > HTML and the included templates). Fixing the Jenkins URL did not fix it. I > then upgraded to Email-ext version 2.19 with Jenkins 1.457. This also did not > fix it. I'm confused because if I "echo %rooturl%" as a Windows Batch script > as a build step - it gives the right response. I can't see any place that the > plugin could be caching this info. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13242) Email Extension plugin - groovy and jelly do not update $rooturl after Jenkins URL updated
[ https://issues.jenkins-ci.org/browse/JENKINS-13242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161022#comment-161022 ] SCM/JIRA link daemon commented on JENKINS-13242: Code changed in jenkins User: Harold Shinsato Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java http://jenkins-ci.org/commit/email-ext-plugin/b6563fa1cbaeb0571a2f826045b85f9e9c8e9f4c Log: Fix for JENKINS-13242 > Email Extension plugin - groovy and jelly do not update $rooturl after > Jenkins URL updated > -- > > Key: JENKINS-13242 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13242 > Project: Jenkins > Issue Type: Bug > Components: email-ext >Affects Versions: current > Environment: Windows 2008 R2 >Reporter: shinsato > > Running the Email Extension plugin - version 2.14.1 with Jenkins 1.424.6 - I > had the Jenkins URL set incorrectly which was causing broken images and the > wrong rooturl in my email-ext status message after a job built (using the > HTML and the included templates). Fixing the Jenkins URL did not fix it. I > then upgraded to Email-ext version 2.19 with Jenkins 1.457. This also did not > fix it. I'm confused because if I "echo %rooturl%" as a Windows Batch script > as a build step - it gives the right response. I can't see any place that the > plugin could be caching this info. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13295) Jenkins hangs for ~1 hour after posting 'Sending Email'
Devin Barbieri created JENKINS-13295: Summary: Jenkins hangs for ~1 hour after posting 'Sending Email' Key: JENKINS-13295 URL: https://issues.jenkins-ci.org/browse/JENKINS-13295 Project: Jenkins Issue Type: Bug Components: email-ext Reporter: Devin Barbieri Priority: Critical -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13280) Fix for JENKINS-9118 breaks archival if symlink referent is in the archive
[ https://issues.jenkins-ci.org/browse/JENKINS-13280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Morris updated JENKINS-13280: --- Component/s: core I'm adding core to the components, since it seems like FilePath is part of the core even though JENKINS-9118 listed clone-workspace as the component. > Fix for JENKINS-9118 breaks archival if symlink referent is in the archive > -- > > Key: JENKINS-13280 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13280 > Project: Jenkins > Issue Type: Bug > Components: clone-workspace, core >Reporter: Brian Morris >Assignee: abayer > > With the fix for JENKINS-9118, the archival process now attempts to preserve > symlinks, but in doing so it now fails to archive if the referent of a > symlink doesn't exist (yet). The problem is that it is apparently trying to > chmod the symlink (which it shouldn't be doing to extract a symlink anyway) > but that fails if the target of the symlink doesn't exist. In our case it > was because the target was also in the archive and hadn't been extracted yet. > Archiving artifacts > ERROR: Failed to archive artifacts: > linux86-deploy/*,solaris2-cross-linux86/*,test21/products/*,src/configuration/defaults/**/*,src/target/**/* > hudson.util.IOException2: hudson.util.IOException2: Failed to extract > /home/jarvis/probebuild/jenkins/workspace/Tools_Linux86_Solaris2_P44/linux86-deploy/*,solaris2-cross-linux86/*,test21/products/*,src/configuration/defaults/**/*,src/target/**/* > at hudson.FilePath.readFromTar(FilePath.java:1817) > at hudson.FilePath.copyRecursiveTo(FilePath.java:1729) > at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656) > at hudson.model.Build$RunnerImpl.post2(Build.java:162) > at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625) > at hudson.model.Run.run(Run.java:1435) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:238) > Caused by: java.io.IOException: Failed to chmod > /home/hal/jenkins/home/jobs/Tools_Linux86_Solaris2_P44/builds/2012-03-28_16-02-44/archive/linux86-deploy/.bochsrc > : No such file or directory > at hudson.FilePath._chmod(FilePath.java:1248) > at hudson.FilePath.readFromTar(FilePath.java:1813) > ... 12 more > at hudson.FilePath.copyRecursiveTo(FilePath.java:1736) > at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656) > at hudson.model.Build$RunnerImpl.post2(Build.java:162) > at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625) > at hudson.model.Run.run(Run.java:1435) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:238) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Pipe > is already closed > at hudson.remoting.Channel$2.adapt(Channel.java:714) > at hudson.remoting.Channel$2.adapt(Channel.java:709) > at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) > at hudson.FilePath.copyRecursiveTo(FilePath.java:1732) > ... 11 more > Caused by: java.io.IOException: Pipe is already closed > at hudson.remoting.PipeWindow.checkDeath(PipeWindow.java:83) > at hudson.remoting.PipeWindow$Real.get(PipeWindow.java:171) > at hudson.remoting.ProxyOutputStream._write(ProxyOutputStream.java:118) > at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:103) > at > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) > at java.io.BufferedOutputStream.write(BufferedOutputStream.java:126) > at > java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:178) > at > java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:135) > at jav
[JIRA] (JENKINS-13296) Changelists that include excluded files and files outside of the client view will trigger a build.
Patrick McKeown created JENKINS-13296: - Summary: Changelists that include excluded files and files outside of the client view will trigger a build. Key: JENKINS-13296 URL: https://issues.jenkins-ci.org/browse/JENKINS-13296 Project: Jenkins Issue Type: Improvement Components: perforce Reporter: Patrick McKeown Priority: Minor If there is already a way to handle this I apologize, looked around but didn't find anything. Given a client spec //depot/test/... //client/test/... with an exclude list such as //depot/test/exclude/... and polling turned on- if someone submits a changelist with an excluded file and a file outside the client spec such as changelist 1234 //depot/test/exclude/example.txt#1 //depot/test2/example2.txt#1 then //depot/test2/example2.txt#1 will trigger the build as it does not match anything in the exclude list. I would like a way to consider any files outside of the client spec as excluded files without actually having to specify them. Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13254) loadAllBuildHistory fails with 404
[ https://issues.jenkins-ci.org/browse/JENKINS-13254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sogabe resolved JENKINS-13254. -- Resolution: Duplicate > loadAllBuildHistory fails with 404 > -- > > Key: JENKINS-13254 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13254 > Project: Jenkins > Issue Type: Bug > Components: core >Reporter: lukas rytz > > On https://scala-webapps.epfl.ch/jenkins/job/scala-checkin/ clicking > "More..." to see all builds fails. The system log does not provide any > information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13238) Loading All Build History Fails
[ https://issues.jenkins-ci.org/browse/JENKINS-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161025#comment-161025 ] OHTAKE Tomohiro commented on JENKINS-13238: --- http://ci.jenkins-ci.org/view/All/job/jenkins_main_trunk/buildHistory/all/ -> 404 http://ci.jenkins-ci.org/view/All/job/jenkins_main_trunk/buildHistory/all -> OK Recently, Stapler has changed its behavior on last slash in URI. https://github.com/stapler/stapler/commit/9604f1e4c796bfd24175a8fff44caaec0cdfe065 JENKINS-12005 > Loading All Build History Fails > --- > > Key: JENKINS-13238 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13238 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: linux, jenkins 1.456 >Reporter: Spencer Oliver > > seems after the update from 1.455 to 1.456 causes an issue where pressing > 'More' to expand the job Build History now fails with a 404. > Calling the build history directly also causes the 404, eg. > http://openocd.zylin.com/jenkins/job/openocd/buildHistory/all/ > For info rolling back to 1.455 cures the problem. > tested 1.457 and issue still present. > jenkins own server also shows the issue: > http://ci.jenkins-ci.org/view/All/job/jenkins_main_trunk/buildHistory/all/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11150) Enable integration with customised Gerrit review categories
[ https://issues.jenkins-ci.org/browse/JENKINS-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161026#comment-161026 ] sdirector commented on JENKINS-11150: - We're working on getting this upstreamed... but until then: https://github.com/openstack-ci/gerrit-trigger-plugin We've been working with the guys from Ericsson to have gerrit respond to multiple event types. One of them is "comment added" - which allows you to respond to any of those. We, in fact, have customized categories and respond to them in our Jenkins. > Enable integration with customised Gerrit review categories > --- > > Key: JENKINS-11150 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11150 > Project: Jenkins > Issue Type: Improvement > Components: gerrit >Reporter: Peter van Zetten >Assignee: jyrkiput >Priority: Minor > > In some projects it may be the case that the Gerrit instance has been > configured with customised review categories, for example to meet more > stringent internal/external PA requirements than the default "code-review" > and "verified". The Gerrit plugin for Jenkins is hard-coded to allow review > of only the two default categories, and therefore cannot integrate with any > such customised instance. > The proposed improvement would be to retrieve the list of available > categories for the selected Gerrit instance, and allow the plugin to be > configured to update any of them. > The list of available review categories can be retrieved from the Gerrit SSH > CLI with the command "ssh -p gerrit approve --help". The output > of this command can be parsed to provide the plugin configuration options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
