[JIRA] (JENKINS-13928) bad version number at offiset=6
[ https://issues.jenkins-ci.org/browse/JENKINS-13928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163247#comment-163247 ] Christian Wolfgang commented on JENKINS-13928: -- Is this the version number reported in the "installed plugins" tab or in the console output? I am well aware of the wrong version number in the console output and it will be fixed in the next version. > bad version number at offiset=6 > --- > > Key: JENKINS-13928 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13928 > Project: Jenkins > Issue Type: Bug > Components: clearcase-ucm >Affects Versions: current > Environment: windows xp , tomcat 6.0.35, jenkins 1.465, > clearcase-ucm-plugin 1.0.7 >Reporter: Carl Chen >Assignee: Christian Wolfgang > Labels: plugin > > jenkins runs well, but after install this plugin, it reports bad version > number error. -- 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-13928) bad version number at offiset=6
[ https://issues.jenkins-ci.org/browse/JENKINS-13928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Wolfgang reassigned JENKINS-13928: Assignee: Christian Wolfgang > bad version number at offiset=6 > --- > > Key: JENKINS-13928 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13928 > Project: Jenkins > Issue Type: Bug > Components: clearcase-ucm >Affects Versions: current > Environment: windows xp , tomcat 6.0.35, jenkins 1.465, > clearcase-ucm-plugin 1.0.7 >Reporter: Carl Chen >Assignee: Christian Wolfgang > Labels: plugin > > jenkins runs well, but after install this plugin, it reports bad version > number error. -- 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-13932) React to failed APK install
Hamilton Turner created JENKINS-13932: - Summary: React to failed APK install Key: JENKINS-13932 URL: https://issues.jenkins-ci.org/browse/JENKINS-13932 Project: Jenkins Issue Type: Improvement Components: android-emulator Affects Versions: current Reporter: Hamilton Turner Assignee: Christopher Orr Priority: Minor Currently a failed APK install won't mark the build as failed - it likely should. Eg: [tmp] $ /home/foo/tools/android-sdk/platform-tools/adb -s localhost:55208 install -r benchmark.apk 783 KB/s (62492 bytes in 0.077s) pkg: /data/local/tmp/benchmark.apk Failure [INSTALL_FAILED_OLDER_SDK] -- 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-13931) sd card option requires multi-configuration axis name to be in capital letters
Hamilton Turner created JENKINS-13931:
-
Summary: sd card option requires multi-configuration axis name to
be in capital letters
Key: JENKINS-13931
URL: https://issues.jenkins-ci.org/browse/JENKINS-13931
Project: Jenkins
Issue Type: Bug
Components: android-emulator
Affects Versions: current
Reporter: Hamilton Turner
Assignee: Christopher Orr
Priority: Minor
Any text entered into the SD card option is automatically capitalized, which
can be a pain. For example, a multi-config with a user-defined axis of sd =
{16M 32M} can be entered into the SD card option box as ${sd}. However, all
builds fail, and looking at the project configuration shows that the text was
changed to ${SD}. The offending code is in EmulatorConfig.java:
sdCardSize = sdCardSize.toUpperCase().replaceAll("[ B]", "");
A similar issue probably exists with locale due to this:
deviceLocale = deviceLocale.substring(0, 2).toLowerCase() +"_"
+ deviceLocale.substring(3).toUpperCase();
--
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-11973) AVD should be in workspace instead of system-global
[ https://issues.jenkins-ci.org/browse/JENKINS-11973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-11973 started by Christopher Orr. > AVD should be in workspace instead of system-global > --- > > Key: JENKINS-11973 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11973 > Project: Jenkins > Issue Type: New Feature > Components: android-emulator >Reporter: Jørgen Tjernø >Assignee: Christopher Orr > > This relates to JENKINS-11083: It's another solution to the underlying issue. > It'd be nice if AVDs could be generated in the workspace, so that there was > no conflict when two jobs wanted to use the same configuration. In addition, > this would allow "concurrent builds" on the same slave for Android > Emulator-dependent jobs. -- 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-11973) AVD should be in workspace instead of system-global
[ https://issues.jenkins-ci.org/browse/JENKINS-11973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-11973 stopped by Hamilton Turner. > AVD should be in workspace instead of system-global > --- > > Key: JENKINS-11973 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11973 > Project: Jenkins > Issue Type: New Feature > Components: android-emulator >Reporter: Jørgen Tjernø >Assignee: Christopher Orr > > This relates to JENKINS-11083: It's another solution to the underlying issue. > It'd be nice if AVDs could be generated in the workspace, so that there was > no conflict when two jobs wanted to use the same configuration. In addition, > this would allow "concurrent builds" on the same slave for Android > Emulator-dependent jobs. -- 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-13464) Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459
[ https://issues.jenkins-ci.org/browse/JENKINS-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gergely Nagy updated JENKINS-13464: --- Attachment: stacktraceflow.txt > Using Other Views filter, I'm getting a stack overflow error after update to > Jenkins 1.459 > -- > > Key: JENKINS-13464 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13464 > Project: Jenkins > Issue Type: Bug > Components: sectioned-view, view-job-filters >Reporter: Vincent Latombe >Assignee: Jacob Robertson >Priority: Blocker > Attachments: StackOverflow.txt, stacktraceflow.txt > > > Due to > https://github.com/jenkinsci/jenkins/commit/85e13303f8cfbebeb7dab347fda8ccf4069070b6 > , any view using Other Views filter now gets a StackOverflowError. > The reason is that it uses a wrong way of retrieving the referenced view, by > getting first 'all' the views. -- 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-13464) Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459
[ https://issues.jenkins-ci.org/browse/JENKINS-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163246#comment-163246 ] Gergely Nagy edited comment on JENKINS-13464 at 5/28/12 9:54 PM: - We were hit by this too - thanks for reporting. It basically cause intermittent hungs, the "no HTTP reply kind" (https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+is+hanging). I haven't found a good way to reproduce this yet, but I'm getting a slightly different log for the endless recursion - attaching. Extract: at hudson.views.AbstractIncludeExcludeJobFilter.filter(AbstractIncludeExcludeJobFilter.java:57) at hudson.model.ListView.getItems(ListView.java:162) at hudson.model.ListView.getItems(ListView.java:58) at hudson.security.AuthorizationStrategy$1.hasPermission(AuthorizationStrategy.java:103) at hudson.security.ACL.hasPermission(ACL.java:65) at hudson.model.View.hasPermission(View.java:503) at hudson.model.ViewGroupMixIn.getViews(ViewGroupMixIn.java:115) at jenkins.model.Jenkins.getViews(Jenkins.java:1370) at hudson.views.OtherViewsFilter.getAllViews(OtherViewsFilter.java:148) at hudson.views.UnclassifiedJobsFilter.doFilter(UnclassifiedJobsFilter.java:27) at hudson.views.AbstractIncludeExcludeJobFilter.filter(AbstractIncludeExcludeJobFilter.java:57) was (Author: inger): We were hit by this too - thanks for reporting. It basically cause intermittent hungs, the "no HTTP reply kind" (https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+is+hanging). I haven't found a good way to reproduce this yet, but I'm getting a slightly different log for the endless recursion - attaching. Extract: at hudson.model.ListView.getItems(ListView.java:138) at hudson.model.ListView.getItems(ListView.java:58) at hudson.security.AuthorizationStrategy$1.hasPermission(AuthorizationStrategy.java:103) at hudson.security.ACL.hasPermission(ACL.java:65) at hudson.model.View.hasPermission(View.java:503) at hudson.model.ViewGroupMixIn.getViews(ViewGroupMixIn.java:115) at jenkins.model.Jenkins.getViews(Jenkins.java:1370) at hudson.views.OtherViewsFilter.getAllViews(OtherViewsFilter.java:148) at hudson.views.UnclassifiedJobsFilter.doFilter(UnclassifiedJobsFilter.java:27) at hudson.views.AbstractIncludeExcludeJobFilter.filter(AbstractIncludeExcludeJobFilter.java:57) at hudson.model.ListView.getItems(ListView.java:162) at hudson.model.ListView.getItems(ListView.java:58) > Using Other Views filter, I'm getting a stack overflow error after update to > Jenkins 1.459 > -- > > Key: JENKINS-13464 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13464 > Project: Jenkins > Issue Type: Bug > Components: sectioned-view, view-job-filters >Reporter: Vincent Latombe >Assignee: Jacob Robertson >Priority: Blocker > Attachments: StackOverflow.txt > > > Due to > https://github.com/jenkinsci/jenkins/commit/85e13303f8cfbebeb7dab347fda8ccf4069070b6 > , any view using Other Views filter now gets a StackOverflowError. > The reason is that it uses a wrong way of retrieving the referenced view, by > getting first 'all' the views. -- 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-13464) Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459
[ https://issues.jenkins-ci.org/browse/JENKINS-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163246#comment-163246 ] Gergely Nagy edited comment on JENKINS-13464 at 5/28/12 9:52 PM: - We were hit by this too - thanks for reporting. It basically cause intermittent hungs, the "no HTTP reply kind" (https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+is+hanging). I haven't found a good way to reproduce this yet, but I'm getting a slightly different log for the endless recursion - attaching. Extract: at hudson.model.ListView.getItems(ListView.java:138) at hudson.model.ListView.getItems(ListView.java:58) at hudson.security.AuthorizationStrategy$1.hasPermission(AuthorizationStrategy.java:103) at hudson.security.ACL.hasPermission(ACL.java:65) at hudson.model.View.hasPermission(View.java:503) at hudson.model.ViewGroupMixIn.getViews(ViewGroupMixIn.java:115) at jenkins.model.Jenkins.getViews(Jenkins.java:1370) at hudson.views.OtherViewsFilter.getAllViews(OtherViewsFilter.java:148) at hudson.views.UnclassifiedJobsFilter.doFilter(UnclassifiedJobsFilter.java:27) at hudson.views.AbstractIncludeExcludeJobFilter.filter(AbstractIncludeExcludeJobFilter.java:57) at hudson.model.ListView.getItems(ListView.java:162) at hudson.model.ListView.getItems(ListView.java:58) was (Author: inger): We were hit by this too - thanks for reporting. It basically cause intermittent hungs, the "no HTTP reply kind" (https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+is+hanging). I haven't found a good way to reproduce this yet, but I'm getting a slightly different log for the endless recursion - attaching. > Using Other Views filter, I'm getting a stack overflow error after update to > Jenkins 1.459 > -- > > Key: JENKINS-13464 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13464 > Project: Jenkins > Issue Type: Bug > Components: sectioned-view, view-job-filters >Reporter: Vincent Latombe >Assignee: Jacob Robertson >Priority: Blocker > Attachments: StackOverflow.txt > > > Due to > https://github.com/jenkinsci/jenkins/commit/85e13303f8cfbebeb7dab347fda8ccf4069070b6 > , any view using Other Views filter now gets a StackOverflowError. > The reason is that it uses a wrong way of retrieving the referenced view, by > getting first 'all' the views. -- 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-13464) Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459
[ https://issues.jenkins-ci.org/browse/JENKINS-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163246#comment-163246 ] Gergely Nagy commented on JENKINS-13464: We were hit by this too - thanks for reporting. It basically cause intermittent hungs, the "no HTTP reply kind" (https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+is+hanging). I haven't found a good way to reproduce this yet, but I'm getting a slightly different log for the endless recursion - attaching. > Using Other Views filter, I'm getting a stack overflow error after update to > Jenkins 1.459 > -- > > Key: JENKINS-13464 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13464 > Project: Jenkins > Issue Type: Bug > Components: sectioned-view, view-job-filters >Reporter: Vincent Latombe >Assignee: Jacob Robertson >Priority: Blocker > Attachments: StackOverflow.txt > > > Due to > https://github.com/jenkinsci/jenkins/commit/85e13303f8cfbebeb7dab347fda8ccf4069070b6 > , any view using Other Views filter now gets a StackOverflowError. > The reason is that it uses a wrong way of retrieving the referenced view, by > getting first 'all' the views. -- 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-13420) Unable to serialize hudson.plugins.android_emulator.SdkInstaller
[
https://issues.jenkins-ci.org/browse/JENKINS-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163245#comment-163245
]
Hamilton Turner commented on JENKINS-13420:
---
Should be fixed once it's merged :
https://github.com/jenkinsci/android-emulator-plugin/pull/10
> Unable to serialize hudson.plugins.android_emulator.SdkInstaller
>
>
> Key: JENKINS-13420
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13420
> Project: Jenkins
> Issue Type: Bug
> Components: android-emulator
>Affects Versions: current
> Environment: Job running on a slave started via Java Web Start.
> Server running on the cloud, slave running inside our office.
>Reporter: Juraci P. Kroehling
>Assignee: Christopher Orr
>
> When starting a job which requires an Android SDK, we see the exception
> below. This happens if we use ANDROID_HOME pointing to an existing
> installation (in this case, the download of the SDK is not performed) as well
> as with automatic download of the needed "tools".
> {code}
> Started by user dashboard
> Building remotely on dashboard in workspace
> /tmp/jenkins/workspace/CI-emulatortest
> [android] No Android SDK found; let's install it automatically...
> Downloading and installing Android SDK from
> http://dl.google.com/android/android-sdk_r16-linux.tgz
> [android] Base SDK installed successfully
> [android] Going to install required Android SDK components...
> [android] Installing the 'platform-tool,tool' SDK component(s)...
> $ /tmp/jenkins/tools/android-sdk/tools/android update sdk -o -u -t
> platform-tool,tool
> Refresh Sources:
> Fetching https://dl-ssl.google.com/android/repository/addons_list-1.xml
> Validate XML
> Parse XML
> Fetched Add-ons List successfully
> Refresh Sources
> Fetching URL: https://dl-ssl.google.com/android/repository/repository-5.xml
> Validate XML: https://dl-ssl.google.com/android/repository/repository-5.xml
> Parse XML:https://dl-ssl.google.com/android/repository/repository-5.xml
> Fetching URL: https://dl-ssl.google.com/android/repository/addon.xml
> Validate XML: https://dl-ssl.google.com/android/repository/addon.xml
> Fetching URL: http://dl.htcdev.com/sdk/addon.xml
> Validate XML: http://dl.htcdev.com/sdk/addon.xml
> Parse XML:http://dl.htcdev.com/sdk/addon.xml
> Fetching URL: http://software.intel.com/sites/landingpage/android/addon.xml
> Validate XML: http://software.intel.com/sites/landingpage/android/addon.xml
> Parse XML:http://software.intel.com/sites/landingpage/android/addon.xml
> Fetching URL: http://www.echobykyocera.com/download/echo_repository.xml
> Validate XML: http://www.echobykyocera.com/download/echo_repository.xml
> Parse XML:http://www.echobykyocera.com/download/echo_repository.xml
> Fetching URL: http://developer.lgmobile.com/sdk/android/repository.xml
> Validate XML: http://developer.lgmobile.com/sdk/android/repository.xml
> Parse XML:http://developer.lgmobile.com/sdk/android/repository.xml
> Fetching URL: http://android-sdk-addons.motodevupdate.com/addons.xml
> Validate XML: http://android-sdk-addons.motodevupdate.com/addons.xml
> Parse XML:http://android-sdk-addons.motodevupdate.com/addons.xml
> Fetching URL:
> http://innovator.samsungmobile.com/android/repository/repository.xml
> Validate XML:
> http://innovator.samsungmobile.com/android/repository/repository.xml
> Parse XML:
> http://innovator.samsungmobile.com/android/repository/repository.xml
> Fetching URL: http://developer.sonyericsson.com/edk/android/repository.xml
> Validate XML: http://developer.sonyericsson.com/edk/android/repository.xml
> Parse XML:http://developer.sonyericsson.com/edk/android/repository.xml
> Refresh Sources:
> Fetching URL: https://dl-ssl.google.com/android/repository/addon.xml
> Validate XML: https://dl-ssl.google.com/android/repository/addon.xml
> Installing Archives:
> Preparing to install archives
> Downloading Android SDK Platform-tools, revision 11
> (22%, 1087 KiB/s, 7 seconds left)
> (41%, 1354 KiB/s, 4 seconds left)
> (59%, 1468 KiB/s, 2 seconds left)
> (77%, 1537 KiB/s, 1 seconds left)
> (94%, 1565 KiB/s, 0 seconds left)
> Installing Android SDK Platform-tools, revision 11
> Stopping ADB server failed (code -1).
> Unzipping Android SDK Platform-tools, revision 11 (4%)
> Unzipping Android SDK Platform-tools, revision 11 (5%)
> Unzipping Android SDK Platform-tools, revision 11 (6%)
> Unzipping Android SDK Platform-tools, revision 11 (9%)
> Unzipping Android SDK Platform-tools, revision 11 (18%)
> Unzipping Android SDK Platform-tools, revision 11 (19%)
> Unzipping Android SDK Platform-tools, revision 11 (99%)
> Installed Android SDK Platform
[JIRA] (JENKINS-13814) java.lang.OutOfMemoryError exception when getting the remote log
[
https://issues.jenkins-ci.org/browse/JENKINS-13814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Clarke resolved JENKINS-13814.
--
Assignee: Michael Clarke
Resolution: Fixed
Fixed by re-applying previously set '-S' filter on rlog command
> java.lang.OutOfMemoryError exception when getting the remote log
>
>
> Key: JENKINS-13814
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13814
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Environment: Jenkins 1.464 on Windows 7 64-bit, 12GB RAM; CVS Plug-in
> 2.4-SNAPSHOT
>Reporter: James Gustafson
>Assignee: Michael Clarke
> Labels: cvs, exception, memory
>
> We are getting a java.lang.OutOfMemoryError exception when getting the remote
> log.
> {quote}
> Started by an SCM change
> Building in workspace C:\x\workspace\project_name_here
> cvs checkout -r BRANCH_NAME_HERE -D 16 May 2012 23:27:38 -0700 -d
> path\projects path/projects
> cvs checkout: Updating path\projects
> cvs checkout: Updating path\projects/dir1
> cvs checkout: Updating path\projects/dir2/dirA
> ... (about 7,224 directories) ...
> cvs checkout: Updating path\projects/dirN
> cvs rlog: Logging path\projects
> ... (about 7,224 directories) ...
> cvs rlog: Logging path\projects/dirN
> FATAL: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> at java.lang.StringCoding$StringDecoder.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.String.(Unknown Source)
> at java.io.ByteArrayOutputStream.toString(Unknown Source)
> at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:540)
> at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:415)
> at hudson.scm.CVSSCM.checkout(CVSSCM.java:825)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
> at
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
> at hudson.model.Run.run(Run.java:1434)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:239)
> {quote}
> Some notes:
> - The path/ and path\ comes from the "Remote Name"/"Local Name" settings
> solution from Issue JENKINS-13264
> - We are using Jenkins 1.464 with the 2.4-SNAPSHOT version of the CVS plugin,
> but may not have been caused by this specific version
> - The arguments setting in the jenkins.xml file currently has -Xms1024m
> (anything larger and Jenkins service won't start)
> - The CVS module has many legacy projects spread out, and thus, contains more
> than 7,000 directories and many more files
> - Things had worked with the 1.6 plug-in & CVSNT client, but it also
> occasionally timed out getting the changelog, hence our testing of the 2.x
> plug-ins
--
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-13814) java.lang.OutOfMemoryError exception when getting the remote log
[
https://issues.jenkins-ci.org/browse/JENKINS-13814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
> java.lang.OutOfMemoryError exception when getting the remote log
>
>
> Key: JENKINS-13814
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13814
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Environment: Jenkins 1.464 on Windows 7 64-bit, 12GB RAM; CVS Plug-in
> 2.4-SNAPSHOT
>Reporter: James Gustafson
> Labels: cvs, exception, memory
>
> We are getting a java.lang.OutOfMemoryError exception when getting the remote
> log.
> {quote}
> Started by an SCM change
> Building in workspace C:\x\workspace\project_name_here
> cvs checkout -r BRANCH_NAME_HERE -D 16 May 2012 23:27:38 -0700 -d
> path\projects path/projects
> cvs checkout: Updating path\projects
> cvs checkout: Updating path\projects/dir1
> cvs checkout: Updating path\projects/dir2/dirA
> ... (about 7,224 directories) ...
> cvs checkout: Updating path\projects/dirN
> cvs rlog: Logging path\projects
> ... (about 7,224 directories) ...
> cvs rlog: Logging path\projects/dirN
> FATAL: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> at java.lang.StringCoding$StringDecoder.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.String.(Unknown Source)
> at java.io.ByteArrayOutputStream.toString(Unknown Source)
> at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:540)
> at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:415)
> at hudson.scm.CVSSCM.checkout(CVSSCM.java:825)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
> at
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
> at hudson.model.Run.run(Run.java:1434)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:239)
> {quote}
> Some notes:
> - The path/ and path\ comes from the "Remote Name"/"Local Name" settings
> solution from Issue JENKINS-13264
> - We are using Jenkins 1.464 with the 2.4-SNAPSHOT version of the CVS plugin,
> but may not have been caused by this specific version
> - The arguments setting in the jenkins.xml file currently has -Xms1024m
> (anything larger and Jenkins service won't start)
> - The CVS module has many legacy projects spread out, and thus, contains more
> than 7,000 directories and many more files
> - Things had worked with the 1.6 plug-in & CVSNT client, but it also
> occasionally timed out getting the changelog, hence our testing of the 2.x
> plug-ins
--
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-12598) In 2.0 update you need to specify branch for every module
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clarke resolved JENKINS-12598. -- Assignee: Michael Clarke Resolution: Fixed A change for this was included in the primary snapshot over a month ago > In 2.0 update you need to specify branch for every module > - > > Key: JENKINS-12598 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12598 > Project: Jenkins > Issue Type: Improvement > Components: cvs >Reporter: Ulli Hafner >Assignee: Michael Clarke >Priority: Critical > Attachments: Jenkins_CvsPluginModules.png, > repositoryLocationProposal.png > > > After an upgrade to the new 2.0 version of the cvs plug-in we now need to > specify the "Module location" (trunk, branch) for each module. This is quite > cumbersome if you have a lot of modules. In the 1.x plug-in releases you are > able to select a given branch for all modules in one text field. > While I think the new "feature" has a lot of use cases (i.e., having trunk > and branches mixed), the usability could be improved here. My requirement is > to select/change the branch (or trunk) for all modules in a simple way. > A non-Ajax suggestion would be to have a "default" entry in the Selection, > i.e. Trunk, Branch, Tag, Default. And you can define the default behavior at > the top of the cvs configuration. -- 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-12598) In 2.0 update you need to specify branch for every module
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > In 2.0 update you need to specify branch for every module > - > > Key: JENKINS-12598 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12598 > Project: Jenkins > Issue Type: Improvement > Components: cvs >Reporter: Ulli Hafner >Priority: Critical > Attachments: Jenkins_CvsPluginModules.png, > repositoryLocationProposal.png > > > After an upgrade to the new 2.0 version of the cvs plug-in we now need to > specify the "Module location" (trunk, branch) for each module. This is quite > cumbersome if you have a lot of modules. In the 1.x plug-in releases you are > able to select a given branch for all modules in one text field. > While I think the new "feature" has a lot of use cases (i.e., having trunk > and branches mixed), the usability could be improved here. My requirement is > to select/change the branch (or trunk) for all modules in a simple way. > A non-Ajax suggestion would be to have a "default" entry in the Selection, > i.e. Trunk, Branch, Tag, Default. And you can define the default behavior at > the top of the cvs configuration. -- 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-13420) Unable to serialize hudson.plugins.android_emulator.SdkInstaller
[
https://issues.jenkins-ci.org/browse/JENKINS-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JENKINS-13420 started by Christopher Orr.
> Unable to serialize hudson.plugins.android_emulator.SdkInstaller
>
>
> Key: JENKINS-13420
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13420
> Project: Jenkins
> Issue Type: Bug
> Components: android-emulator
>Affects Versions: current
> Environment: Job running on a slave started via Java Web Start.
> Server running on the cloud, slave running inside our office.
>Reporter: Juraci P. Kroehling
>Assignee: Christopher Orr
>
> When starting a job which requires an Android SDK, we see the exception
> below. This happens if we use ANDROID_HOME pointing to an existing
> installation (in this case, the download of the SDK is not performed) as well
> as with automatic download of the needed "tools".
> {code}
> Started by user dashboard
> Building remotely on dashboard in workspace
> /tmp/jenkins/workspace/CI-emulatortest
> [android] No Android SDK found; let's install it automatically...
> Downloading and installing Android SDK from
> http://dl.google.com/android/android-sdk_r16-linux.tgz
> [android] Base SDK installed successfully
> [android] Going to install required Android SDK components...
> [android] Installing the 'platform-tool,tool' SDK component(s)...
> $ /tmp/jenkins/tools/android-sdk/tools/android update sdk -o -u -t
> platform-tool,tool
> Refresh Sources:
> Fetching https://dl-ssl.google.com/android/repository/addons_list-1.xml
> Validate XML
> Parse XML
> Fetched Add-ons List successfully
> Refresh Sources
> Fetching URL: https://dl-ssl.google.com/android/repository/repository-5.xml
> Validate XML: https://dl-ssl.google.com/android/repository/repository-5.xml
> Parse XML:https://dl-ssl.google.com/android/repository/repository-5.xml
> Fetching URL: https://dl-ssl.google.com/android/repository/addon.xml
> Validate XML: https://dl-ssl.google.com/android/repository/addon.xml
> Fetching URL: http://dl.htcdev.com/sdk/addon.xml
> Validate XML: http://dl.htcdev.com/sdk/addon.xml
> Parse XML:http://dl.htcdev.com/sdk/addon.xml
> Fetching URL: http://software.intel.com/sites/landingpage/android/addon.xml
> Validate XML: http://software.intel.com/sites/landingpage/android/addon.xml
> Parse XML:http://software.intel.com/sites/landingpage/android/addon.xml
> Fetching URL: http://www.echobykyocera.com/download/echo_repository.xml
> Validate XML: http://www.echobykyocera.com/download/echo_repository.xml
> Parse XML:http://www.echobykyocera.com/download/echo_repository.xml
> Fetching URL: http://developer.lgmobile.com/sdk/android/repository.xml
> Validate XML: http://developer.lgmobile.com/sdk/android/repository.xml
> Parse XML:http://developer.lgmobile.com/sdk/android/repository.xml
> Fetching URL: http://android-sdk-addons.motodevupdate.com/addons.xml
> Validate XML: http://android-sdk-addons.motodevupdate.com/addons.xml
> Parse XML:http://android-sdk-addons.motodevupdate.com/addons.xml
> Fetching URL:
> http://innovator.samsungmobile.com/android/repository/repository.xml
> Validate XML:
> http://innovator.samsungmobile.com/android/repository/repository.xml
> Parse XML:
> http://innovator.samsungmobile.com/android/repository/repository.xml
> Fetching URL: http://developer.sonyericsson.com/edk/android/repository.xml
> Validate XML: http://developer.sonyericsson.com/edk/android/repository.xml
> Parse XML:http://developer.sonyericsson.com/edk/android/repository.xml
> Refresh Sources:
> Fetching URL: https://dl-ssl.google.com/android/repository/addon.xml
> Validate XML: https://dl-ssl.google.com/android/repository/addon.xml
> Installing Archives:
> Preparing to install archives
> Downloading Android SDK Platform-tools, revision 11
> (22%, 1087 KiB/s, 7 seconds left)
> (41%, 1354 KiB/s, 4 seconds left)
> (59%, 1468 KiB/s, 2 seconds left)
> (77%, 1537 KiB/s, 1 seconds left)
> (94%, 1565 KiB/s, 0 seconds left)
> Installing Android SDK Platform-tools, revision 11
> Stopping ADB server failed (code -1).
> Unzipping Android SDK Platform-tools, revision 11 (4%)
> Unzipping Android SDK Platform-tools, revision 11 (5%)
> Unzipping Android SDK Platform-tools, revision 11 (6%)
> Unzipping Android SDK Platform-tools, revision 11 (9%)
> Unzipping Android SDK Platform-tools, revision 11 (18%)
> Unzipping Android SDK Platform-tools, revision 11 (19%)
> Unzipping Android SDK Platform-tools, revision 11 (99%)
> Installed Android SDK Platform-tools, revision 11
> Downloading Android SDK Tools, revision 18
> (11%, 1605 KiB/s, 16 seconds left)
> (17%, 1664 KiB/s, 14 seconds left)
> (23%, 1689 KiB/s, 13 seconds left)
>
[JIRA] (JENKINS-13264) fail checkout 2 modules with different path
[ https://issues.jenkins-ci.org/browse/JENKINS-13264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163242#comment-163242 ] Michael Clarke commented on JENKINS-13264: -- Valentin: based in your comment, do you think changing the CVS command to contain backward slashes for the '-d' argument work in both Windows and Linux (i.e. cvs checkout -P -D 29 Mar 2012 11:40:15 +0800 -d lib\flac-1.2.1 lib/flac-1.2.1)? My test machine is Windows Client -> Windows Server so I can't replicate the defect properly. I reckon that changing to use client side redirection would cause CVS not to create CVS control files in the expected location so I'd have to fiddle about a bit, but may be an option if the backslashes 'quick fix' I've suggested doesn't work. > fail checkout 2 modules with different path > --- > > Key: JENKINS-13264 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13264 > Project: Jenkins > Issue Type: Bug > Components: cvs > Environment: linux >Reporter: Eric Co >Assignee: Michael Clarke > Fix For: current > > > I create two cvs modules with the path > lib/flac-1.2.1 > drv/linux/fuse > when it check out, got the error: > cvs checkout -P -D 29 Mar 2012 11:40:15 +0800 -d lib/flac-1.2.1 > lib/flac-1.2.1 > cvs [checkout aborted]: could not change directory to requested checkout > directory `lib': No such file or directory -- 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-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163241#comment-163241 ] Michael Clarke commented on JENKINS-13227: -- Latest snapshot should fix this issue - give it a shot and let me know. > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau >Assignee: Michael Clarke >Priority: Critical > Labels: cvs > Attachments: rlog.txt > > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- 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-13814) java.lang.OutOfMemoryError exception when getting the remote log
[
https://issues.jenkins-ci.org/browse/JENKINS-13814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163239#comment-163239
]
SCM/JIRA link daemon commented on JENKINS-13814:
Code changed in jenkins
User: mc1arke
Path:
src/test/resources/hudson/scm/cvsRlogOutput2.txt
http://jenkins-ci.org/commit/cvs-plugin/05e417c0c13367bda49761f9cab7618fdfba28ca
Log:
[Fixed JENKINS-13227] change log and polling pick up branch changes properly
[Fixed JENKINS-13814] change log applies filers to prevent OOM Exceptions
> java.lang.OutOfMemoryError exception when getting the remote log
>
>
> Key: JENKINS-13814
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13814
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Environment: Jenkins 1.464 on Windows 7 64-bit, 12GB RAM; CVS Plug-in
> 2.4-SNAPSHOT
>Reporter: James Gustafson
> Labels: cvs, exception, memory
>
> We are getting a java.lang.OutOfMemoryError exception when getting the remote
> log.
> {quote}
> Started by an SCM change
> Building in workspace C:\x\workspace\project_name_here
> cvs checkout -r BRANCH_NAME_HERE -D 16 May 2012 23:27:38 -0700 -d
> path\projects path/projects
> cvs checkout: Updating path\projects
> cvs checkout: Updating path\projects/dir1
> cvs checkout: Updating path\projects/dir2/dirA
> ... (about 7,224 directories) ...
> cvs checkout: Updating path\projects/dirN
> cvs rlog: Logging path\projects
> ... (about 7,224 directories) ...
> cvs rlog: Logging path\projects/dirN
> FATAL: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> at java.lang.StringCoding$StringDecoder.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.String.(Unknown Source)
> at java.io.ByteArrayOutputStream.toString(Unknown Source)
> at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:540)
> at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:415)
> at hudson.scm.CVSSCM.checkout(CVSSCM.java:825)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
> at
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
> at hudson.model.Run.run(Run.java:1434)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:239)
> {quote}
> Some notes:
> - The path/ and path\ comes from the "Remote Name"/"Local Name" settings
> solution from Issue JENKINS-13264
> - We are using Jenkins 1.464 with the 2.4-SNAPSHOT version of the CVS plugin,
> but may not have been caused by this specific version
> - The arguments setting in the jenkins.xml file currently has -Xms1024m
> (anything larger and Jenkins service won't start)
> - The CVS module has many legacy projects spread out, and thus, contains more
> than 7,000 directories and many more files
> - Things had worked with the 1.6 plug-in & CVSNT client, but it also
> occasionally timed out getting the changelog, hence our testing of the 2.x
> plug-ins
--
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-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163240#comment-163240 ] SCM/JIRA link daemon commented on JENKINS-13227: Code changed in jenkins User: mc1arke Path: src/test/resources/hudson/scm/cvsRlogOutput2.txt http://jenkins-ci.org/commit/cvs-plugin/05e417c0c13367bda49761f9cab7618fdfba28ca Log: [Fixed JENKINS-13227] change log and polling pick up branch changes properly [Fixed JENKINS-13814] change log applies filers to prevent OOM Exceptions > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau >Assignee: Michael Clarke >Priority: Critical > Labels: cvs > Attachments: rlog.txt > > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- 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-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163238#comment-163238 ] SCM/JIRA link daemon commented on JENKINS-13227: Code changed in jenkins User: mc1arke Path: src/main/java/hudson/scm/CVSSCM.java src/main/java/hudson/scm/CvsChangeLogHelper.java src/test/java/hudson/scm/CvsChangeLogHelperTest.java http://jenkins-ci.org/commit/cvs-plugin/cd31307e33bc3749a71e5ad8d9f2a09cf3fd733d Log: [Fixed JENKINS-13227] change log and polling pick up branch changes properly [Fixed JENKINS-13814] change log applies filers to prevent OOM Exceptions > CVS plugin 2.1 does not detect changes > -- > > Key: JENKINS-13227 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 > Project: Jenkins > Issue Type: Bug > Components: cvs >Reporter: Guillaume Bilodeau >Assignee: Michael Clarke >Priority: Critical > Labels: cvs > Attachments: rlog.txt > > > As presented in the user group: > https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 > We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS > repository for a few weeks now, without any problems. The CVS plugin (v1.6) > was using the local cvsnt install. > We've since upgraded the CVS plugin to version 2.1 (by manually pinning the > plugin) and since then, CVS changes are not detected. The CVS polling log is > triggered properly, tons of "cvs rlog" instructions are sent, but at the end > "No changes" is displayed. > Using CVS plugin 1.6 the cvs polling command looked like this (executed at > 5:26:21 PM EDT): > cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D > "Thursday, March 22, 2012 9:26:21 PM UTC" > Using CVS plugin 2.1, the last cvs checkout command looked like this > (executed at 11:56:16 AM EDT): > cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 > 11:56:16 EDT -d portailInt portailInt > We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- 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-13814) java.lang.OutOfMemoryError exception when getting the remote log
[
https://issues.jenkins-ci.org/browse/JENKINS-13814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163237#comment-163237
]
SCM/JIRA link daemon commented on JENKINS-13814:
Code changed in jenkins
User: mc1arke
Path:
src/main/java/hudson/scm/CVSSCM.java
src/main/java/hudson/scm/CvsChangeLogHelper.java
src/test/java/hudson/scm/CvsChangeLogHelperTest.java
http://jenkins-ci.org/commit/cvs-plugin/cd31307e33bc3749a71e5ad8d9f2a09cf3fd733d
Log:
[Fixed JENKINS-13227] change log and polling pick up branch changes properly
[Fixed JENKINS-13814] change log applies filers to prevent OOM Exceptions
> java.lang.OutOfMemoryError exception when getting the remote log
>
>
> Key: JENKINS-13814
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13814
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Environment: Jenkins 1.464 on Windows 7 64-bit, 12GB RAM; CVS Plug-in
> 2.4-SNAPSHOT
>Reporter: James Gustafson
> Labels: cvs, exception, memory
>
> We are getting a java.lang.OutOfMemoryError exception when getting the remote
> log.
> {quote}
> Started by an SCM change
> Building in workspace C:\x\workspace\project_name_here
> cvs checkout -r BRANCH_NAME_HERE -D 16 May 2012 23:27:38 -0700 -d
> path\projects path/projects
> cvs checkout: Updating path\projects
> cvs checkout: Updating path\projects/dir1
> cvs checkout: Updating path\projects/dir2/dirA
> ... (about 7,224 directories) ...
> cvs checkout: Updating path\projects/dirN
> cvs rlog: Logging path\projects
> ... (about 7,224 directories) ...
> cvs rlog: Logging path\projects/dirN
> FATAL: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> at java.lang.StringCoding$StringDecoder.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.String.(Unknown Source)
> at java.io.ByteArrayOutputStream.toString(Unknown Source)
> at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:540)
> at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:415)
> at hudson.scm.CVSSCM.checkout(CVSSCM.java:825)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
> at
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
> at hudson.model.Run.run(Run.java:1434)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:239)
> {quote}
> Some notes:
> - The path/ and path\ comes from the "Remote Name"/"Local Name" settings
> solution from Issue JENKINS-13264
> - We are using Jenkins 1.464 with the 2.4-SNAPSHOT version of the CVS plugin,
> but may not have been caused by this specific version
> - The arguments setting in the jenkins.xml file currently has -Xms1024m
> (anything larger and Jenkins service won't start)
> - The CVS module has many legacy projects spread out, and thus, contains more
> than 7,000 directories and many more files
> - Things had worked with the 1.6 plug-in & CVSNT client, but it also
> occasionally timed out getting the changelog, hence our testing of the 2.x
> plug-ins
--
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-13853) Conditional step is not being executed by UserCause
[ https://issues.jenkins-ci.org/browse/JENKINS-13853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163236#comment-163236 ] Leandro Conca commented on JENKINS-13853: - I just confirmed that it is working now on version 0.10 of run-condition-plugin. Thanks! > Conditional step is not being executed by UserCause > --- > > Key: JENKINS-13853 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13853 > Project: Jenkins > Issue Type: Bug > Components: conditional-buildstep, run-condition >Affects Versions: current >Reporter: Leandro Conca >Assignee: domi > Attachments: timer-config.png, timer-console-output.png, > user-config.png, user-console-output.png > > > When a conditional step is created on a job with the conditional being Build > Cause (UserCause), the step is not executed even if the build was triggered > manually by a User. > Steps to reproduce: > - Create a new freestyle job > - Add a conditional step with Build Cause (UserCause) to performe some action > (echo something with batch for example) > - Trigger the build manually. > The step is not executed. > The attachments show the job configuration and actual console output and a > similar job with another Build Cause (TimerTrigger) showing the step working. > I am not sure if this problem is related to the conditional-buildstep plugin > or run-condition, so I added both in the issue. -- 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-13814) java.lang.OutOfMemoryError exception when getting the remote log
[
https://issues.jenkins-ci.org/browse/JENKINS-13814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163235#comment-163235
]
Michael Clarke commented on JENKINS-13814:
--
The issue is being caused by the CVS rlog command not having any filters set so
returning headers for every file within the module. This will affect any
repository with a lot of files in it (both active files and those in the attic)
and is most likely to result in an out of memory error at the point the byte
array the log is created in is converted to a String). I'm going to be
committing a change tonight that sets filters so should prevent this issue.
> java.lang.OutOfMemoryError exception when getting the remote log
>
>
> Key: JENKINS-13814
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13814
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Environment: Jenkins 1.464 on Windows 7 64-bit, 12GB RAM; CVS Plug-in
> 2.4-SNAPSHOT
>Reporter: James Gustafson
> Labels: cvs, exception, memory
>
> We are getting a java.lang.OutOfMemoryError exception when getting the remote
> log.
> {quote}
> Started by an SCM change
> Building in workspace C:\x\workspace\project_name_here
> cvs checkout -r BRANCH_NAME_HERE -D 16 May 2012 23:27:38 -0700 -d
> path\projects path/projects
> cvs checkout: Updating path\projects
> cvs checkout: Updating path\projects/dir1
> cvs checkout: Updating path\projects/dir2/dirA
> ... (about 7,224 directories) ...
> cvs checkout: Updating path\projects/dirN
> cvs rlog: Logging path\projects
> ... (about 7,224 directories) ...
> cvs rlog: Logging path\projects/dirN
> FATAL: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> at java.lang.StringCoding$StringDecoder.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.String.(Unknown Source)
> at java.io.ByteArrayOutputStream.toString(Unknown Source)
> at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:540)
> at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:415)
> at hudson.scm.CVSSCM.checkout(CVSSCM.java:825)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
> at
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
> at hudson.model.Run.run(Run.java:1434)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:239)
> {quote}
> Some notes:
> - The path/ and path\ comes from the "Remote Name"/"Local Name" settings
> solution from Issue JENKINS-13264
> - We are using Jenkins 1.464 with the 2.4-SNAPSHOT version of the CVS plugin,
> but may not have been caused by this specific version
> - The arguments setting in the jenkins.xml file currently has -Xms1024m
> (anything larger and Jenkins service won't start)
> - The CVS module has many legacy projects spread out, and thus, contains more
> than 7,000 directories and many more files
> - Things had worked with the 1.6 plug-in & CVSNT client, but it also
> occasionally timed out getting the changelog, hence our testing of the 2.x
> plug-ins
--
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-13239) ThinBackup puts Jenkins into Shutdown (repeatedly) . . . revisited
[ https://issues.jenkins-ci.org/browse/JENKINS-13239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163234#comment-163234 ] Gary Sorhaindo commented on JENKINS-13239: -- Many thanks for your prompt response Thomas. And I agree with what you say - a different message, which is abortable would be great, if this is possible. But in the mean time - you said that "you cannot fall in a situation where a job modifies data while the backup is running". With regard to that statement, what happens if I de-select the "Wait until Jenkins/Hudson is idle to perform a backup" option that was introduced in Thin backup 1.6? When using this option, do I risk making corrupt backups? Thanks in advance. Gary > ThinBackup puts Jenkins into Shutdown (repeatedly) . . . revisited > -- > > Key: JENKINS-13239 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13239 > Project: Jenkins > Issue Type: Bug > Components: thinBackup >Affects Versions: current > Environment: Win7, approx 100 Projects, incremental backups weekdays, > full backup Sunday >Reporter: Frank Merrow >Assignee: Thomas Fürer > Attachments: shutdown.log > > > One of my fellow workers claimed thinBackup was taking Jenkins down, sure > enough I found that the case myself this morning. > Shutdown could not be cancelled (it would go down, but immediately be > reasserted). ThinBackup had some messages about waiting for quiet mode, but > there also seemed to be an exception related to cancelling shutdown, scanning > with my non-Java eye, it wasn't clear it the exception was thinBackup related > or not. > End of Jenkins log provided -- 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-9803) Problems with the jelly cache?!
[ https://issues.jenkins-ci.org/browse/JENKINS-9803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163233#comment-163233 ] evernat commented on JENKINS-9803: -- Did it appear again? Or can we close this issue? > Problems with the jelly cache?! > --- > > Key: JENKINS-9803 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9803 > Project: Jenkins > Issue Type: Bug > Components: core > Environment: Jenkins 1.404, Ubuntu 10.04 server, Sun Java 1.6 >Reporter: rsandell > > Occurred today when trying to open a view with nested views, after a couple > of days running without problems. > Loading the view-config into another server does _not_ reproduce it. > But it has probably not anything to do with the nested views because the > exact same stack trace appears when I try to look at some (but not all) > build-slave pages. > com.google.common.collect.ComputationException: java.lang.NullPointerException > > com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:218) > > com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100) > > com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515) > org.kohsuke.stapler.AbstractTearOff.findScript(AbstractTearOff.java:65) > org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:74) > org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561) > org.kohsuke.stapler.Stapler.invoke(Stapler.java:646) > org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:233) > > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) > org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561) > org.kohsuke.stapler.Stapler.invoke(Stapler.java:646) > org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) > org.kohsuke.stapler.Stapler.service(Stapler.java:159) > javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94) > net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:157) > net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:131) > > net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:82) > > org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) > hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97) > > hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:52) > hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97) > hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86) > hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) > > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) > > hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) > > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > > org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) > > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > > org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) > > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > > org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) > > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > > org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) > > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > > org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) > > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > > org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) > > hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) > > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > > hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) > hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) > > hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA a
[JIRA] (JENKINS-13717) Mercurial URL hook for triggering polling doesn't work with user/pass set in the repository URL
[ https://issues.jenkins-ci.org/browse/JENKINS-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163232#comment-163232 ] Gonzalo Sainz-Trapaga commented on JENKINS-13717: - ¿Can someone try this out? It's a big annoyance and a trivial patch. > Mercurial URL hook for triggering polling doesn't work with user/pass set in > the repository URL > --- > > Key: JENKINS-13717 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13717 > Project: Jenkins > Issue Type: Bug > Components: mercurial >Affects Versions: current >Reporter: Gonzalo Sainz-Trapaga >Assignee: Kohsuke Kawaguchi > Attachments: strip-credentials.patch > > > This is basically the equivalent of JENKINS-13410 for the Mercurial plugin. > If I set the repo URL to something on the lines of > https://user:pass@url/repo, if I use the notifyCommit hook provided since > 1.38 I get a "No mercurial jobs found" message from the server. > Command line is: > $ curl https://jenkins/mercurial/notifyCommit?url=https://user:pass@url/repo > (copy pasted from the actual URL in the job setup) -- 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-13929) allow to define a fix name for an IPA
[ https://issues.jenkins-ci.org/browse/JENKINS-13929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi updated JENKINS-13929: --- Priority: Major (was: Blocker) > allow to define a fix name for an IPA > - > > Key: JENKINS-13929 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13929 > Project: Jenkins > Issue Type: New Feature > Components: xcode > Environment: xcode-plugin 1.3.1 >Reporter: domi >Assignee: Arnaud Héritier > > The current implementation always adds the build number to the name of the > IPA. This is not very handy if one wants to use permalinks to the final > artifact - as the name always changes. > There are two possible solutions for this: > - allow the user to define a final name for each IPA > - allow the user to choose whether he wants to add the build number to the > IPA name -- 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-13930) "Custom xcodebuild arguments" has no help
[ https://issues.jenkins-ci.org/browse/JENKINS-13930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi updated JENKINS-13930: --- Priority: Minor (was: Blocker) > "Custom xcodebuild arguments" has no help > - > > Key: JENKINS-13930 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13930 > Project: Jenkins > Issue Type: Bug > Components: xcode > Environment: 1.3.1 >Reporter: domi >Assignee: Arnaud Héritier >Priority: Minor > > clicking the help icon for "Custom xcodebuild arguments" results in an error. -- 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-13930) "Custom xcodebuild arguments" has no help
domi created JENKINS-13930: -- Summary: "Custom xcodebuild arguments" has no help Key: JENKINS-13930 URL: https://issues.jenkins-ci.org/browse/JENKINS-13930 Project: Jenkins Issue Type: Bug Components: xcode Environment: 1.3.1 Reporter: domi Assignee: Arnaud Héritier Priority: Blocker clicking the help icon for "Custom xcodebuild arguments" results in an error. -- 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-13412) Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings
[
https://issues.jenkins-ci.org/browse/JENKINS-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Beck reopened JENKINS-13412:
---
Minimal example that fails on Windows (Jenkins 1.447.1, Jenkins Gradle Plugin
1.16) when using default parameter value, which was specified in previous
comments:
{code}
false
FOO
true
false
false
false
false
Gradle 1.0 RC3
false
{code}
Build log:
{code}
Started by user anonymous
[Gradle] - Launching build.
[fail gradle call] $ cmd.exe /C
C:\JenkinsHome\tools\Gradle_1.0_RC3\bin\gradle.bat '-DFOO="
"' && exit %%ERRORLEVEL%%
< was unexpected at this time.
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Finished: FAILURE
{code}
> Gradle plugin fails to quote parameters without whitespace when containing
> input/output redirection symbols, e.g. in XML strings
>
>
> Key: JENKINS-13412
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13412
> Project: Jenkins
> Issue Type: Bug
> Components: gradle
>Affects Versions: current
> Environment: Windows Server 2008 R2
> Jenkins 1.424.6
> Jenkins Gradle Plugin 1.12
>Reporter: Daniel Beck
>Assignee: Gregory Boissinot
>
> Gradle plugin explicitly passes job parameters to the "cmd.exe /c gradle.bat"
> call.
> If one of these arguments looks like XML, but does not contain whitespace, it
> is not quoted. This leads to problems with input/output redirection symbols
> (less-than, greater-than)
> Example String Parameter value:
> {code}
>
> {code}
> Results in the following build output:
> {code}
> [workspace] $ cmd.exe /C C:\path\to\gradle.bat -Dfoo= -i && exit
> %%ERRORLEVEL%%
> The system cannot find the file specified.
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Notifying upstream projects of job completion
> {code}
> Real world example:
> Copy artifacts plugin's "Latest successful build" has the value:
> {code}
>
> {code}
> This results in "File not found" errors on Windows Server. Not tested on
> Linux.
--
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
Re: [JIRA] (JENKINS-13814) java.lang.OutOfMemoryError exception when getting the remote log
Increase the jenkins memory to avoid these problems
Thanks
Niranjan
On Mon, May 28, 2012 at 5:14 PM, urban.no...@supergreatmail.com (JIRA) <
nore...@jenkins-ci.org> wrote:
>
>[
> https://issues.jenkins-ci.org/browse/JENKINS-13814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163230#comment-163230]
>
> Urban Novak commented on JENKINS-13814:
> ---
>
> I've encountered the same problem - it looks like there is a memory leak
> either in jenkins (1.465) or cvs plugin(2.4-SNAPSHOT (private-05/25/2012
> 14:52)). Restarting Jenkins fixed the problem, probably only temporarily.
>
> java.lang.OutOfMemoryError: Java heap space
>at java.lang.StringCoding$StringDecoder.decode(Unknown Source)
>at java.lang.StringCoding.decode(Unknown Source)
>at java.lang.StringCoding.decode(Unknown Source)
>at java.lang.String.(Unknown Source)
>at java.io.ByteArrayOutputStream.toString(Unknown Source)
>at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:540)
>at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:415)
>at hudson.scm.CVSSCM.checkout(CVSSCM.java:825)
>at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
>at
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
>at
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
>at hudson.model.Run.run(Run.java:1434)
>at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
>at
> hudson.model.ResourceController.execute(ResourceController.java:88)
>at hudson.model.Executor.run(Executor.java:239)
>
> > java.lang.OutOfMemoryError exception when getting the remote log
> >
> >
> > Key: JENKINS-13814
> > URL: https://issues.jenkins-ci.org/browse/JENKINS-13814
> > Project: Jenkins
> > Issue Type: Bug
> > Components: cvs
> > Environment: Jenkins 1.464 on Windows 7 64-bit, 12GB RAM; CVS
> Plug-in 2.4-SNAPSHOT
> >Reporter: James Gustafson
> > Labels: cvs, exception, memory
> >
> > We are getting a java.lang.OutOfMemoryError exception when getting the
> remote log.
> > {quote}
> > Started by an SCM change
> > Building in workspace C:\x\workspace\project_name_here
> > cvs checkout -r BRANCH_NAME_HERE -D 16 May 2012 23:27:38 -0700 -d
> path\projects path/projects
> > cvs checkout: Updating path\projects
> > cvs checkout: Updating path\projects/dir1
> > cvs checkout: Updating path\projects/dir2/dirA
> > ... (about 7,224 directories) ...
> > cvs checkout: Updating path\projects/dirN
> > cvs rlog: Logging path\projects
> > ... (about 7,224 directories) ...
> > cvs rlog: Logging path\projects/dirN
> > FATAL: Java heap space
> > java.lang.OutOfMemoryError: Java heap space
> > at java.lang.StringCoding$StringDecoder.decode(Unknown Source)
> > at java.lang.StringCoding.decode(Unknown Source)
> > at java.lang.StringCoding.decode(Unknown Source)
> > at java.lang.String.(Unknown Source)
> > at java.io.ByteArrayOutputStream.toString(Unknown Source)
> > at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:540)
> > at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:415)
> > at hudson.scm.CVSSCM.checkout(CVSSCM.java:825)
> > at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
> > at
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
> > at
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
> > at hudson.model.Run.run(Run.java:1434)
> > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> > at
> hudson.model.ResourceController.execute(ResourceController.java:88)
> > at hudson.model.Executor.run(Executor.java:239)
> > {quote}
> > Some notes:
> > - The path/ and path\ comes from the "Remote Name"/"Local Name" settings
> solution from Issue JENKINS-13264
> > - We are using Jenkins 1.464 with the 2.4-SNAPSHOT version of the CVS
> plugin, but may not have been caused by this specific version
> > - The arguments setting in the jenkins.xml file currently has -Xms1024m
> (anything larger and Jenkins service won't start)
> > - The CVS module has many legacy projects spread out, and thus, contains
> more than 7,000 directories and many more files
> > - Things had worked with the 1.6 plug-in & CVSNT client, but it also
> occasionally timed out getting the changelog, hence our testing of the 2.x
> plug-ins
>
> --
> 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
>
>
>
--
Regards
Niranjan Bansal
[JIRA] (JENKINS-13929) allow to define a fix name for an IPA
domi created JENKINS-13929: -- Summary: allow to define a fix name for an IPA Key: JENKINS-13929 URL: https://issues.jenkins-ci.org/browse/JENKINS-13929 Project: Jenkins Issue Type: New Feature Components: xcode Environment: xcode-plugin 1.3.1 Reporter: domi Assignee: Arnaud Héritier Priority: Blocker The current implementation always adds the build number to the name of the IPA. This is not very handy if one wants to use permalinks to the final artifact - as the name always changes. There are two possible solutions for this: - allow the user to define a final name for each IPA - allow the user to choose whether he wants to add the build number to the IPA name -- 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-13814) java.lang.OutOfMemoryError exception when getting the remote log
[
https://issues.jenkins-ci.org/browse/JENKINS-13814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163230#comment-163230
]
Urban Novak commented on JENKINS-13814:
---
I've encountered the same problem - it looks like there is a memory leak either
in jenkins (1.465) or cvs plugin(2.4-SNAPSHOT (private-05/25/2012 14:52)).
Restarting Jenkins fixed the problem, probably only temporarily.
java.lang.OutOfMemoryError: Java heap space
at java.lang.StringCoding$StringDecoder.decode(Unknown Source)
at java.lang.StringCoding.decode(Unknown Source)
at java.lang.StringCoding.decode(Unknown Source)
at java.lang.String.(Unknown Source)
at java.io.ByteArrayOutputStream.toString(Unknown Source)
at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:540)
at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:415)
at hudson.scm.CVSSCM.checkout(CVSSCM.java:825)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
at
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
at hudson.model.Run.run(Run.java:1434)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
> java.lang.OutOfMemoryError exception when getting the remote log
>
>
> Key: JENKINS-13814
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13814
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Environment: Jenkins 1.464 on Windows 7 64-bit, 12GB RAM; CVS Plug-in
> 2.4-SNAPSHOT
>Reporter: James Gustafson
> Labels: cvs, exception, memory
>
> We are getting a java.lang.OutOfMemoryError exception when getting the remote
> log.
> {quote}
> Started by an SCM change
> Building in workspace C:\x\workspace\project_name_here
> cvs checkout -r BRANCH_NAME_HERE -D 16 May 2012 23:27:38 -0700 -d
> path\projects path/projects
> cvs checkout: Updating path\projects
> cvs checkout: Updating path\projects/dir1
> cvs checkout: Updating path\projects/dir2/dirA
> ... (about 7,224 directories) ...
> cvs checkout: Updating path\projects/dirN
> cvs rlog: Logging path\projects
> ... (about 7,224 directories) ...
> cvs rlog: Logging path\projects/dirN
> FATAL: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> at java.lang.StringCoding$StringDecoder.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.StringCoding.decode(Unknown Source)
> at java.lang.String.(Unknown Source)
> at java.io.ByteArrayOutputStream.toString(Unknown Source)
> at hudson.scm.CVSSCM.getRemoteLogForModule(CVSSCM.java:540)
> at hudson.scm.CVSSCM.calculateChangeLog(CVSSCM.java:415)
> at hudson.scm.CVSSCM.checkout(CVSSCM.java:825)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
> at
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
> at hudson.model.Run.run(Run.java:1434)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:239)
> {quote}
> Some notes:
> - The path/ and path\ comes from the "Remote Name"/"Local Name" settings
> solution from Issue JENKINS-13264
> - We are using Jenkins 1.464 with the 2.4-SNAPSHOT version of the CVS plugin,
> but may not have been caused by this specific version
> - The arguments setting in the jenkins.xml file currently has -Xms1024m
> (anything larger and Jenkins service won't start)
> - The CVS module has many legacy projects spread out, and thus, contains more
> than 7,000 directories and many more files
> - Things had worked with the 1.6 plug-in & CVSNT client, but it also
> occasionally timed out getting the changelog, hence our testing of the 2.x
> plug-ins
--
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-13412) Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings
[
https://issues.jenkins-ci.org/browse/JENKINS-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163229#comment-163229
]
Gregory Boissinot commented on JENKINS-13412:
-
Thanks for your comment.
Unfortunately, I can't reproduce an error with the latest value in my
environment with the Gradle plugin.
I'm closing the issue.
Do no hesitate to reopen it when you would successes to isolate the problem
with only the Gradle plugin.
> Gradle plugin fails to quote parameters without whitespace when containing
> input/output redirection symbols, e.g. in XML strings
>
>
> Key: JENKINS-13412
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13412
> Project: Jenkins
> Issue Type: Bug
> Components: gradle
>Affects Versions: current
> Environment: Windows Server 2008 R2
> Jenkins 1.424.6
> Jenkins Gradle Plugin 1.12
>Reporter: Daniel Beck
>Assignee: Gregory Boissinot
>
> Gradle plugin explicitly passes job parameters to the "cmd.exe /c gradle.bat"
> call.
> If one of these arguments looks like XML, but does not contain whitespace, it
> is not quoted. This leads to problems with input/output redirection symbols
> (less-than, greater-than)
> Example String Parameter value:
> {code}
>
> {code}
> Results in the following build output:
> {code}
> [workspace] $ cmd.exe /C C:\path\to\gradle.bat -Dfoo= -i && exit
> %%ERRORLEVEL%%
> The system cannot find the file specified.
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Notifying upstream projects of job completion
> {code}
> Real world example:
> Copy artifacts plugin's "Latest successful build" has the value:
> {code}
>
> {code}
> This results in "File not found" errors on Windows Server. Not tested on
> Linux.
--
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-13412) Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings
[
https://issues.jenkins-ci.org/browse/JENKINS-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Boissinot closed JENKINS-13412.
---
Resolution: Fixed
> Gradle plugin fails to quote parameters without whitespace when containing
> input/output redirection symbols, e.g. in XML strings
>
>
> Key: JENKINS-13412
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13412
> Project: Jenkins
> Issue Type: Bug
> Components: gradle
>Affects Versions: current
> Environment: Windows Server 2008 R2
> Jenkins 1.424.6
> Jenkins Gradle Plugin 1.12
>Reporter: Daniel Beck
>Assignee: Gregory Boissinot
>
> Gradle plugin explicitly passes job parameters to the "cmd.exe /c gradle.bat"
> call.
> If one of these arguments looks like XML, but does not contain whitespace, it
> is not quoted. This leads to problems with input/output redirection symbols
> (less-than, greater-than)
> Example String Parameter value:
> {code}
>
> {code}
> Results in the following build output:
> {code}
> [workspace] $ cmd.exe /C C:\path\to\gradle.bat -Dfoo= -i && exit
> %%ERRORLEVEL%%
> The system cannot find the file specified.
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Notifying upstream projects of job completion
> {code}
> Real world example:
> Copy artifacts plugin's "Latest successful build" has the value:
> {code}
>
> {code}
> This results in "File not found" errors on Windows Server. Not tested on
> Linux.
--
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-13705) Builds are sequential when there is a "Run conditional step" build step, even though the project is configured for concurrent execution
[ https://issues.jenkins-ci.org/browse/JENKINS-13705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BalagiriPrasad S updated JENKINS-13705: --- Summary: Builds are sequential when there is a "Run conditional step" build step, even though the project is configured for concurrent execution (was: Builds are sequential when there is a "Invoke Maven Target" build step, even though the project is configured for concurrent execution) Labels: parallel run-condition (was: concurrent-build) Description: The description summary the problem. When there is "Run conditional step" then build on one node is waiting for the build on the other node complete, even though the project is configured for parallel builds. (was: The reason for making "Invoke Maven Target" build step not parallel, may be because two concurrent maven calls can corrupt the repository. But when the two builds are happening on different nodes then jenkins should run them in parallel. I am using nodelableparam to select different nodes, throttle Concurrent Builds configured to have 'Maximum Concurrent Builds Per Node' as 1. Attached the project files. In sleep.xml, update with proper values) Component/s: run-condition (was: core) > Builds are sequential when there is a "Run conditional step" build step, even > though the project is configured for concurrent execution > --- > > Key: JENKINS-13705 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13705 > Project: Jenkins > Issue Type: Improvement > Components: run-condition >Affects Versions: current > Environment: Master : Windows, Nodes : Linux >Reporter: BalagiriPrasad S >Priority: Blocker > Labels: parallel, run-condition > Attachments: config.xml, sleep.xml > > > The description summary the problem. When there is "Run conditional step" > then build on one node is waiting for the build on the other node complete, > even though the project is configured for parallel builds. -- 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-13928) bad version number at offiset=6
Carl Chen created JENKINS-13928: --- Summary: bad version number at offiset=6 Key: JENKINS-13928 URL: https://issues.jenkins-ci.org/browse/JENKINS-13928 Project: Jenkins Issue Type: Bug Components: clearcase-ucm Affects Versions: current Environment: windows xp , tomcat 6.0.35, jenkins 1.465, clearcase-ucm-plugin 1.0.7 Reporter: Carl Chen jenkins runs well, but after install this plugin, it reports bad version number error. -- 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-13412) Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings
[
https://issues.jenkins-ci.org/browse/JENKINS-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163228#comment-163228
]
Daniel Beck edited comment on JENKINS-13412 at 5/28/12 7:49 AM:
Nothing in the job configuration. Those are job arguments with the following
values, one per line:
{code}
foo bar
{code}
The first and second are handled properly, but the third, containing both
spaces and XML brackets is quoted twice. That might be the cause of the problem.
I cannot reproduce it on my Windows system without Jenkins etc. right now, I'll
let you know what I find out.
To reproduce my production problem, use Copy Artifacts plugin and a Build
Selector job parameter that is set to "Specific Build". Then the XML value
produced isn't handled properly by the Gradle program call.
was (Author: danielbeck):
Nothing in the job configuration. Those are job arguments with the
following values, one per line:
{code}
foo bar
{code}
The first and second are handled properly, but the third, containing both
spaces and XML brackets is quoted twice, resulting in an error.
I cannot reproduce it on my Windows system right now, I'll let you know what I
find out.
To reproduce my production problem, use Copy Artifacts plugin and a Build
Selector job parameter that is set to "Specific Build". Then the XML value
produced isn't handled properly by the Gradle program call.
> Gradle plugin fails to quote parameters without whitespace when containing
> input/output redirection symbols, e.g. in XML strings
>
>
> Key: JENKINS-13412
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13412
> Project: Jenkins
> Issue Type: Bug
> Components: gradle
>Affects Versions: current
> Environment: Windows Server 2008 R2
> Jenkins 1.424.6
> Jenkins Gradle Plugin 1.12
>Reporter: Daniel Beck
>Assignee: Gregory Boissinot
>
> Gradle plugin explicitly passes job parameters to the "cmd.exe /c gradle.bat"
> call.
> If one of these arguments looks like XML, but does not contain whitespace, it
> is not quoted. This leads to problems with input/output redirection symbols
> (less-than, greater-than)
> Example String Parameter value:
> {code}
>
> {code}
> Results in the following build output:
> {code}
> [workspace] $ cmd.exe /C C:\path\to\gradle.bat -Dfoo= -i && exit
> %%ERRORLEVEL%%
> The system cannot find the file specified.
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Notifying upstream projects of job completion
> {code}
> Real world example:
> Copy artifacts plugin's "Latest successful build" has the value:
> {code}
>
> {code}
> This results in "File not found" errors on Windows Server. Not tested on
> Linux.
--
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-13412) Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings
[
https://issues.jenkins-ci.org/browse/JENKINS-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163228#comment-163228
]
Daniel Beck edited comment on JENKINS-13412 at 5/28/12 7:47 AM:
Nothing in the job configuration. Those are job arguments with the following
values, one per line:
{code}
foo bar
{code}
The first and second are handled properly, but the third, containing both
spaces and XML brackets is quoted twice, resulting in an error.
I cannot reproduce it on my Windows system right now, I'll let you know what I
find out.
To reproduce my production problem, use Copy Artifacts plugin and a Build
Selector job parameter that is set to "Specific Build". Then the XML value
produced isn't handled properly by the Gradle program call.
was (Author: danielbeck):
Nothing in the job configuration. Those are job arguments with the
following values, one per line:
{code}
foo bar
{code}
The first and second are handled properly, but the third, containing both
spaces and XML brackets is quoted twice, resulting in an error.
> Gradle plugin fails to quote parameters without whitespace when containing
> input/output redirection symbols, e.g. in XML strings
>
>
> Key: JENKINS-13412
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13412
> Project: Jenkins
> Issue Type: Bug
> Components: gradle
>Affects Versions: current
> Environment: Windows Server 2008 R2
> Jenkins 1.424.6
> Jenkins Gradle Plugin 1.12
>Reporter: Daniel Beck
>Assignee: Gregory Boissinot
>
> Gradle plugin explicitly passes job parameters to the "cmd.exe /c gradle.bat"
> call.
> If one of these arguments looks like XML, but does not contain whitespace, it
> is not quoted. This leads to problems with input/output redirection symbols
> (less-than, greater-than)
> Example String Parameter value:
> {code}
>
> {code}
> Results in the following build output:
> {code}
> [workspace] $ cmd.exe /C C:\path\to\gradle.bat -Dfoo= -i && exit
> %%ERRORLEVEL%%
> The system cannot find the file specified.
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Notifying upstream projects of job completion
> {code}
> Real world example:
> Copy artifacts plugin's "Latest successful build" has the value:
> {code}
>
> {code}
> This results in "File not found" errors on Windows Server. Not tested on
> Linux.
--
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-13412) Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings
[
https://issues.jenkins-ci.org/browse/JENKINS-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163228#comment-163228
]
Daniel Beck commented on JENKINS-13412:
---
Nothing in the job configuration. Those are job arguments with the following
values, one per line:
{code}
foo bar
{code}
The first and second are handled properly, but the third, containing both
spaces and XML brackets is quoted twice, resulting in an error.
> Gradle plugin fails to quote parameters without whitespace when containing
> input/output redirection symbols, e.g. in XML strings
>
>
> Key: JENKINS-13412
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13412
> Project: Jenkins
> Issue Type: Bug
> Components: gradle
>Affects Versions: current
> Environment: Windows Server 2008 R2
> Jenkins 1.424.6
> Jenkins Gradle Plugin 1.12
>Reporter: Daniel Beck
>Assignee: Gregory Boissinot
>
> Gradle plugin explicitly passes job parameters to the "cmd.exe /c gradle.bat"
> call.
> If one of these arguments looks like XML, but does not contain whitespace, it
> is not quoted. This leads to problems with input/output redirection symbols
> (less-than, greater-than)
> Example String Parameter value:
> {code}
>
> {code}
> Results in the following build output:
> {code}
> [workspace] $ cmd.exe /C C:\path\to\gradle.bat -Dfoo= -i && exit
> %%ERRORLEVEL%%
> The system cannot find the file specified.
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Notifying upstream projects of job completion
> {code}
> Real world example:
> Copy artifacts plugin's "Latest successful build" has the value:
> {code}
>
> {code}
> This results in "File not found" errors on Windows Server. Not tested on
> Linux.
--
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
