[JIRA] (JENKINS-15698) Perforce can't get hostname for slaves
Alexey Larsky created JENKINS-15698 Perforce cant get hostname for slaves Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: P4_settings.png Components: perforce Created: 02/Nov/12 6:31 AM Description: I have lots of Perforce warnings in log. Perforce settings are atteched. WARNING: Could not get hostname for slave rusbuilder-ims Nov 2, 2012 10:12:26 AM hudson.plugins.perforce.PerforceSCM getEffectiveClientName WARNING: Could not get hostname for slave rusbuilder-ims Nov 2, 2012 10:12:26 AM hudson.plugins.perforce.PerforceSCM getEffectiveClientName WARNING: Could not get hostname for slave rusbuilder-ims Nov 2, 2012 10:12:26 AM hudson.plugins.perforce.PerforceSCM getEffectiveClientName WARNING: Could not get hostname for slave rusbuilder-ims Nov 2, 2012 10:12:26 AM hudson.plugins.perforce.PerforceSCM getEffectiveClientName WARNING: Could not get hostname for slave rusbuilder-ims Environment: Jenkins ver. 1.488 Perforce 1.3.17, ws isnt managed by perforce plugin Project: Jenkins Labels: slave plugin windows scm warnings Priority: Minor Reporter: Alexey Larsky 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-15698) Perforce can't get hostname for slaves
Alexey Larsky commented on JENKINS-15698 Perforce cant get hostname for slaves The same issue was closed https://issues.jenkins-ci.org/browse/JENKINS-6257 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-14019) Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building
Andrew Erickson commented on JENKINS-14019 Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building I just encountered this. You need to set the field in the advanced options (the second advanced option set) called "unique SCM name (optional)". It's not really optional when using this plugin (as the tip says). My builds are now not executing on every polling instance. Not sure if it's possible for plugins to make option fields required... but it would be nice if this did that. 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-15699) Improve behaviour of plugin when analyzed code contains compile errors
Mads Nielsen created JENKINS-15699 Improve behaviour of plugin when analyzed code contains compile errors Issue Type: Improvement Affects Versions: current Assignee: Praqma Support Components: prqa Created: 02/Nov/12 9:57 AM Description: QAW does not perform any project wide analysis when a level 9 error occurs. This prevents the QAR reports from being generated so the plugin cannot find them and this makes the build fail. Project: Jenkins Priority: Minor Reporter: Mads Nielsen 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-15700) SVNException: svn: E210003: Malformed reply from SOCKS server at ....
Joël Royer updated JENKINS-15700 SVNException: svn: E210003: Malformed reply from SOCKS server at Change By: Joël Royer (02/Nov/12 10:17 AM) Environment: Jenkinsserver:WindowsServer2003R2/Glassfish3.1.2.2/ OracleJavaSE1.6/ Jenkins1.487Subversionserver:LinuxDebian5x64/Subversion1.4.6 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-15700) SVNException: svn: E210003: Malformed reply from SOCKS server at ....
Joël Royer created JENKINS-15700 SVNException: svn: E210003: Malformed reply from SOCKS server at Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 02/Nov/12 10:16 AM Description: We've got the next error from time to time when jobs tried to update their workspace. The only solution we've found for the moment is to reboot jenkins server. Building in workspace C:\PIC\work\jenkins-work\jobs\MyJob\workspace Updating svn://svnserver/myproject/trunk to revision '2012-10-29T10:43:48.770 +0100' ERROR: Failed to update svn://svnserver/myproject/trunk org.tmatesoft.svn.core.SVNException: svn: E210003: Malformed reply from SOCKS server at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:85) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:69) at org.tmatesoft.svn.core.internal.io.svn.SVNPlainConnector.open(SVNPlainConnector.java:65) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1252) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.testConnection(SVNRepositoryImpl.java:95) at org.tmatesoft.svn.core.io.SVNRepository.getRepositoryUUID(SVNRepository.java:280) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:339) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:328) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:532) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:414) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:324) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1221) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:315) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:295) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:391) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:144) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:799) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:780) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:763) at hudson.FilePath.act(FilePath.java:851) at hudson.FilePath.act(FilePath.java:824) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:746) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:688) at hudson.model.AbstractProject.checkout(AbstractProject.java:1308) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:679) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:584) at hudson.model.Run.execute(Run.java:1516) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.net.SocketException: Malformed reply from SOCKS server at java.net.SocksSocketImpl.readSocksReply(SocksSocketImpl.java:128) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:459) at java.net.Socket.connect(Socket.java:579) at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.connect(SVNSocketFactory.java:112) at
[JIRA] (JENKINS-9616) Revert configuration to an older version
Mirko Friedenhagen commented on JENKINS-9616 Revert configuration to an older version Kathi Stutz: is the release already done? Which version number? 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-15502) Email-ext issues: attachments feature creating issues
Slide-O-Mix commented on JENKINS-15502 Email-ext issues: attachments feature creating issues I'm still trying to see if I can setup something to reproduce this. I don't have a build setup available with slaves, so I'm trying to set something up with VM's 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-15701) Integrate branch gives No changes to be integrated
Tobias Dittrich created JENKINS-15701 Integrate branch gives No changes to be integrated Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: svnmerge Created: 02/Nov/12 11:12 AM Description: Create a project with "Accept Integration from Subversion feature branches" check out trunk of a subversion project build the trunk project Create a feature branch from this project in jenkins (I called it "development") build the branch project integrate the build in the trunk - works correctly change some files in the branch and commit those changes build the branch project again integrate the new build in the trunk Gives: No changes to be integrated. Skipping integration. Completed Environment: svn, Version 1.6.17 (r1128011) (client version on jenkins) SVN/1.6.17 SVNKit/1.3.7-1 (http://svnkit.com/) t20111225_1716 (SVN Server version) Jenkins ver. 1.488 Jenkins svnmerge plugin 1.2 Project: Jenkins Priority: Critical Reporter: Tobias Dittrich 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-15701) Integrate branch gives No changes to be integrated
Tobias Dittrich
updated JENKINS-15701
Integrate branch gives No changes to be integrated
Change By:
Tobias Dittrich
(02/Nov/12 11:14 AM)
Description:
#CreateaprojectwithAcceptIntegrationfromSubversionfeaturebranches#
SCMsetting:
checkouttrunkofasubversionproject#buildthetrunkproject#Createafeaturebranchfromthisprojectinjenkins(Icalleditdevelopment)#buildthebranchproject#integratethebuildinthetrunk-workscorrectly#changesomefilesinthebranchandcommitthosechanges#buildthebranchprojectagain#integratethenewbuildinthetrunkGives:{quote}Nochangestobeintegrated.Skippingintegration.Completed{quote}
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-15701) Integrate branch gives No changes to be integrated
Tobias Dittrich
updated JENKINS-15701
Integrate branch gives No changes to be integrated
Change By:
Tobias Dittrich
(02/Nov/12 11:16 AM)
Description:
#CreateaprojectwithAcceptIntegrationfromSubversionfeaturebranches#SCMsetting:checkouttrunkofasubversionproject#buildthetrunkproject#Createafeaturebranchfromthisprojectinjenkins(Icalleditdevelopment)#buildthebranchproject#integratethebuildinthetrunk-workscorrectly#changesomefilesinthebranchandcommitthosechanges#buildthebranchprojectagain#integratethenewbuildinthetrunkGives:{quote}Nochangestobeintegrated.Skippingintegration.Completed{quote}
Expected:themodifiedfilesaremergedintothetrunk
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-13120) Extend criteria for current regression/improvement triggers
Slide-O-Mix resolved JENKINS-13120 as Incomplete Extend criteria for current regression/improvement triggers Need more information from submitter. Change By: Slide-O-Mix (02/Nov/12 11:22 AM) Status: Open Resolved Resolution: Incomplete 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-6859) [Regression] Error message when proxy auth fails for update center does not allow user to understand/correct the issue.
Tjeerd Verhagen commented on JENKINS-6859 [Regression] Error message when proxy auth fails for update center does not allow user to understand/correct the issue. Workaround: Edit the configuration file 'jenkins.xml' add to the tag service arguments the java option '-Dhttp.maxRedirects=100' to change the number of maximum redirects. 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-6859) [Regression] Error message when proxy auth fails for update center does not allow user to understand/correct the issue.
Tjeerd Verhagen edited a comment on JENKINS-6859 [Regression] Error message when proxy auth fails for update center does not allow user to understand/correct the issue. Workaround: Edit the configuration file 'jenkins.xml' add to the tag service arguments the java option '-Dhttp.maxRedirects=100' to change the number of maximum redirects. Jenkins ver. 1.488 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-6604) Possible race condition in RemoteClassLoader renders slave unusable
Erik Lovlie commented on JENKINS-6604 Possible race condition in RemoteClassLoader renders slave unusable Any chance this can be looked at? It would seem like a big severity/effort ratio. 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-6604) Possible race condition in RemoteClassLoader renders slave unusable
Erik Lovlie assigned JENKINS-6604 to Kohsuke Kawaguchi Possible race condition in RemoteClassLoader renders slave unusable Change By: Erik Lovlie (02/Nov/12 1:17 PM) Assignee: AndreyMyatlyuk KohsukeKawaguchi 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-10318) ConcurrentModificationException reading config.xml on startup
David Ehrenberger commented on JENKINS-10318 ConcurrentModificationException reading config.xml on startup This occurring often on v1.487. Please elevate in priority. 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-10318) ConcurrentModificationException reading config.xml on startup
David Ehrenberger commented on JENKINS-10318 ConcurrentModificationException reading config.xml on startup For what its worth, the following error looks to be related to a coverity publisher: Nov 2, 2012 9:23:25 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job Job.Coverity hudson.util.IOException2: Unable to read /jenkins/jobs/Job.Coverity/config.xml at hudson.XmlFile.read(XmlFile.java:141) at hudson.model.Items.load(Items.java:220) at jenkins.model.Jenkins$17.run(Jenkins.java:2507) 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:883) 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:662) Caused by: com.thoughtworks.xstream.converters.ConversionException: null : null Debugging information cause-exception : java.util.ConcurrentModificationException cause-message : null class : hudson.model.FreeStyleProject required-type : jenkins.plugins.coverity.CoverityPublisher path: /project/publishers/jenkins.plugins.coverity.CoverityPublisher/invocationAssistance line number : 76 --- 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:263) 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 hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:332) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:274) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:221) 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.unmarshal(XStream.java:926) at hudson.util.XStream2.unmarshal(XStream2.java:103) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:912) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:864) at hudson.XmlFile.read(XmlFile.java:137) ... 10 more Caused by: java.util.ConcurrentModificationException at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1100) at java.util.TreeMap$KeyIterator.next(TreeMap.java:1154) at com.thoughtworks.xstream.core.util.PrioritizedList$PrioritizedItemIterator.next(PrioritizedList.java:91) at com.thoughtworks.xstream.core.DefaultConverterLookup.lookupConverterForType(DefaultConverterLookup.java:62) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:332) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:274) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:221) at
[JIRA] (JENKINS-15702) InstantiationError: hudson.scm.AbstractCvs
David Ehrenberger created JENKINS-15702 InstantiationError: hudson.scm.AbstractCvs Issue Type: Bug Assignee: Unassigned Components: cvs Created: 02/Nov/12 1:34 PM Description: Getting the following in the system log at startup. Not sure of the ramifications. Nov 2, 2012 9:23:30 AM hudson.util.RobustReflectionConverter doUnmarshal WARNING: Failed to resolve a type java.lang.InstantiationError: hudson.scm.AbstractCvs at sun.reflect.GeneratedSerializationConstructorAccessor507.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.thoughtworks.xstream.converters.reflection.Sun14ReflectionProvider.newInstance(Sun14ReflectionProvider.java:76) at hudson.util.RobustReflectionConverter.instantiateNewInstance(RobustReflectionConverter.java:375) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:220) 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 hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:332) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:274) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:221) 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.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:61) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) 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 hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:332) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:274) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:221) 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.unmarshal(XStream.java:926) at hudson.util.XStream2.unmarshal(XStream2.java:103) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:912) at hudson.XmlFile.unmarshal(XmlFile.java:160) at hudson.model.Run.reload(Run.java:291) at hudson.model.Run.init(Run.java:280) at hudson.model.AbstractBuild.init(AbstractBuild.java:182) at hudson.model.Build.init(Build.java:103) at hudson.model.FreeStyleBuild.init(FreeStyleBuild.java:41) at sun.reflect.GeneratedConstructorAccessor33.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at
[JIRA] (JENKINS-15493) Excessive memory usage with large number of request threads
Jesse Glick commented on JENKINS-15493 Excessive memory usage with large number of request threads @chrisgwarp: “Build records are now lazy loaded…”, in 1.485, was a huge change, including some known regressions (some fixed in subsequent releases), and your stack trace is almost certainly related to that change rather than the fix for this issue. If you continue to have problems please file a separate bug report and link it to JENKINS-8754. 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-7481) ClearCase polling change degrades performance for large VOBs
bbonn commented on JENKINS-7481 ClearCase polling change degrades performance for large VOBs Sounds good. Any idea when they will do another pull? In the meantime do you have a version I could test with from your branch? I was wondering if there was any new config we have to do to force the -r in stead of -all. Thanks again! 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-15703) Cobertura ClassCastException
Stuart Axon created JENKINS-15703 Cobertura ClassCastException Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: cobertura Created: 02/Nov/12 4:20 PM Description: Coverage has generated reports, but covertura gets a ClassCastException When running I get this error: Ran 7 tests in 2.875s OK Creating test database for alias 'default'... Creating UserProfiles for users made with createsuperuser or syncdb. Creating UserProfiles for users made with createsuperuser or syncdb. Destroying test database for alias 'default'... Terminating xvnc. $ vncserver -kill :10 Killing Xvnc4 process ID 3891 Publishing Cobertura coverage report... ERROR: Publisher hudson.plugins.cobertura.CoberturaPublisher aborted due to exception java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Boolean at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.reset(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.reset(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.reset(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.init(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.init(Unknown Source) at com.sun.xml.internal.stream.XMLInputFactoryImpl.getXMLStreamReaderImpl(Unknown Source) at com.sun.xml.internal.stream.XMLInputFactoryImpl.createXMLStreamReader(Unknown Source) at com.sun.xml.internal.stream.XMLInputFactoryImpl.createXMLEventReader(Unknown Source) at hudson.plugins.cobertura.CoberturaPublisher$ParseReportCallable.invoke(CoberturaPublisher.java:546) at hudson.plugins.cobertura.CoberturaPublisher$ParseReportCallable.invoke(CoberturaPublisher.java:529) at hudson.FilePath.act(FilePath.java:839) at hudson.FilePath.act(FilePath.java:821) at hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:335) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:685) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:632) at hudson.model.Run.run(Run.java:1463) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Recording test results Sending e-mails to: stuart.a...@jpcreative.co.uk Finished: FAILURE Environment: django-jenkins on Ubuntu 12.10 Project: Jenkins Priority: Major Reporter: Stuart Axon 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-15704) Incomplete list of builds when I go to JobName/api/json
Daniel Kaplan created JENKINS-15704 Incomplete list of builds when I go to JobName/api/json Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: json.txt, screenshot.png Components: build-flow, promoted-builds Created: 02/Nov/12 5:21 PM Description: I see a different list of builds when I go to JobName/api/json as I do when I go to JobName from the UI. JobName/api/json has a few less builds and it's even excluding promoted builds at the bottom which is a blocker for our company. I've attached the JSON that we see and a screenshot of the builds on the UI. You can see in the JSON that build number 253 is nowhere to be found even though it's a promoted build and listed on the UI. Project: Jenkins Priority: Major Reporter: Daniel Kaplan 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-15705) Redeploy of .ear files on glassfish don't work.
Elvis Hektor Ratzlaff Koop created JENKINS-15705 Redeploy of .ear files on glassfish dont work. Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: deploy.diff Components: deploy Created: 02/Nov/12 5:33 PM Description: The first time the deploy for .ear files work fine. The second time show the error currently deployed. Attached the fix for redploy .ear files. Project: Jenkins Priority: Major Reporter: Elvis Hektor Ratzlaff Koop 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-15706) Quality center plugin for Jenkins does not work properly
chetbani nadjim updated JENKINS-15706 Quality center plugin for Jenkins does not work properly Change By: chetbani nadjim (02/Nov/12 5:58 PM) Description: HelloAll,Whenstartingthetestwegetthefollowingoutput:Anyhelpwillbegreatlyappreciated.StartedbyuseranonymousBuildinginworkspaceC:\DocumentsandSettings\PRJ\.jenkins\workspace\QC-Test[QC-Test]$cscript/nologoC:\DocumentsandSettings\PRJ\.jenkins\workspace\QC-Test\runTestSet.vbshttp://qc-server/qcbinqc-user TD1PCCTACET DOMPRJDIR \QCQCpluginqcreport-QCplugin-15.xml600RUN_REMOTElocalhost02/11/201218:47:35:Scriptparameters:02/11/201218:47:35:*02/11/201218:47:35:QCServer:http://qc-server/qcbin02/11/201218:47:35:QCUserName:qc-user02/11/201218:47:35:QCPassword:02/11/201218:47:35:QCDomain:DOM02/11/201218:47:35:QCProject:PRJ02/11/201218:47:35:QCTestSetFolder:DIR\QC02/11/201218:47:35:QCTestSetName:QCplugin02/11/201218:47:35:XMLJunitFile:qcreport-QCplugin-15.xml02/11/201218:47:35:Timeout:60002/11/201218:47:35:*02/11/201218:47:35:RunMode:RUN_REMOTE02/11/201218:47:35:RunHost:localhost02/11/201218:47:35:*Connectedtoserverhttp://qc-server/qcbinLoggedinwithuserqc-userOpenedprojectDOM\PRJ+--+|TestSetName|ID|+--+|QCplugin|3077|+--+CouldnotinstantiatetestsetschedulerCreatingreport...GeneratingreportfileReportfilepath:qcreport-QCplugin-15.xml+--+|TestName|Status|+--+ReportCreatedFATAL:CouldntruntestsBuildstepHPQualityCentermarkedbuildasfailureFinished:FAILURE 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-15706) Quality center plugin for Jenkins does not work properly
chetbani nadjim created JENKINS-15706 Quality center plugin for Jenkins does not work properly Issue Type: Bug Assignee: Unassigned Components: plugin Created: 02/Nov/12 5:57 PM Description: Hello All, When starting the test we get the following output : Any help will be greatly appreciated. Started by user anonymous Building in workspace C:\Documents and Settings\PRJ\.jenkins\workspace\QC-Test QC-Test $ cscript /nologo "C:\Documents and Settings\PRJ\.jenkins\workspace\QC-Test\runTestSet.vbs" http://qc-server/qcbin qc-user TD1P CCT ACET\QC "QC plugin" "qcreport-QC plugin-15.xml" 600 RUN_REMOTE localhost 02/11/2012 18:47:35 : Script parameters: 02/11/2012 18:47:35 : * 02/11/2012 18:47:35 : QC Server : http://qc-server/qcbin 02/11/2012 18:47:35 : QC UserName : qc-user 02/11/2012 18:47:35 : QC Password : 02/11/2012 18:47:35 : QC Domain : DOM 02/11/2012 18:47:35 : QC Project : PRJ 02/11/2012 18:47:35 : QC TestSetFolder: DIR\QC 02/11/2012 18:47:35 : QC TestSetName : QC plugin 02/11/2012 18:47:35 : XML Junit File : qcreport-QC plugin-15.xml 02/11/2012 18:47:35 : Timeout : 600 02/11/2012 18:47:35 : * 02/11/2012 18:47:35 : RunMode : RUN_REMOTE 02/11/2012 18:47:35 : RunHost : localhost 02/11/2012 18:47:35 : * Connected to server http://qc-server/qcbin Logged in with user qc-user Opened project DOM\PRJ -- TestSet Name ID -- QC plugin 3077 -- Could not instantiate test set scheduler Creating report... Generating report file Report file path: qcreport-QC plugin-15.xml -- Test Name Status -- Report Created FATAL: Couldn't run tests Build step 'HP Quality Center' marked build as failure Finished: FAILURE Project: Jenkins Priority: Major Reporter: chetbani nadjim 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-15367) Jenkins kicks off the wrong downstream builds for Maven
Alex Koon updated JENKINS-15367 Jenkins kicks off the wrong downstream builds for Maven I have traced this issue as part of https://issues.jenkins-ci.org/browse/JENKINS-12735 I have added a test case to MavenModuleTest to show this and a fix for this in ModuleDependency. I have pushed this to my fork on github at https://github.com/alexkoon/jenkins and the commit is at https://github.com/alexkoon/jenkins/commit/4043905580df5bf22cde0eaf3dec103abdc88017 I can issue a pull request for this if you wish. 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-12735) No upstream or downstream resolution with Maven version ranges
Alex Koon commented on JENKINS-12735 No upstream or downstream resolution with Maven version ranges Commented on this at https://issues.jenkins-ci.org/browse/JENKINS-15367. 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-12735) No upstream or downstream resolution with Maven version ranges
Alex Koon updated JENKINS-12735 No upstream or downstream resolution with Maven version ranges Change By: Alex Koon (02/Nov/12 6:53 PM) Status: Reopened 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-15704) Incomplete list of builds when I go to JobName/api/json
Kohsuke Kawaguchi updated JENKINS-15704 Incomplete list of builds when I go to JobName/api/json Change By: Kohsuke Kawaguchi (02/Nov/12 7:09 PM) Attachment: json.txt 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-15704) Incomplete list of builds when I go to JobName/api/json
Daniel Kaplan updated JENKINS-15704 Incomplete list of builds when I go to JobName/api/json Change By: Daniel Kaplan (02/Nov/12 7:18 PM) Description: IseeadifferentlistofbuildswhenIgotoJobName/api/jsonasIdowhenIgotoJobNamefromtheUI.JobName/api/jsonhasafewlessbuildsanditsevenexcludingpromotedbuildsatthebottomwhichisablockerforourcompany. Iveattached In theJSON thatweseeandascreenshotofthebuildsontheUI.YoucanseeintheJSONthat buildnumber253isnowheretobefoundeventhoughitsapromotedbuildandlistedontheUI. 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-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded
vijay singh commented on JENKINS-15335 Jenkins briefly displays build queue and then it disappears until the page is reloaded This is occurs in 1.487. Every new job created post 1.487 have their builds and workspace disappearing on the UI. Reverted to release 1.486 and all builds and workspace are visible. 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-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded
vijay singh edited a comment on JENKINS-15335 Jenkins briefly displays build queue and then it disappears until the page is reloaded This is occurs in 1.487. Every new job created post 1.487 have their builds and workspace disappearing on the UI. Reverted to release 1.486 and all builds and workspace are visible. Firefox 16.0.1 on Mac OS X 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-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded
vijay singh reopened JENKINS-15335 Jenkins briefly displays build queue and then it disappears until the page is reloaded This is occurs in 1.487. Every new job created post 1.487 have their builds and workspace disappearing on the UI. Reverted to release 1.486 and all builds and workspace are visible. Firefox 16.0.1 on Mac OS X Change By: vijay singh (02/Nov/12 8:12 PM) Resolution: Fixed Status: Resolved 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-15707) Cppcheck Trend graph is blank even though the plugin processes stats correctly
Pierre-Etienne Messier created JENKINS-15707 Cppcheck Trend graph is blank even though the plugin processes stats correctly Issue Type: Bug Assignee: Gregory Boissinot Attachments: cppcheck.png Components: cppcheck Created: 02/Nov/12 9:01 PM Description: When running the cppcheck plugin, it will process successfully the .xml file (displays "Cppcheck: 494 errors." in the build, error list works nice). On the Project scope, the Cppcheck Trend graph is blank even though other graphs display fine (see screenshot). I wonder why (missing dependencies?) Environment: Jenkins ver. 1.488 cppcheck plugin 1.10 cppcheck binary: 1.40 1.57dev Build slave: Ubuntu 10.04 32 bits Jenkins master: Ubuntu 12.04.1 64 bits Fix Versions: current Project: Jenkins Labels: plugin Priority: Major Reporter: Pierre-Etienne Messier 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-15658) EnvInject Undefines Jenkins Global properties referencing WORKSPACE variable
SCM/JIRA link daemon commented on JENKINS-15658 EnvInject Undefines Jenkins Global properties referencing WORKSPACE variable Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectJobProperty.java src/main/java/org/jenkinsci/plugins/envinject/EnvInjectJobPropertyInfo.java src/test/java/org/jenkinsci/plugins/envinject/GlobalPropertiesTest.java http://jenkins-ci.org/commit/envinject-plugin/be86097a4ebf373d4874cc5e89e89fd250bf3a01 Log: Add a regression test to fix JENKINS-15658 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-15658) EnvInject Undefines Jenkins Global properties referencing WORKSPACE variable
Gregory Boissinot resolved JENKINS-15658 as Fixed EnvInject Undefines Jenkins Global properties referencing WORKSPACE variable Change By: Gregory Boissinot (02/Nov/12 9:04 PM) Status: InProgress 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-15664) Help text for EnvInject plugin is wrong
Gregory Boissinot resolved JENKINS-15664 as Fixed Help text for EnvInject plugin is wrong Change By: Gregory Boissinot (02/Nov/12 9:04 PM) Status: InProgress 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-14452) Jenkins/Winstone has problems with IPv6
Kohsuke Kawaguchi
updated JENKINS-14452
Jenkins/Winstone has problems with IPv6
Change By:
Kohsuke Kawaguchi
(02/Nov/12 9:37 PM)
Description:
Note:AsIdonthaveanyideawhichcomponentthisis,astheWinstoneServletEngineisntinthelistandtheredoesntseemtobeanIncomingcomponent,pleasere-assignasrequired.Imusingjenkinswiththedebianpackages.IveconfiguredJenkinstolistenonIPv6,andanIPv4reverseproxy.Everythingworksasexpected,however,Jenkinscomplainsthatthereverseproxyisntconfiguredcorrectly.Afterinvestigatingandusingthehintfromhttps://wiki.jenkins-ci.org/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken,Iveencounteredthefollowingoutput.ItseemsthattheWinstoneServletdoesntsupportIPv6,because2a01:4f8:161:286:::103:8080isntcorrect.Itshouldbe[2a01:4f8:161:286:::103]:8080
{noformat}
wget--no-check-certificate--debug-O/dev/nullhttp://ci.partkeepr.org//administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testSetting--output-document(outputdocument)to/dev/nullDEBUGoutputcreatedbyWget1.13.4onlinux-gnu.URIencoding=`UTF-8--2012-07-1705:38:46--http://ci.partkeepr.org//administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testResolvingci.partkeepr.org(ci.partkeepr.org)...78.46.93.106Cachingci.partkeepr.org=78.46.93.106Connectingtoci.partkeepr.org(ci.partkeepr.org)|78.46.93.106|:80...connected.Createdsocket4.Releasing0x0108b260(newrefcount1).---requestbegin---GET//administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testHTTP/1.1User-Agent:Wget/1.13.4(linux-gnu)Accept:*/*Host:ci.partkeepr.orgConnection:Keep-Alive---requestend---HTTPrequestsent,awaitingresponse...---responsebegin---HTTP/1.1302FoundDate:Tue,17Jul201203:38:46GMTServer:WinstoneServletEnginev0.9.10Location:http://2a01:4f8:161:286:::103:8080/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test-for-reverse-proxy-setupContent-Length:0X-Powered-By:Servlet/2.5(Winstone/0.9.10)Keep-Alive:timeout=15,max=100Connection:Keep-AliveContent-Type:text/plain---responseend---302FoundRegisteredsocket4forpersistentreuse.Location:http://2a01:4f8:161:286:::103:8080/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test-for-reverse-proxy-setup[following]]done.URIcontentencoding=Nonehttp://2a01:4f8:161:286:::103:8080/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test-for-reverse-proxy-setup:Badportnumber.felicitus@feli-desktop~/public_html/PartKeepr$wget--no-check-certificate--debug-O/dev/nullhttp://ci.partkeepr.org/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testSetting--output-document(outputdocument)to/dev/nullDEBUGoutputcreatedbyWget1.13.4onlinux-gnu.URIencoding=`UTF-8--2012-07-1705:38:51--http://ci.partkeepr.org/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testResolvingci.partkeepr.org(ci.partkeepr.org)...78.46.93.106Cachingci.partkeepr.org=78.46.93.106Connectingtoci.partkeepr.org(ci.partkeepr.org)|78.46.93.106|:80...connected.Createdsocket4.Releasing0x01d3c260(newrefcount1).---requestbegin---GET/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testHTTP/1.1User-Agent:Wget/1.13.4(linux-gnu)Accept:*/*Host:ci.partkeepr.orgConnection:Keep-Alive---requestend---HTTPrequestsent,awaitingresponse...---responsebegin---HTTP/1.1302FoundDate:Tue,17Jul201203:38:52GMTServer:WinstoneServletEnginev0.9.10Location:http://2a01:4f8:161:286:::103:8080/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test-for-reverse-proxy-setupContent-Length:0X-Powered-By:Servlet/2.5(Winstone/0.9.10)Keep-Alive:timeout=15,max=100Connection:Keep-AliveContent-Type:text/plain---responseend---302FoundRegisteredsocket4forpersistentreuse.Location:http://2a01:4f8:161:286:::103:8080/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test-for-reverse-proxy-setup[following]]done.URIcontentencoding=Nonehttp://2a01:4f8:161:286:::103:8080/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test-for-reverse-proxy-setup:Badportnumber.
{noformat}
This message is automatically generated by JIRA.
If you think it was sent
[JIRA] (JENKINS-15708) Xcode Plugin not expanding $(SRCROOT) variable
David Howell
created JENKINS-15708
Xcode Plugin not expanding $(SRCROOT) variable
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
xcode
Created:
02/Nov/12 9:48 PM
Description:
I am using the Xcode plugin to build my iOS App. I want to configure the plugin to set the Technical version of the app to e.g. r${SVN_REVISION}.
When I do this it doesn't work and I get the following in my console log. There is a myApp-Info.plist file in the myApp directory.
I have had similar problems around $(SRCROOT) when I ask the plugin to create the ipa file - the command line that is executed contains $(SRCROOT) literally without the variable being evaluated.
Started by user anonymous
Building in workspace /Users/Shared/Jenkins/Home/workspace/iOS-myApp
Updating svn://repository.invoqsystems.com/repository/apex/mobile/ios/trunk
At revision 56840
no change for svn://repository.invoqsystems.com/repository/apex/mobile/ios/trunk since the previous build
iOS-myApp $ /bin/sh -xe /var/folders/_b/vh7gd76s30j_pjy0g5mdzwvm7b/T/hudson38657611056669647.sh
Working directory is /Users/Shared/Jenkins/Home/workspace/iOS-myApp.
iOS-myApp $ /usr/bin/xcodebuild -version
Xcode 4.5
Build version 4G182
Fetching marketing version number (CFBundleShortVersionString) from project.
iOS-myApp $ /usr/bin/agvtool mvers -terse1
Found marketing version (CFBundleShortVersionString): $(SRCROOT)/myApp/myApp-Info.plist
1.0.
Marketing version (CFBundleShortVersionString) found in project configuration: $(SRCROOT)/myApp/myApp-Info.plist
1.0.
Fetching technical version number (CFBundleVersion) from project.
iOS-myApp $ /usr/bin/agvtool vers -terse
No marketing version found (CFBundleVersion)
Technical version (CFBundleVersion) found in project configuration: .
Updating technical version (CFBundleVersion) to: r56831-b39
iOS-myApp $ /usr/bin/agvtool new-version -all r56831-b39
Setting version of project myApp to:
r56831-b39.
Also setting CFBundleVersion key (assuming it exists)
Updating CFBundleVersion in Info.plist(s)...
$(SRCROOT)/myApp/myApp-Info.plist
Cannot find "$(SRCROOT)/myApp/myApp-Info.plist"
Updated CFBundleVersion in "myApp.xcodeproj/../myAppUnitTests/myAppUnitTests-Info.plist" to r56831-b39
Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: $(SRCROOT)/myApp/myApp-Info.plist
1.0
Technical version (CFBundleVersion) used by Jenkins to produce the IPA: r56831-b39
Environment:
OSX 10.8.1
Jenkins 1.488
Xcode Plugin 1.3.1
Project:
Jenkins
Priority:
Major
Reporter:
David Howell
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-14452) Jenkins/Winstone has problems with IPv6
SCM/JIRA link daemon commented on JENKINS-14452 Jenkins/Winstone has problems with IPv6 Code changed in jenkins User: Kohsuke Kawaguchi Path: src/java/winstone/HttpListener.java src/java/winstone/WinstoneRequest.java http://jenkins-ci.org/commit/winstone/f0ffcde68653567780b9e8920457019256e72f7c Log: FIXED JENKINS-14452 Fixed the handling of IPv6 address 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-14452) Jenkins/Winstone has problems with IPv6
SCM/JIRA link daemon resolved JENKINS-14452 as Fixed Jenkins/Winstone has problems with IPv6 Change By: SCM/JIRA link daemon (02/Nov/12 10:23 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-15698) Perforce can't get hostname for slaves
Rob Petti commented on JENKINS-15698 Perforce cant get hostname for slaves This is a problem with core, unfortunately. Getting the hostname of a machine using java is actually quite difficult, so it doesn't work 100% of the time. Check that the hostname is resolvable in DNS, and that the slave isn't running more than one networking interface. Apart from that, there's really nothing else that can be done. 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-14452) Jenkins/Winstone has problems with IPv6
SCM/JIRA link daemon commented on JENKINS-14452 Jenkins/Winstone has problems with IPv6 Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html war/pom.xml http://jenkins-ci.org/commit/jenkins/f79f53ffbdff78c8bb4fefb51c6acbb3f266001b Log: FIXED JENKINS-14452 Integrated the fix made in Winstone. 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-15708) Xcode Plugin not expanding $(SRCROOT) variable
David Howell resolved JENKINS-15708 as Not A Defect Xcode Plugin not expanding $(SRCROOT) variable Sorry - now see that this was an issue with my Xcode project and the plist.info settings Change By: David Howell (02/Nov/12 10:52 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15709) ArtifactDeployer does not appear in Flexible Publish
Mark Ribau created JENKINS-15709 ArtifactDeployer does not appear in Flexible Publish Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: artifactdeployer, flexible-publish Created: 03/Nov/12 2:04 AM Description: Steps to reproduce: In post-build Actions, add a Flexible Publish action. In the Flexible Publish action's Action field, open the drop down. Result: Artifact Deployer action is not listed. Expected: Artifact Deployer action is listed. Project: Jenkins Priority: Major Reporter: Mark Ribau 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
