[JIRA] [core] (JENKINS-19939) Discard Old Builds I/O Performance Issue
Title: Message Title Tomasz Śniatowski commented on JENKINS-19939 Re: Discard Old Builds I/O Performance Issue Hi, thanks a lot for replying. Re 1: I personally do not find it a critical problem that something happens after a build status is determined, but before a next build can happen. It might be a bit confusing, but not the largest UI issue here from my POV. Re 2: This is my main gripe. If something bad happens and discarding takes a long time, there is no trace left anywhere. This makes it hard to analyse or report the problem. Re 3: I have no hard data (because without any logs it's difficult for me) but I do get a feeling that the discarding process is far more IO-heavy than it should be. It might worthwhile to mention something in the config section, but waiting for more data is probably fine too. Yesterday we had a transient IO performance issue in our Jenkins master disk hardware, and a job config change that ended up discarding some 20k builds (almost empty: no artifacts; 10 files and 40KB per build directory). This took over an hour, and I could see it deleting a couple build directories per second. Now whether this was solely caused by the hardware, or if discarding is otherwise sub-optimal (like syncing too much), is something I don't know – but shell IO at the time did not feel as bad. I have to admit though that without better data (like the actual time spent discarding, the time it took to just rm equivalent files, whether there was anything else going on, reproducibility, etc.) it's hard to tell. That's why I primarily just would like to have the logging. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] [ldap-plugin] (JENKINS-28474) Confusing Chrome password manager behavior on ldap auth settings page
Title: Message Title Tomasz Śniatowski commented on JENKINS-28474 Re: Confusing Chrome password manager behavior on ldap auth settings page As per the above it seems that using autocomplete with a value other than off might work Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-28367) perforce plugin don't support P4 ticket authentication
Title: Message Title Bin Yin commented on JENKINS-28367 Re: perforce plugin don't support P4 ticket authentication Thanks for the code change for the fix. I think the fix can resolved this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-28476) Unexpected termination of the channel
Title: Message Title Eduard Biceri-Matei commented on JENKINS-28476 Re: Unexpected termination of the channel Slave log: ===[JENKINS REMOTING CAPACITY]===channel started Slave.jar version: 2.49 This is a Unix slave Evacuated stdout Slave successfully connected and online ERROR: Connection terminated ha:WB+LCP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA=java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.init(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.init(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) ERROR: Socket connection to SSH server was lost ha:WB+LCP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA=java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:196) at java.net.SocketInputStream.read(SocketInputStream.java:122) at com.trilead.ssh2.crypto.cipher.CipherInputStream.fill_buffer(CipherInputStream.java:41) at com.trilead.ssh2.crypto.cipher.CipherInputStream.internal_read(CipherInputStream.java:52) at com.trilead.ssh2.crypto.cipher.CipherInputStream.getBlock(CipherInputStream.java:79) at com.trilead.ssh2.crypto.cipher.CipherInputStream.read(CipherInputStream.java:108) at com.trilead.ssh2.transport.TransportConnection.receiveMessage(TransportConnection.java:232) at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:693) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:489) at java.lang.Thread.run(Thread.java:745) Slave JVM has not reported exit code before the socket was lost [05/22/15 09:44:07] [SSH] Connection closed. Add Comment
[JIRA] [openshift-deployer-plugin] (JENKINS-28509) Deployer Plugin doesn't support ruby deployments
Title: Message Title Will Buck commented on JENKINS-28509 Re: Deployer Plugin doesn't support ruby deployments I would love for this option as well. I think it would benefit Node users additionally, as they do not bundle their source into some kind of deployable either, generally speaking. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-28546) logstash doesn't connect to a server and puts no messages out
Title: Message Title Rinaldo DiGiorgio updated an issue Jenkins / JENKINS-28546 logstash doesn't connect to a server and puts no messages out Change By: Rinaldo DiGiorgio Summary: Plugin logstash doesn'tconnecttoaserverandputsnomessagesout Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Title: Message Title James Judd commented on JENKINS-26854 Re: EC2 slave launch stops working after a while with AmazonServiceException Request has expired It's been almost 24 hours and I have not had any expirations. Created PR #148 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Title: Message Title John Mellor commented on JENKINS-15980 Re: Promotion job doesn't execute on the same machine that the build job executed on. Can we bump this up in priority and get a fix? Its a royal pain to have to hack around it, since it is normal for the promotion to pick a different server than the build artifacts exist on. Simply forcing the promotion to run on the same machine would resolve most of the angst with this plugin and remove most of the need for the published hack of using the copy-artifact plugin to another host, to work around the real issue. My local unix/linux workaround for this issue is to add a stanza to the promotion script to copy the artifacts to the current host. Its not pretty, but it works until this issue gets fixed. HACK: The artifacts may be on a different build host mkdir -p $ARTIFACTS PROMOTED_HOST=`echo $PROMOTED_URL | sed 's%^http://#40;.*#41;:.*%\1%'` scp $PROMOTED_HOST:jobs/$PROMOTED_JOB_NAME/builds/$PROMOTED_NUMBER/archive/$ARTIFACTS/* $ARTIFACTS Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-14157) allow to set subversion workspace version per slave
Title: Message Title Vincent Furia commented on JENKINS-14157 Re: allow to set subversion workspace version per slave I've been having the same problem. The workaround I'm using is to set the svn version in the jenkins plugin to the lowest version I use. Then I call svn upgrade as the first step of my build process. (Really, I check for an error from svn info, then upgrade if needed). Apparently svnkit is tolerant of dealing with different subversion versions regardless of how it is configured in jenkins. After the ugprade, jenkins can still perform an update. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openshift-deployer-plugin] (JENKINS-28509) Deployer Plugin doesn't support ruby deployments
Title: Message Title Will Buck edited a comment on JENKINS-28509 Re: Deployer Plugin doesn't support ruby deployments Iwouldloveforthisoptionaswell.IthinkitwouldbenefitNode andPython usersadditionally,as they neither donotbundletheirsourceintosomekindofdeployableeither ,generallyspeaking asfarasIamaware . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-28546) Plugin doesn't connect to a server and puts no messages out
Title: Message Title Rinaldo DiGiorgio created an issue Jenkins / JENKINS-28546 Plugin doesn't connect to a server and puts no messages out Issue Type: Bug Assignee: Unassigned Components: logstash-plugin Created: 22/May/15 8:31 PM Environment: Elasticsearch 1.4 or Elasticsearch 1.5 logstash 1.0.4 Jenkins 1.613 Labels: logstash elasticsearch Priority: Minor Reporter: Rinaldo DiGiorgio I install the plugin and try to access the server and there is no activity in the log file with default logging. I am using an elasticsearch server without a password. Perhaps that is the issue.
[JIRA] [ansible-plugin] (JENKINS-28547) Inline content Inventory is not interpolated with Jenkins environment variables
Title: Message Title Jean-Christophe Sirot created an issue Jenkins / JENKINS-28547 Inline content Inventory is not interpolated with Jenkins environment variables Issue Type: Bug Assignee: Jean-Christophe Sirot Components: ansible-plugin Created: 22/May/15 10:35 PM Priority: Minor Reporter: Jean-Christophe Sirot Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received
[JIRA] [build-environment-plugin] (JENKINS-28466) Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked
Title: Message Title liu yecheng started work on JENKINS-28466 Change By: liu yecheng Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-environment-plugin] (JENKINS-28466) Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked
Title: Message Title liu yecheng stopped work on JENKINS-28466 Change By: liu yecheng Status: InProgress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-environment-plugin] (JENKINS-28466) Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked
Title: Message Title liu yecheng started work on JENKINS-28466 Change By: liu yecheng Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-lambda-plugin] (JENKINS-28443) invoke lambda function as build-step and post-build-action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28443 Re: invoke lambda function as build-step and post-build-action Code changed in jenkins User: cast Path: src/main/java/com/xti/jenkins/plugin/awslambda/AWSLambdaPublisher.java src/main/java/com/xti/jenkins/plugin/awslambda/LambdaProminentAction.java src/main/java/com/xti/jenkins/plugin/awslambda/LambdaVariables.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/InvokeConfig.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/JsonParameter.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/JsonParameterVariables.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeAction.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeBuildStep.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeBuildStepVariables.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokePublisher.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeVariables.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvoker.java src/main/java/com/xti/jenkins/plugin/awslambda/service/LambdaService.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploadAction.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploadBuildStep.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploadBuildStepVariables.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploader.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/UploadConfig.java src/main/resources/com/xti/jenkins/plugin/awslambda/AWSLambdaPublisher/config.jelly src/main/resources/com/xti/jenkins/plugin/awslambda/LambdaVariables/config.jelly src/main/resources/com/xti/jenkins/plugin/awslambda/invoke/JsonParameter/config.jelly src/main/resources/com/xti/jenkins/plugin/awslambda/invoke/JsonParameterVariables/config.jelly src/main/resources/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeBuildStep/config.jelly src/main/resources/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeBuildStepVariables/config.jelly src/main/resources/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokePublisher/config.jelly src/main/resources/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeVariables/config.jelly src/main/resources/com/xti/jenkins/plugin/awslambda/upload/LambdaUploadBuildStep/config.jelly src/main/resources/com/xti/jenkins/plugin/awslambda/upload/LambdaUploadBuildStepVariables/config.jelly http://jenkins-ci.org/commit/aws-lambda-plugin/8efb77aa0b4743ba38f8a34da90316ea3a325ab7 Log: JENKINS-28443 Added AWS Lambda post build action awaiting testing for Lambda invocation Add Comment
[JIRA] [build-environment-plugin] (JENKINS-28466) Can't use environment variables like JENKINS_URL、JOB_URL、BUILD_URL in a new jenkins before it's save-button which is in system settings is clicked
Title: Message Title liu yecheng stopped work on JENKINS-28466 Change By: liu yecheng Status: InProgress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [snsnotify-plugin] (JENKINS-28542) SNS notifier plugin missing httpcore dependency
Title: Message Title Milo Hyson commented on JENKINS-28542 Re: SNS notifier plugin missing httpcore dependency Submitted a pull-request with a fix: https://github.com/jenkinsci/snsnotify-plugin/pull/6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap-plugin] (JENKINS-28508) Broken link on Tap Results
Title: Message Title Bruno P. Kinoshita started work on JENKINS-28508 Change By: Bruno P. Kinoshita Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-28527) Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error.
Title: Message Title Alex Earl commented on JENKINS-28527 Re: Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error. What was the previous version of Jenkins that you had? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap-plugin] (JENKINS-28508) Broken link on Tap Results
Title: Message Title Bruno P. Kinoshita commented on JENKINS-28508 Re: Broken link on Tap Results Had to fix the URL prefix in Jenkins. Also, updating the minimum version to check compatibility. Also had to change a few parts of the code to be compatible with API changes in Jenkins. Let me know if that works. Thanks for reporting the issue. Bruno Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstest-plugin] (JENKINS-28517) [MSTEST] XML coverage report file not found
Title: Message Title Daniel Wagner commented on JENKINS-28517 Re: [MSTEST] XML coverage report file not found Conversion with https://github.com/yasu-s/CoverageConverter doesn't solve the problem. I'll give you an update when I tried the other approach. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap-plugin] (JENKINS-28508) Broken link on Tap Results
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28508 Re: Broken link on Tap Results Code changed in jenkins User: Bruno P. Kinoshita Path: pom.xml src/main/java/org/tap4j/plugin/TapProjectAction.java src/main/java/org/tap4j/plugin/TapPublisher.java src/main/java/org/tap4j/plugin/TapResult.java src/main/java/org/tap4j/plugin/model/TapTestResultResult.java src/main/resources/org/tap4j/plugin/TapBuildAction/summary.jelly src/main/resources/org/tap4j/plugin/TapResult/index.jelly http://jenkins-ci.org/commit/tap-plugin/a410f4c079e1062bf09f7a55f225ffe728cc581a Log: [FIXED JENKINS-28508] Fix broken links on Tap Results Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap-plugin] (JENKINS-28508) Broken link on Tap Results
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28508 Broken link on Tap Results Change By: SCM/JIRA link daemon Status: InProgress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstest-plugin] (JENKINS-28517) [MSTEST] XML coverage report file not found
Title: Message Title Ivo Bellin Salarin commented on JENKINS-28517 Re: [MSTEST] XML coverage report file not found Could you please add some details about what's going wrong with the yasu-s coverage converter? Could you please provide the coveragexml files you get, if any? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstest-plugin] (JENKINS-28517) [MSTEST] XML coverage report file not found
Title: Message Title Daniel Wagner commented on JENKINS-28517 Re: [MSTEST] XML coverage report file not found Do you have any suggestion which tool to use for generation of the .coveragexml? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-28502) Install from http://groovy.codehaus.org installer method failing
Title: Message Title Daniel Spilker commented on JENKINS-28502 Re: Install from http://groovy.codehaus.org installer method failing Pull request: https://github.com/jenkinsci/backend-crawler/pull/34 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sbt-plugin] (JENKINS-27264) Latest 1.5 SBT Plugin does not work
Title: Message Title Paolo Giarrusso commented on JENKINS-27264 Re: Latest 1.5 SBT Plugin does not work After the above command, things looked better. That seems a problem though. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sbt-plugin] (JENKINS-27264) Latest 1.5 SBT Plugin does not work
Title: Message Title Paolo Giarrusso reopened an issue Jenkins / JENKINS-27264 Latest 1.5 SBT Plugin does not work Change By: Paolo Giarrusso Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [greenballs-plugin] (JENKINS-28422) Jenkins is hanging after a restart (deadlock)
Title: Message Title Ludovic Vercruysse commented on JENKINS-28422 Re: Jenkins is hanging after a restart (deadlock) Dear, Thanks for your help. We have taken into account the snapshot version enclosed to this ticket on our qualification environment and did not see any regression. However, there is no big volume on this environment; we will be able to check this in production. Could you please provide a final release for this plugin ? Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-28545) PipeTest#testReaderCloseWhileWriterIsStillWriting-local-compatibility remoting test hangs on JDK 1.6
Title: Message Title lacostej created an issue Jenkins / JENKINS-28545 PipeTest#testReaderCloseWhileWriterIsStillWriting-local-compatibility remoting test hangs on JDK 1.6 Issue Type: Bug Assignee: Unassigned Attachments: LOG.txt Components: remoting Created: 22/May/15 3:00 PM Environment: Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: /Users/lacostej/local/lib/apache-maven-3.0.5 Java version: 1.6.0_65, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.9.5, arch: x86_64, family: mac Priority: Minor Reporter: lacostej This test hangs when executed through mvn test. With Java 1.6.0_65, on my Mac: If I run mvn test -Dtest=PipeTest, it passes.
[JIRA] [core] (JENKINS-28532) Jobs get stuck in the queue
Title: Message Title James Howe commented on JENKINS-28532 Re: Jobs get stuck in the queue Downgraded plugin to 2.12. Restarted. Dependency graph errors not seen. Items already stuck in queue went through, though a few hours later they were stuck again. Status now shows as (pending—???) Manually deleted from disk fingerprints that mentioned jobs I'd recently deleted. Reloaded. As above. Opened and saved the config of a job that was stuck without making changes. Immediately all jobs that were stuck began executing. Became stuck again later. Unconfirmed if exactly the same jobs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sbt-plugin] (JENKINS-27264) Latest 1.5 SBT Plugin does not work
Title: Message Title Paolo Giarrusso commented on JENKINS-27264 Re: Latest 1.5 SBT Plugin does not work Now the plugin supposedly knows about 0.13.8, but I still don't see Jenkins auto-downloading SBT as documented. Do I really still need to use the above Groovy command? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28383) Infrequent ERROR: Error cloning remote repo 'origin'
Title: Message Title Tony Zedar commented on JENKINS-28383 Re: Infrequent ERROR: Error cloning remote repo 'origin' @mark waite I just finished upgrading Jenkins, the plugins, and Git. I will report back if I still see the error. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Title: Message Title
Ed Randall edited a comment on JENKINS-7695
Re: archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Amalsoexperiencingsimilar,in1.596.2{code}17:13:41GMT+01:00Archivingartifacts17:13:43GMT+01:00ERROR:Failedtoarchiveartifacts:LOGS/,target/**/LOGS/,target/robotframework/17:13:43GMT+01:00java.io.IOException:java.util.concurrent.ExecutionException:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.FilePath.copyRecursiveTo(FilePath.java:2213)17:13:43GMT+01:00 atjenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61)17:13:43GMT+01:00 athudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:218)17:13:43GMT+01:00 athudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.builder.FailFastBuilder.perform(FailFastBuilder.java:102)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.strategy.FailFastExecutionStrategy.perform(FailFastExecutionStrategy.java:63)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.ConditionalPublisher.perform(ConditionalPublisher.java:206)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.FlexiblePublisher.perform(FlexiblePublisher.java:124)17:13:43GMT+01:00 athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)17:13:43GMT+01:00 athudson.model.Build$BuildExecution.post2(Build.java:183)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)17:13:43GMT+01:00 athudson.model.Run.execute(Run.java:1784)17:13:43GMT+01:00 athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)17:13:43GMT+01:00 athudson.model.ResourceController.execute(ResourceController.java:89)17:13:43GMT+01:00 athudson.model.Executor.run(Executor.java:240)17:13:43GMT+01:00Causedby:java.util.concurrent.ExecutionException:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.remoting.Channel$3.adapt(Channel.java:784)17:13:43GMT+01:00 athudson.remoting.Channel$3.adapt(Channel.java:779)17:13:43GMT+01:00 athudson.remoting.FutureAdapter.get(FutureAdapter.java:55)17:13:43GMT+01:00 athudson.FilePath.copyRecursiveTo(FilePath.java:2211)17:13:43GMT+01:00 ...19more17:13:43GMT+01:00Causedby:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.org.apache.tools.tar.TarOutputStream.write(TarOutputStream.java:284)17:13:43GMT+01:00 athudson.util.io.TarArchiver.visit(TarArchiver.java:114)17:13:43GMT+01:00 athudson.util.DirScanner.scanSingle(DirScanner.java:49)17:13:43GMT+01:00 athudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2764)17:13:43GMT+01:00 athudson.FilePath.writeToTar(FilePath.java:2249)17:13:43GMT+01:00 athudson.FilePath.access$2100(FilePath.java:191)17:13:43GMT+01:00 athudson.FilePath$45.invoke(FilePath.java:2190)17:13:43GMT+01:00 athudson.FilePath$45.invoke(FilePath.java:2186)17:13:43GMT+01:00 athudson.FilePath$FileCallableWrapper.call(FilePath.java:2677)17:13:43GMT+01:00 athudson.remoting.UserRequest.perform(UserRequest.java:121)17:13:43GMT+01:00
[JIRA] [core] (JENKINS-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Title: Message Title
Ed Randall edited a comment on JENKINS-7695
Re: archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Amalsoexperiencingsimilar,in1.596.2{code}17:13:41GMT+01:00Archivingartifacts17:13:43GMT+01:00ERROR:Failedtoarchiveartifacts:LOGS/,target/**/LOGS/,target/robotframework/17:13:43GMT+01:00java.io.IOException:java.util.concurrent.ExecutionException:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.FilePath.copyRecursiveTo(FilePath.java:2213)17:13:43GMT+01:00 atjenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61)17:13:43GMT+01:00 athudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:218)17:13:43GMT+01:00 athudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.builder.FailFastBuilder.perform(FailFastBuilder.java:102)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.strategy.FailFastExecutionStrategy.perform(FailFastExecutionStrategy.java:63)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.ConditionalPublisher.perform(ConditionalPublisher.java:206)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.FlexiblePublisher.perform(FlexiblePublisher.java:124)17:13:43GMT+01:00 athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)17:13:43GMT+01:00 athudson.model.Build$BuildExecution.post2(Build.java:183)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)17:13:43GMT+01:00 athudson.model.Run.execute(Run.java:1784)17:13:43GMT+01:00 athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)17:13:43GMT+01:00 athudson.model.ResourceController.execute(ResourceController.java:89)17:13:43GMT+01:00 athudson.model.Executor.run(Executor.java:240)17:13:43GMT+01:00Causedby:java.util.concurrent.ExecutionException:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.remoting.Channel$3.adapt(Channel.java:784)17:13:43GMT+01:00 athudson.remoting.Channel$3.adapt(Channel.java:779)17:13:43GMT+01:00 athudson.remoting.FutureAdapter.get(FutureAdapter.java:55)17:13:43GMT+01:00 athudson.FilePath.copyRecursiveTo(FilePath.java:2211)17:13:43GMT+01:00 ...19more17:13:43GMT+01:00Causedby:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.org.apache.tools.tar.TarOutputStream.write(TarOutputStream.java:284)17:13:43GMT+01:00 athudson.util.io.TarArchiver.visit(TarArchiver.java:114)17:13:43GMT+01:00 athudson.util.DirScanner.scanSingle(DirScanner.java:49)17:13:43GMT+01:00 athudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2764)17:13:43GMT+01:00 athudson.FilePath.writeToTar(FilePath.java:2249)17:13:43GMT+01:00 athudson.FilePath.access$2100(FilePath.java:191)17:13:43GMT+01:00 athudson.FilePath$45.invoke(FilePath.java:2190)17:13:43GMT+01:00 athudson.FilePath$45.invoke(FilePath.java:2186)17:13:43GMT+01:00 athudson.FilePath$FileCallableWrapper.call(FilePath.java:2677)17:13:43GMT+01:00 athudson.remoting.UserRequest.perform(UserRequest.java:121)17:13:43GMT+01:00
[JIRA] [core] (JENKINS-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Title: Message Title Kanstantsin Shautsou commented on JENKINS-7695 Re: archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006' Have you tried disable flexible-publish for artifact manager? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-28367) perforce plugin don't support P4 ticket authentication
Title: Message Title Rob Petti commented on JENKINS-28367 Re: perforce plugin don't support P4 ticket authentication Here's a snapshot build containing the fix if you want to test it: https://dl.dropboxusercontent.com/u/1897231/perforce.hpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-28532) Jobs get stuck in the queue
Title: Message Title James Howe edited a comment on JENKINS-28532 Re: Jobs get stuck in the queue Downgradedpluginto2.12.Restarted.Dependencygrapherrorsnotseen.Itemsalreadystuckinqueuewentthrough,thoughafewhourslatertheywerestuckagain.Statusnowshowsas(pending—???)ManuallydeletedfromdiskfingerprintsthatmentionedjobsI'drecentlydeleted.Reloaded.Asabove.Openedandsavedtheconfigofajobthatwasstuckwithoutmakingchanges.Immediatelyalljobsthatwerestuckbeganexecuting. Became Nexttimethejobcamethroughthequeue,itandsomeothersgot stuckagain later . Unconfirmedifexactlythesamejobs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Title: Message Title
Ed Randall edited a comment on JENKINS-7695
Re: archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Amalsoexperiencingsimilar,in1.596.2{code}17:13:41GMT+01:00Archivingartifacts17:13:43GMT+01:00ERROR:Failedtoarchiveartifacts:LOGS/,target/**/LOGS/,target/robotframework/17:13:43GMT+01:00java.io.IOException:java.util.concurrent.ExecutionException:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.FilePath.copyRecursiveTo(FilePath.java:2213)17:13:43GMT+01:00 atjenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61)17:13:43GMT+01:00 athudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:218)17:13:43GMT+01:00 athudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.builder.FailFastBuilder.perform(FailFastBuilder.java:102)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.strategy.FailFastExecutionStrategy.perform(FailFastExecutionStrategy.java:63)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.ConditionalPublisher.perform(ConditionalPublisher.java:206)17:13:43GMT+01:00 atorg.jenkins_ci.plugins.flexible_publish.FlexiblePublisher.perform(FlexiblePublisher.java:124)17:13:43GMT+01:00 athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)17:13:43GMT+01:00 athudson.model.Build$BuildExecution.post2(Build.java:183)17:13:43GMT+01:00 athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)17:13:43GMT+01:00 athudson.model.Run.execute(Run.java:1784)17:13:43GMT+01:00 athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)17:13:43GMT+01:00 athudson.model.ResourceController.execute(ResourceController.java:89)17:13:43GMT+01:00 athudson.model.Executor.run(Executor.java:240)17:13:43GMT+01:00Causedby:java.util.concurrent.ExecutionException:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.remoting.Channel$3.adapt(Channel.java:784)17:13:43GMT+01:00 athudson.remoting.Channel$3.adapt(Channel.java:779)17:13:43GMT+01:00 athudson.remoting.FutureAdapter.get(FutureAdapter.java:55)17:13:43GMT+01:00 athudson.FilePath.copyRecursiveTo(FilePath.java:2211)17:13:43GMT+01:00 ...19more17:13:43GMT+01:00Causedby:java.io.IOException:requesttowrite'3085'bytesexceedssizeinheaderof'2581956'bytesforentry'target/path/to/file_20_05_2015.log'17:13:43GMT+01:00 athudson.org.apache.tools.tar.TarOutputStream.write(TarOutputStream.java:284)17:13:43GMT+01:00 athudson.util.io.TarArchiver.visit(TarArchiver.java:114)17:13:43GMT+01:00 athudson.util.DirScanner.scanSingle(DirScanner.java:49)17:13:43GMT+01:00 athudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2764)17:13:43GMT+01:00 athudson.FilePath.writeToTar(FilePath.java:2249)17:13:43GMT+01:00 athudson.FilePath.access$2100(FilePath.java:191)17:13:43GMT+01:00 athudson.FilePath$45.invoke(FilePath.java:2190)17:13:43GMT+01:00 athudson.FilePath$45.invoke(FilePath.java:2186)17:13:43GMT+01:00 athudson.FilePath$FileCallableWrapper.call(FilePath.java:2677)17:13:43GMT+01:00 athudson.remoting.UserRequest.perform(UserRequest.java:121)17:13:43GMT+01:00
[JIRA] [git-client-plugin] (JENKINS-23345) Git Plugin should have an option to use clone instead of init/fetch
Title: Message Title Eugene Gunov commented on JENKINS-23345 Re: Git Plugin should have an option to use clone instead of init/fetch The clone functionality is also required to use git extensions for large files such as git-fat. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance-plugin] (JENKINS-22885) Creation of Inheritance Project throws Exception
Title: Message Title Jonathan Romero edited a comment on JENKINS-22885 Re: Creation of Inheritance Project throws Exception TheSafeHTMLworkaroundworkedformeaswellonJenkins1.614 withprojectinheritanceplugin1.5.3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance-plugin] (JENKINS-22885) Creation of Inheritance Project throws Exception
Title: Message Title Jonathan Romero commented on JENKINS-22885 Re: Creation of Inheritance Project throws Exception The Safe HTML workaround worked for me as well on Jenkins 1.614 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstest-plugin] (JENKINS-28517) [MSTEST] XML coverage report file not found
Title: Message Title Ivo Bellin Salarin commented on JENKINS-28517 Re: [MSTEST] XML coverage report file not found Please read the release notes for the 0.14 version on the wiki page. https://wiki.jenkins-ci.org/display/JENKINS/MSTest+Plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-8423) Slave priority
Title: Message Title Mark Janes commented on JENKINS-8423 Re: Slave priority If you just have 2 categories of slaves (fast/slow), you can configure the slow slave's Availability setting to take the slave off-line when idle. Then jobs should go to the faster slaves unless jobs are sitting in the queue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
