[JIRA] [export-params] (JENKINS-24313) Export file to the master
Jonas Bang Christensen
commented on JENKINS-24313
Export file to the master
Sorry, been busy.
Just tested the alternative solution, it works.
Export:
Export parameters to file
Archive the artifacts
Import:
Prepare an environment for the run
Properties File Path: ${JENKINS_HOME}/jobs/JOB_NAME/lastStable/archive/FILE_NAME.properties
Load script and properties files from the master
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and 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] [export-params] (JENKINS-24313) Export file to the master
Jonas Bang Christensen resolved JENKINS-24313 as Wont Fix Export file to the master Alternative solution identified. See comments for details. Change By: Jonas Bang Christensen (28/Aug/14 7:14 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [export-params] (JENKINS-24313) Export file to the master
Jonas Bang Christensen closed JENKINS-24313 as Wont Fix Export file to the master Change By: Jonas Bang Christensen (28/Aug/14 7:15 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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
rin_ne commented on JENKINS-24445 Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification Sorry, I missed attachment and fully understand. BTW, it seems that this plugin has some useful logs around the related logic. So I think you had better provide logs if you have. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [maven] (JENKINS-23826) Allow automatic install of Maven 3.2.2
Gregory SSI-YAN-KAI commented on JENKINS-23826 Allow automatic install of Maven 3.2.2 Pull request submitted: https://github.com/jenkinsci/backend-crawler/pull/26 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [checkstyle] (JENKINS-19932) Publish FindBugs/Checkstyle from slave failed
Andreas Bergermeier edited a comment on JENKINS-19932 Publish FindBugs/Checkstyle from slave failed Set property Julia mentioned is just a hack to make Checkstyle working for now. Setting the property prevents the SAXParserFactory from searching the classpath for SAXParserFactory-services. Somehow the slaves find the org.apache.xerces.jaxp.SAXParserFactoryImpl as SAXParserFactory-service but are unable to load the service (class). Unfortunately the cause of javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found is not shown in the log. Using the Script-Console for a slave we figured out that the class org.apache.xerces.jaxp.SAXParserFactoryImpl cannot be loaded because of: Caused by: java.lang.ClassNotFoundException: Classloading from system classloader disabled This lead to the conclusion that there is either too much or too little transferred to the slave. Maybe too much because the SAXParserFactory-Service is found. Maybe too little because the class cannot be loaded. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [checkstyle] (JENKINS-19932) Publish FindBugs/Checkstyle from slave failed
Andreas Bergermeier commented on JENKINS-19932 Publish FindBugs/Checkstyle from slave failed Set property Julia mentined is just a hack to make Checkstyle working for now. Setting the property prevents the SAXParserFactory from searching the classpath for SAXParserFactory-services. Somehow the slaves find the org.apache.xerces.jaxp.SAXParserFactoryImpl as SAXParserFactory-service but are unable to load the service (class). Unfortunately the cause of javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found is not shown in the log. Using the Script-Console for a slave we figured out that the class org.apache.xerces.jaxp.SAXParserFactoryImpl cannot be loaded because of: Caused by: java.lang.ClassNotFoundException: Classloading from system classloader disabled This lead to the conclusion that there is either too much or too little transferred to the slave. Maybe too much because the SAXParserFactory-Service is found. Maybe too little because the class cannot be loaded. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-24447) latest ghprb plugin still broken for github enterprise users although JENKINS-24145 marked as resolved
Michael Wild updated JENKINS-24447 latest ghprb plugin still broken for github enterprise users although JENKINS-24145 marked as resolved Change By: Michael Wild (28/Aug/14 8:10 AM) Summary: latestghprbpluginstillbrokenforgithubenterpriseusers athough although JENKINS-24145markedasresolved This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-24447) latest ghprb plugin still broken for github enterprise users although JENKINS-24145 marked as resolved
Michael Wild commented on JENKINS-24447 latest ghprb plugin still broken for github enterprise users although JENKINS-24145 marked as resolved Thank you very much. It works with v1.15-0. >From my point of view this issue may be marked as resolved. Just for a better understanding: Is this workaround responsible for the list of changes in jenkins saying "no changes"? (For the time being this is not a big problem, since the causing pull request is linked.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
rin_ne commented on JENKINS-24445 Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification I reproduced this on the latest plugin code but there is a bit difference with what you mentioned. This will let Test_2 finish successfully (as Test_2 always succeeds). The bug that happens now, is that the trigger plugin uploads a "Verified +1" message, DESPITE "Test_1 #2" not yet being finished. When LOCKFILE_Test_2-2 was removed, any message was not uploaded. Next, LOCKFILE_Test_1-1 was removed. Then message "Verified -1" was uploaded from "Test_1 #1". Also message "Verified +1" was uploaded when LOCKFILE_Test_2-1 was removed. Finally, LOCKFILE_Test_1_2 was removed. Then message "Verified -1" was uploaded with verdict value both "Test_1 #2" and "Test_2 #2". It means that uploading message for "Test_2 #2" was pended until "Test_1 #2" is completed. It means that: Running builds for event from Gerrit were deviated from verdict logic by manual triggered ones. But these were still enabled as individual triggered build. So I think that the issue you should address is #2. right? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [gitlab] (JENKINS-24474) gitlab-plugin
Guy Attrill created JENKINS-24474 gitlab-plugin Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: gitlab Created: 28/Aug/14 8:30 AM Description: I have set up a simple project in gitlab with one branch I have set up a merge build job as described I press test settings on gitlab ci page of gitlab settings for testmerge project This error comess through on jenkins Test-gitmerge triggered. Aug 28, 2014 9:09:49 AM WARNING com.dabsquared.gitlabjenkins.GitLabPushTrigger$2 createActions Could not fetch source project's data from Gitlab. (java.net.MalformedURLException: no protocol: /api/v3/projects/137: no protocol: /api/v3/projects/137) Environment: jenkins 1.565.1 gitlab plugin 1.1.1 GitLab 7.2.0 Project: Jenkins Labels: plugin jenkins exception gitlab Priority: Minor Reporter: Guy Attrill This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
rin_ne commented on JENKINS-24445 Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification Sorry, missed one condition. So I will update. In case jobs has no builds(means started as #1), NPE was happened. INFO: Test_1 #1 main build action completed: FAILURE Aug 28, 2014 6:13:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener onCompleted INFO: Obtained failure message: null Aug 28, 2014 6:13:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.model.BuildMemory setEntryFailureMessage INFO: Recording unsuccessful message for PatchsetCreated: Change: 7 PatchSet: 28: null Aug 28, 2014 6:13:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener allBuildsCompleted INFO: All Builds are completed for cause: GerritCause: PatchsetCreated: Change: 7 PatchSet: 28 silent: false Aug 28, 2014 6:13:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.GerritNotifier buildCompleted SEVERE: Could not complete BuildCompleted notification! java.lang.NullPointerException at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ParameterExpander.createBuildsStats(ParameterExpander.java:554) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ParameterExpander.getBuildCompletedCommand(ParameterExpander.java:485) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.GerritNotifier.buildCompleted(GerritNotifier.java:113) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.job.ssh.BuildCompletedCommandJob.run(BuildCompletedCommandJob.java:64) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
rin_ne edited a comment on JENKINS-24445 Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification I reproduced this on the latest plugin code but there is a bit difference with what you mentioned. UPDATE: The below results are in condition: jobs has one completed build as "#1". So "#2" is triggered build by event, "#3" is triggered build by manual trigger. This will let Test_2 finish successfully (as Test_2 always succeeds). The bug that happens now, is that the trigger plugin uploads a "Verified +1" message, DESPITE "Test_1 #2" not yet being finished. When LOCKFILE_Test_2-3 was removed, any message was not uploaded. Next, LOCKFILE_Test_1-2 was removed. Then message "Verified -1" was uploaded from "Test_1 #2". Also message "Verified +1" was uploaded when LOCKFILE_Test_2-2 was removed. Finally, LOCKFILE_Test_1-3 was removed. Then message "Verified -1" was uploaded with verdict value both "Test_1 #3" and "Test_2 #3". It means that uploading message for "Test_2 #3" was pended until "Test_1 #3" is completed. It means that: Running builds for event from Gerrit were deviated from verdict logic by manual triggered ones. But these were still enabled as individual triggered build. So I think that the issue you should address is #2. right? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
rin_ne edited a comment on JENKINS-24445 Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification I reproduced this on the latest plugin code but there is a bit difference with what you mentioned. *UPDATE: The below results are in condition: jobs has one completed build as "#1". So "#2" is triggered build by event, "#3" is triggered build by manual trigger. This will let Test_2 finish successfully (as Test_2 always succeeds). The bug that happens now, is that the trigger plugin uploads a "Verified +1" message, DESPITE "Test_1 #2" not yet being finished. When LOCKFILE_Test_2-3 was removed, any message was not uploaded. Next, LOCKFILE_Test_1-2 was removed. Then message "Verified -1" was uploaded from "Test_1 #2". Also message "Verified +1" was uploaded when LOCKFILE_Test_2-2 was removed. Finally, LOCKFILE_Test_1-3 was removed. Then message "Verified -1" was uploaded with verdict value both "Test_1 #3" and "Test_2 #3". It means that uploading message for "Test_2 #3" was pended until "Test_1 #3" is completed. It means that: Running builds for event from Gerrit were deviated from verdict logic by manual triggered ones. But these were still enabled as individual triggered build. So I think that the issue you should address is #2. right? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-24467) Possible regression of JENKINS-14321
Rob Langley commented on JENKINS-24467 Possible regression of JENKINS-14321 So I've done a little more investigation, it would appear the git ls-remote command is being run on the Debian master rather than the windows slave. To ascertain this I renamed every git.exe on the windows machine which made no difference, after reverting them I did the same to /usr/bin/git which resulted in the following error: Started on 28-Aug-2014 10:17:24 Polling SCM changes on XXX Using strategy: Default [poll] Last Built Revision: Revision 131f327074161ac81f7dc523363ec08841739669 (origin/master) git ls-remote -h git@XXX:XXX/XXX.git master # timeout=10 FATAL: hudson.plugins.git.GitException: Error performing command: git ls-remote -h git@XXX:XXX/XXX.git master hudson.util.IOException2: hudson.plugins.git.GitException: Error performing command: git ls-remote -h g...@github.bromium.net:rob-langley/glowing-octo-dangerzone.git master at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:462) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:357) at hudson.scm.SCM.poll(SCM.java:374) at org.jenkinsci.plugins.multiplescms.MultiSCM.compareRemoteRevisionWith(MultiSCM.java:92) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:357) at hudson.scm.SCM.poll(SCM.java:374) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1449) at hudson.model.AbstractProject._poll(AbstractProject.java:1420) at hudson.model.AbstractProject.poll(AbstractProject.java:1331) at com.cloudbees.jenkins.GitHubPushTrigger$1.runPolling(GitHubPushTrigger.java:73) at com.cloudbees.jenkins.GitHubPushTrigger$1.run(GitHubPushTrigger.java:98) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: hudson.plugins.git.GitException: Error performing command: git ls-remote -h git@XXX:XXX/XXX.git master at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1414) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1195) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1119) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1110) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:2004) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:495) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:460) ... 18 more Caused by: java.io.IOException: Cannot run program "git": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:780) at hudson.Launcher$ProcStarter.start(Launcher.java:360) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1403) ... 24 more Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.init(UNIXProcess.java:135) at java.lang.ProcessImpl.start(ProcessImpl.java:130) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022) ... 29 more Done. Took 16 ms No changes Following up from this I swapped /usr/bin/git for a shell script that echo'ed the path and got: C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell 1.0\;C:\Program Files (x86)\Git in;C:\Program Files (x86)\Java\jre7 in Which is completely wrong for a Debian box, I think the polling is picking up the path from the last build job then either incorrectly trying to use it on the Debian box or incorrectly running the polling on the Debian box. I imagine it's probably the former.
[JIRA] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
rin_ne edited a comment on JENKINS-24445 Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification Sorry, missed one condition. So I will update. In case jobs has no builds(means started as #1), NPE was happened. INFO: Test_1 #1 main build action completed: FAILURE Aug 28, 2014 6:13:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener onCompleted INFO: Obtained failure message: null Aug 28, 2014 6:13:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.model.BuildMemory setEntryFailureMessage INFO: Recording unsuccessful message for PatchsetCreated: Change: 7 PatchSet: 28: null Aug 28, 2014 6:13:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener allBuildsCompleted INFO: All Builds are completed for cause: GerritCause: PatchsetCreated: Change: 7 PatchSet: 28 silent: false Aug 28, 2014 6:13:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.GerritNotifier buildCompleted SEVERE: Could not complete BuildCompleted notification! java.lang.NullPointerException at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ParameterExpander.createBuildsStats(ParameterExpander.java:554) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ParameterExpander.getBuildCompletedCommand(ParameterExpander.java:485) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.GerritNotifier.buildCompleted(GerritNotifier.java:113) at com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.job.ssh.BuildCompletedCommandJob.run(BuildCompletedCommandJob.java:64) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) But I think the issue in previous comment is potential one for this NPE. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
Martin Schröder commented on JENKINS-24445 Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification Hi Rin. The main point of this issue is, that the Gerrit Trigger fails evaluating patch sets correctly. You can confuse it with the manual trigger so much, that it forgets that it needs to wait 2 tests to complete, before it can approve or deny a change. Taking a look at the log in my original submission, the issue is as follows. I uploaded the patch-set, and let the two tests continue running. The message uploaded by the plugin is correct so far: --- Jenkins Patch Set 1: -Verified Build Started Test_2/1/ (1/2) --- Jenkins Patch Set 1: Build Started Test_1/1/ (2/2) --- This is all normal behaviour. It notified the user of the start, and waits for the jobs to finish, before deciding on a verdict. Now while those two jobs were still running, I started a "manual retrigger" on the same patch set, causing Gerrit Trigger to spawn two new builds: --- Jenkins Patch Set 1: Build Started Test_2/2/ (2/2) --- Jenkins Patch Set 1: Build Started Test_1/2/ (2/2) --- It did not need to do a "-Verified", as it knows that it is currently building the same patchset. If you have enabled the "Only build on newest patchset" feature, it even helpfully aborts the two previous jobs for you. But there's something wrong here: It actually lost count of the number of tests it started. Instead of writing (1/2) (2/2) or maybe even (3/4) (4/4) it instead writes (2/2) twice. So it lost count. This might not be so bad, but now, the bug strikes, when we deliberately let only "Test_2" finish, which always succeeds. Remember, Gerrit Trigger should wait for BOTH tests to finish. --- Jenkins Patch Set 1: Verified+1 Build Successful Test_2/2/ : SUCCESS --- As you can see, it did not wait. It immediately uploaded a Verified+1. If you have any form of auto-commit in Gerrit, this is immediately deadly. It also allows users to (accidentally) subvert the verification process. I will try to replicate this again later on my machine, and look if I also get an NPE. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-24407) missing weather icons (randomly?)
Tom FENNELLY edited a comment on JENKINS-24407 missing weather icons (randomly?) Hi guys. Can we confirm is it only when Jenkins is running as a Windows Service, or does that matter? I did a quick test on this locally but failed to reproduce (using latest source on OSX). Would it be possible for someone that has this issue to: 1. Create a public test project in their github that uses Cobertura (or other) and can be used in #2 2. Provide a sample job (that uses the test project from #1) that I can install locally that reproduces the 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-24407) missing weather icons (randomly?)
Tom FENNELLY commented on JENKINS-24407 missing weather icons (randomly?) Hi guys. Can we confirm is it only when Jenkins is running as a Windows Service, or does that matter? I did a quick test on this locally but failed to reproduce (using latest source on OSX). Would it be possible for someone that has this issue to: 1. Create a public test project in their github that uses Cobertura (or other) and can be used in #2 2. Provide a sample job that I can install locally that reproduces the 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] [ownership] (JENKINS-24475) Managing ownership not possible
Stephan Krull created JENKINS-24475 Managing ownership not possible Issue Type: Bug Assignee: Oleg Nenashev Components: ownership Created: 28/Aug/14 10:34 AM Description: After upgraded to latest LTS and ownership plugin version I am no longer able to configure ownership of jobs and nodes. Trying to visit "JENKINS_URL/computer/NODENAME/ownership/manage-owners" or "JENKINS_URL/job/JOBNAME/ownership/manage-owners" I get redirected to i.e. "JENKINS_URL/login?from=%2Fjob%2FJOBNAME%2Fownership%2Fmanage-owners" although I am logged in already; session is kept alive. I tried with changing from "project based matrix access" to "all access to authenticated users" but same error. I tried with a clean jenkins instance (LTS 1.565.1), installing ownership plugin only; configured ownership to pin current user to created job; configured global security: all access to authenticated user, user self registration enabled; then registered myself, created a job. See myself as primary owner of the job. Taking the described action leads to the same error. Environment: Jenkins LTS 1.565.1; ownership plugin 0.4 without job-restrictions plugin and role-strategy plugin; global security settings: - user realm: LDAP - project based matrix access Project: Jenkins Priority: Blocker Reporter: Stephan Krull This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [disk-usage] (JENKINS-24476) class hudson.plugins.disk_usage.BuildDiskUsageAction doesn't have @ExportedBean
Andrea Barbieri created JENKINS-24476 class hudson.plugins.disk_usage.BuildDiskUsageAction doesnt have @ExportedBean Issue Type: Bug Affects Versions: current Assignee: Lucie Votypkova Components: disk-usage Created: 28/Aug/14 10:46 AM Description: noticed these exceptions reported in the jenkins log file: Aug 28, 2014 6:35:00 AM org.kohsuke.stapler.export.Property writeValue WARNING: null org.kohsuke.stapler.export.NotExportableException: class hudson.plugins.disk_usage.BuildDiskUsageAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions at org.kohsuke.stapler.export.Model.init(Model.java:73) at org.kohsuke.stapler.export.ModelBuilder.get(ModelBuilder.java:51) at org.kohsuke.stapler.export.Property.writeValue(Property.java:231) at org.kohsuke.stapler.export.Property.writeValue(Property.java:187) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:190) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeTo(Model.java:157) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doJson(Api.java:205) at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:180) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at
[JIRA] [changelog-history] (JENKINS-24477) class com.cloudbees.jenkins.plugins.changelog.ChangelogAction doesn't have @ExportedBean
Andrea Barbieri created JENKINS-24477 class com.cloudbees.jenkins.plugins.changelog.ChangelogAction doesnt have @ExportedBean Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: changelog-history Created: 28/Aug/14 10:51 AM Description: the following exception found in jenkins log file: Aug 28, 2014 6:46:50 AM org.kohsuke.stapler.export.Property writeValue WARNING: null org.kohsuke.stapler.export.NotExportableException: class com.cloudbees.jenkins.plugins.changelog.ChangelogAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions at org.kohsuke.stapler.export.Model.init(Model.java:73) at org.kohsuke.stapler.export.ModelBuilder.get(ModelBuilder.java:51) at org.kohsuke.stapler.export.Property.writeValue(Property.java:231) at org.kohsuke.stapler.export.Property.writeValue(Property.java:187) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:190) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeTo(Model.java:157) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doJson(Api.java:205) at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:180) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at
[JIRA] [ownership] (JENKINS-24475) Managing ownership not possible
Oleg Nenashev started work on JENKINS-24475 Managing ownership not possible Change By: Oleg Nenashev (28/Aug/14 10:56 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ci-game] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTe
Andrea Barbieri created JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Issue Type: Bug Assignee: redsolo Components: ci-game Created: 28/Aug/14 10:58 AM Description: the ci-game plugin is throwing the following exception: Recording test results [ci-game] evaluating rule: Build result [ci-game] scored: 1.0 [ci-game] evaluating rule: Increased number of passed tests ERROR: Publisher hudson.plugins.cigame.GamePublisher aborted due to exception java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at hudson.plugins.cigame.rules.unittesting.AbstractUnitTestsRule.getPreviousBuildWithResults(AbstractUnitTestsRule.java:49) at hudson.plugins.cigame.rules.unittesting.AbstractUnitTestsRule.evaluate(AbstractUnitTestsRule.java:70) at hudson.plugins.cigame.model.ScoreCard.evaluate(ScoreCard.java:102) at hudson.plugins.cigame.model.ScoreCard.record(ScoreCard.java:45) at hudson.plugins.cigame.model.ScoreCard.record(ScoreCard.java:122) at hudson.plugins.cigame.GamePublisher.perform(GamePublisher.java:60) at hudson.plugins.cigame.GamePublisher.perform(GamePublisher.java:45) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1786) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) if required I can dig into the historical logs to determine which version of Jenkins started to generate the above exception. Environment: Fedora 20 64 bit Jenkins 1.577 Oracle JDK 1.7.0_45 Project: Jenkins Priority: Major Reporter: Andrea Barbieri This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately
Tim-Christian Bloss reopened JENKINS-18455 all modules of all maven projects are listed separately Hi, the problem seems to persist when using slicing to set JDK per maven project. When reconfiguring projects for new JDK versions, I see al modules of all projects listed. Environment: Debian 7.6 amd64 Oracle JRE7 1.7.0_60 Tomcat 7.0.54 Jenkins 1.554.3 Locale/Charset: de_DE.UTF-8 Change By: Tim-Christian Bloss (28/Aug/14 11:09 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately
Tim-Christian Bloss edited a comment on JENKINS-18455 all modules of all maven projects are listed separately Hi, the problem seems to persist when using slicing to set JDK per maven project. When reconfiguring projects for new JDK versions, I see al modules of all projects listed. Environment: Debian 7.6 amd64 Oracle JRE7 1.7.0_60 Tomcat 7.0.54 Jenkins 1.554.3 Locale/Charset: de_DE.UTF-8 EDIT 20140829@1310 : Configuration Sclicing Plugin 1.38.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-3122) auto build of downstream projects doesn't workfor m2 jobs in unstable state, when using surefire flag testFailureIgnore
Adam H commented on JENKINS-3122 auto build of downstream projects doesnt workfor m2 jobs in unstable state, when using surefire flag testFailureIgnore @peter: Yes, I would appreciate that a lot. I'm using the warnings plugin and want my builds to turn yellow on warnings, while still kicking off downstream jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23330) Spaces in project names are not encoded on tr IDs
Dominique Brice commented on JENKINS-23330 Spaces in project names are not encoded on tr IDs As noted in the PR, solution 1 and 2 breaks a feature of the keyboard plugin (selecting a job on a view page using the 'n' key for instance). Some code change is required in the Keyboard plugin in conjunction with JENKINS-23330. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [vsphere-cloud] (JENKINS-24479) The vSphere cloud will not allow this slave to start at this time.
Antonie Kriek created JENKINS-24479 The vSphere cloud will not allow this slave to start at this time. Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud Created: 28/Aug/14 11:53 AM Description: It looks as if there is a scenario where vSphereCloud.java Hashtable currentOnline does not get updated as it should. The nodes will work as they should, then it will fail to launch new nodes. From the looks of it the method vSphereCloud.canMarkVMOnline() return FALSE on 2nd or 3rd if statement. I had a quick look and I think the problem is in the vSphereCloudLauncher.postDisconnectVSphereActions() method. The vSphereCloud vsC = findOurVsInstance(); throws an exception just before the markVMOffline() is called. It will then never mark the VM as offline and you can never launch a node on that VM again until you restart Jenkins. Project: Jenkins Priority: Major Reporter: Antonie Kriek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-22130) keychain with the same name already exists error with developer profile import
Cesar Carrasco commented on JENKINS-22130 keychain with the same name already exists error with developer profile import deleting the key prior to building as GH Portefait suggested worked for me: security delete-keychain "jenkins-$JOB_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] [gui] (JENKINS-24472) Large XML results tables overlap Buld History
Daniel Beck commented on JENKINS-24472 Large XML results tables overlap Buld History Which Jenkins version is this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-24472) Large XML results tables overlap Build History
Daniel Beck updated JENKINS-24472 Large XML results tables overlap Build History Change By: Daniel Beck (28/Aug/14 12:15 PM) Summary: LargeXMLresultstablesoverlap Buld Build History This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [ci-game] (JENKINS-24473) Exception caught while evaluating ci-gam results
Philip Aston commented on JENKINS-24473 Exception caught while evaluating ci-gam results I upgraded to CI Game 1.20 and Jenkins 1.577 yesterday. CI Game breaks with same stack trace. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-23330) Spaces in project names are not encoded on tr IDs
Hubert Grzeskowiak commented on JENKINS-23330 Spaces in project names are not encoded on tr IDs We don't use the Keyboard Plugin either, but as noted above, IDs may be useful for Scrapping/Browser-Automation or for future Plugins. I vote for stripping spaces or replacing them by "-", "_" or even "%20" (html5 only). Latter solution has the advantage of generic URL encoding being possible to apply on all special chars, and URL fragments being the same as paths for the jobs. So jenkins/#My%20Job would jump to the "My Job" row, while jenkins/My%20Job would jump to the job's dashboard. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Murilo Opsfelder commented on JENKINS-15792 jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I downloaded the war file http://mirrors.jenkins-ci.org/war/1.565/jenkins.war, which I believe is the corresponding version of http://pkg.jenkins-ci.org/redhat-stable/jenkins-1.565.1-1.1.noarch.rpm, and it worked. By working I mean it started and I was able to access Jenkins web page at http://server:8080/. I started jenkins.war using the command below, which is different from the arguments used by /etc/init.d/jenkins script from jenkins-1.565.1-1.1 rpm. What's the difference between the war file and the jar file delivered by the rpm? java -jar jenkins-1.565.war Running from: /home/jenkins/jenkins-1.565.war webroot: $user.home/.jenkins Aug 28, 2014 9:42:40 AM winstone.Logger logInternal INFO: Beginning extraction from war file Aug 28, 2014 9:42:43 AM org.eclipse.jetty.util.log.JavaUtilLog info INFO: jetty-8.y.z-SNAPSHOT Aug 28, 2014 9:42:46 AM org.eclipse.jetty.util.log.JavaUtilLog info INFO: NO JSP Support for , did not find org.apache.jasper.servlet.JspServlet Jenkins home directory: /root/.jenkins found at: $user.home/.jenkins Aug 28, 2014 9:42:47 AM org.eclipse.jetty.util.log.JavaUtilLog info INFO: Started SelectChannelConnector@0.0.0.0:8080 Aug 28, 2014 9:42:47 AM winstone.Logger logInternal INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled Aug 28, 2014 9:42:48 AM jenkins.InitReactorRunner$1 onAttained INFO: Started initialization Aug 28, 2014 9:43:04 AM jenkins.InitReactorRunner$1 onAttained INFO: Listed all plugins Aug 28, 2014 9:43:04 AM jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins Aug 28, 2014 9:43:04 AM jenkins.InitReactorRunner$1 onAttained INFO: Started all plugins Aug 28, 2014 9:43:04 AM jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions Aug 28, 2014 9:43:04 AM jenkins.InitReactorRunner$1 onAttained INFO: Loaded all jobs Aug 28, 2014 9:43:04 AM hudson.ExtensionFinder$Sezpoz scout WARNING: Failed to scout hudson.tasks.test.AbstractTestResultAction$Summarizer java.lang.InstantiationException: java.lang.NoClassDefFoundError: hudson/model/Run$StatusSummarizer at net.java.sezpoz.IndexItem.element(IndexItem.java:146) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:666) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:335) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:334) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.get(ExtensionList.java:153) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1171) at hudson.maven.PluginImpl.init(PluginImpl.java:58) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoClassDefFoundError: hudson/model/Run$StatusSummarizer at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:755) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown
[JIRA] [build-flow] (JENKINS-24480) Unable to set environment variable or parameters of upstream job
James McGivern
created JENKINS-24480
Unable to set environment variable or parameters of upstream job
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
build-flow, core
Created:
28/Aug/14 12:54 PM
Description:
We are trying to build a "pipeline" orchestrated by a buildflow job and consisting of some "resuable" other parameterised jobs. The problem I am having is passing variables between a downstream job and the parent buildflow.
Here is the current code of a downstream job:
import com.cloudbees.plugins.flow.FlowRun
import groovy.json.JsonSlurper
import hudson.model.ParametersAction
import hudson.model.StringParameterValue
def commitMessage = build.environment.get("COMMIT_MESSAGE")
def password = build.environment.get("jenkins-read-only")
def issueKey = (commitMessage =~ $/(\p{Alpha}+-\d+).*/$)[0][1]
Authenticator.setDefault (new Authenticator() {
protected PasswordAuthentication getPasswordAuthentication() {
return new PasswordAuthentication ("jenkins-read-only", password.toCharArray())
}
})
def issueUrl = new URL("http://jira.scansafe.cisco.com/rest/api/2/issue/${issueKey}")
def content = new BufferedReader(new InputStreamReader(issueUrl.openConnection().getContent() as InputStream))
def issue = new JsonSlurper().parse(content)
String linkedReleaseTicket = issue.fields.issuelinks.inwardIssue.key.find { it =~ /RL-/}
if(linkedReleaseTicket == null) {
throw new IllegalStateException("Expected issue '${issueKey}' to be linked to ONE release ticket")
}
build.getCauses().each {
FlowRun run = it.flowRun
println(run)
println(run.class)
run.buildVariables.put("JIRA_TICKET", linkedReleaseTicket)
def existingParams = (ParametersAction) run.getAction(ParametersAction.class)
def newParams = [new StringParameterValue("JIRA_TICKET", linkedReleaseTicket)]
if (existingParams == null) {
run.addAction(new ParametersAction(newParams))
} else {
run.replaceAction(existingParams.createUpdated(newParams))
}
printVars("env", run.environment)
printVars("var", run.buildVariables)
}
build.environment.put("JIRA_TICKET", linkedReleaseTicket)
build.buildVariables.put("JIRA_TICKET", linkedReleaseTicket)
def void printVars(String name, def vars) {
println("-"*32)
println("")
println(name + "::")
vars.each {
println " ${it.key} : ${it.value}"
}
println("")
println("-"*32)
println("")
}
return "Found release ticket: ${linkedReleaseTicket}"
I've tried putting it in every "environment" map possible and even the hack from StackOverflow (using the dynamic parameters) doesn't seem to work. In the child job you can see the value of the variable, but in the parent its always null.
Its as if the child got an immutable copy of the parent's environment variables, and that the child also doesn't expose any modifications of its own environment variables so that in the parent buildflow you can do something like:
releaseTicketJob = build("lookup-release-ticket", COMMIT_MESSAGE: commitMessage)
def ticket = releaseTicketJob.build.environment.get("JIRA_TICKET")
or
releaseTicketJob = build("lookup-release-ticket", COMMIT_MESSAGE: commitMessage)
def ticket = params.get("JIRA_TICKET")
Is there any way to pass this information between the child and parent job?
Thanks
Environment:
Jenkins 1.570, Build flow plugin v0.12
Project:
Jenkins
Priority:
Major
Reporter:
James McGivern
[JIRA] [delivery-pipeline] (JENKINS-22843) Show test result in task if any
Per Flitig commented on JENKINS-22843 Show test result in task if any I also think this would be a really nice feature, though perhaps not exactly like in the screenshots - I really like the current flat background status colors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-24461) Filter change log based on included/excluded regions
Dan Glanzmann commented on JENKINS-24461 Filter change log based on included/excluded regions I can not speak for my namesake, but yes to filter the changelog is exactly what I need for my project. We have two jenkins jobs building different projects stored in a common git repository. Currently we have with this setup the list of all changes of both jobs in the changelog and need a possibility to filter only the interesting source paths (pom.xml or included/excluded job rule) for 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] [build-flow] (JENKINS-24480) Unable to set environment variable or parameters of upstream job
James McGivern commented on JENKINS-24480 Unable to set environment variable or parameters of upstream job Forgot to note I'm using the EnvInject plugin to inject the password for the user so its not exposed in the general job configuration This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Hi. I'm using the 2.12-Snapshot Android Emulator Plugin from the pull 39 link/post on Mac OS X 10.9 and Android SDK Revision 23.0.2 I'm not sure if my problem is 100% the problem described here. Here my problem: If my Jenkins job starts then the Android Emulator sometimes starts without any problem and sometimes I get the device offline notification. I can't reproduce, when the emulator will work fine or will fail to start. I tried different screen sizes and I was using an existing emulator and I created a new emulator while the Jenkins jobs. I don't know what further steps I can do. So I will post my log and hope you can help me. $ /Library/android-sdk-macosx/tools/android list target [android] Using Android SDK: /Library/android-sdk-macosx [android] Creating Android AVD: /Users/Shared/Jenkins/Home/jobs/(placeholder)/workspace/.android/avd/hudson_de-DE_160_HVGA_Google_Inc._Google_APIs_19_armeabi-v7a.avd [android] /Library/android-sdk-macosx/tools/android create avd -f -a -s HVGA -n hudson_de-DE_160_HVGA_Google_Inc._Google_APIs_19_armeabi-v7a -t "Google Inc.:Google APIs:19" --abi armeabi-v7a $ /Library/android-sdk-macosx/platform-tools/adb start-server * daemon not running. starting it now on port 5897 * * daemon started successfully * $ /Library/android-sdk-macosx/platform-tools/adb start-server [android] Starting Android emulator $ /Library/android-sdk-macosx/tools/emulator -no-boot-anim -ports 5895,5896 -prop persist.sys.language=de -prop persist.sys.country=DE -avd hudson_de-DE_160_HVGA_Google_Inc._Google_APIs_19_armeabi-v7a -no-snapshot-load -no-snapshot-save -wipe-data -no-window $ /Library/android-sdk-macosx/platform-tools/adb connect emulator-5895 [android] Waiting for emulator to finish booting... $ /Library/android-sdk-macosx/platform-tools/adb devices -l List of devices attached emulator-5895 offline [android] adb devices returned 0 $ /Library/android-sdk-macosx/platform-tools/adb -s emulator-5895 shell getprop dev.bootcomplete error: device offline error: device offline $ /Library/android-sdk-macosx/platform-tools/adb connect emulator-5895 $ /Library/android-sdk-macosx/platform-tools/adb devices -l List of devices attached emulator-5895 offline [android] adb devices returned 0 $ /Library/android-sdk-macosx/platform-tools/adb -s emulator-5895 shell getprop dev.bootcomplete error: device offline error: device offline $ /Library/android-sdk-macosx/platform-tools/adb connect emulator-5895 $ /Library/android-sdk-macosx/platform-tools/adb devices -l List of devices attached emulator-5895 offline [android] adb devices returned 0 $ /Library/android-sdk-macosx/platform-tools/adb -s emulator-5895 shell getprop dev.bootcomplete error: device offline error: device offline $ /Library/android-sdk-macosx/platform-tools/adb disconnect emulator-5895 $ /Library/android-sdk-macosx/platform-tools/adb connect emulator-5895 $ /Library/android-sdk-macosx/platform-tools/adb devices -l List of devices attached emulator-5895 offline [android] adb devices returned 0 $ /Library/android-sdk-macosx/platform-tools/adb -s emulator-5895 shell getprop dev.bootcomplete error: device offline error: device offline $ /Library/android-sdk-macosx/platform-tools/adb connect emulator-5895 $ /Library/android-sdk-macosx/platform-tools/adb devices -l List of devices attached emulator-5895 offline [android] adb devices returned 0 $ /Library/android-sdk-macosx/platform-tools/adb -s emulator-5895 shell getprop dev.bootcomplete error: device offline error: device offline $ /Library/android-sdk-macosx/platform-tools/adb connect emulator-5895 $ /Library/android-sdk-macosx/platform-tools/adb devices -l List of devices attached emulator-5895 offline [android] adb devices returned 0 $ /Library/android-sdk-macosx/platform-tools/adb -s emulator-5895 shell getprop dev.bootcomplete error: device offline error: device offline $ /Library/android-sdk-macosx/platform-tools/adb disconnect emulator-5895 $ /Library/android-sdk-macosx/platform-tools/adb connect emulator-5895 $ /Library/android-sdk-macosx/platform-tools/adb devices -l List of devices attached emulator-5895 offline [android] adb devices returned 0 $ /Library/android-sdk-macosx/platform-tools/adb -s emulator-5895 shell getprop dev.bootcomplete error: device offline error: device offline $
[JIRA] [changelog-history] (JENKINS-24477) class com.cloudbees.jenkins.plugins.changelog.ChangelogAction doesn't have @ExportedBean
Henrik Nicolaisen commented on JENKINS-24477 class com.cloudbees.jenkins.plugins.changelog.ChangelogAction doesnt have @ExportedBean I started getting this error yesterday as well This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [allure-jenkins] (JENKINS-24481) Could not deleting files/folder in workspace
Arpit Nagar created JENKINS-24481 Could not deleting files/folder in workspace Issue Type: Bug Affects Versions: current Assignee: Artem Eroshenko Components: allure-jenkins Created: 28/Aug/14 1:10 PM Description: We are getting Error in deleting files/folder in workspace. Please see below logs for more detail _ _ 18:17:46 Allure Report Generation: attach report link to build and project 18:17:48 Allure Report Generation: Can't delete directory D:\Jenkins\Core\Artifacts\workspace\Scepter-Hotel-Search-Travelguru_1_0\allure3996563737139319681.tmp 18:17:48 java.io.IOException: remote file operation failed: D:\Jenkins\Core\Artifacts\workspace\Scepter-Hotel-Search-Travelguru_1_0\allure3996563737139319681.tmp at hudson.remoting.Channel@f61a9a:Cylon-Slave 18:17:48 at hudson.FilePath.act(FilePath.java:913) 18:17:48 at hudson.FilePath.act(FilePath.java:895) 18:17:48 at hudson.FilePath.deleteContents(FilePath.java:1104) 18:17:48 at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.deleteRecursive(AllureReportPublisher.java:215) 18:17:48 at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.perform(AllureReportPublisher.java:137) 18:17:48 at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110) 18:17:48 at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154) 18:17:48 at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105) 18:17:48 at org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher.perform(ConditionalPublisher.java:134) 18:17:48 at org.jenkins_ci.plugins.flexible_publish.FlexiblePublisher.perform(FlexiblePublisher.java:111) 18:17:48 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 18:17:48 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) 18:17:48 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) 18:17:48 at hudson.model.Build$BuildExecution.post2(Build.java:183) 18:17:48 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) 18:17:48 at hudson.model.Run.execute(Run.java:1765) 18:17:48 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 18:17:48 at hudson.model.ResourceController.execute(ResourceController.java:89) 18:17:48 at hudson.model.Executor.run(Executor.java:240) 18:17:48 Caused by: java.nio.file.FileSystemException: D:\Jenkins\Core\Artifacts\workspace\Scepter-Hotel-Search-Travelguru_1_0\allure3996563737139319681.tmp\repositories\com\fasterxml\jackson\core\jackson-annotations\2.3.0\jackson-annotations-2.3.0.jar: The process cannot access the file because it is being used by another process. 18:17:48 18:17:48 at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) 18:17:48 at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) 18:17:48 at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) 18:17:48 at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) 18:17:48 at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) 18:17:48 at java.nio.file.Files.delete(Unknown Source) 18:17:48 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 18:17:48 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 18:17:48 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 18:17:48 at java.lang.reflect.Method.invoke(Unknown Source) 18:17:48 at hudson.Util.deleteFile(Util.java:247) 18:17:48 at hudson.Util.deleteRecursive(Util.java:310) 18:17:48 at hudson.Util.deleteContentsRecursive(Util.java:212) 18:17:48 at hudson.Util.deleteRecursive(Util.java:301) 18:17:48 at hudson.Util.deleteContentsRecursive(Util.java:212) 18:17:48 at hudson.Util.deleteRecursive(Util.java:301) 18:17:48 at hudson.Util.deleteContentsRecursive(Util.java:212) 18:17:48 at
[JIRA] [scm-sync-configuration] (JENKINS-14847) Apply button not taken into account
Jay Beeckman commented on JENKINS-14847 Apply button not taken into account Any update on this? I'd even settle for a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-environment] (JENKINS-24482) Shell syntax highlighting for Build step gone after upgrade to v1.577
Alexandru Gheorghe created JENKINS-24482 Shell syntax highlighting for Build step gone after upgrade to v1.577 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-environment Created: 28/Aug/14 1:39 PM Description: After upgrading to Jenkins v1.577, scrolling of the build step shell execution has failed and also syntax highlighting fails. Also seems that horizontal scrolling is no longer available as everything wraps. Could be because of fixes for regressions in v1.576, not sure. Observed with Iceweasel 24.7.0 Environment: OS: Ubuntu 12.04.4 LTS; Java: java version 1.6.0_31 + OpenJDK Runtime Environment (IcedTea6 1.13.3) (6b31-1.13.3-1ubuntu1~0.12.04.2) + OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode); Jenkins v1.577 Project: Jenkins Labels: usability Priority: Trivial Reporter: Alexandru Gheorghe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] (JENKINS-24482) Shell syntax highlighting for Build step gone after upgrade to v1.577
Alexandru Gheorghe updated JENKINS-24482 Shell syntax highlighting for Build step gone after upgrade to v1.577 Attached 1-scroll.png and 2-scroll.png depicting the issue. Change By: Alexandru Gheorghe (28/Aug/14 1:41 PM) Attachment: 1-scroll.png Attachment: 2-scroll.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [template-project] (JENKINS-23204) Template Plugin to be able to import job parameters
Tom Ghyselinck commented on JENKINS-23204 Template Plugin to be able to import job parameters Please give this a high priority! This is a feature that would decrease our configuration and maintenance effort by factor 3! We have several Jobs which are used as template for other Jobs which have only minor changes in configuration parameters. All the rest of the configuration is identical and shared from the main Job: scm repositories (which currently does not work for some Jobs because of https://issues.jenkins-ci.org/browse/JENKINS-24404) build steps post-build actions ... This is one of the last missing _shared configuration item_s 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] [ci-game] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTe
Dell Green commented on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction it doesn't happen all the time, just randomly for the same job/s This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [ci-game] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTe
Dell Green commented on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Having the exact same problem, on my Jenkins Mac Server, Running Oracle JDK 1.8.0_11-b12 Jenkins: 1.577 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [rebuild] (JENKINS-24468) Rebuild should offer parameters not currently defined on the job
Larry Grill commented on JENKINS-24468 Rebuild should offer parameters not currently defined on the job It appears that this is also not connected to the Jenkins version, but has been working for us due to a magical combination of plugins on our release build system. I will still argue that the goal of the Rebuild plugin is to rebuild the last run of the job using the same parameters that job run used (whether they are configured in the job or not) and that the should use the parameter list one sees with http://jenkins-url/job/job-name/1/parameters/ I am now assuming that we can achieve the desired behavior by matching a required plugin set. If that proves impossible to replicate we can attempt to enhance the Rebuild plugin to support this capability. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [rebuild] (JENKINS-24468) Rebuild should offer parameters not currently defined on the job
Larry Grill edited a comment on JENKINS-24468 Rebuild should offer parameters not currently defined on the job It appears that this is also not connected to the Jenkins version, but has been working for us due to a magical combination of plugins on our release build system. I will still argue that the goal of the Rebuild plugin is to rebuild the last run of the job using the same parameters that job run used (whether they are configured in the job or not) and that the rebuild should use the parameter list one sees with http://jenkins-url/job/job-name/1/parameters/ I am now assuming that we can achieve the desired behavior by matching a required plugin set. If that proves impossible to replicate we can attempt to enhance the Rebuild plugin to support this capability. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-23330) Spaces in project names are not encoded on tr IDs
Daniel Beck commented on JENKINS-23330 Spaces in project names are not encoded on tr IDs IDs may be useful for Scrapping/Browser-Automation or for future Plugins Sounds like YAGNI to me. 1. The "feature" is broken. 2. Nobody* uses it. The best fix would be to just get rid of it in core. It's just something that needs to be maintained for no real reason. It could always be added again later once someone actually needs it, has a good reason for it, and can provide an implementation that's not trivially broken. *400 stagnating installs is close enough to nobody and so far no other implemented use cases of this have been mentioned. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-23330) Spaces in project names are not encoded on tr IDs
Hubert Grzeskowiak commented on JENKINS-23330 Spaces in project names are not encoded on tr IDs Fair point and ok for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-24483) RepositoryBrowser.getChangeSetLink exceptions from Jelly pollute log
Jesse Glick created JENKINS-24483 RepositoryBrowser.getChangeSetLink exceptions from Jelly pollute log Issue Type: Bug Assignee: Nicolas De Loof Components: core, git Created: 28/Aug/14 2:49 PM Description: Your Jenkins log can fill up with long stack traces like h.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: browser.getChangeSetLink(cs) in /jenkins/job/.../1234/. Reason: java.net.MalformedURLException: no protocol: java.net.MalformedURLException: no protocol: at java.net.URL.init(URL.java:585) at java.net.URL.init(URL.java:482) at java.net.URL.init(URL.java:431) at hudson.plugins.git.browser.GitRepositoryBrowser.getUrl(GitRepositoryBrowser.java:47) at hudson.plugins.git.browser.GithubWeb.getChangeSetLink(GithubWeb.java:40) at ... when this is a harmless condition: just an unconfigured base URL. Probably RepositoryBrowser should get a new method that calls getChangeSetLink but logs exceptions at FINE and returns null, and then Jelly views (both in core and plugins) should be updated to use it. (Falling back to displaying an unlinked changeset, just as if getChangeSetLink returned null.) Project: Jenkins Labels: scm jelly exception Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [all-changes] (JENKINS-19347) Lowongan Kerja terbaru 2013
Jesse Glick closed JENKINS-19347 as Not A Defect Lowongan Kerja terbaru 2013 Change By: Jesse Glick (28/Aug/14 2:55 PM) Status: Reopened Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [all-changes] (JENKINS-19347) Lowongan Kerja terbaru 2013
Jesse Glick reopened JENKINS-19347 Lowongan Kerja terbaru 2013 Argh, need to reopen just to clear spam label. Change By: Jesse Glick (28/Aug/14 2:55 PM) Resolution: NotADefect Status: Closed Reopened Assignee: wolfs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [all-changes] (JENKINS-19347) Lowongan Kerja terbaru 2013
Jesse Glick updated JENKINS-19347 Lowongan Kerja terbaru 2013 Change By: Jesse Glick (28/Aug/14 2:55 PM) Labels: lowongan,kerja,terbaru This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-24467) Possible regression of JENKINS-14321
Mark Waite commented on JENKINS-24467 Possible regression of JENKINS-14321 If it were me, I'd first go looking for other places which may have introduced that incorrect setting of the PATH environment variable. For example, check that the Jenkins system settings did not somehow get a PATH setting with those flawed values. A "grep" for that path string in the Jenkins home directory may quickly show you where that value has been incorrectly placed. I propose to close this as "not a bug", since there is no indication that the root of the problem is due to a git plugin or git client plugin bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot] (JENKINS-22290) Code style: Mixes between tabs and spaces in source code
Jesse Glick updated JENKINS-22290 Code style: Mixes between tabs and spaces in source code Change By: Jesse Glick (28/Aug/14 2:56 PM) Labels: tab,space,codestyle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-21574) Turn on autorefresh by default
Jesse Glick updated JENKINS-21574 Turn on autorefresh by default Change By: Jesse Glick (28/Aug/14 2:57 PM) Labels: refresh, auto ,autorefresh,ajax,web, -refresh ui ,interface,user, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge] (JENKINS-11379) Local module directory not copied from trunk project when creating a feature branch
Jesse Glick updated JENKINS-11379 Local module directory not copied from trunk project when creating a feature branch Change By: Jesse Glick (28/Aug/14 2:57 PM) Labels: https://github.com/jenkinsci/svnmerge-plugin/pull/4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-21574) Turn on autorefresh by default
Jesse Glick resolved JENKINS-21574 as Wont Fix Turn on autorefresh by default No way. Change By: Jesse Glick (28/Aug/14 2:57 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-20667) cli over internet doesn't work
Jesse Glick updated JENKINS-20667 cli over internet doesnt work Change By: Jesse Glick (28/Aug/14 2:59 PM) Labels: cli ,http,internet This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge] (JENKINS-15830) Error: Unable to infer the new branch name from XXX
Jesse Glick updated JENKINS-15830 Error: Unable to infer the new branch name from XXX Change By: Jesse Glick (28/Aug/14 2:59 PM) Labels: error , pluginsvnmerge This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-16684) Add GIT_URL to build environment
Jesse Glick updated JENKINS-16684 Add GIT_URL to build environment Change By: Jesse Glick (28/Aug/14 2:59 PM) Labels: git , jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [avatar] (JENKINS-18494) Switch source code to GIT
Jesse Glick updated JENKINS-18494 Switch source code to GIT Change By: Jesse Glick (28/Aug/14 3:01 PM) Labels: git , githubscm , This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-23556) Git fetch fails when Repository URL is a Parameter with trailing whitespace
Jesse Glick updated JENKINS-23556 Git fetch fails when Repository URL is a Parameter with trailing whitespace Change By: Jesse Glick (28/Aug/14 3:00 PM) Labels: git,git-clientgit-plugin, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-21553) Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL
Jesse Glick updated JENKINS-21553 Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL Change By: Jesse Glick (28/Aug/14 3:00 PM) Labels: create,creation,git,https,job,maven, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [cobertura] (JENKINS-17749) Data displayed in Jenkins, do not correspond exactly to the data in the file coverage.xml
Jesse Glick updated JENKINS-17749 Data displayed in Jenkins, do not correspond exactly to the data in the file coverage.xml Change By: Jesse Glick (28/Aug/14 3:01 PM) Labels: cobertura , coverage , xml , This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20512) Git Plugin 2.0: Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins
Jesse Glick updated JENKINS-20512 Git Plugin 2.0: Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins Change By: Jesse Glick (28/Aug/14 3:01 PM) Labels: git , pollingscm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-21553) Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL
Jesse Glick reopened JENKINS-21553 Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL (reopening just to clear bad labels) Change By: Jesse Glick (28/Aug/14 3:00 PM) Resolution: CannotReproduce Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.
Jesse Glick updated JENKINS-21518 Error while using SSH credentials to fetch git repository. Change By: Jesse Glick (28/Aug/14 3:01 PM) Labels: authentication , gitssh , This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [cobertura] (JENKINS-17749) Data displayed in Jenkins, do not correspond exactly to the data in the file coverage.xml
Jesse Glick updated JENKINS-17749 Data displayed in Jenkins, do not correspond exactly to the data in the file coverage.xml Change By: Jesse Glick (28/Aug/14 3:02 PM) Labels: cobertura coveragexml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-21553) Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL
Jesse Glick closed JENKINS-21553 as Cannot Reproduce Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL Change By: Jesse Glick (28/Aug/14 3:00 PM) Status: Reopened Closed Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer] (JENKINS-16808) deployment of more files
Jesse Glick reopened JENKINS-16808 deployment of more files (reopening just to clear bad labels) Change By: Jesse Glick (28/Aug/14 3:02 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [publish-over-cifs] (JENKINS-20363) Implement option in GUI to disable checkpointing feature
Jesse Glick updated JENKINS-20363 Implement option in GUI to disable checkpointing feature Change By: Jesse Glick (28/Aug/14 3:03 PM) Labels: BuildMonitorcheckpointcifsdelay jenkins, post-build This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer] (JENKINS-16808) deployment of more files
Jesse Glick closed JENKINS-16808 as Fixed deployment of more files Change By: Jesse Glick (28/Aug/14 3:03 PM) Status: Reopened Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24467) Possible regression of JENKINS-14321
Daniel Beck commented on JENKINS-24467 Possible regression of JENKINS-14321 Seriously Rob, things like this need to be reproducible with envinject disabled to be valid. It's been the real culprit too often... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [maven2] (JENKINS-13926) The relation between the Global MAVEN_OPTS and the job-specific MAVEN_OPTS
Jesse Glick updated JENKINS-13926 The relation between the Global MAVEN_OPTS and the job-specific MAVEN_OPTS Change By: Jesse Glick (28/Aug/14 3:03 PM) Labels: configuration maven2, options This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [weblogic-deployer] (JENKINS-16808) deployment of more files
Jesse Glick updated JENKINS-16808 deployment of more files Change By: Jesse Glick (28/Aug/14 3:02 PM) Labels: deployearmaven , warweblogic This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-12472) Older subversion credentials used after given new credentials
Jesse Glick updated JENKINS-12472 Older subversion credentials used after given new credentials Change By: Jesse Glick (28/Aug/14 3:04 PM) Labels: credentials jenkins,subversion,svn, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [email-ext] (JENKINS-14311) Add new trigger to email-ext plugin: Success with changes
Jesse Glick closed JENKINS-14311 as Wont Fix Add new trigger to email-ext plugin: Success with changes Change By: Jesse Glick (28/Aug/14 3:05 PM) Status: Reopened Closed Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-14554) With german locale buttons Advanced and Test are not visible in security management
Jesse Glick updated JENKINS-14554 With german locale buttons Advanced and Test are not visible in security management Change By: Jesse Glick (28/Aug/14 3:04 PM) Labels: jenkins,plugins windows This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [email-ext] (JENKINS-14311) Add new trigger to email-ext plugin: Success with changes
Jesse Glick reopened JENKINS-14311 Add new trigger to email-ext plugin: Success with changes (reopening just to clear bad labels) Change By: Jesse Glick (28/Aug/14 3:04 PM) Resolution: WontFix Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-12473) Subversion option vanishes under Source-Code-Management in project configuration
Jesse Glick updated JENKINS-12473 Subversion option vanishes under Source-Code-Management in project configuration Change By: Jesse Glick (28/Aug/14 3:05 PM) Labels: jenkins,subversion, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [rebuild] (JENKINS-16874) java.lang.NullPointerException: Current Project is null
Jesse Glick updated JENKINS-16874 java.lang.NullPointerException: Current Project is null Change By: Jesse Glick (28/Aug/14 3:04 PM) Labels: envinject jenkins,plugin, rebuild This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [email-ext] (JENKINS-14311) Add new trigger to email-ext plugin: Success with changes
Jesse Glick updated JENKINS-14311 Add new trigger to email-ext plugin: Success with changes Change By: Jesse Glick (28/Aug/14 3:04 PM) Labels: changes,email-ext,featurejenkins,plugin, scm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-12474) Subversion rejected Basic challenge
Jesse Glick updated JENKINS-12474 Subversion rejected Basic challenge Change By: Jesse Glick (28/Aug/14 3:05 PM) Labels: credentials jenkins,subversion, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [jenkins-multijob-plugin] (JENKINS-19917) Job getting failed because of Maven plugin update in Jenkins 1.509.2 upgradation
Jesse Glick updated JENKINS-19917 Job getting failed because of Maven plugin update in Jenkins 1.509.2 upgradation Change By: Jesse Glick (28/Aug/14 3:05 PM) Labels: jenkins maven2 plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-13088) Possibility to populate scm in pom's
Jesse Glick updated JENKINS-13088 Possibility to populate scm in poms Change By: Jesse Glick (28/Aug/14 3:06 PM) Labels: jenkins maven2scm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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] [maven2] (JENKINS-19267) Jenkins 1.527 and latter does not use JDK5 defined at job - compile phase still use JDK6
Jesse Glick updated JENKINS-19267 Jenkins 1.527 and latter does not use JDK5 defined at job - compile phase still use JDK6 Change By: Jesse Glick (28/Aug/14 3:06 PM) Labels: java5 jenkins maven2 plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-23781) ActiveDirectory plugin 'test' button doesn't support ipv6
Jesse Glick updated JENKINS-23781 ActiveDirectory plugin test button doesnt support ipv6 Change By: Jesse Glick (28/Aug/14 3:07 PM) Labels: active_directory, exceptionipv6 plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-20064) Cannot use CLI or URL with API token with Active Directory as the access control security realm
Jesse Glick updated JENKINS-20064 Cannot use CLI or URL with API token with Active Directory as the access control security realm Change By: Jesse Glick (28/Aug/14 3:07 PM) Labels: LDAP active_directory, clisecurity This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-17824) Error when upgrading from version 1.30: com4j.ComException:The server is not operational.
Jesse Glick updated JENKINS-17824 Error when upgrading from version 1.30: com4j.ComException:The server is not operational. Change By: Jesse Glick (28/Aug/14 3:08 PM) Labels: active_directory, authentication This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-19011) Role-Based Strategy plugin users error
Jesse Glick reopened JENKINS-19011 Role-Based Strategy plugin users error (reopening just to clear bad labels) Change By: Jesse Glick (28/Aug/14 3:08 PM) Resolution: Duplicate Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-19011) Role-Based Strategy plugin users error
Jesse Glick closed JENKINS-19011 as Duplicate Role-Based Strategy plugin users error Change By: Jesse Glick (28/Aug/14 3:08 PM) Status: Reopened Closed 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/d/optout.
[JIRA] [active-directory] (JENKINS-18906) Problem with Active Directory plugin and Role-Based Strategy plugin working together
Jesse Glick updated JENKINS-18906 Problem with Active Directory plugin and Role-Based Strategy plugin working together Change By: Jesse Glick (28/Aug/14 3:08 PM) Labels: active_directory, configuration jenkinspluginsrole_strategy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-12370) Multiple domains aren't allowed for Authentication test tool in Active Directory Plugin
Jesse Glick updated JENKINS-12370 Multiple domains arent allowed for Authentication test tool in Active Directory Plugin Change By: Jesse Glick (28/Aug/14 3:09 PM) Labels: active_directory, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-12907) Active Directory/LDAP group with special characters causes authentication/retrieveUser to fail
Jesse Glick updated JENKINS-12907 Active Directory/LDAP group with special characters causes authentication/retrieveUser to fail Change By: Jesse Glick (28/Aug/14 3:09 PM) Labels: active_directory, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-13677) Active Direcoty Plugin not encrypted - FINE: Failed to start TLS. Authentication will be done via plain-text LDAP
Jesse Glick updated JENKINS-13677 Active Direcoty Plugin not encrypted - FINE: Failed to start TLS. Authentication will be done via plain-text LDAP Change By: Jesse Glick (28/Aug/14 3:09 PM) Labels: LDAPLDAPSSSL active_directory, encryptionplain-texttls This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and 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-24467) Possible regression of JENKINS-14321
Mark Waite resolved JENKINS-24467 as Not A Defect Possible regression of JENKINS-14321 Change By: Mark Waite (28/Aug/14 3:08 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
