[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
akiko_pusu commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity Dale, thank you for your information. My Jenkins is running on CentOS, installed via RPM package. So, I'm try to modify init script and going to report the result. 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-20682) Starting Jenkins with defined --webroot or JETTY_HOME not working.
Stefan Brausch commented on JENKINS-20682 Starting Jenkins with defined --webroot or JETTY_HOME not working. Agree Ben, this it's a big problem. Icons are missing and slaves couldn't start automatically, slave.jar is also missing. /tmp is really a bad place for the extracted war file 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-21249) Update Groovy
Daniel Spilker created JENKINS-21249 Update Groovy Issue Type: Improvement Assignee: Unassigned Components: core Created: 07/Jan/14 8:16 AM Description: Currently Jenkins uses Groovy 1.8.x. To be able to use new Groovy 2.x features in the script console or the CLI commands, the dependency to Groovy should be updated to the latest version. Project: Jenkins Priority: Major Reporter: Daniel Spilker 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-client] (JENKINS-21248) Add shallow update init for submodule
Masaki Muranaka created JENKINS-21248 Add shallow update init for submodule Issue Type: Improvement Assignee: Nicolas De Loof Components: git-client Created: 07/Jan/14 8:16 AM Description: Recent versions of cgit support shallow clone support in submodule. Like this git submodule update --init --depth 1 But it doesn't support this new feature in current version of git-client-plugin. Environment: cgit = 1.8.4 Project: Jenkins Labels: plugin git-client Priority: Minor Reporter: Masaki Muranaka 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] [build-publisher] (JENKINS-21250) NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+
Norbert Pfistner created JENKINS-21250 NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+ Issue Type: Bug Assignee: vjuranek Attachments: selenium_firefox Config [Jenkins] - Mozilla Firefox_2014-01-07_09-24-03.png Components: build-publisher Created: 07/Jan/14 8:26 AM Description: We have a job which triggers three other jobs and aggregates their test results using post build actions: Aggregate post build test results (german: "Nachgelagerte Testergebnisse zusammenfassen") x Aggregate all post build jobs x Aggregate failed build result Build jobs (german: "Weitere Projekte bauen") x trigger only on build success [ ] trigger even when build is instable [ ] trigger even when build fails When starting this job it fails quickly with an NullPointer exception: Started by user anonymous Building in workspace /ps/devop/jenkins/data/jobs/selenium_firefox/workspace ERROR: Publisher hudson.tasks.test.AggregatedTestResultPublisher aborted due to exception java.lang.NullPointerException at hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.getProject(AggregatedTestResultPublisher.java:173) at hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.init(AggregatedTestResultPublisher.java:146) at hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.init(AggregatedTestResultPublisher.java:135) at hudson.tasks.test.AggregatedTestResultPublisher.perform(AggregatedTestResultPublisher.java:90) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Finished: FAILURE The aggregation is crucial for our dashboard which displays the overall testresults history chart. P.S.: Sorry, I only use the german translation, so I just guessed the actual english configuration lables above. Project: Jenkins Priority: Blocker Reporter: Norbert Pfistner 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] [build-publisher] (JENKINS-21250) NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+
Norbert Pfistner commented on JENKINS-21250 NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+ The effected versions are 1.545 and 1.546 so far. Switching back to version 1.544 fixes the bug but is for sure no suitable solution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [build-publisher] (JENKINS-21250) NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+
vjuranek assigned JENKINS-21250 to Lucie Votypkova NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+ Change By: vjuranek (07/Jan/14 8:56 AM) Assignee: vjuranek LucieVotypkova 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] [prioritysorter] (JENKINS-21236) PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem
Magnus Sandberg commented on JENKINS-21236 PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem Now the update center for lts contains 2.4 so you should be able to install it. Please let me know if everything works for you if you encounter any issues. 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] [maven2] (JENKINS-19396) Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger
Christian Eichenberger reopened JENKINS-19396 Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger With Jenkins ver. 1.532.1, we still get too many of these entries: Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted INFO: Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted INFO: Reactor Build Order: Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted INFO: Jan 06, 2014 9:43:20 PM org.apache.maven.cli.event.ExecutionEventLogger sessionStarted INFO: Change By: Christian Eichenberger (07/Jan/14 9:10 AM) 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 -- 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-19222) Update to 1.527 breaks ${NODE_NAME} as node parameter on master
Dirk Kuypers
commented on JENKINS-19222
Update to 1.527 breaks ${NODE_NAME} as node parameter on master
Sorry for the delay, I have been on holidays.
I tried with 1.546 with my small test jobs I have attached to this ticket:
It doesn't work. JOB B states
pending #9 cancel this build (pending—All nodes of label ‘’ are offline) LabelParameterValue: HOST_NAME=
while staying in the build queue forever.
If this is only fixed in LTS with 1532.1, I have to re-test.
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-19222) Update to 1.527 breaks ${NODE_NAME} as node parameter on master
Dirk Kuypers
commented on JENKINS-19222
Update to 1.527 breaks ${NODE_NAME} as node parameter on master
Just retested with 1.532.1, same result:
pending #9 cancel this build (pending—All nodes of label ‘’ are offline) LabelParameterValue: HOST_NAME=
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] [prioritysorter] (JENKINS-21236) PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem
pedro reis commented on JENKINS-21236 PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem Hi Magnus, "stopped working" doesn't mean it shows erros, it simply isn't prioritizing anything anymore at v1.532.1. I wasn't planning using 1.532.1 yet, but the recommended wget http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war has downloaded this version, so I have trusted this! Ok, now at update center I can see 2.4, thanks. I'll give it a try. 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] [maven2] (JENKINS-19396) Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger
Daniel Beck commented on JENKINS-19396 Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger Christian Eichenberger: Update Maven Plugin to version 2.0. It's now independent of the core version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext] (JENKINS-21180) [email-ext] Attach Build Log conflicts with the ansi-color plugin
Aaron Searle commented on JENKINS-21180 [email-ext] Attach Build Log conflicts with the ansi-color plugin Jenkins in the UI offers a plain-text view of the log and a html view, in order to produce the plain-text view it must strip out/decode anything that the ansi-color plugin has put in place; so there must be a way to retrieve that. Looking at the AbstractBuild class perhaps it uses the getLogText (I have not tested this out myself). 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] [delivery-pipeline] (JENKINS-21010) Better representation of parallel stages
Patrik Boström started work on JENKINS-21010 Better representation of parallel stages Change By: Patrik Boström (07/Jan/14 10:17 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [delivery-pipeline] (JENKINS-21010) Better representation of parallel stages
Patrik Boström assigned JENKINS-21010 to Patrik Boström Better representation of parallel stages Change By: Patrik Boström (07/Jan/14 10:17 AM) Assignee: PatrikBoström 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] [prioritysorter] (JENKINS-21236) PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem
pedro reis commented on JENKINS-21236 PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem There must be some problem, because it doesn't upgrades to 2.4. 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] [delivery-pipeline] (JENKINS-21010) Better representation of parallel stages
Patrik Boström commented on JENKINS-21010 Better representation of parallel stages Have done a implementation of this in a feature branch called JENKINS-21010. https://github.com/Diabol/delivery-pipeline-plugin/tree/JENKINS-21010 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-21251) Slave channel timeout seemingly caused by usage of System.currentTimeMillis()
Ben Combrink created JENKINS-21251 Slave channel timeout seemingly caused by usage of System.currentTimeMillis() Issue Type: Bug Assignee: Unassigned Components: core Created: 07/Jan/14 11:03 AM Description: My projects run on separate slave machines/nodes. Some of these projects have testcases that change the system clock. This causes Jenkins and the slave to immediately disconnect. It always happens. I've tried to dig into it a bit and here's what I have: I'm looking at hudson.remoting.PingThread.java The timeout on the channel ping is enforced by calculating the difference between 2 counter values, each obtained with System.currentTimeMillis(). However System.currentTimeMillis() is not the right way of obtaining such counters - the values are not monotonically increasing. If wall-clock time changes for any reason (like maybe Daylight savings or a manual change) then the value returned might become smaller than a moment ago. Obtaining the counter values with System.nanoTime() would solve this. STACK TRACE below: FATAL: Unable to delete script file C:\WINDOWS\TEMP\hudson2959765976006672203.bat 00:44:00 hudson.util.IOException2: remote file operation failed: C:\WINDOWS\TEMP\hudson2959765976006672203.bat at hudson.remoting.Channel@62ec4e:UTM-RT5AUTOM027 00:44:00 at hudson.FilePath.act(FilePath.java:901) 00:44:00 at hudson.FilePath.act(FilePath.java:878) 00:44:00 at hudson.FilePath.delete(FilePath.java:1263) 00:44:00 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:101) 00:44:00 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) 00:44:00 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 00:44:00 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802) 00:44:00 at hudson.model.Build$BuildExecution.build(Build.java:199) 00:44:00 at hudson.model.Build$BuildExecution.doRun(Build.java:160) 00:44:00 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:584) 00:44:00 at hudson.model.Run.execute(Run.java:1592) 00:44:00 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 00:44:00 at hudson.model.ResourceController.execute(ResourceController.java:88) 00:44:00 at hudson.model.Executor.run(Executor.java:237) 00:44:00 Caused by: hudson.remoting.ChannelClosedException: channel is already closed 00:44:00 at hudson.remoting.Channel.send(Channel.java:494) 00:44:00 at hudson.remoting.Request.call(Request.java:129) 00:44:00 at hudson.remoting.Channel.call(Channel.java:672) 00:44:00 at hudson.FilePath.act(FilePath.java:894) 00:44:00 ... 13 more 00:44:00 Caused by: java.io.IOException: Unexpected termination of the channel 00:44:00 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) 00:44:00 Caused by: java.io.EOFException 00:44:00 at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2554) 00:44:00 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) 00:44:00 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) 00:44:00 at hudson.remoting.Command.readFrom(Command.java:92) 00:44:00 at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) 00:44:00 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 00:44:00 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel 00:44:00 hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel 00:44:00 at hudson.remoting.Request.call(Request.java:174) 00:44:00 at hudson.remoting.Channel.call(Channel.java:672) 00:44:00 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) 00:44:00 at $Proxy45.join(Unknown Source) 00:44:00 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:925) 00:44:00 at hudson.Launcher$ProcStarter.join(Launcher.java:360) 00:44:00
[JIRA] [delivery-pipeline] (JENKINS-21010) Better representation of parallel stages
Patrik Boström commented on JENKINS-21010 Better representation of parallel stages My interpretation of the requirements for this is: Show the relationship between stages. If a task in a stage triggers a task in an other stage, show that relation. If a task in a stage calls another task in the same stage, do not show that relationship. 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] [delivery-pipeline] (JENKINS-21010) Better representation of parallel stages
Patrik Boström edited a comment on JENKINS-21010 Better representation of parallel stages My interpretation of the requirements for this is: Show the relationship between stages. If a task in a stage triggers a task in an other stage, show that relation. If a task in a stage calls another task in the same stage, do not show that relationship. Is that correct? 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-21252) UnsatisfiedLinkError on Startup
Lars Wolter created JENKINS-21252 UnsatisfiedLinkError on Startup Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 07/Jan/14 11:31 AM Description: After upgrading from 1.538 - 1.546 Jenkins system log shows the following error: Jan 07, 2014 9:54:38 AM WARNING jenkins.diagnosis.HsErrPidList Failed to list up hs_err_pid files java.lang.UnsatisfiedLinkError: com.sun.jna.Native.open(Ljava/lang/String;)J at com.sun.jna.Native.open(Native Method) at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:236) at com.sun.jna.Library$Handler.init(Library.java:140) at com.sun.jna.Native.loadLibrary(Native.java:366) at com.sun.jna.Native.loadLibrary(Native.java:351) at com.sun.akuma.CLibrary.clinit(CLibrary.java:89) at com.sun.akuma.JavaVMArguments.resolvePID(JavaVMArguments.java:126) at com.sun.akuma.JavaVMArguments.ofLinux(JavaVMArguments.java:114) at com.sun.akuma.JavaVMArguments.of(JavaVMArguments.java:104) at com.sun.akuma.JavaVMArguments.current(JavaVMArguments.java:92) at jenkins.diagnosis.HsErrPidList.init(HsErrPidList.java:62) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:429) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382) at hudson.ExtensionFinder._find(ExtensionFinder.java:151) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:316) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ExtensionList.get(ExtensionList.java:129) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:899) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at
[JIRA] [email-ext] (JENKINS-14378) Email-ext plugin failed to install
Alex Earl resolved JENKINS-14378 as Cannot Reproduce Email-ext plugin failed to install Change By: Alex Earl (07/Jan/14 11:35 AM) Status: Open Resolved Resolution: CannotReproduce 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] [email-ext] (JENKINS-21246) email-ext serialises concurrent builds waiting for checkpoint
Alex Earl resolved JENKINS-21246 as Duplicate email-ext serialises concurrent builds waiting for checkpoint Change By: Alex Earl (07/Jan/14 11:38 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-17526) Broken CSS when reloading Jenkins after a time of inactivity
Kate Taylor started work on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity Change By: Kate Taylor (07/Jan/14 12:00 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-17526) Broken CSS when reloading Jenkins after a time of inactivity
Kate Taylor updated JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity Change By: Kate Taylor (07/Jan/14 12:00 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 -- 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-20682) Starting Jenkins with defined --webroot or JETTY_HOME not working.
Richard Mortimer assigned JENKINS-20682 to Kohsuke Kawaguchi Starting Jenkins with defined --webroot or JETTY_HOME not working. Assigning to Kohsuke (who made the change to Jetty) for comment. I believe that this is an unintended consequence of moving to Jetty. Note that this is not just a case of the war being exploded into TEMPDIR but I have observed that it continues to serve images etc from the old --webroot location based on the last non-Jetty version of Jenkins (see JENKINS-20858 ). The symptoms are quite subtle and at a minimum this bug needs resolving before the next LTS release. Change By: Richard Mortimer (07/Jan/14 12:00 PM) Assignee: 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 -- 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] [xunit] (JENKINS-17193) Missing Delete button
Hans-Juergen Hafner commented on JENKINS-17193 Missing Delete button Yes, we had several build actions and xUnit was one of the last. 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-client] (JENKINS-21248) Add shallow update init for submodule
Masaki Muranaka commented on JENKINS-21248 Add shallow update init for submodule The candidate patch against this issue is pull-requested at https://github.com/jenkinsci/git-client-plugin/pull/63 . I'll update it. 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-18410) Use RunAction2 from TestResultAction
Derk-Jan Hartman commented on JENKINS-18410 Use RunAction2 from TestResultAction The fix to the fix didn't make it to 1.546 it seems, causing both 1.545 and 1.546 to fail jobs in the aggregate test results phase with the NPE listed in the previous comments. The workaround for this is to explicitly set the names of the jobs that you want aggregated in your job configuration or to remove the entire aggregate task from the job. 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] [maven2] (JENKINS-19396) Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger
kutzi resolved JENKINS-19396 as Fixed Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger Change By: kutzi (07/Jan/14 1:19 PM) Status: Reopened 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] [maven2] (JENKINS-19396) Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger
kutzi updated JENKINS-19396 Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger Change By: kutzi (07/Jan/14 1:19 PM) Priority: Critical Minor 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] [delivery-pipeline] (JENKINS-20756) Dont work with Folders plugin
Patrik Boström closed JENKINS-20756 as Fixed Dont work with Folders plugin Released Change By: Patrik Boström (07/Jan/14 1:51 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] [delivery-pipeline] (JENKINS-20807) Triggered by always include anonymous user
Patrik Boström closed JENKINS-20807 as Fixed Triggered by always include anonymous user Released Change By: Patrik Boström (07/Jan/14 1:51 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] [xcode] (JENKINS-21253) Generate archive causes code sign failure
Cameron Palmer created JENKINS-21253 Generate archive causes code sign failure Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: xcode Created: 07/Jan/14 1:50 PM Description: When adding the Generate Archive option in the Xcode plugin. The build fails to install on devices because of a code sign problem. Checking original app + /usr/bin/codesign --verify - /Users/iosbuildmaster/Jenkins/Home/jobs/Nordea Bedrift - iOS/workspace/build/NordeaBedrift.app Program /usr/bin/codesign returned 1 : [/Users/iosbuildmaster/Jenkins/Home/jobs/Nordea Bedrift - iOS/workspace/build/NordeaBedrift.app: a sealed resource is missing or invalid file modified: /Users/iosbuildmaster/Jenkins/Home/jobs/Nordea Bedrift - iOS/workspace/build/NordeaBedrift.app/Assets.car ] Codesign check fails : /Users/iosbuildmaster/Jenkins/Home/jobs/Nordea Bedrift - iOS/workspace/build/NordeaBedrift.app: a sealed resource is missing or invalid file modified: /Users/iosbuildmaster/Jenkins/Home/jobs/Nordea Bedrift - iOS/workspace/build/NordeaBedrift.app/Assets.car Unchecking Generate Archive results in correctly signed builds. Environment: Mac OS X Project: Jenkins Priority: Minor Reporter: Cameron Palmer 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] [delivery-pipeline] (JENKINS-20822) Pipeline start cause
Patrik Boström closed JENKINS-20822 as Fixed Pipeline start cause Released Change By: Patrik Boström (07/Jan/14 1:51 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] [delivery-pipeline] (JENKINS-21070) Set build displayname does not work
Patrik Boström closed JENKINS-21070 as Fixed Set build displayname does not work Change By: Patrik Boström (07/Jan/14 1:52 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] [delivery-pipeline] (JENKINS-21008) Severe performance degradation when loading view
Patrik Boström closed JENKINS-21008 as Fixed Severe performance degradation when loading view Released Change By: Patrik Boström (07/Jan/14 1:52 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] [core] (JENKINS-21254) /login offers link to /opensearch.xml which anonymous users cannot retrieve
Jesse Glick created JENKINS-21254 /login offers link to /opensearch.xml which anonymous users cannot retrieve Issue Type: Bug Assignee: Unassigned Components: core Created: 07/Jan/14 2:06 PM Description: The login page should not offer an OpenSearch link when this is not actually available to anonymous users. Project: Jenkins Labels: security Priority: Minor 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] [xunit] (JENKINS-11191) Test Name Reported as (root)
Andy Bigos commented on JENKINS-11191 Test Name Reported as (root) With xUnit plugin, there is missing the package name, so there is the default 'root' package name. Is it possible to set the package name from the XML? E.g. if the attribute 'package' was present it would be used to set the name? 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] [analysis-collector] (JENKINS-21255) NullPointerException on hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.getProject(..)
Choon Chern Lim created JENKINS-21255 NullPointerException on hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.getProject(..) Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: analysis-collector Created: 07/Jan/14 2:16 PM Description: When enabling "Aggregate downstream test results" post-build action, I'm getting this error in v1.545 and v1.546. ANALYSIS-COLLECTOR Computing warning deltas based on reference build #34 ERROR: Publisher hudson.tasks.test.AggregatedTestResultPublisher aborted due to exception java.lang.NullPointerException at hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.getProject(AggregatedTestResultPublisher.java:173) at hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.init(AggregatedTestResultPublisher.java:146) at hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.init(AggregatedTestResultPublisher.java:135) at hudson.tasks.test.AggregatedTestResultPublisher.perform(AggregatedTestResultPublisher.java:90) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1030) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Environment: Ubuntu 64bit Project: Jenkins Priority: Major Reporter: Choon Chern Lim 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-21255) NullPointerException on hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.getProject(..)
Ulli Hafner updated JENKINS-21255 NullPointerException on hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.getProject(..) Wrong component, unrelated to analysis collector. Change By: Ulli Hafner (07/Jan/14 2:25 PM) Assignee: UlliHafner Component/s: core Component/s: analysis-collector 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] [findbugs] (JENKINS-21256) Findbug: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
Ulli Hafner commented on JENKINS-21256 Findbug: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory Is this build run on a slave or master? Can you please clear var/lib/jenkins/.jenkins/cache/ and retry. Which Java versions are you using? In which container is Jenkins running? 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] [findbugs] (JENKINS-21256) Findbug: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
Choon Chern Lim commented on JENKINS-21256 Findbug: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory The build runs on master. I cleared the given path, but I still get the same error message. Here's the Java version:- java version "1.7.0_25" OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.12.04.2) OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) I believe Jenkins runs on Jetty because I'm using this approach to install it on Ubuntu: https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu Hope this helps. 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] [drmemory] (JENKINS-17464) Invisible Graph list (our case 8914)
Mads Nielsen resolved JENKINS-17464 as Fixed Invisible Graph list (our case 8914) This has been fixed by a friendly user for us. Thanks! Fixed in upcomming 1.2. Change By: Mads Nielsen (07/Jan/14 2:41 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21254) /login offers link to /opensearch.xml which anonymous users cannot retrieve
Jesse Glick started work on JENKINS-21254 /login offers link to /opensearch.xml which anonymous users cannot retrieve Change By: Jesse Glick (07/Jan/14 2:42 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21254) /login offers link to /opensearch.xml which anonymous users cannot retrieve
Jesse Glick assigned JENKINS-21254 to Jesse Glick /login offers link to /opensearch.xml which anonymous users cannot retrieve Change By: Jesse Glick (07/Jan/14 2:42 PM) Assignee: JesseGlick 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] [gui] (JENKINS-13978) Add posibility to copy view
Andréas Berg commented on JENKINS-13978 Add posibility to copy view I can confirm too. I see no trace of this functionality after upgrading to 1.546. Was really looking forward to this one. 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] [prioritysorter] (JENKINS-21236) PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem
pedro reis commented on JENKINS-21236 PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem ok, it upgraded now. (this time, I have updated some other plugins along with priority sorter, and it did the trick) will report if now works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [viewVC] (JENKINS-18283) Wrong URL in diff
Alexander Ost commented on JENKINS-18283 Wrong URL in diff The problem also exists on the LTS branch (1.509.4). Since the pull request is already available, is there any chance to get this released soon? 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] [prioritysorter] (JENKINS-21236) PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem
pedro reis commented on JENKINS-21236 PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem Nope, It still doesn't work on 2.4 @ 1.532.1! Priority order not respected when asking the jobs to start simultaneously: 2014-01-07 14:54:05.907000 2014-01-07 14:54:05.908000 2014-01-07 14:54:05.908000 2014-01-07 14:54:05.909000 2014-01-07 14:54:05.91 2014-01-07 14:54:05.911000 Also the jobs were on build queue and started to build without respecting the priority order. 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-21254) /login offers link to /opensearch.xml which anonymous users cannot retrieve
SCM/JIRA link daemon commented on JENKINS-21254 /login offers link to /opensearch.xml which anonymous users cannot retrieve Code changed in jenkins User: Jesse Glick Path: src/main/resources/hudson/plugins/translation/L10nDecorator/footer.jelly http://jenkins-ci.org/commit/translation-plugin/b39189fe6c636e563374c4e61d5e372ebbf951bc Log: JENKINS-21254 Do not offer to let anonymous users without Overall/Read submit translations from the /login 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] [subversion] (JENKINS-21042) Allow exclusions from SVN polling for certain repository URLs
Daniel Beck commented on JENKINS-21042 Allow exclusions from SVN polling for certain repository URLs This is what the include/exclude regions in the Advanced configuration are for. They still show up in the changes though (if tools change more often than main, this will lead to long change lists). 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-20898) SVN post commit hook not working after update to 1.542
Daniel Beck commented on JENKINS-20898 SVN post commit hook not working after update to 1.542 Would be helpful if you only updated one of (Jenkins, SVN plugin) to narrow down the cause. 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] [maven] (JENKINS-11695) Jenkins does not respect Maven profiles - so pom module parsing fails
Julien Carsique
commented on JENKINS-11695
Jenkins does not respect Maven profiles - so pom module parsing fails
Confirmed with a repository added from a profile and containing an updated parent POM, providing a new dependency in its dependencyManagement.
The POM parsing fails with "'dependencies.dependency.version' for org.quartz-scheduler:quartz-oracle:jar is missing".
This error corresponds to not using the profile configured in the job ("qa" in my case):
$ mvn help:effective-pom -Pqa |grep -C2 quartz-oracle
dependency
groupIdorg.quartz-scheduler/groupId
artifactIdquartz-oracle/artifactId
version1.8.6/version
/dependency
$ mvn help:effective-pom |grep -C2 quartz-oracle
Validation Messages:
[0] 'dependencies.dependency.version' is missing for org.quartz-scheduler:quartz-oracle:jar
The suggested workaround, I saw in some mailing list thread, to provide a custom settings which activates the wanted profile doesn't work neither.
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-18410) Use RunAction2 from TestResultAction
Jesse Glick commented on JENKINS-18410 Use RunAction2 from TestResultAction Correct, the fix should be in 1.547, and the workaround is to set names explicitly. Sorry for any disruption. 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] [email-ext] (JENKINS-21228) add shell variable into pre-send groovy script context
Alex Earl commented on JENKINS-21228 add shell variable into pre-send groovy script context Some admins allow normal users to configure jobs, not just sysadmins. What do you mean it accepts "string script" only? You should be able to use tokens in it just like the content. I would need more information as to why you can't just the attach build log feature to attach the log from the build slave. 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] [email-ext] (JENKINS-21245) userid to email address lookup
Alex Earl commented on JENKINS-21245 userid to email address lookup I think this would be better implemented as a separate plugin that provided an implementation of the Mailer plugin's MailAddressResolver, see 1. 1 - https://github.com/jenkinsci/mailer-plugin/blob/master/src/main/java/hudson/tasks/MailAddressResolver.java 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] [email-ext] (JENKINS-20804) [Email ext plugin] showDependencies for ${CHANGES} doesn't seem to work
Alex Earl
commented on JENKINS-20804
[Email ext plugin] showDependencies for ${CHANGES} doesnt seem to work
This is what it does for showDependencies, I'm not real familiar with this code, so I can't comment on what exactly it should do
for (EntryAbstractProject, DependencyChange e : build.getDependencyChanges(previousBuild).entrySet()) {
buf.append("\n===\n");
buf.append("\nChanges in ").append(e.getKey().getName())
.append(":\n");
for (AbstractBuild?, ? b : e.getValue().getBuilds()) {
for (ChangeLogSet.Entry entry : b.getChangeSet()) {
Util.printf(buf, format, new ChangesSincePrintfSpec(entry, pathFormat, dateFormatter));
}
}
}
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-21257) up link of downstream job from multiconfig job is going nowhere
Derk-Jan Hartman created JENKINS-21257 up link of downstream job from multiconfig job is going nowhere Issue Type: Bug Assignee: Unassigned Components: core Created: 07/Jan/14 4:13 PM Description: In the UI of the downstream job of a multiconfiguration job, in the top left there is a link named "up". This link points to http://server/job and results in a 404: "Problem accessing /job/. Reason: Not Found" So the UI for: http://server/job/multiconfig-job/label=aLabel I would expect it to link to: http://server/job/multiconfig-job But it links to http://server/job/ Environment: 1.546 Project: Jenkins Priority: Major Reporter: Derk-Jan Hartman 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-21257) up link of downstream job from multiconfig job is going nowhere
Derk-Jan Hartman updated JENKINS-21257 up link of downstream job from multiconfig job is going nowhere Change By: Derk-Jan Hartman (07/Jan/14 4:16 PM) Priority: Major Minor 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-21254) /login offers link to /opensearch.xml which anonymous users cannot retrieve
SCM/JIRA link daemon resolved JENKINS-21254 as Fixed /login offers link to /opensearch.xml which anonymous users cannot retrieve Change By: SCM/JIRA link daemon (07/Jan/14 4:16 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 -- 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-21254) /login offers link to /opensearch.xml which anonymous users cannot retrieve
SCM/JIRA link daemon commented on JENKINS-21254 /login offers link to /opensearch.xml which anonymous users cannot retrieve Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/resources/lib/layout/layout.jelly test/src/main/java/org/jvnet/hudson/test/JenkinsRule.java test/src/test/java/lib/layout/LayoutTest.java http://jenkins-ci.org/commit/jenkins/7c91c402a7c491d51f776178898ee473989ab6c9 Log: FIXED JENKINS-21254 Ensuring that all links offered on the /login page can be read even by anonymous users without Jenkins.READ. Compare: https://github.com/jenkinsci/jenkins/compare/67f3465e0378...7c91c402a7c4 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] [viewVC] (JENKINS-18283) Wrong URL in diff
Idan Bidani commented on JENKINS-18283 Wrong URL in diff We have the same issue I've had to compile it and manually upload the plugin. any chance to approve this pull request https://github.com/jenkinsci/viewVC-plugin/pull/4 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] [viewVC] (JENKINS-18283) Wrong URL in diff
Idan Bidani edited a comment on JENKINS-18283 Wrong URL in diff We have the same issue I've had to compile it and manually upload the plugin. any chance to approve this pull request https://github.com/jenkinsci/viewVC-plugin/pull/1 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-19544) OutOfMemory due to unbounded storage in OldDataMonitor
Jesse Glick updated JENKINS-19544 OutOfMemory due to unbounded storage in OldDataMonitor Change By: Jesse Glick (07/Jan/14 4:37 PM) Labels: memory-leak performance 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-19741) Massive jobs execution causes issues in lastSuccessfulBuild permalink update
Lukáš Zach updated JENKINS-19741 Massive jobs execution causes issues in lastSuccessfulBuild permalink update Change By: Lukáš Zach (07/Jan/14 4:47 PM) Attachment: 140107-LZA-J19741-log-fragment.log 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-19741) Massive jobs execution causes issues in lastSuccessfulBuild permalink update
Lukáš Zach commented on JENKINS-19741 Massive jobs execution causes issues in lastSuccessfulBuild permalink update We are facing the same issue (on Linux as original reporter). Jenkins ver Jenkins ver. 1.509.4 LTS OS ver Scientific Linux release 6.4 (Carbon) The same stacktrace as above. Jan 01, 2014 7:05:37 PM jenkins.model.PeepholePermalink updateCache WARNING: Failed to update hudson.model.FreeStyleProject@6d5d2cc[prototype load] lastStableBuild permalink for prototype load t2mg0i1lkvibf4v07yw184j0m0j6yk2m-1383593938@qa-9 8prototype-1.na.getgooddata.com java.nio.file.NoSuchFileException: /var/lib/jenkins/jobs/prototype load/builds/lastStableBuild.tmp at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.readSymbolicLink(UnixFileSystemProvider.java:495) at java.nio.file.Files.readSymbolicLink(Files.java:1382) at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.Util.resolveSymlink(Util.java:1216) at jenkins.model.PeepholePermalink.writeSymlink(PeepholePermalink.java:169) at jenkins.model.PeepholePermalink.updateCache(PeepholePermalink.java:137) at jenkins.model.PeepholePermalink$RunListenerImpl.onCompleted(PeepholePermalink.java:214) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199) at hudson.model.Run.execute(Run.java:1642) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Bigger log fragment here - 140107-LZA-J19741-log-fragment.log Statistic per day on our Jenkins instance: [root@jenkins-1509:/var/lib/jenkins/logs] zgrep -c "WARNING: Failed to update hudson.model.FreeStyleProject" jen* | sort -r jenkins.log:23 (20140106) jenkins.log-20140104.gz:26 jenkins.log-20140101.gz:22 jenkins.log-20131227.gz:18 jenkins.log-20131221.gz:23 jenkins.log-20131219.gz:1 IMO it has nothing to do with windows platform. = Reopening 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-19741) Massive jobs execution causes issues in lastSuccessfulBuild permalink update
Lukáš Zach reopened JENKINS-19741 Massive jobs execution causes issues in lastSuccessfulBuild permalink update Change By: Lukáš Zach (07/Jan/14 4:46 PM) Resolution: Duplicate 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 -- 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-19741) Massive jobs execution causes issues in lastSuccessfulBuild permalink update
Lukáš Zach updated JENKINS-19741 Massive jobs execution causes issues in lastSuccessfulBuild permalink update Change By: Lukáš Zach (07/Jan/14 4:48 PM) Environment: 1 )1 .509.3,Linuxserver(RHEL6) 2)1.509.4LTS,SLLinux6.4 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] [sloccount] (JENKINS-21258) Graphical artefacts in the trend graphs
Michal Turek created JENKINS-21258 Graphical artefacts in the trend graphs Issue Type: Bug Affects Versions: current Assignee: Michal Turek Attachments: trend_missing_data_bug.png, trend_missing_data_fixed.png Components: sloccount Created: 07/Jan/14 5:54 PM Description: If a language newly appears/disappears in/from SLOCCount report the trend graphs will contain graphical artifacts. The issue is visible mainly in the delta trend but it is (and always was) present in the absolute one too. The code doesn't consider that currently processed build may contain different languages than the previous and next ones. See the attached screenshots. Environment: Bug in the code logic. Project: Jenkins Priority: Major Reporter: Michal Turek 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-21042) Allow exclusions from SVN polling for certain repository URLs
S Daigle commented on JENKINS-21042 Allow exclusions from SVN polling for certain repository URLs Ah, thank you. I've only been using Jenkins for 6 years or so. I would have found those options in another 5 :-\ Thanks again. Those should work fine. 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] [sloccount] (JENKINS-21258) Graphical artefacts in the trend graphs
Michal Turek commented on JENKINS-21258 Graphical artefacts in the trend graphs Fixed in https://github.com/mixalturek/sloccount-plugin/commit/b214b258df66a1671271be14a24d0391ea8c57aa. 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-19826) JavaScript errors corrupt Apply button in IE10 Compat View
Jesse Glick commented on JENKINS-19826 _javascript_ errors corrupt Apply button in IE10 Compat View So the response body from configSubmit is correct (supposed to show Saved in the notification bar). But in apply.js, the iframe has no content. Unclear whether this is actually related to the JS errors thrown earlier. 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] [disk-usage] (JENKINS-21259) Can't save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number.
Jesper Jensen updated JENKINS-21259 Cant save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number. Change By: Jesper Jensen (07/Jan/14 6:21 PM) Description: Jenkinsversion1.543. ItriedtoupdatethesystemconfigurationandthenIgetthiserror.ThefieldthatItriedtoupdatewasthetimeoutfortheslaveTimeoutforcalculationofslaveworkspaceinminutesfrom10minto20min.quotejavax.servlet.ServletException:net.sf.json.JSONException:JSONObject[allJobsSize]isnotanumber. atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631) atorg.kohsuke.stapler.Stapler.service(Stapler.java:225) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) atnet.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) atorg.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) atcom.marvelution.hudson.plugins.apiv2.servlet.filter.HudsonAPIV2ServletFilter.doFilter(HudsonAPIV2ServletFilter.java:115) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) athudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
[JIRA] [disk-usage] (JENKINS-21259) Can't save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number.
Jesper Jensen created JENKINS-21259 Cant save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number. Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage Created: 07/Jan/14 6:20 PM Description: I tried to update the system configuration and then I get this error. The field that I tried to update was the timeout for the slave "Time out for calculation of slave workspace in minutes" from 10 min to 20 min. quote javax.servlet.ServletException: net.sf.json.JSONException: JSONObjectallJobsSize is not a number. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.hudson.plugins.apiv2.servlet.filter.HudsonAPIV2ServletFilter.doFilter(HudsonAPIV2ServletFilter.java:115) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) 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 jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) 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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) 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
[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command
Bernardo Oliveira Pinto commented on JENKINS-20387 Timeout (10min) on git clone command @Kjell you can go to Manage Jenkins Manage Nodes slave Configure and set the JVM Options to -Dorg.jenkinsci.plugins.gitclient.Git.timeOut=400 (I'm using the Launch slave agents on Unix machines via SSH option). This worked for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [integrity-plugin] (JENKINS-21260) PTC integrity plugin: version 1.9 does not
Grigoriy Milman created JENKINS-21260 PTC integrity plugin: version 1.9 does not Issue Type: Bug Assignee: Cletus DSouza Attachments: PTC1_9 History.jpg, PTC1_9Config.jpg Components: integrity-plugin Created: 07/Jan/14 6:26 PM Description: After upgrading from PTC integrity plugin from 1.8 to 1.9, build job is instantly triggered each time when polling SCM changes is scheduled, though there were no changes in repository! PTC plugin version 1.8 doesn't have such "feature" Environment: Windows 7 Project: Jenkins Priority: Critical Reporter: Grigoriy Milman 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-19826) JavaScript errors corrupt Apply button in IE10 Compat View
Jesse Glick commented on JENKINS-19826 _javascript_ errors corrupt Apply button in IE10 Compat View http://stackoverflow.com/questions/2181385/ie-issue-submitting-form-to-an-iframe-using-_javascript_ seems to be the explanation. 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-19826) JavaScript errors corrupt Apply button in IE10 Compat View
Jesse Glick assigned JENKINS-19826 to Jesse Glick _javascript_ errors corrupt Apply button in IE10 Compat View Change By: Jesse Glick (07/Jan/14 6:25 PM) Assignee: JesseGlick 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-19826) JavaScript errors corrupt Apply button in IE10 Compat View
Jesse Glick started work on JENKINS-19826 _javascript_ errors corrupt Apply button in IE10 Compat View Change By: Jesse Glick (07/Jan/14 6:25 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21042) Allow exclusions from SVN polling for certain repository URLs
Daniel Beck resolved JENKINS-21042 as Not A Defect Allow exclusions from SVN polling for certain repository URLs You're welcome. Assuming this issue is resolved. If not, please reopen and edit the issue title and description to match your current expectations (e.g. to just have a new option to hide excluded regions from the change log). Change By: Daniel Beck (07/Jan/14 6:13 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 -- 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] [integrity-plugin] (JENKINS-20751) PTC_Integrity Plugin- file exclude filter not working for multiple entries
SCM/JIRA link daemon commented on JENKINS-20751 PTC_Integrity Plugin- file exclude filter not working for multiple entries Code changed in jenkins User: Cletus D'Souza Path: pom.xml src/main/java/hudson/scm/APISession.java src/main/java/hudson/scm/IntegrityCMProject.java src/main/java/hudson/scm/IntegrityCheckinAction.java src/main/java/hudson/scm/IntegrityCheckpointAction.java src/main/java/hudson/scm/IntegrityConfigurable.java src/main/java/hudson/scm/IntegrityItemAction.java src/main/java/hudson/scm/IntegritySCM.java src/main/resources/hudson/scm/IntegrityItemAction/config.jelly src/main/resources/hudson/scm/IntegritySCM/help-configurationName.html http://jenkins-ci.org/commit/integrity-plugin/34618c8c84390f502eb61cf18664e455e9e6ef8c Log: JENKINS-20751: PTC_Integrity Plugin- file exclude filter not working for multiple entries - Fix contributed by Matthias Rump JENKINS-20541: Expose Checkpoint Number to build environment Fixed potential security issue where Firefox can expose saved passwords in clear text 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] [integrity-plugin] (JENKINS-20541) Expose Checkpoint Number to build environment
SCM/JIRA link daemon commented on JENKINS-20541 Expose Checkpoint Number to build environment Code changed in jenkins User: Cletus D'Souza Path: pom.xml src/main/java/hudson/scm/APISession.java src/main/java/hudson/scm/IntegrityCMProject.java src/main/java/hudson/scm/IntegrityCheckinAction.java src/main/java/hudson/scm/IntegrityCheckpointAction.java src/main/java/hudson/scm/IntegrityConfigurable.java src/main/java/hudson/scm/IntegrityItemAction.java src/main/java/hudson/scm/IntegritySCM.java src/main/resources/hudson/scm/IntegrityItemAction/config.jelly src/main/resources/hudson/scm/IntegritySCM/help-configurationName.html http://jenkins-ci.org/commit/integrity-plugin/34618c8c84390f502eb61cf18664e455e9e6ef8c Log: JENKINS-20751: PTC_Integrity Plugin- file exclude filter not working for multiple entries - Fix contributed by Matthias Rump JENKINS-20541: Expose Checkpoint Number to build environment Fixed potential security issue where Firefox can expose saved passwords in clear text 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-19826) JavaScript errors corrupt Apply button in IE10 Compat View
Jesse Glick updated JENKINS-19826 _javascript_ errors corrupt Apply button in IE10 Compat View Change By: Jesse Glick (07/Jan/14 6:36 PM) Labels: coreerrorf:select _javascript_ webpage lts-candidate 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-19826) Apply button does not work in IE Compat View
Jesse Glick updated JENKINS-19826 Apply button does not work in IE Compat View I see no evidence that the JS errors were in any way related to the problem with the Apply button. Maybe they should be fixed somehow, but I do not know what their cause is, or what the impact is. Testing on IE 9. Change By: Jesse Glick (07/Jan/14 6:40 PM) Summary: _javascript_errorscorrupt Applybutton doesnotwork in IE10 IE CompatView 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] [integrity-plugin] (JENKINS-21260) PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed!
Grigoriy Milman updated JENKINS-21260 PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed! Change By: Grigoriy Milman (07/Jan/14 6:43 PM) Summary: PTCintegrityplugin:version1.9 does instantlytriggersnewbuildthoughcorrespondingfilesinrepositoryhave not beenchanged! 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-18678) Builds disappear some time after renaming job
Marko Stefanovic commented on JENKINS-18678 Builds disappear some time after renaming job I had a similar problem where build would "disappear". Reason was a missing build.xml in the build folders. After some research I found out that the problem was using the Warnings plugin while the Maven plugin was deactivated. After I activated the Maven the build.xml was correctly created and the following builds were shown correctly. 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-18678) Builds disappear some time after renaming job
Oleg Nenashev commented on JENKINS-18678 Builds disappear some time after renaming job @Marko AFAIK, Maven plugin is an optional dependency for Warnings plugin. Hence Warnings plugin should work properly without it. I recommend to create a separate issue for your case. 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-18678) Builds disappear some time after renaming job
Marko Stefanovic edited a comment on JENKINS-18678 Builds disappear some time after renaming job I had a similar problem where build would "disappear". Reason was a missing build.xml in the build folders. After some research I found out that the problem was using the Warnings plugin for a msbuild project while the Maven plugin was deactivated. After I activated the Maven plugin the build.xml was correctly created and the following builds were shown correctly in the history. 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-18678) Builds disappear some time after renaming job
Jesse Glick commented on JENKINS-18678 Builds disappear some time after renaming job @marquito77 yes that sounds really unrelated. 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] [integrity-plugin] (JENKINS-20541) Expose Checkpoint Number to build environment
Cletus DSouza resolved JENKINS-20541 as Fixed Expose Checkpoint Number to build environment Added enhancement in version 1.20. The pre-build checkpoin number is exposed to the environment in a variable named MKSSSI_BUILD Change By: Cletus DSouza (07/Jan/14 7:08 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 -- 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] [integrity-plugin] (JENKINS-20581) Incorrect concept of Author in Change Log
Cletus DSouza commented on JENKINS-20581 Incorrect concept of Author in Change Log Yes, that is correct. This is as designed. Fundamentally, this plugin allows you to switch from any configuration to any configuration and is not dependent on the use of Change Packages. If we need to resolve this issue, then we'll have to mandate that all users must use Change Packages. Eventually, the core product will be moving in that direction and we can re-visit this architectural change at that time. 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] [integrity-plugin] (JENKINS-20665) cannot do si command through windows service
Cletus DSouza resolved JENKINS-20665 as Not A Defect cannot do si command through windows service I'm sorry, but the plugin doesn't use the Integrity CLI. So, while this is an issue from a general support standpoint, this is not a plugin issue. Please open a PTC Integrity support ticket for ways to execute the CLI from a Windows Service. Thanks! Cletus Change By: Cletus DSouza (07/Jan/14 7:14 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 -- 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] [integrity-plugin] (JENKINS-20581) Incorrect concept of Author in Change Log
Cletus DSouza resolved JENKINS-20581 as Postponed Incorrect concept of Author in Change Log Change By: Cletus DSouza (07/Jan/14 7:14 PM) Status: Open Resolved Resolution: Postponed 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] [integrity-plugin] (JENKINS-20540) Unable to add Integrity - Workflow Item postbuild action to a job
Cletus DSouza commented on JENKINS-20540 Unable to add Integrity - Workflow Item postbuild action to a job There was a bug in the jelly file that was not setting the default hostname for the connection. This is fixed in version 1.20 of the plugin. Can you confirm that this resolves your problem? Thanks! Cletus 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] [integrity-plugin] (JENKINS-20751) PTC_Integrity Plugin- file exclude filter not working for multiple entries
Cletus DSouza resolved JENKINS-20751 as Fixed PTC_Integrity Plugin- file exclude filter not working for multiple entries Thanks for the contribution! This is incorporated in v1.20 Change By: Cletus DSouza (07/Jan/14 7:17 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 -- 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] [integrity-plugin] (JENKINS-20839) Checkout reports success, but workspace folders are empty.
Cletus DSouza commented on JENKINS-20839 Checkout reports success, but workspace folders are empty. This might be due to an environment issue. What JRE is picked up when you run this as a window service vs in interactive mode? Other users that have run into this problem were running Jenkins using Java 1.7 u40+. You must stay at Update 40 or lower for the Integrity API to work. 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] [integrity-plugin] (JENKINS-21260) PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed!
Cletus DSouza commented on JENKINS-21260 PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed! There were come configuration changes made in v1.19 that has changed the default location for the embedded Derby database. Can you delete your Job and re-create it to see if that resolves the polling 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.
[JIRA] [integrity-plugin] (JENKINS-18445) Local Integration Point
Cletus DSouza commented on JENKINS-18445 Local Integration Point The mksapi.jar that is shipped with the plugin is as of version 10.3. So, trying to connect to the older client using the Integration Point feature will not work. You'd need to use a 10.3 client or newer. 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.
