[JIRA] (JENKINS-14287) Selective RSS feed for updates of Jenkins and installed plugins
Rüdiger zu Dohna created JENKINS-14287 Selective RSS feed for updates of Jenkins and installed plugins Issue Type: New Feature Assignee: Unassigned Components: plugin Created: 03/Jul/12 6:50 AM Description: It would be nice if my local Jenkins would provide an RSS filter for new releases of Jenkins itself and all plugins I've installed, so I'll actively be informed as soon as I can do an update, and won't have to check manually and regularily. Project: Jenkins Priority: Major Reporter: Rüdiger zu Dohna 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
[JIRA] (JENKINS-14017) main-page can't show picture/icon before login
Andreas Sandberg closed JENKINS-14017 as Not A Defect main-page can't show picture/icon before login Fixed in the Greenballs plugin (version 1.12). https://wiki.jenkins-ci.org/display/JENKINS/Green+Balls Change By: Andreas Sandberg (03/Jul/12 6:46 AM) Status: Open Closed Fix Version/s: current Resolution: Not A Defect 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
[JIRA] (JENKINS-14017) main-page can't show picture/icon before login
Andreas Sandberg commented on JENKINS-14017 main-page can't show picture/icon before login I've just realized that this bug is not related to Jenkins (core) but is related to the GreenBalls plugin (didnt realize that when I edited the issue). The good news is that this issue is already solved in the GreenBalls plugin (version 1.12). So in order to fix this, update your greenballs plugin to the current version. See release notes: https://wiki.jenkins-ci.org/display/JENKINS/Green+Balls 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
[JIRA] (JENKINS-14017) main-page can't show picture/icon before login
Andreas Sandberg updated JENKINS-14017 main-page can't show picture/icon before login Change By: Andreas Sandberg (03/Jul/12 6:24 AM) Attachment: FullStacktrace.txt Environment: jenkins:1.464OS:LINux Alternative environment:Jenkins 1.473Using Active Directory plugin for authentication.OS: Windows Server 2008 Description: Before user login , the picuture of web shows "X" as attachment . Easiest way to reproduce is to setup security in Jenkins (current version) and press CTRL+F5 (full reload) in the web browser (before logging in).I've also found this stacktrace in the jenkins.err.log file which seems to be related to the images. Please see attachement for full stacktrace:2012-jul-03 08:17:13 winstone.Logger logInternalVARNING: Untrapped Error in Servletjava.lang.NullPointerException at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:50) 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
[JIRA] (JENKINS-14224) email-ext plugin blocks execution of the other publishers when recipienced box is empty
Alexey Gavrilov commented on JENKINS-14224 email-ext plugin blocks execution of the other publishers when recipienced box is empty Because, I need to inform recipients 1,2 in case of failure and recipients 1,2,3,4,5,6 in case of success. I rolled back email-ext to 2.20 temporary as a quick solution. 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
[JIRA] (JENKINS-14286) Promoted Build Plugin stacktraces on manual approve
Terry Sposato created JENKINS-14286 Promoted Build Plugin stacktraces on manual approve Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: promoted-builds Created: 03/Jul/12 3:00 AM Description: When I configure my username as a manual approval for a promoted build step for any job, I get the following error: http://pastie.org/4190777 If I click on Force promotion the job runs fine. Environment: apache-tomcat-7.0.26 Project: Jenkins Priority: Major Reporter: Terry Sposato 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
[JIRA] (JENKINS-14273) Matrix jobs don't get loaded
Richard Mortimer resolved JENKINS-14273 as Fixed Matrix jobs don't get loaded Marking as fixed in 1.475 Change By: Richard Mortimer (02/Jul/12 10:53 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
[JIRA] (JENKINS-14273) Matrix jobs don't get loaded
Richard Mortimer commented on JENKINS-14273 Matrix jobs don't get loaded I came across this earlier today on Ubuntu. Looking at the the source in MatrixProject.java:431 this was fixed earlier today and will be in 1.475 https://github.com/jenkinsci/jenkins/commit/a811f406e785a8c8e6cb4b9246829dce9c7b97ae I have verified the fix using a local snapshot build of Jenkins. 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
[JIRA] (JENKINS-14271) EnvInject claims global env vars are unresolved on slave
SCM/JIRA link daemon commented on JENKINS-14271 EnvInject claims global env vars are unresolved on slave Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/service/EnvInjectEnvVars.java http://jenkins-ci.org/commit/envinject-plugin/62ee63e51638c513f91439a0f0091a3435850eb0 Log: Fix JENKINS-14271 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
[JIRA] (JENKINS-13614) archiving artefacts from remote MacOS X slave fails
Xavier Nodet commented on JENKINS-13614 archiving artefacts from remote MacOS X slave fails I experience this exact same issue on two (slightly) different machines: Linux ??? 2.6.16.60-0.42.10-ppc64 #1 SMP Tue Apr 27 05:11:27 UTC 2010 ppc64 ppc64 ppc64 GNU/Linux with J2RE 1.5.0 IBM J9 2.3 Linux ppc64-64 j9vmxp6423ifx-20100125 (JIT enabled) J9VM - 20100122_52103_BHdSMr JIT - 20091016_1845ifx1_r8 GC - 20091026_AA Linux ??? 2.6.16.60-0.83.2-default #1 SMP Fri Sep 2 13:49:16 UTC 2011 s390x s390x s390x GNU/Linux with J2RE 1.5.0 IBM J9 2.3 Linux s390x-64 j9vmxz6423ifx-20100125 (JIT enabled) J9VM - 20100122_52103_BHdSMr JIT - 20091016_1845ifx1_r8 GC - 20091026_AA 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
[JIRA] (JENKINS-14273) Matrix jobs don't get loaded
Leo Davis commented on JENKINS-14273 Matrix jobs don't get loaded I'm also experiencing this on CentOS 5.8 with the same error messages. 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
[JIRA] (JENKINS-14284) Single backslashes are droped or used as escape char
SCM/JIRA link daemon commented on JENKINS-14284 Single backslashes are droped or used as escape char Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/service/PropertiesLoader.java http://jenkins-ci.org/commit/envinject-plugin/2be7887c9c5c8c01ad47070c4807a159a137ec97 Log: Fix JENKINS-14284 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
[JIRA] (JENKINS-13561) Compilation error building plugin using mvn install
Gregory Boissinot resolved JENKINS-13561 as Fixed Compilation error building plugin using mvn install Maybe an environment problem. Ok for me. Ok for the Jenkins reference instance https://buildhive.cloudbees.com/job/jenkinsci/job/postbuildscript-plugin/ Change By: Gregory Boissinot (02/Jul/12 7:44 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
[JIRA] (JENKINS-14284) Single backslashes are droped or used as escape char
Milos Svasek created JENKINS-14284 Single backslashes are droped or used as escape char Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 02/Jul/12 7:03 PM Description: Example: When setup "\\server\D\tmp" you got the "serverD mp" so the 1st backslash is dropped and the 2nd one is interpreted as escape char for tab (\t). When setup "\\server\\Dtmp" it is interpreted as is, so file were not found. So there is no way to setup the environment vaiable contains single backslash and it is serious problem, especialy on Windows platform. This problem is only for EnvInject verion 1.57 so the version 1.56 is not affected. Environment: EnvInject 1.57 (only) Jenkins 1.447.2 (LTS) MS Windows OS family. Project: Jenkins Priority: Blocker Reporter: Milos Svasek 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
[JIRA] (JENKINS-14283) Publish Over FTP - as Build Step
Kat Lim Ruiz created JENKINS-14283 Publish Over FTP - as Build Step Issue Type: New Feature Assignee: bap Components: publish-over-ftp Created: 02/Jul/12 6:29 PM Description: It should be a must that all Publish Over plugins can be setup as Build Steps (like Over SSH does). I have the case where I want to upload a zip file to an FTP server, and then trigger the deploy of that zip. I can't do it because the Over FTP can only be Post-build Step (and that is too late in my process). Project: Jenkins Labels: plugin publish Priority: Blocker Reporter: Kat Lim Ruiz 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
[JIRA] (JENKINS-13604) On startup, Error injecting constructor, java.lang.NoClassDefFoundError: hudson/ivy/AntIvyBuildWrapper
Walter Kacynski assigned JENKINS-13604 to yossis On startup, Error injecting constructor, java.lang.NoClassDefFoundError: hudson/ivy/AntIvyBuildWrapper Change By: Walter Kacynski (02/Jul/12 6:21 PM) Assignee: Timothy Bingaman yossis 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
[JIRA] (JENKINS-13604) On startup, Error injecting constructor, java.lang.NoClassDefFoundError: hudson/ivy/AntIvyBuildWrapper
Walter Kacynski updated JENKINS-13604 On startup, Error injecting constructor, java.lang.NoClassDefFoundError: hudson/ivy/AntIvyBuildWrapper I have this exact problem and disabling the artifactory plugin has corrected the problem. Change By: Walter Kacynski (02/Jul/12 6:20 PM) Component/s: artifactory 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
[JIRA] (JENKINS-13801) Allow label/node passthrough for job chaining
domi resolved JENKINS-13801 as Fixed Allow label/node passthrough for job chaining fixed with 1.2 Change By: domi (02/Jul/12 5:46 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
[JIRA] (JENKINS-13801) Allow label/node passthrough for job chaining
Dirk Kuypers commented on JENKINS-13801 Allow label/node passthrough for job chaining Yes, works like a charme. Thanks for the fix fix. 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
[JIRA] (JENKINS-13469) Prototype.Selector is undefined
domi resolved JENKINS-13469 as Cannot Reproduce Prototype.Selector is undefined closing as of no feedback... Change By: domi (02/Jul/12 5:43 PM) Status: Open Resolved Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-14026) git plugin doesn't support branch name contains slash ("/")
SCM/JIRA link daemon
commented on JENKINS-14026
git plugin doesn't support branch name contains slash ("/")
Code changed in jenkins
User: Nicolas De Loof
Path:
src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java
http://jenkins-ci.org/commit/git-plugin/3b1ad202004ec3617f2023e147868876bea2e305
Log:
[FIXED JENKINS-14026] always add remote to branch for rev-parse
also support multiple remotes
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
[JIRA] (JENKINS-14026) git plugin doesn't support branch name contains slash ("/")
SCM/JIRA link daemon
resolved JENKINS-14026 as Fixed
git plugin doesn't support branch name contains slash ("/")
Change By:
SCM/JIRA link daemon
(02/Jul/12 5:26 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
[JIRA] (JENKINS-13801) Allow label/node passthrough for job chaining
domi commented on JENKINS-13801 Allow label/node passthrough for job chaining is 1.2 working for you? 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
[JIRA] (JENKINS-13799) Job name sensitive
domi commented on JENKINS-13799 Job name sensitive is this still an issue? 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
[JIRA] (JENKINS-10931) NullPointerException in Perforce plugin when building if no view is entered in the configuration
William Roberts
commented on JENKINS-10931
NullPointerException in Perforce plugin when building if no view is entered in the configuration
I see this as well (Perforce plugin 1.3.15), but the stack trace is now
java.lang.NullPointerException
at hudson.plugins.perforce.PerforceSCM.parseProjectPath(PerforceSCM.java:2102)
at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1488)
at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1380)
at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:774)
at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:117)
It's doing split("\n") on a null string, so it would be easy to detect the problem.
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
[JIRA] (JENKINS-14281) Could not call hudson.plugins.warnings.WarningsPublisher.readResolve() : null
Timo Leinonen created JENKINS-14281 Could not call hudson.plugins.warnings.WarningsPublisher.readResolve() : null Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 02/Jul/12 4:29 PM Description: We are currently using version 4.5 of the warnings plugin. If we try to update to version 4.6 we get the following error during server start: 2012-07-02 18:05:20,442 ERROR [STDERR] Jul 2, 2012 6:05:20 PM jenkins.model.Jenkins$6 onTaskFailed SEVERE: Failed Loading job TPOE_201206_MW hudson.util.IOException2: Unable to read /jboss/hudson/jobs/TPOE_201206_MW/config.xml at hudson.XmlFile.read(XmlFile.java:134) at hudson.model.Items.load(Items.java:114) at jenkins.model.Jenkins$14.run(Jenkins.java:2273) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$5.runTask(Jenkins.java:797) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) 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:619) Caused by: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.plugins.warnings.WarningsPublisher.readResolve() : null : Could not call hudson.plugins.warnings.WarningsPublisher.readResolve() : null Debugging information message : Could not call hudson.plugins.warnings.WarningsPublisher.readResolve() : null cause-exception : com.thoughtworks.xstream.converters.reflection.ObjectAccessException cause-message : Could not call hudson.plugins.warnings.WarningsPublisher.readResolve() : null class : hudson.model.FreeStyleProject required-type : hudson.plugins.warnings.WarningsPublisher path: /project/publishers/hudson.plugins.warnings.WarningsPublisher line number : 158 --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:89) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:193) at hudson.util.DescribableList$ConverterImpl.unmarshal(DescribableList.java:244) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:290) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:233) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:180) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:137) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:33) at com.thoughtworks.xstream.XStream.un
[JIRA] (JENKINS-14273) Matrix jobs don't get loaded
erwan_q commented on JENKINS-14273 Matrix jobs don't get loaded I reproduce this critical issue with Jenkins ver. 1.473 version. Reverted to Jenkins ver. 1.472 solved the issue. Blocker bug 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
[JIRA] (JENKINS-14273) Matrix jobs don't get loaded
erwan_q updated JENKINS-14273 Matrix jobs don't get loaded Change By: erwan_q (02/Jul/12 4:30 PM) Priority: Critical Blocker 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
[JIRA] (JENKINS-14280) Add option to allow slaves to be restricted to jobs tied to their explicit node label only
teilo created JENKINS-14280 Add option to allow slaves to be restricted to jobs tied to their explicit node label only Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: core Created: 02/Jul/12 4:23 PM Description: Labels are used to restrict jobs to slaves, but also to assign tool installations to slaves. Unfortunatly sometimes these labels are orthoganal. For instance - our Linux JDK bundle would be used by all slaves that have the label "RH". Jobs that need a linux machine would be tied to the label "RH". All is well, but then we have a RH machine (call it machine X) that isn't the same rubber stamp template as the other redHat machines - and we don't want jobs tied to "RH" to be able to use that slave. Unfortunatly as I found out the slave option "Leave this machine for tied jobs only" treats any label as equal so the jobs that run on it are the ones that have the explicit slaveName labelAtom set as well as the ones that that the generic label set. The two possible workarounds are not nice. 1) update all jobs so that there requirements are (RH && ! slavename) 2) update all tool installations to add extra slave label and remove labels from slave. It would be better for a new "Usage" model to be defined alongside Node.mode.EXCLUSIVE and Node.mode.NORMAL to provide this requirement (say Node.mode.EXPLICIT) Project: Jenkins Priority: Major Reporter: teilo 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
[JIRA] (JENKINS-13957) Matrix builds disappear after Jenkins upgrade
Stephane Le Bris commented on JENKINS-13957 Matrix builds disappear after Jenkins upgrade My problem is related to JENKINS-14273 "Matrix jobs don't get loaded". 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
[JIRA] (JENKINS-13957) Matrix builds disappear after Jenkins upgrade
Stephane Le Bris commented on JENKINS-13957 Matrix builds disappear after Jenkins upgrade I have almost the same behaviour after an update from 1.464 version to 1.473 version: all Matrix jobs are no longer accessible. The Matrix jobs configurations files are present on the hard disks but Matrix Jobs are not accessible from the viewer. Jenkins is running on Windows 7 - 64 bits. 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
[JIRA] (JENKINS-14232) EnvInject/Parameterized trigger not handling properties file with logical lines
Mike Harris closed JENKINS-14232 as Fixed EnvInject/Parameterized trigger not handling properties file with logical lines I have verified version 1.57 fixes the issue for me. Thanks. Change By: Mike Harris (02/Jul/12 3:48 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14279) Report "missed items" rather that coverage percentage
Mickael Istria commented on JENKINS-14279 Report "missed items" rather that coverage percentage Original discussion: https://groups.google.com/forum/?fromgroups#!topic/jenkins-jacoco-plugin-mailing-list/016MPoIIr2c 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
[JIRA] (JENKINS-14279) Report "missed items" rather that coverage percentage
Mickael Istria created JENKINS-14279 Report "missed items" rather that coverage percentage Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco Created: 02/Jul/12 3:45 PM Description: Coverage percentage is often a meaningless metric. Instead, or in addition, Jacoco Jenkins plugin should be able to show missed items, as the Jacoco report task does by default. It makes it faster to know which piece of code is not covered and to find places where to focus effort. Project: Jenkins Priority: Major Reporter: Mickael Istria 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
[JIRA] (JENKINS-13916) Multiline text parameter displays as single line
Rafa de la Torre started work on JENKINS-13916 Multiline text parameter displays as single line Change By: Rafa de la Torre (02/Jul/12 2:38 PM) Status: Open In Progress 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
[JIRA] (JENKINS-13916) Multiline text parameter displays as single line
Rafa de la Torre updated JENKINS-13916 Multiline text parameter displays as single line Change By: Rafa de la Torre (02/Jul/12 2:38 PM) Issue Type: Improvement Bug 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
[JIRA] (JENKINS-13916) Multiline text parameter displays as single line
Rafa de la Torre assigned JENKINS-13916 to Rafa de la Torre Multiline text parameter displays as single line Change By: Rafa de la Torre (02/Jul/12 2:38 PM) Assignee: Rafa de la Torre 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
[JIRA] (JENKINS-14017) main-page can't show picture/icon before login
Andreas Sandberg updated JENKINS-14017 main-page can't show picture/icon before login Change By: Andreas Sandberg (02/Jul/12 2:11 PM) Affects Version/s: current 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
[JIRA] (JENKINS-14278) A parameterized buildstep in a matrix project causes IllegalArgumentException
rsandell created JENKINS-14278 A parameterized buildstep in a matrix project causes IllegalArgumentException Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 02/Jul/12 2:02 PM Description: Started by upstream project "Experimental_bobby_MatrixParameterized" build number 2 Building on master [nisse] $ /bin/sh -xe /srv/hudson/tomcat/latest/temp/hudson5741840414633660975.sh + echo another FATAL: Can't parse test2 java.lang.IllegalArgumentException: Can't parse test2 at hudson.matrix.Combination.fromString(Combination.java:218) at hudson.matrix.MatrixProject.getItem(MatrixProject.java:442) at hudson.matrix.MatrixProject.getItem(MatrixProject.java:91) at jenkins.model.Jenkins.getItem(Jenkins.java:2142) at jenkins.model.Jenkins.getItem(Jenkins.java:2163) at hudson.model.Items.fromNameList(Items.java:100) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.getProjectList(BuildTriggerConfig.java:132) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.perform2(BuildTriggerConfig.java:241) at hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.perform2(BlockableBuildTriggerConfig.java:56) at hudson.plugins.parameterizedtrigger.TriggerBuilder.perform(TriggerBuilder.java:96) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:697) 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:467) at hudson.model.Run.run(Run.java:1404) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Environment: Plugin version 2.15 Jenkins ver. 1.447.2 Project: Jenkins Priority: Critical Reporter: rsandell 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
[JIRA] (JENKINS-14277) Jenkins launches newly created jobs that were copied from other jobs
jieryn updated JENKINS-14277 Jenkins launches newly created jobs that were copied from other jobs Change By: jieryn (02/Jul/12 1:46 PM) Issue Type: Bug Improvement Component/s: core Component/s: job-poll-action 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
[JIRA] (JENKINS-14277) Jenkins launches newly created jobs that were copied from other jobs
jieryn assigned JENKINS-14277 to Unassigned Jenkins launches newly created jobs that were copied from other jobs Change By: jieryn (02/Jul/12 1:46 PM) Assignee: jieryn 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
[JIRA] (JENKINS-14277) Jenkins launches newly created jobs that were copied from other jobs
Powers Foss created JENKINS-14277 Jenkins launches newly created jobs that were copied from other jobs Issue Type: Bug Affects Versions: current Assignee: jieryn Components: job-poll-action Created: 02/Jul/12 1:17 PM Description: Every time we create a new Jenkins job that based off of an existing job using the "Copy from existing job" selection, Jenkins automatically runs the new job before we can go into the job and make any modifications. This leads to bogus job stats, puts build installers out onto our NAS, and creates extra cleanup steps that have to be done as a result. To effectively copy a job, now we have to disable the existing job first, then create the new job as a copy of that job, then go back into the existing job and re-enable it. A hassle... when you remember to do it. A real cleanup pain when you forget. Project: Jenkins Priority: Minor Reporter: Powers Foss 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
[JIRA] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Martin E
updated JENKINS-14276
Git SCM-polling doesn't work when using a parametrized branch-name
Change By:
Martin E
(02/Jul/12 1:10 PM)
Description:
Setup:- Git Plugin 1.1.20- a parameterized build with parameter "Branch", default "**"- Git SCM with branch specifier "$
\
{Branch
\
}"- SCM polling activatedIntended behaviour:- if _any_ branch changes, Jenkins
checkous
checks
out and builds this branch- when executed manually, the user enters the name of the branch to be builtActual behaviour:- no changes are detected (
brcause
because
the "$
\
{Branch
\
}" value isn't resolved when polling)
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
[JIRA] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Martin E updated JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name WOrkaround: disable branch filtering if the branch-specifier contains variables (see patchfile) Change By: Martin E (02/Jul/12 1:07 PM) Attachment: JENKINS-14276.patch 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
[JIRA] (JENKINS-14144) Build config history getting spammed
Darragh Bailey updated JENKINS-14144 Build config history getting spammed created a simple job that uses sleep. Seems you need to give the config history plugin long enough to both spot the change to the build.xml and be able to create a back of the change before the build job completes. Added xml from http://localhost:8080/pluginManager/api/xml?depth=1 as well as xml files for envinject, jobConfigHistory and system configuration. Versions Jenkins: 1.472 EnvInject: 1.56 JobConfigHistory: 1.13 Change By: Darragh Bailey (02/Jul/12 1:04 PM) Attachment: test-job.tar.gz Attachment: plugins.xml Attachment: config.xml Attachment: envInject.xml Attachment: jobConfigHistory.xml 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
[JIRA] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Martin E
created JENKINS-14276
Git SCM-polling doesn't work when using a parametrized branch-name
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git
Created:
02/Jul/12 1:02 PM
Description:
Setup:
Git Plugin 1.1.20
a parameterized build with parameter "Branch", default "**"
Git SCM with branch specifier "${Branch}"
- SCM polling activated
Intended behaviour:
- if any branch changes, Jenkins checkous out and builds this branch
- when executed manually, the user enters the name of the branch to be built
Actual behaviour:
- no changes are detected (brcause the "${Branch}" value isn't resolved when polling)
Project:
Jenkins
Priority:
Major
Reporter:
Martin E
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
[JIRA] (JENKINS-14275) Wrong folder permissions when downloading artifacts
Xav DELAS created JENKINS-14275 Wrong folder permissions when downloading artifacts Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 02/Jul/12 12:53 PM Description: While downloading the artifact using the link: 'all files in zip' the archive received has rw-rw-rw- permissions on folder while r-x is at least expected Without the execute permission, while unziping, you can't change directory (permissions denied) You need to change manually the permissions The jenkins version #1.404 was working fine Environment: ubunutu with jenkins 1.472 Project: Jenkins Priority: Major Reporter: Xav DELAS 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
[JIRA] (JENKINS-14022) job-exporter not working
regis gerard commented on JENKINS-14022 job-exporter not working nobody has an idea...thanks for you help 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
[JIRA] (JENKINS-14273) Matrix jobs don't get loaded
Patrick Cherry commented on JENKINS-14273 Matrix jobs don't get loaded Seen this also running under Debian squeeze, Jenkins v1.473. Downgrading back to 1.472 fixes. 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
[JIRA] (JENKINS-14103) Grails 2.0.4 not listed in installer doropdown
Jeroen Wesbeek
edited a comment on JENKINS-14103
Grails 2.0.4 not listed in installer doropdown
I am having the same issues as the reporter. In addition to Grails 2.0.4 not being in the json file, Grails 1.3.9 (the latest stable 1.x release) is also missing from the json file. I just locally tested the Grails backend crawler ( https://github.com/jenkinsci/backend-crawler/blob/master/grails.groovy ) which seems to work just fine and, apart from some warnings, properly outputs all available grails packages. I assume the backend crawler is not run at a timed interval to update the json file?
To get jenkins going with Grails 1.3.9 and 2.0.4 I already made some manual changes to the locally cached json file in ~/.jenkins/updates/com.g2one.hudson.grails.GrailsInstaller to add Grails 1.3.9 and Grails 2.0.4, and while I was indeed able to then configure Grails 1.3.9 and 2.0.4 in Jenkins, the file is constantly being overwritten with the incomplete online version.
I noticed a gist by Kiyotaka Oku ( https://gist.github.com/2711617 ) which contained the correct output of the backend crawler. Could you please make sure the online distributed json file is automatically kept up to date and always contains the latest available Grails packages?
Cheers, Jeroen
ps. the output of the grails.groovy script in the backend crawler:
jeroen@ripcurl /tmp $ ./grails.groovy
Jul 2, 2012 11:54:31 AM com.gargoylesoftware.htmlunit.html.HtmlPage loadJavaScriptFromUrl
WARNING: Expected content type of 'text/_javascript_' or 'application/x-_javascript_' for remotely loaded _javascript_ element at 'http://grails.org/static/olHYw9s4sRWKtAqM0Gycx7M0Zi61vStT4U3dxxe4zR.js', but got 'application/_javascript_'.
Jul 2, 2012 11:54:31 AM com.gargoylesoftware.htmlunit.html.HtmlPage loadJavaScriptFromUrl
WARNING: Expected content type of 'text/_javascript_' or 'application/x-_javascript_' for remotely loaded _javascript_ element at 'http://grails.org/static/SMqIhZQnW0hVcv1ddCsxzQAJ71v52rNDzHCwyhS4NHM.js', but got 'application/_javascript_'.
Jul 2, 2012 11:54:32 AM com.gargoylesoftware.htmlunit.html.HtmlPage loadJavaScriptFromUrl
WARNING: Expected content type of 'text/_javascript_' or 'application/x-_javascript_' for remotely loaded _javascript_ element at 'http://grails.org/static/zJHP5VyHm7tL27vEElZXfjJUO9IWNUqhzUqJ7jXFex1.js', but got 'application/_javascript_'.
Jul 2, 2012 11:54:32 AM com.gargoylesoftware.htmlunit.html.HtmlPage loadJavaScriptFromUrl
WARNING: Expected content type of 'text/_javascript_' or 'application/x-_javascript_' for remotely loaded _javascript_ element at 'http://grails.org/static/A9S42WFGksTUJWihLBxBNwwMHWyMp5ti18HnZqmgDmT.js', but got 'application/_javascript_'.
Jul 2, 2012 11:54:35 AM com.gargoylesoftware.htmlunit._javascript_.StrictErrorReporter runtimeError
SEVERE: runtimeError: message=[ActiveXObject Error: no value for ShockwaveFlash.ShockwaveFlash.7.] sourceName=[http://www.google-analytics.com/ga.js] line=[19] lineSource=[null] lineOffset=[0]
Jul 2, 2012 11:54:35 AM com.gargoylesoftware.htmlunit._javascript_.StrictErrorReporter runtimeError
SEVERE: runtimeError: message=[ActiveXObject Error: no value for ShockwaveFlash.ShockwaveFlash.6.] sourceName=[http://www.google-analytics.com/ga.js] line=[19] lineSource=[null] lineOffset=[0]
Jul 2, 2012 11:54:35 AM com.gargoylesoftware.htmlunit._javascript_.StrictErrorReporter runtimeError
SEVERE: runtimeError: message=[ActiveXObject Error: no value for ShockwaveFlash.ShockwaveFlash.] sourceName=[http://www.google-analytics.com/ga.js] line=[19] lineSource=[null] lineOffset=[0]
{"list": [
{
"id": "2.1.0.RC3",
"name": "Grails 2.1.0.RC3",
"url": "http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-2.1.0.RC3.zip"
},
{
"id": "2.0.4",
"name": "Grails 2.0.4",
"url": "http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-2.0.4.zip"
},
{
"id": "2.1.0.RC2",
"name": "Grails 2.1.0.RC2",
"url": "http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-2.1.0.RC2.zip"
},
{
"id": "1.3.9",
"name": "Grails 1.3.9",
"url": "http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-1.3.9.zip"
},
{
"id": "2.1.0.RC1",
"name": "Grails 2.1.0.RC1",
"url": "http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-2.1.0.RC1.zip"
},
{
"id": "2.0.3",
"name": "Grails 2.0.3",
"url": "http://dist.springframework.org.s3.amazonaws.
[JIRA] (JENKINS-14103) Grails 2.0.4 not listed in installer doropdown
Jeroen Wesbeek
edited a comment on JENKINS-14103
Grails 2.0.4 not listed in installer doropdown
I am having the same issues as the reporter. In addition to Grails 2.0.4 not being in the json file, Grails 1.3.9 (the latest stable 1.x release) is also missing from the json file. I just locally tested the Grails backend crawler ( https://github.com/jenkinsci/backend-crawler/blob/master/grails.groovy ) which seems to work just fine and, apart from some warnings, properly outputs all available grails packages. I assume the backend crawler is not run at a timed interval to update the json file?
To get jenkins going with Grails 1.3.9 and 2.0.4 I already made some manual changes to the locally cached json file in ~/.jenkins/updates/com.g2one.hudson.grails.GrailsInstaller to add Grails 1.3.9 and Grails 2.0.4, and while I was indeed able to then configure Grails 1.3.9 and 2.0.4 in Jenkins, the file is constantly being overwritten with the incomplete online version.
I noticed a gist by Kiyotaka Oku ( https://gist.github.com/2711617 ) which contained the correct output of the backend crawler. Could you please make sure the online distributed json file is automatically kept up to date and always contains the latest available Grails packages?
Cheers, Jeroen
jeroen@ripcurl /tmp $ ./grails.groovy
Jul 2, 2012 11:54:31 AM com.gargoylesoftware.htmlunit.html.HtmlPage loadJavaScriptFromUrl
WARNING: Expected content type of 'text/_javascript_' or 'application/x-_javascript_' for remotely loaded _javascript_ element at 'http://grails.org/static/olHYw9s4sRWKtAqM0Gycx7M0Zi61vStT4U3dxxe4zR.js', but got 'application/_javascript_'.
Jul 2, 2012 11:54:31 AM com.gargoylesoftware.htmlunit.html.HtmlPage loadJavaScriptFromUrl
WARNING: Expected content type of 'text/_javascript_' or 'application/x-_javascript_' for remotely loaded _javascript_ element at 'http://grails.org/static/SMqIhZQnW0hVcv1ddCsxzQAJ71v52rNDzHCwyhS4NHM.js', but got 'application/_javascript_'.
Jul 2, 2012 11:54:32 AM com.gargoylesoftware.htmlunit.html.HtmlPage loadJavaScriptFromUrl
WARNING: Expected content type of 'text/_javascript_' or 'application/x-_javascript_' for remotely loaded _javascript_ element at 'http://grails.org/static/zJHP5VyHm7tL27vEElZXfjJUO9IWNUqhzUqJ7jXFex1.js', but got 'application/_javascript_'.
Jul 2, 2012 11:54:32 AM com.gargoylesoftware.htmlunit.html.HtmlPage loadJavaScriptFromUrl
WARNING: Expected content type of 'text/_javascript_' or 'application/x-_javascript_' for remotely loaded _javascript_ element at 'http://grails.org/static/A9S42WFGksTUJWihLBxBNwwMHWyMp5ti18HnZqmgDmT.js', but got 'application/_javascript_'.
Jul 2, 2012 11:54:35 AM com.gargoylesoftware.htmlunit._javascript_.StrictErrorReporter runtimeError
SEVERE: runtimeError: message=[ActiveXObject Error: no value for ShockwaveFlash.ShockwaveFlash.7.] sourceName=[http://www.google-analytics.com/ga.js] line=[19] lineSource=[null] lineOffset=[0]
Jul 2, 2012 11:54:35 AM com.gargoylesoftware.htmlunit._javascript_.StrictErrorReporter runtimeError
SEVERE: runtimeError: message=[ActiveXObject Error: no value for ShockwaveFlash.ShockwaveFlash.6.] sourceName=[http://www.google-analytics.com/ga.js] line=[19] lineSource=[null] lineOffset=[0]
Jul 2, 2012 11:54:35 AM com.gargoylesoftware.htmlunit._javascript_.StrictErrorReporter runtimeError
SEVERE: runtimeError: message=[ActiveXObject Error: no value for ShockwaveFlash.ShockwaveFlash.] sourceName=[http://www.google-analytics.com/ga.js] line=[19] lineSource=[null] lineOffset=[0]
{"list": [
{
"id": "2.1.0.RC3",
"name": "Grails 2.1.0.RC3",
"url": "http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-2.1.0.RC3.zip"
},
{
"id": "2.0.4",
"name": "Grails 2.0.4",
"url": "http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-2.0.4.zip"
},
{
"id": "2.1.0.RC2",
"name": "Grails 2.1.0.RC2",
"url": "http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-2.1.0.RC2.zip"
},
{
"id": "1.3.9",
"name": "Grails 1.3.9",
"url": "http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-1.3.9.zip"
},
{
"id": "2.1.0.RC1",
"name": "Grails 2.1.0.RC1",
"url": "http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-2.1.0.RC1.zip"
},
{
"id": "2.0.3",
"name": "Grails 2.0.3",
"url": "http://dist.springframework.org.s3.amazonaws.com/release/GRAILS/grails-2.0.3.zip"
},
{
"id": "2.0.2",
[JIRA] (JENKINS-14103) Grails 2.0.4 not listed in installer doropdown
Jeroen Wesbeek
edited a comment on JENKINS-14103
Grails 2.0.4 not listed in installer doropdown
I am having the same issues as the reporter. In addition to Grails 2.0.4 not being in the json file, Grails 1.3.9 (the latest stable 1.x release) is also missing from the json file. I just locally tested the Grails backend crawler ( https://github.com/jenkinsci/backend-crawler/blob/master/grails.groovy ) which seems to work just fine and, apart from some warnings, properly outputs all available grails packages. I assume the backend crawler is not run at a timed interval to update the json file?
To get jenkins going with Grails 1.3.9 and 2.0.4 I already made some manual changes to the locally cached json file in ~/.jenkins/updates/com.g2one.hudson.grails.GrailsInstaller to add Grails 1.3.9 and Grails 2.0.4, and while I was indeed able to then configure Grails 1.3.9 and 2.0.4 in Jenkins, the file is constantly being overwritten with the incomplete online version.
I noticed a gist by Kiyotaka Oku ( https://gist.github.com/2711617 ) which contained the correct output of the backend crawler. Could you please make sure the online distributed json file is automatically kept up to date and always contains the latest available Grails packages?
Cheers, Jeroen
jeroen@ripcurl /tmp $ ./grails.groovy
Jul 2, 2012 11:54:31 AM com.gargoylesoftware.htmlunit.html.HtmlPage loadJavaScriptFromUrl
WARNING: Expected content type of 'text/_javascript_' or 'application/x-_javascript_' for remotely loaded _javascript_ element at 'http://grails.org/static/olHYw9s4sRWKtAqM0Gycx7M0Zi61vStT4U3dxxe4zR.js', but got 'application/_javascript_'.
Jul 2, 2012 11:54:31 AM com.gargoylesoftware.htmlunit.html.HtmlPage loadJavaScriptFromUrl
WARNING: Expected content type of 'text/_javascript_' or 'application/x-_javascript_' for remotely loaded _javascript_ element at 'http://grails.org/static/SMqIhZQnW0hVcv1ddCsxzQAJ71v52rNDzHCwyhS4NHM.js', but got 'application/_javascript_'.
Jul 2, 2012 11:54:32 AM com.gargoylesoftware.htmlunit.html.HtmlPage loadJavaScriptFromUrl
WARNING: Expected content type of 'text/_javascript_' or 'application/x-_javascript_' for remotely loaded _javascript_ element at 'http://grails.org/static/zJHP5VyHm7tL27vEElZXfjJUO9IWNUqhzUqJ7jXFex1.js', but got 'application/_javascript_'.
Jul 2, 2012 11:54:32 AM com.gargoylesoftware.htmlunit.html.HtmlPage loadJavaScriptFromUrl
WARNING: Expected content type of 'text/_javascript_' or 'application/x-_javascript_' for remotely loaded _javascript_ element at 'http://grails.org/static/A9S42WFGksTUJWihLBxBNwwMHWyMp5ti18HnZqmgDmT.js', but got 'application/_javascript_'.
Jul 2, 2012 11:54:35 AM com.gargoylesoftware.htmlunit._javascript_.StrictErrorReporter runtimeError
SEVERE: runtimeError: message=[ActiveXObject Error: no value for ShockwaveFlash.ShockwaveFlash.7.] sourceName=http://www.google-analytics.com/ga.js line=[19] lineSource=[null] lineOffset=[0]
Jul 2, 2012 11:54:35 AM com.gargoylesoftware.htmlunit._javascript_.StrictErrorReporter runtimeError
SEVERE: runtimeError: message=[ActiveXObject Error: no value for ShockwaveFlash.ShockwaveFlash.6.] sourceName=http://www.google-analytics.com/ga.js line=[19] lineSource=[null] lineOffset=[0]
Jul 2, 2012 11:54:35 AM com.gargoylesoftware.htmlunit._javascript_.StrictErrorReporter runtimeError
SEVERE: runtimeError: message=[ActiveXObject Error: no value for ShockwaveFlash.ShockwaveFlash.] sourceName=http://www.google-analytics.com/ga.js line=[19] lineSource=[null] lineOffset=[0]
{"list": [
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
"id"} ,
Unknown macro: {
[JIRA] (JENKINS-14103) Grails 2.0.4 not listed in installer doropdown
Jeroen Wesbeek edited a comment on JENKINS-14103 Grails 2.0.4 not listed in installer doropdown I am having the same issues as the reporter. In addition to Grails 2.0.4 not being in the json file, Grails 1.3.9 (the latest stable 1.x release) is also missing from the json file. I just locally tested the Grails backend crawler ( https://github.com/jenkinsci/backend-crawler/blob/master/grails.groovy ) which seems to work just fine and, apart from some warnings, properly outputs all available grails packages. I assume the backend crawler is not run at a timed interval to update the json file? To get jenkins going with Grails 1.3.9 and 2.0.4 I already made some manual changes to the locally cached json file in ~/.jenkins/updates/com.g2one.hudson.grails.GrailsInstaller to add Grails 1.3.9 and Grails 2.0.4, and while I was indeed able to then configure Grails 1.3.9 and 2.0.4 in Jenkins, the file is constantly being overwritten with the incomplete online version. I noticed a gist by Kiyotaka Oku ( https://gist.github.com/2711617 ) which contained the correct output of the backend crawler. Could you please make sure the online distributed json file is automatically kept up to date and always contains the latest available Grails packages? Cheers, Jeroen 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
[JIRA] (JENKINS-14273) Matrix jobs don't get loaded
John Dickinson commented on JENKINS-14273 Matrix jobs don't get loaded We are also seeing this issue with identical error messages. 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
[JIRA] (JENKINS-14103) Grails 2.0.4 not listed in installer doropdown
Jeroen Wesbeek edited a comment on JENKINS-14103 Grails 2.0.4 not listed in installer doropdown I am having the same issues as the reporter. In addition to Grails 2.0.4 not being in the json file, Grails 1.3.9 (the latest stable 1.x release) is also missing from the json file. I just locally tested the backend crawler ( https://github.com/jenkinsci/backend-crawler/blob/master/grails.groovy ) which seems to work just fine and apart from some warnings properly outputs all available grails packages. I assume the backend crawler is not run at a timed interval to update the json file? To get jenkins going with Grails 1.3.9 and 2.0.4 I already made some manual changes to the locally cached json file in ~/.jenkins/updates/com.g2one.hudson.grails.GrailsInstaller to add Grails 1.3.9 and Grails 2.0.4, and while I was indeed able to then configure Grails 1.3.9 and 2.0.4 in Jenkins, the file is constantly being overwritten with the incomplete online version. I noticed a gist by Kiyotaka Oku ( https://gist.github.com/2711617 ) which contained the correct output of the backend crawler. Could you please make sure the online distributed json file is automatically kept up to date and always contains the latest available Grails packages? Cheers, Jeroen 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
[JIRA] (JENKINS-14103) Grails 2.0.4 not listed in installer doropdown
Jeroen Wesbeek edited a comment on JENKINS-14103 Grails 2.0.4 not listed in installer doropdown I am having the same issues as the reporter. In addition to Grails 2.0.4 not being in the json file, Grails 1.3.9 (the latest stable 1.x release) is also missing from the json file. I just locally tested the backend crawler ( https://github.com/jenkinsci/backend-crawler/blob/master/grails.groovy ) which seems to work just fine and, apart from some warnings, properly outputs all available grails packages. I assume the backend crawler is not run at a timed interval to update the json file? To get jenkins going with Grails 1.3.9 and 2.0.4 I already made some manual changes to the locally cached json file in ~/.jenkins/updates/com.g2one.hudson.grails.GrailsInstaller to add Grails 1.3.9 and Grails 2.0.4, and while I was indeed able to then configure Grails 1.3.9 and 2.0.4 in Jenkins, the file is constantly being overwritten with the incomplete online version. I noticed a gist by Kiyotaka Oku ( https://gist.github.com/2711617 ) which contained the correct output of the backend crawler. Could you please make sure the online distributed json file is automatically kept up to date and always contains the latest available Grails packages? Cheers, Jeroen 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
[JIRA] (JENKINS-14103) Grails 2.0.4 not listed in installer doropdown
Jeroen Wesbeek edited a comment on JENKINS-14103 Grails 2.0.4 not listed in installer doropdown I am having the same issues as the reporter. In addition to Grails 2.0.4 not being in the json file, Grails 1.3.9 (the latest stable 1.x release) is also missing from the json file. I just tested the backend crawler ( https://github.com/jenkinsci/backend-crawler/blob/master/grails.groovy ) which seems to work just fine. I assume the backend crawler is not run at a timed interval to update the json file? Could you please make sure the json is up to date? I already made some manual changes to the locally cached json file in ~/.jenkins/updates/com.g2one.hudson.grails.GrailsInstaller to add Grails 1.3.9 and Grails 2.0.4, and while I was indeed able to then configure Grails 1.3.9 and 2.0.4 in Jenkins, the file is constantly being overwritten with the incomplete online version. I noticed a gist by Kiyotaka Oku https://gist.github.com/2711617 which indeed properly contained all currently available Grails packages (which is the same output as running the backend crawler locally). Could you make sure the online distributed json file is automatically kept up to date? Cheers, Jeroen 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
[JIRA] (JENKINS-14103) Grails 2.0.4 not listed in installer doropdown
Jeroen Wesbeek commented on JENKINS-14103 Grails 2.0.4 not listed in installer doropdown I am having the same issues as the reporter. In addition to Grails 2.0.4 not being in the json file, Grails 1.3.9 (the latest stable 1.x release) is also missing from the XML file. I just tested the backend crawler ( https://github.com/jenkinsci/backend-crawler/blob/master/grails.groovy ) which seems to work just fine. I assume the backend crawler is not run at a timed interval to update the json file? Could you please make sure the json is up to date? I already made some manual changes to the locally cached json file in ~/.jenkins/updates/com.g2one.hudson.grails.GrailsInstaller to add Grails 1.3.9 and Grails 2.0.4, and while I was indeed able to then configure Grails 1.3.9 and 2.0.4 in Jenkins, the file is constantly being overwritten with the incomplete online version. I noticed a gist by Kiyotaka Oku https://gist.github.com/2711617 which indeed properly contained all currently available Grails packages (which is the same output as running the backend crawler locally). Could you make sure the online distributed json file is automatically kept up to date? Cheers, Jeroen 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
[JIRA] (JENKINS-14273) Matrix jobs don't get loaded
Christoph Jaehnigen created JENKINS-14273 Matrix jobs don't get loaded Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: matrix Created: 02/Jul/12 9:39 AM Description: No matrix jobs get loaded with Jenkins 1.473. The jobs and any related information is missing. The log shows the following backtrace: Jul 2, 2012 11:14:34 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job Test matrix java.lang.NullPointerException at hudson.matrix.MatrixProject.updateTransientActions(MatrixProject.java:431) at hudson.model.AbstractProject.onLoad(AbstractProject.java:296) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:466) at hudson.model.Items.load(Items.java:115) at jenkins.model.Jenkins$17.run(Jenkins.java:2492) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:878) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Environment: CentOS 6.2 Project: Jenkins Priority: Critical Reporter: Christoph Jaehnigen 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
[JIRA] (JENKINS-14272) allow defining custom path to gradlew (gradle wrapper) scipt
wujek srujek created JENKINS-14272 allow defining custom path to gradlew (gradle wrapper) scipt Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: gradle Created: 02/Jul/12 9:01 AM Description: The gradle Wrapper task creates the gradle wrapper scripts, but it does so in the project root, which sometimes is not wanted. One can override it, so that the scripts are found in, say, a 'contrib' folder, along with other helper scripts. Jenkins Gradle plugin has the option to use the wrapper, but it blindly tries to invoke gradlew from the project root - it is unaware of custom settings. Please let users define a custom path to the gradlew script within the project, or, ideally, read if somehow from the build.gradle file (it might be difficult, I aggree). Having users specify it explicitly is good enough, IMHO. Environment: all Project: Jenkins Priority: Major Reporter: wujek srujek 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
[JIRA] (JENKINS-14248) DiskUsage dont show values.
Tomek Kaczanowski commented on JENKINS-14248 DiskUsage dont show values. I have exactly the same problem. Disk Usage ver. 0.17, Jenkins 1.458 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
[JIRA] (JENKINS-14135) NPE
Carsten Otto commented on JENKINS-14135 NPE Yes, now it works. 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
[JIRA] (JENKINS-13928) bad version number at offiset=6
Christian Wolfgang commented on JENKINS-13928 bad version number at offiset=6 Sorry for the delay. Could you please try to make a fresh jenkins home and install the plugin again? set JENKINS_HOME=c:\somewhere 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
