[JIRA] (JENKINS-12768) Building Jenkins on Windows fails with test errors
[
https://issues.jenkins-ci.org/browse/JENKINS-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159981#comment-159981
]
Christian Wolfgang commented on JENKINS-12768:
--
I have a similar problem. I have the following unit test:
{code}
FreeStyleProject project = createFreeStyleProject( drmemory );
final InputStream in = getClass().getClassLoader().getResourceAsStream(
results.txt );
/* To get the real workspace and copy the results.txt */
project.getBuildersList().add(new TestBuilder() {
public boolean perform(AbstractBuild?, ? build, Launcher launcher,
BuildListener listener) throws InterruptedException, IOException {
build.getWorkspace().child(drmemory).child( 1 ).child(
results.txt ).copyFrom( in );
return true;
}
});
Builder builder = new DrMemoryBuilder( , , drmemory );
project.getBuildersList().add( builder );
DrMemoryPublisher publisher = new DrMemoryPublisher();
project.getPublishersList().add( publisher );
FreeStyleBuild b = project.scheduleBuild2( 0, new Cause.UserIdCause() ).get();
{code}
which results in a Failed to clean up temp dirs error, because the publisher
copies the file drmemory/1/results.txt to the builds folder and it is unable
to delete that file.
Building Jenkins on Windows fails with test errors
--
Key: JENKINS-12768
URL: https://issues.jenkins-ci.org/browse/JENKINS-12768
Project: Jenkins
Issue Type: Bug
Components: core
Environment: Windows 7 x64 Ultimate
javac 1.6.0_30 64-bit
Jenkins 1.452
Reporter: Slide-O-Mix
Assignee: Kohsuke Kawaguchi
Running jenkins.RemotingJarSignatureTest
Verifying
C:\Users\USER\.m2\repository\org\jenkins-ci\main\remoting\2.12\remoting-2.12.jar
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.027 sec
Results :
Failed tests:
testRotation(hudson.util.io.ReopenableRotatingFileOutputStreamTest):
expected:Content[4] but was:Content[2]
Tests in error:
testCopyTo2(hudson.FilePathTest): remote file operation failed:
C:\Users\USER\Code\jenkins\jenkins\core\target\testCopyTo6068700686750233812
at hudson.remoting.Channel@17094d48:The other side of the channel
testRemoting(hudson.util.ProcessTreeTest): Failed to read environment
variable table error=299 at .\envvar-cmdline.cpp:114
testIsSymlink(hudson.UtilTest): got: false, expected: is true
Tests run: 2429, Failures: 1, Errors: 3, Skipped: 0
The testCopyTo2 test functions correctly on a 32-bit JDK, but the other tests
fail for the same reasons.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases
[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno P. Kinoshita closed JENKINS-12810. Fixed in 3.1 JUnit test results are getting wrongly attached to all the test cases - Key: JENKINS-12810 URL: https://issues.jenkins-ci.org/browse/JENKINS-12810 Project: Jenkins Issue Type: Bug Components: testlink Affects Versions: current Reporter: Vignesh Senapathy Assignee: Bruno P. Kinoshita Fix For: current Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, schema.jpg, screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png, testlink-3.1-alpha2.hpi, testlink-3.1-RC2.hpi Hi, I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the Junit Test results are getting generated. This in turn calls the Testlink xml rpc and attaches the results to the test case, but the test results are attached wrongly. The 1st test case has 6 results, the next has 5 and so on and the last one has 1 test result attached to it. I dont know if it is bug which is causing this. Please let me know what seems to be the problems. Also the execution flags are correctly rendered in this. which ever test case fails is marked as failed and which passed is marked as passed. Also I have one custom field which maps to the test suite name and test classname. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11442) The plug-in is using disabled tests
[ https://issues.jenkins-ci.org/browse/JENKINS-11442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno P. Kinoshita closed JENKINS-11442. Fixed in 3.1 The plug-in is using disabled tests --- Key: JENKINS-11442 URL: https://issues.jenkins-ci.org/browse/JENKINS-11442 Project: Jenkins Issue Type: Bug Components: testlink Reporter: Bruno P. Kinoshita Assignee: Bruno P. Kinoshita Assuming the following JUnit XML report: ?xml version=1.0 encoding=UTF-8? testsuites tests=2 failures=0 disabled=1 errors=0 time=11.000 name=AllTests testsuite name=ClassA tests=1 failures=0 disabled=0 errors=0 time=5.000 testcase name=UseCaseA status=run time=5.000 classname=ClassA / /testsuite testsuite name=ClassB tests=1 failures=0 disabled=1 errors=0 time=6.000 testcase name=DISABLED_UseCaseB status=notrun time=6.000 classname=ClassB / /testsuite /testsuites At moment, TestLink plugin reports the above XML as a test that passed though one is disabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno P. Kinoshita closed JENKINS-12916.
Fixed in 3.1
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11777) Jenkins configuration page does not work properly when Jenkins Slave SetupPlugin enabled
[ https://issues.jenkins-ci.org/browse/JENKINS-11777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm reassigned JENKINS-11777: Assignee: Frederik Fromm (was: Kohsuke Kawaguchi) Jenkins configuration page does not work properly when Jenkins Slave SetupPlugin enabled Key: JENKINS-11777 URL: https://issues.jenkins-ci.org/browse/JENKINS-11777 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Reporter: Oleksandr Popov Assignee: Frederik Fromm Attachments: issue.JPG Jenkins configuration page does not work properly when Jenkins Slave SetupPlugin enabled. This issue appeared since I use Jenkins 1.437 and it not fixed until now (v. 1.437). See screenshot. In such way Jenkins got stacked if this plugin enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11894) All tests {test Methods} of TestNG, belonging to the same class are shown as FAILURE, if just one of the test is a failure
[
https://issues.jenkins-ci.org/browse/JENKINS-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno P. Kinoshita closed JENKINS-11894.
Fixed in 3.1
All tests {test Methods} of TestNG, belonging to the same class are shown as
FAILURE, if just one of the test is a failure
-
Key: JENKINS-11894
URL: https://issues.jenkins-ci.org/browse/JENKINS-11894
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: Jenkins Version 1.440 {Testlink Plugin - Version 3.0.2}
Testlink Version 1.9.3 (Prague)
Reporter: Venugopal Shenoy
Assignee: Bruno P. Kinoshita
Priority: Critical
Labels: plugin
Attachments: testlink.hpi, testng-results.xml
Create one TestNG test class with several test methods {say 3 methods}. One
of the test is deliberately failed {using assertTrue(false);}. All the
tests are shown as failure in Testlink, when the testng xml test results are
pushed to testlink using the Jenkins-Testlink plugin. {TestNG XML Results
file is attached}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10849) OutOfMemoryError using TestLink plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno P. Kinoshita closed JENKINS-10849. The same issue is being treated in https://issues.jenkins-ci.org/browse/JENKINS-11393 OutOfMemoryError using TestLink plugin -- Key: JENKINS-10849 URL: https://issues.jenkins-ci.org/browse/JENKINS-10849 Project: Jenkins Issue Type: Bug Components: testlink Environment: Jenkins run on RedHat Linux (master and slaves) within VMware. Reporter: John Sillers Assignee: Bruno P. Kinoshita Attachments: JENKINS-10849.ods, junitXml.jar, testlink-3.0-alpha1.hpi Failure is: FATAL: Unkown internal error. Please, open an issue in Jenkins JIRA with the complete stack trace. If possible, try including the JUnit XML(s) too. hudson.plugins.testlink.result.TestResultSeekerException: Unkown internal error. Please, open an issue in Jenkins JIRA with the complete stack trace. If possible, try including the JUnit XML(s) too. at hudson.plugins.testlink.result.junit.JUnitTestCasesTestResultSeeker.seek(JUnitTestCasesTestResultSeeker.java:117) at hudson.plugins.testlink.result.TestResultsCallable.seekTestResults(TestResultsCallable.java:111) at hudson.plugins.testlink.result.TestResultsCallable.invoke(TestResultsCallable.java:153) at hudson.plugins.testlink.result.TestResultsCallable.invoke(TestResultsCallable.java:47) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1994) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) 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:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: java.lang.OutOfMemoryError: Java heap space ERROR: An error occured while trying to retrieve the test results: Unkown internal error. Please, open an issue in Jenkins JIRA with the complete stack trace. If possible, try including the JUnit XML(s) too.. We recently started using the testlink plugin. I was evaluating it until last night when I applied it to our 'real' build system. The job that failed above had succeeded before. I also saw this fail with OutOfMemoryError when using this pattern for the JUnit XML files: **/TEST*Test.xml . Changing the pattern to **/Test*TestSuites.xml seemed to get us over the failure, but apparently not. I have attached the JUnit XML files. After seeing suggestions for increasing the max memory for slaves when an OutOfMemory error occurs I set the slave memory setting to -Xmx1024m. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11777) Jenkins configuration page does not work properly when Jenkins Slave SetupPlugin enabled
[ https://issues.jenkins-ci.org/browse/JENKINS-11777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm reassigned JENKINS-11777: Assignee: Oleksandr Popov (was: Frederik Fromm) Do you mind to check this and to close this issue if it working. Thanks. Jenkins configuration page does not work properly when Jenkins Slave SetupPlugin enabled Key: JENKINS-11777 URL: https://issues.jenkins-ci.org/browse/JENKINS-11777 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Reporter: Oleksandr Popov Assignee: Oleksandr Popov Attachments: issue.JPG Jenkins configuration page does not work properly when Jenkins Slave SetupPlugin enabled. This issue appeared since I use Jenkins 1.437 and it not fixed until now (v. 1.437). See screenshot. In such way Jenkins got stacked if this plugin enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11618) Prototype 1.7 is missing the instance 'toJSON' method
[
https://issues.jenkins-ci.org/browse/JENKINS-11618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159992#comment-159992
]
OHTAKE Tomohiro commented on JENKINS-11618:
---
FYI:
As 1.454 was released to fix too restrictive HTML sanitization rules,
1.455 will be the first version which bundles prototype 1.7.
Prototype 1.7 is missing the instance 'toJSON' method
-
Key: JENKINS-11618
URL: https://issues.jenkins-ci.org/browse/JENKINS-11618
Project: Jenkins
Issue Type: Bug
Components: html5-notifier
Affects Versions: current
Environment: n/a
Reporter: Dan Savilonis
Assignee: jieryn
Priority: Blocker
When the html5-notifier plugin is enabled, you cannot save a job with more
than one build step. To reproduce, install the plugin and add a new job with
two windows batch file or shell script build steps. If only one is created,
it will save, but if two are created, you will see an error like the
following:
Failed to parse form data. Please report this problem as a bug
JSON={:,builder:\[{\command\:\bar\,\stapler-class\:\hudson.tasks.Shell\,\kind\:\hudson.tasks.Shell\},
{\command\:\cd
foo\,\stapler-class\:\hudson.tasks.Shell\,\kind\:\hudson.tasks.Shell\}]\,description:,hasSlaveAffinity:{assignedLabelString:windowsexpander},name:debug_job2,properties:{hudson-model-ParametersDefinitionProperty:{},hudson-plugins-batch_task-BatchTaskProperty:{},stapler-class-bag:true},scm:{value:3}}
net.sf.json.JSONException: A JSONArray text must start with '[' at character
1 of [{command:cd
bar,stapler-class:hudson.tasks.Shell,kind:hudson.tasks.Shell},
{command:cd
foo,stapler-class:hudson.tasks.Shell,kind:hudson.tasks.Shell}]
at net.sf.json.util.JSONTokener.syntaxError(JSONTokener.java:512)
at net.sf.json.JSONArray._fromJSONTokener(JSONArray.java:903)
at net.sf.json.JSONArray._fromString(JSONArray.java:983)
at net.sf.json.JSONArray.fromObject(JSONArray.java:141)
at net.sf.json.JSONArray.fromObject(JSONArray.java:120)
at
hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:863)
at
hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:853)
at hudson.util.DescribableList.rebuildHetero(DescribableList.java:185)
at hudson.model.Project.submit(Project.java:197)
at hudson.model.Job.doConfigSubmit(Job.java:966)
at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:643)
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:616)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:104)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:646)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:234)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:646)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:249)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:335)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
[JIRA] (JENKINS-11837) Single job on multi slaves
[ https://issues.jenkins-ci.org/browse/JENKINS-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-11837 stopped by Frederik Fromm. Single job on multi slaves -- Key: JENKINS-11837 URL: https://issues.jenkins-ci.org/browse/JENKINS-11837 Project: Jenkins Issue Type: New Feature Components: slave-setup Affects Versions: current Reporter: Gangadharan Ramakrishnan Assignee: Frederik Fromm Attachments: multislave.jpg Hi Team, I know there is an option to configure a single job to run on multiple slave nodes. But i was just wondering if there is something like, when i click on a job it shud give me options to run the job against any number of slave agents.. something like in the attached jpg.. it would be great if we have an option to select which slave we need to run the job against -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11837) Single job on multi slaves
[ https://issues.jenkins-ci.org/browse/JENKINS-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm reassigned JENKINS-11837: Assignee: Gangadharan Ramakrishnan (was: Frederik Fromm) Could you please have a look at the comments. If you agree, you are welcome to move or close this issue. Thanks. Single job on multi slaves -- Key: JENKINS-11837 URL: https://issues.jenkins-ci.org/browse/JENKINS-11837 Project: Jenkins Issue Type: New Feature Components: slave-setup Affects Versions: current Reporter: Gangadharan Ramakrishnan Assignee: Gangadharan Ramakrishnan Attachments: multislave.jpg Hi Team, I know there is an option to configure a single job to run on multiple slave nodes. But i was just wondering if there is something like, when i click on a job it shud give me options to run the job against any number of slave agents.. something like in the attached jpg.. it would be great if we have an option to select which slave we need to run the job against -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12667) No possibility to specify Workspace Root Directory for Slave node
[ https://issues.jenkins-ci.org/browse/JENKINS-12667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159997#comment-159997 ] Frederik Fromm commented on JENKINS-12667: -- Hmmm... in the node configuration page computer/node name/configure there is a field Remote FS root where you define the workspace root directory on a slave. Is this what you are looking for? The slave setup plugin uses the Remote FS root directory to copy the files to and from where the script can be executed. No possibility to specify Workspace Root Directory for Slave node --- Key: JENKINS-12667 URL: https://issues.jenkins-ci.org/browse/JENKINS-12667 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Environment: Jenkins 1.452 Reporter: Oleksandr Popov Assignee: Kohsuke Kawaguchi Priority: Critical There is no possibility to specify Workspace Root Directory for Slave node as it is for Master node. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160001#comment-160001
]
Christopher Orr commented on JENKINS-12120:
---
Did this happen to an existing emulator, or was it created during the build
where you saw this error?
Probably you can delete the emulator and try again.
Emulator startup shouldn't fail when .ini is missing
Key: JENKINS-12120
URL: https://issues.jenkins-ci.org/browse/JENKINS-12120
Project: Jenkins
Issue Type: Bug
Components: android-emulator
Reporter: Jørgen Tjernø
Assignee: Christopher Orr
{noformat}
17:14:47 [android] Starting Android emulator
17:14:47 [android] Erasing existing emulator data...
17:14:47 $ /Users/buildserver/Android/sdk/tools/emulator -no-boot-anim
-ports 58108,58109 -prop persist.sys.language=en -prop persist.sys.country=US
-avd hudson_en-US_160_841x490_android-7 -no-snapshot-load -no-snapshot-save
-wipe-data -no-window -no-snapshot-update-time
17:14:50 PANIC: Could not open:
/tmp/jenkins-root-ssh/workspace/client_android_staging_test/.android/avd/hudson_en-US_160_841x490_android-7.ini*
daemon not running. starting it now on port 58110 *
17:14:50 * daemon started successfully *
17:15:52 [android] Emulator did not appear to start; giving up
{noformat}
I'm guessing the code tests for a .avd but not a .ini - I don't know how my
machine managed to end up with only a .avd (I checked, and it existed), but
in that scenario, the plugin should probably recreate the emulator (android
create avd -f).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12866) Unable to connect to jenkins slave running on ARM platform
[ https://issues.jenkins-ci.org/browse/JENKINS-12866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160002#comment-160002 ] Frederik Fromm commented on JENKINS-12866: -- Is this really related to the slave setup plugin? Which version did you use? I am missing the line Copying setup script files in your log that should appear after the line Copied classworlds.jar and before the line Slave successfully connected and online. Is this issue still a problem? If not, please close this issue. Thanks. Unable to connect to jenkins slave running on ARM platform -- Key: JENKINS-12866 URL: https://issues.jenkins-ci.org/browse/JENKINS-12866 Project: Jenkins Issue Type: Bug Components: slave-setup Environment: pandaboard, ARM platform Reporter: Eric Huang Assignee: Kohsuke Kawaguchi I am trying to setup a jenkins slave that is running on a pandaboard. I have Ubuntu 11.10 oneiric installed, and I am using OpenJDK Runtime Environment (IcedTea6 1.11pre). I am getting a Invalid encoded sequence encountered error when attempting to connect to the slave via ssh: [02/22/12 16:45:41] [SSH] Opening SSH connection to panda-devboard:22. 6:45:47] [SSH] Authentication successful. [02/22/12 16:45:47] [SSH] The remote users environment is: BASH=/bin/bash BASHOPTS=cmdhist:extquote:force_fignore:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath BASH_ALIASES=() BASH_ARGC=() BASH_ARGV=() BASH_CMDS=() BASH_EXECUTION_STRING=set BASH_LINENO=() BASH_SOURCE=() BASH_VERSINFO=([0]=4 [1]=2 [2]=10 [3]=1 [4]=release [5]=arm-unknown-linux-gnueabi) BASH_VERSION='4.2.10(1)-release' DIRSTACK=() EUID=4086 GROUPS=() HOME=/home/release HOSTNAME=panda-devboard HOSTTYPE=arm IFS=$' \t\n' LANG=en_CA.UTF-8 LOGNAME=release MACHTYPE=arm-unknown-linux-gnueabi MAIL=/var/mail/release OPTERR=1 OPTIND=1 OSTYPE=linux-gnueabi PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games PIPESTATUS=([0]=0) PPID=10358 PS4='+ ' PWD=/home/release SHELL=/bin/bash SHELLOPTS=braceexpand:hashall:interactive-comments SHLVL=1 SSH_CLIENT='10.1.0.195 4050 22' SSH_CONNECTION='10.1.0.195 4050 10.1.124.85 22' TERM=dumb UID=4086 USER=release XDG_SESSION_COOKIE=5c9ceadb707acb8eae13745b0009-1329957946.802516-2119305671 _=']' [02/22/12 16:45:47] [SSH] Checking java version of java [02/22/12 16:45:48] [SSH] java -version returned 1.6.0_23. [02/22/12 16:45:48] [SSH] Starting sftp client. [02/22/12 16:45:48] [SSH] Copying latest slave.jar... [02/22/12 16:45:48] [SSH] Copied 257,564 bytes. [02/22/12 16:45:48] [SSH] Starting slave process: cd '/var/hudson' java -jar slave.jar -text Running in text mode ===[JENKINS REMOTING CAPACITY]==[HUDSON TRANSMISSION BEGINS]===channel started Slave.jar version: 2.12 This is a Unix slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Slave successfully connected and online [02/22/12 16:45:54] [SSH] Opening SSH connection to panda-devboard:22. ERROR: Connection terminated java.io.IOException: Invalid encoded sequence encountered: 6A 6D 6D 5F 19 EB 4C 7A 6A 2B C9 4B 1A at hudson.remoting.BinarySafeStream$1._read(BinarySafeStream.java:194) at hudson.remoting.BinarySafeStream$1.read(BinarySafeStream.java:80) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1127) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12866) Unable to connect to jenkins slave running on ARM platform
[ https://issues.jenkins-ci.org/browse/JENKINS-12866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm reassigned JENKINS-12866: Assignee: Eric Huang (was: Kohsuke Kawaguchi) Please have a look at the comments. If you agree you may close the issue. Thanks. Unable to connect to jenkins slave running on ARM platform -- Key: JENKINS-12866 URL: https://issues.jenkins-ci.org/browse/JENKINS-12866 Project: Jenkins Issue Type: Bug Components: slave-setup Environment: pandaboard, ARM platform Reporter: Eric Huang Assignee: Eric Huang I am trying to setup a jenkins slave that is running on a pandaboard. I have Ubuntu 11.10 oneiric installed, and I am using OpenJDK Runtime Environment (IcedTea6 1.11pre). I am getting a Invalid encoded sequence encountered error when attempting to connect to the slave via ssh: [02/22/12 16:45:41] [SSH] Opening SSH connection to panda-devboard:22. 6:45:47] [SSH] Authentication successful. [02/22/12 16:45:47] [SSH] The remote users environment is: BASH=/bin/bash BASHOPTS=cmdhist:extquote:force_fignore:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath BASH_ALIASES=() BASH_ARGC=() BASH_ARGV=() BASH_CMDS=() BASH_EXECUTION_STRING=set BASH_LINENO=() BASH_SOURCE=() BASH_VERSINFO=([0]=4 [1]=2 [2]=10 [3]=1 [4]=release [5]=arm-unknown-linux-gnueabi) BASH_VERSION='4.2.10(1)-release' DIRSTACK=() EUID=4086 GROUPS=() HOME=/home/release HOSTNAME=panda-devboard HOSTTYPE=arm IFS=$' \t\n' LANG=en_CA.UTF-8 LOGNAME=release MACHTYPE=arm-unknown-linux-gnueabi MAIL=/var/mail/release OPTERR=1 OPTIND=1 OSTYPE=linux-gnueabi PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games PIPESTATUS=([0]=0) PPID=10358 PS4='+ ' PWD=/home/release SHELL=/bin/bash SHELLOPTS=braceexpand:hashall:interactive-comments SHLVL=1 SSH_CLIENT='10.1.0.195 4050 22' SSH_CONNECTION='10.1.0.195 4050 10.1.124.85 22' TERM=dumb UID=4086 USER=release XDG_SESSION_COOKIE=5c9ceadb707acb8eae13745b0009-1329957946.802516-2119305671 _=']' [02/22/12 16:45:47] [SSH] Checking java version of java [02/22/12 16:45:48] [SSH] java -version returned 1.6.0_23. [02/22/12 16:45:48] [SSH] Starting sftp client. [02/22/12 16:45:48] [SSH] Copying latest slave.jar... [02/22/12 16:45:48] [SSH] Copied 257,564 bytes. [02/22/12 16:45:48] [SSH] Starting slave process: cd '/var/hudson' java -jar slave.jar -text Running in text mode ===[JENKINS REMOTING CAPACITY]==[HUDSON TRANSMISSION BEGINS]===channel started Slave.jar version: 2.12 This is a Unix slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Slave successfully connected and online [02/22/12 16:45:54] [SSH] Opening SSH connection to panda-devboard:22. ERROR: Connection terminated java.io.IOException: Invalid encoded sequence encountered: 6A 6D 6D 5F 19 EB 4C 7A 6A 2B C9 4B 1A at hudson.remoting.BinarySafeStream$1._read(BinarySafeStream.java:194) at hudson.remoting.BinarySafeStream$1.read(BinarySafeStream.java:80) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1127) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12660) Fail to start the windows service when trying to launch slave node
[
https://issues.jenkins-ci.org/browse/JENKINS-12660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frederik Fromm updated JENKINS-12660:
-
Component/s: master-slave
(was: slave-setup)
Fail to start the windows service when trying to launch slave node
--
Key: JENKINS-12660
URL: https://issues.jenkins-ci.org/browse/JENKINS-12660
Project: Jenkins
Issue Type: Bug
Components: master-slave
Affects Versions: current
Environment: Master : Redhat 5
Slave Node : Win7 x64
Reporter: Rico ZHANG
Assignee: Kohsuke Kawaguchi
We used to be able to launch the slave node successfully, but it did not work
since we upgraded the jenkins to latest version (1.449)
It doesn't dump any exception to the console, but I captured the output:
{noformat}
Connecting to 192.168.160.62
Checking if Java exists
java full version 1.7.0-b147
Installing the Jenkins slave service
Copying jenkins-slave.exe
Copying slave.jar
Copying jenkins-slave.xml
Registering the service
ERROR: Failed to create a service: Status Invalid Service Account
...
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12660) Fail to start the windows service when trying to launch slave node
[
https://issues.jenkins-ci.org/browse/JENKINS-12660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160004#comment-160004
]
Frederik Fromm commented on JENKINS-12660:
--
changed to master/slave component as it is not related to the slave-setup
plugin.
Fail to start the windows service when trying to launch slave node
--
Key: JENKINS-12660
URL: https://issues.jenkins-ci.org/browse/JENKINS-12660
Project: Jenkins
Issue Type: Bug
Components: master-slave
Affects Versions: current
Environment: Master : Redhat 5
Slave Node : Win7 x64
Reporter: Rico ZHANG
Assignee: Kohsuke Kawaguchi
We used to be able to launch the slave node successfully, but it did not work
since we upgraded the jenkins to latest version (1.449)
It doesn't dump any exception to the console, but I captured the output:
{noformat}
Connecting to 192.168.160.62
Checking if Java exists
java full version 1.7.0-b147
Installing the Jenkins slave service
Copying jenkins-slave.exe
Copying slave.jar
Copying jenkins-slave.xml
Registering the service
ERROR: Failed to create a service: Status Invalid Service Account
...
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12630) Solaris tar does not support gzip (z option)
[
https://issues.jenkins-ci.org/browse/JENKINS-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frederik Fromm reassigned JENKINS-12630:
Assignee: Floris Bruynooghe (was: Kohsuke Kawaguchi)
Is this issue still a problem? Is it really related to the slave-setup-plugin?
If not, please move it to the master-slave component or close this issue.
Thanks!
Solaris tar does not support gzip (z option)
Key: JENKINS-12630
URL: https://issues.jenkins-ci.org/browse/JENKINS-12630
Project: Jenkins
Issue Type: Bug
Components: slave-setup
Affects Versions: current
Environment: Solaris 10
Reporter: Floris Bruynooghe
Assignee: Floris Bruynooghe
Jenkins is trying to deploy a new JDK onto a slave and is using a
GNU-extension to tar which gunzips tarfiles on the fly:
Building remotely on despina in workspace /export/home/hudson/workspace/xunit
Installing JDK jdk-7-oth-JPR
Downloading JDK from
http://download.oracle.com/otn-pub/java/jdk/7/jdk-7-solaris-sparcv9.tar.gz
Downloading 12979380bytes
Installing /export/home/hudson/tools/JRE/jdk.sh
[JRE] $ tar xvzf /export/home/hudson/tools/JRE/jdk.sh
tar: z: unknown function modifier
Usage: tar {c|r|t|u|x}[BDeEFhilmnopPqTvw@[0-7]][bfk][X...] [blocksize]
[tarfile] [size] [exclude-file...] {file | -I include-file | -C directory
file}...
ERROR: Failed to install JDK. Exit code=1
Finished: FAILURE
The correct way to unpack this tarfile for Solaris (or any POSIX machine) is
gunzip -c /export/home/hudson/tools/JRE/jdk.sh | tar -xvf -
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10771) hudson.util.IOException2: remote file operation failed
[
https://issues.jenkins-ci.org/browse/JENKINS-10771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160006#comment-160006
]
jens persson commented on JENKINS-10771:
Getting the same exception.
Server Ubuntu, Jenkins various versions up until ver. 1.454
Client Ubuntu, running on EC2 provisioned with Amazon EC2 Plugin v 1.13 (will
update to 1.14 and report back if it solves the problem)
I also have one Windows and one AIX client that connect with webstart that do
not show the problem.
Before I started fiddling it presented it self only on one buildjob and then
always on the checkout of the same file in the repro (other buildjobs on the
same host contain the same file and worked without problems). I tried changing
the memory allocation by giving the slave-jvm various -Xmx flags which moved
the error to other files.
{code}
hudson.util.IOException2: remote file operation failed:
/mnt/workspace/7.70_Global_Linux_build at
hudson.remoting.Channel@46638f:i-6a654923
at hudson.FilePath.act(FilePath.java:784)
at hudson.FilePath.act(FilePath.java:770)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:735)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:677)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1195)
at
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468)
at hudson.model.Run.run(Run.java:1408)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Caused by: java.io.IOException: Remote call on i-6a654923 failed
at hudson.remoting.Channel.call(Channel.java:690)
at hudson.FilePath.act(FilePath.java:777)
... 10 more
Caused by: java.lang.OutOfMemoryError: Java heap space
at
com.sun.org.apache.xerces.internal.util.XMLStringBuffer.append(XMLStringBuffer.java:205)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.refresh(XMLDocumentScannerImpl.java:1522)
at
com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.invokeListeners(XMLEntityScanner.java:2070)
at
com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.peekChar(XMLEntityScanner.java:486)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2687)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:754)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:719)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:216)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:364)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:285)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:276)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:264)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:266)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1263)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:820)
at
org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:564)
at
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:401)
at
org.tmatesoft.svn.core.wc.SVNUpdateClient.handleExternalChange(SVNUpdateClient.java:1865)
at
org.tmatesoft.svn.core.wc.SVNUpdateClient.handleExternalItemChange(SVNUpdateClient.java:1725)
at
[JIRA] (JENKINS-8059) Subversion Plugin does break native svn command line authentication, credentials missing after rewriting auth cache file
[
https://issues.jenkins-ci.org/browse/JENKINS-8059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160007#comment-160007
]
Stanislav Kanev commented on JENKINS-8059:
--
I found more details:
1. even when you have empty svn externals file, the native credentials are
overwritten. Completely removing the file with svn propdel svn:externals .
solves the issue.
2. when I removed all auth files from ~/.subversion/auth/svn.simple/* and
cleaned up the workspace the jenkins build with/without externals didint failed
and was able to pick up the sources from the svn repo. So jenkins does not use
the native credentials at all.
So the usage of ~/.subversion/auth/svn.simple/* files should be removed at all
from the plugin.
Subversion Plugin does break native svn command line authentication,
credentials missing after rewriting auth cache file
Key: JENKINS-8059
URL: https://issues.jenkins-ci.org/browse/JENKINS-8059
Project: Jenkins
Issue Type: Bug
Components: subversion
Environment: Linux, Ubuntu Hardy and Jaunty, Solaris
Reporter: tkrah
Assignee: Kohsuke Kawaguchi
Priority: Blocker
Attachments: subversion.hpi
Hudson does rewrite the authentication file under
${user.home}/.subversion/auth/svn.simple/$file and does not insert
credentials stuff.
I am using a custom build which does use the command line client (in addition
to the normal svn usage of the hudson project) - so the credentials are
important to be in there. My custom project is broken every time hudson does
rewrite those authentication cache file from subversion.
Is it possible to configure hudson not to do this rewrite or to insert those
credentials when the rewrite does happen?
The only workaround found is to set the immutable bit (removing write
privileges is not enough) as root user to the file in question which hudson
is not able to workaround (which is expected here and good).
Project does build but the log grows with these exception trace:
Nov 10, 2010 10:54:47 AM hudson.scm.SubversionSCM$CheckOutTask invoke
INFO: Failed to estimate the remote time stamp
org.tmatesoft.svn.core.SVNException: svn: Cannot rename file
'/home/hudson/.subversion/auth/svn.simple/auth.d17e3535-2c01-0010-81b2-1f57b38e3f1e.tmp'
to
'/home/hudson/.subversion/auth/svn.simple/1755861b3f63d264955a25532195c4f8'
at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at
org.tmatesoft.svn.core.internal.wc.SVNFileUtil.rename(SVNFileUtil.java:552)
at
org.tmatesoft.svn.core.internal.wc.SVNWCProperties.setProperties(SVNWCProperties.java:352)
at
org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager$PersistentAuthenticationProvider.saveAuthentication(DefaultSVNAuthenticationManager.java:810)
at
org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.acknowledgeAuthentication(DefaultSVNAuthenticationManager.java:276)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:606)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:275)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:263)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:516)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:98)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1001)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.info(DAVRepository.java:724)
at
hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:698)
at
hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:596)
at hudson.FilePath.act(FilePath.java:753)
at hudson.FilePath.act(FilePath.java:735)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:589)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:537)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1119)
at
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1324)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:139)
Of cause it can not rename the file, the immutable bit is set and only the
root
[JIRA] (JENKINS-12425) Windows service install fails with file in use
[ https://issues.jenkins-ci.org/browse/JENKINS-12425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160008#comment-160008 ] Frederik Fromm commented on JENKINS-12425: -- moved to master-slave component Windows service install fails with file in use -- Key: JENKINS-12425 URL: https://issues.jenkins-ci.org/browse/JENKINS-12425 Project: Jenkins Issue Type: Bug Components: master-slave Affects Versions: current Environment: WindowsXP 32 bit. Reporter: Anthony Berent Assignee: Kohsuke Kawaguchi I want to install a slave service on a Windows machine. I start the slave using the launch button on the Web page. This works fine. I then select Rile/Install as Windows Service on the slave pop-up, and click OK. This results in a large stack trace (unfortunately not in a window with copy and paste) starting with: java.io.FileNotFoundException: c:\JenkinsTest\jenkins-slave.exe (The process cannot access the file because it is being used by another process) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12425) Windows service install fails with file in use
[ https://issues.jenkins-ci.org/browse/JENKINS-12425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm updated JENKINS-12425: - Component/s: master-slave (was: slave-setup) Windows service install fails with file in use -- Key: JENKINS-12425 URL: https://issues.jenkins-ci.org/browse/JENKINS-12425 Project: Jenkins Issue Type: Bug Components: master-slave Affects Versions: current Environment: WindowsXP 32 bit. Reporter: Anthony Berent Assignee: Kohsuke Kawaguchi I want to install a slave service on a Windows machine. I start the slave using the launch button on the Web page. This works fine. I then select Rile/Install as Windows Service on the slave pop-up, and click OK. This results in a large stack trace (unfortunately not in a window with copy and paste) starting with: java.io.FileNotFoundException: c:\JenkinsTest\jenkins-slave.exe (The process cannot access the file because it is being used by another process) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8059) Subversion Plugin does break native svn command line authentication, credentials missing after rewriting auth cache file
[
https://issues.jenkins-ci.org/browse/JENKINS-8059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160007#comment-160007
]
Stanislav Kanev edited comment on JENKINS-8059 at 3/8/12 11:50 AM:
---
I found more details:
1. even when you have empty svn externals property, the native credentials are
overwritten. Completely removing the property with svn propdel svn:externals .
solves the issue.
2. when I removed all auth files from ~/.subversion/auth/svn.simple/* and
cleaned up the workspace the jenkins build with/without externals didint failed
and was able to pick up the sources from the svn repo. So jenkins does not use
the native credentials at all.
So the usage of ~/.subversion/auth/svn.simple/* files should be removed at all
from the plugin.
I think that this issue is related to the svnkit.
was (Author: naninani):
I found more details:
1. even when you have empty svn externals file, the native credentials are
overwritten. Completely removing the file with svn propdel svn:externals .
solves the issue.
2. when I removed all auth files from ~/.subversion/auth/svn.simple/* and
cleaned up the workspace the jenkins build with/without externals didint failed
and was able to pick up the sources from the svn repo. So jenkins does not use
the native credentials at all.
So the usage of ~/.subversion/auth/svn.simple/* files should be removed at all
from the plugin.
Subversion Plugin does break native svn command line authentication,
credentials missing after rewriting auth cache file
Key: JENKINS-8059
URL: https://issues.jenkins-ci.org/browse/JENKINS-8059
Project: Jenkins
Issue Type: Bug
Components: subversion
Environment: Linux, Ubuntu Hardy and Jaunty, Solaris
Reporter: tkrah
Assignee: Kohsuke Kawaguchi
Priority: Blocker
Attachments: subversion.hpi
Hudson does rewrite the authentication file under
${user.home}/.subversion/auth/svn.simple/$file and does not insert
credentials stuff.
I am using a custom build which does use the command line client (in addition
to the normal svn usage of the hudson project) - so the credentials are
important to be in there. My custom project is broken every time hudson does
rewrite those authentication cache file from subversion.
Is it possible to configure hudson not to do this rewrite or to insert those
credentials when the rewrite does happen?
The only workaround found is to set the immutable bit (removing write
privileges is not enough) as root user to the file in question which hudson
is not able to workaround (which is expected here and good).
Project does build but the log grows with these exception trace:
Nov 10, 2010 10:54:47 AM hudson.scm.SubversionSCM$CheckOutTask invoke
INFO: Failed to estimate the remote time stamp
org.tmatesoft.svn.core.SVNException: svn: Cannot rename file
'/home/hudson/.subversion/auth/svn.simple/auth.d17e3535-2c01-0010-81b2-1f57b38e3f1e.tmp'
to
'/home/hudson/.subversion/auth/svn.simple/1755861b3f63d264955a25532195c4f8'
at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at
org.tmatesoft.svn.core.internal.wc.SVNFileUtil.rename(SVNFileUtil.java:552)
at
org.tmatesoft.svn.core.internal.wc.SVNWCProperties.setProperties(SVNWCProperties.java:352)
at
org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager$PersistentAuthenticationProvider.saveAuthentication(DefaultSVNAuthenticationManager.java:810)
at
org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.acknowledgeAuthentication(DefaultSVNAuthenticationManager.java:276)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:606)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:275)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:263)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:516)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:98)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1001)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.info(DAVRepository.java:724)
at
hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:698)
at
hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:596)
at hudson.FilePath.act(FilePath.java:753)
at hudson.FilePath.act(FilePath.java:735)
at
[JIRA] (JENKINS-11149) JNLP slave fails to connect if Anonymous has not permission READ
[ https://issues.jenkins-ci.org/browse/JENKINS-11149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm updated JENKINS-11149: - Component/s: master-slave (was: slave-setup) JNLP slave fails to connect if Anonymous has not permission READ Key: JENKINS-11149 URL: https://issues.jenkins-ci.org/browse/JENKINS-11149 Project: Jenkins Issue Type: Bug Components: master-slave Affects Versions: current Reporter: Matthias Vach Assignee: Kohsuke Kawaguchi Hi all, I do face a problem with JNLP based windows slaves in combination with restricted permissions of Anonymous. If user Anonymous doesn't has READ permission granted, the JNLP slave (converted to a windows service) fails to connect to the master. The jenkins-slave.xml contains arguments-Xrs -jar %BASE%\slave.jar -jnlpUrl https://xxx:8443/hudson/computer/xxx/slave-agent.jnlp -jnlpCredentials abcd:efgh -auth abcd:efgh/arguments The tomcat-users.xml contains tomcat-users role rolename=admin/ role rolename=manager/ user username=abcd password=efgh roles=admin,manager/ /tomcat-users The jenkins-slave.err.log contains Failing to obtain https://xxx:8443/hudson/computer/xxx/slave-agent.jnlp java.io.IOException: Failed to load https://xxx:8443/hudson/computer/xxx/slave-agent.jnlp: 500 Internal Server Error at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:228) at hudson.remoting.Launcher.run(Launcher.java:190) at hudson.remoting.Launcher.main(Launcher.java:166) Waiting 10 seconds before retry The tomcat's localhost.2011-xx-xx.log contains SEVERE: Servlet.service() for servlet Stapler threw exception hudson.security.AccessDeniedException2: anonymous is missing the Read permission at hudson.security.ACL.checkPermission(ACL.java:53) at hudson.model.Node.checkPermission(Node.java:363) at hudson.model.Hudson.getTarget(Hudson.java:3538) ... The setup is as follows: OS: Windows 7 Tomcat: 6.0.33 Jenkins: 1.4.10 (also not working with 1.4.31) JDK: 1.6.27 Security Realm: Matrix based Security is enabled Authorization: Delegate to servlet container permissions of user abcd: Overall Read, Overall Administer permissions of user Anonymous: none -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11367) Enabling slave setup plugin on ubuntu breaks configuration page
[ https://issues.jenkins-ci.org/browse/JENKINS-11367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm resolved JENKINS-11367. -- Assignee: b2jrock Resolution: Fixed Fixed with version 1.2. Actual is version 1.4. Please check if its working now and close the issue. Thanks! Enabling slave setup plugin on ubuntu breaks configuration page --- Key: JENKINS-11367 URL: https://issues.jenkins-ci.org/browse/JENKINS-11367 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Environment: Ubuntu 11.10, installed 1.434 from apt-get. Reporter: b2jrock Assignee: b2jrock Priority: Minor When Active Directory plugin is enabled on Ubuntu, and the user clicks on Manage Jenkins - Configure, it results in the console staying at Loading, or a page with this at the top: Status Code: null Exception: Stacktrace: (none) Generated by Winstone Servlet Engine v0.9.10 at Mon Oct 17 03:29:59 CEST 2011 It may be necessary to have a windows slave configured to reproduce the error. Edit: similar issue occurs with the slave-setup plugin as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12029) Crash while attempting to install multiple slaves as a windows service on a single computer
[ https://issues.jenkins-ci.org/browse/JENKINS-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm updated JENKINS-12029: - Component/s: master-slave (was: slave-setup) Crash while attempting to install multiple slaves as a windows service on a single computer --- Key: JENKINS-12029 URL: https://issues.jenkins-ci.org/browse/JENKINS-12029 Project: Jenkins Issue Type: Bug Components: master-slave Affects Versions: current Environment: Windows 32bit Reporter: Salim Fadhley Assignee: Frederik Fromm Priority: Minor I can launch a slave using web-start and then install it as a windows service. After some manual configuration this service reliably starts up connects to the master node. For various reasons some of our more powerful servers are shared between teams which have their own jenkins master nodes. Previously (with Hudson) we ran multiple web-start clients (not as a service) which allowed for any number of slaves to run on one computer (providing they were configured with unique directories) Recently we were forced to switch to using a service - as a consequence we have noticed that it is no longer possible to install more than one Jenkins slave service on any single box. Steps to re-create: * Ensure that your slave hosting PC does NOT have any Jenkins slave services configured (use sc command to delete if needed) * Set up 2 nodes on Jenkins master, give each different directories * Launch the first node configure to run as a service. Verify that slave is running. * Launch the 2nd node configure to run as a service Result: * First slave installs OK, second slave will crash on service installation * The 2nd windows service will not be created Conclusion: * The existance of a previously installed Jenkins service will always cause any subsequent jenkins service installations to fail. How are we running Jenkins? - Tomcat 7 on a Windows 64bit host - Slaves are launched via Web-start then installed as a service. With which Java VM (Oracle, IBM etc.)? - Oracle, latest in 1.6 series, 64bit On which operating system? 32- or 64-bit? - Windows 2003 Server R2 64bit for server - Windows XP 32bit for slaves Did this error start occurring after an upgrade? - No -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12029) Crash while attempting to install multiple slaves as a windows service on a single computer
[ https://issues.jenkins-ci.org/browse/JENKINS-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm reassigned JENKINS-12029: Assignee: Kohsuke Kawaguchi (was: Frederik Fromm) Crash while attempting to install multiple slaves as a windows service on a single computer --- Key: JENKINS-12029 URL: https://issues.jenkins-ci.org/browse/JENKINS-12029 Project: Jenkins Issue Type: Bug Components: master-slave Affects Versions: current Environment: Windows 32bit Reporter: Salim Fadhley Assignee: Kohsuke Kawaguchi Priority: Minor I can launch a slave using web-start and then install it as a windows service. After some manual configuration this service reliably starts up connects to the master node. For various reasons some of our more powerful servers are shared between teams which have their own jenkins master nodes. Previously (with Hudson) we ran multiple web-start clients (not as a service) which allowed for any number of slaves to run on one computer (providing they were configured with unique directories) Recently we were forced to switch to using a service - as a consequence we have noticed that it is no longer possible to install more than one Jenkins slave service on any single box. Steps to re-create: * Ensure that your slave hosting PC does NOT have any Jenkins slave services configured (use sc command to delete if needed) * Set up 2 nodes on Jenkins master, give each different directories * Launch the first node configure to run as a service. Verify that slave is running. * Launch the 2nd node configure to run as a service Result: * First slave installs OK, second slave will crash on service installation * The 2nd windows service will not be created Conclusion: * The existance of a previously installed Jenkins service will always cause any subsequent jenkins service installations to fail. How are we running Jenkins? - Tomcat 7 on a Windows 64bit host - Slaves are launched via Web-start then installed as a service. With which Java VM (Oracle, IBM etc.)? - Oracle, latest in 1.6 series, 64bit On which operating system? 32- or 64-bit? - Windows 2003 Server R2 64bit for server - Windows XP 32bit for slaves Did this error start occurring after an upgrade? - No -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11608) Slave service fails to launch on same machine as master under a different account
[ https://issues.jenkins-ci.org/browse/JENKINS-11608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160012#comment-160012 ] Frederik Fromm commented on JENKINS-11608: -- moved to master-slave component Slave service fails to launch on same machine as master under a different account - Key: JENKINS-11608 URL: https://issues.jenkins-ci.org/browse/JENKINS-11608 Project: Jenkins Issue Type: Bug Components: master-slave Affects Versions: current Environment: Windows 2008 Server R2 x86_64 - Installed/running as a service - No additional VM parameters - java.runtime.name Java(TM) SE Runtime Environment - java.runtime.version1.6.0_23-b05 Reporter: alex parkinson Assignee: Kohsuke Kawaguchi Priority: Minor Getting a Windows detected your registry file is still in use by other applications or services exception under the following non-standard execution scenario. We're trying to run a slave (as a service) on the same machine as the master (as a service) under different accounts. The reason for this is that we're trying to use Jenkins in a Deployment Executor role in a Continuous Delivery scenario, whereby we are trying to run deployers as slave services with different deployment responsibilities/access rights. Note that running master and slave services on the same machine under the same account works fine. There is a registry contention issue. The event log entry follows: -- Log Name: Application Source: User Profile Service EventID: 1530 Level: Warning User: SYSTEM Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 14 user registry handles leaked from \Registry\User\S-1-5-21-2143357078-987198913-1287535205-37427: Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427 Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427 Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427 Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427 Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427 Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427\Software\Policies\Microsoft\SystemCertificates Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427\Software\Microsoft\Windows\CurrentVersion\Explorer Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427\Software\Microsoft\SystemCertificates\My Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427\Software\Microsoft\SystemCertificates\CA Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427\Software\Microsoft\SystemCertificates\Root Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427\Software\Microsoft\SystemCertificates\trust Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427\Software\Microsoft\SystemCertificates\SmartCardRoot Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key \REGISTRY\USER\S-1-5-21-2143357078-987198913-1287535205-37427\Software\Microsoft\SystemCertificates\TrustedPeople Process 3916 (\Device\HarddiskVolume2\hudson-slaves\PG_PRD_DeployerAgent\jenkins-slave.exe) has opened key
[JIRA] (JENKINS-12029) Crash while attempting to install multiple slaves as a windows service on a single computer
[ https://issues.jenkins-ci.org/browse/JENKINS-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160013#comment-160013 ] salimfadhley commented on JENKINS-12029: FYI, the work-around for this bug was to manually configure services. I made a Windows batch-file which set up file dependancies and then added the required objects to services.msc. It's not very satisfying but it was sufficient for my purposes. Crash while attempting to install multiple slaves as a windows service on a single computer --- Key: JENKINS-12029 URL: https://issues.jenkins-ci.org/browse/JENKINS-12029 Project: Jenkins Issue Type: Bug Components: master-slave Affects Versions: current Environment: Windows 32bit Reporter: Salim Fadhley Assignee: Kohsuke Kawaguchi Priority: Minor I can launch a slave using web-start and then install it as a windows service. After some manual configuration this service reliably starts up connects to the master node. For various reasons some of our more powerful servers are shared between teams which have their own jenkins master nodes. Previously (with Hudson) we ran multiple web-start clients (not as a service) which allowed for any number of slaves to run on one computer (providing they were configured with unique directories) Recently we were forced to switch to using a service - as a consequence we have noticed that it is no longer possible to install more than one Jenkins slave service on any single box. Steps to re-create: * Ensure that your slave hosting PC does NOT have any Jenkins slave services configured (use sc command to delete if needed) * Set up 2 nodes on Jenkins master, give each different directories * Launch the first node configure to run as a service. Verify that slave is running. * Launch the 2nd node configure to run as a service Result: * First slave installs OK, second slave will crash on service installation * The 2nd windows service will not be created Conclusion: * The existance of a previously installed Jenkins service will always cause any subsequent jenkins service installations to fail. How are we running Jenkins? - Tomcat 7 on a Windows 64bit host - Slaves are launched via Web-start then installed as a service. With which Java VM (Oracle, IBM etc.)? - Oracle, latest in 1.6 series, 64bit On which operating system? 32- or 64-bit? - Windows 2003 Server R2 64bit for server - Windows XP 32bit for slaves Did this error start occurring after an upgrade? - No -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin was unexpected at this time.' error
[
https://issues.jenkins-ci.org/browse/JENKINS-11992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160014#comment-160014
]
Frederik Fromm commented on JENKINS-11992:
--
moved to master-slave component
Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing '
\Java\jre6\bin was unexpected at this time.' error
Key: JENKINS-11992
URL: https://issues.jenkins-ci.org/browse/JENKINS-11992
Project: Jenkins
Issue Type: Bug
Components: master-slave
Affects Versions: current
Environment: Win7 x64
Reporter: Mark MacVicar
Assignee: Kohsuke Kawaguchi
Priority: Minor
Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing '
\Java\jre6\bin was unexpected at this time.' error
I had installed the x86 Java 6, Version 6 update 29, (build 1.6.0_29-b11),
which installs into C:\Program Files (x86)\Java\jre6. When I started the
jenkins client and ran a build I received ' \Java\jre6\bin was unexpected
at this time.' errors in the console any time a shell command was invoked on
the slave.
Upon investigation it appears that the Java runtime set to path to (as
reported by the Manage Jenkins -- Manage Nodes -- My Slave -- Systeminfo
page:
{panel}
C:\Program Files (x86)\Java\jre6\bin;...;C:\Program Files
(x86)\Java\jre6\bin
{panel}
Searching about on the internet I see several projects reporting issues about
unescaped parens being added to the path.
https://issues.apache.org/jira/browse/GERONIMO-5365
https://forums.oracle.com/forums/thread.jspa?threadID=2171702
I can work around this issue by using the x64 JRE on 64-bit OS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin was unexpected at this time.' error
[
https://issues.jenkins-ci.org/browse/JENKINS-11992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frederik Fromm updated JENKINS-11992:
-
Component/s: master-slave
(was: slave-setup)
Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing '
\Java\jre6\bin was unexpected at this time.' error
Key: JENKINS-11992
URL: https://issues.jenkins-ci.org/browse/JENKINS-11992
Project: Jenkins
Issue Type: Bug
Components: master-slave
Affects Versions: current
Environment: Win7 x64
Reporter: Mark MacVicar
Assignee: Kohsuke Kawaguchi
Priority: Minor
Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing '
\Java\jre6\bin was unexpected at this time.' error
I had installed the x86 Java 6, Version 6 update 29, (build 1.6.0_29-b11),
which installs into C:\Program Files (x86)\Java\jre6. When I started the
jenkins client and ran a build I received ' \Java\jre6\bin was unexpected
at this time.' errors in the console any time a shell command was invoked on
the slave.
Upon investigation it appears that the Java runtime set to path to (as
reported by the Manage Jenkins -- Manage Nodes -- My Slave -- Systeminfo
page:
{panel}
C:\Program Files (x86)\Java\jre6\bin;...;C:\Program Files
(x86)\Java\jre6\bin
{panel}
Searching about on the internet I see several projects reporting issues about
unescaped parens being added to the path.
https://issues.apache.org/jira/browse/GERONIMO-5365
https://forums.oracle.com/forums/thread.jspa?threadID=2171702
I can work around this issue by using the x64 JRE on 64-bit OS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-4100) Add the job description to the email message body.
[ https://issues.jenkins-ci.org/browse/JENKINS-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-4100 started by Slide-O-Mix. Add the job description to the email message body. -- Key: JENKINS-4100 URL: https://issues.jenkins-ci.org/browse/JENKINS-4100 Project: Jenkins Issue Type: Improvement Components: email-ext Affects Versions: current Environment: Platform: All, OS: All Reporter: bhayward Assignee: Slide-O-Mix We have this cool ability to add a job description to a job. It would be nice if that were included in the hudson is back to normal or job failed emails. Just for convenience, I know the link is already in there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11895) Email-ext plugin: Should support BUILD_ID
[ https://issues.jenkins-ci.org/browse/JENKINS-11895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-11895 started by Slide-O-Mix. Email-ext plugin: Should support BUILD_ID - Key: JENKINS-11895 URL: https://issues.jenkins-ci.org/browse/JENKINS-11895 Project: Jenkins Issue Type: Improvement Components: email-ext Reporter: jwgrenning Assignee: Slide-O-Mix Priority: Minor I create a artifact using the BUILD_ID for part of the name. I need to be able to email that once it is created. Right now the BUILD_ID is not expanded. thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13020) DRY kills job publisher when out of memory - java.lang.OutOfMemoryError: Java heap space
Greg Moncreaff created JENKINS-13020: Summary: DRY kills job publisher when out of memory - java.lang.OutOfMemoryError: Java heap space Key: JENKINS-13020 URL: https://issues.jenkins-ci.org/browse/JENKINS-13020 Project: Jenkins Issue Type: Bug Components: dry Affects Versions: current Environment: rhel 5.5, no limits (xmx on heap growth when starting jenkins), machine has 12 GB of RAM, typically see Jenkins java process using about 4 GB (3.6 Virtual, 1.4 Resident) Reporter: Greg Moncreaff Assignee: Ulli Hafner Is it possible to catch this flag build as unstable but not automatically failed, (or use the error during processing result) and abort only DRY publisher but still let the other publishers have a chance? a few web searches indicate that reuse of objects instead of allocating new and letting GC reclaim might be something to consider? 11:56:51 [DRY] Collecting duplicate code analysis files... 12:02:34 FATAL: Java heap space 12:02:34 java.lang.OutOfMemoryError: Java heap space 12:02:34at java.util.Arrays.copyOf(Arrays.java:2882) 12:02:34at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100) 12:02:34at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:515) 12:02:34at java.lang.StringBuilder.append(StringBuilder.java:189) 12:02:34at org.apache.commons.digester3.Digester.characters(Digester.java:988) 12:02:34at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.characters(AbstractSAXParser.java:538) 12:02:34at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:464) 12:02:34at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) 12:02:34at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) 12:02:34at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) 12:02:34at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) 12:02:34at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) 12:02:34at org.apache.commons.digester3.Digester.parse(Digester.java:1642) 12:02:34at org.apache.commons.digester3.Digester.parse(Digester.java:1701) 12:02:34at hudson.plugins.dry.parser.cpd.CpdParser.parse(CpdParser.java:86) 12:02:34at hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:73) 12:02:34at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:358) 12:02:34at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:317) 12:02:34at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:266) 12:02:34at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) 12:02:34at hudson.FilePath.act(FilePath.java:788) 12:02:34at hudson.FilePath.act(FilePath.java:770) 12:02:34at hudson.plugins.dry.DryPublisher.perform(DryPublisher.java:171) 12:02:34at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:338) 12:02:34at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 12:02:34at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:700) 12:02:34at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:675) 12:02:34at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:653) 12:02:34at hudson.model.Build$RunnerImpl.post2(Build.java:162) 12:02:34at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:622) 12:02:34at hudson.model.Run.run(Run.java:1434) 12:02:34at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11522) Workspace has a .git repository, but it appears to be corrupt. No Git repository yet, an initial checkout is required
[ https://issues.jenkins-ci.org/browse/JENKINS-11522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160016#comment-160016 ] Asaf M commented on JENKINS-11522: -- All the referenced duplicate bugs are all marked Resolved: Duplicate as well, so where is the bug that is actually worked on? Workspace has a .git repository, but it appears to be corrupt. No Git repository yet, an initial checkout is required - Key: JENKINS-11522 URL: https://issues.jenkins-ci.org/browse/JENKINS-11522 Project: Jenkins Issue Type: Bug Environment: Jenkins-Git plugin, Windows Server 2003 SP2, IIS v6.0 Reporter: Murali Srinivasan I have configured Jenkins to generate builds for the GIT repository in Windows Server. My Jenkins job is configured to Poll the repository continuously and trigger build if any change is found in the repository. The issue is Jenkins job triggers automatically even there is no change in the repository. When I checked the polling log it printed the following message Started on Oct 27, 2011 9:45:54 AM Using strategy: Default [poll] Last Build : #289 [poll] Last Built Revision: Revision 7fd9fb8139dd0c449a0382b505c7857c8634f33f (origin/Prod_dev) Workspace has a .git repository, but it appears to be corrupt. No Git repository yet, an initial checkout is required Done. Took 11 sec Changes found -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11895) Email-ext plugin: Should support BUILD_ID
[ https://issues.jenkins-ci.org/browse/JENKINS-11895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slide-O-Mix resolved JENKINS-11895. --- Resolution: Fixed Fixed in b19a265 Email-ext plugin: Should support BUILD_ID - Key: JENKINS-11895 URL: https://issues.jenkins-ci.org/browse/JENKINS-11895 Project: Jenkins Issue Type: Improvement Components: email-ext Reporter: jwgrenning Assignee: Slide-O-Mix Priority: Minor I create a artifact using the BUILD_ID for part of the name. I need to be able to email that once it is created. Right now the BUILD_ID is not expanded. thanks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-4100) Add the job description to the email message body.
[ https://issues.jenkins-ci.org/browse/JENKINS-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160018#comment-160018 ] SCM/JIRA link daemon commented on JENKINS-4100: --- Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/EmailExtensionPlugin.java src/main/java/hudson/plugins/emailext/plugins/content/BuildIdContent.java src/main/java/hudson/plugins/emailext/plugins/content/JobDescriptionContent.java http://jenkins-ci.org/commit/email-ext-plugin/b19a26597d190c934ce96572c689124cb451cd34 Log: Fix JENKINS-4100 and JENKINS-11895 - Added BUILD_ID token and JOB_DESCRIPTION token Add the job description to the email message body. -- Key: JENKINS-4100 URL: https://issues.jenkins-ci.org/browse/JENKINS-4100 Project: Jenkins Issue Type: Improvement Components: email-ext Affects Versions: current Environment: Platform: All, OS: All Reporter: bhayward Assignee: Slide-O-Mix We have this cool ability to add a job description to a job. It would be nice if that were included in the hudson is back to normal or job failed emails. Just for convenience, I know the link is already in there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-4100) Add the job description to the email message body.
[ https://issues.jenkins-ci.org/browse/JENKINS-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slide-O-Mix resolved JENKINS-4100. -- Resolution: Fixed Fixed in b19a265 Add the job description to the email message body. -- Key: JENKINS-4100 URL: https://issues.jenkins-ci.org/browse/JENKINS-4100 Project: Jenkins Issue Type: Improvement Components: email-ext Affects Versions: current Environment: Platform: All, OS: All Reporter: bhayward Assignee: Slide-O-Mix We have this cool ability to add a job description to a job. It would be nice if that were included in the hudson is back to normal or job failed emails. Just for convenience, I know the link is already in there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11367) Enabling slave setup plugin on ubuntu breaks configuration page
[ https://issues.jenkins-ci.org/browse/JENKINS-11367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160021#comment-160021 ] b2jrock commented on JENKINS-11367: --- That seems to have resolved it here. I was just acting as proxy for another user that brought this up on IRC. Looks good, thanks! Enabling slave setup plugin on ubuntu breaks configuration page --- Key: JENKINS-11367 URL: https://issues.jenkins-ci.org/browse/JENKINS-11367 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Environment: Ubuntu 11.10, installed 1.434 from apt-get. Reporter: b2jrock Assignee: b2jrock Priority: Minor When Active Directory plugin is enabled on Ubuntu, and the user clicks on Manage Jenkins - Configure, it results in the console staying at Loading, or a page with this at the top: Status Code: null Exception: Stacktrace: (none) Generated by Winstone Servlet Engine v0.9.10 at Mon Oct 17 03:29:59 CEST 2011 It may be necessary to have a windows slave configured to reproduce the error. Edit: similar issue occurs with the slave-setup plugin as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12861) klocwork - update to recognize 9.5.x xml schema
[
https://issues.jenkins-ci.org/browse/JENKINS-12861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160022#comment-160022
]
Greg Moncreaff commented on JENKINS-12861:
--
I think yes?
klocwork - update to recognize 9.5.x xml schema
---
Key: JENKINS-12861
URL: https://issues.jenkins-ci.org/browse/JENKINS-12861
Project: Jenkins
Issue Type: Improvement
Components: klocwork
Affects Versions: current
Environment: rhel 5.5
Reporter: Greg Moncreaff
Assignee: gbois
schema changed. current plugin can digest
errorList version=9.2.2
...
citingStatusAnalyze/citingStatusstateExisting/stateseverityError/severityseveritylevel3/severityleveldisplayAsError/displayAsdateOriginated1327694645000/dateOriginated
but new owner field appears in 9.5
errorList version=9.5.2
citingStatusAnalyze/citingStatusstateNew/stateownerunowned/ownerseverityCritical/severityseveritylevel1/severityleveldisplayAsError/displayAs
that causes publisher to be less than graceful:
22:08:53 Processing 2 files with the pattern 'kw*.xml'.
22:08:53 Parsing has been canceled. XML Validation failed. See errors below :
22:08:53 At line 47 of
file:/view/mafi_int_kw/vobs/csci33/csc11/kw.xml:cvc-complex-type.2.4.a:
Invalid content was found starting with element 'owner'. One of
'{http://www.klocwork.com/inForce/report/1.0:severity,
http://www.klocwork.com/inForce/report/1.0:severitylevel,
http://www.klocwork.com/inForce/report/1.0:displayAs,
http://www.klocwork.com/inForce/report/1.0:dateOriginated,
http://www.klocwork.com/inForce/report/1.0:url,
http://www.klocwork.com/inForce/report/1.0:comment,
http://www.klocwork.com/inForce/report/1.0:history,
http://www.klocwork.com/inForce/report/1.0:lastCommitter,
http://www.klocwork.com/inForce/report/1.0:dateFixed,
http://www.klocwork.com/inForce/report/1.0:category,
http://www.klocwork.com/inForce/report/1.0:lastCommit}' is expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11367) Enabling slave setup plugin on ubuntu breaks configuration page
[ https://issues.jenkins-ci.org/browse/JENKINS-11367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm closed JENKINS-11367. Enabling slave setup plugin on ubuntu breaks configuration page --- Key: JENKINS-11367 URL: https://issues.jenkins-ci.org/browse/JENKINS-11367 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Environment: Ubuntu 11.10, installed 1.434 from apt-get. Reporter: b2jrock Assignee: b2jrock Priority: Minor When Active Directory plugin is enabled on Ubuntu, and the user clicks on Manage Jenkins - Configure, it results in the console staying at Loading, or a page with this at the top: Status Code: null Exception: Stacktrace: (none) Generated by Winstone Servlet Engine v0.9.10 at Mon Oct 17 03:29:59 CEST 2011 It may be necessary to have a windows slave configured to reproduce the error. Edit: similar issue occurs with the slave-setup plugin as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11522) Workspace has a .git repository, but it appears to be corrupt. No Git repository yet, an initial checkout is required
[ https://issues.jenkins-ci.org/browse/JENKINS-11522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160023#comment-160023 ] Murali Srinivasan commented on JENKINS-11522: - This is the one still open. https://issues.jenkins-ci.org/browse/JENKINS-11547 Workspace has a .git repository, but it appears to be corrupt. No Git repository yet, an initial checkout is required - Key: JENKINS-11522 URL: https://issues.jenkins-ci.org/browse/JENKINS-11522 Project: Jenkins Issue Type: Bug Environment: Jenkins-Git plugin, Windows Server 2003 SP2, IIS v6.0 Reporter: Murali Srinivasan I have configured Jenkins to generate builds for the GIT repository in Windows Server. My Jenkins job is configured to Poll the repository continuously and trigger build if any change is found in the repository. The issue is Jenkins job triggers automatically even there is no change in the repository. When I checked the polling log it printed the following message Started on Oct 27, 2011 9:45:54 AM Using strategy: Default [poll] Last Build : #289 [poll] Last Built Revision: Revision 7fd9fb8139dd0c449a0382b505c7857c8634f33f (origin/Prod_dev) Workspace has a .git repository, but it appears to be corrupt. No Git repository yet, an initial checkout is required Done. Took 11 sec Changes found -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11777) Jenkins configuration page does not work properly when Jenkins Slave SetupPlugin enabled
[ https://issues.jenkins-ci.org/browse/JENKINS-11777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm closed JENKINS-11777. Jenkins configuration page does not work properly when Jenkins Slave SetupPlugin enabled Key: JENKINS-11777 URL: https://issues.jenkins-ci.org/browse/JENKINS-11777 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Reporter: Oleksandr Popov Assignee: Oleksandr Popov Attachments: issue.JPG Jenkins configuration page does not work properly when Jenkins Slave SetupPlugin enabled. This issue appeared since I use Jenkins 1.437 and it not fixed until now (v. 1.437). See screenshot. In such way Jenkins got stacked if this plugin enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11053) Configure System page errors out with stacktrace after slave-setup module is installed
[ https://issues.jenkins-ci.org/browse/JENKINS-11053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm closed JENKINS-11053. Configure System page errors out with stacktrace after slave-setup module is installed Key: JENKINS-11053 URL: https://issues.jenkins-ci.org/browse/JENKINS-11053 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Environment: Linux, Jenkins ver. 1.430 Windows 1.445 Reporter: Gavin Mogan Assignee: Kohsuke Kawaguchi Priority: Blocker Configure System page stops just after Maven Maven installations With a stacktrace (in the log) [Winstone 2011/09/19 11:08:24] - Untrapped Error in Servlet javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/war/WEB-INF/lib/jenkins-core-1.430.jar!/jenkins/model/Jenkins/configure.jelly:58:84: st:include No page found 'config.jelly' for class org.jenkinsci.plugins.slave_setup.SetupConfig at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:100) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:646) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) at org.kohsuke.stapler.Stapler.service(Stapler.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:249) at winstone.RequestDispatcher.forward(RequestDispatcher.java:335) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:195) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:195) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:195) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:195) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368) at
[JIRA] (JENKINS-11750) Jenkins Slave Setup Plugin crashes Jenkins Configure System
[ https://issues.jenkins-ci.org/browse/JENKINS-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederik Fromm closed JENKINS-11750. Jenkins Slave Setup Plugin crashes Jenkins Configure System -- Key: JENKINS-11750 URL: https://issues.jenkins-ci.org/browse/JENKINS-11750 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Environment: Jenkins ver 1.439 Slave-setup plugin ver.1.0 Reporter: Greg Swiec Assignee: Kohsuke Kawaguchi Labels: plugin Attachments: jenkins_bug.jpg, jenkins_bug2.jpg Steps to reproduce: 1. Install fresh jenkins 2. Install Slave Setup plugin using jenkins 3. Go to Manage Jenkins-Configure System 4. Configure system fails to fully showup with error message as attached. P.S. Beggining of console trace also attached -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160024#comment-160024
]
Christopher Orr commented on JENKINS-12120:
---
Sounds like a different bug.
Can you paste more of the console output somewhere; in a new bug if you're not
seeing the PANIC: Could not open ... .ini message?
Emulator startup shouldn't fail when .ini is missing
Key: JENKINS-12120
URL: https://issues.jenkins-ci.org/browse/JENKINS-12120
Project: Jenkins
Issue Type: Bug
Components: android-emulator
Reporter: Jørgen Tjernø
Assignee: Christopher Orr
{noformat}
17:14:47 [android] Starting Android emulator
17:14:47 [android] Erasing existing emulator data...
17:14:47 $ /Users/buildserver/Android/sdk/tools/emulator -no-boot-anim
-ports 58108,58109 -prop persist.sys.language=en -prop persist.sys.country=US
-avd hudson_en-US_160_841x490_android-7 -no-snapshot-load -no-snapshot-save
-wipe-data -no-window -no-snapshot-update-time
17:14:50 PANIC: Could not open:
/tmp/jenkins-root-ssh/workspace/client_android_staging_test/.android/avd/hudson_en-US_160_841x490_android-7.ini*
daemon not running. starting it now on port 58110 *
17:14:50 * daemon started successfully *
17:15:52 [android] Emulator did not appear to start; giving up
{noformat}
I'm guessing the code tests for a .avd but not a .ini - I don't know how my
machine managed to end up with only a .avd (I checked, and it existed), but
in that scenario, the plugin should probably recreate the emulator (android
create avd -f).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
[ https://issues.jenkins-ci.org/browse/JENKINS-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slide-O-Mix updated JENKINS-12421: -- Summary: Add pre-send step to email-ext that can modify the mail message object (was: Build failure emails are continually sent to all culprits even if one culprit has already claimed the build) Add pre-send step to email-ext that can modify the mail message object -- Key: JENKINS-12421 URL: https://issues.jenkins-ci.org/browse/JENKINS-12421 Project: Jenkins Issue Type: New Feature Components: claim, email-ext Affects Versions: current Environment: All Reporter: terryl westerhold Assignee: Slide-O-Mix Labels: claim, email-ext, feature, groovy, jenkins, plugin, script When the Email-Ext plugin is used in conjunction with the Claim plugin there is no way to configure a project's email options to only send to the one who has claimed it. This results in every person on a team receiving emails for a build they did not break, turning Jenkins emails into something annoying instead of something useful. For someone who knew the code this would be a pretty easy feature to add. And while this would be a good feature, I think a more elaborate solution that would allow Email-ext plugin users to access/modify all parts of the email message (including who the message is being sent to) would be more useful in the long run. Giving users access to all parts of the email message and the option to run a Groovy script after the email has been built, but before the email has been sent would satisfy this feature request and would make the Email-Ext plugin much more versatile. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
[ https://issues.jenkins-ci.org/browse/JENKINS-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12421 started by Slide-O-Mix. Add pre-send step to email-ext that can modify the mail message object -- Key: JENKINS-12421 URL: https://issues.jenkins-ci.org/browse/JENKINS-12421 Project: Jenkins Issue Type: New Feature Components: claim, email-ext Affects Versions: current Environment: All Reporter: terryl westerhold Assignee: Slide-O-Mix Labels: claim, email-ext, feature, groovy, jenkins, plugin, script When the Email-Ext plugin is used in conjunction with the Claim plugin there is no way to configure a project's email options to only send to the one who has claimed it. This results in every person on a team receiving emails for a build they did not break, turning Jenkins emails into something annoying instead of something useful. For someone who knew the code this would be a pretty easy feature to add. And while this would be a good feature, I think a more elaborate solution that would allow Email-ext plugin users to access/modify all parts of the email message (including who the message is being sent to) would be more useful in the long run. Giving users access to all parts of the email message and the option to run a Groovy script after the email has been built, but before the email has been sent would satisfy this feature request and would make the Email-Ext plugin much more versatile. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12962) Workspace Cleanup Plugin does not play nicely with the Copy To Slave plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160025#comment-160025 ] Thomas Fields commented on JENKINS-12962: - Hi, Were you able to repro the issue? Regards, Tom. Workspace Cleanup Plugin does not play nicely with the Copy To Slave plugin --- Key: JENKINS-12962 URL: https://issues.jenkins-ci.org/browse/JENKINS-12962 Project: Jenkins Issue Type: Bug Components: ws-cleanup Affects Versions: current Environment: Jenkins 1.452, Win7 Reporter: Thomas Fields Assignee: vjuranek Hi there, The Workspace Cleanup Plugin does not play nicely with the Copy To Slave plugin. Here's a snippet from my console output for my build: 14:33:23 Deleting project workspace... done 14:33:23 14:33:23 [copy-to-slave] Copying 'Engine/Lib/**/*.lib, Engine/Lib/**/*.pdb, Engine/Lib/**/*.a', excluding nothing, from 'file:/c:/JCI/workspace/Expat-Live/CONFIG/Debug/TARGET/GCC/VSVERSION/2008' on 'hudson.slaves.DumbSlave@720397f7' to 'file:/C:/JCI/current_build/Expat-Live/CL167206' on the master. Note how the workspace is deleted before the copy step begins. Can this be fixed please? I assume deleting a workspace is something you'd always want to do last. I'd be happy to test any fixes. Regards, Tom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160026#comment-160026
]
francisdb commented on JENKINS-12120:
-
Logs look similar, nothing mentioned about creating the avd failing, and the
command used is not logged, otherwise I could try it manually.
Checking out Revision f8d74574069d0aac99890ca930a166c948729f6b (origin/HEAD,
origin/master)
Warning : There are multiple branch changesets here
$ /opt/android-sdk-linux/tools/android list target
[android] Using Android SDK: /opt/android-sdk-linux
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd
$ /opt/android-sdk-linux/platform-tools/adb start-server
[android] Starting Android emulator
$ /opt/android-sdk-linux/tools/emulator -no-boot-anim -ports 55292,32849 -prop
persist.sys.language=en -prop persist.sys.country=US -avd
hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7 -no-snapshot-load
-no-snapshot-save -no-window -logcat *:d
PANIC: Could not open:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.ini*
daemon not running. starting it now on port 33012 *
* daemon started successfully *
[android] Emulator did not appear to start; giving up
$ /opt/android-sdk-linux/platform-tools/adb disconnect localhost:32849
[android] Stopping Android emulator
$ /opt/android-sdk-linux/platform-tools/adb kill-server
Recording test results
No test report files were found. Configuration error?
Emma: looking for coverage reports in the provided path:
**/coverage/coverage*.xml
Finished: NOT_BUILT
Emulator startup shouldn't fail when .ini is missing
Key: JENKINS-12120
URL: https://issues.jenkins-ci.org/browse/JENKINS-12120
Project: Jenkins
Issue Type: Bug
Components: android-emulator
Reporter: Jørgen Tjernø
Assignee: Christopher Orr
{noformat}
17:14:47 [android] Starting Android emulator
17:14:47 [android] Erasing existing emulator data...
17:14:47 $ /Users/buildserver/Android/sdk/tools/emulator -no-boot-anim
-ports 58108,58109 -prop persist.sys.language=en -prop persist.sys.country=US
-avd hudson_en-US_160_841x490_android-7 -no-snapshot-load -no-snapshot-save
-wipe-data -no-window -no-snapshot-update-time
17:14:50 PANIC: Could not open:
/tmp/jenkins-root-ssh/workspace/client_android_staging_test/.android/avd/hudson_en-US_160_841x490_android-7.ini*
daemon not running. starting it now on port 58110 *
17:14:50 * daemon started successfully *
17:15:52 [android] Emulator did not appear to start; giving up
{noformat}
I'm guessing the code tests for a .avd but not a .ini - I don't know how my
machine managed to end up with only a .avd (I checked, and it existed), but
in that scenario, the plugin should probably recreate the emulator (android
create avd -f).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10583) List view shrinks to root when page refresh happens
[ https://issues.jenkins-ci.org/browse/JENKINS-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160027#comment-160027 ] Thomas Fields commented on JENKINS-10583: - This is still an issues in 1.454 and is really annoying. Please fix. List view shrinks to root when page refresh happens --- Key: JENKINS-10583 URL: https://issues.jenkins-ci.org/browse/JENKINS-10583 Project: Jenkins Issue Type: Bug Components: core Environment: Jenkins 1.424 Reporter: Thomas Fields Priority: Minor Hi, I'm using the Archive the artifacts option and the Files to archive box contains: tfields/Live/Engine/Tools/*.exe, tfields/Live/Engine/Tools/*.dll, tfields/Live/Engine/Tools/Plugins/*.dll So as you can that's archiving files in multiple directories. So when the build succeeds I get a Last Successful Artifacts link in my project page which has an expandable list view below it containing all my artifacts. This is all cool. The problem is if you have Auto refresh of the page enabled. If you expand the list, and the refresh occurs, the list will be shrunk back to the root. This is very annoying. Can it be fixed? I've tested in Chrome and Firefox - both exhibit the same behaviour. Regards, Tom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160026#comment-160026
]
francisdb edited comment on JENKINS-12120 at 3/8/12 2:59 PM:
-
Logs look similar, nothing mentioned about creating the avd failing, and the
command used is not logged, otherwise I could try it manually.
{code}
Checking out Revision f8d74574069d0aac99890ca930a166c948729f6b (origin/HEAD,
origin/master)
Warning : There are multiple branch changesets here
$ /opt/android-sdk-linux/tools/android list target
[android] Using Android SDK: /opt/android-sdk-linux
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd
$ /opt/android-sdk-linux/platform-tools/adb start-server
[android] Starting Android emulator
$ /opt/android-sdk-linux/tools/emulator -no-boot-anim -ports 55292,32849 -prop
persist.sys.language=en -prop persist.sys.country=US -avd
hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7 -no-snapshot-load
-no-snapshot-save -no-window -logcat *:d
PANIC: Could not open:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.ini*
daemon not running. starting it now on port 33012 *
* daemon started successfully *
[android] Emulator did not appear to start; giving up
$ /opt/android-sdk-linux/platform-tools/adb disconnect localhost:32849
[android] Stopping Android emulator
$ /opt/android-sdk-linux/platform-tools/adb kill-server
Recording test results
No test report files were found. Configuration error?
Emma: looking for coverage reports in the provided path:
**/coverage/coverage*.xml
Finished: NOT_BUILT
{code}
was (Author: francisdb):
Logs look similar, nothing mentioned about creating the avd failing, and
the command used is not logged, otherwise I could try it manually.
Checking out Revision f8d74574069d0aac99890ca930a166c948729f6b (origin/HEAD,
origin/master)
Warning : There are multiple branch changesets here
$ /opt/android-sdk-linux/tools/android list target
[android] Using Android SDK: /opt/android-sdk-linux
[android] Creating Android AVD:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd
$ /opt/android-sdk-linux/platform-tools/adb start-server
[android] Starting Android emulator
$ /opt/android-sdk-linux/tools/emulator -no-boot-anim -ports 55292,32849 -prop
persist.sys.language=en -prop persist.sys.country=US -avd
hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7 -no-snapshot-load
-no-snapshot-save -no-window -logcat *:d
PANIC: Could not open:
/var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.ini*
daemon not running. starting it now on port 33012 *
* daemon started successfully *
[android] Emulator did not appear to start; giving up
$ /opt/android-sdk-linux/platform-tools/adb disconnect localhost:32849
[android] Stopping Android emulator
$ /opt/android-sdk-linux/platform-tools/adb kill-server
Recording test results
No test report files were found. Configuration error?
Emma: looking for coverage reports in the provided path:
**/coverage/coverage*.xml
Finished: NOT_BUILT
Emulator startup shouldn't fail when .ini is missing
Key: JENKINS-12120
URL: https://issues.jenkins-ci.org/browse/JENKINS-12120
Project: Jenkins
Issue Type: Bug
Components: android-emulator
Reporter: Jørgen Tjernø
Assignee: Christopher Orr
{noformat}
17:14:47 [android] Starting Android emulator
17:14:47 [android] Erasing existing emulator data...
17:14:47 $ /Users/buildserver/Android/sdk/tools/emulator -no-boot-anim
-ports 58108,58109 -prop persist.sys.language=en -prop persist.sys.country=US
-avd hudson_en-US_160_841x490_android-7 -no-snapshot-load -no-snapshot-save
-wipe-data -no-window -no-snapshot-update-time
17:14:50 PANIC: Could not open:
/tmp/jenkins-root-ssh/workspace/client_android_staging_test/.android/avd/hudson_en-US_160_841x490_android-7.ini*
daemon not running. starting it now on port 58110 *
17:14:50 * daemon started successfully *
17:15:52 [android] Emulator did not appear to start; giving up
{noformat}
I'm guessing the code tests for a .avd but not a .ini - I don't know how my
machine managed to end up with only a .avd (I checked, and it existed), but
in that scenario, the plugin should probably recreate the emulator (android
create avd -f).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12962) Workspace Cleanup Plugin does not play nicely with the Copy To Slave plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160028#comment-160028 ] vjuranek commented on JENKINS-12962: Sorry haven't had time for it so far, hopefully tomorrow or during the weekend Workspace Cleanup Plugin does not play nicely with the Copy To Slave plugin --- Key: JENKINS-12962 URL: https://issues.jenkins-ci.org/browse/JENKINS-12962 Project: Jenkins Issue Type: Bug Components: ws-cleanup Affects Versions: current Environment: Jenkins 1.452, Win7 Reporter: Thomas Fields Assignee: vjuranek Hi there, The Workspace Cleanup Plugin does not play nicely with the Copy To Slave plugin. Here's a snippet from my console output for my build: 14:33:23 Deleting project workspace... done 14:33:23 14:33:23 [copy-to-slave] Copying 'Engine/Lib/**/*.lib, Engine/Lib/**/*.pdb, Engine/Lib/**/*.a', excluding nothing, from 'file:/c:/JCI/workspace/Expat-Live/CONFIG/Debug/TARGET/GCC/VSVERSION/2008' on 'hudson.slaves.DumbSlave@720397f7' to 'file:/C:/JCI/current_build/Expat-Live/CL167206' on the master. Note how the workspace is deleted before the copy step begins. Can this be fixed please? I assume deleting a workspace is something you'd always want to do last. I'd be happy to test any fixes. Regards, Tom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13021) Base Clearcase: Tracking changes on labels
Stephan Schueler created JENKINS-13021: -- Summary: Base Clearcase: Tracking changes on labels Key: JENKINS-13021 URL: https://issues.jenkins-ci.org/browse/JENKINS-13021 Project: Jenkins Issue Type: Improvement Components: clearcase Affects Versions: current Reporter: Stephan Schueler Assignee: Vincent Latombe Priority: Minor Triggering a build by SCM change works fine with load rules + branches + label, but Jenkins detects changes only for well-known labels (MY_LABEL_1). But sometimes it would be very helpful to have wildcards available for labels, e.g. if you know the basename of a new label, but not its revision (MY_LABEL_*). Example: I want to trigger a build only if there's a new element version available in main branch tagged with a label: load rule@@/branch/MY_LABEL_* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160031#comment-160031
]
Christopher Orr commented on JENKINS-12120:
---
Can you check if hudson_en-US_160_WVGA_Google_Inc._Google_APIs_7.avd was
created *anywhere* on disk, not just in /var/lib/jenkins/.android/avd?
Sometimes there can be a conflict between where the plugin looks for AVDs and
where the `android` tool creates them.
Emulator startup shouldn't fail when .ini is missing
Key: JENKINS-12120
URL: https://issues.jenkins-ci.org/browse/JENKINS-12120
Project: Jenkins
Issue Type: Bug
Components: android-emulator
Reporter: Jørgen Tjernø
Assignee: Christopher Orr
{noformat}
17:14:47 [android] Starting Android emulator
17:14:47 [android] Erasing existing emulator data...
17:14:47 $ /Users/buildserver/Android/sdk/tools/emulator -no-boot-anim
-ports 58108,58109 -prop persist.sys.language=en -prop persist.sys.country=US
-avd hudson_en-US_160_841x490_android-7 -no-snapshot-load -no-snapshot-save
-wipe-data -no-window -no-snapshot-update-time
17:14:50 PANIC: Could not open:
/tmp/jenkins-root-ssh/workspace/client_android_staging_test/.android/avd/hudson_en-US_160_841x490_android-7.ini*
daemon not running. starting it now on port 58110 *
17:14:50 * daemon started successfully *
17:15:52 [android] Emulator did not appear to start; giving up
{noformat}
I'm guessing the code tests for a .avd but not a .ini - I don't know how my
machine managed to end up with only a .avd (I checked, and it existed), but
in that scenario, the plugin should probably recreate the emulator (android
create avd -f).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12787) LOADING overlay does not go away on the Configure System page
[
https://issues.jenkins-ci.org/browse/JENKINS-12787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160030#comment-160030
]
Curtis Ruck commented on JENKINS-12787:
---
I'm seeing this in the Mantis Plugin.
LOADING overlay does not go away on the Configure System page
-
Key: JENKINS-12787
URL: https://issues.jenkins-ci.org/browse/JENKINS-12787
Project: Jenkins
Issue Type: Bug
Components: gui
Affects Versions: current
Environment: Jenkins
Reporter: Joshua Davis
Labels: gui, jenkins
After navigating to Manage-Configure System, the LOADING overlay never goes
away. It is impossible to save any configuration changes.
EXPECTED:
* You can save your global configuration.
Here is the stack trace from Chrome's JS console:
{code}
Uncaught TypeError: Object #Object has no method 'findMatchingInput'
(anonymous function)
e.targetUrl hudson-behavior.js:338
registerValidator hudson-behavior.js:343
apply behavior.js:73
(anonymous function) behavior.js:79
Behaviour.applySubtree behavior.js:68
Behaviour.applybehavior.js:54
(anonymous function)behavior.js:49
window.onload
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9001) Repository polling: build order of projects does not respect configured project dependencies
[ https://issues.jenkins-ci.org/browse/JENKINS-9001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160032#comment-160032 ] evernat commented on JENKINS-9001: -- In the configuration of the jobs, and in the Advanced project options, have you tried to check Block build when upstream project is building? Repository polling: build order of projects does not respect configured project dependencies Key: JENKINS-9001 URL: https://issues.jenkins-ci.org/browse/JENKINS-9001 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: n.a. Reporter: Alexander Veit Regularly we run into the following bug: After changes in several projects have been committed in a single SVN transaction, Jenkins polls the repository and recognizes the changes. Unfortunately Jenkins' project build order is not compatible with existing (and configured) project dependencies. So dependent projects run into build errors and turn to red. The dependencies are tree-like (no cycles). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12120) Emulator startup shouldn't fail when .ini is missing
[
https://issues.jenkins-ci.org/browse/JENKINS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160034#comment-160034
]
francisdb commented on JENKINS-12120:
-
Have not found any avd, could you tell me the command used by the plugin to
create the avd so I can try to reproduce this?
Emulator startup shouldn't fail when .ini is missing
Key: JENKINS-12120
URL: https://issues.jenkins-ci.org/browse/JENKINS-12120
Project: Jenkins
Issue Type: Bug
Components: android-emulator
Reporter: Jørgen Tjernø
Assignee: Christopher Orr
{noformat}
17:14:47 [android] Starting Android emulator
17:14:47 [android] Erasing existing emulator data...
17:14:47 $ /Users/buildserver/Android/sdk/tools/emulator -no-boot-anim
-ports 58108,58109 -prop persist.sys.language=en -prop persist.sys.country=US
-avd hudson_en-US_160_841x490_android-7 -no-snapshot-load -no-snapshot-save
-wipe-data -no-window -no-snapshot-update-time
17:14:50 PANIC: Could not open:
/tmp/jenkins-root-ssh/workspace/client_android_staging_test/.android/avd/hudson_en-US_160_841x490_android-7.ini*
daemon not running. starting it now on port 58110 *
17:14:50 * daemon started successfully *
17:15:52 [android] Emulator did not appear to start; giving up
{noformat}
I'm guessing the code tests for a .avd but not a .ini - I don't know how my
machine managed to end up with only a .avd (I checked, and it existed), but
in that scenario, the plugin should probably recreate the emulator (android
create avd -f).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12962) Workspace Cleanup Plugin does not play nicely with the Copy To Slave plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160033#comment-160033 ] vjuranek commented on JENKINS-12962: Hi, can reproduce. Seems like bug in jenkins core which doesn't respect setup of ordinal annotation. Need to dig deeper into jenkins core to verify it. Workspace Cleanup Plugin does not play nicely with the Copy To Slave plugin --- Key: JENKINS-12962 URL: https://issues.jenkins-ci.org/browse/JENKINS-12962 Project: Jenkins Issue Type: Bug Components: ws-cleanup Affects Versions: current Environment: Jenkins 1.452, Win7 Reporter: Thomas Fields Assignee: vjuranek Hi there, The Workspace Cleanup Plugin does not play nicely with the Copy To Slave plugin. Here's a snippet from my console output for my build: 14:33:23 Deleting project workspace... done 14:33:23 14:33:23 [copy-to-slave] Copying 'Engine/Lib/**/*.lib, Engine/Lib/**/*.pdb, Engine/Lib/**/*.a', excluding nothing, from 'file:/c:/JCI/workspace/Expat-Live/CONFIG/Debug/TARGET/GCC/VSVERSION/2008' on 'hudson.slaves.DumbSlave@720397f7' to 'file:/C:/JCI/current_build/Expat-Live/CL167206' on the master. Note how the workspace is deleted before the copy step begins. Can this be fixed please? I assume deleting a workspace is something you'd always want to do last. I'd be happy to test any fixes. Regards, Tom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12866) Unable to connect to jenkins slave running on ARM platform
[ https://issues.jenkins-ci.org/browse/JENKINS-12866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160035#comment-160035 ] Eric Huang commented on JENKINS-12866: -- I am using Jenkins SSH Slaves plugin version 0.21, and yes this is still an issues for us. Is there suppose to be a Copying setup script files in the log? I took a look at another working slave connection I have and did not see that line as well. Unable to connect to jenkins slave running on ARM platform -- Key: JENKINS-12866 URL: https://issues.jenkins-ci.org/browse/JENKINS-12866 Project: Jenkins Issue Type: Bug Components: slave-setup Environment: pandaboard, ARM platform Reporter: Eric Huang Assignee: Eric Huang I am trying to setup a jenkins slave that is running on a pandaboard. I have Ubuntu 11.10 oneiric installed, and I am using OpenJDK Runtime Environment (IcedTea6 1.11pre). I am getting a Invalid encoded sequence encountered error when attempting to connect to the slave via ssh: [02/22/12 16:45:41] [SSH] Opening SSH connection to panda-devboard:22. 6:45:47] [SSH] Authentication successful. [02/22/12 16:45:47] [SSH] The remote users environment is: BASH=/bin/bash BASHOPTS=cmdhist:extquote:force_fignore:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath BASH_ALIASES=() BASH_ARGC=() BASH_ARGV=() BASH_CMDS=() BASH_EXECUTION_STRING=set BASH_LINENO=() BASH_SOURCE=() BASH_VERSINFO=([0]=4 [1]=2 [2]=10 [3]=1 [4]=release [5]=arm-unknown-linux-gnueabi) BASH_VERSION='4.2.10(1)-release' DIRSTACK=() EUID=4086 GROUPS=() HOME=/home/release HOSTNAME=panda-devboard HOSTTYPE=arm IFS=$' \t\n' LANG=en_CA.UTF-8 LOGNAME=release MACHTYPE=arm-unknown-linux-gnueabi MAIL=/var/mail/release OPTERR=1 OPTIND=1 OSTYPE=linux-gnueabi PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games PIPESTATUS=([0]=0) PPID=10358 PS4='+ ' PWD=/home/release SHELL=/bin/bash SHELLOPTS=braceexpand:hashall:interactive-comments SHLVL=1 SSH_CLIENT='10.1.0.195 4050 22' SSH_CONNECTION='10.1.0.195 4050 10.1.124.85 22' TERM=dumb UID=4086 USER=release XDG_SESSION_COOKIE=5c9ceadb707acb8eae13745b0009-1329957946.802516-2119305671 _=']' [02/22/12 16:45:47] [SSH] Checking java version of java [02/22/12 16:45:48] [SSH] java -version returned 1.6.0_23. [02/22/12 16:45:48] [SSH] Starting sftp client. [02/22/12 16:45:48] [SSH] Copying latest slave.jar... [02/22/12 16:45:48] [SSH] Copied 257,564 bytes. [02/22/12 16:45:48] [SSH] Starting slave process: cd '/var/hudson' java -jar slave.jar -text Running in text mode ===[JENKINS REMOTING CAPACITY]==[HUDSON TRANSMISSION BEGINS]===channel started Slave.jar version: 2.12 This is a Unix slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Slave successfully connected and online [02/22/12 16:45:54] [SSH] Opening SSH connection to panda-devboard:22. ERROR: Connection terminated java.io.IOException: Invalid encoded sequence encountered: 6A 6D 6D 5F 19 EB 4C 7A 6A 2B C9 4B 1A at hudson.remoting.BinarySafeStream$1._read(BinarySafeStream.java:194) at hudson.remoting.BinarySafeStream$1.read(BinarySafeStream.java:80) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1127) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12619) Failed to test the validity of the user name on all security matrices since upgrade
[ https://issues.jenkins-ci.org/browse/JENKINS-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160036#comment-160036 ] Mark Badolato commented on JENKINS-12619: - Same here FreeBSD 8.2, happening on Jenkins 1.454 with AD 1.26. Everything appears to be working, however (as others have also stated) Failed to test the validity of the user name on all security matrices since upgrade - Key: JENKINS-12619 URL: https://issues.jenkins-ci.org/browse/JENKINS-12619 Project: Jenkins Issue Type: Bug Components: active-directory Environment: Jenkins 1.450, plugin version 1.26 Windows Server 2003, non-domain server Installed as local user Our Windows domain name specified in configuration as ourdomain.co.uk Reporter: Tom Fanning Priority: Minor Labels: jenkins, plugin, windows Upgraded plugin to version 1.26 just after upgrading Jenkins to 1.450 Now get message Failed to test the validity of the user name x wherever there is a security checkbox matrix. Everything seems to work alright still as far as I can tell. Stack trace: org.acegisecurity.BadCredentialsException: Failed to retrieve user information for x; nested exception is javax.naming.NamingException: [LDAP: error code 1 - 04DC: LdapErr: DSID-0C0906E8, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, v1db1]; remaining name 'DC=ourdomain,DC=co,DC=uk' at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:231) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:130) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:95) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:27) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.loadUserByUsername(ActiveDirectorySecurityRealm.java:551) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName_(GlobalMatrixAuthorizationStrategy.java:304) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName(GlobalMatrixAuthorizationStrategy.java:288) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) at org.kohsuke.stapler.Stapler.service(Stapler.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at
[JIRA] (JENKINS-13022) EnvInject 1.33 doesn''t seem to work with Jenkins 1.454
Jim Searle created JENKINS-13022: Summary: EnvInject 1.33 doesn''t seem to work with Jenkins 1.454 Key: JENKINS-13022 URL: https://issues.jenkins-ci.org/browse/JENKINS-13022 Project: Jenkins Issue Type: Bug Components: envinject Reporter: Jim Searle Assignee: gbois I upgraded jenkins to 1.454 and envinject to 1.33 and the variables where not being set. I downgraded envinject to 1.31 and it worked again. I'm using Prepare an environment for the job Properties Content section and have Keep Jenkins Environment Variables and Keep Jenkins Build Variables enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13023) Mantis Plugin causes Configuration Loading Overlay to not disappear.
Curtis Ruck created JENKINS-13023:
-
Summary: Mantis Plugin causes Configuration Loading Overlay to not
disappear.
Key: JENKINS-13023
URL: https://issues.jenkins-ci.org/browse/JENKINS-13023
Project: Jenkins
Issue Type: Bug
Components: mantis
Affects Versions: current
Reporter: Curtis Ruck
Assignee: sogabe
This appears to come from Mantis's global.jelly, function checkUrl(base) { var
url = encodeURIComponent(Form.findMatchingInput(base,'mantis.url').value);
Uncaught TypeError: Object #Object has no method 'findMatchingInput'
checkUrlconfigure:384
(anonymous function)
e.targetUrlhudson-behavior.js:339
registerValidatorhudson-behavior.js:344
applybehavior.js:73
(anonymous function)behavior.js:79
Behaviour.applySubtreebehavior.js:68
Behaviour.applybehavior.js:54
(anonymous function)behavior.js:49
window.onload
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12258) Plugin is missing descriptor, which throws spurious exception text in jenkins.err.log
[
https://issues.jenkins-ci.org/browse/JENKINS-12258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160038#comment-160038
]
Nathmie S commented on JENKINS-12258:
-
Please could this be looked at. I am getting this bug on Jenkins ver. 1.454.
Plugin is missing descriptor, which throws spurious exception text in
jenkins.err.log
-
Key: JENKINS-12258
URL: https://issues.jenkins-ci.org/browse/JENKINS-12258
Project: Jenkins
Issue Type: Bug
Components: htmlpublisher
Reporter: Garen Parham
Assignee: mcrooney
Priority: Minor
Guessing the plugin needs to be updated for newer versions of Jenkins--using
it throws an exception like so in my jenkins.err.log:
{noformat}
WARNING: Caught exception evaluating:
descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason:
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at
org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at
org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at
org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at
org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at
org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:63)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
[JIRA] (JENKINS-10996) fisheye links are wrong for individual files
[ https://issues.jenkins-ci.org/browse/JENKINS-10996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Petti resolved JENKINS-10996. - Resolution: Fixed fisheye links are wrong for individual files Key: JENKINS-10996 URL: https://issues.jenkins-ci.org/browse/JENKINS-10996 Project: Jenkins Issue Type: Bug Components: perforce Affects Versions: current Reporter: Scott Bartram Assignee: Rob Petti When viewing changes for a specific build, the links to FishEye are correct for the changelist but incorrect for the individual files. For example, my build contains the correct changelist link: http://fisheye.foo.com/changelog/mydepot/?cs=270181 However, the individual files have incorrect links because the depot is repeated: http://fisheye.foo.com/browse/mydepot/mydepot/insite/MAIN/properties/src/main/properties/properties.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7436) Add support for perforce shelve builds
[ https://issues.jenkins-ci.org/browse/JENKINS-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160039#comment-160039 ] Rob Petti commented on JENKINS-7436: Wait, if you are leaving the unshelved files behind, doesn't that pollute the build environment for the next build? Or are you cleaning and force syncing on every build? Add support for perforce shelve builds -- Key: JENKINS-7436 URL: https://issues.jenkins-ci.org/browse/JENKINS-7436 Project: Jenkins Issue Type: New Feature Components: perforce Reporter: vbuzzsaw It would be really useful if the perforce plugin could add support for shelving -- Functionality added perforce in version 2009.2. Here is a good blog writeup --http://blog.perforce.com/blog/?p=1872 Many things hudson is great for is finding out if anyone broke the build by polling source repositories looking for commits and kicking off builds. But breaking builds and backing code is a pain sometimes. It would be even better if you could run a build in hudson BEFORE checking in your changelist to see if your changelist WOULD break the build and fix problems before they occur. That is exactly what perforce shelving does -- It allows you to shelve your changelist -- saving all your modifications to the server (without committing them), and then allowing others to pull down the shelved modified code and perform a build. I'm not sure if the underlying tek42 perforce client library you use supports shelving, but if so this would be really useful functionality. Thanks. Doug -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12994) Quiet period is blocking other jobs in queue
[ https://issues.jenkins-ci.org/browse/JENKINS-12994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160040#comment-160040 ] allenservedio commented on JENKINS-12994: - I am seeing the same thing in 1.454. Even worse, I am starting to see deadlocks around this. I had to go in and kill a three jobs where two of them were stuck in an infinite loop of quiet periods and the third (a scheduled job) was stuck waiting for an executor. As I was not watching the builds, they were stuck in that state for over an hour before I caught them (the quiet period for the other two jobs was 190 seconds, it just kept cycling through quiet periods). Quiet period is blocking other jobs in queue Key: JENKINS-12994 URL: https://issues.jenkins-ci.org/browse/JENKINS-12994 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Platform: All, OS: All Reporter: teetoivo Starting from version 1.452, a job in queue waiting for the quiet period to pass is blocking all other jobs that have been queued after it. Example: # Job A has quiet period set to 10 seconds # Job B has quiet period set to 300 seconds # Job C has quiet period set to 100 seconds # Jobs get queued in A-B-C order. # Job A starts executing after 10 seconds # After 100 seconds, status of job C changes to pending - Waiting for next available executor even if free executors are available # After 300 seconds both jobs B and C start executing This problem is hardly visible when short quiet periods are used but becomes problematic with longer quiet periods or plugins like Naginator that will increase the quiet period to hours if the builds fail enough. Version 1.451 is the last release where this problem isn't visible. From public releases, at least 1.452 and 1.454 are affected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13022) EnvInject 1.33 doesn''t seem to work with Jenkins 1.454
[ https://issues.jenkins-ci.org/browse/JENKINS-13022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13022 started by gbois. EnvInject 1.33 doesn''t seem to work with Jenkins 1.454 --- Key: JENKINS-13022 URL: https://issues.jenkins-ci.org/browse/JENKINS-13022 Project: Jenkins Issue Type: Bug Components: envinject Reporter: Jim Searle Assignee: gbois I upgraded jenkins to 1.454 and envinject to 1.33 and the variables where not being set. I downgraded envinject to 1.31 and it worked again. I'm using Prepare an environment for the job Properties Content section and have Keep Jenkins Environment Variables andKeep Jenkins Build Variables enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13022) EnvInject 1.33 doesn''t seem to work with Jenkins 1.454
[ https://issues.jenkins-ci.org/browse/JENKINS-13022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160041#comment-160041 ] gbois commented on JENKINS-13022: - I tried with version 1.454 and I'm afraid I didn't reproduce the issue. Could you attach your job descriptor (config.xml - found in $JENKINS_HOME/jobs/job_name/config.xml)? I'll try to reproduce it with your configuration. Thanks Gregory EnvInject 1.33 doesn''t seem to work with Jenkins 1.454 --- Key: JENKINS-13022 URL: https://issues.jenkins-ci.org/browse/JENKINS-13022 Project: Jenkins Issue Type: Bug Components: envinject Reporter: Jim Searle Assignee: gbois I upgraded jenkins to 1.454 and envinject to 1.33 and the variables where not being set. I downgraded envinject to 1.31 and it worked again. I'm using Prepare an environment for the job Properties Content section and have Keep Jenkins Environment Variables andKeep Jenkins Build Variables enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13022) EnvInject 1.33 doesn''t seem to work with Jenkins 1.454
[ https://issues.jenkins-ci.org/browse/JENKINS-13022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] anthonyjeffery updated JENKINS-13022: - Attachment: config.xml Attaching job descriptor per your request EnvInject 1.33 doesn''t seem to work with Jenkins 1.454 --- Key: JENKINS-13022 URL: https://issues.jenkins-ci.org/browse/JENKINS-13022 Project: Jenkins Issue Type: Bug Components: envinject Reporter: Jim Searle Assignee: gbois Attachments: config.xml I upgraded jenkins to 1.454 and envinject to 1.33 and the variables where not being set. I downgraded envinject to 1.31 and it worked again. I'm using Prepare an environment for the job Properties Content section and have Keep Jenkins Environment Variables andKeep Jenkins Build Variables enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12258) Plugin is missing descriptor, which throws spurious exception text in jenkins.err.log
[
https://issues.jenkins-ci.org/browse/JENKINS-12258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mcrooney reassigned JENKINS-12258:
--
Assignee: (was: mcrooney)
I unfortunately don't know anything about this particular issue, and haven't
run into any issues, so I'm unassigning it from myself. Please, anyone feel
free to look into it.
Plugin is missing descriptor, which throws spurious exception text in
jenkins.err.log
-
Key: JENKINS-12258
URL: https://issues.jenkins-ci.org/browse/JENKINS-12258
Project: Jenkins
Issue Type: Bug
Components: htmlpublisher
Reporter: Garen Parham
Priority: Minor
Guessing the plugin needs to be updated for newer versions of Jenkins--using
it throws an exception like so in my jenkins.err.log:
{noformat}
WARNING: Caught exception evaluating:
descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason:
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at
org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at
org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at
org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at
org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at
org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:63)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at
[JIRA] (JENKINS-13022) EnvInject 1.33 doesn''t seem to work with Jenkins 1.454
[ https://issues.jenkins-ci.org/browse/JENKINS-13022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-13022. - Resolution: Fixed Thanks for your input. I fixed it. EnvInject 1.33 doesn''t seem to work with Jenkins 1.454 --- Key: JENKINS-13022 URL: https://issues.jenkins-ci.org/browse/JENKINS-13022 Project: Jenkins Issue Type: Bug Components: envinject Reporter: Jim Searle Assignee: gbois Attachments: config.xml I upgraded jenkins to 1.454 and envinject to 1.33 and the variables where not being set. I downgraded envinject to 1.31 and it worked again. I'm using Prepare an environment for the job Properties Content section and have Keep Jenkins Environment Variables andKeep Jenkins Build Variables enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13022) EnvInject 1.33 doesn''t seem to work with Jenkins 1.454
[ https://issues.jenkins-ci.org/browse/JENKINS-13022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160044#comment-160044 ] SCM/JIRA link daemon commented on JENKINS-13022: Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectBuildWrapper.java src/main/java/org/jenkinsci/plugins/envinject/EnvInjectBuilder.java src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java src/main/java/org/jenkinsci/plugins/envinject/service/EnvInjectVariableGetter.java http://jenkins-ci.org/commit/envinject-plugin/bf15513e57f910d0376bca9f4f9c22cf1966d637 Log: Fix JENKINS-13022 EnvInject 1.33 doesn''t seem to work with Jenkins 1.454 --- Key: JENKINS-13022 URL: https://issues.jenkins-ci.org/browse/JENKINS-13022 Project: Jenkins Issue Type: Bug Components: envinject Reporter: Jim Searle Assignee: gbois Attachments: config.xml I upgraded jenkins to 1.454 and envinject to 1.33 and the variables where not being set. I downgraded envinject to 1.31 and it worked again. I'm using Prepare an environment for the job Properties Content section and have Keep Jenkins Environment Variables andKeep Jenkins Build Variables enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12936) EnvInject Plugin 1.30 does not display all properties on job config page
[
https://issues.jenkins-ci.org/browse/JENKINS-12936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160046#comment-160046
]
gbois commented on JENKINS-12936:
-
Yes released.
It's always take some time to have the plugin available in the update center.
You can check and download latest version directly in the repository:
http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/envinject
EnvInject Plugin 1.30 does not display all properties on job config page
Key: JENKINS-12936
URL: https://issues.jenkins-ci.org/browse/JENKINS-12936
Project: Jenkins
Issue Type: Bug
Components: envinject
Reporter: mwebber
Assignee: gbois
I upgraded from EnvInject Plugin 1.28 to 1.30. The result was that, for some
jobs, variables I have previously defined are not displayed on the job
configuration page.
This is where I have selected Inject environment variables to the build
process, and have entries in the Properties Content box. Even though the
entries are on teh job config file, they are not always displayed in the
Properties Content box.
When the config.xml looks like this, the Properties Content box IS
correctly populated:
{noformat}
EnvInjectBuildWrapper
info
propertiesContentbranchTagPath=v0.9/propertiesContent
loadFilesFromMasterfalse/loadFilesFromMaster
/info
/EnvInjectBuildWrapper
{noformat}
When the config.xml looks like this, the Properties Content box s
incorrectly displays EMPTY:
{noformat}
EnvInjectBuildWrapper
info
propertiesContentMap class=linked-hash-map
entry
stringmaterialize_component/string
stringsda/string
/entry
entry
stringmaterialize_category/string
stringsda/string
/entry
entry
stringmaterialize_version/string
stringv0.9/string
/entry
entry
stringmaterialize_workspace_path/string
string${WORKSPACE}/materialize_workspace/string
/entry
/propertiesContentMap
loadFilesFromMasterfalse/loadFilesFromMaster
/info
/EnvInjectBuildWrapper
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12898) Option for Valgrind report to include each problem as a test failure
[ https://issues.jenkins-ci.org/browse/JENKINS-12898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160047#comment-160047 ] gbois commented on JENKINS-12898: - Any update? Option for Valgrind report to include each problem as a test failure Key: JENKINS-12898 URL: https://issues.jenkins-ci.org/browse/JENKINS-12898 Project: Jenkins Issue Type: Improvement Components: xunit Reporter: Chris Withers Assignee: gbois Priority: Minor It would be great if Valgrind xml could be turned into one-test-failure-per-error as an option. The current support turns the whole valgrind run into one test, which either passes or fails. This is great if you're starting from a zero-problem situation, however, if you're starting from a 1000s-of-problems situation, it would be great to be able to see the trend graph going down over time. I believe the proposal I make will address this, and might only need an xslt, but I don't have the xml skills to make that work... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13025) Active Directory Plugin version 1.26 results in org.acegisecurity.BadCredentialsException: Failed to retrieve user information when 1.24 does not
Don Lindsay created JENKINS-13025: - Summary: Active Directory Plugin version 1.26 results in org.acegisecurity.BadCredentialsException: Failed to retrieve user information when 1.24 does not Key: JENKINS-13025 URL: https://issues.jenkins-ci.org/browse/JENKINS-13025 Project: Jenkins Issue Type: Bug Components: active-directory Environment: jenkins-1.424.6-1.1.noarch RPM on x86_64 CentOS 6.2, active directory plugin 1.24 versus 1.26 Reporter: Don Lindsay All of our login IDs are LDAP/Active Directory names. We can log in. When we upgraded the Active Directory plugin to 1.26, we noticed that the Configure System contained error indications. Specifically, under Authorization, there is a user/group list, and each username had been replaced by an error indication. Examination showed the same error for each username. For example: org.acegisecurity.BadCredentialsException: Failed to retrieve user information for d_lindsay; nested exception is javax.naming.NamingException: [LDAP: error code 1 - : LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece\ufffd]; remaining name 'DC=ocarina,DC=local' at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProv\ ider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:231) Reverting to the 1.24 plugin fixed this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
