Re: JMS Restart
Please help it is really urgent -- View this message in context: http://jenkins.361315.n4.nabble.com/JMS-Restart-tp4665741p4665833.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-16361) @Grab Grape support
Justin Ryan commented on JENKINS-16361 @Grab Grape support Let's leave this open until after it's documented. I just started using this feature today, so give me a few days to clean it up to be used as an example. Thanks for adding the page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extensible-choice-parameter] (JENKINS-17875) Make Jenkins environment variables available to dynamic providers
mirumpf commented on JENKINS-17875 Make Jenkins environment variables available to dynamic providers We have a large list of projects (with role strategy plugin which makes assigns a LDAP role to projects with a certain prefix): LDAP: ROLE_PREFIX1 prefix1-projA-trunk prefix1-projA-branchI prefix1-projA-branchII prefix1-projA-branchIII prefix1-projB-trunk prefix1-projB-branchI prefix1-projB-branchII prefix1-projB-branchIII LDAP: ROLE_PREFIX2 prefix2-projA-trunk prefix2-projA-branchI prefix2-projA-branchII prefix2-projA-branchIII prefix2-projB-trunk prefix2-projB-branchI prefix2-projB-branchII prefix2-projB-branchIII For those project groups I now want to create an admin job for each prefix: prefix1-admin-create-branch-job prefix2-admin-create-branch-job Those admin jobs share the same System Groovy script CreateBranchJobFromTrunk.groovy, which clones a job and modifies the Subversion URL and the Sonar branch name. The admin job is configured to have an Extensible Choice Parameter system Groovy script provider. The system Groovy script collects all jobs with the same prefix as the admin job itself and with a "trunk" suffix. For example: The "prefix1-admin-create-branch-job" collects the two projects "prefix1-projA-trunk" and "prefix1-projB-trunk". Having the job name available in the System Groovy List Provider we could just clone the "prefix1-admin-create-branch-job" for new prefixes "prefix3" ... "prefixN" without having to worry that the prefix does not match. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extensible-choice-parameter] (JENKINS-17875) Make Jenkins environment variables available to dynamic providers
mirumpf edited a comment on JENKINS-17875 Make Jenkins environment variables available to dynamic providers We have a large list of projects (with role strategy plugin which assigns a LDAP role to projects with a certain prefix): LDAP: ROLE_PREFIX1 prefix1-projA-trunk prefix1-projA-branchI prefix1-projA-branchII prefix1-projA-branchIII prefix1-projB-trunk prefix1-projB-branchI prefix1-projB-branchII prefix1-projB-branchIII LDAP: ROLE_PREFIX2 prefix2-projA-trunk prefix2-projA-branchI prefix2-projA-branchII prefix2-projA-branchIII prefix2-projB-trunk prefix2-projB-branchI prefix2-projB-branchII prefix2-projB-branchIII For those project groups I now want to create an admin job for each prefix: prefix1-admin-create-branch-job prefix2-admin-create-branch-job Those admin jobs share the same System Groovy script CreateBranchJobFromTrunk.groovy, which clones a job and modifies the Subversion URL and the Sonar branch name. The admin job is configured to have an Extensible Choice Parameter system Groovy script provider. The system Groovy script collects all jobs with the same prefix as the admin job itself and with a "trunk" suffix. For example: The "prefix1-admin-create-branch-job" collects the two projects "prefix1-projA-trunk" and "prefix1-projB-trunk". Having the job name available in the System Groovy List Provider we could just clone the "prefix1-admin-create-branch-job" for new prefixes "prefix3" ... "prefixN" without having to worry that the prefix does not match. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Alex Ouzounis commented on JENKINS-17831 Update to latest xTrigger all jobs dependant of ivy trigger are now failling to load when using 0.26 Debugging information reference : ../../filePathFactory class : org.jenkinsci.plugins.ivytrigger.util.PropertiesFileContentExtractor required-type : org.jenkinsci.plugins.ivytrigger.util.PropertiesFileContentExtractor converter-type : hudson.util.RobustReflectionConverter path: /project/triggers/org.jenkinsci.plugins.ivytrigger.IvyTrigger/propertiesFileContentExtractor/filePathFactory line number : 68 class[1]: org.jenkinsci.plugins.ivytrigger.IvyTrigger class[2]: java.util.Vector converter-type[1] : hudson.util.RobustCollectionConverter class[3]: hudson.model.FreeStyleProject version : null --- at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:57) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) 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:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061) at hudson.util.XStream2.unmarshal(XStream2.java:109) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:925) at hudson.XmlFile.read(XmlFile.java:143) ... 10 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For
[JIRA] [build-flow] (JENKINS-17906) Executor dies because of AssertionError
Adam Andrzejewski edited a comment on JENKINS-17906 Executor dies because of AssertionError upgrade to 1.514 did not fix 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: JMS Restart
Try adding the following line to the start of the shell used in Step 3 BUILD_ID=dontKillMe please see the following page for some info: https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller On Fri, May 10, 2013 at 8:24 AM, tushanka wrote: > Please help it is really urgent > > > > -- > View this message in context: > http://jenkins.361315.n4.nabble.com/JMS-Restart-tp4665741p4665833.html > Sent from the Jenkins issues mailing list archive at Nabble.com. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Issues" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-issues+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactory] (JENKINS-17905) how to create a maven projectto download files from maven repository.and also how to use POM.xml.
haritha chundu started work on JENKINS-17905 how to create a maven projectto download files from maven repository.and also how to use POM.xml. Change By: haritha chundu (10/May/13 11:07 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactory] (JENKINS-17905) how to create a maven projectto download files from maven repository.and also how to use POM.xml.
haritha chundu stopped work on JENKINS-17905 how to create a maven projectto download files from maven repository.and also how to use POM.xml. Change By: haritha chundu (10/May/13 11:07 AM) Status: In Progress 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clone-workspace] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Chris Z commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel Hi, our team also started to get this kind of error after upgrading subversion plugin from 1.34 to 1.45, jenkins version 1.505 java jvm: hotspot, jre: 1.6.0_22 And this is strange that this started to show up after subversion plugin update. This is not showing on testing jenkins where subversion plugin was 1.40 and was updated to 1.45 and everything works fine there. FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:672) at hudson.FilePath.act(FilePath.java:893) at hudson.FilePath.act(FilePath.java:877) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1575) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) May 10, 2013 1:09:25 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel slave_server java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-15136) Support for "Poll on Master" for git SCM plugin
Mark Waite resolved JENKINS-15136 as Fixed Support for "Poll on Master" for git SCM plugin Fast remote polling resolves this request. The "git ls-remote" command is used to implement the polling without requiring a clone of the repository on the master. Change By: Mark Waite (10/May/13 11:30 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-15136) Support for "Poll on Master" for git SCM plugin
Mark Waite closed JENKINS-15136 as Fixed Support for "Poll on Master" for git SCM plugin Fast remote polling resolves this request Change By: Mark Waite (10/May/13 11:31 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite
updated JENKINS-16941
Git publisher post build action fails on slave agent - unable to serialize
Change By:
Mark Waite
(10/May/13 11:39 AM)
Description:
Using the git plugin to publish a merged change to a central repository previously was successful from either the master node or a slave agent. With the 1.2.0 (and 1.3.0) version of the git plugin it is no longer able to push changes to the central repository after they have merged and are successfully built on the slave.
The merge still works as expected when performed on the master node.
The stack trace reports:Commencing build of Revision 363396d76a09a12a2f4b5d94fb4e9981e05ad4a9 (origin/proposals)hudson.util.IOException2: remote file operation failed: /var/lib/jenkins/mwaite6-slave/workspace/merge-proposals at hudson.remoting.Channel@4a6ecaf9:fc-agile-2011 at hudson.FilePath.act(FilePath.java:848) at hudson.FilePath.act(FilePath.java:834) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1133) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495) at hudson.model.Run.execute(Run.java:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237)Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@7c0a37f8 at hudson.remoting.UserRequest.serialize(UserRequest.java:166) at hudson.remoting.UserRequest.(UserRequest.java:62) at hudson.remoting.Channel.call(Channel.java:671) at hudson.FilePath.act(FilePath.java:841) ... 10 moreCaused by: java.io.NotSerializableException: hudson.model.FreeStyleBuild at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1180) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) ... 13 moreSteps to recreate the problem: - configure a Git repository into which the Jenkins user can push changes - create a "master" branch and a "proposals" branch on the Git repository - define a Jenkins job which clones the Git repository with ssh protocol - configure the Jenkins job git plugin to merge from "*/proposals" and "*/master" to "master-proposals" - restrict the job to execute on any node except master node ("!master") - define a post build action to push the resulting merge to the origin/master branch - Submit a change to the central git repository on the "proposals" branch - Run the Jenkins job to confirm it will combine the master and proposals branches - Confirm the Jenkins job fails to push the combined change = Serialization exception between master and slave.Refer to merge-proposals.xml for the job definition I used in my tests.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-i
[JIRA] [git] (JENKINS-11645) git plugin is extremely slow creating a clone - takes 5-8 minutes in jenkins job
Mark Waite resolved JENKINS-11645 as Cannot Reproduce git plugin is extremely slow creating a clone - takes 5-8 minutes in jenkins job I don't think there is much hope of duplicating this issue 18 months after it was reported. I didn't see this problem even back when it was reported (as far as I can recall). The Git plugin has been through major revisions since the bug was first reported. It still uses the same basic mechanism for cloning as it did at the time this bug was reported, and it still has many hundreds of users on Debian machines. If the original submitter can still duplicate the bug, hopefully they can provide additional information on how to configure a system that will show the bug. Change By: Mark Waite (10/May/13 11:44 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Jenkins multi project multi platform system
I believed that Jenkins could make auto build/test easier, so I spent over a month to customize the right jobs/configurations/plugins to build and test our c++ code base (I am talking about 700k lines of C++ cross platform applications using Qt/Coin), this is more than 10 libraries, 5 applications, six platforms, and loads of tests of different types, but now I face too many difficulties, mainly: 1. I am using Matrix jobs to build on different platforms (Console/GUI/Win32/Win64/Linux/Mac). If one configuration is taking long time (e.g. GUI) then all other configurations will wait before triggering the next downstream job (e.g. Console that triggers later more tests), this is causing the build process after each commit to take far longer 2. If a single commit involved files of two different libraries, in two different Jenkins jobs, I found no way to trigger the upstream job first, so Jenkins could randomly trigger the downstream job first, which will get built using out of date files for the other job, hence building all other jobs and call all other tests for half baked unfinished code, a mix that should not exist, this leads to too many temporary unjustified failures until the upstream job is triggered 3. Although there are many ways of showing results on dashboards, I found no simple way of showing latest up to date results, I believe it is better for a job shown as passed to be shown in different status if another upstream job is running I spent the last week trying to find plugins or any solution to the above issues but failed, and I do not want to regret the very long time and resources I spent to move to Jenkins Any help is highly appreciated and thanks in advance -- View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-multi-project-multi-platform-system-tp4665852.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [github-oauth] (JENKINS-17916) NullPointerException when GitHub OAuth Plugin is used
cliffano created JENKINS-17916 NullPointerException when GitHub OAuth Plugin is used Issue Type: Bug Assignee: Sam Kottler Components: github-oauth Created: 10/May/13 11:49 AM Description: Using Jenkins 1.514 and GitHub OAuth Plugin 0.13.1 I've configured Jenkins to use Github Authentication Plugin security realm and I try to use Jenkins API token to authenticate, I got this stack trace: NullPointerException: java.lang.NullPointerException at org.jenkinsci.plugins.GithubSecurityRealm.loadGroupByGroupname(GithubSecurityRealm.java:459) at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:428) at hudson.model.User.impersonate(User.java:256) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:52) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) According to this wiki page, any security realm used should work seamlessly with basic auth. https://wiki.jenkins-ci.org/display/JENKINS/Authenticating+scripted+clients Project: Jenkins Priority: Major Reporter: cliffano This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nodeofflinenotification] (JENKINS-17917) Global configration of Node Offline Email doesn't work
Walter Kacynski created JENKINS-17917 Global configration of Node Offline Email doesn't work Issue Type: Bug Assignee: Unassigned Components: nodeofflinenotification Created: 10/May/13 12:31 PM Description: When I specify an email in the global Jenkins configuration under "Global Properties" the value seems to have NO effect when any slave or the master goes offline. I ONLY get email notification when the notification has been configured at the slave level. Project: Jenkins Priority: Minor Reporter: Walter Kacynski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nodeofflinenotification] (JENKINS-17917) Global configration of Node Offline Email doesn't work
Walter Kacynski assigned JENKINS-17917 to Jens Christensen Global configration of Node Offline Email doesn't work Change By: Walter Kacynski (10/May/13 12:34 PM) Assignee: Jens Christensen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
David Ehrenberger commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly FYI I downgraded to 1.513 and am still seeing the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: JMS Restart
Dear Geoff , Thanks a lot for your reply. I added this above the script and tried ...got same error between the script ...got same error and after the script ...got same error cd /opt/app/documentum/share/jboss4.3.0/server nohup ./startMethodServer.sh i dnt have any idea how to proceed. -- View this message in context: http://jenkins.361315.n4.nabble.com/JMS-Restart-tp4665741p4665857.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17918) SEVERE: Error while serving http://jxxxxxxx/computer/api/xml
Ohad Basan created JENKINS-17918 SEVERE: Error while serving http://jxxx/computer/api/xml Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 10/May/13 1:05 PM Description: Repeating exceptions appearing on jenkins.log SEVERE: Error while serving http://jenkins.eng.lab.tlv.redhat.com/computer/api/xml java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor641.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winsto
[JIRA] [core] (JENKINS-17918) SEVERE: Error while serving http://jxxxxxxx/computer/api/xml
Ohad Basan updated JENKINS-17918 SEVERE: Error while serving http://jxxx/computer/api/xml Change By: Ohad Basan (10/May/13 1:06 PM) Description: Repeating exceptions appearing on jenkins.logSEVERE: Error while serving http:// jenkins xxx . eng.lab.tlv.redhat. com/computer/api/xmljava.lang.reflect.InvocationTargetExceptionat sun.reflect.GeneratedMethodAccessor641.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)at java.lang.reflect.Method.invoke(Method.java:597)at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487)at org.kohsuke.stapler.Stapler.service(Stapler.java:164)at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)at winstone.FilterConfiguration.execute(FilterConfigu
[JIRA] [mercurial] (JENKINS-9686) Mercurial polling does not expand parameters/tokens
Marc Swingler commented on JENKINS-9686 Mercurial polling does not expand parameters/tokens Thanks for looking into it Jesse. I've just updated to 1.514 and latest for my installed plugins. I'll see if the issue is still reproducible early next week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-17467) CoverityPublisher aborted due to NullPointerException
Kyle O'Connor updated JENKINS-17467 CoverityPublisher aborted due to NullPointerException Change By: Kyle O'Connor (10/May/13 2:13 PM) Affects Version/s: current Environment: jenkins 1.509 .1 LTS , coverity plugin 1.2. 0 2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-17467) CoverityPublisher aborted due to NullPointerException
Kyle O'Connor
commented on JENKINS-17467
CoverityPublisher aborted due to NullPointerException
ERROR: Publisher jenkins.plugins.coverity.CoverityPublisher aborted due to exception
java.lang.NullPointerException
at jenkins.plugins.coverity.CoverityPublisher.perform(CoverityPublisher.java:248)
at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724)
at hudson.model.Run.execute(Run.java:1600)
at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:237)
Clearly a simple NPE at line 248 of CoverityPublisher because you moved this block of code
-if(invocationAssistance.getSaOverride() != null) {
- home = new CoverityInstallation(invocationAssistance.getSaOverride()).forEnvironment(build.getEnvironment(listener)).getHome();
-}
out from underneath the check for
if(invocationAssistance != null) {
at line 265.
This prevents me from using the plugin at all and fails all my builds. I'll put in a ticket with Coverity support as well hoping to get this fixed ASAP.
Thanks.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17900) subversion credentials are not stored in hudson.scm.SubversionSCM.xml
Duncan Tincello
commented on JENKINS-17900
subversion credentials are not stored in hudson.scm.SubversionSCM.xml
I have the same issue. I found a way of working around this problem:
Use the command line SVN settings in ~/.subversion/servers as described in http://svnbook.red-bean.com/en/1.6/svn-book.html#svn.serverconfig.httpd.ssl.client
Test this with the Subversion command line, e.g. svn info .
Jenkins now checks the repository URL ("https://...") when you type it into the job configuration, and finds that the connection is working, so it does not prompt you for credentials.
Works for me on Ubuntu 10.04.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-17919) TFS plugin throws an exception when parsing a change set
Guillaume Lemay created JENKINS-17919 TFS plugin throws an exception when parsing a change set Issue Type: Bug Affects Versions: current Assignee: redsolo Attachments: consoleText Components: tfs Created: 10/May/13 3:13 PM Description: TFS Plugin gives and error while parsing the changeset. I get the same error for all projects built from this machine. Tried with projects both on TFS 2008 and TFS 2010. Note that the build server is a Windows XP French machine and that the installed Visual Studio and tools are also in French. I tried changing the region on the build server to English (US) or French (Canada), but neither work. I've also attached the full build log. FATAL: Parse error. Unable to find an item within a changeset. Please report this as a bug. Changesetdata = " --- Ensemble de modifications: 2561 Utilisateur: CN1215 Date: Friday, May 10, 2013 10:58:48 AM Commentaire : Pointer sur les DLL locales Éléments : modifier $/Ordonnancement(TE)/Source/Client/HQActions/HQActions.csproj modifier $/Ordonnancement(TE)/Source/Client/HQForms/HQForms.csproj Notes d'archivage : Vérificateur de code : Vérificateur de la sécurité : Vérificateur des performances : ". Environment: Windows XP SP3, .Net 4, TFS 2010 and TFS 2008 Project: Jenkins Priority: Major Reporter: Guillaume Lemay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17563) java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory)
Christopher Prosser commented on JENKINS-17563 java.io.FileNotFoundException: Engineering/iOS/UScapeIt/UScapeIt.app.ipa (No such file or directory) My team just started getting this too. Had been working pretty much flawlessly since last November. Updated to latest jenkins plugin to no avail. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [checkstyle] (JENKINS-17920) Checkstyle and FindBugs uninstallable after upgrade
Whitney Marshall created JENKINS-17920 Checkstyle and FindBugs uninstallable after upgrade Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: checkstyle Created: 10/May/13 4:18 PM Description: I cannot install either Checkstyle or FindBugs after upgrading a 1.434 installation to 1.514. Failure continues even after wiping out the $JENKINS_HOME/war directory and starting fresh. What I have not tried is wiping out the plugins directory (because I don't want to have to reinstall all my working plugins). I get the following stack trace on startup, after downloading e.g. checkstyle. SEVERE: Failed Loading plugin checkstyle hudson.util.IOException2: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:371) at hudson.PluginManager$2$1$1.run(PluginManager.java:334) 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:893) 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(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V at org.apache.commons.logging.impl.SLF4JLocationAwareLog.error(SLF4JLocationAwareLog.java:225) at org.apache.commons.digester.Digester.endElement(Digester.java:1350) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1916) at hudson.plugins.checkstyle.rules.CheckStyleRules.initialize(CheckStyleRules.java:60) at hudson.plugins.checkstyle.CheckStylePlugin.start(CheckStylePlugin.java:14) at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:379) at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:368) ... 9 more Environment: Windows XP Project: Jenkins Labels: plugin Priority: Minor Reporter: Whitney Marshall This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups
[JIRA] [checkstyle] (JENKINS-17920) Checkstyle and FindBugs uninstallable after upgrade
Whitney Marshall
updated JENKINS-17920
Checkstyle and FindBugs uninstallable after upgrade
Change By:
Whitney Marshall
(10/May/13 4:20 PM)
Description:
I cannot install either Checkstyle or FindBugs after upgrading a 1.434 installation to 1.514. Failure continues even after wiping out the $JENKINS_HOME/war directory and starting fresh. What I have not tried is wiping out the plugins directory (because I don't want to have to reinstall all my working plugins).I get the following stack trace on startup, after downloading e.g. checkstyle.
{noformat}
SEVERE: Failed Loading plugin checkstylehudson.util.IOException2: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:371) at hudson.PluginManager$2$1$1.run(PluginManager.java:334) 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:893) 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(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V at org.apache.commons.logging.impl.SLF4JLocationAwareLog.error(SLF4JLocationAwareLog.java:225) at org.apache.commons.digester.Digester.endElement(Digester.java:1350) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1916) at hudson.plugins.checkstyle.rules.CheckStyleRules.initialize(CheckStyleRules.java:60) at hudson.plugins.checkstyle.CheckStylePlugin.start(CheckStylePlugin.java:14) at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:379) at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:368) ... 9 more
{noformat}
Jenkins version: 1.514Checkstyle plugin: 3.35
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [checkstyle] (JENKINS-17920) Checkstyle and FindBugs uninstallable after upgrade
Whitney Marshall updated JENKINS-17920 Checkstyle and FindBugs uninstallable after upgrade Change By: Whitney Marshall (10/May/13 4:19 PM) Description: I cannot install either Checkstyle or FindBugs after upgrading a 1.434 installation to 1.514. Failure continues even after wiping out the $JENKINS_HOME/war directory and starting fresh. What I have not tried is wiping out the plugins directory (because I don't want to have to reinstall all my working plugins).I get the following stack trace on startup, after downloading e.g. checkstyle.SEVERE: Failed Loading plugin checkstylehudson.util.IOException2: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:371) at hudson.PluginManager$2$1$1.run(PluginManager.java:334) 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:893) 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(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V at org.apache.commons.logging.impl.SLF4JLocationAwareLog.error(SLF4JLocationAwareLog.java:225) at org.apache.commons.digester.Digester.endElement(Digester.java:1350) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1916) at hudson.plugins.checkstyle.rules.CheckStyleRules.initialize(CheckStyleRules.java:60) at hudson.plugins.checkstyle.CheckStylePlugin.start(CheckStylePlugin.java:14) at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:379) at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:368) ... 9 more Jenkins version: 1.514Checkstyle plugin: 3.35 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [checkstyle] (JENKINS-17920) Checkstyle and FindBugs uninstallable after upgrade
Whitney Marshall commented on JENKINS-17920 Checkstyle and FindBugs uninstallable after upgrade I see a similar stack trace for findbugs (version 4.48), with a NoSuchMethodException for the exact same method: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: JMS Restart
hmm... did you have the & after the nohup ./startMethodServer.sh does it start and then stop the server, or does the job just hang? try putting just this in the Execute Shell build step: #! /bin/bash export BUILD_ID=dontKillMe cd /opt/app/documentum/share/jboss4.3.0/server nohup ./startMethodServer.sh & I have just noticed, you might be better asking the question to * jenkinsci-us...@googlegroups.com* List details on the following page http://jenkins-ci.org/content/mailing-lists On Fri, May 10, 2013 at 1:46 PM, tushanka wrote: > Dear Geoff , > > Thanks a lot for your reply. > I added this above the script and tried ...got same error > between the script ...got same error > and after the script ...got same error > > cd /opt/app/documentum/share/jboss4.3.0/server > nohup ./startMethodServer.sh > > > i dnt have any idea how to proceed. > > > > -- > View this message in context: > http://jenkins.361315.n4.nabble.com/JMS-Restart-tp4665741p4665857.html > Sent from the Jenkins issues mailing list archive at Nabble.com. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Issues" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-issues+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
Brent Atkinson commented on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content I ended up patching the jenkins fork of svnkit locally, building the subversion-plugin 1.45 with the patched version of svnkin. It does indeed appear to fix the behavior. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17116) gracefull job termination
owenmehegan commented on JENKINS-17116 gracefull job termination This may explain a problem I've been seeing. When a user cancels a build while a Ruby 'bundle install' operation is happening, the job exits but the bundle process goes into a zombie-ish state (not literally a zombie process but it never exits), no longer a child of the Jenkins process. I have to kill it manually, and sometimes it freaks out and consumes a lot of resources on the box as well. I'm not sure if we need a bigger/different hammer here, or what. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jiratestresultreporter] (JENKINS-17921) JiraTestResultReporter plugin does not handle carriage returns in test output
Richard Fuchs created JENKINS-17921 JiraTestResultReporter plugin does not handle carriage returns in test output Issue Type: Bug Assignee: Unassigned Attachments: JiraReporter.java Components: jiratestresultreporter Created: 10/May/13 5:28 PM Description: Using the google C++ test framework, I inserted a failure case into the supplied test cases to trigger a JIRA issue to be created. [--] 2 tests from SkipPrefixTest [ RUN ] SkipPrefixTest.SkipsWhenPrefixMatches [ OK ] SkipPrefixTest.SkipsWhenPrefixMatches (0 ms) [ RUN ] SkipPrefixTest.DoesNotSkipWhenPrefixDoesNotMatch ..\test\gtest_unittest.cc(7337): error: Value of: 1 Expected: 0 [ FAILED ] SkipPrefixTest.DoesNotSkipWhenPrefixDoesNotMatch (0 ms) [--] 2 tests from SkipPrefixTest (0 ms total) Because there are carriage returns in the output, when the json payload is created, these control characters are not escaped, so JIRA does not accept the input. Also, I was having serialization issues when I first installed the plugin and these were resolved by removing the use of the workspace. I can't reproduce the errors now, so I didn't create a separate issue for it. The attached file is what I'm using to strip out the control characters. Project: Jenkins Priority: Major Reporter: Richard Fuchs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-16280) EC2 Plugin will not build Java projects.
Joseph Lawson commented on JENKINS-16280 EC2 Plugin will not build Java projects. I hit this error as well and resolved it by making sure Remote FS root is set. (it is /tmp by default so you can try 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sctmexecutor] (JENKINS-17922) SCTM Executor plugin Class loading issue when running jenkins on JBoss AS 5 (
JJ Weaver created JENKINS-17922 SCTM Executor plugin Class loading issue when running jenkins on JBoss AS 5 ( Issue Type: Bug Affects Versions: current Assignee: Sebastian Kornexl Attachments: exception.txt Components: sctmexecutor Created: 10/May/13 7:26 PM Description: Created attachment 230728 [details] Exception thrown when loading axis libs Running Jenkins 1.452 with SCTMExecutor 1.5.1 on top of JBoss AS 5 http://wiki.hudson-ci.org/display/HUDSON/SCTMExecutor The plugin fails to execute due to a class loading issue. The issue deals with the axis jars and the javax/xml/namespace/QName class. I have tried completely removing the class from the jar and moving them to the shared JBoss lib directory. So far I haven't had any luck. Your help is appreciated. javax.servlet.ServletException: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.apache.axis.message.MessageElement.getChildElements(Ljavax/xml/namespace/QName;)Ljava/util/Iterator;" the class loader (instance of java/net/URLClassLoader) of the current class, org/apache/axis/message/MessageElement, and the class loader (instance of ) for interface javax/xml/soap/SOAPElement have different Class objects for the type javax/xml/namespace/QName used in the signature Environment: Linux jenkins 2.6.32-220.17.1.el6.x86_64 #1 SMP Thu Apr 26 13:37:13 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux Jenkins 1.452 JBoss AS 5 Project: Jenkins Priority: Blocker Reporter: JJ Weaver This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-5724) Choosing what to build is slow when using a lot of branches.
Jonathan Rogers commented on JENKINS-5724 Choosing what to build is slow when using a lot of branches. This remains a big problem for anyone with a large number of branches. I eventually abandoned the git plugin entirely in favor of custom scripts to handle checkouts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Luiz Casey commented on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL So is this fix in the latest release 1.45 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17923) ComException thrown from ActiveDirectoryAuthenticationProvider constructor
Jesse Glick created JENKINS-17923 ComException thrown from ActiveDirectoryAuthenticationProvider constructor Issue Type: Bug Assignee: Unassigned Attachments: error.txt Components: active-directory Created: 10/May/13 8:07 PM Description: Excerpt from error screen: com4j.ExecutionException: com4j.ComException: 8007054b Failed to MkParseDisplayName : The specified domain either does not exist or could not be contacted. : .\com4j.cpp:217 at com4j.ComThread.execute(ComThread.java:203) at com4j.Task.execute(Task.java:25) at com4j.COM4J.getObject(COM4J.java:256) at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.(ActiveDirectoryAuthenticationProvider.java:46) Installed Jenkins 1.509.1 service on a fresh Windows Server 2012 installation and tried turning on AD authentication. No idea if an AD server was even running, but I should be allowed to experiment right? Instead I got this error when I pressed Save from the security configuration screen, which is not very friendly. Should rather show an error in form validation etc. Not even sure why these calls are being done from the constructor; seems to be unused except for logging. Project: Jenkins Labels: exception Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-3002) TFS Support to get labels
Jorge Villarroel commented on JENKINS-3002 TFS Support to get labels Hi, I try to compile the Code avaliable at: http://github.com/kopcheski/tfs-plugin but appears this error: \tfs-plugin-master\src\main\java\hudson\plugins\tfs\TeamFoundationServerScm.java:[59,7] hudson.plugins.tfs.TeamFoundationServerScm is not abstract and does not override abstract method compareRemoteRevisionWith(hudson.model.AbstractProject,hudson.Launcher,hudson.FilePath,hudson.model.TaskListener,hudson.scm.SCMRevisionState) in hudson.scm.SCM \tfs-plugin-master\src\main\java\hudson\plugins\tfs\TeamFoundationServerScm.java:[291,4] method does not override or implement a method from a supertype This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-3002) TFS Support to get labels
Jorge Villarroel commented on JENKINS-3002 TFS Support to get labels Is it possible to get the hpi file for this update? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17924) Matrix jobs should be able to checkout a repository just once
Emanuel Andrada created JENKINS-17924 Matrix jobs should be able to checkout a repository just once Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core, matrix Created: 10/May/13 8:38 PM Description: Matrix jobs with custom workspaces should be able to checkout/clone the repository just once and then copy it to the axis-specific directories, to avoid several checkouts the very first time the project is built, as the first checkout is the heavier download. Project: Jenkins Labels: matrix Priority: Major Reporter: Emanuel Andrada This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-17911) StyleCop parser not displayed dispite violations plugin being installed
Michael Fowler closed JENKINS-17911 as Fixed StyleCop parser not displayed dispite violations plugin being installed Change By: Michael Fowler (10/May/13 8:46 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-17925) StyleCop Parser Fails with Exception: Content is not allowed in prolog
Michael Fowler created JENKINS-17925 StyleCop Parser Fails with Exception: Content is not allowed in prolog Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Attachments: buildLog.txt Components: warnings Created: 10/May/13 8:54 PM Description: [WARNINGS] Parsing warnings in console log with parser StyleCop ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception hudson.util.IOException2: Content is not allowed in prolog. at hudson.plugins.violations.types.stylecop.StyleCopParser.parse(StyleCopParser.java:69) at hudson.plugins.warnings.parser.ViolationsAdapter.parse(ViolationsAdapter.java:60) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:313) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:292) at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:392) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:318) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:331) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724) at hudson.model.Run.execute(Run.java:1600) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) at hudson.plugins.violations.types.stylecop.StyleCopParser.parse(StyleCopParser.java:53) ... 15 more Environment: Win 2k8 x64 Project: Jenkins Priority: Major Reporter: Michael Fowler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-16361) @Grab Grape support
Justin Ryan resolved JENKINS-16361 as Fixed @Grab Grape support Change By: Justin Ryan (10/May/13 9:52 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-17467) CoverityPublisher aborted due to NullPointerException
Josh Vinson started work on JENKINS-17467 CoverityPublisher aborted due to NullPointerException Change By: Josh Vinson (10/May/13 9:59 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-17467) CoverityPublisher aborted due to NullPointerException
Josh Vinson resolved JENKINS-17467 as Fixed CoverityPublisher aborted due to NullPointerException Fixed. Thanks for pointing this out! Change By: Josh Vinson (10/May/13 10:00 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-3002) TFS Support to get labels
Vinicius Kopcheski commented on JENKINS-3002 TFS Support to get labels Hi, Jorge. As Jenkins is now compiled with JDK7 the tfs-plugin can't compile anymore with its current dependencies (just noticed that because of buildhive). It happens because org.jvnet.hudson.plugins:plugin. Even its latest version has the same problem. Now, with org.jenkins-ci.plugins:plugin we have a couple of new methods to be implemented in TeamFoundationServerScm class. Still don't know how to implement them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [global-variable-string-parameter] (JENKINS-17926) one job build by passing env to ant QA, STAGE, DEV, PROD to build for the giving parameters.
ayman mousa created JENKINS-17926 one job build by passing env to ant QA, STAGE, DEV, PROD to build for the giving parameters. Issue Type: Bug Assignee: Unassigned Components: global-variable-string-parameter Created: 10/May/13 10:55 PM Description: Hi I am running jenkins on a windows 2008 and have setup JDK, tomcat and ant. Created a new project and pulled the source from perforce. I have one admin.property file that is being ignored from being synced. I am using parabuild tool which allows me to setup build parameters such env = qa, dev, stage, prod. when I execute and invoke ant it will pass the parameter to the ant command for which environments build for this is what i use in parabuild set JAVA_HOME=C:\Program Files\Java\jdk1.6.0_21 set TOMCAT_HOME=C:\opt\apache-tomcat-6.0.29 call ant -Ddeployment-env=%ENV% -Dtomcat.home=%TOMCAT_HOME% clean package note the env is already setup qa, dev, stage, prod. like to know using one JOB in Jenkins how can i use this method? Due Date: 10/May/13 12:00 AM Environment: dev, qa, stageqa, and prod Project: Jenkins Priority: Blocker Reporter: ayman mousa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-16280) EC2 Plugin will not build Java projects.
Francis Upton resolved JENKINS-16280 as Not A Defect EC2 Plugin will not build Java projects. This does not sound like a bug, if you still think it is, please provide more information and reopen it. Change By: Francis Upton (10/May/13 11:07 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17923) ComException thrown from ActiveDirectoryAuthenticationProvider constructor
SCM/JIRA link daemon commented on JENKINS-17923 ComException thrown from ActiveDirectoryAuthenticationProvider constructor Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/plugins/active_directory/ActiveDirectoryAuthenticationProvider.java src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java src/main/resources/hudson/plugins/active_directory/ActiveDirectorySecurityRealm/config.jelly http://jenkins-ci.org/commit/active-directory-plugin/fbe42164339e5e399de5b8f37a328dbdabd64809 Log: [FIXED JENKINS-17923] added form validation check to the ADSI codepath. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17923) ComException thrown from ActiveDirectoryAuthenticationProvider constructor
SCM/JIRA link daemon resolved JENKINS-17923 as Fixed ComException thrown from ActiveDirectoryAuthenticationProvider constructor Change By: SCM/JIRA link daemon (11/May/13 12:23 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extensible-choice-parameter] (JENKINS-17875) Make Jenkins environment variables available to dynamic providers
ikedam commented on JENKINS-17875 Make Jenkins environment variables available to dynamic providers Thanks for details. So the points are: Job names are used as an access control. Users shouldn't copy jobs that they are not allowed to access to. I agree that the best way is to use a job name in a groovy script for this case. But as mentioned before, there seems no proper way to access the job information from ParameterDefinition... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17927) hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem
ben patterson created JENKINS-17927 hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkinshttp500.png, morestacktrace.txt Components: core, maven2 Created: 11/May/13 3:04 AM Description: Upgraded to latest Jenkins from 1.489. We have a number of plugins including maven-plugin installed. For unauthenticated users, we get an http500 error within the default view. I would attempt to disable the Maven plugin to see if I can get rid of the error, but it is considered part of Maven core. Partial Stacktrace here. Attaching screenshot and more of the stacktrace. Exception: org.apache.commons.jelly.JellyTagException: jar:file:/usr/local/jboss-4.2.3.GA/server/production/tmp/deploy/tmp2463229018850549093hudson-exp.war/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/model/View/index.jelly:44:43: org.apache.commons.jelly.JellyTagException: jar:file:/usr/local/jboss-4.2.3.GA/server/production/tmp/deploy/tmp2463229018850549093hudson-exp.war/WEB-INF/lib/jenkins-core-1.514.jar!/lib/hudson/projectView.jelly:63:22: hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/usr/local/jboss-4.2.3.GA/server/production/tmp/deploy/tmp2463229018850549093hudson-exp.war/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/model/View/index.jelly:44:43: org.apache.commons.jelly.JellyTagException: jar:file:/usr/local/jboss-4.2.3.GA/server/production/tmp/deploy/tmp2463229018850549093hudson-exp.war/WEB-INF/lib/jenkins-core-1.514.jar!/lib/hudson/projectView.jelly:63:22: hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:736) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) Environment:
