[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Jeanjean LaGuigne commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Hi, I was not here last weekend, sorry! We could do this this week. Cheers! This message is automatically generated by JIRA. 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] [promoted-builds] (JENKINS-17605) Only approver should be able to promote build
Chris Sparling updated JENKINS-17605 Only approver should be able to promote build Change By: Chris Sparling (15/Apr/13 7:23 AM) Description: Atthemomentyoucansetabuildsoitcanonlybeapprovedbyspecifiedusers,however,itsstillpossibleforanotherusertoforcethepromotionofthebuild.Forourenvironmentwedliketolimitwhocanexecutethefinalpromotion(ReadyforLive)toonlythosewhoarelistedasapprovers. ItwouldbegoodifthepluginallowedyoutodisableForcePromotion This message is automatically generated by JIRA. 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] [testlink] (JENKINS-17608) Test Link plugin, show the test results in the category notes
Jeanjean LaGuigne created JENKINS-17608 Test Link plugin, show the test results in the category notes Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: testlink Created: 15/Apr/13 7:37 AM Description: TestLink is used a lot in entreprise. But when a tester needs to analyse 200 tests failed, it's not convenient to open 200 files ".xml". So if we add test results in "notes" it should be more comfortable to correct failed tests. Project: Jenkins Priority: Major Reporter: Jeanjean LaGuigne This message is automatically generated by JIRA. 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] [logging] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042
Christian Wolfgang commented on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042 So you are using the logging plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ccm] (JENKINS-13592) Details part of each ccm warning always displays all file
Louis Henry Nayegon commented on JENKINS-13592 Details part of each ccm warning always displays all file At present this plugin only supports one code complexity tool, is there a plan for it to support more than 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] [core] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Christian Apel commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs Thanks for the hint. We are still on version 1.505 because of the issue JENKINS-17264, which has been introduced in version 1.506. But according to the latest comment of yesterday, the current snapshot of the m2release-plugin should solve this issue. I will try to install the latest Jenkins version in the next few days. This message is automatically generated by JIRA. 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] [cvs] (JENKINS-17533) Jenkins 1.510 deletes all CVS branch checkout files
Abhishek Chikane commented on JENKINS-17533 Jenkins 1.510 deletes all CVS branch checkout files My environment details, CVS Plugin - Jenkins CVS Plug-in 2.8 This jenkins is master node. OS - Windows 2008 Jenkins: 1.510 Please let me know if anyone need some more info. This message is automatically generated by JIRA. 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-flow] (JENKINS-17512) Throttling per category doesn't work for build flows
David Wallin updated JENKINS-17512 Throttling per category doesnt work for build flows Change By: David Wallin (15/Apr/13 9:20 AM) Component/s: build-flow This message is automatically generated by JIRA. 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-16845) NullPointer in getPreviousBuild
Alex Ouzounis commented on JENKINS-16845 NullPointer in getPreviousBuild updated your Jenkins to 1.511 and problem is gone! Obviously the log now contains a dozen of these: Apr 15, 2013 10:22:09 AM hudson.tasks.Fingerprinter$FingerprintAction onLoad WARNING: JENKINS-16845: broken FingerprintAction record Would it be more helpful to have the warning updated such that it displays the build name and number that contains the broken FingerprintAction record ? This message is automatically generated by JIRA. 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-16845) NullPointer in getPreviousBuild
Alex Ouzounis edited a comment on JENKINS-16845 NullPointer in getPreviousBuild updated our Jenkins to 1.511 and problem is gone! Obviously the log now contains a dozen of these: Apr 15, 2013 10:22:09 AM hudson.tasks.Fingerprinter$FingerprintAction onLoad WARNING: JENKINS-16845: broken FingerprintAction record Would it be more helpful to have the warning updated such that it displays the build name and number that contains the broken FingerprintAction record ? This message is automatically generated by JIRA. 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-2295) Jenkins cannot handle modules added by profiles - if profile is not activated via '-P' (was: Assertion in MavenModuleSetBuild for aggregator POM with modules provided by
Yves DM commented on JENKINS-2295 Jenkins cannot handle modules added by profiles - if profile is not activated via -P (was: Assertion in MavenModuleSetBuild for aggregator POM with modules provided by profile) Encountered this bug... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-9920) Aggregated test result chart doesn't display test results of the aggregating job
wernight edited a comment on JENKINS-9920 Aggregated test result chart doesnt display test results of the aggregating job This is also something I'd like to see as there is no other simple fix especially if job A archives artifacts used by B. For example: Job A compiles and runs unit tests Job B runs system tests on another Jenkins node Both jobs generate xUnit reports but B must run after A has archived artifacts A should report xUnit reports of itself and B. Currently it can only report xUnit reports of itself (x)or B. This message is automatically generated by JIRA. 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-17590) Builds fail because of slave went offline during the build
Marc Günther commented on JENKINS-17590 Builds fail because of slave went offline during the build Example, this is from a job with a Maven buildstep followed by the following postbuild actions, Archive Artifact, Publish HTML, Publish JUnit: ... [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 27 minutes 17 seconds [INFO] Finished at: Fri Apr 12 15:20:59 CEST 2013 [INFO] Final Memory: 50M/496M [INFO] Looks like the node went offline during the build. Check the slave log for the details.FATAL: null java.lang.NullPointerException This message is automatically generated by JIRA. 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] [other] (JENKINS-17609) java heap size issue
Anup T S created JENKINS-17609 java heap size issue Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: other Created: 15/Apr/13 10:05 AM Description: Hello, We are frequently getting the Java heap size issue and we have collected the java_pid2213.hprof file,but dont know how to analyze the issue.May i know how can i proceed? cant attach the file here as it is 1.1GB.Please let me know the solution asap.its scrwing up the production environment. Due Date: 15/Apr/13 12:00 AM Environment: Production Fix Versions: current Project: Jenkins Priority: Major Reporter: Anup T S This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-7813) Archiving artifacts very slow
stephenconnolly commented on JENKINS-7813 Archiving artifacts very slow @pancake: you do know that the warning is just a warning and not an actual problem. It was just some debugging code and when it is printed it means that you will not see the performance improvements but otherwise everything will be fine. i.e. cosmetic This message is automatically generated by JIRA. 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-17580) Add token for project Display Name
Alex Earl commented on JENKINS-17580 Add token for project Display Name The PROJECT_NAME token returns getProjectFullDisplayName(), what getter would you expect for PROJECT_DISPLAY_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] [ios-device-connector] (JENKINS-15578) hudson.security.AccessDeniedException2: anonymous is missing the Administer permission
Christopher Orr commented on JENKINS-15578 hudson.security.AccessDeniedException2: anonymous is missing the Administer permission I'm not really clear on how slave permissions should work, so I haven't merged this, but here's a patch: https://github.com/jenkinsci/ios-device-connector-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] [cvs] (JENKINS-17533) Jenkins 1.510 deletes all CVS branch checkout files
Michael Clarke commented on JENKINS-17533 Jenkins 1.510 deletes all CVS branch checkout files Can you answer my other questions (other build steps in job, any other versions of Jenkins or the CVS plugin you've tried this in, can the results be reproduced running the checkout as the only step in a job, is this running a clean checkout or are there files in the workspace, what options to you have configured for the cvs job config)? Thanks, Michael This message is automatically generated by JIRA. 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-17611) WinIOException: Failed to create a symlink to builds/lastStableBuild error=183:null
Petar Petrov
updated JENKINS-17611
WinIOException: Failed to create a symlink to builds/lastStableBuild error=183:null
Change By:
Petar Petrov
(15/Apr/13 12:05 PM)
Summary:
Buildfaileddueto
WinIOException:Failedtocreateasymlinktobuilds/lastStableBuilderror=183:null
Description:
ThisisonJenkinsver.1.510
{code:java}...lnbuilds/lastStableBuildC:\Jenkins\jobs\
JobNameWithSpaces
JobName
\lastStablefailedhudson.util.jna.WinIOException:FailedtocreateasymlinkC:\Jenkins\jobs\
JobNameWithSpaces
JobName
\lastStabletobuilds/lastStableBuilderror=183:null athudson.util.jna.Kernel32Utils.createSymbolicLink(Kernel32Utils.java:92) athudson.Util.createSymlink(Util.java:1061) athudson.model.AbstractBuild.createSymlink(AbstractBuild.java:488) athudson.model.AbstractBuild.access$700(AbstractBuild.java:103) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:723) athudson.model.Run.execute(Run.java:1600) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:237)
Emailwastriggeredfor:FailureSendingemailfortrigger:Failure
...{code}
(i)
This
isonJenkinsver
exceptionoccuresattheendofeachbuild
.
1
Itdoes*NOT*affectthebuildoutcome,e
.
510
g.SuccessorFailure.(i)Thisexceptionoccureseveniftherearenospacesinthepath
This message is automatically generated by JIRA.
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] [throttle-concurrents] (JENKINS-17612) Deadlock after simultaneous starting of two jobs
Aleksandr Baramykov updated JENKINS-17612 Deadlock after simultaneous starting of two jobs Change By: Aleksandr Baramykov (15/Apr/13 12:10 PM) Environment: Winserver2003Java1.6 Jenkins1.505 ThrottleConcurrentBuildsPlugin1.7.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Oliver Bock commented on JENKINS-7641 Slaves hang when archiving artifacts This issue just got worse: with 1.502, when the build itself was successful, a failure to archive the artefacts did at least not change the overall build result to FAILURE. Unfortunately, with 1.511 it does: === Running test === Test passed === Archiving artifacts ERROR: Failed to archive artifacts: build.log hudson.util.IOException2: java.io.IOException at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:175) at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61) at java.io.FilterInputStream.read(FilterInputStream.java:107) at hudson.util.HeadBufferingStream.fillSide(HeadBufferingStream.java:83) at hudson.FilePath$TarCompression$2.extract(FilePath.java:625) at hudson.FilePath.copyRecursiveTo(FilePath.java:1926) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724) at hudson.model.Run.execute(Run.java:1600) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) at hudson.FilePath.copyRecursiveTo(FilePath.java:1933) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724) at hudson.model.Run.execute(Run.java:1600) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: java.util.concurrent.ExecutionException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request$1.get(Request.java:278) at hudson.remoting.Request$1.get(Request.java:210) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.FilePath.copyRecursiveTo(FilePath.java:1929) ... 10 more Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Build step 'Archive the artifacts' changed build result to FAILURE Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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
[JIRA] [sloccount] (JENKINS-17427) sloccount NPE
sogabe edited a comment on JENKINS-17427 sloccount NPE Is this reporoduced with the latest 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] [core] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Oliver Bock commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error By the way anyone using proprietary or unusual platforms should not expect that Jenkins core developers will be able to reproduce their problems. Debug it yourself and file a pull request if you want a prompt fix. @jglick: What if we'd provide access to an affected machine, either via ssh or direct access? Would some core developer be willing to tackle the problem in that 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] [git] (JENKINS-7411) Slave environment variables are not used during Git Polling
Christoph Linder
commented on JENKINS-7411
Slave environment variables are not used during Git Polling
Also: setting the tool location on the slave via environment variables is not considered during polling.
Steps to reproduce using Jenking Git Plugin 1.3.0 on Jenkins 1.510:
Set environment variable on master:
PATH_TO_TOOLS=c:\somewhere\tools
On the Slave:
PATH_TO_TOOLS=d:\elsewhere\tools
Tool-Location for default git installation: ${PATH_TO_TOOLS}/git/git.exe
During polling, jenkins always tries to execute git.exe in c:\somewhere\tools, although it is run on the 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] [ghprb] (JENKINS-16921) Missing scheme from github API URL
Honza Brázdil resolved JENKINS-16921 as Fixed Missing scheme from github API URL Change By: Honza Brázdil (15/Apr/13 1:11 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] [core] (JENKINS-17613) NullPointerException when renaming build plan
Patrick Hancke created JENKINS-17613 NullPointerException when renaming build plan Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins-rename1.png, jenkins-rename2.png, jenkins-rename3.png Components: core Created: 15/Apr/13 1:19 PM Description: When I try to rename a build plan, I get a NullPointerException like below. See also screenshots of the steps to follow. The rename however seems to be successfull when I return to the Jenkins home page. Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at 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 winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at
[JIRA] [ghprb] (JENKINS-16174) add documentation and help
Honza Brázdil started work on JENKINS-16174 add documentation and help Change By: Honza Brázdil (15/Apr/13 1:23 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] [publish-over-ftp] (JENKINS-17165) Publish over FTP plugin with version 1.9 does'nt work after Jenkins upgrade to Version 1.504
Alexander Fischer commented on JENKINS-17165 Publish over FTP plugin with version 1.9 doesnt work after Jenkins upgrade to Version 1.504 I have added a complete patched version of the plugins "publish-over" (base) and "publish-over-ftp" on GitHub: https://github.com/afischer211/publish-over-plugin https://github.com/afischer211/publish-over-ftp-plugin Can you test 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] [subversion] (JENKINS-777) The need for Subversion command line options.
George Russell commented on JENKINS-777 The need for Subversion command line options. It would be nice to able to set --ignore-keywords for the operations used by the SVN plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-17220) Add Maven 3.0.5 to the auto installer.
twolfart updated JENKINS-17220 Add Maven 3.0.5 to the auto installer. Change By: twolfart (15/Apr/13 2:05 PM) Description: http://jenkins.mirror.isppower.de/updates/updates/hudson.tasks.Maven.MavenInstaller.jsondoesntlistMaven3.0.5.Pleaseadd [ Maven3.0.5 |http://maven.apache.org/docs/3.0.5/release-notes.html] totheautoinstallerfilesforhudson.tasks.Maven.MavenInstaller. This message is automatically generated by JIRA. 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-17220) Add Maven 3.0.5 to the auto installer.
twolfart assigned JENKINS-17220 to Kohsuke Kawaguchi Add Maven 3.0.5 to the auto installer. Change By: twolfart (15/Apr/13 2:05 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] [core] (JENKINS-7291) Flyweight jobs and zero executors
Christophe Demarey commented on JENKINS-7291 Flyweight jobs and zero executors Does it mean that a workspace will be created on the master? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Alexander Uvizhev created JENKINS-17614 Jenkins triggers builds on SCM changes although not configured Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 15/Apr/13 2:13 PM Description: Hi, Recently I've upgraded Jenkins to ver 1.508 and many plugins (including Jenkins GIT plugin from 1.1.25 to 1.3.0) and since that time I got a lot of my jobs using Git SCM running very frequently without any reason. None of my jobs using "Poll SCM" in "Build Triggers". But I see them running with build cause "Started by an SCM change" though very often there are no changes at all. And Polling Log is always empty. Project: Jenkins Priority: Major Reporter: Alexander Uvizhev This message is automatically generated by JIRA. 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] [platformlabeler] (JENKINS-17615) Platform labels disappear from SSH slave node
Krzysztof Malinowski created JENKINS-17615 Platform labels disappear from SSH slave node Issue Type: Bug Affects Versions: current Assignee: lifeless Components: platformlabeler Created: 15/Apr/13 2:34 PM Description: I have 4 similar SSH slave nodes configured. After upgrading to Jenkins 1.510 one of them keeps losing platform labels. In effect all jobs tied to a platform label skip this node. The node has one manually assigned label. When the issue happens only this one label stays on the node, but all automatically assigned platform labels disappear. To recover from such situation I need: Disconnect the node and relaunch it, Enter node configuration and press Save button. After first step (disconnect/relaunch) platform labels do show up, but Jenkins still does not see those labels (reporting no executors with required label available). I need to perform second step (Configure/Save) to make Jenkins actually refresh its labels knowledge. This is an issue I already reported, just in this case it's always reproducible. Anyway, this solution is not permanent, because after some time platform labels get dropped again and I need to repeat the steps above. I wasn't observing this issue before upgrade to 1.510. Environment: Jenkins 1.510 on RHEL5 x86_64 Project: Jenkins Priority: Major Reporter: Krzysztof Malinowski This message is automatically generated by JIRA. 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-17616) Performance issue with Subversion plugin - trigger build on SVN commit takes too long
Glen Core created JENKINS-17616 Performance issue with Subversion plugin - trigger build on SVN commit takes too long Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 15/Apr/13 2:36 PM Description: After upgrade of Jenkins/Subversion plugin from version 1.447/1.39 to version 1.501/1.45, we have noticed significant delay in triggering builds on commit (around 1 minute). We are using notify CI method in our post-commit hooks.Users who do not have jobs configured in Jenkins are being badly impacted, while post commit hook notifies Jenkins. Downgrading Subversion plugin back to 1.39 removes this issue, but we would like to be on a higher version as Subversion 1.7 is supported those versions. Environment: Windows, Visual SVN Project: Jenkins Priority: Major Reporter: Glen Core This message is automatically generated by JIRA. 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] [platformlabeler] (JENKINS-17615) Platform labels disappear from SSH slave node
Krzysztof Malinowski updated JENKINS-17615 Platform labels disappear from SSH slave node Change By: Krzysztof Malinowski (15/Apr/13 2:36 PM) Description: Ihave4similarSSHslavenodesconfigured.AfterupgradingtoJenkins1.510oneofthemkeepslosingplatformlabels.Ineffectalljobstiedtoaplatformlabelskipthisnode.Thenodehasonemanuallyassignedlabel.Whentheissuehappensonlythisonelabelstaysonthenode,butallautomaticallyassignedplatformlabelsdisappear.TorecoverfromsuchsituationIneed:-Disconnectthenodeandrelaunchit,-EnternodeconfigurationandpressSavebutton.Afterfirststep(disconnect/relaunch)platformlabelsdoshowup,butJenkinsstilldoesnotseethoselabels(reportingnoexecutorswithrequiredlabelavailable).Ineedtoperformsecondstep(Configure/Save)tomakeJenkinsactuallyrefreshitslabelsknowledge.ThisisanissueIalreadyreported (JENKINS-9586) ,justinthiscaseitsalwaysreproducible.Anyway,thissolutionisnotpermanent,becauseaftersometimeplatformlabelsgetdroppedagainandIneedtorepeatthestepsabove.Iwasntobservingthisissuebeforeupgradeto1.510. This message is automatically generated by JIRA. 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] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Alexander Fischer commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. I have added a complete patched version of the plugins "publish-over" (base) and "publish-over-ssh" on GitHub: https://github.com/afischer211/publish-over-plugin https://github.com/afischer211/publish-over-ssh-plugin Can you test 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-17617) SECURITY: It's possible to set SSH key for another user
Krzysztof Malinowski created JENKINS-17617 SECURITY: Its possible to set SSH key for another user Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 15/Apr/13 3:00 PM Description: It is possible to enter another user configuration, using URL like http://jenkins-instance/user/username/configure and change (or assign) SSH key for this user. It is now possible to authenticate through CLI as this user and initiate actions on behalf of another user, probably with higher privileges. Additionally, since not many users are aware of configuration section per user, this change may get unnoticed for quite a long time. Environment: Jenkins 1.510 on RHEL5 x86_64 Project: Jenkins Priority: Critical Reporter: Krzysztof Malinowski This message is automatically generated by JIRA. 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-17577) Add trigger list of triggers that fired to the object model of the pre-send script
Alex Earl resolved JENKINS-17577 as Fixed Add trigger list of triggers that fired to the object model of the pre-send script Added two variables to the object model: trigger - the current trigger (EmailTrigger instance) causing an email to be sent triggered - a MapString,EmailTrigger that is a name-trigger map for all the triggers that were triggered to send emails. This is an unmodifiable map. Change By: Alex Earl (15/Apr/13 3:01 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] [email-ext] (JENKINS-17577) Add trigger list of triggers that fired to the object model of the pre-send script
SCM/JIRA link daemon commented on JENKINS-17577 Add trigger list of triggers that fired to the object model of the pre-send script Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/test/java/hudson/plugins/emailext/plugins/content/JellyScriptContentTest.java src/test/java/hudson/plugins/emailext/plugins/content/ScriptContentTest.java http://jenkins-ci.org/commit/email-ext-plugin/dba4fe1fd045f44037272989cb2926abb033292b Log: Fixed JENKINS-17577 This message is automatically generated by JIRA. 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-17460) Error occurs viewing build history on some builds
Bruce Coveny updated JENKINS-17460 Error occurs viewing build history on some builds Change By: Bruce Coveny (15/Apr/13 3:53 PM) Component/s: parameterized-trigger This message is automatically generated by JIRA. 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] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
drnic commented on JENKINS-11024 Some commands dont work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others I wrote up the use of the CLI and how to setup this workaround http://starkandwayne.com/articles/2013/04/12/jenkins-builds-from-cli/ This message is automatically generated by JIRA. 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-16865) SVN fail to revert working dir : NullPointerException
Marcel Juenemann commented on JENKINS-16865 SVN fail to revert working dir : NullPointerException I had the exact same error multiple times now. I'm using the check-out strategy "Use 'svn update' as much as possible" and SVN version is set to 1.6. I have a SCM trigger configured, but that shouldn't matter, since it's usually triggered by an upstream project. Any idea what could cause this? This message is automatically generated by JIRA. 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-16865) SVN fail to revert working dir : NullPointerException
Marcel Juenemann edited a comment on JENKINS-16865 SVN fail to revert working dir : NullPointerException I had the same error multiple times now, except not during revert, but during update: Updating https://... at revision 2465 FATAL: null java.lang.NullPointerException at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:176) ... I'm using the check-out strategy "Use 'svn update' as much as possible" and SVN version is set to 1.6. I have a SCM trigger configured, but that shouldn't matter, since it's usually triggered by an upstream project. Any idea what could cause this? This message is automatically generated by JIRA. 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-13253) Slave connection reset issues since 1.456
Nicholas Lun commented on JENKINS-13253 Slave connection reset issues since 1.456 Is there any update to this issue? All I can tell from the stacktrace is that at the end of the build, Jenkins requests that the slave kill the remaining processes. But, before it can do so it receives a response that the Connection was terminated due to some failure during a read operation(can't see the reason behind the failure in the stacktrace). Doesn't this seem like some kind of race condition where the slave is trying to finish up and kill the remaining processes while the master terminates the connection before the slave can finish? This message is automatically generated by JIRA. 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] [logging] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042
Dan Lewis commented on JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS, case 9042 am I using logging plugin? no. but I didn't know what module to put in for this problem? Help? It's not clear to me from the stack trace where this problem is coming from. This message is automatically generated by JIRA. 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-17580) Add token for project Display Name
Ken Morse commented on JENKINS-17580 Add token for project Display Name Very cool! Thanks, Alex! This message is automatically generated by JIRA. 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-17618) Changes not yet saved message on Configuration screens
Marc Günther created JENKINS-17618 Changes not yet saved message on Configuration screens Issue Type: New Feature Assignee: Unassigned Components: core Created: 15/Apr/13 5:10 PM Description: Suggestion: As soon as you make a change to any field on a Configuration screen, the following message should show next to the Save and Apply buttons: Save | Apply | Changes not yet saved I know this from a different CI system, and it is very helpful. On Jenkins, I keep loosing configuration changes, because I accidentally forget to save or navigate away from the page. Project: Jenkins Priority: Minor Reporter: Marc Günther This message is automatically generated by JIRA. 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-13995) Would like the ability to disable hover-over context menus.
G. Ann Campbell commented on JENKINS-13995 Would like the ability to disable hover-over context menus. I agree that the 'v' is hard to use. If I can't have the old functionality back (which I loved) how about you don't have to click on the 'v' it just drops down automatically? This message is automatically generated by JIRA. 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-15355) AdjunctManager: exception upon startup
domi commented on JENKINS-15355 AdjunctManager: exception upon startup are you running jenkins within a different container? e.g. Tomcat? or is it the default, Winston? This message is automatically generated by JIRA. 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-16865) SVN fail to revert working dir : NullPointerException
Mukul Sharma commented on JENKINS-16865 SVN fail to revert working dir : NullPointerException We have SVN version 1.6.18 on the node in question. We don't have an SVN trigger, simply an svn update (by doing revert first) at the start of the build. Not sure if that counts. This message is automatically generated by JIRA. 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-13995) Would like the ability to disable hover-over context menus.
G. Ann Campbell commented on JENKINS-13995 Would like the ability to disable hover-over context menus. Was the queue time popup for jobs in the build queue supposed to be incorporated into the now-non-default context menu? Since the context menu is now a separate function, I'd like to see the queue time popup return. This message is automatically generated by JIRA. 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-17619) Allow directory excludes for REKEY process: jenkins.security.RekeySecretAdminMonitor
David Johansen created JENKINS-17619 Allow directory excludes for REKEY process: jenkins.security.RekeySecretAdminMonitor Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 15/Apr/13 5:30 PM Description: When re-keying we run into an issue where jenkins is scanning all directories, even the hidden NAS directories with backups, ".snapshots" which causes it to scan 30x the files it needs to while failing due to permissions on this directory. It would be great to have an option to exclude directories from this process. I couldn't find any info about this problem yet, so as far as I know this is the first ISSUE created for it... ERROR: Failed to rewrite /var/lib/jenkins/.snapshot/nightly.29/job_history/jobs/JOBNAME REMOVED/2013-01-04_15-09-39/config.xml hudson.util.IOException2: Failed to create a temporary file in /var/lib/jenkins/.snapshot/nightly.29/job_history/jobs/JOBNAME REMOVED/2013-01-04_15-09-39 at hudson.util.AtomicFileWriter.init(AtomicFileWriter.java:67) at hudson.util.SecretRewriter.rewrite(SecretRewriter.java:79) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:170) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:182) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:182) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:182) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:182) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:182) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:182) at hudson.util.SecretRewriter.rewriteRecursive(SecretRewriter.java:143) at jenkins.security.RekeySecretAdminMonitor$RekeyThread.run(RekeySecretAdminMonitor.java:182) Caused by: java.io.IOException: Read-only file system at java.io.UnixFileSystem.createFileExclusively(Native Method) at java.io.File.checkAndCreate(File.java:1717) at java.io.File.createTempFile0(File.java:1738) at java.io.File.createTempFile(File.java:1815) at hudson.util.AtomicFileWriter.init(AtomicFileWriter.java:65) ... 10 more Environment: RHEL/CentOS Linux Fix Versions: current Project: Jenkins Labels: jenkins Priority: Minor Reporter: David Johansen This message is automatically generated by JIRA. 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] [promoted-builds] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
wgracelee commented on JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 When we upgraded Jenkins to 1.510, we saw the problem. But once we upgraded the promoted builds plugin to 2.10 (from 2.6.2), the problem went away. This message is automatically generated by JIRA. 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] [envinject] (JENKINS-17620) Inject env. vars in a pre-build step of a Maven project does not work
Marc Günther created JENKINS-17620 Inject env. vars in a pre-build step of a Maven project does not work Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 15/Apr/13 6:05 PM Description: You can "inject environment variables" in the "Build Environment" section, or as a build step. In a Maven project type, when I use a build step (pre build step in this case), the properties were not available in the maven step, whereas it worked when I used the Build Environment setting. In a Freestyle project, both version worked. Expected: A Pre build step "Inject Environment Variables" in a Maven Project should make those properties available to the main Maven build step Project: Jenkins Priority: Minor Reporter: Marc Günther This message is automatically generated by JIRA. 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-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Balder VC commented on JENKINS-17508 The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503. LogRotator delegates the delete to the actual Run, for just the log files the delete is delegated all the way to the MavenModuleSetBuild, however for the deleteArtifacts this is not done. My knowledge of the Jenkins code base is very small at the moment. Just starting to get a grasp of it. But here is what I mean, https://github.com/redlab/jenkins/commit/d4459d9d0f99b951974f6ab1bedf6a580a some lines of code can say more then words. I've ran all unit tests but didn't add one yet. ( if this could fix it I can create a pull request if you want ) This message is automatically generated by JIRA. 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] [perforce] (JENKINS-13332) OutOfMemoryError from Perforce polling
evernat resolved JENKINS-13332 as Cannot Reproduce OutOfMemoryError from Perforce polling If it has not occured again, resolving as can not reproduced. Please reopen if reproduced. Change By: evernat (15/Apr/13 7:32 PM) 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] [junit] (JENKINS-7970) If all JUnit tests are skipped, the build fails
Joel Beaudoin commented on JENKINS-7970 If all JUnit tests are skipped, the build fails Thanks mate. I missed the 'upcoming changes' link. This message is automatically generated by JIRA. 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] [envinject] (JENKINS-16233) EnvInject plugin using a cached value for ${WORKSPACE}
Bob Yao
commented on JENKINS-16233
EnvInject plugin using a cached value for ${WORKSPACE}
I'm getting this issue as well. I've restarted several times, but problem didn't go away. Let me know how I can help give you more info.
EnvInject - Loading node environment variables.
Building on master in workspace /home/jenkins/jobs/aura-snapshot-build/workspace
Checkout:workspace / /home/jenkins/jobs/aura-snapshot-build/workspace - hudson.remoting.LocalChannel@42e934e
Using strategy: Default
Last Built Revision: Revision 1092e00a1953421e0e65447d3aa0089f933fdc92 (origin/master-pending-update-copyright-headers)
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository OMIT
git --version
git version 1.7.0.4
Fetching upstream changes from origin
Cleaning workspace
Resetting working tree
Seen branch in repository origin/master-pending-update-copyright-headers
Commencing build of Revision 1092e00a1953421e0e65447d3aa0089f933fdc92 (origin/master-pending-update-copyright-headers)
Checking out Revision 1092e00a1953421e0e65447d3aa0089f933fdc92 (origin/master-pending-update-copyright-headers)
Cleaning workspace
Resetting working tree
No emails were triggered.
workspace $ /bin/bash -xe /tmp/hudson3897671398590473161.sh
+ mkdir -p /home/jenkins/jobs/~masterArtifactMonitor/workspace/tmp
mkdir -p ${WORKSPACE}/tmp
WORKSPACE=/home/jenkins/jobs/~masterArtifactMonitor/workspace
actual workspace should be /home/jenkins/jobs/aura-snapshot-build/workspace
This message is automatically generated by JIRA.
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-17621) Return quiet_down value in API
drnic commented on JENKINS-17621 Return quiet_down value in API I found the value in the node configuration XML. Unsure why its XML; but its in there. This message is automatically generated by JIRA. 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] [testlink] (JENKINS-17622) Cannot access TestLink environment variables within Jenkins build
Lisa Stanley created JENKINS-17622 Cannot access TestLink environment variables within Jenkins build Issue Type: Bug Assignee: Bruno P. Kinoshita Components: testlink Created: 16/Apr/13 12:06 AM Description: I'm configuring my first Jenkins / TestLink job. I don't seem to have access to any of the TestLink environment variables. I have pared down my Jenkins job to the following two statements under Build / Invoke TestLink / Test Execution / Single Build Steps / Execute Shell: echo "Test plan name is: $TESTLINK_TESTPLAN_NAME" echo "Build number is: $BUILD_NUMBER" The Jenkins console output is as follows: Started by user lisas Building in workspace /var/lib/jenkins/jobs/Website-Linkchecker-TestLink-integration/workspace Preparing TestLink client API. Using TestLink URL: http://localhost/testlink/lib/api/xmlrpc.php Found 1 automated test cases in TestLink. Sorting automated test cases by TestLink test plan execution order. Executing single Build Steps. workspace $ /bin/sh -xe /tmp/hudson8927570372825500742.sh + echo Test plan name is: Test plan name is: + echo Build number is: 8 Build number is: 8 Executing iterative Build Steps. Looking for the test results of TestLink test cases. Found 0 test result(s). Finished: SUCCESS As you can see, the $BUILD_NUMBER environment variable is translated as expected. The $TESTLINK_TESTPLAN_NAME environment variable is not. Any hints as to what might have gone wrong? Project: Jenkins Priority: Major Reporter: Lisa Stanley This message is automatically generated by JIRA. 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] [testlink] (JENKINS-17622) Cannot access TestLink environment variables within Jenkins build
Lisa Stanley commented on JENKINS-17622 Cannot access TestLink environment variables within Jenkins build Info I forgot to add: Jenkins version: 1.509 TestLink version: 1.9.6 Plugin version: 3.3 This message is automatically generated by JIRA. 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] [testlink] (JENKINS-17622) Cannot access TestLink environment variables within Jenkins build
Bruno P. Kinoshita commented on JENKINS-17622 Cannot access TestLink environment variables within Jenkins build Hi Lisa tl;dr: this information is (unfortunately) not available for single build steps. In the first versions of the plug-in, there were only iterative build steps. And during a huge code refactoring we added the result seeking strategies, but we didn't add environment variables to single build steps. I can't recall if there was any limitation, maybe in the TestLink XML-RPC API... I'll take a look on it, but if you have spare time to send a pull request, or any suggestions or questions just let me know :o) Thanks and sorry for missing this. I even had to use it once and I think I use some quick n' dirty script for that... /Bruno This message is automatically generated by JIRA. 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] [testlink] (JENKINS-17622) Cannot access TestLink environment variables within Jenkins build
Bruno P. Kinoshita started work on JENKINS-17622 Cannot access TestLink environment variables within Jenkins build Change By: Bruno P. Kinoshita (16/Apr/13 1:14 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] [testlink] (JENKINS-17622) Cannot access TestLink environment variables within Jenkins build
Lisa Stanley commented on JENKINS-17622 Cannot access TestLink environment variables within Jenkins build Bruno, Many thanks for the incredibly quick response! I'm mostly relieved that I wasn't doing something silly, since these tools are very new to me. I have moved my echo statements to the iterative build steps and confirmed that the results are as expected. So now I know what I have to work with for today. I'll see if I can generate any more requests for you this week! Thanks again for the very quick response. Lisa This message is automatically generated by JIRA. 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Kohsuke Kawaguchi commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online Consolidating to JENKINS-17366 This message is automatically generated by JIRA. 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] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Kohsuke Kawaguchi resolved JENKINS-17519 as Duplicate After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online Change By: Kohsuke Kawaguchi (16/Apr/13 1:28 AM) Status: Reopened 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] [ssh-slaves] (JENKINS-17366) ssh slave login via keyfile not working in 0.23
Kohsuke Kawaguchi commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 I've been trying the upgrade scenario today, and so far I have been unable to reproduce this problem. I created a passphrase-protected private key and used Jenkins 1.480 (with ssh-slaves plugin 0.22) to set up a slave. The slave also uses a different user name than what the master runs. I then upgraded to Jenkins 1.511, which uses the ssh-slaves plugin 0.23, and I see that the configuration has been successfully migrated, and the slave connected as it should be. So there must be something deeper going on that what it appears. I do agree with the poor error message. I have just fixed this. This would let us better understand what's going wrong. This error message fix will be in 0.24. This message is automatically generated by JIRA. 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] [testlink] (JENKINS-17622) Cannot access TestLink environment variables within Jenkins build
Bruno P. Kinoshita commented on JENKINS-17622 Cannot access TestLink environment variables within Jenkins build No worries Lisa, I was working on other issues for the next release. Keep an eye in the commit log, I'll try to include this issue in the next release. Cheers, /B This message is automatically generated by JIRA. 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] [ssh-slaves] (JENKINS-17366) ssh slave login via keyfile not working in 0.23
Kohsuke Kawaguchi commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 I've released 0.24 with improved error diagnostics. If you are seeing this problem, please upgrade to ssh-slaves 0.24 and report the error message in the slave log that you see. Also, as we still haven't quite determined the root cause yet, please report the type of the authentication method you use (username+password? private key? if so, with or without passphrase? do you specify the user name?) Thanks for your cooperation! This message is automatically generated by JIRA. 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] [ssh-slaves] (JENKINS-17366) ssh slave login via keyfile not working in 0.23
Kohsuke Kawaguchi started work on JENKINS-17366 ssh slave login via keyfile not working in 0.23 Change By: Kohsuke Kawaguchi (16/Apr/13 1:52 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] [ssh-slaves] (JENKINS-12374) hudson fails to connect unix slaves which are keonized
Kohsuke Kawaguchi resolved JENKINS-12374 as Fixed hudson fails to connect unix slaves which are keonized SSH slaves plugin 0.24 interprets "keyboard-interactive" as synonymous to the "password" authentication. Change By: Kohsuke Kawaguchi (16/Apr/13 1:53 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-8183) ssh connection failed when login banner is too long
Kohsuke Kawaguchi commented on JENKINS-8183 ssh connection failed when login banner is too long Note that this is not a login banner but the comment in the SSH protocol version exchange, which is normally used for a server implementation name. According to RFC 4253, this comment section can be only up to 255 chars, so 512 bytes are plenty. Note that you'll also see this error if something other than SSHD is running on port 22. This message is automatically generated by JIRA. 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] [ssh-slaves] (JENKINS-8183) ssh connection failed when login banner is too long
Kohsuke Kawaguchi resolved JENKINS-8183 as Not A Defect ssh connection failed when login banner is too long Given that it tolerates two times what's specified in RFC, I'm closing this as not a defect. Change By: Kohsuke Kawaguchi (16/Apr/13 2:03 AM) Status: InProgress 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] [ssh-slaves] (JENKINS-8183) ssh connection failed when login banner is too long
SCM/JIRA link daemon commented on JENKINS-8183 ssh connection failed when login banner is too long Code changed in jenkins User: Kohsuke Kawaguchi Path: src/com/trilead/ssh2/transport/ClientServerHello.java http://jenkins-ci.org/commit/trilead-ssh2/d2e7f313c83d6d87f03bfffbf0b3f9628377694d Log: JENKINS-8183 report what's read thus far to assist the trouble-shooting in case something other than SSHD is running on port 22. This message is automatically generated by JIRA. 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] [ssh] (JENKINS-17256) Unexpected error in launching a slave (NegativeArraySizeException)
Kohsuke Kawaguchi commented on JENKINS-17256 Unexpected error in launching a slave (NegativeArraySizeException) bogdan d, your PuTTY private key file must be in a newer format that Jenkins doesn't understand. Can you provide us a mangled version of your private key? If you change the base64 encoded in your key file and fill it by 'A', that won't reveal your actual secret key, but it'll provide us necessary information about the structure of the file we need to address the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
Kenny Ayers commented on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content We are seeing file contents double when using SVN mv commands as well. This means files that are svn mv'd to a location, then added back to the repo have their contents duplicated. Versions: Jenkins: 1.508 Jenkins Subversion Plug-in: 1.45 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
