[JIRA] [git] (JENKINS-6856) Git builds with detached head no matter what
Joshua Moody commented on JENKINS-6856 Git builds with detached head no matter what I second what Michael Floering says. I don't believe this has been fixed. The detached head state is causing a bunch of problems for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22693) Resource leak in hudson.model.FileParameterValue
evernat
created JENKINS-22693
Resource leak in hudson.model.FileParameterValue
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
20/Apr/14 10:05 AM
Description:
A FileInputStream is not closed in hudson.model.FileParameterValue for "return IOUtils.toByteArray(new FileInputStream(file))".
This is a resource leak.
The FileInputStream should be closed, using finally. For example:
final InputStream input = new FileInputStream(file);
try {
return IOUtils.toByteArray(input);
} finally {
input.close();
}
Project:
Jenkins
Priority:
Major
Reporter:
evernat
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-22693) Resource leak in hudson.model.FileParameterValue
evernat
updated JENKINS-22693
Resource leak in hudson.model.FileParameterValue
Change By:
evernat
(20/Apr/14 10:06 AM)
Description:
A FileInputStream is not closed in [hudson.model.FileParameterValue|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/FileParameterValue.java#L260] for "return IOUtils.toByteArray(new FileInputStream(file))".This is a resource leak.The FileInputStream should be closed, using finally. For example:
{code}
final InputStream input = new FileInputStream(file);try {return IOUtils.toByteArray(input);} finally {input.close();}
{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22682) git "HTTP request failed" in Jenkins
Everard Brown commented on JENKINS-22682 git "HTTP request failed" in Jenkins Lots of suggestions... thanks. Here's what did not work: o The skip certificate check plugin o Upgrade my native git package to 1.7.10+ Here's what did work: o Copied my cacert.pem to the jenkins server (into $HOME/.git-certs/) o Added the following lines to $HOME/.gitconfig: [http] sslVerify = true sslCAPath = /home/jenkins/.git-certs I have upgraded my native git package to git-1.7.12.3, and still can't clone (due to java.lang.IllegalArgumentException: Null value not allowed as an environment variable: GIT_COMMIT) but methinks that is a different bug/feature. This issue can be 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] [git] (JENKINS-22682) git "HTTP request failed" in Jenkins
Everard Brown edited a comment on JENKINS-22682 git "HTTP request failed" in Jenkins Lots of suggestions... thanks. Here's what did not work: o The skip certificate check plugin o Upgrade my native git package to 1.7.10+ (but that was how I was able to figure out what the real problem was - the error message informs you that you need the CA cert) Here's what did work: o Copied my cacert.pem to the jenkins server (into $HOME/.git-certs/) o Added the following lines to $HOME/.gitconfig: [http] sslVerify = true sslCAPath = /home/jenkins/.git-certs I have upgraded my native git package to git-1.7.12.3, and still can't clone (due to java.lang.IllegalArgumentException: Null value not allowed as an environment variable: GIT_COMMIT) but methinks that is a different bug/feature. This issue can be 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] [git] (JENKINS-22682) git "HTTP request failed" in Jenkins
Mark Waite closed JENKINS-22682 as Not A Defect git "HTTP request failed" in Jenkins Change By: Mark Waite (20/Apr/14 11:31 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] [git] (JENKINS-22682) git "HTTP request failed" in Jenkins
Mark Waite resolved JENKINS-22682 as Not A Defect git "HTTP request failed" in Jenkins Change By: Mark Waite (20/Apr/14 11:31 AM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17510) Create an executor service wrapper class that sets the security context in each thread
Daniel Beck commented on JENKINS-17510 Create an executor service wrapper class that sets the security context in each thread Do the commits resolve 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-13546) buildWithParameters: return a JSON string when client request it through content-type header
SCM/JIRA link daemon commented on JENKINS-13546 buildWithParameters: return a JSON string when client request it through content-type header Code changed in jenkins User: Daniel Beck Path: changelog.html http://jenkins-ci.org/commit/jenkins/14b6e10243522cd7d3db58d55a2363ef51fe3440 Log: Noted #648, #737, #733, JENKINS-13546 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-19246) Configure Project loading overloay not hiding error "invalid gitTool selection Default"
Joshua Moody commented on JENKINS-19246 Configure Project loading overloay not hiding error "invalid gitTool selection Default" I still see this problem in 1.559. MacOS 10.9.2 git version 1.9.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-6856) Git builds with detached head no matter what
Joshua Moody edited a comment on JENKINS-6856 Git builds with detached head no matter what I second what Michael Floering says. I don't believe this has been fixed. The detached head state is causing a bunch of problems for us. UPDATE: After sleeping on the problem I, made a changes which I think resolved the detached head problem: In the Git plugin Advanced Options, I added: "Checkout to a specific local branch" and provided a branch name. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22694) Java authentication dialog pop-up appears from JNLP slave if bitbucket username/password attempted
Mark Waite created JENKINS-22694 Java authentication dialog pop-up appears from JNLP slave if bitbucket username/password attempted Issue Type: Bug Assignee: Nicolas De Loof Components: git-client Created: 20/Apr/14 3:07 PM Description: I created a private bitbucket git repository and tried to clone it to each of my Jenkins slave agents using a username/password credential for my bitbucket account. When the job ran, the slave machines running JNLP popped up a Java authentication dialog asking for the user name and password for bitbucket.org. JNLP agents should not prompt for username and password, and the git-client-plugin should use my valid username and password as entered instead of prompting for authentication. Steps I took to show the problem: Define a domain specific credential for bitbucket.org Define a credential in that domain for my username and password Define a job which runs on all my slave agents (I used the elastic-axis plugin to make that easier) Use git as the source repository for that job Use my bitbucket repository and credentials for that job (I used https://bitbucket.org/markewaite/git-client-plugin.git) Run the job, and watch the consoles of those slave computers using JNLP Environment: Jenknis 1.544.1 RC, git-client-plugin 1.8.0, git-plugin 2.2.1 Project: Jenkins Priority: Major Reporter: Mark Waite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22685) Jenkins cannot restart Windows service
Sal Merino commented on JENKINS-22685 Jenkins cannot restart Windows service Here's what's happening: 1. Restarting Jenkins (after plugin-update or by calling /restart) spawns a new process to execute "jenkins.exe restart" (i.e., restarting via the Windows Service wrapper). The Parent Process ID of this new process equals the Process ID that is running jenkins.war. 2. Jenkins.exe's "restart" command is a three-part process: A) stop the jenkins.war PID and all children PID; B) Wait for jenkins.war PID to stop; C) launch jenkins.war in a new process. 3. Since this execution of "jenkins.exe restart" is itself a child process of jenkins.war, the Jenkins service is killing it as part of 2A. This results in: 3A. Killing "jenkins.exe restart" (via SIGINT) causes that process to return w/ errorlevel=1. The WindowsServiceLifecycle restart method is checking the errorlevel from running "jenkins.exe restart" and seeing that it is not 0, and therefore throws an IOException. This is the error message seen in jenkins.err.log. 3B. Since the process running "jenkins.exe restart" gets killed as part of Step 2A, it does not get a change to complete the restart process, so Jenkins remains stopped. Solution: From looking at the WinSW project, it looks like there was some anticipation of this issue, in regards to the "secret" "restart!" command vs. the standard "restart". However, simply changing WindowsServiceLifecycle so that it calls "jenkins.exe restart!" does not fix the issue (actually, I just switched the "restart" and "restart!" commands in WinSW as that was easier to drop in and test), as there are additional exceptions thrown that prevent the service from stopping. Something that should work would be if WinSW.Main.StopProcessAndChildren(), when it recurses over the jenkins.war PID and children, would skip killing a child PID if that Process's ExecutablePath is equal to the WinSW executable path. Testing this idea and will submit a pull request if it works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22685) Jenkins cannot restart Windows service
Sal Merino edited a comment on JENKINS-22685 Jenkins cannot restart Windows service Here's what's happening: 1. Restarting Jenkins (after plugin-update or by calling /restart) spawns a new process to execute "jenkins.exe restart" (i.e., restarting via the Windows Service wrapper). The Parent Process ID of this new process equals the Process ID that is running jenkins.war. 2. Jenkins.exe's "restart" command is a three-part process: A) stop the jenkins.war PID and all children PID; B) Wait for jenkins.war PID to stop; C) launch jenkins.war in a new process. 3. Since this execution of "jenkins.exe restart" is itself a child process of jenkins.war, the Jenkins service is killing it as part of 2A. This results in: 3A. Killing "jenkins.exe restart" (via SIGINT) causes that process to return w/ errorlevel=1. The WindowsServiceLifecycle restart method is checking the errorlevel from running "jenkins.exe restart" and seeing that it is not 0, and therefore throws an IOException. This is the error message seen in jenkins.err.log. 3B. Since the process running "jenkins.exe restart" gets killed as part of Step 2A, it does not get a change to complete the restart process, so Jenkins remains stopped. Solution: From looking at the WinSW project, it looks like there was some anticipation of this issue, in regards to the "secret" "restart!" command vs. the standard "restart". However, simply changing WindowsServiceLifecycle so that it calls "jenkins.exe restart!" does not fix the issue (actually, I just switched the "restart" and "restart!" commands in WinSW as that was easier to drop in and test), as there are additional exceptions thrown that prevent the service from stopping. Something that should work would be if WinSW.Main.StopProcessAndChildren(), when it recurses over the jenkins.war PID and children, would skip killing a child PID if that Process's ExecutablePath is equal to the WinSW executable path. Testing this idea and will submit a pull request if it works. Note: There's also a bug in the output from WinSW.Main.StopProcessAndChildren: variable "pid" is the process being killed during this execution of the method (either the main jenkins.war PID or the PID of one of its children), but the "Send SIGINT/SIGINT to" log output uses process.Id, which is always the jenkins.war PID. So the log output looks like multiple SIGINTs are being sent to the same PID, which is not the case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode] (JENKINS-20916) Code Sign error: No matching provisioning profile found
Amr El-Dessouky commented on JENKINS-20916 Code Sign error: No matching provisioning profile found Hello, I was able to solve this issue, which was due to two main reasons, Xcode when invoked from Jenkins looks to ite resources from the System & not the user, so to fix at least get sure that you did the following:- 1-Ensure the project is building successfully from Xcode to real target. -In KeyChain 2-Copy all the development cretificates & credentials form your user folder to the system folder 3-Copy all the Provisioning profiles existing in Users//Library/MobileDevice/Provisioning Profiles to System/Library/MobileDevice/Provisioning Profiles Create the missing folders if they don’t exist below 'Library' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22685) Jenkins cannot restart Windows service
JCK commented on JENKINS-22685 Jenkins cannot restart Windows service WinSW pull request submitted: https://github.com/kohsuke/winsw/pull/37 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer] (JENKINS-22695) Mailer plugin NullPointerException
John Doe created JENKINS-22695 Mailer plugin NullPointerException Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: mailer Created: 20/Apr/14 8:18 PM Description: We're seeing the attached NullPointerException from the mailer plugin. This is because this call can return null as documented here. If it's important, our use case is we're trying to send an email after the failure of a Build Flow job. As of version 0.11, the plugin no longer creates or maintains a workspace. Thank you! Publisher hudson.tasks.Mailer aborted due to exception java.lang.NullPointerException at hudson.tasks.MailSender.createFailureMail(MailSender.java:278) at hudson.tasks.MailSender.getMail(MailSender.java:153) at hudson.tasks.MailSender.execute(MailSender.java:101) at hudson.tasks.Mailer.perform(Mailer.java:137) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:714) at hudson.model.Build$BuildExecution.post2(Build.java:182) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:663) at hudson.model.Run.execute(Run.java:1725) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Project: Jenkins Priority: Major Reporter: John Doe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22550) GHPRB NoSuchMethodError
Joshua Moody commented on JENKINS-22550 GHPRB NoSuchMethodError I am also seeing this on: Jenkins: 1.559 GHPRB:1.11.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
Maciej Pasternacki edited a comment on JENKINS-22641 Jenkins no longer kills running processes after job fails I can confirm: this is affecting me too, with succeeding and failing jobs. One of the job has been relying on the process reaping mechanism to clean up (started a redis-server daemon before the build and relied on Jenkins killing it afterwards). That was working fine on Jenkins 1.554, and stopped working with upgrade to 1.558; this issue still occurs on 1.559. Ubuntu 12.04, x86_64, Oracle JDK 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] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
Maciej Pasternacki commented on JENKINS-22641 Jenkins no longer kills running processes after job fails I can confirm: this is affecting me too, with succeeding and failing jobs. One of the job has been relying on the process reaping mechanism to clean up (started a redis-server daemon before the build and relied on Jenkins killing it afterwards). That was working fine on Jenkins 1.554, and stopped working with upgrade to 1.558; this issue still occurs on 1.559. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-pipeline] (JENKINS-21527) getting incorrect parameter values from upstream job when a manual downstream job is shared by multiple upstream jobs.
shane kim resolved JENKINS-21527 as Fixed getting incorrect parameter values from upstream job when a manual downstream job is shared by multiple upstream jobs. Merged into jenkins' master. https://github.com/jenkinsci/build-pipeline-plugin/pull/24 https://github.com/jenkinsci/build-pipeline-plugin/commit/376b460e12576e5285394da9fc8a9d275cfcf3a9 Change By: shane kim (20/Apr/14 11:06 PM) Status: Open Resolved Assignee: shane kim Fix Version/s: current 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] [ws-cleanup] (JENKINS-22696) Delete workspace with sudo doesn't work
Harry Flink created JENKINS-22696 Delete workspace with sudo doesn't work Issue Type: Bug Affects Versions: current Assignee: vjuranek Components: ws-cleanup Created: 21/Apr/14 12:58 AM Description: Some projects create root owned files in the project's work directory. The project work space cannot be cleaned up using ws-cleanup plugin before building the project again, because root-owned files cannot be deleted. Here are the steps to test: 1. Select "Delete workspace before build starts 2. Clicking "Advanced" button 3. Enter command "sudo rm -rf %s" into "External Deletion Command". 4. Add build step to do "ls -alF" so that you can see if the previous build's files exists or did the clean-up work. 5. Start rebuilding the project. I have tried this on a slave host and it doesn't work there, at least. The jenkins-user is in sudoers file (in the slave host) and sudo is configured not to require password. An interesting detail is that the "/var/log/auth.log" shows a log row for a correct command-line, but that still doesn't work: Apr 21 03:30:06 imx7 sudo: jenkins : TTY=unknown ; PWD=/var/lib/jenkins ; USER=root ; COMMAND=/bin/rm -rf "/var/lib/jenkins/workspace/my-test-project-with-root-owned-files" Environment: Ubuntu 12.04 LTS Jenkins WAR v1.559 ws-clean plug-in v0.20 Project: Jenkins Priority: Major Reporter: Harry Flink This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-22696) Delete workspace with sudo doesn't work
Harry Flink commented on JENKINS-22696 Delete workspace with sudo doesn't work Also, the console output says... Deleting project workspace... Using command: sudo rm -rf "/var/lib/jenkins/workspace/my-test-project-with-root-owned-files" done ...but nothing gets deleted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-22696) Delete workspace with sudo doesn't work
Harry Flink commented on JENKINS-22696 Delete workspace with sudo doesn't work Also, I haven't found any kind of workaround yet to this issue in whole Jenkins environment. I can use "sudo" in shell build commands, so sudo works OK, but I cannot delete project workspace content in the build commands because then my whole branched Bazaar repository would get deleted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-22696) Delete workspace with sudo doesn't work
Harry Flink commented on JENKINS-22696 Delete workspace with sudo doesn't work Wait... I think I finally found a workaround, after 5-6h of trying to solve this, for Bazaar projects at least. Uncheck "Delete workspace before build starts" because it fails the build if it cannot delete the work directory. Add "Execute Shell" build step as a very first step with content like this: Unable to find source-code formatter for language: bash. Available languages are: _javascript_, sql, xhtml, actionscript, none, html, xml, javasudo chown "$USER" . bzr revert --no-backup bzr clean-tree --ignored --unknown --force --detritus Start rebuilding the project. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-22696) Delete workspace with sudo doesn't work
Harry Flink edited a comment on JENKINS-22696 Delete workspace with sudo doesn't work Wait... I think I finally found a workaround, after 5-6h of trying to solve this, for Bazaar projects at least. Uncheck "Delete workspace before build starts" because it fails the build if it cannot delete the work directory. Add "Execute Shell" build step as a very first step with content like this: sudo chown "$USER" . bzr revert --no-backup bzr clean-tree --ignored --unknown --force --detritus Start rebuilding the project. EDIT: No bash formatter installed in Jira, fixed the code-block layout. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameters] (JENKINS-22512) Saving config fails after deleting a build parameter
Michael Fowler closed JENKINS-22512 as Duplicate Saving config fails after deleting a build parameter Change By: Michael Fowler (21/Apr/14 2:12 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-20550) download artifacts is very slow
Dennys Hsieh commented on JENKINS-20550 download artifacts is very slow I changed from 217 to 214 and the download speed is changed from 100KB/sec to 210KB/sec. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
