[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
sanga
commented on JENKINS-13915
NPE Exception, possibly caused by disabled jobs?
I stumbled into this bug as well, with a much simpler job config, namely:
build( "do1" )
build( "do2" )
parallel (
{ build("do1") },
{ build("do2") },
)
the stack is the same, but for completeness sake:
Started by user anonymous
Building on master in workspace /var/lib/jenkins/jobs/tims-flow/workspace
Trigger job do1
do1 #4 completed
Trigger job do2
do2 #4 completed
parallel {
Trigger job do1
Trigger job do2
do1 #5 completed
do2 #5 completed
FATAL: null
java.lang.NullPointerException
at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.acceptGetProperty(GetEffectivePojoPropertySite.java:51)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:227)
at com.cloudbees.plugins.flow.FlowDelegate$_parallel_closure3.doCall(FlowDSL.groovy:216)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
at groovy.lang.Closure.call(Closure.java:412)
at groovy.lang.Closure.call(Closure.java:425)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1377)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1349)
at org.codehaus.groovy.runtime.dgm$149.invoke(Unknown Source)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at com.cloudbees.plugins.flow.FlowDelegate.parallel(FlowDSL.groovy:215)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:361)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:66)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:145)
at Script1$_run_closure1.doCall(Script1.groovy:3)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:66)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141)
at Script1$_run_closure1.doCall(Script1.groovy)
at
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
sanga commented on JENKINS-13915 NPE Exception, possibly caused by disabled jobs? Actually, have you tried updating Jenkins? As I just did that and I can't reproduce this anymore. And (though I don't precisely recall) the version was similar to yours, 1.467 I think, and now with 1.476, I don't have 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-3009) Encoding problems since ver 1.282
dotsev reopened JENKINS-3009 Encoding problems since ver 1.282 Like cforce101 said, the "Umlauts" are not correct, when using the zip-function. Any idea? Change By: dotsev (08/Aug/12 6:58 AM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14725) Build promotion leads to Upstream Subversion URL is not specified
Torsten Beuck created JENKINS-14725 Build promotion leads to Upstream Subversion URL is not specified Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: svnmerge Created: 08/Aug/12 7:24 AM Description: we are using the svn merge plugin and the promoted builds plugin. The promotion is configured to "Promote builds..." "only when manually approved" and "Integrate to upstream upon succesful build" is configured as action. If we now approve the promotion manually, the following error appears: Legacy code started this job. No cause information is available Building in workspace /var/opt/int/hudson/server/hudsontest02/data/jobs/buildtest-feat001/workspace Promoting buildtest-feat001 #10 Upstream Subversion URL is not specified. Configuration problem? failed build jenkins.plugins.svnmerge.IntegrationPublisher@4cb3b97f SUCCESS Finished: FAILURE "This project builds a Subversion feature branch" is checked and the upstream project name is set. Environment: promoted builds plugin 2.6.2 svn merge plugin 1.0 jenkins 1.4.7.4 Project: Jenkins Priority: Major Reporter: Torsten Beuck 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-14057) With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails
schtefan updated JENKINS-14057 With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails Change By: schtefan (08/Aug/12 8:19 AM) Summary: With ActiveDirectoryPlugin doesntworkanymore( ,the user/group identification validation inauthorizationstrategy ofconfigurationscreen fails ) 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-13774) Provide option for cloning all branches with Mercurial SCM
Henrik Skupin commented on JENKINS-13774 Provide option for cloning all branches with Mercurial SCM jglick, Dave and myself are working on the same project. So I have just added more details to our problem. As I have mentioned we can't have multiple subdirectories (checkouts) of the repository because the build process has to be able to do a hotswap between branches. That means all named branches of the local clone have to be up-to-date. 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-14321) Git plugin's 'Fast remote polling' uses slave environment, not master environment.
SCM/JIRA link daemon resolved JENKINS-14321 as Fixed Git plugins Fast remote polling uses slave environment, not master environment. Change By: SCM/JIRA link daemon (08/Aug/12 8:52 AM) 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-14321) Git plugin's 'Fast remote polling' uses slave environment, not master environment.
SCM/JIRA link daemon commented on JENKINS-14321 Git plugins Fast remote polling uses slave environment, not master environment. Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/GitSCM.java src/main/java/hudson/plugins/git/util/GitUtils.java http://jenkins-ci.org/commit/git-plugin/3d9a73d26b129249c51fccfca6060280197b25eb Log: FIXED JENKINS-14321 don't reuse last build environment for fast polling Compare: https://github.com/jenkinsci/git-plugin/compare/ef3349e6c254...3d9a73d26b12 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-14712) Bulk Builder plugin doesn't show views created within a nested view
Simon Westcott commented on JENKINS-14712 Bulk Builder plugin doesnt show views created within a nested view Hi Tillu, I'm not familiar with nested views. Are these native to Jenkins or are you using the Nested View plugin @ https://wiki.jenkins-ci.org/display/JENKINS/Nested+View+Plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14726) Jenkins integration with Subversion....
Maheshkumar kalasenavaru created JENKINS-14726 Jenkins integration with Subversion Issue Type: Task Affects Versions: current Assignee: k2nakamura Components: svn-release-mgr, svn-tag Created: 08/Aug/12 8:54 AM Description: Hi Team, Currently we are trying to set up a CI system with the below tools in place. 1. Subversion. 2. Jenkins CI server. 3. Maven build tool. I am able to configure a job to auto-build deploy whenever the developer checks-in the latest code into the subversion trunk. The requirement is to carry out the auto triggering of the builds from Jenkins based on the Subversion tags for each artifact in the repository. How do I go about it guyss please let me know. Any help would be appreciated very much. Please let me know if any further information needed. Thanks in advance, Mahesh Due Date: 18/Aug/12 12:00 AM Environment: OS - Microsoft Windows XP 2002 SP3 Platform : Subversion - LINUX, Jenkins - Windows Fix Versions: current Project: Jenkins Priority: Major Reporter: Maheshkumar kalasenavaru 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-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding updated JENKINS-13915 NPE Exception, possibly caused by disabled jobs? Change By: Ben Golding (08/Aug/12 8:59 AM) Environment: Jenkins1. 465 476 BuildFlow0. 3 4 RedHatEnterpriseLinux5.564bitSunJava1.6.0_20 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-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding commented on JENKINS-13915 NPE Exception, possibly caused by disabled jobs? I am using the latest available at time of writing: Jenkins 1.476, Build Flow 0.4 The bug persists... 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-13844) Emulate clean checkout by... does not work with 1.7 subversion repositories
Martin Adam commented on JENKINS-13844 Emulate clean checkout by... does not work with 1.7 subversion repositories same here, environmen same as in comment above me, only I have jenkins 1.475 and it's a master building node 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-7235) set log level for file hudson.err.log
Ilya Lebedev
commented on JENKINS-7235
set log level for file hudson.err.log
Is it possible to set some default log level for GLOBAL LOGGER as
Logger.getLogger("")..getHandlers()..setLevel(Level.WARN);
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-7235) set log level for file hudson.err.log
Ilya Lebedev
edited a comment on JENKINS-7235
set log level for file hudson.err.log
Is it possible to set some default log level for GLOBAL LOGGER as
Logger.getLogger("").getHandlers().setLevel(Level.WARNING);
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-7235) set log level for file hudson.err.log
Ilya Lebedev
edited a comment on JENKINS-7235
set log level for file hudson.err.log
Is it possible to set some default log level for GLOBAL LOGGER as
Logger.getLogger("").getHandlers().setLevel(Level.WARN);
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-14727) Make dependency to bundled maven-plugin optional
Ben Golding created JENKINS-14727 Make dependency to bundled maven-plugin optional Issue Type: Improvement Assignee: Ulli Hafner Components: warnings Created: 08/Aug/12 10:40 AM Description: Make dependency from warnings to (bundled) maven-plugin optional. The maven-plugin also brings an indirect dependency to javadoc We don't use Maven or Java in our Jenkins. All other bundled plugins were removed from jenkins.war (purpose: keep '/pluginManager/installed' UI list shorter, save some disk space) Environment: Jenkins 1.476 Build Flow 0.4 Red Hat Enterprise Linux 5.5 64 bit Sun Java 1.6.0_20 Project: Jenkins Priority: Trivial Reporter: Ben Golding 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-11025) Allow the build to fail on low coverage
Ravi Teja Lokineni commented on JENKINS-11025 Allow the build to fail on low coverage @Podar can you ask this on the jenkins mailing list probably someone might respond 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-14727) Make dependency to bundled maven-plugin optional
Ben Golding updated JENKINS-14727 Make dependency to bundled maven-plugin optional Change By: Ben Golding (08/Aug/12 11:02 AM) Environment: Jenkins1.476 BuildFlow0. Warnings 4 .13 RedHatEnterpriseLinux5.564bitSunJava1.6.0_20 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-14619) Matrix problem with Parameterized Build
morlajb commented on JENKINS-14619 Matrix problem with Parameterized Build Hi , Thanks for your reply , I wasn't in the office in the last days. you are right this is exactly the configuration I used. 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-14619) Matrix problem with Parameterized Build
morlajb edited a comment on JENKINS-14619 Matrix problem with Parameterized Build Hi , Thanks for your reply , I wasn't in the office in the last days. you are right this is exactly the configuration I used. here is the log of the matrix job : 15:10:37 U management\flow-triggering\oo-flow-triggering-api\pom.xml 15:11:13 At revision 10313 and all the activate jobs shows the following : 15:12:01 U management\l10n\oo-l10n-ja\src\main\resources\deployment_ja.properties 15:14:01 At revision 10317 I was trying to add the config file and couldn't find the way ... 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-14619) Matrix problem with Parameterized Build
morlajb updated JENKINS-14619 Matrix problem with Parameterized Build Change By: morlajb (08/Aug/12 11:30 AM) Attachment: config.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-14619) Matrix problem with Parameterized Build
morlajb edited a comment on JENKINS-14619 Matrix problem with Parameterized Build here is the config.xml contains the problem. do you need any more info for this 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-14619) Matrix problem with Parameterized Build
morlajb updated JENKINS-14619 Matrix problem with Parameterized Build here is the config.xml contains the problem. Change By: morlajb (08/Aug/12 11:29 AM) Attachment: config.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-14619) Matrix problem with Parameterized Build
morlajb edited a comment on JENKINS-14619 Matrix problem with Parameterized Build Hi , Thanks for your reply , I wasn't in the office in the last days. you are right this is exactly the configuration I used. here is the log of the matrix job : 15:10:37 U management\flow-triggering\oo-flow-triggering-api\pom.xml 15:11:13 At revision 10313 and all the activate jobs shows the following : 15:12:01 U management\l10n\oo-l10n-ja\src\main\resources\deployment_ja.properties 15:14:01 At revision 10317 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-14314) MultiJob Build Type in view
hagzag resolved JENKINS-14314 as Fixed MultiJob Build Type in view Fixed in jobtype-column-plugin https://github.com/jenkinsci/jobtype-column-plugin/pull/1 Change By: hagzag (08/Aug/12 12:17 PM) Status: Open Resolved Fix Version/s: current 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-14728) Buil-flow jobs fail to load the job history if the envinject plugin is installed
Andrei Ababei created JENKINS-14728 Buil-flow jobs fail to load the job history if the envinject plugin is installed Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: jenkins.err.log Components: build-flow, envinject Created: 08/Aug/12 12:48 PM Description: Steps to reproduce : 1.Install build-flow and envinject 2.Create a build-flow job 3.Successfully run the build-flow job 4.Restart jenkins The following occurs: No builds will be displayed in the history. Relevant jenkins log entry is attached. 08.08.2012 12:33:25 hudson.model.RunMap load WARNING: could not load E:\Jenkins\jobs\test111\builds\2012-07-31_17-20-02 hudson.util.IOException2: Unable to read E:\Jenkins\jobs\test111\builds\2012-07-31_17-20-02\build.xml at hudson.XmlFile.unmarshal(XmlFile.java:164) at hudson.model.Run.reload(Run.java:290) at hudson.model.Run.init(Run.java:279) Caused by: com.thoughtworks.xstream.converters.ConversionException: Could not call org.jenkinsci.plugins.envinject.EnvInjectPluginAction.readResolve() : null : Could not call org.jenkinsci.plugins.envinject.EnvInjectPluginAction.readResolve() : null Debugging information message : Could not call org.jenkinsci.plugins.envinject.EnvInjectPluginAction.readResolve() : null cause-exception : com.thoughtworks.xstream.converters.reflection.ObjectAccessException cause-message : Could not call org.jenkinsci.plugins.envinject.EnvInjectPluginAction.readResolve() : null class : com.cloudbees.plugins.flow.FlowRun required-type : org.jenkinsci.plugins.envinject.EnvInjectPluginAction path: /com.cloudbees.plugins.flow.FlowRun/builds/edgeMap/entry/org.jgrapht.graph.IntrusiveEdge/target/actions/org.jenkinsci.plugins.envinject.EnvInjectPluginAction line number : 59 --- Note: Manually deleting all lines containing "envinject" from Jenkins\jobs\test111\builds\2012-07-31_17-20-02\build.xml allows for the build to properly be loaded and displayed in the build history. Environment: Jenkins : 1.476 envinject : 1.65 build-flow : 0.4 Project: Jenkins Labels: plugin Priority: Minor Reporter: Andrei Ababei 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-14729) Allow project to configure categories on an ad-hoc basis
Jacob Robertson created JENKINS-14729 Allow project to configure categories on an ad-hoc basis Issue Type: Improvement Affects Versions: current Assignee: abayer Components: matrix, throttle-concurrents Created: 08/Aug/12 12:55 PM Description: I've written an integration test for different OS's and different databases. Now I've created a matrix job with two axis (slaves "database"). The slaves have multiple executors, being able to run the integration tests in parallel. But for each database there exists only one account, therefor when running the build, axis combinations using the same database must not be running in parallel. How about a (throttle-) flag in the axis definition to mark this axis not to be used in parallel? As a workaround I'm using the "Run each configuration sequentially", but it's unnecessary slow's down the build. Environment: Linux x64 Fix Versions: current Project: Jenkins Priority: Minor Reporter: Jacob Robertson 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-14728) Buil-flow jobs fail to load the job history if the envinject plugin is installed
Andrei Ababei updated JENKINS-14728 Buil-flow jobs fail to load the job history if the envinject plugin is installed Attached "build-original.xml" the load error and "build-edited.xml" edited to remove the envinject stuff Change By: Andrei Ababei (08/Aug/12 12:59 PM) Attachment: build-original.xml Attachment: build-edited.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-6094) Allow cobertura coverage report generation for failed builds
Podar Wang stopped work on JENKINS-6094 Allow cobertura coverage report generation for failed builds Change By: Podar Wang (08/Aug/12 2:55 PM) Status: InProgress Open 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-14712) Bulk Builder plugin doesn't show views created within a nested view
tillu sri commented on JENKINS-14712 Bulk Builder plugin doesnt show views created within a nested view I am using the nested view plugin, the one mentioned in the url. 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-14712) Bulk Builder plugin doesn't show views created within a nested view
Simon Westcott updated JENKINS-14712 Bulk Builder plugin doesnt show views created within a nested view Ah, I see. Updating the type to new feature as integration with other plugins was not previously planned. Change By: Simon Westcott (08/Aug/12 3:41 PM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14712) Bulk Builder plugin doesn't show views created within a nested view
Simon Westcott commented on JENKINS-14712 Bulk Builder plugin doesnt show views created within a nested view Note to self: https://wiki.jenkins-ci.org/display/JENKINS/Dependencies+among+plugins 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-14712) Bulk Builder plugin doesn't show views created within a nested view
tillu sri commented on JENKINS-14712 Bulk Builder plugin doesnt show views created within a nested view But that makes the bulk builder paralyzed when an organization uses hundreds of applications organized in multiple nested views. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14733) How to deploy multiple builds with hudson in SVN using single user
Vinodh J created JENKINS-14733 How to deploy multiple builds with hudson in SVN using single user Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: locks-and-latches, subversion Created: 08/Aug/12 4:39 PM Description: Hi, We have linux server with Subversion. We would like to have a deployment tool like hudson. I have some doubt in the configuration, i.e a) we will use a windows box with hudson setup b) Will install tortoise svn in that box, with SVN username and pwd c) Then we will configure hudson and point the linux SVN server, for the build process. d) My doubt is, We will specify a project in hudson for build process, is that possible for multiple hudson users to build at a time. Since tortoise svn is configured with one SVN user. Will the SVN lock issue occur for hudson users. Please advise, im new to this. Any help will be much appreciated.. thx jv Environment: Staging Project: Jenkins Priority: Major Reporter: Vinodh J 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-14733) How to deploy multiple builds with hudson in SVN using single user
Vinodh J updated JENKINS-14733 How to deploy multiple builds with hudson in SVN using single user Change By: Vinodh J (08/Aug/12 4:41 PM) Description: Hi,WehavelinuxserverwithSubversion.Wewouldliketohaveadeploymenttoollikehudson.Ihavesomedoubtintheconfiguration,i.ea)wewilluseawindowsboxwithhudsonsetupb)Willinstalltortoisesvninthatbox,withSVNusernameandpwdc)ThenwewillconfigurehudsonandpointthelinuxSVNserver,forthebuildprocess.d)Mydoubtis,Wewillspecifyaprojectinhudsonforbuildprocess,isthatpossibleformultiplehudsonuserstobuildatatime.SincetortoisesvnisconfiguredwithoneSVNuser.WilltheSVNlockissueoccurforhudsonusers. Becausesayforeg.2hudsonuserswilltryingtobuild,theprojectisbasedon2differentdir,since2dircantbeupdatedatatime,whatiflockissuearises.isthereanypluginorsolution,pleasehelpme.. Pleaseadvise,imnewtothis.Anyhelpwillbemuchappreciated..thxjv 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-8744) Maven cannot run with JDK1.5 anymore
Kohsuke Kawaguchi resolved JENKINS-8744 as Duplicate Maven cannot run with JDK1.5 anymore I'm marking this as fixed as a duplicate of JENKINS-13659. My earlier fix to remoting would provide critical information needed to fix recurrence of similar bugs. If people continue to see this problem, please upgrade to 1.463 or later and then report the stack trace, which will contain the offending class name. Change By: Kohsuke Kawaguchi (08/Aug/12 4:51 PM) Status: Open Resolved Assignee: KohsukeKawaguchi Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14720) Fast remote polling setting does not save when selected in job config
owenmehegan commented on JENKINS-14720 Fast remote polling setting does not save when selected in job config I get it now. So the help says: "If you want to use this, you can have only one repository with one branch (no wildcards!), and you can not use any excluded regions, excluded users or submodules, otherwise this option will disable itself after save." I would say this behavior is a little bit unexpected. If you don't read the help (which admittedly you should!), it's confusing to set the option and then have it unset silently. It seems like a visual cue/warning would be preferable. I'll leave this open with that as the bug/feature request. 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-14720) Warning should display if fast remote polling setting cannot be used
owenmehegan updated JENKINS-14720 Warning should display if fast remote polling setting cannot be used Change By: owenmehegan (08/Aug/12 5:22 PM) Summary: Fast Warningshoulddisplayiffast remotepolling setting doesnotsavewhenselectedinjobconfig cannotbeused 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-14734) Jenkins Polling fails on windows slaves
Vasudeva Bhat created JENKINS-14734 Jenkins Polling fails on windows slaves Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: mercurial Created: 08/Aug/12 6:15 PM Description: Mercurial polling on a Windows slave reports there are no changes even when there are. The error reported is different from JENKINS-11222, so, I created a new ticket. Jenkins reports http authorization missing, and no changes are seen. If I kick off the build manually, no issues with authorization, as well as the changes are brought in. Mercurial Polling Log: Started on Aug 8, 2012 8:00:05 PM $ hg pull --rev default abort: http authorization required Done. Took 0.79 sec No changes Is there a problem polling with http access? Jenkins ver. 1.461 Hg: 1.38 Project: Jenkins Priority: Major Reporter: Vasudeva Bhat 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-14712) Bulk Builder plugin doesn't show views created within a nested view
Simon Westcott commented on JENKINS-14712 Bulk Builder plugin doesnt show views created within a nested view I don't dispute that, however adding support for the nested view plugin is a new feature rather than a bug. Patches on Github are most welcome if this is causing particular pain for yourself. 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-14697) Can't use an existing view in a nested view - Nested view component
Simon Westcott commented on JENKINS-14697 Cant use an existing view in a nested view - Nested view component Is this a dup of JENKINS-6961? 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-14728) Buil-flow jobs fail to load the job history if the envinject plugin is installed
SCM/JIRA link daemon commented on JENKINS-14728 Buil-flow jobs fail to load the job history if the envinject plugin is installed Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/lib/envinject/EnvInjectAction.java http://jenkins-ci.org/commit/envinject-lib/38e2c3f2b10388328a38dbc553f217ca75fdd5e5 Log: More tolerant to avoid loading errors (JENKINS-14728) 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-14735) Cannot ovveride Subversion credentials to authenticate to server
Lee Solomon created JENKINS-14735 Cannot ovveride Subversion credentials to authenticate to server Issue Type: Bug Assignee: Unassigned Components: subversion Created: 08/Aug/12 7:35 PM Description: I am using Jenkins 1.475 on Windows and when configuring a project to connect to a Subversion repository, I go to the 'enter credentials' screen and enter my username and password. I get a 403 Forbidden error. From the Apache server logs I can see that it is trying to authenticate with username 'hudsonUser' as opposed to my username. Can someone please help me with this? Environment: Jenkins 1.475 on Windows Project: Jenkins Priority: Major Reporter: Lee Solomon 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-14728) Buil-flow jobs fail to load the job history if the envinject plugin is installed
Gregory Boissinot started work on JENKINS-14728 Buil-flow jobs fail to load the job history if the envinject plugin is installed Change By: Gregory Boissinot (08/Aug/12 7:38 PM) Status: Open InProgress 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-14728) Buil-flow jobs fail to load the job history if the envinject plugin is installed
Gregory Boissinot commented on JENKINS-14728 Buil-flow jobs fail to load the job history if the envinject plugin is installed Could you check if the following version of the EnvInject plugin fix the issue? https://buildhive.cloudbees.com/job/jenkinsci/job/envinject-plugin/ws/target/ 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-14736) Secured pages should redirect to login prompt instead of generating 404
Alex Rovner created JENKINS-14736 Secured pages should redirect to login prompt instead of generating 404 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: security Created: 08/Aug/12 8:11 PM Description: Using version 1.475 We have set our permissions to disallow anonymous "read job". What ends up happening is that when you are logged out and try to access a build or a job (Example: http://jenkins.core:8080/job/campaign-management%20release-candidate/210/) Jenkins returns 404 instead of redirecting you to the log-in page. At the minimum, it should display an error message that you are not authenticated. Error returned below: Status Code: 404 Exception: Stacktrace: (none) Generated by Winstone Servlet Engine v0.9.10 at Wed Aug 08 16:00:55 EDT 2012 Project: Jenkins Priority: Major Reporter: Alex Rovner 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-14737) maven-site-plugin 3.1 causes Static Analysis Utilities not to display any results
Steven Goldsmith created JENKINS-14737 maven-site-plugin 3.1 causes Static Analysis Utilities not to display any results Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: analysis-core, plugin Created: 08/Aug/12 8:20 PM Description: Version 3.1 of maven-site-plugin causes Checkstyle, PMD and FindBugs plugins to no longer display graphs. There are no errors in Tomcat log. Switching back to version 3.0 of maven-site-plugin allows you to see graphs again. Environment: Ubuntu 12.04, Tomcat 7, JDK 6/7, Jenkins 1.476, 1.466.1 Project: Jenkins Priority: Major Reporter: Steven Goldsmith 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-12180) Active Directory Plugin - Adding AD Group Throws BadCredentialsException
John Prester commented on JENKINS-12180 Active Directory Plugin - Adding AD Group Throws BadCredentialsException What is the status of this issue? I'm still seeing it in version 1.29 of the plugin. Will it be fixed by a code change in an upcoming release? 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-14738) USe new alive repository fromn github
cforce created JENKINS-14738 USe new alive repository fromn github Issue Type: Task Assignee: gaooh Components: redmine Created: 08/Aug/12 10:48 PM Description: This projects src repo seens to be dead. No chnages this years! Please change to this github repo, in already pulled requests. https://github.com/larrycai/redmine-plugin Project: Jenkins Priority: Critical Reporter: cforce 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-14739) EnvInject params are overwritten by default string params
Ben Kershner
created JENKINS-14739
EnvInject params are overwritten by default string params
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Components:
envinject
Created:
08/Aug/12 11:52 PM
Description:
A parameter created by EnvInject by a parent job will be overwritten by triggered jobs if a string parameter already exists.
For example:
1) A parameterized parent project exists. It has a string parameter (defaulted to one):
PARAM_SLAVE_NUMBER=1
It creates a new parameter with EnvInject:
PARAM_SLAVE=Win7-Slave-$PARAM_SLAVE_NUMBER
It then triggers a child project with current build paramters
2) The child project is parameterized with a string parameter as well:
PARAM_SLAVE=Win7-Slave-2
The child project then runs a script on the node specified by PARAM_SLAVE.
The expected operation is that since string parameters should only take the default values when they're not set already (pseudocode: IF NOT EXISTS($PARAM_SLAVE) { PARAM_SLAVE=Win7-Slave-2 }), EnvInject should set PARAM_SLAVE first, and the child project should not re-set PARAM_SLAVE, however, that's not what happens. In the case above, the script will always be run on Win7-Slave-2, no matter what PARAM_SLAVE_NUMBER is set to.
Environment:
Jenkins 1.455 running on Ubuntu 11.04
Project:
Jenkins
Priority:
Major
Reporter:
Ben Kershner
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-14740) ABI isn't used in generated emulator name
Christopher Orr created JENKINS-14740 ABI isnt used in generated emulator name Issue Type: Bug Assignee: Christopher Orr Components: android-emulator Created: 09/Aug/12 12:09 AM Description: If we create two emulators for the same platform, but with different ABIs, the plugin won't realise that a new emulator needs to be created. e.g. a job using an Android 4.1 AVD with x86 ABI will use the name "hudson_en-US_240_WVGA_android-16". Creating another job with Android 4.1, but with the ARM ABI will check for an emulator also called "hudson_en-US_240_WVGA_android-16", find that it exists and won't create it. Ideally, the ABI name (if any) should be part of the generated AVD name. Project: Jenkins Priority: Minor Reporter: Christopher Orr 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-14741) ABI field should be ignored when creating an AVD if not relevant
Christopher Orr created JENKINS-14741 ABI field should be ignored when creating an AVD if not relevant Issue Type: Improvement Assignee: Christopher Orr Components: android-emulator Created: 09/Aug/12 12:12 AM Description: Currently it's not simple to create a matrix job which includes 2.x AVDs as well as 4.x AVDs, since the former don't require an ABI, but the latter do. So if you enter the ABI "armeabi-v7a" in the job configuration, this will be used even when trying to generate the 2.x AVDs, which will fail. Conversely, if you don't enter an ABI, the 2.x AVDs will be generated correctly, but the 4.x ones will fail. We should not pass the "--abi" flag to "android create avd" if the platform version doesn't support ABIs. Project: Jenkins Priority: Minor Reporter: Christopher Orr 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-2673) Invalid CRON Warnings
trejkaz reopened JENKINS-2673 Invalid CRON Warnings Reopening because I'm discovering this now. If it wants to warn about "every hour", it should warn about "every hour", not "every minute". Change By: trejkaz (09/Aug/12 1:34 AM) Resolution: WontFix Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-2673) Invalid CRON Warnings
trejkaz edited a comment on JENKINS-2673 Invalid CRON Warnings Reopening because I'm discovering this now. If it wants to warn about "every hour", it should warn about "every hour", not "every minute". Our rule is even simpler: # Poll every minute. * * * * * 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-14701) Environment Script should be able to run only on the 'master' Matrix Build task
SCM/JIRA link daemon commented on JENKINS-14701 Environment Script should be able to run only on the master Matrix Build task Code changed in jenkins User: Jørgen P. Tjernø Path: src/main/java/com/lookout/jenkins/EnvironmentScript.java src/main/java/com/lookout/jenkins/PersistedEnvironment.java src/main/resources/com/lookout/jenkins/EnvironmentScript/config.jelly src/test/java/com/lookout/jenkins/CountBuilder.java src/test/java/com/lookout/jenkins/EnvironmentScriptMatrixTest.java src/test/java/com/lookout/jenkins/EnvironmentScriptTest.java http://jenkins-ci.org/commit/environment-script-plugin/59b67f5a6a2ed088d70f19f70ea4233d4841d10f Log: JENKINS-14701 Thorough Matrix support. This allows you to only run the script once - on the parent job, before the "configuration" builds are run. This is supported through a new checkbox in the configuration UI. Compare: https://github.com/jenkinsci/environment-script-plugin/compare/272de430a961...59b67f5a6a2e 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-14478) 1.474 breaks adding a list-view to sectioned-view plugin
Bob commented on JENKINS-14478 1.474 breaks adding a list-view to sectioned-view plugin Anybody know how to solve this 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-14478) 1.474 breaks adding a list-view to sectioned-view plugin
Timothy Bingaman commented on JENKINS-14478 1.474 breaks adding a list-view to sectioned-view plugin If it really is related to the linked issues, then it has already been fixed, but not yet released. The associated fix is scheduled for Jenkins v1.477, but I have not verified if that fix actually fixes this particular 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-14701) Environment Script should be able to run only on the 'master' Matrix Build task
Jørgen Tjernø closed JENKINS-14701 as Fixed Environment Script should be able to run only on the master Matrix Build task Change By: Jørgen Tjernø (09/Aug/12 3:19 AM) 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-14701) Environment Script should be able to run only on the 'master' Matrix Build task
Jørgen Tjernø resolved JENKINS-14701 as Fixed Environment Script should be able to run only on the master Matrix Build task Added this feature in 1.1, which was just released. Change By: Jørgen Tjernø (09/Aug/12 3:19 AM) 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-14742) 1.476 can't adding a list-view session delete txt view session related to sectioned-view plugin
Bob created JENKINS-14742 1.476 cant adding a list-view session delete txt view session related to sectioned-view plugin Issue Type: Bug Affects Versions: current Assignee: Timothy Bingaman Attachments: QQ截图20120809112200.jpg, Status Code.jpg Components: sectioned-view Created: 09/Aug/12 3:23 AM Description: 1, when click "delete session" button, make no sense. 2, when add a "list-view session", it will cause "Status Code: 500" error, see attachment. Due Date: 13/Aug/12 12:00 AM Environment: Linux r49d05001.xy2.aliyun.com 2.6.18-164.11.1.el5 #1 SMP Wed Jan 6 13:26:04 EST 2010 x86_64 x86_64 x86_64 GNU/Linux Project: Jenkins Labels: jenkins plugin list-view-session sectioned-view Priority: Blocker Reporter: Bob 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-14742) 1.476 can't adding a list-view session delete txt view session related to sectioned-view plugin
Bob updated JENKINS-14742 1.476 cant adding a list-view session delete txt view session related to sectioned-view plugin Change By: Bob (09/Aug/12 3:24 AM) Attachment: StatusCode.jpg 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-14478) 1.474 breaks adding a list-view to sectioned-view plugin
Bob commented on JENKINS-14478 1.474 breaks adding a list-view to sectioned-view plugin Thx very much, I will close another ticket rised by me... hope this version can be released as soon as possible. and btw, it also can not delete the session when you click the "delete session" button, do you also know this problem? can this problem also be fixed in new version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14742) 1.476 can't adding a list-view session delete txt view session related to sectioned-view plugin
Bob commented on JENKINS-14742 1.476 cant adding a list-view session delete txt view session related to sectioned-view plugin sorry, I've found the related issue: https://issues.jenkins-ci.org/browse/JENKINS-14478 this ticket will be colsed. 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
