[JIRA] [bugzilla] (JENKINS-22799) Bugzilla Tab in jenkins
sandeep reddy mallepally commented on JENKINS-22799 Bugzilla Tab in jenkins click Manage Jenkins and select configure system we need to set Bugzilla url of ur oraganization. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21867) Jenkins slave disappeared constantly
Pei-Tang Huang commented on JENKINS-21867 Jenkins slave disappeared constantly Thank you, you can mark this issues duplicated to JENKINS-22525, I will follow this issue here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xunit] (JENKINS-23101) xUnit plugin fails to work after upgrade
Vyacheslav Koshcheyev created JENKINS-23101 xUnit plugin fails to work after upgrade Issue Type: Bug Assignee: Gregory Boissinot Attachments: Update Center [Jenkins] 2014-05-20 13-06-32 2014-05-20 13-06-37.jpg, Update Center [Jenkins] 2014-05-20 13-10-56 2014-05-20 13-10-58.jpg Components: xunit Created: 20/May/14 6:11 AM Description: 1. xUnit plugin works fine on ver 1.67 2. upgrade it to 1.88 3. No xUnit found in plugins installed list Environment: OS X 10.9.3 Jenkins 1.563 xUnit plugin 1.67 - 1.88 Project: Jenkins Labels: plugin Priority: Major Reporter: Vyacheslav Koshcheyev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22525) A Slave disappears every time Jenkins boots up
Pei-Tang Huang commented on JENKINS-22525 A Slave disappears every time Jenkins boots up We first encounter this situation from about Oct/13 The jvm info of my installation: JRE 1.6.0 IBM J9 2.4 Windows Server 2008 R2 amd64-64 jvmwa6460sr10fp1-20120202_101568 (JIT enabled, AOT enabled)J9VM - 20120202_101568JIT - r9_2007_21307ifx1GC - 20120202_AA This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xunit] (JENKINS-23101) xUnit plugin fails to work after upgrade
Vyacheslav Koshcheyev updated JENKINS-23101 xUnit plugin fails to work after upgrade Change By: Vyacheslav Koshcheyev (20/May/14 6:17 AM) Attachment: UpdateCenter[Jenkins]2014-05-2013-16-012014-05-2013-16-03.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit] (JENKINS-23101) xUnit plugin fails to work after upgrade
Vyacheslav Koshcheyev updated JENKINS-23101 xUnit plugin fails to work after upgrade Change By: Vyacheslav Koshcheyev (20/May/14 6:19 AM) Environment: OSX10. 9 7 . 3 5 Jenkins1.563xUnitplugin1.67-1.88 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xunit] (JENKINS-23101) xUnit plugin fails to work after upgrade
Vyacheslav Koshcheyev updated JENKINS-23101 xUnit plugin fails to work after upgrade Change By: Vyacheslav Koshcheyev (20/May/14 6:45 AM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [dry] (JENKINS-23102) dry plugin slow down jenkins.
shans zoe created JENKINS-23102 dry plugin slow down jenkins. Issue Type: Bug Assignee: Ulli Hafner Components: dry Created: 20/May/14 7:17 AM Description: I have simian to scan my code, and the result file is about 2.5M. When i click the hyperlinks or icon to view the detail，jenkins responds so slowly, that it always takes me a few minutes to wait for another operation untill i restart the master. Environment: jenkins: 1.559 to 1.563 dry: 2.40 Project: Jenkins Priority: Major Reporter: shans zoe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ssh-slaves] (JENKINS-22320) High CPU consumption because of SSH communication
Thomas Herrlin
commented on JENKINS-22320
High CPU consumption because of SSH communication
Preliminary tests where actually not so good. Forgot to remove the java exclusions when using the jvisualvm CPU sampler. Majority of CPU time still within socketRead0native even after my buffer hack.
Also tried forcing setTcpNoDelay(false) as src/main/java/hudson/plugins/sshslaves/SSHLauncher.java sets connection.setTCPNoDelay(true).
Setting to false should reduce the number of packets and thus the amount of interrupts.
TCPNoDelay should mostly be used for interactive connections to get fast non piggybacked ACKs and not so good for bulk transfers as far as I understand. I find commit c2fcc257 in sshslaves to be contradictory to my understanding on how the TCP protocol works, but perhaps there are some cases in the real world where ACK piggybacking causes problems.
Did a simple "ifconfig ; sleep 3 ; ifconfig" while jenkins was transferring a big non-compressible mocked artifact, average RX packet size was about 1100 bytes.
SSH buffer size seems to be set to 4Mb in the sshslaves plugin:
src/main/java/hudson/plugins/sshslaves/SSHLauncher.java
private void expandChannelBufferSize(Session session, TaskListener listener) {
// see hudson.remoting.Channel.PIPE_WINDOW_SIZE for the discussion of why 1MB is in the right ball park
// but this particular session is where all the master/slave communication will happen, so
// it's worth using a bigger buffer to really better utilize bandwidth even when the latency is even larger
// (and since we are draining this pipe very rapidly, it's unlikely that we'll actually accumulate this much data)
int sz = 4;
m.invoke(session, sz*1024*1024);
I am using trilead-ssh2-build217-jenkins-3, sshslaves 1.6, Jenkins 1.554.1 with the bundled jetty container.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [master-slave] (JENKINS-22722) Master doesn't show connected slave
Michaël Burtin commented on JENKINS-22722 Master doesnt show connected slave I experience the same issue with Jenkins 1.563. Slaves are started via Amazon EC2 plugin, using Spot instance, and connect to master via JNLP. Sometimes master refuse to show slave as online, node logs only show: JNLP agent connected from /172.x.x.x Usually a master restart bring back everything to normal. Node logs show: JNLP agent connected from /172.x.x.x ===[JENKINS REMOTING CAPACITY]===Slave.jar version: 2.41 This is a Unix slave Slave successfully connected and online ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ghprb] (JENKINS-23103) Specify branches to build
Johannes Schüth created JENKINS-23103 Specify branches to build Issue Type: Improvement Affects Versions: current Assignee: Honza Brázdil Components: ghprb Created: 20/May/14 7:56 AM Description: Currently all pull requests are handled. It would be good to selectively build a pull request. I suggest adding a blacklist/whitelist field for branches. Compare to travis-ci: http://docs.travis-ci.com/user/build-configuration/#Specify-branches-to-build Project: Jenkins Priority: Minor Reporter: Johannes Schüth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22853) SEVERE: Trying to unexport an object that's already unexported
Filip Noetzel commented on JENKINS-22853 SEVERE: Trying to unexport an object thats already unexported I'm also seeing this with 1.562 when using slaves that connect to localhost. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-2487) Please wait, getting ready to work takes very long
francisdb commented on JENKINS-2487 Please wait, getting ready to work takes very long And a service that needs 10 minutes to start is ok? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [credentials] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
T K commented on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. Still the same with subversion plugin 2.4 and jenkins 1.563 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-23104) Gerrit trigger: support a 'Comment added' trigger with no verdict restriction
Marco Leogrande created JENKINS-23104 Gerrit trigger: support a Comment added trigger with no verdict restriction Issue Type: New Feature Assignee: rsandell Components: gerrit-trigger Created: 20/May/14 8:40 AM Description: It would be nice to be able to trigger builds when any comment is left by the user in Gerrit (e.g., to support commands via comments, like "run tests again", or Openstack CI's "recheck XXX bug"). To be able to perform these builds, the Jenkins script should be able to run upon the receipt on any comment: therefore when selecting a 'Comment added' trigger, the user should be able to select "any comment", not just those that match the specific verdict and value. Project: Jenkins Priority: Major Reporter: Marco Leogrande This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19224) java.io.IOException: failed to rename job
Daniel Beck commented on JENKINS-19224 java.io.IOException: failed to rename job Jesse: I've seen it too many times when my Jenkins master was still on Windows that I ended up with two partial build dirs. This is how Jenkins deals with it, and my Gradle scripts running on Windows need to do things like if(!f.deleteDir()!f.deleteDir()!f.deleteDir())throw Notably, a similar hack is missing in Job.java for renaming the builds directory, and it tries only once before throwing. Jakub: Is your Jenkins home on an NFS share? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xunit] (JENKINS-22268) Boost C++ unit tests and the xUnit plugin - Not working
satish kumar commented on JENKINS-22268 Boost C++ unit tests and the xUnit plugin - Not working Since it is production code binary. I cannot share it. Please guide me how to resolve 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] [xunit] (JENKINS-22268) Boost C++ unit tests and the xUnit plugin - Not working
satish kumar edited a comment on JENKINS-22268 Boost C++ unit tests and the xUnit plugin - Not working I will attach my xml file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit] (JENKINS-22268) Boost C++ unit tests and the xUnit plugin - Not working
satish kumar updated JENKINS-22268 Boost C++ unit tests and the xUnit plugin - Not working Change By: satish kumar (20/May/14 9:29 AM) Attachment: test.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-5312) Global properties not being replaced
Daniel Beck commented on JENKINS-5312 Global properties not being replaced This needs to be reproduced on a recent Jenkins version with clear instructions how to reproduce. Note that global properties are provided mostly as environment variables to build steps, so run set (Windows, Batch build step) or env (Linux, Shell build step) to see whether it's actually not defined, or just not passed to e.g. Ant as system property. Also, need to reproduce with EnvInject plugin disabled if you're filing a core bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [buildtriggerbadge] (JENKINS-18824) Build Causer doesn't resolve CLI based usernames
Daniel Beck assigned JENKINS-18824 to Daniel Beck Build Causer doesnt resolve CLI based usernames Change By: Daniel Beck (20/May/14 10:04 AM) Assignee: BaptisteMathus DanielBeck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xunit] (JENKINS-23101) xUnit plugin fails to work after upgrade
Vyacheslav Koshcheyev commented on JENKINS-23101 xUnit plugin fails to work after upgrade BTW, just the same problem with "Priority Sorter Plugin" 2.3 - 2.6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Jakub Czaplicki edited a comment on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history The file and the line that require modification : https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly#L59 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Jakub Czaplicki commented on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history File and line that requires modification : https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly#L59 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-8099) org.jvnet.hudson.reactor.ReactorException: hudson.util.IOException2: Unable to read D:\config.xml
Oleg Nenashev resolved JENKINS-8099 as Wont Fix org.jvnet.hudson.reactor.ReactorException: hudson.util.IOException2: Unable to read D:\config.xml Java 1.5 is not supported by Jenkins anymore. Closing the issue Change By: Oleg Nenashev (20/May/14 10:51 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Jakub Czaplicki edited a comment on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history The file and the line that require modification : https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly#L59 I suggest to use the jQuery Expander Plugin or a similar solution if jQuery is not built in in Jenkins core: http://plugins.learningjquery.com/expander/demo/index.html http://plugins.learningjquery.com/expander/index.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-7903) Unable to load winp.x64.dll
Oleg Nenashev resolved JENKINS-7903 as Fixed Unable to load winp.x64.dll The issue has been fixed in 6.1.0 Change By: Oleg Nenashev (20/May/14 10:53 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7903) Unable to load winp.x64.dll
Oleg Nenashev closed JENKINS-7903 as Fixed Unable to load winp.x64.dll Change By: Oleg Nenashev (20/May/14 10:53 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7232) Ability to align views vertically
Oleg Nenashev closed JENKINS-7232 as Fixed Ability to align views vertically Change By: Oleg Nenashev (20/May/14 10:57 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7232) Ability to align views vertically
Oleg Nenashev resolved JENKINS-7232 as Fixed Ability to align views vertically Sectioned View Plugin provides such feature https://wiki.jenkins-ci.org/display/JENKINS/Sectioned+View+Plugin Change By: Oleg Nenashev (20/May/14 10:57 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] [core] (JENKINS-4664) Allow to authorize build removal from queue and execution
Oleg Nenashev closed JENKINS-4664 as Fixed Allow to authorize build removal from queue and execution Change By: Oleg Nenashev (20/May/14 11:11 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4664) Allow to authorize build removal from queue and execution
Oleg Nenashev resolved JENKINS-4664 as Fixed Allow to authorize build removal from queue and execution The Job.Cancel permission is available in 1.480+ Change By: Oleg Nenashev (20/May/14 11:11 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] [xframe-filter] (JENKINS-23105) Plugin Causes Page not to fully Load
Kayhan Sefat created JENKINS-23105 Plugin Causes Page not to fully Load Issue Type: Bug Assignee: Unassigned Attachments: jenkins_plugins_page.PNG Components: xframe-filter Created: 20/May/14 11:20 AM Description: Running 1.561 When clicking on the plugins page, then the Installed Tab when this plugins details load in the table, it is incomplete. Upshot is also that there are no Confirm buttons to save enabling/disabling any plugins. Project: Jenkins Priority: Minor Reporter: Kayhan Sefat This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [veracode-scanner-plugin] (JENKINS-23106) Exception thrown when configuring the veracode scanner plugin
Sean Moloney created JENKINS-23106 Exception thrown when configuring the veracode scanner plugin Issue Type: Bug Affects Versions: current Assignee: Mike Bockus Components: veracode-scanner-plugin Created: 20/May/14 11:26 AM Description: APIJenkins ver. 1.563 javax.servlet.ServletException: java.lang.UnsupportedClassVersionError: com/veracode/apiwrapper/wrappers/UploadAPIWrapper : Unsupported major.minor version 51.0 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at
[JIRA] [veracode-scanner-plugin] (JENKINS-23106) Exception thrown when configuring the veracode scanner plugin
Sean Moloney
updated JENKINS-23106
Exception thrown when configuring the veracode scanner plugin
Change By:
Sean Moloney
(20/May/14 11:28 AM)
Description:
APIJenkinsver.1.563
TheexceptionisthrownaftertheIhaveaddedtheveracodepluginasapostbuildstep,pressingthesavebuttonthrowstheexception.
{code}javax.servlet.ServletException:java.lang.UnsupportedClassVersionError:com/veracode/apiwrapper/wrappers/UploadAPIWrapper:Unsupportedmajor.minorversion51.0 atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631) atorg.kohsuke.stapler.Stapler.service(Stapler.java:225) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) atorg.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) atorg.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) atorg.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) atorg.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) atorg.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) atorg.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) atorg.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) atorg.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) atorg.eclipse.jetty.server.Server.handle(Server.java:370) atorg.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) atorg.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) atorg.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) atorg.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) atorg.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) atorg.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) atorg.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) atorg.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) atwinstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource)
[JIRA] [svnmerge] (JENKINS-23107) Rebase not working for simple setup
Chris Platts created JENKINS-23107 Rebase not working for simple setup Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: svnmerge Created: 20/May/14 11:43 AM Description: Hi, I've just installed the svnmerge plugin to take the pain out of branching and creating matching projects. It looks ideal! So, I've clicked one of my software build jobs and enabled svnmerge in its config. I've created a branch via the svnmerge options and it's correctly created the branch in svn and the job to build it in Jenkins. I've since made changes on the trunk and want to rebase the branch (which is as of now still unmodified after branching). I've clicked the Rebase option on the branch job and chosen Latest Revision. Unfortunately this fails with the following message. Rebasing is in progress java.lang.NullPointerException at jenkins.plugins.svnmerge.FeatureBranchProperty.rebase(FeatureBranchProperty.java:159) at jenkins.plugins.svnmerge.RebaseAction.perform(RebaseAction.java:105) at jenkins.plugins.svnmerge.RebaseAction.perform(RebaseAction.java:25) at jenkins.plugins.svnmerge.AbstractSvnmergeTaskAction$WorkerThread.perform(AbstractSvnmergeTaskAction.java:105) at hudson.model.TaskThread.run(TaskThread.java:127) at jenkins.plugins.svnmerge.AbstractSvnmergeTaskAction$TaskImpl$1.run(AbstractSvnmergeTaskAction.java:161) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) I don't want to play with the plugin any further until I get the basics working any ideas? Thanks, Chris Environment: Windows jenkins host, Linux slave for builds. Jenkins v1.509.2, svnmerge plugin v2.1, subversion plugin v2.4. Project: Jenkins Priority: Major Reporter: Chris Platts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-2487) Please wait, getting ready to work takes very long
taksan commented on JENKINS-2487 Please wait, getting ready to work takes very long Just some insight for this issue: We had profiled jenkins during our slow startup and found that what was really taking a long time was reading all the builds. To work around the problem, we did an exhaustive cleanup and setup a very aggressive policy to clean up old builds (only a few selected jobs keep a longer history). We were able to reduce the startup time from 80min to 5 minutes. Other things that help: because the problem is due to intensive I/O reading every build file, improving the hardware also helps to alleviate the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-22320) High CPU consumption because of SSH communication
Thomas Herrlin commented on JENKINS-22320 High CPU consumption because of SSH communication Looks like I may be chasing a red herring The slowdowns I see may not actually be related to this ticket, even if I get high cpu usage in fill_buffer - socketRead0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-2487) Please wait, getting ready to work takes very long
Oleg Nenashev commented on JENKINS-2487 Please wait, getting ready to work takes very long @francisdb And a service that needs 10 minutes to start is ok? Many services like DBMS may require several hours to startup, so several minutes are not the showstopper in general. Jenkins developers have implemented much features to decrease the data traffic on the startup (lazy loading of builds, delayed tasks, etc.). BTW, Jenkins definitely need to initialize much data objects and to establish connections with nodes, hence it is not possible to nullify the initialization time. Any plugin can "contribute" to the startup time, hence it is mandatory to know about the Jenkins configuration to localize your issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18213) Copying an existing job to a new one gives an error with Status Code: 500
rakesh jain commented on JENKINS-18213 Copying an existing job to a new one gives an error with Status Code: 500 The issue is still there. I have a script to copy jobs. I havent upgraded the jenkins version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-2487) Please wait, getting ready to work takes very long
Sergey Valkanesko commented on JENKINS-2487 Please wait, getting ready to work takes very long Many services like DBMS may require several hours to startup, so several minutes are not the showstopper in general. This statement received in email notification made me recover my password to reply. Seriously? Do you really believe that this should be considered an excuse for this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22340) Cannot configure colums of 'All' view
Oleg Nenashev resolved JENKINS-22340 as Wont Fix Cannot configure colums of All view As designed. All View is just a last hope if you install a buggy column to your personal views. Hence it takes a minimal set of columns. BTW, you can set another view as a default one. More info: https://issues.jenkins-ci.org/browse/JENKINS-5431 https://wiki.jenkins-ci.org/display/JENKINS/Editing+or+Replacing+the+All+View for more info Change By: Oleg Nenashev (20/May/14 12:21 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Kevin Phillips edited a comment on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed I have a few follow up questions: 1. If I understand correctly, this "process tree killer" feature was pre-existing in earlier Jenkins releases, but only in the latest update was it "changed" to add recursive killing of processes, correct? 2. That being the case, does setting "BUILD_ID=dontKillMe" disable termination of all processes or just this new "recursive" behavior? If it disables all process terminations I'd say this proposal would not be a viable workaround since it could risk leaving other rogue processes orphaned on a build machine, which has many adverse side effects (which, I'm guessing you already know since I suspect this feature was implemented to resolve these exact problems) 3. Won't setting the "BUILD_ID=dontKillMe" affect other parts of the build? The BUILD_ID env var is used as a unique identifier throughout the job after all. Changing it from the unique identifier it is meant to be, to a statically defined character string seems fragile at best. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Kevin Phillips commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed I have a few follow up questions: 1. If I understand correctly, this "process tree killer" feature was pre-existing in earlier Jenkins releases, but only in the latest update was it "changed" to add recursive killing of processes, correct? 2. That being the case, does setting "BUILD_ID=dontKillMe" disable termination of all processes or just this new "recursive" behavior? If it disables all process terminations I'd say this proposal would not be a viable workaround since it could risk leaving other rogue processes orphaned on a build machine, which has many adverse side effects (which, I'm guessing you already know since I suspect this feature was implemented to resolve these exact problems) 3. Won't setting the "BUILD_ID=dontKillMe" affect other parts of the build. The BUILD_ID env var is used as a unique identifier throughout the job after all. Changing it from the unique identifier it is meant to be, to a statically defined character string seems fragile at best. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22750) Polling no longer triggers builds (regression 1.560)
Eric Tucker commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) Can we please get this into the next release? Cannot upgrade Jenkins until this issue is resolved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-2487) Please wait, getting ready to work takes very long
Oleg Nenashev commented on JENKINS-2487 Please wait, getting ready to work takes very long Nobody excuses for the "issue". Many systems (including Jenkins) are slow by design due to the runtime specifics. In the case of Jenkins there're known bottlenecks: queue handling, security checks, listeners, etc. The performance could be improved step-by-step, but it is not a single issue in the code. If you have such strong complains, just bother to provide the info about your installation and to profile your Jenkins installation. Any other contributions to Jenkins core or plugins would be appreciated as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22750) Polling no longer triggers builds (regression 1.560)
Eric Tucker edited a comment on JENKINS-22750 Polling no longer triggers builds (regression 1.560) Can we please get this into the next release? Cannot upgrade Jenkins until this issue is resolved. The regression only broke polling for users with no slaves and using an SCM that requires a workspace for polling. So, most setups? The average installation of Jenkins is probably not using slaves and most are probably using git. This statement is ridiculous. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Kevin Phillips commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed So far, based on the recent comment threads, my admittedly superficial understanding of the root cause, and some quick Googling, it seems there are only a few viable options to resolve this issue: 1. A python script was written by an earlier commenter, which leverages the BUILD_ID env var to strategically control the lifetime of the pdbsrv process itself without affecting other parts of the build. This seems like a pretty harsh workaround to what is obviously a problem introduced by changes made in the latest Jenkins LTS update. 2. Roll back the version of this "process tree killer" used by Jenkins LTS to v1.16, before this new "recursive" behavior was added according to an earlier comment. I assume LTS releases are expected to maintain a certain level of stability and consistency in their behaviors. That being the case, this change obviously caused critical, debilitating side effects to Visual Studio users and thus should not have been included in an update release. 3. Provide some kind of workaround within the "process tree killer" or the Jenkins core libraries to compensate for this newly discovered problem. From what I gather from the earlier comments, this may be a non trivial task. However, if this new recursive logic in the process tree killer is absolutely required in Jenkins LTS for some reason, I think this work must be done. Anything else (scripting, documentation notes, etc.) would just be trying to hide the fact that this is an underlying architectural problem - imo. 4. Accept the fact that Visual Studio users will likely never use Jenkins version that include this "new feature", forcing them to use versions of Jenkins that predate this change. Currently this is the solution that my team and I have chosen to adopt until a more reasonable solution can be found. Just to clarify our rationale for this decision: Using v1.532.x works just fine with Visual Studio. Upgrading to v1.554.x does not work - at all. Period. To do otherwise would require extra time (and, hence, money) on our part to workaround the problem, for little to no benefit on our 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Kevin Phillips edited a comment on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed So far, based on the recent comment threads, my admittedly superficial understanding of the root cause, and some quick Googling, it seems there are only a few viable options to resolve this issue: 1. A python script was written by an earlier commenter, which leverages the BUILD_ID env var to strategically control the lifetime of the pdbsrv process itself without affecting other parts of the build. This seems like a pretty harsh workaround to what is obviously a problem introduced by changes made in the latest Jenkins LTS update. 2. Roll back the version of this "process tree killer" used by Jenkins LTS to v1.16, before this new "recursive" behavior was added according to an earlier comment. I assume LTS releases are expected to maintain a certain level of stability and consistency in their behaviors. That being the case, this change obviously caused critical, debilitating side effects to Visual Studio users and thus should not have been included in an update release. 3. Provide some kind of workaround within the "process tree killer" or the Jenkins core libraries to compensate for this newly discovered problem. From what I gather from the earlier comments, this may be a non trivial task. However, if this new recursive logic in the process tree killer is absolutely required in Jenkins LTS for some reason, I think this work must be done. Anything else (scripting, documentation notes, etc.) would just be trying to hide the fact that this is an underlying architectural problem - imo. 4. Accept the fact that Visual Studio users will likely never use Jenkins version that include this "new feature", forcing them to use versions of Jenkins that predate this change. Currently this is the solution that my team and I have chosen to adopt until a more reasonable solution can be found. Just to clarify our rationale for this decision: Using v1.532.x works just fine with Visual Studio. Upgrading to v1.554.x does not work - at all. Period. To do otherwise would require extra time (and, hence, money) on our part to workaround the problem, for little to no benefit on our 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] [timestamper] (JENKINS-23108) Printout different between current and previous line
Karl-Heinz Marbaise created JENKINS-23108 Printout different between current and previous line Issue Type: Improvement Affects Versions: current Assignee: stevengbrown Components: timestamper Created: 20/May/14 12:48 PM Description: It would be nice having an output which prints out the calculated difference between the current and the previous line. 00:00:00.000 Started... 00:00:01.256 Doing something 00:00:12.245 An other step. 00:00:00.657 More things.. ... With this output i can directly see that the 3. line take 12.245 seconds to execute... This would make analyzing performance issue very simple. Project: Jenkins Priority: Major Reporter: Karl-Heinz Marbaise This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Kevin Phillips commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed Aside I probably should say that I truly believe the real root cause of this problem is an underlying architectural issue with Visual Studio and it's use of this pdbsrv process in their newer compilers, but numerous forums and bug reports to Microsoft appear to fall on deaf ears (ie: they claim it's working this way by design). Given the fact that this has been a problem in Visual Studio for several releases spread across many years it's unlikely to change any time soon, so you may be forced to compensate for it here in your tool. To do otherwise will simply make it more difficult (and, by extension, less likely) for Visual Studio users to adopt / continue using your tool. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17813) Jobs should have built in option to never clean workspace
Kevin Phillips commented on JENKINS-17813 Jobs should have built in option to never clean workspace Workspaces, where Jenkins stores temporary build data, are supposed to be managed by Jenkins as much as possible Agreed it's not an 'advanced project option' hidden by default by accident! Can you point me to this "advanced project option"? I have been unable to locate any option that effectively disables this behavior, advanced or not. Perhaps it's too well hidden Deletion of workspace contents is trivial Possibly for small projects, or projects that are relatively well structured. Large projects, with code written decades ago with varying degrees of "cleanliness" are not so easily managed. For your specific use case (which seems very unusual), it'd likely be best to not use a custom workspace, but just cd or xcopy out of that directory to accomplish your specific goals. Doing so would require me to do all of my own artifact management, thus defeating the purpose of using Jenkins in the first place, but may be worth considering. Maybe you're just using the wrong tool for the job: Something like Windows Scheduled Tasks might be better suited for what you're trying to accomplish Interesting suggestion. If I could create a scheduled task that could trigger when changes were made to a source-code repository, I would consider that approach, but so far as I can tell this is not possible. The closest thing would be to have a task scheduled to run every minute, which I'm not sure would work so well on Windows. ...consider emailing the jenkinsci-users list asking for advice in your specific situation ... this is also the wrong place to discuss this... For future reference, can you give me more details of where this 'jenkinsci-users' list is, or where the 'appropriate' venue for this discussion would be? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin test
Marco Miller updated JENKINS-23004 Contributing 1st Active-Directory plugin test Change By: Marco Miller (20/May/14 1:15 PM) Description: /*** Scenario:UsercanadministerJenkinsafterADsecurityconfigured-br*GivenaJenkinsinstancethatisoftype=existingbr*Andapre-installedactive-directorypluginversion1.34(1.37failed)br*AndanADsecurityconfigurationthatismatrix-based(projectornot)br*AndauseraddedtothatmatrixsoshecanAdministerbr*WhenIsavesuchanADsecurityconfigurationbr*ThenthatAdminusercanlog-intothatJenkinsbr*AndshecanviewheruserwithAdministerset.br * Scenario:TODOadd-ingtest(s)foruser / group;workinprogress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin test
Marco Miller updated JENKINS-23004 Contributing 1st Active-Directory plugin test Change By: Marco Miller (20/May/14 1:14 PM) Description: TODO /***Scenario:UsercanadministerJenkinsafterADsecurityconfigured-br*GivenaJenkinsinstancethatisoftype=existingbr*Andapre-installedactive-directorypluginversion1.34(1.37failed)br*AndanADsecurityconfigurationthatismatrix-based(projectornot)br*AndauseraddedtothatmatrixsoshecanAdministerbr*WhenIsavesuchanADsecurityconfigurationbr*ThenthatAdminusercanlog-intothatJenkinsbr*AndshecanviewheruserwithAdministerset.br*/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin test
Marco Miller updated JENKINS-23004 Contributing 1st Active-Directory plugin test Change By: Marco Miller (20/May/14 1:16 PM) Description: Scenario:UsercanadministerJenkinsafterADsecurityconfigured-br*GivenaJenkinsinstancethatisoftype=existingbr*Andapre-installedactive-directorypluginversion1.34(1.37failed)br*AndanADsecurityconfigurationthatismatrix-based(projectornot)br*AndauseraddedtothatmatrixsoshecanAdministerbr*WhenIsavesuchanADsecurityconfigurationbr*ThenthatAdminusercanlog-intothatJenkinsbr*AndshecanviewheruserwithAdministerset. br Scenario:TODOadd-ingtest(s)foruser/group;workinprogress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-2487) Please wait, getting ready to work takes very long
francisdb commented on JENKINS-2487 Please wait, getting ready to work takes very long If all builds ever executed need to be read in before jenkins kan show it's main ui this indeed sounds like a design issue. Anyway, I no longer have a big instance running so I can live with the ~1 min startup time we have here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18213) Copying an existing job to a new one gives an error with Status Code: 500
Daniel Beck commented on JENKINS-18213 Copying an existing job to a new one gives an error with Status Code: 500 1.512 is pretty outdated (a year old!) therefore the question whether this is still an issue in current Jenkins or could be resolved by updating. Could you at least update to 1.532.3, the previous LTS release of Jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22750) Polling no longer triggers builds (regression 1.560)
Jesse Glick commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) FWIW, for performance and security reasons it is recommended to not have any executors on the master (use slaves exclusively); and current versions of the Git plugin default to remote polling (no workspace required). Some commercial SCMs unfortunately require workspace-based polling. At any rate, this has already been put in for 1.565. Could be backported to the rc branch for 1.564 as well; not sure who “owns” 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] [core] (JENKINS-17813) Jobs should have built in option to never clean workspace
Kevin Phillips commented on JENKINS-17813 Jobs should have built in option to never clean workspace For future reference, we ended up working around our original use case using symbolic links, something like this: Setup Jenkins job to monitor source files in SVN Run the job once on the agent of choice Log into remote machine and make symbolic links to the appropriate files / folders in the appropriate locations (e.g.: mklink "%userprofile%\project.settings" "c:\jenkins\workspaces\job_folder\project.settings" ) Then the files and folders exist within the Jenkins workspace realm, their sources can be monitored directly in the SCM and kept up to date automatically, without requiring further human intervention. Also deleting and restoring the files leaves the symbolic links largely unaffected - so long as you take care not to run tasks in parallel that may require access to those artifacts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17813) Jobs should have built in option to never clean workspace
Kevin Phillips commented on JENKINS-17813 Jobs should have built in option to never clean workspace Also for reference sake, you should be aware that I've found it helpful to use Jenkins as a generic build farm management tool as well as a build automation tool. Including such configuration management operations on the dashboard provides a consistent location and toolset which I've found to be much easier than having several different tools which serve similar purposes all monitored and maintained separately. Although it may not have been designed as such, it serves the purpose well - most of the time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Daniel Beck commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed Does this also happen with MSBuild, or only Devenv? Can you switch to the former? What about systems without Visual Studio installed, instead using only MSBuild/Windows SDK? (I'm not too familiar with Visual Studio projects beyond pressing an F-key to build them, so this might well be a stupid question) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21224) Catch all errors thrown by listeners
Jesse Glick commented on JENKINS-21224 Catch all errors thrown by listeners That is definitely not a supported use case. A listener is for receiving event notifications only. APIs intended to allow listeners to affect the caller state so explicitly and generally have a different signature, either throwing a checked exception or returning boolean. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-13975) Promoted-builds not following jenkins access control policies
Liam Nichols commented on JENKINS-13975 Promoted-builds not following jenkins access control policies Its getting on for 2 years since this was reported, is anybody able to look into it? 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-22750) Polling no longer triggers builds (regression 1.560)
Jens Brejner commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) You are right - the administrator should do 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-22750) Polling no longer triggers builds (regression 1.560)
Eric Tucker commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) If that's the recommended approach then the default installation of Jenkins should be configured with a master and a single slave by default. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Kevin Phillips commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed From what I understand this is a problem with the compiler, which I think is the same compiler used under the hood by both msbuild and devenv, however I have not confirmed first hand the same problems arise in both situations. I'd be surprised if they didn't. As for building our projects without Visual Studio, with just MSBuild / Windows SDK, we have as of yet been unable to do so. We have heavy dependencies on MFC which hasn't, until recently, been available outside of Visual Studio. Plus we have had numerous technical issues migrating to the newer versions of the SDK / MSBuild that do include them. Regardless, again I'd be surprised if any of this made any difference unless the compiler that ships with the SDK is fundamentally architecturally different than the one that ships with VS. If I can spare some time to confirm a few of these details I'll let you know, even if just for curiosities sake. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22750) Polling no longer triggers builds (regression 1.560)
Eric Tucker commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) I mean that without any steps other than 'yum install jenkins' I should get the behaviour that is best practice. The average user is not going to know about slaves. I myself only found out about slaves because of this bug. If we're saying I should have been using slaves all along (and we've been using Jenkins for over a year) then there's a problem with the default setup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Jesse Glick updated JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted Change By: Jesse Glick (20/May/14 1:35 PM) Labels: JNLP MasterSlave disconnect javastartweb regressionslaves This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-2487) Please wait, getting ready to work takes very long
Oleg Nenashev commented on JENKINS-2487 Please wait, getting ready to work takes very long @francisdb If all builds ever executed need to be read in before jenkins kan show it's main ui this indeed sounds like a design issue This issue has been already solved in 1.485 (JENKINS-8754). However, there were many regression issues caused by the lazy loading, hence it is recommended to use 1.532+ Now Jenkins loads only the required set if builds. Some plugins may require all builds to be loaded, but it is a topic for additional issues on Jenkins JIRA. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22803) 'JellyTagException: st:include For input string: ' on job view
João Enomoto commented on JENKINS-22803 JellyTagException: st:include For input string: on job view Sorry for being a bit late. Our Jenkins server is a Windows Server 2008 R2. Not quite sure if is there symbolic link support for it, already heard about it somehow but not completely sure. 'lastSuccessfulBuild' is a text file whose content is a integer number, probably pointing to an build's id. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23063) Test Result Trend : flipTrend works fine with Opera, not with FF, Chrome or IE
Philippe Lambert updated JENKINS-23063 Test Result Trend : flipTrend works fine with Opera, not with FF, Chrome or IE Change By: Philippe Lambert (20/May/14 1:53 PM) Description: TestResultTrendchartseemstohaveanissue:the(justshowfailures)linkisbrokeni.e.test/flipTrendiscalledbutdiagramisstillthesame(test#andfailure#).ThishappenswithFirefox(ESR24.4.0),Chrome(34.0.1847.137)andInternetExplorer(8.0.760.1.17514and11.0.9600.17041),whicharethemainbrowsersusedinmycompany.HoweveritdoesworkwhenusingOpera(12.17)!Iexperiencedexactlythesamebehaviourwithsomeothercolleaguesmachines.Thisfeaturewasstillworkingproperlyafewweeksago.Onlychangeswereaboutjobsrenaming(containingwhitespaces).Maybeafirstleadfortheinvestigation. --EDIT---Idoconfirm:removingspacesfixestheissue.AndusingtheDisplaynameoptionhelpedmetofillmyneeds.--EDIT--- OS:Windows7EnterpriseJenkins:version1.562FYIaposthasbeencreatedintheJenkinsUsersGooglegroupaboutthisissue:https://groups.google.com/forum/#!topic/jenkinsci-users/xQhboJoYu_w This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-9715) 1.411/1.412 - Several plugins go to uninstalled state.
Oleg Nenashev resolved JENKINS-9715 as Cannot Reproduce 1.411/1.412 - Several plugins go to uninstalled state. The issue is very outdated. Please reopen the issue if it appears again in newer versions Change By: Oleg Nenashev (20/May/14 2:14 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Steve Carter commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed Solution 5: Don't run MsBuild projects in parallel. Before I built the python workaround, that's what I did using a throttling plugin. Works fine. pdbsrv gets killed at the end of each build, and started afresh by the microsoft toolchain on the next job. But if you are trying to do continuous build on development branches, then this won't have the capacity to keep up. Solution 6: Set BUILD_ID to hide pdbsrv from the processtreekiller. Live with the chance that once in a while pdbsrv might time out mid-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] [svnmerge] (JENKINS-23107) Rebase not working for simple setup
Hugues Chabot commented on JENKINS-23107 Rebase not working for simple setup Can you confirm if the bug persist after the project is build for the first time? I suspect this happens because the workspace did not exists. There is a pull request regarding 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] [core] (JENKINS-8927) Create a view from the XML API
Oleg Nenashev commented on JENKINS-8927 Create a view from the XML API @Patrik Should we consider the issue as "Resolved"? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-8505) Allow users to re-enable Monitors
Oleg Nenashev closed JENKINS-8505 as Fixed Allow users to re-enable Monitors Change By: Oleg Nenashev (20/May/14 2:23 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] [core] (JENKINS-8980) Turn ListView regexp support into ViewJobFilter
Oleg Nenashev resolved JENKINS-8980 as Fixed Turn ListView regexp support into ViewJobFilter View Job Filters Plugin provides such filter https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters I suppose there's no need to touch the "legacy" functionality since it does not add new features Change By: Oleg Nenashev (20/May/14 2:19 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-14538) Separate configure tools page
Oleg Nenashev updated JENKINS-14538 Separate configure tools page Currently, the request is just an improvement. Most of the work has been already integrated into the core Change By: Oleg Nenashev (20/May/14 2:27 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jiratestresultreporter] (JENKINS-23109) JiraTestResultReporter: Add ability to customize issue creation
Shawn Speer created JENKINS-23109 JiraTestResultReporter: Add ability to customize issue creation Issue Type: Improvement Assignee: Unassigned Components: jiratestresultreporter Created: 20/May/14 2:29 PM Description: A comment was made in the plugin home page about adding the ability to customize the created issue: Is it possible to customize issue creation: set component set fix version set affected version set priority etc. To add to this.. set assignee customize description Attach files I think that this will be really useful. It is nice to have issues generated automatically for each failed test case, however there isn't much context in the issue and it requires a good bit of manual intervention to get the useful information within the issue for a developer to analyze. Allowing to at least customize the description would give the user the flexibility to add more information into the issue. For example, a link to the test case result page or the jenkins build home page could be inserted into the description. Environment: Jenkins version 1.563 JiraTestResultReporter version 1.0.4 Project: Jenkins Priority: Minor Reporter: Shawn Speer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-8505) Allow users to re-enable Monitors
Oleg Nenashev resolved JENKINS-8505 as Fixed Allow users to re-enable Monitors Noe monitors can be configured via WebUI in newest Jenkins versions Change By: Oleg Nenashev (20/May/14 2:23 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] [scm-sync-configuration] (JENKINS-21827) Error with SCM-syn-configuration
Dave McClelland commented on JENKINS-21827 Error with SCM-syn-configuration Hi Frédéric, I don't mean to pester you, but it would be nice to have an update on the status of this issue. Is it being looked into? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [slave-setup] (JENKINS-23110) StreamCorruptedException: invalid stream header: 090CACED
Giuseppe Mazzotta created JENKINS-23110 StreamCorruptedException: invalid stream header: 090CACED Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 20/May/14 2:38 PM Description: I am using the option for creating slaves through command executed on master. This is the error: ===[JENKINS REMOTING CAPACITY]===Exception in thread "main" java.io.StreamCorruptedException: invalid stream header: 090CACED at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804) at java.io.ObjectInputStream.init(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.init(ObjectInputStreamEx.java:40) at hudson.remoting.ChannelBuilder.makeTransport(ChannelBuilder.java:259) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:220) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:149) at hudson.remoting.Launcher.main(Launcher.java:507) at hudson.remoting.Launcher.runWithStdinStdout(Launcher.java:457) at hudson.remoting.Launcher.run(Launcher.java:238) at hudson.remoting.Launcher.main(Launcher.java:192) ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:443) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:339) at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) ERROR: Connection terminated java.io.IOException: Unexpected EOF at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:90) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected EOF at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:90) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) I have captured (with a `tee` command) this output sent by the slave: ===[JENKINS REMOTING CAPACITY]===rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQABAgABSgAEbWFza3hwAP4= I have tried slave options like -text and definition of encoding without success. My integration with Jenkins has come to a dead end Environment: Jenkins 1.563 on Ubuntu 14 Project: Jenkins Priority: Major
[JIRA] [slave-setup] (JENKINS-23110) StreamCorruptedException: invalid stream header: 090CACED
Giuseppe Mazzotta updated JENKINS-23110 StreamCorruptedException: invalid stream header: 090CACED Change By: Giuseppe Mazzotta (20/May/14 2:42 PM) Environment: Jenkins1.563 onUbuntu14 runningwithOpenJDK7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22750) Polling no longer triggers builds (regression 1.560)
Jesse Glick commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) Unfortunately by its nature the default setup cannot include slaves. (Well, it could add a local slave, but that does not have any benefit.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Kevin Phillips commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed Solution 5: Don't run MsBuild projects in parallel. That may be fine for small projects but not for larger ones. For example, our main codebase is configured with about 40 jobs per configuration to build each "tier" or "module" in our codebase more efficiently - running jobs in parallel whenever possible. Doing so reduced our "clean" build times from 14 hours to 3. Numbers like that are hard to argue against. Are there other ways we could achieve similar results? Possibly, but they all require time and effort (aka: money) which we do not have. Solution 6: Set BUILD_ID to hide pdbsrv from the processtreekiller. Live with the chance that once in a while pdbsrv might time out mid-build. Could you clarify what you are referring to here? I assume you mean something other than using your python script since that was the very first "potential fix" I had mentioned above. It has been my experience that so long as you leave Visual Studio to it's own internal details to manage pdbsrv it works reliably for extended periods, keeping the service alive when needed and terminating it safely when it isn't, even if you run multiple builds in parallel via Jenkins. In fact that is what we do now and it never causes problems with our builds. This is saying something considering the size and scale of our build farm, with hundreds of jobs spread across nearly a dozen servers, all running 24/7! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20923) Jenkins CI website shows incorrect version (1.509.4, not 1.532.1) for latest LTS release
Oleg Nenashev resolved JENKINS-20923 as Fixed Jenkins CI website shows incorrect version (1.509.4, not 1.532.1) for latest LTS release Change By: Oleg Nenashev (20/May/14 2:47 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-23111) pull few folders via tfs
reut israeli created JENKINS-23111 pull few folders via tfs Issue Type: Bug Assignee: redsolo Components: tfs Created: 20/May/14 2:48 PM Description: How do pull multiple TFS folders into a single workspace in Jenkis , like we have with subversion , we can add different URL. Due Date: 30/May/14 12:00 AM Project: Jenkins Priority: Major Reporter: reut israeli This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-12753) PluginManager.dynamicLoad on installed plugin fails on NFS with IOException not RestartRequiredException
Jesse Glick updated JENKINS-12753 PluginManager.dynamicLoad on installed plugin fails on NFS with IOException not RestartRequiredException It seems that the problem has been misstated because the bug itself masks the problem. When you already have a plugin installed, you cannot dynamically load its update, ever. Normally Jenkins stops you from trying to do so by throwing a RestartRequiredException. Unfortunately when PluginManager.dynamicLoad is checking whether the plugin is already installed, it calls ClassicPluginStrategy.createPluginWrapper which actually unpacks the *.hpi right away, and when on a filesystem with locks, that fails—and the IOException then is reported as if this were the real error, when the error is simply a user misunderstanding. Change By: Jesse Glick (20/May/14 3:05 PM) Summary: Instantupdateofpluginsdoesntworkinnfsdirectory PluginManager.dynamicLoadoninstalledpluginfailsonNFSwithIOExceptionnotRestartRequiredException Labels: lockplugin Component/s: core Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12753) PluginManager.dynamicLoad on installed plugin fails on NFS with IOException not RestartRequiredException
Jesse Glick commented on JENKINS-12753 PluginManager.dynamicLoad on installed plugin fails on NFS with IOException not RestartRequiredException Here is a typical stack trace: java.nio.file.FileSystemException: /…/plugins/credentials/WEB-INF/lib/.nfs…: Device or resource busy at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:244) at sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:103) at java.nio.file.Files.delete(Files.java:1077) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.Util.deleteFile(Util.java:238) at hudson.Util.deleteRecursive(Util.java:301) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:300) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:292) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:292) at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:423) at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:128) at hudson.PluginManager.dynamicLoad(PluginManager.java:412) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1300) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22750) Polling no longer triggers builds (regression 1.560)
Daniel Beck commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) How about an administrative monitor similar to the one shown when security is disabled? Link to /computer/new as well as a wiki page describing node best practices. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Daniel Beck commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed Maybe the following workaround would work: If mspdbsrv.exe runs as the user launching devenv, you could create a whole bunch of slaves all running on the same machine, but as different users, each having a single executor. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-21827) Error with SCM-syn-configuration
Frédéric Camblor commented on JENKINS-21827 Error with SCM-syn-configuration Which version of svn plugin do you use ? There seems to be a problem with svn 2.0 (and greater) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-21827) Error with SCM-syn-configuration
Dave McClelland commented on JENKINS-21827 Error with SCM-syn-configuration 2.3, recently upgraded to 2.4. Seeing it on both. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22750) Polling no longer triggers builds (regression 1.560)
Herbert Vojčík commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) What can be done, is not to install any executors by default, allow users to install master executors by hand, but with visible not that this is not recommended and link to "add a node" screen. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22750) Polling no longer triggers builds (regression 1.560)
Emmett Keyser commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) I disagree that the master should not be able to execute. It's a build server - why does it need to be more complicated by default? Slaves? I don't need to manage yet another machine (in this case a slave req not to be local). Hopefully not too brash but I'm just stating what I think most people might also agree with. On another note, thanks to all who got this into 1.650 and for the work that went into fixing this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dry] (JENKINS-23102) dry plugin slow down jenkins.
Ulli Hafner commented on JENKINS-23102 dry plugin slow down jenkins. Please attach a thread dump. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin test
SCM/JIRA link daemon commented on JENKINS-23004 Contributing 1st Active-Directory plugin test Code changed in jenkins User: Marco Miller Path: src/main/java/org/jenkinsci/test/acceptance/plugins/active_directory/ActiveDirectoryEnv.java src/main/java/org/jenkinsci/test/acceptance/plugins/active_directory/ActiveDirectorySecurity.java src/test/java/plugins/ActiveDirectoryTest.java http://jenkins-ci.org/commit/acceptance-test-harness/53aa13aa97700348951415d11aabb2e886931c68 Log: JENKINS-23004 Start AD plugin test(s) = 1st scenario; usage: javadoc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ssh-slaves] (JENKINS-22320) High CPU consumption because of SSH communication
Joshua K commented on JENKINS-22320 High CPU consumption because of SSH communication I strace'd and it looks like a lot of the traffic is due to repeatedly sending exceptions over the remoting channel: write(8, "q\0~\0\5\0\2\16`\0\0\0\0sr\0 java.lang.ClassNotFoundException\177Z\315f\324 \216\2\0\1L\0\2exq\0~\0\1xq\0~\0\10pt\0\23java.nio.file.Filesuq\0~\0\r\0\0\0\21sq\0~\0\17\0\0\5_t\0\33jenkins.util.AntClassLoadert\0\23AntClassLoader.javat\0\25findClassInComponentssq\0~\0\17\0\0\5-q\0~\0004q\0~\0005t\0\tfindClasssq\0~\0\17", 233) = 233 This is plausible, as our slaves/master run on Java 1.6 and java.nio.file.Files is new in 1.7. I will try to bump our slaves to use JDK 1.7 and see if that helps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12753) PluginManager.dynamicLoad on installed plugin fails on NFS with IOException not RestartRequiredException
Jesse Glick started work on JENKINS-12753 PluginManager.dynamicLoad on installed plugin fails on NFS with IOException not RestartRequiredException Change By: Jesse Glick (20/May/14 4:05 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12753) PluginManager.dynamicLoad on installed plugin fails on NFS with IOException not RestartRequiredException
Jesse Glick assigned JENKINS-12753 to Jesse Glick PluginManager.dynamicLoad on installed plugin fails on NFS with IOException not RestartRequiredException Change By: Jesse Glick (20/May/14 4:05 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
