[JIRA] [junit-plugin] (JENKINS-12218) Performance problems with JUnit reports
Christian Gnüchtel closed JENKINS-12218 as Fixed Performance problems with JUnit reports With a recent version of Jenkins this problem could not be reproduced. The pages are displayed quickly. Thanks for your good work guys! Change By: Christian Gnüchtel (09/Oct/14 6:57 AM) Status: Open Closed 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] [build-failure-analyzer] (JENKINS-24925) When using BFA with MongoDB the causes gives the oops page and a traceback.
Markus Strand commented on JENKINS-24925 When using BFA with MongoDB the causes gives the oops page and a traceback. The new version of the plugin fixed the bug. Thank you very much. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [build-failure-analyzer] (JENKINS-24925) When using BFA with MongoDB the causes gives the oops page and a traceback.
Markus Strand resolved JENKINS-24925 as Fixed When using BFA with MongoDB the causes gives the oops page and a traceback. Version 1.10.2 fixed the issue Change By: Markus Strand (09/Oct/14 7:25 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-ucm] (JENKINS-25059) Poll sibling changeset should be calculated using slave (case 12085)
Mads Nielsen created JENKINS-25059 Poll sibling changeset should be calculated using slave (case 12085) Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm Created: 09/Oct/14 7:55 AM Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Manni Heumann commented on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found Ran into the same problem today. For a while, 1.583 worked ok for us, the this morning our sessions were gone and logging in again didn't work. Browsers used were Chrome and Opera. We are using the "Project-based Matrix Authorization Strategy" Jenkins is installed as an rpm via yum from the jenkins rpm repository. We are accessing jenkins via "/tools/jenkins" The jenkins logfiles shows absolutely nothing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Manni Heumann edited a comment on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found Ran into the same problem today. For a while, 1.583 worked ok for us, then this morning our sessions were gone and logging in again didn't work. Downgrading to 1.582 fixed this. Browsers used were Chrome and Opera. We are using the "Project-based Matrix Authorization Strategy" Jenkins is installed as an rpm via yum from the jenkins rpm repository. We are accessing jenkins via "/tools/jenkins" The jenkins logfiles shows absolutely nothing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25026) Console output stops populating after several seconds
Martin Schayna
commented on JENKINS-25026
Console output stops populating after several seconds
The spinner disappears and the browser stops polling for changes.
There is a _javascript_ function fetchNext(...) in the console page which does polling. The code is pretty straightforward, it doesn't re-instantiate setTimeout when X-More-Data header is missing in the response and it stops polling (I think) forever:
if (rsp.getResponseHeader("X-More-Data") == "true")
setTimeout(function() {
fetchNext(e, href);
}, 1000);
else
$("spinner").style.display = "none";
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] (JENKINS-18588) Git polling builds same branch multiple times when 'Execute concurrent builds if necessary' turned on
Ilya Vassilevsky commented on JENKINS-18588 Git polling builds same branch multiple times when Execute concurrent builds if necessary turned on I have the same problem in Jenkins 1.583 building Stash's refs/pull-requests//merge branches This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [remoting] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Calin Marina commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel @Ian: that's fair enough but I'd expect for ssh key regeneration to be done in the background without breaking the connection. @cowwoc: I'll try that but I'm not yet sure where to change the setting, should it be on the master node of slave? I'll do a bit of reading on how ssh does this This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pending-changes] (JENKINS-25027) Plugin exceptions with No credential to try with Subversion SCM plugin 2.0 and above
Andreas Vogler started work on JENKINS-25027 Plugin exceptions with No credential to try with Subversion SCM plugin 2.0 and above Change By: Andreas Vogler (09/Oct/14 8:32 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Dan Albu commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel @Calin Marina : i am using Jenkins LTS versions and i don't have this issue ... to much . Maybe consider switching to LTS. Much more stable in a production enviroment This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka commented on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found Jenkins version 1.583 OS and version Windows Server 2013 How was Jenkins installed? as a service Container and version, if not using the native installer native one What's the context path (e.g. / or /jenkins), and what's the URL that fails? http://hostname:8080/ What's the authentication realm (where are the users coming from, Jenkins User Database, LDAP, PAM, ...) What's the authorization strategy (e.g. matrix auth, logged in users can do anything, ...), and what permissions does anonymous have? Which client OS and web browser (+ versions of each)? Win 7 (IE 10 and Firefox (32)) + Windows 2013; This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Pawel Grzegrzolka edited a comment on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found Jenkins version 1.583 OS and version Windows Server 2013 How was Jenkins installed? as a service Container and version, if not using the native installer native one What's the context path (e.g. / or /jenkins), and what's the URL that fails? http://hostname:8080/ What's the authentication realm (where are the users coming from, Jenkins User Database, LDAP, PAM, ...) What's the authorization strategy (e.g. matrix auth, logged in users can do anything, ...), and what permissions does anonymous have? Matrix Authorization Strategy Plugin Which client OS and web browser (+ versions of each)? Win 7 (IE 10 and Firefox (32)) + Windows 2013; This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [any-buildstep] (JENKINS-25060) sudo: no tty present and no askpass program specified
Niraj Nandane created JENKINS-25060 sudo: no tty present and no askpass program specified Issue Type: Task Assignee: bap Components: any-buildstep Created: 09/Oct/14 8:48 AM Description: Hi All, I am building a project on linux slave. I have a user "abc" on slave with limited sudo access. On of the sudo access is "(root) /bin/chown" .If i run a build on build machine without using jenkins then , "sudo -u root chown username" works fine. And if i run build through jenkins then it says sudo: no tty present and no askpass program specified What i can do now. I dont have access to /etc/sudoers file . Working of chown is very imp for me. Please any help would be greatly appreciated Environment: Jenkins version=latest war file Project: Jenkins Priority: Blocker Reporter: Niraj Nandane This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [any-buildstep] (JENKINS-25060) sudo: no tty present and no askpass program specified
Niraj Nandane commented on JENKINS-25060 sudo: no tty present and no askpass program specified If someone is able to explain what iternally happens in brief when we build on slave node using jenkins ,could help me ..thanks a lot in advance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [remoting] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Calin Marina commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel unfortunately I only have full access to the slaves not on the master server... master is administered by others and I can only lobby for changes for now This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [remoting] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Dan Albu commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel that is very bad...especially if you need more access to configure This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [remoting] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Dan Albu edited a comment on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel that is very bad...especially if you need more access to configure. I am the build manager for my team so it is simpler for all devs because i am very fast to approach This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-7744) Aborting job fails to kill processes started during cancel action
gck commented on JENKINS-7744 Aborting job fails to kill processes started during cancel action I can't reproduce the problem any more with 1.583. Looking into the code I touched in my patch from 4 years ago I can see that a lot of stuff have changed. It could be that the bug has been fixed by 550678074ebeae884cf98850c4032141a936fe09. No sure though. Since I can't find a recipe to reproduce anymore I would not regard my patch as anyhow useful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobconfighistory] (JENKINS-25061) Slave Config History page has incorrect html title: Job Config History
Oliver Gondža created JENKINS-25061 Slave Config History page has incorrect html title: Job Config History Issue Type: Bug Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 09/Oct/14 9:42 AM Project: Jenkins Priority: Minor Reporter: 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] [throttle-concurrent-builds-plugin] (JENKINS-13619) Add ability to throttle number of concurrent builds of matrix configurations per node
Oleg Nenashev resolved JENKINS-13619 as Fixed Add ability to throttle number of concurrent builds of matrix configurations per node Marking as resolved (1.8.3). There will be several improvements in 1.8.4 Change By: Oleg Nenashev (09/Oct/14 9:51 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [any-buildstep] (JENKINS-25060) sudo: no tty present and no askpass program specified
Daniel Beck resolved JENKINS-25060 as Not A Defect sudo: no tty present and no askpass program specified Please do not use Jira to ask for assistance. We have the jenkinsci-users mailing list and #jenkins on Freenode for that. Also, Google. This is a very easily searchable problem. Change By: Daniel Beck (09/Oct/14 9:59 AM) Status: Open Resolved Assignee: bap Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink] (JENKINS-25062) Jenkins Testlink plugin cannot find testing result, shows Not run
Venkat N created JENKINS-25062 Jenkins Testlink plugin cannot find testing result, shows Not run Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: Custom_Field_1.png, Custom_Field_2.png, Jenkins_Command_Line.png, Jenkins_TestLink_Result_1.png, Jenkins_TestLink_Result_2.png, Result_Seeking_Strategy.png, TestLink_Jenkins_Config.png, testng_results.png Components: testlink Created: 09/Oct/14 10:00 AM Description: Hi Bruno We are unable to get the results from Jenkins to TestLink. It always shows "Not Run". I have mentioned the environment details above. Please find the attached screen shots for details about custom fields, Jenkins configurations testng results. It would be really helpful if you can provide your expertise to solve this issue. We have been stuck at this point for a while. Thanking in advance Environment: Jenkins Testlink Plugin -3.10 TestLink Version -1.9.12 Jenkins Version - 1.554.3 Project: Jenkins Priority: Major Reporter: Venkat N This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25054) javax.servlet.ServletException: java.lang.IllegalArgumentException when depth != 0 in job API
Daniel Beck commented on JENKINS-25054 javax.servlet.ServletException: java.lang.IllegalArgumentException when depth != 0 in job API Could be an issue with some actions configured in the job, or stored in builds. Would be helpful if you copied the job (on the file system, so all builds are copied too, at least the build.xml), and then, if the copy has the same problem, deleted things (configuration, builds) one by one from it until it works. Then check what was last deleted. As it is, the stacktrace is pretty useless and you didn't provide anything else to aid investigation (job config.xml, build.xml files, Jenkins configuration, ...). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [remoting] (JENKINS-22494) Multiconfiguration project does not respect label restrictions
Martin Skinner reopened JENKINS-22494 Multiconfiguration project does not respect label restrictions changing from bug to feature request Change By: Martin Skinner (09/Oct/14 10:09 AM) Resolution: NotADefect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-22494) Multiconfiguration project does not respect label restrictions
Martin Skinner updated JENKINS-22494 Multiconfiguration project does not respect label restrictions Change By: Martin Skinner (09/Oct/14 10:10 AM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-dsl-plugin] (JENKINS-25051) ConcurrentModificationException in DSL plugin 1.2.6
Daniel Spilker updated JENKINS-25051 ConcurrentModificationException in DSL plugin 1.2.6 I reduced the priority since there is a workaround. Change By: Daniel Spilker (09/Oct/14 10:11 AM) 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] [job-dsl-plugin] (JENKINS-25051) ConcurrentModificationException in DSL plugin 1.2.6
Daniel Spilker
commented on JENKINS-25051
ConcurrentModificationException in DSL plugin 1.2.6
The problem is that startsWithParameters calls the new startsWithParameters method of BuildPipelineView which then internally adds a new WithXmlAction and that causes the ConcurrentModificationException.
To avoid this, the startsWithParameters element name in the configure block should be quoted:
...
configure { pipelineNode -
pipelineNode {
'startsWithParameters'(true)
}
}
...
This will happen for other element names when a method with the same name exists in the scope. I'm not sure if changing the closures resolution strategy will help or break other things.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [flexible-publish] (JENKINS-25017) BuildTrigger in Flexible Publish doesn't work since Jenkins 1.501
ikedam commented on JENKINS-25017 BuildTrigger in Flexible Publish doesnt work since Jenkins 1.501 This would work both for Jenkins 1.501 and = 1.501. http://javadoc.jenkins-ci.org/hudson/util/DescribableList.html#buildDependencyGraph(hudson.model.AbstractProject,%20hudson.model.DependencyGraph) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
becky yy commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Daniel, Recently we used VisualSVN Server to set up the repositories. And the credentials method is Integrated Windows Authentication. So it's controlled by Active Directory. In the jenkins project configuration, I entered my login id as the credentials. And also for the "Additional Credential", I have put "https://svnserver:443 VisualSVN Server" and also used the same credentials as the repositories. However there are always an error "Unable to access https://library.mea.adinternal.com/svn/YYTest : svn: E200015:". I am not sure what's wrong. Do you have any idea? Thank you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials becky yy: Please don't ask for assistance in JIRA. It's irrelevant to the 60 people watching this. Use e.g. the jenkinsci-users mailing list for that instead. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [test-results-analyzer] (JENKINS-25063) Unable to view the link to test result analyzer for users with non-admin permissions
Varun Menon created JENKINS-25063 Unable to view the link to test result analyzer for users with non-admin permissions Issue Type: Bug Assignee: Varun Menon Components: test-results-analyzer Created: 09/Oct/14 11:24 AM Project: Jenkins Priority: Minor Reporter: Varun Menon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [test-results-analyzer] (JENKINS-25063) Unable to view the link to test result analyzer for users with non-admin permissions
SCM/JIRA link daemon commented on JENKINS-25063 Unable to view the link to test result analyzer for users with non-admin permissions Code changed in jenkins User: Varun Menon Path: src/main/java/org/jenkinsci/plugins/testresultsanalyzer/TestResultsAnalyzerAction.java src/main/webapp/js/testresult.js http://jenkins-ci.org/commit/test-results-analyzer-plugin/080d8d63510767e0c45fdbc3f151d20b88daf5cc Log: Fixing issue JENKINS-24263,JENKINS-25063 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [test-results-analyzer] (JENKINS-24263) Test Results Analyzer plugin : Expendable cross does not working well
SCM/JIRA link daemon commented on JENKINS-24263 Test Results Analyzer plugin : Expendable cross does not working well Code changed in jenkins User: Varun Menon Path: src/main/java/org/jenkinsci/plugins/testresultsanalyzer/TestResultsAnalyzerAction.java src/main/webapp/js/testresult.js http://jenkins-ci.org/commit/test-results-analyzer-plugin/080d8d63510767e0c45fdbc3f151d20b88daf5cc Log: Fixing issue JENKINS-24263,JENKINS-25063 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [security] (JENKINS-25065) https://github.com/jenkinsci/jenkins/pull/1397/commits which over-rides system default umask of 022 to 027 causes problems with folder creation in jobs in release 1.5
Duncan Bell created JENKINS-25065 https://github.com/jenkinsci/jenkins/pull/1397/commits which over-rides system default umask of 022 to 027 causes problems with folder creation in jobs in release 1.582 Issue Type: Bug Assignee: Unassigned Components: security Created: 09/Oct/14 11:40 AM Description: I just wanted to point out and double check if anyone else had similar issues recently. I frequently build build vm's installing and setting up Jenkins and yesterday came across an issue where some of my jobs then started failing on a new Jenkins setup due to file/folder permissions. It seemed to mkdir -p commands were setting folders to 750 rather than 755 so some commands run as sudo would make folders as root normally at 755 as 750 then the Jenkins user would not be able to access them. Normally this was never a problem. Testing on the command line everything appeared fine on the server and umask was set to 022 in /etc/login.defs Changing to become Jenkins user from root and creating directories showed nothing to be wrong... folders 755 and files 664 Anyway I noticed this... https://github.com/jenkinsci/jenkins/pull/1397/commits So the umask value in /etc/defaults/jenkins was being ignored and now is being picked up... so now it is 027 I was just wondering maybe this has broken builds for other people where folders get created as root, or one process happens as root and then the jenkins user tries to read the folder or file? root@server:# cd /tmp/ root@server:/tmp# mkdir testfolder root@server:/tmp# chmod 750 testfolder/ root@server:/tmp# su jenkins jenkins@server:/tmp$ cd testfolder/ bash: cd: testfolder/: Permission denied jenkins@server:/tmp$ touch testfolder/testfile touch: cannot touch `testfolder/testfile': Permission denied Why the need for this umask 027 default? I am sedding it out of the /etc/default/jenkins when I create my vm and using the system default. Project: Jenkins Priority: Minor Reporter: Duncan Bell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [test-results-analyzer] (JENKINS-25063) Unable to view the link to test result analyzer for users with non-admin permissions
Varun Menon resolved JENKINS-25063 as Fixed Unable to view the link to test result analyzer for users with non-admin permissions Fixed 0.1.2 version of plugin Change By: Varun Menon (09/Oct/14 11:41 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm] (JENKINS-25064) Swarm toollocations don't work for all tools
Nico Mommaerts created JENKINS-25064 Swarm toollocations dont work for all tools Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: swarm Created: 09/Oct/14 11:39 AM Description: I'm sorry, I keep finding bugs in my own code... I noticed that the swarm client wouldn't recognize all tools, some were added as Ant installations. That's because Ant is the first item in the dropdown. Turns out the way I generate the toolinstallation key is not entirely correct. The keys that I have encountered that don't work are those for Ant and Maven. In my tests I always used Groovy, JDK and Ant...Ant seemed to work because it default to the first item in the listbox, being Ant.. I have asked for some help here: https://groups.google.com/forum/#!topic/jenkinsci-dev/QwYKkMvtw9s Project: Jenkins Priority: Critical Reporter: Nico Mommaerts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [test-results-analyzer] (JENKINS-24263) Test Results Analyzer plugin : Expendable cross does not working well
Varun Menon resolved JENKINS-24263 as Fixed Test Results Analyzer plugin : Expendable cross does not working well Fixed 0.1.2 version of plugin Change By: Varun Menon (09/Oct/14 11:41 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25009) Provide a clearer message when creating a job in a non-existing folder
SCM/JIRA link daemon resolved JENKINS-25009 as Fixed Provide a clearer message when creating a job in a non-existing folder Change By: SCM/JIRA link daemon (09/Oct/14 11:44 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25009) Provide a clearer message when creating a job in a non-existing folder
SCM/JIRA link daemon commented on JENKINS-25009 Provide a clearer message when creating a job in a non-existing folder Code changed in jenkins User: nico.mommaerts Path: job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JenkinsJobManagement.java job-dsl-plugin/src/main/resources/javaposse/jobdsl/plugin/Messages.properties job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/JenkinsJobManagementSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/5c32ed5daa7d548ec8f1696c23226f32564030ea Log: FIXED JENKINS-25009 Catch the npe when creating a job in a parent (folder) that doesn't exist This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-dsl-plugin] (JENKINS-25009) Provide a clearer message when creating a job in a non-existing folder
SCM/JIRA link daemon commented on JENKINS-25009 Provide a clearer message when creating a job in a non-existing folder Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JenkinsJobManagement.java job-dsl-plugin/src/main/resources/javaposse/jobdsl/plugin/Messages.properties job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/JenkinsJobManagementSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/51a71977195bb072b7915bf704050f106f42c176 Log: cleanup, also fixed JENKINS-25009 for views This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-dsl-plugin] (JENKINS-25009) Provide a clearer message when creating a job in a non-existing folder
SCM/JIRA link daemon commented on JENKINS-25009 Provide a clearer message when creating a job in a non-existing folder Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JenkinsJobManagement.java job-dsl-plugin/src/main/resources/javaposse/jobdsl/plugin/Messages.properties job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/JenkinsJobManagementSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/4cc853b5dcacae514d14d138cf0cdf75e34d32f2 Log: Merge branch 'JENKINS-25009' Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/6b8288798c7b...4cc853b5dcac This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21311) Queue item cancellation via REST api works but returns a 404
Barthélémy von Haller commented on JENKINS-21311 Queue item cancellation via REST api works but returns a 404 I have just tried again and could reproduce it with Jenkins 1.579. I did https://xxx.yyy.ch/jenkins/view/job/jobname/buildWithParameters?module=xyz And got a 201 with a location in the header : Location: https://xxx.yyy.ch/jenkins/queue/item/1137/ I then I did : https://xxx.yyy.ch/jenkins/queue/cancelItem?id=1137 And got the following header : Status Code: 404 Not Found Cache-Control: no-cache Connection: close Content-Length: 952 Content-Type: text/html;charset=utf-8 Date: Thu, 09 Oct 2014 11:45:15 GMT Expires: Thu, 01 Jan 1970 01:00:00 CET Pragma: No-cache Yet, the queue item was cancelled ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [security] (JENKINS-25065) https://github.com/jenkinsci/jenkins/pull/1397/commits which over-rides system default umask of 022 to 027 causes problems with folder creation in jobs in release 1.5
Duncan Bell updated JENKINS-25065 https://github.com/jenkinsci/jenkins/pull/1397/commits which over-rides system default umask of 022 to 027 causes problems with folder creation in jobs in release 1.582 Change By: Duncan Bell (09/Oct/14 11:48 AM) Description: Ijustwantedtopointout aproblemIencounted, anddoublecheckifanyoneelsehadsimilarissuesrecently.IfrequentlybuildbuildvmsinstallingandsettingupJenkinsandyesterdaycameacrossanissuewheresomeofmyjobsthenstartedfailingonanewJenkinssetupduetofile/folderpermissions.Itseemedtomkdir-pcommandsweresettingfoldersto750ratherthan755sosomecommandsrunassudowouldmakefoldersasrootnormallyat755as750thentheJenkinsuserwouldnotbeabletoaccessthem.Normallythiswasneveraproblem.Testingonthecommandlineeverythingappearedfineontheserverandumaskwassetto022in/etc/login.defsChangingtobecomeJenkinsuserfromrootandcreatingdirectoriesshowednothingtobewrong...folders755andfiles664AnywayInoticedthis...https://github.com/jenkinsci/jenkins/pull/1397/commitsSotheumaskvaluein/etc/defaults/jenkinswasbeingignoredandnowisbeingpickedup...sonowitis027Iwasjustwonderingmaybethishasbrokenbuildsforotherpeoplewherefoldersgetcreatedasroot,oroneprocesshappensasrootandthenthejenkinsusertriestoreadthefolderorfile?root@server:#cd/tmp/root@server:/tmp#mkdirtestfolderroot@server:/tmp#chmod750testfolder/root@server:/tmp#sujenkinsjenkins@server:/tmp$cdtestfolder/bash:cd:testfolder/:Permissiondeniedjenkins@server:/tmp$touchtestfolder/testfiletouch:cannottouch`testfolder/testfile:PermissiondeniedWhytheneedforthisumask027default?Iamseddingitoutofthe/etc/default/jenkinswhenIcreatemyvmandusingthesystemdefault. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-dsl-plugin] (JENKINS-25051) ConcurrentModificationException in DSL plugin 1.2.6
Jeff Storey commented on JENKINS-25051 ConcurrentModificationException in DSL plugin 1.2.6 Thanks for looking into this so quickly. Agree that it is no longer a blocker. An alternative fix is to just upgrade to the new method. Though quoting it would ensure it works on older versions too. I understand your concerns about not necessarily wanting to change the closure strategy for this as this is probably an edge case. Feel free to close as won't fix since there is a reasonably easy workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
Design Development
Hi, First of all, I would like to utilize the opportunity to introduce myself to you as Web Development Manager, India Web development Company. As an Internet Application Development company, we have been progressively growing over our year of operations. Our designers and developers have been delivering their best by pushing their creative horizons. We like to move along with constantly transforming technology and hence adopt the most advanced tools and practices. We listen and understand the personalized needs of our clients to deliver precisely with what's needed.Our prices are best in the market, which is why we have a client base in countries like US, UK, Canada, Australia, Germany and Netherlands. We can help your business/organization to earn the identity it needs on the internet as it is the best platform for marketing today. Our services web development in Web Designing includes: * Logo Designing,* Graphic Designing* Custom Web Designing* Corporate Website Designing* Website Redesigning* Web 2.0 based designing* E-Commerce Web Designing* Mobile Website Development* PSD to xHTML and Wordpress conversion.* Reseller Development Services We provide a comprehensive range of web services and require you to sell our services on our behalf. Our prices are highly competitive and the quality we can guarantee would be inimitable. Send us the project details along with requirements to receive a quick price quote. Feel free to write us back for all sorts of queries. Wishing you a great day ahead In case of questions and queries feel free writing us back? Best Regards,jaisal Andrews -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [parameterized-trigger] (JENKINS-25066) Build on the same node option triggers runs on node with same label and not on identical node
Tobias Del Fabro created JENKINS-25066 Build on the same node option triggers runs on node with same label and not on identical node Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 09/Oct/14 12:06 PM Description: The implementation for "Build on the same node" parameter in "NodeParameters.java" implies that the next job is triggered on a node with the same label. According to the parameter name, I would assume the job to be triggered on the very same (identical) node! The label is supposed to group nodes, e.g. running windows / suse. Further, a job can anyway be configured to run only on nodes with a specific label. Example: Jenkins with 2 Slaves: Name: Slave1, Label: debian Name: Slave2, Label: debian 4 jobs in a pipeline: should run on very same workspace(node), triggered with option "build on same node" A (checkout + build) - B - C - D (release) Scenario: 1. Slave2 runs A-D @Revision 10 2. Slave1 starts A @Revision 20 3. A triggers B on Slave1 4. B triggers C on Slave2 due to the label (and since less active?) 5. C does no checkout and runs @Revision 10 6. C triggers D on Slave2 @Revision 10 Result/Impact: Release is done using Revision 10, instead of 20. Would not be noticed, unless someone compares the exact revisions/node names. Workarounds (not very nice): a) one workspace for each job, each job checks out b) using unique labels for each node and configuring job to run on each label Ideas: 1. Renaming parameter to "Build on node with same label" and providing new feature for execution on very same node 2. Changing the functionality to run on node with same name Environment: Jenkins 1.580 Parameterized Trigger Plugin 2.25 Build Pipeline Plugin 1.4.3 Project: Jenkins Priority: Major Reporter: Tobias Del Fabro This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sauce-ondemand] (JENKINS-25067) Embed Sauce OnDemand reports option doesn't exist for Publish NUnit test result report section
apgray created JENKINS-25067 Embed Sauce OnDemand reports option doesnt exist for Publish NUnit test result report section Issue Type: Bug Assignee: Ross Rowe Components: sauce-ondemand Created: 09/Oct/14 12:09 PM Description: Embed Sauce Reports checkbox only exists under "Publish JUnit test result report" section. It does not exist under "Publish NUnit test result report" section. It needs to. Environment: All Project: Jenkins Priority: Major Reporter: apgray This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [integrity-plugin] (JENKINS-25068) uncaught null pointer exception SCM during polling
Matthias Rump created JENKINS-25068 uncaught null pointer exception SCM during polling Issue Type: Bug Assignee: Cletus DSouza Components: integrity-plugin Created: 09/Oct/14 12:20 PM Description: Okt 09, 2014 12:49:07 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@28553675myJobName java.lang.NullPointerException at hudson.scm.IntegrityCMProject.parseProject(IntegrityCMProject.java:351) at hudson.scm.IntegritySCM.initializeCMProjectMembers(IntegritySCM.java:653) at hudson.scm.IntegritySCM.compareRemoteRevisionWith(IntegritySCM.java:897) at hudson.scm.SCM.poll(SCM.java:401) at hudson.model.AbstractProject._poll(AbstractProject.java:1429) at hudson.model.AbstractProject.poll(AbstractProject.java:1332) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 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 java.lang.Thread.run(Unknown Source) Okt 09, 2014 12:49:07 PM DEBUG IntegritySCM - Member context: /E-EC/_Komponenten/BDK/Global/030_Software/Komponenten/70_Quellen/Master/Komponenten/Code/Shared/APP/project.pj Environment: Plugin Version 1.27 Integrity Server I10.4 Project: Jenkins Priority: Major Reporter: Matthias Rump This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [integrity-plugin] (JENKINS-25068) uncaught null pointer exception during SCM polling
Matthias Rump updated JENKINS-25068 uncaught null pointer exception during SCM polling Change By: Matthias Rump (09/Oct/14 12:21 PM) Summary: uncaughtnullpointerexception SCM during SCM polling Description: Okt09,201412:49:07PMhudson.triggers.SCMTrigger$RunnerrunPollingSEVERE:FailedtorecordSCMpollingforhudson.model.FreeStyleProject@28553675[myJobName]java.lang.NullPointerException athudson.scm.IntegrityCMProject.parseProject(IntegrityCMProject.java:351) athudson.scm.IntegritySCM.initializeCMProjectMembers(IntegritySCM.java:653) athudson.scm.IntegritySCM.compareRemoteRevisionWith(IntegritySCM.java:897) athudson.scm.SCM.poll(SCM.java:401) athudson.model.AbstractProject._poll(AbstractProject.java:1429) athudson.model.AbstractProject.poll(AbstractProject.java:1332) athudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) athudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) athudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) atjava.util.concurrent.Executors$RunnableAdapter.call(UnknownSource) atjava.util.concurrent.FutureTask$Sync.innerRun(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) atjava.lang.Thread.run(UnknownSource)Okt09,201412:49:07PM[DEBUG]IntegritySCM-Membercontext:/E-EC/_Komponenten/BDK/Global/030_Software/Komponenten/70_Quellen/Master/Komponenten/Code/Shared/APP/project.pj This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24703) Search box background color (white) not matching navbar backround (black)
Daniel Beck commented on JENKINS-24703 Search box background color (white) not matching navbar backround (black) Tom, I'd like to see this fixed this week if you're busy I'd just revert the bad change for JENKINS-24625 for now. Please let me know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [build-flow] (JENKINS-23360) Post-build actions are not getting executed in BuildFlow job.
Patxi Gortázar commented on JENKINS-23360 Post-build actions are not getting executed in BuildFlow job. I happens also in an Ubuntu Server x64. I've seen that post build actions are executed if "Flow run needs a workspace" is checked. They're not executed otherwise. So a workaround would be to enable that option in flow jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [swarm] (JENKINS-25064) Swarm toollocations don't work for all tools
Nico Mommaerts commented on JENKINS-25064 Swarm toollocations dont work for all tools Found a solution but I'm gonna test first a bit This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21311) Queue item cancellation via REST api works but returns a 404
Daniel Beck commented on JENKINS-21311 Queue item cancellation via REST api works but returns a 404 It makes sense to me now. It redirects to the referer URL, which, if that's not set, defaults to '.', or /queue/ (which isn't mean to be used interactively, so there's nothing there 404). This is why I was asking where /queue/cancelItem was advertised as being part of the Jenkins API it's not documented in /queue/api. If it's advertised nowhere, and you're just using it because it exists, then there's no reasonable expectation of URLs used by the Jenkins UI to also work outside that context. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [pretested-integration] (JENKINS-25069) Plugin does not work with stash-git-hook
Mads Nielsen created JENKINS-25069 Plugin does not work with stash-git-hook Issue Type: Bug Assignee: Praqma Support Components: pretested-integration Created: 09/Oct/14 12:47 PM Project: Jenkins Priority: Minor Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21311) Queue item cancellation via REST api works but returns a 404
Barthélémy von Haller commented on JENKINS-21311 Queue item cancellation via REST api works but returns a 404 Actually the second link points to a post from you This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21311) Queue item cancellation via REST api works but returns a 404
Barthélémy von Haller commented on JENKINS-21311 Queue item cancellation via REST api works but returns a 404 Ok, fair enough. For information I got the information about it in these two places : http://stackoverflow.com/questions/21021905/how-to-stop-a-build-in-jenkins-via-the-rest-api https://groups.google.com/forum/#!topic/jenkinsci-users/aN_WFvgTz2Y Is there a more standard way of cancelling a queue item ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25020) Accessing parameters of triggered build has strange syntax
Kaaleppi Kekkola commented on JENKINS-25020 Accessing parameters of triggered build has strange syntax No it won't include para2. The parameters I'm talking about are those declared in "This build is parameterized" part. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25020) Accessing parameters of triggered build has strange syntax
Kaaleppi Kekkola edited a comment on JENKINS-25020 Accessing parameters of triggered build has strange syntax No it won't include para2. The parameters I'm talking about in the description are those declared in "This build is parameterized" part. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21311) Queue item cancellation via REST api works but returns a 404
Jesse Glick updated JENKINS-21311 Queue item cancellation via REST api works but returns a 404 Change By: Jesse Glick (09/Oct/14 12:59 PM) Labels: queuerest stapler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21311) Queue item cancellation via REST api works but returns a 404
Jesse Glick commented on JENKINS-21311 Queue item cancellation via REST api works but returns a 404 There are lots of API endpoints which are not documented, mainly because the creator did not document them. (In this case I am at fault, though I doubt the endpoint I was replacing was documented either.) So this is simply a bug. Using HttpResponses.forwardToPreviousPage() is commonplace in @RequirePOST endpoints that are not expected to display anything special where the UI invoker is just something that sends a POST via a form and does not want the rendered page to change. One easy fix would be to make this method in Stapler check whether there actually is a Referer, and if not, just delegate to ok() instead. The proper fix would probably be to think of this as a real API and return 204 No Content, optionally with some body or status message indicating whether anything was actually canceled. It is also necessary to ensure that whatever status code is chosen, stopButton.jelly (called from two places with cancelItem) will not try to reload the page. From the use of _onclick_="new Ajax.Request(this.href); return false" it looks like this would already be true regardless of the status code. And it looks like we need a Queue/_api.jelly listing the various operations. Currently this gives only generic information. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-25070) Subversion fails to update externals once after external is changed.
James Noonan created JENKINS-25070 Subversion fails to update externals once after external is changed. Issue Type: Bug Assignee: Unassigned Components: subversion Created: 09/Oct/14 1:19 PM Description: SVN Check out fails at external check-out. This only occurs if the external has changed. In this case, the external revision was updated to a more recent version. (For us, this happens maybe once a week so). We run quite a number of jobs that access this same repository. Whenever the SVN External is changed, they all fail. They all fail only once and are fine the next time they run. The jobs themselves run on multiple machines from a pool. An individual machine does not impact the above. So, if the job-A runs on machine-X after the external change, job-A will fail. If job-B then runs on machine-X, it will fail. Then if job-A runs on machine-Y, it’s fine. Jobs need to get through this fail, machines do not. Note we have other jobs that use Subversion on the command line; they check out the same code but do not hit this problem. Our jobs are configured using a shared workspace. The externals all have the same access credentials. We have configured ‘Additional Credentials’ as well as the Subversion Credentials, but all are the same. Also, as this only happens after an external change, all work correctly. 13:03:47 Fetching 'https://repo/product/trunk/tools/scripts/pyadb' at -1 into '/local/ws/BUILD_PRODUCT_TRUNK/tools/scripts/jenkins/canaries/pyadb' 13:03:47 At revision 193923 13:03:47 At revision 193923 13:03:48 no change for https://repo/product/trunk/components/csf-foundation/include since the previous build 13:03:48 no change for https://repo/product/trunk/components/common-foundation/CommonFoundation since the previous build 13:03:48 hudson.util.IOException2: revision check failed on https://repo/product/thirdparty-allversions/internal/sipcc/imports/IMPORT_synbase_main 13:03:48 at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:186) 13:03:48 at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:128) 13:03:48 at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:739) 13:03:48 at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:900) 13:03:48 at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) 13:03:48 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615) 13:03:48 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 13:03:48 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524) 13:03:48 at hudson.model.Run.execute(Run.java:1706) 13:03:48 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 13:03:48 at hudson.model.ResourceController.execute(ResourceController.java:88) 13:03:48 at hudson.model.Executor.run(Executor.java:232) 13:03:48 Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /product/thirdparty-allversions/internal/sipcc/imports/IMPORT_synbase_main failed 13:03:48 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) 13:03:48 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) 13:03:48 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) 13:03:48 at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) 13:03:48 at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) 13:03:48 at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) 13:03:48 at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) 13:03:48 at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) 13:03:48 at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) 13:03:48 at
[JIRA] [disk-usage] (JENKINS-24829) Calculationg Disk usage on a slave is way too slow
Andreas Kaiser commented on JENKINS-24829 Calculationg Disk usage on a slave is way too slow same problem on Linux slave 15:19:06 Finished Calculation of disk usage of build in 0 seconds 15:19:06 Started calculate disk usage of workspace 15:24:06 Finished Calculation of disk usage of workspace in 5 minutes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-20941) Stored git credentials not used when submodule is updated
Kamil Ślesiński commented on JENKINS-20941 Stored git credentials not used when submodule is updated Hi, We've been seeing this issue for months now. Authentication doesn't work on https submodules. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-13435) Auto Install jdk from oracle downloads html instead of bin
Thejus R commented on JENKINS-13435 Auto Install jdk from oracle downloads html instead of bin Does the cache look something like this?? jenkins@Some cache$ ll -lrt jars/ total 120 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 49 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 F4 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 99 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 6C drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 30 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 A3 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 33 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 31 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 BF drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 0B drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 DB drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 9B drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 36 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 C2 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 5E drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:16 27 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:17 21 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:17 F2 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:17 CA drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:17 9A drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:17 7A drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:17 78 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:17 43 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:17 23 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:17 85 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:17 25 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:17 E3 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:43 84 drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:43 CD drwxr-xr-x 2 jenkins jenkins 4096 Sep 9 02:43 2C jenkins@Some cache$ Please help as I possibly do not know where my $JENKINS_HOME points to. And still the above reported error persists. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [other] (JENKINS-25071) Keep this build forever seems to break Max # of builds to keep
Mark Levine created JENKINS-25071 Keep this build forever seems to break Max # of builds to keep Issue Type: Bug Assignee: Unassigned Attachments: Jenkins_Build_History_2014-10-09_10-12-04.jpg Components: other Created: 09/Oct/14 2:14 PM Description: After setting a build job to Keep this build forever, the build history is no longer constrained by Max # of builds to keep. The Build History keeps growing. Even if I remove keep the build forever, (don't keep build) the Build History still grows Environment: Jenkins 1.5.8.2 Project: Jenkins Labels: jenkins Priority: Minor Reporter: Mark Levine This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-postbuild] (JENKINS-18989) Cannot get Plugin to honor Java Jar added via Additional groovy classpath
Torben Knerr commented on JENKINS-18989 Cannot get Plugin to honor Java Jar added via Additional groovy classpath Frank Merrow, Viktor Berke would be higly interested in that, too This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24926) Connection to slave constantly breaks, java process can only be kill -9-ed
Johannes Wienke commented on JENKINS-24926 Connection to slave constantly breaks, java process can only be kill -9-ed Since this is really bothering us: has anyone got an idea how to debug this? Any logger to attach in Jenkins to get better debug output or anything like that? Any help is very much appreciated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25071) Keep this build forever seems to break Max # of builds to keep
Daniel Beck updated JENKINS-25071 Keep this build forever seems to break Max # of builds to keep BTW, quoting the instructions on the create issue form: Select the component(s) that this issue relates to or has an effect on. Enter core if this is about Jenkins itself and Please do not use labels that add no information, like "plugin" or "jenkins". Change By: Daniel Beck (09/Oct/14 2:26 PM) Environment: Jenkins1. 5.8.2 582 Labels: jenkins Component/s: core Component/s: other This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25071) Keep this build forever seems to break Max # of builds to keep
Daniel Beck commented on JENKINS-25071 Keep this build forever seems to break Max # of builds to keep Log rotation is only run after a build completes. As the newest build is from the 8th and the screenshot from the 9th, I suggest you start a new build and wait for completion. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-25070) Subversion fails to update externals once after external is changed.
Daniel Beck commented on JENKINS-25070 Subversion fails to update externals once after external is changed. Externals need 'Additional Credentials' defined, see JENKINS-21785. Did you specify those? (Please don't post a comment there, it's too noisy already) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (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. Yes. The externals are all on the same repo. The same credentials are specified in 'Additional Credentials' as for the main subversion check-out. Also, 99% of the time, there is no problem. It seems to be only when the external revision changes. And we are on revision 2.3. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25071) Keep this build forever seems to break Max # of builds to keep
Mark Levine resolved JENKINS-25071 as Not A Defect Keep this build forever seems to break Max # of builds to keep Change By: Mark Levine (09/Oct/14 2:36 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [batch-task] (JENKINS-25072) batch file is not an internal or external is not recognized as internal or external command
Dion I created JENKINS-25072 batch file is not an internal or external is not recognized as internal or external command Issue Type: Bug Assignee: Dion I Components: batch-task, subversion Created: 09/Oct/14 2:49 PM Description: Hello, I am trying to build a Delphi XE6 project. The source code is being pulled from two subversion folders. Inside one of these folders are a few .bat files that need to be run. I assigned these .bat files to be run on a build task. When trying to build the project everything goes fine until the build needs the execute the .bat files. I get the following error: bat file is not recognized as an internal or external command, operable program or batch file. I already tried adding the subversion and the Jenkins workspace directory to the Windows Path, but this has not fixed the problem. I also disabled UAC. Hopefully someone can help me. Environment: Jenkins: 1.583 Windows 8.1 Google Chrome Installed plugins: Credentials CVS Javadoc JUnit LDAP Matrix Authorization Strategy Maven Project OWASP Markup Formatter PAM Authentication SSH Credentials SSH Slaves Subversion Translation Assitance Project: Jenkins Labels: subversion batch windows Priority: Blocker Reporter: Dion I This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25075) Weather column should render asynchronously
Jesse Glick created JENKINS-25075 Weather column should render asynchronously Issue Type: Bug Assignee: Unassigned Components: core Created: 09/Oct/14 2:51 PM Description: Job.getBuildHealthReports can be expensive, especially with Maven projects (see JENKINS-19392). Putting jobs into folders does not help, because Folder.getBuildHealthReports recursively traverses them, and the default WorstChildHealthMetric checks the result of each leaf. It should not be called synchronously during page rendering. Rather, WeatherColumn/column.jelly should use an AJAX callback of some kind, effective while the page is fronted. So you would get a quick page load, with some icons filling in progressively. Still puts load on the server but potentially much less. Project: Jenkins Labels: view performance health folders Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder] (JENKINS-25073) Double-counting of health reports from child folders
Jesse Glick
created JENKINS-25073
Double-counting of health reports from child folders
Issue Type:
Bug
Assignee:
stephenconnolly
Components:
cloudbees-folder
Created:
09/Oct/14 2:51 PM
Description:
Folder.getBuildHealthReports looks like it is double-counting each child Folder. It does a recursive traversal of the folder, applying FolderHealthMetric.Reporter to each node (leaf or not). But a typical FolderHealthMetric like WorstChildHealthMetric also calls getHealthReport on the child Folder, which winds up calling Folder.getBuildHealthReports recursively! This seems like a mistake.
Possible fixes:
Make WorstChildHealthMetric.ReporterImpl.observe (and any other similar impls) ignore a Folder it is given.
Make Folder.getBuildHealthReports not ask a reporter to observe a Folder.
Make Folder.getBuildHealthReports not do a recursive traversal, only asking about direct children.
My preference is for the third fix, as it leaves the reporter in control of the logic; if it needs a recursive call it can do one.
By the way, the awkward reflection code in getHealthReport suggests that we need an interface in Jenkins core, such as
interface ItemWithHealthReport extends Item {
HealthReport getBuildHealth();
ListHealthReport getBuildHealthReports();
}
Project:
Jenkins
Labels:
performance
health
Priority:
Major
Reporter:
Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25074) Build health computed twice per job
Jesse Glick created JENKINS-25074 Build health computed twice per job Issue Type: Bug Assignee: Unassigned Components: core Created: 09/Oct/14 2:51 PM Description: buildHealth.jelly asks for both job.buildHealth and job.buildHealthReports, causing Job/Folder.getBuildHealthReports to be called twice just to render a single table cell. I would guess that the performance problem comes in the first call, and the second call is mostly working off a hot cache, but if you are under memory pressure it is always possible that garbage collection has to run between the two calls and so work is wasted. I see no need to call job.buildHealth; should suffice to assume that the implementation is simply going to be to look up the first element in job.buildHealthReports (as it is in both Job and Folder). Project: Jenkins Labels: performance view health Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [batch-task] (JENKINS-25072) batch file is not an internal or external is not recognized as internal or external command
Daniel Beck resolved JENKINS-25072 as Not A Defect batch file is not an internal or external is not recognized as internal or external command JIRA is an issue tracker, not a support site. Please direct requests for assistance somewhere else, e.g. the jenkinsci-users mailing list. Change By: Daniel Beck (09/Oct/14 2:52 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [integrity-plugin] (JENKINS-25068) uncaught null pointer exception during SCM polling
Cletus DSouza commented on JENKINS-25068 uncaught null pointer exception during SCM polling Seems like the member in /E-EC/_Komponenten/BDK/Global/030_Software/Komponenten/70_Quellen/Master/Komponenten/Code/Shared/APP/project.pj is missing a timestamp for the revision. Very strange! I can code a workaround to default to 'now' which will hopefully prevent this from happening. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [integrity-plugin] (JENKINS-25068) uncaught null pointer exception during SCM polling
SCM/JIRA link daemon commented on JENKINS-25068 uncaught null pointer exception during SCM polling Code changed in jenkins User: Cletus D'Souza Path: src/main/java/hudson/scm/IntegrityCMProject.java http://jenkins-ci.org/commit/integrity-plugin/69aa2c365037d3690ad547293d89ad46d4d1c6d7 Log: Resolved JENKINS-25068 uncaught null pointer exception during SCM polling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [integrity-plugin] (JENKINS-25068) uncaught null pointer exception during SCM polling
Cletus DSouza resolved JENKINS-25068 as Fixed uncaught null pointer exception during SCM polling Change By: Cletus DSouza (09/Oct/14 3:05 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] [core] (JENKINS-24703) Search box background color (white) not matching navbar backround (black)
Tom FENNELLY commented on JENKINS-24703 Search box background color (white) not matching navbar backround (black) Sorry Daniel. I merged this and created a PR at https://github.com/jenkinsci/jenkins/pull/1423. We will merge upstream shortly (assuming it passes the build). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Liam Reimers commented on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found I'm hitting this one, too, after upgrading to 1.583. Jenkins version 1.583 (Upgraded from 1.559) OS and version Mac OS X 10.9.2 How was Jenkins installed? From the official installer package; automatic upgrade from 1.559 via the Jenkins web UI. Container and version, if not using the native installer Native installer What's the context path (e.g. / or /jenkins), and what's the URL that fails? /jenkins, URL that fails is /jenkins/;jsessionid=1qfdq9lhzfvtw10h62t8khybgl (Redirected after login) What's the authentication realm (where are the users coming from, Jenkins User Database, LDAP, PAM, ...) LDAP What's the authorization strategy (e.g. matrix auth, logged in users can do anything, ...), and what permissions does anonymous have? Matrix; anonymous have no permissions. Which client OS and web browser (+ versions of each)? Client OS is Mac OS X 10.9.5, using Safari 7.1 -What are the exact steps to reproduce this problem in a new browser session (no cookies etc.). Be as precise and exhaustive in these instructions as you can (imagine explaining it to your technologically impaired parents/grandparents/spouse). 1. Load Jenkins login page in an unauthenticated browser session 2. Log in with valid credentials 3. See problem This can be worked around by removing the ";jsessionid=1qfdq9lhzfvtw10h62t8khybg" part of the URL that hits 404 after login. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Liam Reimers edited a comment on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found I'm hitting this one, too, after upgrading to 1.583. Jenkins version 1.583 (Upgraded from 1.559) OS and version Mac OS X 10.9.2 How was Jenkins installed? >From the official installer package; automatic upgrade from 1.559 via the Jenkins web UI. Container and version, if not using the native installer Native installer What's the context path (e.g. / or /jenkins), and what's the URL that fails? /jenkins, URL that fails is /jenkins/;jsessionid=1qfdq9lhzfvtw10h62t8khybgl (Redirected after login) What's the authentication realm (where are the users coming from, Jenkins User Database, LDAP, PAM, ...) LDAP What's the authorization strategy (e.g. matrix auth, logged in users can do anything, ...), and what permissions does anonymous have? Matrix; anonymous have no permissions. Which client OS and web browser (+ versions of each)? Client OS is Mac OS X 10.9.5, using Safari 7.1 What are the exact steps to reproduce this problem in a new browser session (no cookies etc.). Be as precise and exhaustive in these instructions as you can (imagine explaining it to your technologically impaired parents/grandparents/spouse). 1. Load Jenkins login page in an unauthenticated browser session 2. Log in with valid credentials 3. See problem This can be worked around by removing the ";jsessionid=1qfdq9lhzfvtw10h62t8khybg" part of the URL that hits 404 after login. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [promoted-builds] (JENKINS-8963) Remote API to create/delete/modify promotions
eguess74 commented on JENKINS-8963 Remote API to create/delete/modify promotions Jesse, Thank you very much for implementing this long awaited feature!! Can you please look into adding a separate permission into matrix-based security allowing to create promotions? Do you want it to be pulled into separated bug? Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19215) Consistent daily morning deadlocks
milki mlk commented on JENKINS-19215 Consistent daily morning deadlocks Upgrading Java to 7u55, increasing PermGen to 128m, and adding a ton more ram seems to do the trick. The irc plugin can still kill winstone and there are still File Descriptor leaks. But Jenkins no longer consistently deadlocks at least. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19215) Consistent daily morning deadlocks
milki mlk resolved JENKINS-19215 as Fixed Consistent daily morning deadlocks Change By: milki mlk (09/Oct/14 3:46 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] [tfs] (JENKINS-15384) TFS Plugin does not seem to work (can't get latest)
marlene cote commented on JENKINS-15384 TFS Plugin does not seem to work (cant get latest) I am seeing the same thing. We invested days in trying to get Jenkins working with tfs source control for builds. Someone needs to own this and fix it please thank you. Marlene This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [android-lint] (JENKINS-22176) Add a column provider for the number of total Lint issues
Christopher Orr closed JENKINS-22176 as Fixed Add a column provider for the number of total Lint issues Version 2.2 of the plugin has been released, which includes this feature. Change By: Christopher Orr (09/Oct/14 4:22 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Steve Jansen commented on JENKINS-21750 Promoted Builds Plugin @Thomas, my understanding is the external config files exist because each promotion is really a child job in Jenkins, and child jobs have their own config, history, etc. This makes sense when you start to think about how a promotion with manual approval would be hard to implement in a single job config. What do you think? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jacoco] (JENKINS-25076) Jenkins Jacoco plugin shows 0% branch coverage when jacoco report shows n/a
Jeremy Brown created JENKINS-25076 Jenkins Jacoco plugin shows 0% branch coverage when jacoco report shows n/a Issue Type: Bug Assignee: Ognjen Bubalo Attachments: Screen Shot 2014-10-08 at 3.19.05 PM.png, Screen Shot 2014-10-09 at 11.31.46 AM.png Components: jacoco Created: 09/Oct/14 4:42 PM Description: Jenkins Jacoco plugin shows 0% branch coverage on Classes and packages with no branch logic. For the same class the Jacoco report correctly shows an n/a . Project: Jenkins Priority: Major Reporter: Jeremy Brown This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jacoco] (JENKINS-25076) Jenkins Jacoco plugin shows 0% branch coverage when jacoco report shows n/a
Jeremy Brown updated JENKINS-25076 Jenkins Jacoco plugin shows 0% branch coverage when jacoco report shows n/a Change By: Jeremy Brown (09/Oct/14 4:45 PM) Description: JenkinsJacocopluginshows0%branchcoverageonClassesandpackageswithnobranchlogic.ForthesameclasstheJacocoreportcorrectlyshowsann/a. Thisskewstheaggregatebranchcoveragereporttowardsafalsedecline. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jacoco] (JENKINS-25076) Jenkins Jacoco plugin shows 0% branch coverage when jacoco report shows n/a
Jeremy Brown updated JENKINS-25076 Jenkins Jacoco plugin shows 0% branch coverage when jacoco report shows n/a Change By: Jeremy Brown (09/Oct/14 4:44 PM) Description: JenkinsJacocopluginshows0%branchcoverageonClassesandpackageswithnobranchlogic.ForthesameclasstheJacocoreportcorrectlyshowsann/a. Thisskewstheaggregatebranchcoveragereporttowardsafalsedecline. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [youtrack] (JENKINS-25057) Backlinks option is commenting on wrong projects.
SCM/JIRA link daemon commented on JENKINS-25057 Backlinks option is commenting on wrong projects. Code changed in jenkins User: Erik Zielke Path: src/main/java/org/jenkinsci/plugins/youtrack/YoutrackIssueUpdater.java src/test/java/org/jenkinsci/plugins/youtrack/YouTrackSCMListenerTest.java http://jenkins-ci.org/commit/youtrack-plugin/ba4ab603f963c61c360efc77966438f82c0e5e82 Log: fixes JENKINS-25057 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25077) Provide rest API to validate config.xml files without actually building a job
Sean Abbott created JENKINS-25077 Provide rest API to validate config.xml files without actually building a job Issue Type: New Feature Assignee: Unassigned Components: core Created: 09/Oct/14 4:58 PM Description: I have a large-ish jenkins environment (several hundred jobs, 6 workers, etc.) I drive all of this via an automated configuration script. When testing new changes to the configuration script, it would be very useful to be able to validate the XML that I generate without actually creating a job. (For testing, etc.) This validation would need to also use the plugins that I have installed. Project: Jenkins Priority: Minor Reporter: Sean Abbott This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-25048) Git plugin ignores included/excluded paths when triggering build on commit nitification
Mark Waite commented on JENKINS-25048 Git plugin ignores included/excluded paths when triggering build on commit nitification If you've not already configured the job to force polling using workspace, you may want to try that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25026) Console output stops populating after several seconds
Daniel Beck commented on JENKINS-25026 Console output stops populating after several seconds Stapler sets X-More-Data if the file being read hasn't been completed yet though, so I was simply wrong about the behavior of this header: https://github.com/stapler/stapler/blob/master/core/src/main/java/org/kohsuke/stapler/framework/io/LargeText.java#L266 The Jenkins parts also look reasonable: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Run.java#L1439 https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Run.java#L501 https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Run.java#L234 Does this occur for all jobs? Are you doing weird things in Groovy scripts? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [promoted-builds] (JENKINS-8963) Remote API to create/delete/modify promotions
Jesse Glick commented on JENKINS-8963 Remote API to create/delete/modify promotions Certainly that would be a separate issue. I would not have time to work on it myself (someone else may). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24703) Search box background color (white) not matching navbar backround (black)
Daniel Beck commented on JENKINS-24703 Search box background color (white) not matching navbar backround (black) Great, thanks Tom! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24703) Search box background color (white) not matching navbar backround (black)
SCM/JIRA link daemon commented on JENKINS-24703 Search box background color (white) not matching navbar backround (black) Code changed in jenkins User: Tom Fennelly Path: war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/4eefff9f95570ed8be4b98ab4ae683004dc65de8 Log: Merge pull request #1423 from tfennelly/JENKINS-24703 FIXED JENKINS-24703 Do not set any colors for input elements Compare: https://github.com/jenkinsci/jenkins/compare/e72c11ae4b2a...4eefff9f9557 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
