[JIRA] [exclusive-execution-plugin] (JENKINS-24854) Exclusive Execution Plugin stays in shutdown mode if build aborts
Fernando Miguelez assigned JENKINS-24854 to Fernando Miguelez Exclusive Execution Plugin stays in shutdown mode if build aborts Change By: Fernando Miguelez (09/Jan/15 8:09 AM) Assignee: Marco Ambu Fernando Miguelez This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [exclusive-execution-plugin] (JENKINS-26175) Allow exclusive execution plugin skip wait for end of execution of jobs
Fernando Miguelez assigned JENKINS-26175 to Fernando Miguelez Allow exclusive execution plugin skip wait for end of execution of jobs Change By: Fernando Miguelez (09/Jan/15 8:10 AM) Assignee: Marco Ambu Fernando Miguelez This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25070) Subversion fails to update externals once after external is changed.
sirwiö sirwiö commented on JENKINS-25070 Subversion fails to update externals once after external is changed. We are facing the exact problems as described in the description by the original reporter on a very similar repository setup. It is 100% reproducable. This is with Jenkins 1.580.2 and Subversion Plug-in 2.5 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [exclusive-execution-plugin] (JENKINS-26351) Spanish translation
Fernando Miguelez created JENKINS-26351 Spanish translation Issue Type: New Feature Assignee: Fernando Miguelez Components: exclusive-execution-plugin Created: 09/Jan/15 8:14 AM Description: Translation into Spanish is desired. Project: Jenkins Priority: Minor Reporter: Fernando Miguelez This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [xcode-plugin] (JENKINS-25433) Xcodebuild sigining fails
lacostej resolved JENKINS-25433 as Not A Defect Xcodebuild sigining fails Not a bug in jenkins, but in xcrun. We could detect from the output that xcode is buggy, and add a jenkins specific warning message. Any other idea ? Change By: lacostej (09/Jan/15 8:42 AM) Status: Reopened Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26349) Save buttons don't show properly on long pages
Daniel Beck resolved JENKINS-26349 as Duplicate Save buttons don't show properly on long pages Duplicates JENKINS-26312 Change By: Daniel Beck (09/Jan/15 8:45 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/d/optout.
[JIRA] [perforce-plugin] (JENKINS-15698) Perforce can't get hostname for slaves
Oleg Nenashev
commented on JENKINS-15698
Perforce can't get hostname for slaves
According to Javadoc, hostname is null if...
> ... if the host name cannot be computed (for example because this computer is offline, because the slave is behind the firewall, etc.)
The hostname is being calculated using java.net.InetAddress::getCanonicalHostName(), so the real result depends on the implementation in JVM. I see a glitch in Perforce Plugin code, which may cause an NPE. However, it should not cause the described behavior.
Currently, the most of plugin EnvVar substitutions will fail if they really need ${hostname}.
I would vote for merging https://github.com/jenkinsci/perforce-plugin/pull/66
This message is automatically generated by JIRA.
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/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-22492) java.io.IOException: Pipe broken
lacostej commented on JENKINS-22492 java.io.IOException: Pipe broken Johannes, is this 100% reproducible ? I don't yet know why the pipe breaks. Have you tried looking at specific errors in the Editor.log file? Are they displayed under the job console ? This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26349) Save buttons don't show properly on long pages
Josh Taylor commented on JENKINS-26349 Save buttons don't show properly on long pages Ahh, tried searching but couldn't find it, sorry! This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25070) Subversion fails to update externals once after external is changed.
James Noonan commented on JENKINS-25070 Subversion fails to update externals once after external is changed. Hello Sirwio: A bit of relief that it's no longer so unique For us, the problem has not occurred for quite a while. We performed a number of steps to help, but there is no step we carried out that definitely stopped it. Two things that may have helped are that we removed the number of nodes (though it's increased again since) and removed the VM Node Plugin. The VM Node Plugin caused a lot of disconnect/connect events, so we thought that that might be a cause of stress. After removing, the problem occurred one more time. So, two questions: How do you reproduce this problem. We never had a set of steps that would make the problem happen. And perhaps we should compare our list of plug-ins / versions. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [digitalocean-plugin] (JENKINS-26352) Cannot create Jenkins slaves
arazauci
created JENKINS-26352
Cannot create Jenkins slaves
Issue Type:
Bug
Assignee:
Unassigned
Components:
digitalocean-plugin
Created:
09/Jan/15 9:30 AM
Description:
The plugin is not able to create jenkins slave. The jenkins logs show the following exception message (hidding some of my details)
com.myjeeva.digitalocean.exception.RequestUnsuccessfulException: DigitalOcean API request unsuccessful, possible reason colud be incorrect values https://api.digitalocean.com/droplets/new/?client_id=xx&api_key=&name=jenkins_ea8482b1-665c-4d5b-805d-a5bbe35c50c3®ion_id=3&ssh_key_ids=xxx&image_id=xxx&size_id=63.
DigitalOcean support says that the plugin has invalid values for host name
As for the API call itself, it appears that your hostname in the call contains invalid characters:
{"status":"ERROR","error_message":"Name Only valid hostname characters are allowed. (a-z, A-Z, 0-9, . and -)","message":"Name Only valid hostname characters are allowed. (a-z, A-Z, 0-9, . and -)"}
Please try again using another hostname.
Project:
Jenkins
Priority:
Blocker
Reporter:
arazauci
This message is automatically generated by JIRA.
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/d/optout.
[JIRA] [copy-to-slave-plugin] (JENKINS-26353) Copy to slave fails and getting error message "Pipe is already closed"
Atul Kote created JENKINS-26353 Copy to slave fails and getting error message "Pipe is already closed" Issue Type: Bug Assignee: Vivekanand SV Components: copy-to-slave-plugin Created: 09/Jan/15 9:40 AM Description: After upgrading the latest jenkins version, getting continuous error message ""Pipe is already closed" while trying to access from master to slave. This is really scratch our heads. Now, we have jenkins version "1.596". Please look at this issue asap as this blocks our day to day work. "[copy-to-slave] Copying ' .pl, Include//, noarch/*/, .jar, *.zip, Test-XML//, tools-linux/*/, tools-solaris/*/, tools-windows/*/ ', excluding nothing, from 'file:/var/lib/jenkins/userContent/' on the master to 'file:/C:/Test/' on 'WIN2K8-X64'. FATAL: Pipe is already closed java.io.IOException: Pipe is already closed at hudson.remoting.PipeWindow.checkDeath(PipeWindow.java:108) at hudson.remoting.PipeWindow$Real.get(PipeWindow.java:203) at hudson.remoting.ProxyOutputStream._write(ProxyOutputStream.java:141) at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:109) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) at java.io.BufferedOutputStream.write(BufferedOutputStream.java:126) at com.jcraft.jzlib.DeflaterOutputStream.deflate(DeflaterOutputStream.java:144) at com.jcraft.jzlib.DeflaterOutputStream.write(DeflaterOutputStream.java:102) at java.io.BufferedOutputStream.write(BufferedOutputStream.java:122) at org.apache.tools.tar.TarBuffer.writeBlock(TarBuffer.java:410) at org.apache.tools.tar.TarBuffer.writeRecord(TarBuffer.java:351) at hudson.org.apache.tools.tar.TarOutputStream.writeEOFRecord(TarOutputStream.java:356) at hudson.org.apache.tools.tar.TarOutputStream.finish(TarOutputStream.java:137) at hudson.org.apache.tools.tar.TarOutputStream.close(TarOutputStream.java:149) at hudson.util.io.TarArchiver.close(TarArchiver.java:125) at com.michelin.cio.hudson.plugins.copytoslave.MyFilePath.writeToTar(MyFilePath.java:230) at com.michelin.cio.hudson.plugins.copytoslave.MyFilePath.copyRecursiveTo(MyFilePath.java:143) at com.michelin.cio.hudson.plugins.copytoslave.CopyToSlaveBuildWrapper.setUp(CopyToSlaveBuildWrapper.java:133) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.io.IOException: Pipe is already closed at hudson.remoting.FastPipedOutputStream.write(FastPipedOutputStream.java:153) at hudson.remoting.FastPipedOutputStream.write(FastPipedOutputStream.java:137) at hudson.remoting.ProxyOutputStream$Chunk$1.run(ProxyOutputStream.java:264) at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Caused by: hudson.remoting.FastPipedInputStream$ClosedBy: The pipe was closed at... at hudson.remoting.FastPipedInputStream.close(FastPipedInputStream.java:112) at com.michelin.cio.hudson.plugins.copytoslave.MyFilePath$2.invoke(MyFilePath.java:138) at com.michelin.cio.hudson.plugins.copytoslave.MyFilePath$2.invoke(MyFilePath.java:130) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2677) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request
[JIRA] [compact-columns-plugin] (JENKINS-26336) Compact Columns Plugin does not play well with Folders Plugin
Rich Kang commented on JENKINS-26336 Compact Columns Plugin does not play well with Folders Plugin Yes that is correct. I believe I've already fixed it (it seems to be a pretty simple one). I mainly put this issue in as the pull request hadn't been picked up by anyone. The code is here: https://github.com/jenkinsci/compact-columns-plugin/pull/1 I'm not sure why that test failed (the colour one) as it doesn't when I run mvn test locally. And I believe the two lines I've changed in the jelly files are unlikely to be affecting that? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Hans Marggraff commented on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. Daniel: I have tried it with three different Jenkins configurations all running on Linux servers against the same repository (Server version Subversion 1.6.11 (r934486)). It is managed by enterprise it, so I can not do anything about it. (Its a global Bank, so upgrading software is extremely conservative) However it works on a very old installation of Jenkins, so the server does not seem to be the problem: 1. Jenkins 1.549, Credentials plugin 1.9.4, Subversion Plugin 1.54, Subversion Workspace format 1.6 It fails after upgrading to newer versions of Jenkins: 2. Jenkins version 1594, Credentials Plugin 1.20, subversion plugin 2.5, Workspace format 1.6 3. Jenkins 1.596, Credentials Plugin 1.19, subversion plugin 2.4.5, Workspace format 1.7 To me it is the credentials plugin (or its use by the subversion plugin), that seems most suspicious. The upgrade made it a lot more complicated in a way, that we neither need nor want. Also Idea configured to use svnkit does not have any problems with the externals setup from my local windows development machine. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Hans Marggraff updated JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. This is what our subversion configuration with credentials looks like. Maybe something is wrong there? Change By: Hans Marggraff (09/Jan/15 9:54 AM) Attachment: hans-marggraff-jenkins-externals credentials-config.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Hans Marggraff updated JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. Change By: Hans Marggraff (09/Jan/15 9:56 AM) Attachment: Jenkins-externals .png This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [job-restrictions-plugin] (JENKINS-25771) Add "started by a member of group" JobRestriction
Oleg Nenashev started work on JENKINS-25771 Add "started by a member of group" JobRestriction Change By: Oleg Nenashev (09/Jan/15 10:05 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-restrictions-plugin] (JENKINS-25771) Add "started by a member of group" JobRestriction
Oleg Nenashev assigned JENKINS-25771 to Christopher Suarez Add "started by a member of group" JobRestriction Change By: Oleg Nenashev (09/Jan/15 10:06 AM) Assignee: Christopher Suarez This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Rickard Lebbin
commented on JENKINS-26312
Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Adding this to the end of style.css worked for me. It't not pretty but it works.
#footer {
display: none;
padding: 3px 0px;
}
#footer-container:hover > #footer, #footer td{
display: inherit;
padding: 10px 0px;
}
This message is automatically generated by JIRA.
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/d/optout.
[JIRA] [exclusive-execution-plugin] (JENKINS-26175) Allow exclusive execution plugin skip wait for end of execution of jobs
Fernando Miguelez commented on JENKINS-26175 Allow exclusive execution plugin skip wait for end of execution of jobs Pull-request submitted: https://github.com/jenkinsci/exclusive-execution-plugin/pull/4 Awaiting approval. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [exclusive-execution-plugin] (JENKINS-26351) Spanish translation
Fernando Miguelez commented on JENKINS-26351 Spanish translation Pull-request submitted: https://github.com/jenkinsci/exclusive-execution-plugin/pull/4 Awaiting approval. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [exclusive-execution-plugin] (JENKINS-24854) Exclusive Execution Plugin stays in shutdown mode if build aborts
Fernando Miguelez commented on JENKINS-24854 Exclusive Execution Plugin stays in shutdown mode if build aborts Pull-request submitted: https://github.com/jenkinsci/exclusive-execution-plugin/pull/4 Awaiting approval. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [git-plugin] (JENKINS-26354) Git polling found changes but they are not displayed in Changes section
Max Usachev updated JENKINS-26354 Git polling found changes but they are not displayed in Changes section Change By: Max Usachev (09/Jan/15 10:45 AM) Summary: Git polling found changes but they are not displayed in Changes section This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [git-plugin] (JENKINS-26354) Git polling found changes but they are not displayed in Changes
Max Usachev created JENKINS-26354 Git polling found changes but they are not displayed in Changes Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 09/Jan/15 10:44 AM Description: Suppose, we have master branch. Then we checkout to a new branch, lets name it branch1: git checkout -b branch1 Then we do some commits: echo "a" > a.txt && git add a.txt && git commit -m 'Added file: a.txt' echo "b" > b.txt && git add b.txt && git commit -m 'Added file: b.txt' Then we push our branch to Git repository: git push origin branch1 In Jenkins, Git polling reports: ... Seen branch in repository origin/branch1 Seen XXX remote branches > /usr/bin/git log --full-history --no-abbrev --format=raw -M -m --raw 0a6eb107fea5bb6371c450db1b5f6e100e0fba28..d8c5018ca184fb75e46386de2f16e552906fe106 # timeout=10 Done. Took 3.5 sec Changes found but Changes section shows nothing, it means, that no changes were made. Nevertheless, build was triggered. The problem is deeper, suppose our build runs unit tests, and they failed. In that case, no emails will be send to committers, because of no changes. We have caught this case and got a problems I think, it's a bug, because 2 new commits were created and Jenkins should show it in Changes section. Environment: Jenkins ver. 1.591 Git plugin 2.3.3 GIT client plugin 1.15.0 Project: Jenkins Labels: git-plugin polling pollscm git Priority: Major Reporter: Max Usachev This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26355) Jenkins bottom-sticker, wrong position under footer-container
Martin Zajic created JENKINS-26355 Jenkins bottom-sticker, wrong position under footer-container Issue Type: Bug Assignee: Unassigned Attachments: bug_jenkins.png Components: core Created: 09/Jan/15 10:51 AM Description: In job config, bottom-sticker with save buttons is hidden behind footer-container. It's css is set to bottom:0px and should be above bottom: 37px (footer height) Environment: Jenkins ver. 1.596 AnsiColor 0.4.1 Ant Plugin 1.2 Credentials Plugin 1.20 CVS Plug-in 2.12 External Monitor Job Type Plugin 1.4 GIT client plugin 1.15.0 GIT plugin 2.3.4 HTML5 Notifier Plugin 1.3 Hudson Post build task 1.8 Javadoc Plugin 1.3 JUnit Plugin 1.3 LDAP Plugin 1.11 Mailer Plugin 1.12 MapDB API Plugin 1.0.6.0 Matrix Authorization Strategy Plugin 1.2 Matrix Project Plugin 1.4 Maven Integration plugin 2.8 OWASP Markup Formatter Plugin 1.3 PAM Authentication plugin 1.2 Pre SCM BuildStep Plugin 0.3 Role-based Authorization Strategy 2.2.0 SCM API Plugin 0.2 SSH Credentials Plugin 1.10 SSH Slaves plugin 1.9 Subversion Plug-in 2.5 Translation Assistance plugin 1.12 Windows Slaves Plugin 1.0 Project: Jenkins Priority: Trivial Reporter: Martin Zajic This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26355) Jenkins bottom-sticker, wrong position under footer-container
Martin Zajic resolved JENKINS-26355 as Duplicate Jenkins bottom-sticker, wrong position under footer-container Sorry duplicate to https://issues.jenkins-ci.org/browse/JENKINS-26312 Change By: Martin Zajic (09/Jan/15 10:53 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/d/optout.
[JIRA] [core] (JENKINS-26356) Unable tail pages in Console Output from version 1.596
Petr Rocen created JENKINS-26356 Unable tail pages in Console Output from version 1.596 Issue Type: Bug Assignee: Unassigned Components: core Created: 09/Jan/15 11:10 AM Description: When running any job Doesn't work tail page in console output after I installed version 1.596. Please fix for this functionality Petr Ročeň Environment: Jenkins version 1.596 Project: Jenkins Priority: Critical Reporter: Petr Rocen This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [call-remote-job-plugin] (JENKINS-20856) Call Remote jenkins job plugin bad pass parameters from list subversion tags
Petr Rocen closed JENKINS-20856 as Fixed Call Remote jenkins job plugin bad pass parameters from list subversion tags Change By: Petr Rocen (09/Jan/15 11:14 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge-plugin] (JENKINS-26357) Unable to create a Feature Branch
Hugues Chabot started work on JENKINS-26357 Unable to create a Feature Branch Change By: Hugues Chabot (09/Jan/15 11:38 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge-plugin] (JENKINS-26357) Unable to create a Feature Branch
Hugues Chabot created JENKINS-26357 Unable to create a Feature Branch Issue Type: Bug Assignee: Hugues Chabot Components: svnmerge-plugin Created: 09/Jan/15 11:38 AM Description: I cannot create a "Feature Branch" when using svnmerge plugin 2.4 and subversion plugin 2.5 but I can if I use subversion plugin 2.4.x. _Note: If I create the SVN branch and the Jenkins job manually, I still cannot rebase (see JENKINS-26347). Here is the stack trace. javax.servlet.ServletException: hudson.scm.SubversionSCM.createAuthenticationProvider(Lhudson/model/AbstractProject;Lhudson/scm/SubversionSCM$ModuleLocation;)Lorg/tmatesoft/svn/core/auth/ISVNAuthenticationProvider; at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) 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(HudsonFil
[JIRA] [svnmerge-plugin] (JENKINS-26357) Unable to create a Feature Branch
Hugues Chabot
updated JENKINS-26357
Unable to create a Feature Branch
Change By:
Hugues Chabot
(09/Jan/15 11:39 AM)
Description:
I cannot create a "Feature Branch" when using svnmerge plugin 2.4 and subversion plugin 2.5 but I can if I use subversion plugin 2.4.x.
_Note
Note
: If I create the SVN branch and the Jenkins job manually, I still cannot rebase (see JENKINS-26347).
_
Here is the stack trace.{noformat}javax.servlet.ServletException: hudson.scm.SubversionSCM.createAuthenticationProvider(Lhudson/model/AbstractProject;Lhudson/scm/SubversionSCM$ModuleLocation;)Lorg/tmatesoft/svn/core/auth/ISVNAuthenticationProvider; at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) 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 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.kohsuke.stapler.compre
[JIRA] [svnmerge-plugin] (JENKINS-26357) Unable to create a Feature Branch
Hugues Chabot
updated JENKINS-26357
Unable to create a Feature Branch
Change By:
Hugues Chabot
(09/Jan/15 11:39 AM)
Description:
I cannot create a "Feature Branch" when using svnmerge plugin 2.4 and subversion plugin 2.5 but I can if I use subversion plugin 2.4.x._Note: If I create the SVN branch and the Jenkins job manually, I still cannot rebase (see JENKINS-26347).
_
Here is the stack trace.{noformat}javax.servlet.ServletException: hudson.scm.SubversionSCM.createAuthenticationProvider(Lhudson/model/AbstractProject;Lhudson/scm/SubversionSCM$ModuleLocation;)Lorg/tmatesoft/svn/core/auth/ISVNAuthenticationProvider; at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) 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 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.kohsuke.stapler.compression.C
[JIRA] [subversion-plugin] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
Helge Willum Larsen commented on JENKINS-17431 500 Internal Server Error on attempt to run a build We too experienced these issues. During an earlier import from another repository, 45378 revisions had been left without a svn:date property, which caused the HTTP 500 error. The svn:date properties were fixed using the set-svn-date script from http://docs.codehaus.org/display/HAUSMATES/Could+not+access+revision+times (BTW: If you are going to use that script, you have to fix generate_propsets to take in an URL parameter) This is still a major problem, as we cannot prevent this from happening again while allowing our developers to do svn revprop changes (which is necessary). I think this logic of using revision datestamps is severely flawed, because you cannot trust the timestamps in any way! Even if you make sure that every revision has an svn:date timestamp, there are several scenarios which can result in an inconsistent timeline. The revision numbers are "right there" and easy to get, and they are guaranteed to be consistent - why not use them? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26354) Git polling found changes but they are not displayed in Changes section
Mark Waite commented on JENKINS-26354 Git polling found changes but they are not displayed in Changes section I can't duplicate the bug based on the steps you've provided. Can you provide more details or clarify the areas in which my steps are different than your steps? Steps I took: Create a new git repo ( repo=~/git/bugs/JENKINS-26534; mkdir -p $repo; cd $repo; git init ) Commit a change to that repo ( branch=master; date >> $branch; git add $branch; git commit -m "Add date to $branch" ) Create a freestyle project to monitor that repo ( poll git often, or create a post-receive hook ) Define "Branches to build" as "*" so that any branch which appears will start a build Confirm that the project builds on its first polling interval Confirm that the log of the first build contains the line "First time build. Skipping changelog." Confirm that Changes and Recent Changes show no change for that first time build Add a branch to the repo with a commit ( branch=branch-a; git checkout -b $branch; date >> $branch; git add $branch; git commit -m "Add date to $branch" ) Confirm that the next poll starts that job Confirm that the console output contains the line "First time build. Skipping changelog." Commit a second change to the branch (branch=branch-a; git checkout $branch; date >> $branch; git add $branch; git commit -m "Add date to $branch" ) Confirm that the next poll starts that job Confirm that the changes show the commit (since it is not a first time build) Is the bug you're reporting that the first time build for a new branch does not list any changes? If so, it is difficult to make a good general case decision of what should be the basis of those changes. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
SCM/JIRA link daemon commented on JENKINS-25601 JDK9 with jigsaw file layer is not detected as valid JDK Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/JDK.java http://jenkins-ci.org/commit/jenkins/b33b921dc5d4dacdca7a9b73cfbe6f8a57f05307 Log: JENKINS-25601 Noting merge of #1499. Compare: https://github.com/jenkinsci/jenkins/compare/75eeccf8668e...b33b921dc5d4 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
SCM/JIRA link daemon commented on JENKINS-25601 JDK9 with jigsaw file layer is not detected as valid JDK Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/JDK.java http://jenkins-ci.org/commit/jenkins/1186e7b4047a70162a1a3be399fc449ae3b0e1f5 Log: [FIXED JENKINS-25601] Amend JAVA_HOME check to work with JDK 9 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
SCM/JIRA link daemon resolved JENKINS-25601 as Fixed JDK9 with jigsaw file layer is not detected as valid JDK Change By: SCM/JIRA link daemon (09/Jan/15 12:18 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-25338) list-jobs cli
SCM/JIRA link daemon resolved JENKINS-25338 as Fixed list-jobs cli Change By: SCM/JIRA link daemon (09/Jan/15 12:22 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Jean Blanchard commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name I created a pull request [1] to address the issue mentioned by Antoine Morisseau (polling should take the default value of a param, not the one from the last build). It also fixes the commit notification for those parametrized jobs. [1] https://github.com/jenkinsci/git-plugin/pull/293 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [cli] (JENKINS-25338) list-jobs cli
SCM/JIRA link daemon commented on JENKINS-25338 list-jobs cli Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/cli/ListJobsCommand.java http://jenkins-ci.org/commit/jenkins/8e5199e377c748907b823bdcbbbda223e3e43c80 Log: JENKINS-25338 Noting merge of #1497. Compare: https://github.com/jenkinsci/jenkins/compare/b33b921dc5d4...8e5199e377c7 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [cli] (JENKINS-25338) list-jobs cli
SCM/JIRA link daemon commented on JENKINS-25338 list-jobs cli Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/cli/ListJobsCommand.java http://jenkins-ci.org/commit/jenkins/2647af48c81e17ea17bfb144bf804abea22530fe Log: [FIXED JENKINS-25338] Show job name rather than display name in 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/d/optout.
[JIRA] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
SCM/JIRA link daemon commented on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly http://jenkins-ci.org/commit/jenkins/44e6b5d76211bc40e1a608ae3aa93c083befaeba Log: [FIXED JENKINS-22311] Show queue item parameters in tool tip This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
SCM/JIRA link daemon resolved JENKINS-22311 as Fixed Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history Change By: SCM/JIRA link daemon (09/Jan/15 12:26 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-23493) Unable to checkout from svn
Helge Willum Larsen commented on JENKINS-23493 Unable to checkout from svn Perhaps you are experiencing this issue: https://issues.jenkins-ci.org/browse/JENKINS-17431 Check your web server error.log for "Could not access revision times" If this is your issue, there's some more information and a possible fix here: http://docs.codehaus.org/display/HAUSMATES/Could+not+access+revision+times (btw: if you are going to try the Ruby script, modify the generate_propsets function to include a URL parameter) This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
SCM/JIRA link daemon commented on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly http://jenkins-ci.org/commit/jenkins/7ef3d0bbf0f5250ac28797193eb105a06454d904 Log: JENKINS-22311 Noting merge of #1492. Compare: https://github.com/jenkinsci/jenkins/compare/8e5199e377c7...7ef3d0bbf0f5 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [git-plugin] (JENKINS-26354) Git polling found changes but they are not displayed in Changes section
Mark Waite commented on JENKINS-26354 Git polling found changes but they are not displayed in Changes section I confirmed that a multi-branch job (recently added plugin which allows a git or subversion based job to create a new job for each new branch detected) behaves similarly. The first build of a new job lists in the console output that it is a first time build and is not computing the changelog. Subsequent builds compute the changelog. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [git-plugin] (JENKINS-26350) nullpointer exception with git checkout branch / tag
Mark Waite commented on JENKINS-26350 nullpointer exception with git checkout branch / tag I am unable to duplicate this problem using the Jenkins long term support version, 1.580.2. I tried both a tag as selected by the git parameter plugin, and a tag as selected by a string parameter. Can you confirm that you can duplicate the problem on the latest Jenkins long term support version? I may be using the wrong steps to duplicate the problem. The steps I took: Create a new bare git repository (/var/lib/git/mwaite/bugs/JENKINS-26350.git) Clone that bare git repository and push some changes to it Create a tag and push the tag (I created master-tag-01) Define a freestyle project using that repository as a parameterized build with a Git parameter using a tag Run the job once so that the list of tags can be read Confirm the git parameter in the build shows the master-tag-01 Add commits and a tag and push them to the bare repository Confirm the git parameter shows the new tag Confirm the build run with that new tag uses the expected SHA1 Remove the Git parameter and replace it with a string parameter Run the job with that string parameter set to the name of the new tag Confirm the job uses that string parameter without error and without stack trace This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [groovy-plugin] (JENKINS-26070) Unable to add multiple jars to classpath with wildcard
SCM/JIRA link daemon commented on JENKINS-26070 Unable to add multiple jars to classpath with wildcard Code changed in jenkins User: Vojtech Juranek Path: src/test/java/hudson/plugins/groovy/ClassPathTest.java src/test/resources/lib/groovy-cp-test.jar http://jenkins-ci.org/commit/groovy-plugin/485ba4ace71be1b4c140c20235fdd9c31dd13f72 Log: JENKINS-26070 Test that class path can contain wild cards This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-24519) Flyweight tasks only use one-off executor when they can be scheduled immediately
SCM/JIRA link daemon commented on JENKINS-24519 Flyweight tasks only use one-off executor when they can be scheduled immediately Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/LoadBalancer.java core/src/main/java/hudson/model/Queue.java core/src/main/java/jenkins/model/Jenkins.java test/src/test/java/hudson/model/QueueTest.java http://jenkins-ci.org/commit/jenkins/9e333bc1e60dd82b9983135276f9379d3eb4d392 Log: JENKINS-10944 JENKINS-24519 Noting merge of #1513. Compare: https://github.com/jenkinsci/jenkins/compare/7ce51328d515...9e333bc1e60d This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-10944) MatrixProject can run on a heavyweight executor, leading to deadlocks
SCM/JIRA link daemon commented on JENKINS-10944 MatrixProject can run on a heavyweight executor, leading to deadlocks Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/LoadBalancer.java core/src/main/java/hudson/model/Queue.java core/src/main/java/jenkins/model/Jenkins.java test/src/test/java/hudson/model/QueueTest.java http://jenkins-ci.org/commit/jenkins/9e333bc1e60dd82b9983135276f9379d3eb4d392 Log: JENKINS-10944 JENKINS-24519 Noting merge of #1513. Compare: https://github.com/jenkinsci/jenkins/compare/7ce51328d515...9e333bc1e60d This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-24519) Flyweight tasks only use one-off executor when they can be scheduled immediately
SCM/JIRA link daemon commented on JENKINS-24519 Flyweight tasks only use one-off executor when they can be scheduled immediately Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Queue.java test/src/test/java/hudson/model/QueueTest.java http://jenkins-ci.org/commit/jenkins/3e344a94a9eed316d0c351becb08287b473b6521 Log: [FIXED JENKINS-10944] [FIXED JENKINS-24519] If makeBuildable fails on a FlyweightTask, keep it in queue. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-10944) MatrixProject can run on a heavyweight executor, leading to deadlocks
SCM/JIRA link daemon commented on JENKINS-10944 MatrixProject can run on a heavyweight executor, leading to deadlocks Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Queue.java test/src/test/java/hudson/model/QueueTest.java http://jenkins-ci.org/commit/jenkins/3e344a94a9eed316d0c351becb08287b473b6521 Log: [FIXED JENKINS-10944] [FIXED JENKINS-24519] If makeBuildable fails on a FlyweightTask, keep it in queue. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-10944) MatrixProject can run on a heavyweight executor, leading to deadlocks
Jesse Glick resolved JENKINS-10944 as Fixed MatrixProject can run on a heavyweight executor, leading to deadlocks Change By: Jesse Glick (09/Jan/15 1:00 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24519) Flyweight tasks only use one-off executor when they can be scheduled immediately
Jesse Glick resolved JENKINS-24519 as Fixed Flyweight tasks only use one-off executor when they can be scheduled immediately Change By: Jesse Glick (09/Jan/15 1:00 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26350) nullpointer exception with git checkout branch / tag
Mark Waite
edited a comment on JENKINS-26350
nullpointer exception with git checkout branch / tag
I am unable to duplicate this problem using the Jenkins long term support version, 1.580.2. I tried both a tag as selected by the git parameter plugin, and a tag as selected by a string parameter.
Can you confirm that you can duplicate the problem on the latest Jenkins long term support version? I may be using the wrong steps to duplicate the problem.
The steps I took:
Create a new bare git repository (/var/lib/git/mwaite/bugs/JENKINS-26350.git)
Clone that bare git repository and push some changes to it
Create a tag and push the tag (I created master-tag-01)
Define a freestyle project using that repository as a parameterized build with a Git parameter using a tag
Run the job once so that the list of tags can be read
Confirm the git parameter in the build shows the master-tag-01
Add commits and a tag and push them to the bare repository
Confirm the git parameter shows the new tag
Confirm the build run with that new tag uses the expected SHA1
Remove the Git parameter and replace it with a string parameter (I named my parameter TagToBuild)
Change the "Branches to build" to refer to the string parameter (${TagToBuild} in my case)
Run the job with that string parameter set to the name of the new tag
Confirm the job uses that string parameter without error and without stack trace
This message is automatically generated by JIRA.
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/d/optout.
[JIRA] [groovy-plugin] (JENKINS-26070) Unable to add multiple jars to classpath with wildcard
vjuranek resolved JENKINS-26070 as Fixed Unable to add multiple jars to classpath with wildcard Hi, I tested that class paths with wild cards are expanded and added automated test for it (see previous comment). If doesn't work for you, please make sure you have recent java and groovy version (IIRC wildcard support was added in java 6 and in groovy since 1.7.1). If you have recent java and groovy and still doesn't work, please reopen with more details about your environment. Change By: vjuranek (09/Jan/15 1:03 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/d/optout.
[JIRA] [git-plugin] (JENKINS-26350) nullpointer exception with git checkout branch / tag
yann collette commented on JENKINS-26350 nullpointer exception with git checkout branch / tag Thanks for the procedure, I will try to do this ASAP. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-26327) Git or Git Client Plugin Appending Additional Slash To Git SSH Url Scheme
Mark Waite resolved JENKINS-26327 as Not A Defect Git or Git Client Plugin Appending Additional Slash To Git SSH Url Scheme I'm resolving this as "Not A Defect" since the ssh URL format being used in this bug report does not support a relative path. Use the scp URL format as described in the stackoverflow article for repositories with relative paths. Change By: Mark Waite (09/Jan/15 1:08 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25601) JDK9 with jigsaw file layer is not detected as valid JDK
dogfood commented on JENKINS-25601 JDK9 with jigsaw file layer is not detected as valid JDK Integrated in jenkins_main_trunk #3923 [FIXED JENKINS-25601] Amend JAVA_HOME check to work with JDK 9 (Revision 1186e7b4047a70162a1a3be399fc449ae3b0e1f5) Result = SUCCESS daniel-beck : 1186e7b4047a70162a1a3be399fc449ae3b0e1f5 Files : core/src/main/java/hudson/model/JDK.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/d/optout.
[JIRA] [git-plugin] (JENKINS-26354) Git polling found changes but they are not displayed in Changes section
Max Usachev commented on JENKINS-26354 Git polling found changes but they are not displayed in Changes section Yes, the problem related to the first time build for new branch, which was discovered by Git polling. For the next changes in existing remote branch changes are shown correct. I don't know details of the implementation of Git plugin, but it seems to me, that plugin can store list of all commit hashes of repository and when it see new remote branch, try to find those commits which are in new branch but not in commits store. And then build changelog based on these commits. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [gerrit-plugin] (JENKINS-26323) The "Build Current Patches Only" only works, if NO parameters in the build are altered
SCM/JIRA link daemon commented on JENKINS-26323 The "Build Current Patches Only" only works, if NO parameters in the build are altered Code changed in jenkins User: Martin Schroeder Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/97b08eebefcc27a165063212fa7efefc66b89531 Log: JENKINS-26323 Fix "Build Current Patches Only" by scanning for event The "Build Current Patches Only" feature currently identifies previous builds based on their parameters as they were present when the build was first scheduled. If you use a plugin that alters the parameters after the job has started, the cancelling of previous builds does not work, since the GerritTrigger#cancelJob() method does not find the job anymore. This is easily and trivially fixed, by not scanning for the parameters, but instead for the GerritEvent that is stored in the GerritCause used to start a build. The only downside to this is, that the current patch-set scans for identity, but not equality of the two events. After a Jenkins restart, they might not be identical anymore, since Jenkins reschedules queued builds and can't unify the two events via Stapler; as they are stored in separate files. It'd be trivially easy to alter this to Event.equals(otherEvent), in case this degradation is not wanted. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [gerrit-plugin] (JENKINS-26323) The "Build Current Patches Only" only works, if NO parameters in the build are altered
SCM/JIRA link daemon commented on JENKINS-26323 The "Build Current Patches Only" only works, if NO parameters in the build are altered Code changed in jenkins User: Robert Sandell Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/2c0a52387aa9faaee4b6691a29850da6d9fd78ef Log: Merge pull request #195 from HedAurabesh/v2.13.0-abort-on-new-fix JENKINS-26323 Fix "Build Current Patches Only" by scanning for event Compare: https://github.com/jenkinsci/gerrit-trigger-plugin/compare/c3899eaf4e05...2c0a52387aa9 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [sonargraph-plugin] (JENKINS-26358) Jenkins plugin configuration page: Free-form field for Sonargraph version
Esteban Angee created JENKINS-26358 Jenkins plugin configuration page: Free-form field for Sonargraph version Issue Type: Improvement Assignee: Esteban Angee Components: sonargraph-plugin Created: 09/Jan/15 1:27 PM Description: We currently need to update the Jenkins plugin, everytime a new SG7 version is released, since the available version numbers are hard-coded values of a combo-box. This should rather be a text field, so that the release of the SG7 and Jenkins plugin are decoupled. Project: Jenkins Priority: Minor Reporter: Esteban Angee This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [sonargraph-plugin] (JENKINS-26360) User should be able to define the metrics to be displayed as charts
Esteban Angee created JENKINS-26360 User should be able to define the metrics to be displayed as charts Issue Type: Improvement Assignee: Esteban Angee Components: sonargraph-plugin Created: 09/Jan/15 1:30 PM Description: To be discussed: Add more/all metrics to CSV file handler? E.g. RACD, etc. that are not included in the default report? Let the user configure the metrics on the Job configuration page (sonargraph-plugin/src/main/resources/com/hello2morrow/sonargraph/jenkinsplugin/controller/SonargraphReportBuilder/config.jelly) Default set of metrics (as before) Possibility to add new metrics. Check that no metric is added twice. Possibility to remove metrics (all? or only the added ones?) Page creating the charts must iterate over the set of configured metrics (/sonargraph-plugin/src/main/resources/com/hello2morrow/sonargraph/jenkinsplugin/controller/SonargraphChartAction/index.jelly) Project: Jenkins Priority: Major Reporter: Esteban Angee This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [sonargraph-plugin] (JENKINS-26359) Jenkins plugin config page: [user-home] default value leads to validation error
Esteban Angee created JENKINS-26359 Jenkins plugin config page: [user-home] default value leads to validation error Issue Type: Bug Assignee: Esteban Angee Components: sonargraph-plugin Created: 09/Jan/15 1:28 PM Project: Jenkins Priority: Minor Reporter: Esteban Angee This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [sonargraph-plugin] (JENKINS-26358) Configuration page: Free-form field for Sonargraph version
Esteban Angee updated JENKINS-26358 Configuration page: Free-form field for Sonargraph version Change By: Esteban Angee (09/Jan/15 1:32 PM) Summary: Jenkins plugin configuration Configuration page: Free-form field for Sonargraph 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/d/optout.
[JIRA] [sonargraph-plugin] (JENKINS-26359) Config page: [user-home] default value leads to validation error
Esteban Angee updated JENKINS-26359 Config page: [user-home] default value leads to validation error Change By: Esteban Angee (09/Jan/15 1:31 PM) Summary: Jenkins plugin config Config page: [user-home] default value leads to validation error This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [git-plugin] (JENKINS-26354) First time build does not show changelog
Mark Waite updated JENKINS-26354 First time build does not show changelog Change By: Mark Waite (09/Jan/15 1:33 PM) Summary: Git polling found changes but they are First time build does not displayed in Changes section show changelog This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26158) Jenkins v1.586 breaks Active Directory authentication for Subversion plugin.
Björn Olsson updated JENKINS-26158 Jenkins v1.586 breaks Active Directory authentication for Subversion plugin. Change By: Björn Olsson (09/Jan/15 1:38 PM) Summary: Jenkins v1.586 breaks Active Directory authentication using jna for Subversion 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/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26361) Subversion plugin 2.5 unable view tag name in List Subversions Tag
Petr Rocen created JENKINS-26361 Subversion plugin 2.5 unable view tag name in List Subversions Tag Issue Type: Bug Assignee: Unassigned Attachments: list_subversion_task.png, SVN_TAG_display_2_45_version.png, SVN_TAG_display_2_50_version.png Components: subversion-plugin Created: 09/Jan/15 1:40 PM Description: Subversion plugin can not view tag in the list subversion tag (view pictures in the attachement). I use subversion version 1.7. This version is select in jenkins configuration (Subversion Workspace Version) Please fix for this functionality Thank you. Petr Ročeň Environment: Jenkins 1.596 subversion plugin 2.5 Project: Jenkins Priority: Blocker Reporter: Petr Rocen This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [git-plugin] (JENKINS-26314) Using a Tag in Branch Specifier causes the polling to not detect the head revision
Mark Waite commented on JENKINS-26314 Using a Tag in Branch Specifier causes the polling to not detect the head revision If you force polling to use a workspace, does it resolve the problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-26362) Updating version control plugins is breaking jenkins
Benjamin Mahr created JENKINS-26362 Updating version control plugins is breaking jenkins Issue Type: Bug Assignee: Unassigned Attachments: 09-01-2015 14-39-41.png, 09-01-2015 14-53-18.png Components: github-plugin, mapdb-api-plugin, scm-api-plugin, subversion-plugin Created: 09/Jan/15 1:54 PM Description: If version control plugin updates are done and jenkins was resatartet, almost all plugins are gone and cant be used and installed anymore. Environment: Windows 7 Wildfly 8.1.0Final Jenkins 1.596 Project: Jenkins Labels: plugins jenkins Priority: Blocker Reporter: Benjamin Mahr This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26363) Can't stop nor delete the workflow job when it is awaiting for input
Timur Batyrshin
updated JENKINS-26363
Can't stop nor delete the workflow job when it is awaiting for input
Change By:
Timur Batyrshin
(09/Jan/15 2:04 PM)
Description:
Given I am Jenkins administrator when I create a job like the following:{code}node { echo "test" input id: 'Edebd25a79a1ac52da788eba9a7fcc3a', message: 'hey!', ok: 'yo', submitter: 'foobar' parameters: []}{code}... I'm
unable
not able
to
stop/kill
answer
the
job
question it asks
as I get an error saying "You need to be foobar to submit this"
and I'm unable to stop/kill the job (it just doesn't work)
.Probably there should be special permission for admins to stop such jobs and/or the plugin should check if the submitter is a real person when saving/running the job.I'm using Jenkins ver. 1.596 and workflow plugin v1.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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26363) Can't stop nor delete the workflow job when it is awaiting for input
Timur Batyrshin
created JENKINS-26363
Can't stop nor delete the workflow job when it is awaiting for input
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
09/Jan/15 2:03 PM
Description:
Given I am Jenkins administrator when I create a job like the following:
node {
echo "test"
input id: 'Edebd25a79a1ac52da788eba9a7fcc3a', message: 'hey!', ok: 'yo', submitter: 'foobar' parameters: []
}
... I'm unable to stop/kill the job as I get an error saying "You need to be foobar to submit this".
Probably there should be special permission for admins to stop such jobs and/or the plugin should check if the submitter is a real person when saving/running the job.
I'm using Jenkins ver. 1.596 and workflow plugin v1.1
Project:
Jenkins
Priority:
Major
Reporter:
Timur Batyrshin
This message is automatically generated by JIRA.
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/d/optout.
[JIRA] [core] (JENKINS-24519) Flyweight tasks only use one-off executor when they can be scheduled immediately
dogfood commented on JENKINS-24519 Flyweight tasks only use one-off executor when they can be scheduled immediately Integrated in jenkins_main_trunk #3924 [FIXED JENKINS-10944] [FIXED JENKINS-24519] If makeBuildable fails on a FlyweightTask, keep it in queue. (Revision 3e344a94a9eed316d0c351becb08287b473b6521) Result = SUCCESS jesse glick : 3e344a94a9eed316d0c351becb08287b473b6521 Files : test/src/test/java/hudson/model/QueueTest.java core/src/main/java/hudson/model/Queue.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/d/optout.
[JIRA] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
dogfood commented on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history Integrated in jenkins_main_trunk #3924 [FIXED JENKINS-22311] Show queue item parameters in tool tip (Revision 44e6b5d76211bc40e1a608ae3aa93c083befaeba) Result = SUCCESS daniel-beck : 44e6b5d76211bc40e1a608ae3aa93c083befaeba Files : core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-10944) MatrixProject can run on a heavyweight executor, leading to deadlocks
dogfood commented on JENKINS-10944 MatrixProject can run on a heavyweight executor, leading to deadlocks Integrated in jenkins_main_trunk #3924 [FIXED JENKINS-10944] [FIXED JENKINS-24519] If makeBuildable fails on a FlyweightTask, keep it in queue. (Revision 3e344a94a9eed316d0c351becb08287b473b6521) Result = SUCCESS jesse glick : 3e344a94a9eed316d0c351becb08287b473b6521 Files : test/src/test/java/hudson/model/QueueTest.java core/src/main/java/hudson/model/Queue.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/d/optout.
[JIRA] [cli] (JENKINS-25338) list-jobs cli
dogfood commented on JENKINS-25338 list-jobs cli Integrated in jenkins_main_trunk #3924 [FIXED JENKINS-25338] Show job name rather than display name in CLI (Revision 2647af48c81e17ea17bfb144bf804abea22530fe) Result = SUCCESS daniel-beck : 2647af48c81e17ea17bfb144bf804abea22530fe Files : core/src/main/java/hudson/cli/ListJobsCommand.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/d/optout.
[JIRA] [core] (JENKINS-26356) Unable tail pages in Console Output from version 1.596
Daniel Beck resolved JENKINS-26356 as Duplicate Unable tail pages in Console Output from version 1.596 Duplicates JENKINS-26298. Far from critical, you just need to scroll down manually. Change By: Daniel Beck (09/Jan/15 2:43 PM) 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/d/optout.
[JIRA] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect
G. Kr. commented on JENKINS-12523 Could not initialize class org.libvirt.Connect Hi Daniel, your help is very much appreciated, I am not used to maven, not to speak of development for jenkins. your suggestion worked. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [gerrit-plugin] (JENKINS-26323) The "Build Current Patches Only" only works, if NO parameters in the build are altered
Martin Schröder updated JENKINS-26323 The "Build Current Patches Only" only works, if NO parameters in the build are altered Change By: Martin Schröder (09/Jan/15 2:55 PM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/ 194 195 This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26298) Console output does not scroll anymore
Tom FENNELLY started work on JENKINS-26298 Console output does not scroll anymore Change By: Tom FENNELLY (09/Jan/15 3:02 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26361) Subversion plugin 2.5 unable view tag name in List Subversions Tag
Petr Rocen updated JENKINS-26361 Subversion plugin 2.5 unable view tag name in List Subversions Tag Change By: Petr Rocen (09/Jan/15 3:06 PM) Priority: Blocker Major This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26298) Console output does not scroll anymore
Tom FENNELLY commented on JENKINS-26298 Console output does not scroll anymore @Klemes back again ... CI is currently rebuilding https://github.com/jenkinsci/jenkins/pull/1520 . Should now fix your scrolling issue. Sorry about the delay. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26356) Unable tail pages in Console Output from version 1.596
Petr Rocen commented on JENKINS-26356 Unable tail pages in Console Output from version 1.596 Sorry I chose bad priority, but this problem is a little annoying This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [claim-plugin] (JENKINS-26364) Expose claimed failing tests via the REST API
mstave created JENKINS-26364 Expose claimed failing tests via the REST API Issue Type: Improvement Assignee: Christian Bremer Components: claim-plugin Created: 09/Jan/15 3:20 PM Description: Would be helpful to be able to see which failing tests have been claimed via the REST API. For example: http://myserver/job/somejob/3049/testReport/api/json and http://myserver/job/somejob/3049/testReport/junit/com.mycompany.mysuite/mytestclass/sometest/api/json Project: Jenkins Priority: Minor Reporter: mstave This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26365) Green/Blue ball won't open Console Output
Eugene Kabanets created JENKINS-26365 Green/Blue ball won't open Console Output Issue Type: Bug Assignee: Unassigned Attachments: ball_bug.png Components: core Created: 09/Jan/15 3:39 PM Description: Seems like since ver. 1.59* (particularly 1.594) there is no possibility to go from ball to Console Output. Link behind Ball (green/yellow/red, whatever) in Build History will contain URL for Job Page instead. See attached screenshot (highlighted in left lower corner). Environment: Linux/Windows, Jenkins ver 1.594; Java 6/7, Jenkins run as service, container-less Project: Jenkins Labels: jenkins ball build-flow consoleoutput Priority: Minor Reporter: Eugene Kabanets This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26365) Build Ball won't open Console Output
Eugene Kabanets updated JENKINS-26365 Build Ball won't open Console Output Change By: Eugene Kabanets (09/Jan/15 3:40 PM) Summary: Green/Blue ball Build Ball won't open Console Output This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-13554) Matrix jobs does not automatically remove old builds for configurations
SCM/JIRA link daemon commented on JENKINS-13554 Matrix jobs does not automatically remove old builds for configurations Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/matrix/MatrixBuild.java src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll.jelly src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_de.properties src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_es.properties src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_ja.properties src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_pt.properties src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_ru.properties src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_zh_TW.properties src/main/resources/hudson/matrix/MatrixBuild/delete.jelly src/main/resources/hudson/matrix/MatrixBuild/delete_ca.properties src/main/resources/hudson/matrix/MatrixBuild/delete_cs.properties src/main/resources/hudson/matrix/MatrixBuild/delete_de.properties src/main/resources/hudson/matrix/MatrixBuild/delete_es.properties src/main/resources/hudson/matrix/MatrixBuild/delete_ja.properties src/main/resources/hudson/matrix/MatrixBuild/delete_ko.properties src/main/resources/hudson/matrix/MatrixBuild/delete_pl.properties src/main/resources/hudson/matrix/MatrixBuild/delete_pt.properties src/main/resources/hudson/matrix/MatrixBuild/delete_pt_BR.properties src/main/resources/hudson/matrix/MatrixBuild/delete_ru.properties src/main/resources/hudson/matrix/MatrixBuild/delete_zh_CN.properties src/main/resources/hudson/matrix/MatrixBuild/delete_zh_TW.properties src/test/groovy/hudson/matrix/MatrixProjectTest.groovy http://jenkins-ci.org/commit/matrix-project-plugin/4e22a02287c358260fde84f6b3c5d33f480601e0 Log: [FIXED JENKINS-13554] Delete configurations from MatrixBuild#delete This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-13554) Matrix jobs does not automatically remove old builds for configurations
SCM/JIRA link daemon commented on JENKINS-13554 Matrix jobs does not automatically remove old builds for configurations Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/matrix/MatrixBuild.java src/test/groovy/hudson/matrix/MatrixProjectTest.groovy http://jenkins-ci.org/commit/matrix-project-plugin/815b8d08c4b11ec3315ef8745b2554d663c0b5ac Log: JENKINS-13554 Do not keep locked builds This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-13554) Matrix jobs does not automatically remove old builds for configurations
SCM/JIRA link daemon resolved JENKINS-13554 as Fixed Matrix jobs does not automatically remove old builds for configurations Change By: SCM/JIRA link daemon (09/Jan/15 3:43 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-13554) Matrix jobs does not automatically remove old builds for configurations
SCM/JIRA link daemon commented on JENKINS-13554 Matrix jobs does not automatically remove old builds for configurations Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/matrix/MatrixBuild.java src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll.jelly src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_de.properties src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_es.properties src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_ja.properties src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_pt.properties src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_ru.properties src/main/resources/hudson/matrix/MatrixBuild/confirmDeleteAll_zh_TW.properties src/main/resources/hudson/matrix/MatrixBuild/delete.jelly src/main/resources/hudson/matrix/MatrixBuild/delete_ca.properties src/main/resources/hudson/matrix/MatrixBuild/delete_cs.properties src/main/resources/hudson/matrix/MatrixBuild/delete_de.properties src/main/resources/hudson/matrix/MatrixBuild/delete_es.properties src/main/resources/hudson/matrix/MatrixBuild/delete_ja.properties src/main/resources/hudson/matrix/MatrixBuild/delete_ko.properties src/main/resources/hudson/matrix/MatrixBuild/delete_pl.properties src/main/resources/hudson/matrix/MatrixBuild/delete_pt.properties src/main/resources/hudson/matrix/MatrixBuild/delete_pt_BR.properties src/main/resources/hudson/matrix/MatrixBuild/delete_ru.properties src/main/resources/hudson/matrix/MatrixBuild/delete_zh_CN.properties src/main/resources/hudson/matrix/MatrixBuild/delete_zh_TW.properties src/test/groovy/hudson/matrix/MatrixProjectTest.groovy http://jenkins-ci.org/commit/matrix-project-plugin/cfdf9e33bdfda54f29f2871ac9dd49c60310c298 Log: Merge pull request #13 from olivergondza/JENKINS-13554 [FIXED JENKINS-13554] Delete configurations from MatrixBuild#delete Compare: https://github.com/jenkinsci/matrix-project-plugin/compare/5b4dedbc7ff0...cfdf9e33bdfd This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-23614) URL isn't escaped properly (leads to an 404 error).
Oliver Gondža assigned JENKINS-23614 to Oliver Gondža URL isn't escaped properly (leads to an 404 error). Change By: Oliver Gondža (09/Jan/15 3:48 PM) Assignee: Oliver Gondža This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26363) Can't stop nor delete the workflow job when it is awaiting for input
Jesse Glick commented on JENKINS-26363 Can't stop nor delete the workflow job when it is awaiting for input The bug is that anyone with cancel permission for the build overall ought to be able to cancel the input step, whether or not they match submitter. The stop function is implemented for the input step, but just delegates to the cancellation of the input, so that does not help in your case. Form validation should be added for submitter to check whether it is an existing user ID or external group, insofar as the SecurityRealm can give a definitive answer. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26363) Input step should permit cancellation from anyone with build abort permission
Jesse Glick updated JENKINS-26363 Input step should permit cancellation from anyone with build abort permission Change By: Jesse Glick (09/Jan/15 4:03 PM) Summary: Can't stop nor delete the workflow job when it is awaiting for input Input step should permit cancellation from anyone with build abort permission This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-26366) Error deploying to WebLogic when using Promoted Builds plugin
Brian Ochs
created JENKINS-26366
Error deploying to WebLogic when using Promoted Builds plugin
Issue Type:
Improvement
Assignee:
Raphael CHAUMIER
Components:
weblogic-deployer-plugin
Created:
09/Jan/15 4:09 PM
Description:
When trying to use the WebLogic Deployer Plugin in a promotion process step, the following error occurs.
[WeblogicDeploymentPlugin] - Pay attention of Jdk version {selected version is 1.6.0_43} compatibility with Weblogic Deployer API (see Oracle documentation).
[WeblogicDeploymentPlugin] - The JDK C:\Program Files\Java\jdk1.6.0_43 will be used.
java.lang.RuntimeException: No artifact selector has been found for the jop type [class hudson.plugins.promoted_builds.PromotionProcess]
at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:148)
at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.perform(WeblogicDeploymentPlugin.java:236)
at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:282)
at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:224)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
at hudson.model.Run.execute(Run.java:1759)
at hudson.model.Run.run(Run.java:1697)
at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:174)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory : No artifact selector has been found for the jop type [class hudson.plugins.promoted_builds.PromotionProcess]
Environment:
Jenkins 1.596, WebLogic Deployer Plugin 2.12
Project:
Jenkins
Labels:
plugin
Priority:
Minor
Reporter:
Brian Ochs
This message is automatically generated by JIRA.
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/d/optout.
[JIRA] [selenium-plugin] (JENKINS-26367) java.io.IOException: Unexpected termination of the channel when launching slave
Ashok Manji created JENKINS-26367 java.io.IOException: Unexpected termination of the channel when launching slave Issue Type: Bug Assignee: Richard Lavoie Attachments: slave.log Components: selenium-plugin Created: 09/Jan/15 4:30 PM Description: Selenium Plugin works perfectly fine on older Jenkins ver. 1.554.2 with the latest Selenium Plugin 2.4.1, however with the latest stable release Jenkins ver. 1.580.2, slaves are unable to connect to the master due to: java.io.IOException: Unexpected termination of the channel This is blocking Selenium Grid slaves to be connected and online, thus blocking all automation using Selenium Grid. Attached slave.log Environment: Jenkins ver. 1.580.2 Selenium Plugin 2.4.1 amzn1.x86_64 Project: Jenkins Labels: slave selenium plugin jenkins exception Priority: Blocker Reporter: Ashok Manji This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [core] (JENKINS-26367) java.io.IOException: Unexpected termination of the channel when launching slave
Ashok Manji updated JENKINS-26367 java.io.IOException: Unexpected termination of the channel when launching slave Change By: Ashok Manji (09/Jan/15 4:31 PM) Component/s: 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/d/optout.
[JIRA] [xcode-plugin] (JENKINS-26368) Technical Version / Marketing Version Not Updating
James Parker
created JENKINS-26368
Technical Version / Marketing Version Not Updating
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
jenkinslogfile.txt
Components:
xcode-plugin
Created:
09/Jan/15 4:32 PM
Description:
I updated my build server to Yosemite so that I could start building iOS 8 projects. At that time my builds stopped replacing / updating the technical & marketing values within the projects plist file.
When I look at the log file (see attached) I see that it appears to be setting the information correctly, but at the bottom you can see that it's not actually using that information.
I've made sure that the plist file is being referenced correctly in all locations and I'm not using any kind of relative path such as ${src} for it's file path.
Build version 6A2008a
Fetching marketing version number (CFBundleShortVersionString) from project.
[Project] $ /usr/bin/agvtool mvers -terse1
No marketing version found (CFBundleShortVersionString).
Marketing version (CFBundleShortVersionString) found in project configuration: .
Fetching technical version number (CFBundleVersion) from project.
[Project] $ /usr/bin/agvtool vers -terse
No marketing version found (CFBundleVersion)
Technical version (CFBundleVersion) found in project configuration: .
Updating marketing version (CFBundleShortVersionString) to: 0.1.13
[Project] $ /usr/bin/agvtool new-marketing-version 0.1.13
Setting CFBundleShortVersionString of project Project to:
0.1.13.
Updating CFBundleShortVersionString in Info.plist(s)...
Cannot find "Project.xcodeproj/../INFOPLIST_FILE"
Updating technical version (CFBundleVersion) to: 0.1.13.216
[Project] $ /usr/bin/agvtool new-version -all 0.1.13.216
Setting version of project Project to:
0.1.13.216.
Also setting CFBundleVersion key (assuming it exists)
Updating CFBundleVersion in Info.plist(s)...
Cannot find "Project.xcodeproj/../INFOPLIST_FILE"
Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 0.1.13
Technical version (CFBundleVersion) used by Jenkins to produce the IPA: 0.1.13.216
** BUILD SUCCEEDED **
Cleaning up previously generated .ipa files
Cleaning up previously generated .dSYM.zip files
Packaging IPA
[Project] $ /usr/libexec/PlistBuddy -c "Print :CFBundleVersion" "/Users/userXXX/.jenkins/workspace/ProjectXXX/build/Project.app/Info.plist"
[Project] $ /usr/libexec/PlistBuddy -c "Print :CFBundleShortVersionString" "/Users/userXXX/.jenkins/workspace/ProjectXXX/build/Project.app/Info.plist"
Packaging Project.app => /Users/userXXX/.jenkins/workspace/ProjectXXX/build/Project-0.1.13-0.1.13.4.ipa
[Project] $ /usr/bin/xcrun -sdk iphoneos PackageApplication -v "/Users/userXXX/.jenkins/workspace/ProjectXXX/build/Project.app" -o "/Users/userXXX/.jenkins/workspace/ProjectXXX/build/Project-0.1.13-0.1.13.4.ipa"
Packaging application: '/Users/userXXX/.jenkins/workspace/ProjectXXX/build/Project.app'
Arguments: output=/Users/userXXX/.jenkins/workspace/ProjectXXX/build/Project-0.1.13-0.1.13.4.ipa verbose=1
Environment:
Jenkins v1.585, Xcode Plugin v1.4.7
Project:
Jenkins
Labels:
xcode
argvtool
Priority:
Minor
Reporter:
James Parker
This message is automatically generated by JIRA.
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 m
[JIRA] [ec2-plugin] (JENKINS-26369) Allow manual slave launch instead of SSH for on-demand instances
Jeremy Jongsma created JENKINS-26369 Allow manual slave launch instead of SSH for on-demand instances Issue Type: Improvement Assignee: Francis Upton Components: ec2-plugin Created: 09/Jan/15 4:45 PM Description: The EC2 plugin requires launching slaves via SSH for on-demand instances. Due to various connectivity issues that have been reported with the SSH slaves plugin (and which I am experiencing constantly), I'd like to use an AMI that does its own connection to Jenkins master based on EC2 user-data. The only change needed to support this would be a configuration option that allows me to tell the plugin to treat the on-demand instances like spot instances in terms of launching the Jenkins slave. Environment: Jenkins 1.596 Ubuntu 14.04 Project: Jenkins Labels: slave ec2 Priority: Minor Reporter: Jeremy Jongsma This message is automatically generated by JIRA. 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/d/optout.
