[JIRA] [gradle] (JENKINS-17505) Gradle Plugin seems to change gradlew
Jens Schauder created JENKINS-17505 Gradle Plugin seems to change gradlew Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: gradle Created: 07/Apr/13 7:14 AM Description: When I configure a job to use the gradlewrapper gradlew gets changed (and possibly a bunch of directories created). This is a problem at least to me, since I'd like to use the job for releasing and the release plugin checks that the workingcopy is unmodified (which I can disable, but which is actually a useful and important feature to get reproducable builds) Here is a stackoverflow question, created by myself regarding the issue ( http://stackoverflow.com/q/15847518/66686 ): The plugin starts by checking if my working copy is clean, so that only properly versioned stuff gets released. This works just fine on my local machine. But when I try the same thing in a Jenkins job, the build fails complaining various stuff is changed in the workplace. I decided that a lot of stuff was just internally used by jenkins and added it to `gitignore`: caches/ native/ wrapper/ But it also considers `gradlew` as changed: FAILURE: Build failed with an exception. What went wrong: Execution failed for task ':checkCommitNeeded'. > You have uncommitted files: ~ M gradlew ~ Environment: Cloudbees Jenkins; Gradle Plugin Version 1.22 Project: Jenkins Priority: Major Reporter: Jens Schauder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gradle] (JENKINS-17505) Gradle Plugin seems to change gradlew
Jens Schauder commented on JENKINS-17505 Gradle Plugin seems to change gradlew I wonder if this is related to JENKINS-17505 ??? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10891) Page Title French Translation missing for "New Job" page
dogfood commented on JENKINS-10891 Page Title French Translation missing for "New Job" page Integrated in jenkins_main_trunk #2442 [FIXED JENKINS-10891] Page Title French Translation missing for "New (Revision a72d2a0e51eff66c5f27d3ec5f0096d4a773c214) Result = SUCCESS github : a72d2a0e51eff66c5f27d3ec5f0096d4a773c214 Files : core/src/main/resources/hudson/model/View/newJob_fr.properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-12410) Downstream jobs not associated with upstream parent job properly
domi assigned JENKINS-12410 to huybrechts Downstream jobs not associated with upstream parent job properly Change By: domi (07/Apr/13 11:06 AM) Assignee: domi huybrechts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17068) Subprojects aren't stop when stopping multijob project
Roni Licht resolved JENKINS-17068 as Fixed Subprojects aren't stop when stopping multijob project Change By: Roni Licht (07/Apr/13 12:02 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17068) Subprojects aren't stop when stopping multijob project
Roni Licht assigned JENKINS-17068 to Roni Licht Subprojects aren't stop when stopping multijob project Change By: Roni Licht (07/Apr/13 12:01 PM) Assignee: Roni Licht This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-16048) MultiJob Detailed Table is missing when non valid MultiJob phase exits
Roni Licht resolved JENKINS-16048 as Duplicate MultiJob Detailed Table is missing when non valid MultiJob phase exits JENKINS-17284 Change By: Roni Licht (07/Apr/13 12:08 PM) Status: Open Resolved Fix Version/s: current Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17351) Archiving artifacts does not work at all
Harald Albers assigned JENKINS-17351 to Harald Albers Archiving artifacts does not work at all Change By: Harald Albers (07/Apr/13 12:28 PM) Assignee: Harald Albers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17351) Archiving artifacts does not work at all
Harald Albers commented on JENKINS-17351 Archiving artifacts does not work at all There seems to be no support for absolute file paths on Windows file systems. Thus, a path like c:\... is treated as a relative path starting with c: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mstest] (JENKINS-17506) MsTest plugin doesn't parse and display the from the tag.
Mahesh Sarma created JENKINS-17506 MsTest plugin doesn't parse and display the from the tag. Issue Type: Improvement Assignee: acmarques Components: mstest Created: 07/Apr/13 12:38 PM Description: The trx could contain additional information on a test which could be logged by using the TextContext.WriteLine. This information is not displayed in the Specific Test page. eg: given RomanCalc object exists when args I and II are passed to the Add Method then III is returned Project: Jenkins Priority: Minor Reporter: Mahesh Sarma This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-17047) Make dependency to bundled ant plugin optional
Ulli Hafner updated JENKINS-17047 Make dependency to bundled ant plugin optional Change By: Ulli Hafner (07/Apr/13 1:00 PM) Component/s: warnings This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tasks-plugin] (JENKINS-17496) Remove Ant Plugin Dependency
Ulli Hafner resolved JENKINS-17496 as Duplicate Remove Ant Plugin Dependency Please watch JENKINS-17047. Change By: Ulli Hafner (07/Apr/13 1:02 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-15648) Multi Job plugins stops when sub job fails or aborted also when the "Mark phase as successful" is set as always continue
Roni Licht assigned JENKINS-15648 to Roni Licht Multi Job plugins stops when sub job fails or aborted also when the "Mark phase as successful" is set as always continue Change By: Roni Licht (07/Apr/13 1:33 PM) Assignee: itai Or Roni Licht This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-15648) Multi Job plugins stops when sub job fails or aborted also when the "Mark phase as successful" is set as always continue
Roni Licht resolved JENKINS-15648 as Fixed Multi Job plugins stops when sub job fails or aborted also when the "Mark phase as successful" is set as always continue Change By: Roni Licht (07/Apr/13 1:33 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17285) Submultijob runs as Job on Slaves
Roni Licht assigned JENKINS-17285 to Roni Licht Submultijob runs as Job on Slaves Change By: Roni Licht (07/Apr/13 1:52 PM) Assignee: Roni Licht This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17285) Submultijob runs as Job on Slaves
Roni Licht resolved JENKINS-17285 as Not A Defect Submultijob runs as Job on Slaves The multijob needs one executor and if you have only one executor it will be a problem to run the submultijob. I this case you need at lest two executors like if you run two jobs in parallel using the triggered paramterized plugin you need at least two executors. Change By: Roni Licht (07/Apr/13 1:55 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [text-finder] (JENKINS-17507) Text finder plugin has BuildStepMonitor.BUILD for getRequiredMonitorService
abayer created JENKINS-17507 Text finder plugin has BuildStepMonitor.BUILD for getRequiredMonitorService Issue Type: Bug Assignee: abayer Components: text-finder Created: 07/Apr/13 3:43 PM Description: The text finder plugin's getRequiredMonitorService() returns BuildStepMonitor.BUILD, which means that if you have it enabled on a build with concurrent builds enabled, if a later build finishes before an earlier build does, the later build gets stuck until the earlier build finishes. There doesn't seem to be a legit reason for this. Project: Jenkins Priority: Major Reporter: abayer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [bazaar] (JENKINS-4985) Set an env var with the Bzr rev number in the bzr plugin
Alexandre Garnier commented on JENKINS-4985 Set an env var with the Bzr rev number in the bzr plugin Pull request link is broken but feature was implemented by commits ec71594 and b95a6ca: BZR_REVID and BZR_REVISION env vars are available. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [bazaar] (JENKINS-17376) BZR Environment Variables
Alexandre Garnier updated JENKINS-17376 BZR Environment Variables Change By: Alexandre Garnier (07/Apr/13 4:49 PM) Description: When a Jenkins job executes, it sets some environment variables. It would be nice if BZR variables were available. I saw that BZR_REVNO BZR_REV--NO-+ID+ and BZR_REVISION are available, but it doesn't look like they currently work.I would also like to requestBZR_AUTHOR or BZR_COMMITERBZR_MESSAGEWould these be possible to implement? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17351) Archiving artifacts does not work at all
Harald Albers commented on JENKINS-17351 Archiving artifacts does not work at all The archive artifacts feature expects the build artifacts to reside in the workspace. When searching for matching artifacts, it recursively scans the workspace and its subdirectories. The actual work is delegated to the Ant DirectoryScanner, which will not break out of the parent directory (the workspace in our case). See Jenkins help message: See the @includes of Ant fileset for the exact format. The base directory is the workspace. and Ant documentation: In general, patterns are considered relative paths, relative to a task dependent base directory (the dir attribute in the case of ). Only files found below that base directory are considered. So while a pattern like ../foo.java is possible, it will not match anything when applied since the base directory's parent is never scanned for files. To solve your particular problem, I would recommend you redirect your tool's output to a file in the job's workspace and configure archiving for that 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/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Per J. Lund created JENKINS-17508 The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503. Issue Type: Bug Affects Versions: current Assignee: vjuranek Components: disk-usage Created: 07/Apr/13 5:17 PM Description: Activating the 'Discard Old Builds' checkbox on a job allows an Advanced option to specify 'Max # of builds to keep with artifacts'. This does not seem to clean up the artifacts for my builds anymore. I have tested 1.502, 1.503, 1.504 up to 1.510. It works fine in 1.502 but in none of the later versions. The artifacts I refer to are archived with the default archiving mechanism (not the archiving that can be configured as a post-step). Environment: Fedora 18 x86_64 Project: Jenkins Priority: Major Reporter: Per J. Lund This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17351) Archiving artifacts does not work at all
SCM/JIRA link daemon commented on JENKINS-17351 Archiving artifacts does not work at all Code changed in jenkins User: Olivier Lamy Path: core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts.html core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_de.html http://jenkins-ci.org/commit/jenkins/b99a794c6ed28507e4515e68e9c356dff3e6fd76 Log: Merge pull request #756 from albers/JENKINS-17351 JENKINS-17351 won't fix - clarified help text Thanks ! Compare: https://github.com/jenkinsci/jenkins/compare/77a0d6c5bafc...b99a794c6ed2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17351) Archiving artifacts does not work at all
SCM/JIRA link daemon commented on JENKINS-17351 Archiving artifacts does not work at all Code changed in jenkins User: Harald Albers Path: core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts.html core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_de.html http://jenkins-ci.org/commit/jenkins/433e0bfea0b632f341a5b84cf87342d566fe2012 Log: JENKINS-17351 clarified help text This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [pollscm] (JENKINS-17509) Global security loses Poll SCM permission for anonymous users after Jenkins restart
Adham Hassan created JENKINS-17509 Global security loses Poll SCM permission for anonymous users after Jenkins restart Issue Type: Bug Affects Versions: current Assignee: Vincent Latombe Components: pollscm Created: 07/Apr/13 11:50 PM Description: I've assigned security permissions so anonymous users can use the Poll SCM now feature for all jobs, but not Build Now. If I restart Jenkins though, it says there is Old Data that needs to be removed, and recommends me to use the Manage Old Data feature to get rid of it. Specifically: IllegalArgumentException: Failed to parse 'hudson.model.Item.Poll:anonymous' — no such permission If I go into Global Security Configuration, and enable Poll and click save, the issue goes away until next restart. Environment: Jenkins 1.510 Windows Server 2003 SP2 Project: Jenkins Labels: pollscm plugin Priority: Critical Reporter: Adham Hassan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17351) Archiving artifacts does not work at all
dogfood commented on JENKINS-17351 Archiving artifacts does not work at all Integrated in jenkins_main_trunk #2443 JENKINS-17351 clarified help text (Revision 433e0bfea0b632f341a5b84cf87342d566fe2012) Result = SUCCESS github : 433e0bfea0b632f341a5b84cf87342d566fe2012 Files : core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts_de.html core/src/main/resources/hudson/tasks/ArtifactArchiver/help-artifacts.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/groups/opt_out.
[JIRA] [security] (JENKINS-17510) Create an executor service wrapper class that sets the security context in each thread
Patrick McKeown
created JENKINS-17510
Create an executor service wrapper class that sets the security context in each thread
Issue Type:
Improvement
Assignee:
Patrick McKeown
Components:
security
Created:
08/Apr/13 2:43 AM
Description:
Initially suggested by jglick when I asked about this on the developer group https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/H8gAZcDOqgc -
The cleaner way to do this would probably be to create a delegating ExecutorService implementation whose submit and related methods capture the current SecurityContext
and then wrap the task in a block like the above. Then you could simply write:
SomeUtilityClass.wrapExecutorWithSecurity(service).submit(new Callable() {
public Void call() throws Exception {
Jenkins.getInstance().getItem(whatever); // should work
return null;
}
});
Such a wrapper would be a welcome addition to Jenkins core, I think. Use the jenkins.security package if you want to play with a pull request, or it could be added to
hudson.security.ACL which already hosts the impersonate methods.
Project:
Jenkins
Labels:
security
Priority:
Minor
Reporter:
Patrick McKeown
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Mark Waite resolved JENKINS-17198 as Fixed Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files No response from original submitter. Fixed in git-client-plugin 1.0.5 bu reverting to the git command line implementation until the JGit implementation is able to handle the Jenkins use cases. Change By: Mark Waite (08/Apr/13 3:37 AM) Status: Reopened 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/groups/opt_out.
[JIRA] [git] (JENKINS-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Mark Waite edited a comment on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files No response from original submitter. Fixed in git-client-plugin 1.0.5 by reverting to the git command line implementation until the JGit implementation is able to handle the Jenkins use cases. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
sharon xia commented on JENKINS-17349 CPU on master node keeps increasing and never come down After the JVM arguments changed to -Xmx2048m -XX:MaxPermSize=512m, there is still a CPU increase after several days run. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-17510) Create an executor service wrapper class that sets the security context in each thread
Patrick McKeown
updated JENKINS-17510
Create an executor service wrapper class that sets the security context in each thread
Change By:
Patrick McKeown
(08/Apr/13 5:14 AM)
Description:
Initially suggested by jglick when I asked
about this
a question
on the developer group https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/H8gAZcDOqgc -The cleaner way to do this would probably be to create a delegating ExecutorService implementation whose submit and related methods capture the current SecurityContext and then wrap the task in a block like the above. Then you could simply write: SomeUtilityClass.wrapExecutorWithSecurity(service).submit(new Callable() { public Void call() throws Exception { Jenkins.getInstance().getItem(whatever); // should work return null; } }); Such a wrapper would be a welcome addition to Jenkins core, I think. Use the jenkins.security package if you want to play with a pull request, or it could be added to hudson.security.ACL which already hosts the impersonate methods.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
sharon xia updated JENKINS-17349 CPU on master node keeps increasing and never come down JavaMelody pdf after memory inceased. Change By: sharon xia (08/Apr/13 5:14 AM) Attachment: JavaMelody__CNRDGPS_4_8_13.pdf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-17510) Create an executor service wrapper class that sets the security context in each thread
Patrick McKeown
updated JENKINS-17510
Create an executor service wrapper class that sets the security context in each thread
Change By:
Patrick McKeown
(08/Apr/13 5:16 AM)
Description:
Initially suggested by jglick when I asked a question on the developer group https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/H8gAZcDOqgc -
The cleaner way to do this would probably be to create
Creates
a delegating ExecutorService implementation whose submit and related methods capture the current SecurityContext and then wrap the task in a block
like
that resets
the
above
context afterwards
.
Then you
Using this one
could simply write: SomeUtilityClass.wrapExecutorWithSecurity(service).submit(new Callable() { public Void call() throws Exception { Jenkins.getInstance().getItem(whatever); // should work return null; } });
Such a wrapper would be a welcome addition to Jenkins core, I think. Use the jenkins.security package if you want to play with a pull request, or it could be added to hudson.security.ACL which already hosts the impersonate methods.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
sharon xia updated JENKINS-17349 CPU on master node keeps increasing and never come down In the middle of the picture, the CPU decreased dramatically after a system restart to let new parameters take effect. However, after about one week, the cpu increased to ~= 6%. Change By: sharon xia (08/Apr/13 5:18 AM) Attachment: CPU incease pic.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/groups/opt_out.
[JIRA] [core] (JENKINS-17351) Archiving artifacts does not work at all
Harald Albers resolved JENKINS-17351 as Won't Fix Archiving artifacts does not work at all This is not a bug, see comment. The help message has been updated to state that artifacts outside the workspace cannot be archived. Change By: Harald Albers (08/Apr/13 6:53 AM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
