[JIRA] [other] (JENKINS-2551) Option to compress build logs
Title: Message Title
Mr Cinquero edited a comment on JENKINS-2551
Re: Option to compress build logs
The plugin disables the console tail functionality. And it does not compress any leftover logs. And you need to enable it by hand for each single job.Best solution so far (on Linux boxes): set up a daily script job:{code:java}set -Eexcd "$JENKINS_HOME/jobs"find * -regex '^\([^/]+/builds/[0-9]+/log\|[^/]+/modules/[^/]+/builds/[0-9]+/log\)$' -cmin +600 -exec gzip -9v '{}' \;{code} This compresses all uncompressed build logs which haven't been touched in the last 10 hours (to avoid processing active logs).
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-2551) Option to compress build logs
Title: Message Title
Mr Cinquero edited a comment on JENKINS-2551
Re: Option to compress build logs
The plugin disables the console tail functionality. And it does not compress any leftover logs. And you need to enable it by hand for each single job.Best solution so far (on Linux boxes): set up a daily script job: {code:java} set -Eexcd "$JENKINS_HOME/jobs"find * -regex '^\([^/]+/builds/[0-9]+/log\|[^/]+/modules/[^/]+/builds/[0-9]+/log\)$' -cmin +600 -exec gzip -9v '{}' \; {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-2551) Option to compress build logs
Title: Message Title
Mr Cinquero commented on JENKINS-2551
Re: Option to compress build logs
The plugin disables the console tail functionality. And it does not compress any leftover logs. And you need to enable it by hand for each single job.
Best solution so far (on Linux boxes): set up a daily script job:
set -Eex cd "$JENKINS_HOME/jobs" find * -regex '^([^/]
/builds/[0-9]
/log|[^/]
/modules/[^/]
/builds/[0-9]+/log)$' -cmin +600 -exec gzip -9v '{}' \;
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-33335) Jenkins stuck in build loop even after solving the dependency issue
Title: Message Title Mr Cinquero created an issue Jenkins / JENKINS-5 Jenkins stuck in build loop even after solving the dependency issue Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 06/Mar/16 3:01 AM Priority: Minor Reporter: Mr Cinquero Okay, I have project A and project B. Project B happens to be a multi-module maven project. A and B have each one build job defined in Jenkins. A depends on one sub-module of B. I detected the build loop, moved the sub-module from B into a separate job C, but Jenkins is still stuck in that build loop and somehow cannot forget C being part of B...?! I even checked the dependency by running a maven build with a clean local repo on the command line. There is no loop. And there are no SCM changes. Jenkins just triggers A when finishing B and B when finishing A. Interestingly, the new Job C does not trigger A. However, when B is disabled, C does trigger A The fingerprint for C's generated jar artifact lists A and B as being dependent on C (ie. listed in usages section). After a lot of trying, it seems Jenkins gets its maven dependency information from the modules/ subdirectory structure beneath each job's root directory. I removed B's modules/C directory and now it works.. Not sure how to resolve this. It's not user-friendly/fail safe right now.
[JIRA] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Mr Cinquero updated an issue Jenkins / JENKINS-23697 IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) build log file reproducing the exception when doing a "curl http://localhost:9087/job/android/8/consoleFull" Change By: Mr Cinquero Attachment: log.txt Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title
Mr Cinquero edited a comment on JENKINS-23697
Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Hokay, I traced down a log file producing that error and traced it further down to the exact line: {noformat} [JENKINS] Recording test results[INFO] ha:YB+LCP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEGvvmZ+X75ZekLlOVfvTjc8FPJgaGiiIGKaiG5Py84vycVD1nCA1SyAABjCCFBQCV27OjYA==[INFO] --- maven-source-plugin:2.3:jar-no-fork (attach-sources) @ android-aggregator --- {noformat} Interestingly, I can't see the second line on my console. It only appeared after pasting it here. Every time I open that build's log in Jenkins, the exception gets logged to /var/log/jenkins.log. However, I don't get to see the exception in the frontend again ... that only seems to happen during live builds.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Mr Cinquero edited a comment on JENKINS-23697 Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) Hokay, I traced down a log file producing that error and traced it further down to the exact line:[JENKINS] Recording test results[INFO] ha:YB+LCP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEGvvmZ+X75ZekLlOVfvTjc8FPJgaGiiIGKaiG5Py84vycVD1nCA1SyAABjCCFBQCV27OjYA==[INFO] --- maven-source-plugin:2.3:jar-no-fork (attach-sources) @ android-aggregator ---Interestingly, I can't see the second line on my console. It only appeared after pasting it here. Every time I open that build's log in Jenkins, the exception gets logged to /var/log/jenkins.log. However, I don't get to see the exception in the frontend again ... that only seems to happen during live builds. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Mr Cinquero commented on JENKINS-23697 Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) Hokay, I traced down a log file producing that error and traced it further down to the exact line: [JENKINS] Recording test results[INFO] ha:YB+LCP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEGvvmZ+X75ZekLlOVfvTjc8FPJgaGiiIGKaiG5Py84vycVD1nCA1SyAABjCCFBQCV27OjYA== [INFO] — maven-source-plugin:2.3:jar-no-fork (attach-sources) @ android-aggregator — Interestingly, I can't see the second line on my console. It only appeared after pasting it here. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title
Mr Cinquero edited a comment on JENKINS-23697
Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
hudson.tasks._maven.Maven3MojoNote.annotate(): {code:java} text.addMarkup(7,text.length(),"",""); {code} The "7" comes from the pattern defined inside the same class: {code:java} public static Pattern PATTERN = Pattern.compile("\\[INFO\\] --- .+-plugin:[^:]+:[^ ]+ \\(.+\\) @ .+ ---"); {code} However, I see nothing that ensures that the mentioned method gets only called for Strings matching that pattern. ?!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title
Mr Cinquero commented on JENKINS-23697
Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
hudson.tasks._maven.Maven3MojoNote.annotate():
text.addMarkup(7,text.length(),"","");
The "7" comes from the pattern defined inside the same class:
public static Pattern PATTERN = Pattern.compile("\\[INFO] — .
-plugin:[^:]
:[^ ]+ \\(.
) @ .
---");
However, I see nothing that ensures that the mentioned method gets only called for Strings matching that pattern. ?!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Mr Cinquero edited a comment on JENKINS-23697 Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) I don't have console tail plugin installed , so yes, it's happening with the built-in build html tail follow. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Mr Cinquero commented on JENKINS-23697 Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) I don't have console tail plugin installed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Mr Cinquero edited a comment on JENKINS-23697 Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) Re-appeared at 1.613 , no problems when looking at complete console output (html formatted) afterwards, just a problem with tail . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Title: Message Title Mr Cinquero commented on JENKINS-23697 Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) Re-appeared at 1.613. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-25633) maven pom analysis does not cover maven plugins' dependencies
Mr Cinquero
updated JENKINS-25633
maven pom analysis does not cover maven plugins' dependencies
Change By:
Mr Cinquero
(15/Nov/14 11:34 AM)
Description:
Jenkins analyzes the maven pom.xml during execution of the maven build, which includes analyzing the dependencies. However, it does not seem to work for plugins' dependencies, namely "my.pkg:artId" in the following example:{noformat}org.codehaus.mojoexec-maven-pluginprocess-resourcesjavatruemy.pkgartIdmy.pkg.bla.Appmy.pkgartId1.0-SNAPSHOT{noformat}Is there any way (except manually configuring the Jenkins jobs) to tell Jenkins to consider my.pkg:artId as one of the project's dependencies? I tried putting the dependency declaration into the build dependency list using the provided scope. That, however, has side-effects: for example, NetBeans will consider transitive dependencies of my.pkg:artId as present, thereby not indicating missing dependencies in the build etc:{noformat}my.pkgartIdprovided**...{noformat}The exclusions somewhat mitigate the problem introduced by mis-using the
provded
provided
scope and reduce it to resources/classes contained in my.pkg:artId.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-25633) maven pom analysis does not cover maven plugins' dependencies
Mr Cinquero created JENKINS-25633 maven pom analysis does not cover maven plugins' dependencies Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 15/Nov/14 11:32 AM Description: Jenkins analyzes the maven pom.xml during execution of the maven build, which includes analyzing the dependencies. However, it does not seem to work for plugins' dependencies, namely "my.pkg:artId" in the following example: org.codehaus.mojo exec-maven-plugin process-resources java true my.pkg artId my.pkg.bla.App my.pkg artId 1.0-SNAPSHOT Is there any way (except manually configuring the Jenkins jobs) to tell Jenkins to consider my.pkg:artId as one of the project's dependencies? I tried putting the dependency declaration into the build dependency list using the provided scope. That, however, has side-effects: for example, NetBeans will consider transitive dependencies of my.pkg:artId as present, thereby not indicating missing dependencies in the build etc: my.pkg artId provided * * ... The exclusions somewhat mitigate the problem introduced by mis-using the provded scope and reduce it to resources/classes contained in my.pkg:artId. Project: Jenkins Priority: Minor Reporter: Mr Cinquero This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-25633) maven pom analysis does not cover maven plugins' dependencies
Mr Cinquero
updated JENKINS-25633
maven pom analysis does not cover maven plugins' dependencies
Change By:
Mr Cinquero
(15/Nov/14 11:33 AM)
Description:
Jenkins analyzes the maven pom.xml during execution of the maven build, which includes analyzing the dependencies. However, it does not seem to work for plugins' dependencies, namely "my.pkg:artId" in the following example:
{noformat}
org.codehaus.mojoexec-maven-pluginprocess-resourcesjavatruemy.pkgartIdmy.pkg.bla.Appmy.pkgartId1.0-SNAPSHOT
{noformat}
Is there any way (except manually configuring the Jenkins jobs) to tell Jenkins to consider my.pkg:artId as one of the project's dependencies? I tried putting the dependency declaration into the build dependency list using the provided scope. That, however, has side-effects: for example, NetBeans will consider transitive dependencies of my.pkg:artId as present, thereby not indicating missing dependencies in the build etc:
{noformat}
my.pkgartIdprovided**...
{noformat}
The exclusions somewhat mitigate the problem introduced by mis-using the provded scope and reduce it to resources/classes contained in my.pkg:artId.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [console-tail] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)
Mr Cinquero created JENKINS-23697 IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: console-tail Created: 07/Jul/14 11:00 AM Description: Getting the following exception while doing a console tail: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: java.lang.IndexOutOfBoundsException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHa
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero edited a comment on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path OK, I found a possible solution: is the old java.io.* API still being used? If so, upgrade to java.nio.*, especially when reading filenames from disk the java.io.File.listFiles() method replaces invalid chars with the default unknown char character of the active charset, whereas java.nio.Files.newDirectoryStream() does not do such a thing (at least apparently, see https://github.com/jjYBdx4IL/filenameenc/blob/master/src/main/java/filenameenc/Test.java). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero commented on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path OK, I found a possible solution: is the old java.io.* API still being used? If so, upgrade to java.nio.*, especially when reading filenames from disk the java.nio.File.listFiles() method replaces invalid chars with the default unknown char character of the active charset, whereas java.nio.Files.newDirectoryStream does not do such a thing (at least apparently, see https://github.com/jjYBdx4IL/filenameenc/blob/master/src/main/java/filenameenc/Test.java). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero edited a comment on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path OK, I found a possible solution: is the old java.io.* API still being used? If so, upgrade to java.nio.*, especially when reading filenames from disk the java.io.File.listFiles() method replaces invalid chars with the default unknown char character of the active charset, whereas java.nio.Files.newDirectoryStream does not do such a thing (at least apparently, see https://github.com/jjYBdx4IL/filenameenc/blob/master/src/main/java/filenameenc/Test.java). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero edited a comment on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path Maybe. Or it may just be an indication that we need a workaround because otherwise the problem won't go away, possibly never because the JLS guys may decide it to be a feature I propose to use some platform-specific means for removing such badly encoded files, ie. run "rm -f $strange-filename" on Linux, and the equivalent on Windows. I guess that there are probably already libraries around doing exactly that, though I'm not aware of any. Another solution would be to let Jenkins always run with a full 8-bit charset as the default charset, ie. one that has no invalid characters/holes in the binary representation per se, though I'm not sure what undesirable side-effects that would bring about. Thinking about it further, I guess that this was no problem in the old days before Unicode, and it is rather a side-effect now that had to be introduced through the introducation of Unicode... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero edited a comment on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path Maybe. Or it may just be an indication that we need a workaround because otherwise the problem won't go away, possibly never because the JLS guys may decide it to be a feature I propose to use some platform-specific means for removing such badly encoded files, ie. run "rm -f $strange-filename" on Linux, and the equivalent on Windows. I guess that there are probably already libraries around doing exactly that, though I'm not aware of any. Another solution would be to let Jenkins always run with a full 8-bit charset as the default charset, ie. one that has no invalid characters/holes in the binary representation per se, though I'm not sure what undesirable side-effects that would bring about. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero edited a comment on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path Maybe. Or it may just be an indication that we need a workaround because otherwise the problem won't go away, possibly never because the JLS guys may decide it to be a feature I propose to use some platform-specific means for removing such badly encoded files, ie. run "rm -f $strange-filename" on Linux, and the equivalent on Windows. I guess that there are probably already libraries around doing exactly that, though I'm not aware of any. Another solution would be to let Jenkins always run with a full 8-bit charset as the default charset, ie. one that has no invalid characters per se, though I'm not sure what undesirable side-effects that would bring about. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero edited a comment on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path Maybe. Or it may just be an indication that we need a workaround because otherwise the problem won't go away, possibly never because the JLS guys may decide it to be a feature I propose to use some platform-specific means for removing such badly encoded files, ie. run "rm -f $strange-filename" on Linux, and the equivalent on Windows. I guess that there are probably already libraries around doing exactly that, though I'm not aware of any. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero commented on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path Maybe. Or it may just be an indication that we need a workaround because otherwise the problem won't go away, possibly never because the JLS guys may decide it to be a feature ))) I propose to use some platform-specific means for removing such badly encoded files, ie. run "rm -f $strange-filename" on Linux, and the equivalent on Windows. I guess that there are probably already libraries around doing exactly that, though I'm not aware of any. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero commented on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path I have created a test case to verify the issue that is possibly at hand here: https://github.com/jjYBdx4IL/filenameenc There is also a topic at stackoverflow, but the people there don't get it yet, hopefully they do with the example at github. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero commented on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path Yeah, I just checked it again, and it seems java.io.File always operates on the basis of a java.lang.String, ie. with an internal representation-independent form and it always uses the environment settings when choosing the actual filename repesentation when interacting with the filesystem layer. That is nuts because it seemingly cannot handle files with bad name encodings, ie. one could think of falling back to a generic charset like iso8859-1 to handle such cases, at least when the filename's correct encoding is not an issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero edited a comment on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path Yeah, I just checked it again, and it seems java.io.File always operates on the basis of a java.lang.String, ie. with an internal representation-independent form and it always uses the environment settings (or file.encoding sys prop) when choosing the actual filename repesentation when interacting with the filesystem layer. That is nuts because it seemingly cannot handle files with bad name encodings, ie. one could think of falling back to a generic charset like iso8859-1 to handle such cases, at least when the filename's correct encoding is not an issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero updated JENKINS-22434 jgit clean after checkout fails with unmappable chars in path Change By: Mr Cinquero (01/Apr/14 1:58 AM) Attachment: org.eclipse.jgit.java7.test.tar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero commented on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path There is no .git so I don't know. My guess is that it is strictly java.io.File related. I had such issues before where Java strictly refuses to process files with filenames not encoded according to locale settings. Obviously this is one such case: I always let Jenkins run with LC_ALL=C and the umlaut 'ä' in this case is obviously encoded as UTF-8. See the attached tar file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero created JENKINS-22434 jgit clean after checkout fails with unmappable chars in path Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git-client Created: 31/Mar/14 3:45 PM Description: Started by user anonymous Building in workspace /var/lib/jenkins/jobs/ext-jgit-3.3.0/workspace Cloning the remote Git repository Cloning repository https://github.com/eclipse/jgit.git ERROR: Failed to clean the workspace java.io.IOException: java.lang.reflect.InvocationTargetException at hudson.Util.isSymlinkJava7(Util.java:360) at hudson.Util.isSymlink(Util.java:325) at hudson.Util.deleteRecursive(Util.java:291) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:292) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:292) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:292) at hudson.Util.deleteContentsRecursive(Util.java:203) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:327) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:845) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:878) at hudson.model.AbstractProject.checkout(AbstractProject.java:1320) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1688) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.Util.isSymlinkJava7(Util.java:355) ... 20 more Caused by: java.nio.file.InvalidPathException: Malformed input or input contains unmappable chacraters: /var/lib/jenkins/jobs/ext-jgit-3.3.0/workspace/org.eclipse.jgit.java7.test/target/tmp_7536346264520663349/?? at sun.nio.fs.UnixPath.encode(UnixPath.java:147) at sun.nio.fs.UnixPath.(UnixPath.java:71) at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281) at java.io.File.toPath(File.java:2186) ... 24 more ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Failed to delete workspace at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:330) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:845) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:878) at hudson.model.AbstractProject.checkout(AbstractProject.java:1320) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1688) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.io.IOException: java.lang.reflect.InvocationTargetException at hudson.Util.isSymlinkJava7(Util.java:360) at hudson.Util.isSymlink(Util.java:325) at hudson.Util.deleteRecursive(Util.java:291) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:292) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:292) at hudson.Util.deleteContentsRecursive(Util.java:203) at hudson.Util.deleteRecursive(Util.java:292) at hudson.Util.deleteContentsRecursive(Util.java:203) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:327) ... 10 mo
[JIRA] [maven] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Mr Cinquero commented on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Maybe. However, I have always been using maven-enforcer-plugin with the dependency convergence enforcement enabled (http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html) and never had any issues with it. I just forced dependencies to use higher versions of some lib dependencies and it worked This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Mr Cinquero commented on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Maybe a bit off-topic, but better class isolation? Wouldn't that imply even more or at least not less memory footprint? Jenkins is already wasting quite a lot of memory with its plugin design. I think it would be better to have a proper integration test system for the plugins and dump the class isolation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [audit-trail] (JENKINS-22246) Audit Trail Plugin should record system changes
Mr Cinquero updated JENKINS-22246 Audit Trail Plugin should record system changes Change By: Mr Cinquero (18/Mar/14 2:32 PM) Description: It would be extremely useful to have a protocol when about changes in the build system environment changed and in which way . Things to get started:Jenkins boot (including server version) and shutdown.Plugin installations, removals, upgrades and downgrades (including versions). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [audit-trail] (JENKINS-22246) Audit Trail Plugin should record system changes
Mr Cinquero created JENKINS-22246 Audit Trail Plugin should record system changes Issue Type: Improvement Assignee: Alan Harder Components: audit-trail Created: 18/Mar/14 2:31 PM Description: It would be extremely useful to have a protocol when the build system environment changed and in which way. Things to get started: Jenkins boot (including server version) and shutdown. Plugin installations, removals, upgrades and downgrades (including versions). Project: Jenkins Priority: Major Reporter: Mr Cinquero This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22089) android userdata.img not found and skin name not valid
Mr Cinquero commented on JENKINS-22089 android userdata.img not found and skin name not valid https://code.google.com/p/android/issues/detail?id=66980 Hint: try to omit the abi definition on the command line. Should be selected through the target. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22089) android userdata.img not found and skin name not valid
Mr Cinquero commented on JENKINS-22089 android userdata.img not found and skin name not valid the plugin should also add -no-audio because there is an open bug with the emulator: it enters and endless loop on headless kvm machines with more recent images This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22089) android userdata.img not found and skin name not valid
Mr Cinquero edited a comment on JENKINS-22089 android userdata.img not found and skin name not valid hmmm.. AVD auto-setup now worked with OS version 2.3.3 after I had created the AVD for 4.0.3 manually... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22089) android userdata.img not found and skin name not valid
Mr Cinquero commented on JENKINS-22089 android userdata.img not found and skin name not valid hmmm.. ACD auto-setup now worked with OS version 2.3.3 after I had created the AVD for 4.0.3 manually... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22089) android userdata.img not found and skin name not valid
Mr Cinquero commented on JENKINS-22089 android userdata.img not found and skin name not valid hmmm... looks like the command line avd manager is broken. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22089) android userdata.img not found and skin name not valid
Mr Cinquero updated JENKINS-22089 android userdata.img not found and skin name not valid Change By: Mr Cinquero (07/Mar/14 3:58 PM) Description: I let the plugin install everything needed (from scratch!) and activated "run emulator" feature.For Android OS Version 3.2 I get:$ /var/lib/jenkins/tools/android-sdk/tools/android list target[android] Using Android SDK: /var/lib/jenkins/tools/android-sdk[android] Creating Android AVD: /var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_android-13.avd[android] /var/lib/jenkins/tools/android-sdk/tools/android create avd -f -a -c 512M -s WVGA800 -n hudson_en-US_160_WVGA_android-13 -t android-13 Error: 'WVGA800' is not a valid skin name or size (NNNxMMM) [android] Could not create Android emulator: Failed to run AVD creation commandFinished: NOT_BUILTFor OS version 4+ I get:$ /var/lib/jenkins/tools/android-sdk/tools/android list target[android] Using Android SDK: /var/lib/jenkins/tools/android-sdk[android] Creating Android AVD: /var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_android-15_armeabi-v7a.avd[android] /var/lib/jenkins/tools/android-sdk/tools/android create avd -f -a -c 512M -s WVGA800 -n hudson_en-US_160_WVGA_android-15_armeabi-v7a -t android-15 --abi armeabi-v7a Error: Unable to find a 'userdata.img' file for ABI armeabi-v7a to copy into the AVD folder. [android] Could not create Android emulator: Failed to run AVD creation commandFinished: NOT_BUILT This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22089) android userdata.img not found and skin name not valid
Mr Cinquero created JENKINS-22089 android userdata.img not found and skin name not valid Issue Type: Bug Affects Versions: current Assignee: Christopher Orr Components: android-emulator Created: 07/Mar/14 3:41 PM Description: I let the plugin install everything needed and activated "run emulator" feature. For Android OS Version 3.2 I get: $ /var/lib/jenkins/tools/android-sdk/tools/android list target [android] Using Android SDK: /var/lib/jenkins/tools/android-sdk [android] Creating Android AVD: /var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_android-13.avd [android] /var/lib/jenkins/tools/android-sdk/tools/android create avd -f -a -c 512M -s WVGA800 -n hudson_en-US_160_WVGA_android-13 -t android-13 Error: 'WVGA800' is not a valid skin name or size (NNNxMMM) [android] Could not create Android emulator: Failed to run AVD creation command Finished: NOT_BUILT For OS version 4+ I get: $ /var/lib/jenkins/tools/android-sdk/tools/android list target [android] Using Android SDK: /var/lib/jenkins/tools/android-sdk [android] Creating Android AVD: /var/lib/jenkins/.android/avd/hudson_en-US_160_WVGA_android-15_armeabi-v7a.avd [android] /var/lib/jenkins/tools/android-sdk/tools/android create avd -f -a -c 512M -s WVGA800 -n hudson_en-US_160_WVGA_android-15_armeabi-v7a -t android-15 --abi armeabi-v7a Error: Unable to find a 'userdata.img' file for ABI armeabi-v7a to copy into the AVD folder. [android] Could not create Android emulator: Failed to run AVD creation command Finished: NOT_BUILT Environment: jenkins 1.553, up-to-date Ubuntu 12.04 LTS on amd64, using jdk7 from distro Project: Jenkins Priority: Major Reporter: Mr Cinquero This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
