[JIRA] [packaging] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Daniel Beck commented on JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x Nobody here bothered to confirm this now works. So what's the point in nominating an unconfirmed fix for backporting? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28022) Build description longer than 30 chars has hex zero width space added
Daniel Beck commented on JENKINS-28022 Build description longer than 30 chars has hex zero width space added Why is this assigned to me? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Qingyou Meng commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Same problem on a slave node. Downgrade to 1.609 fixed the problem. size of jar files are about 1~2M size of a tar.gz file is about 37M build log = Notifying upstream projects of job completion Join notifier requires a CauseAction [INFO] [INFO] Reactor Summary: [INFO] [INFO] web-common SUCCESS [0.587s] [INFO] web-common-open ... SUCCESS [3.574s] [INFO] web-common-frontend ... SUCCESS [1.031s] [INFO] web-common-backend SUCCESS [0.808s] [INFO] web-common-business ... SUCCESS [10.231s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 19.959s [INFO] Finished at: Tue Apr 21 14:14:53 CST 2015 [INFO] Final Memory: 30M/165M [INFO] [JENKINS] Archiving /home/jenkinsslave/workspace/workspace/web_dept/web_dept__devprj/考勤v2.0/web-common/web-common-frontend/pom.xml to com.jingoal.web-common/web-common-frontend/1.0.0/web-common-frontend-1.0.0.pom [JENKINS] Archiving /home/jenkinsslave/workspace/workspace/web_dept/web_dept__devprj/考勤v2.0/web-common/web-common-frontend/target/web-common-frontend-1.0.0.jar to com.jingoal.web-common/web-common-frontend/1.0.0/web-common-frontend-1.0.0.jar [JENKINS] Archiving /home/jenkinsslave/workspace/workspace/web_dept/web_dept__devprj/考勤v2.0/web-common/web-common-frontend/target/web-common-frontend-1.0.0-sources.jar to com.jingoal.web-common/web-common-frontend/1.0.0/web-common-frontend-1.0.0-sources.jar ERROR: Failed to parse POMs java.io.IOException: Failed to extract /home/jenkinsslave/workspace/workspace/web_dept/web_dept__devprj/考勤v2.0/web-common/web-common-frontend/transfer of 3 files at hudson.FilePath.readFromTar(FilePath.java:2299) at hudson.FilePath.copyRecursiveTo(FilePath.java:2208) channel stopped at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at hudson.maven.MavenBuild$ProxyImpl.performArchiving(MavenBuild.java:483) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:851) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1741) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.io.IOException: Truncated TAR archive at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.read(TarArchiveInputStream.java:614) at java.io.InputStream.read(InputStream.java:101) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) at hudson.util.IOUtils.copy(IOUtils.java:40) at hudson.FilePath.readFromTar(FilePath.java:2289) ... 9 more Skipping sonar analysis due to bad build status FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28012) "Failed to parse POMs" during archiving of poms when running maven job
Daniel Hiller updated JENKINS-28012 "Failed to parse POMs" during archiving of poms when running maven job I've attached the pom anyway Change By: Daniel Hiller (21/Apr/15 6:04 AM) Attachment: pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-28019) Some jobs not pulling in revisions at all
ngiger commented on JENKINS-28019 Some jobs not pulling in revisions at all I will try to make a new release, adding among other https://github.com/jenkinsci/git-parameter-plugin/pull/11. Maybe this will fix your problem, too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28012) "Failed to parse POMs" during archiving of poms when running maven job
Daniel Hiller edited a comment on JENKINS-28012 "Failed to parse POMs" during archiving of poms when running maven job Furthermore I don't think that this is related to the issue JENKINS-10629 as Slavomir suggests because the generated jar file (of which I think that it would have been transferred) was only 20k of size. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28012) "Failed to parse POMs" during archiving of poms when running maven job
Daniel Hiller commented on JENKINS-28012 "Failed to parse POMs" during archiving of poms when running maven job Furthermore I don't think that this is related to the issue JENKINS-10629 as Oleg suggests because the generated jar file (of which I think that it would have been transferred) was only 20k of size. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28012) "Failed to parse POMs" during archiving of poms when running maven job
Daniel Hiller commented on JENKINS-28012 "Failed to parse POMs" during archiving of poms when running maven job By reading the stacktrace I don't think it has anything to do with the poms themselves. I must make clear that the failed build has run on a slave node and the line java.io.IOException: Failed to extract /home/jenkins/workspace/lexdb-legacy/lexdb-oracle-urteilid/transfer of 2 files from the stack trace snippet makes me think that there is something wrong with transferring some files from slave to master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step-plugin] (JENKINS-27296) Jenkins stopped displaying build progress after docker update
Jay Kah resolved JENKINS-27296 as Fixed Jenkins stopped displaying build progress after docker update The latest plugin update seems to have fixed the issue. Change By: Jay Kah (21/Apr/15 2:30 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24640) File modes are wrong after git checkout
Mark Waite commented on JENKINS-24640 File modes are wrong after git checkout The git client plugin 1.16.1 uses JGit 3.6.2.201501210735-r This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24640) File modes are wrong after git checkout
Gustavo Chaves reopened JENKINS-24640 File modes are wrong after git checkout Hi there. Since my previous comment the JGit project fixed the issue that was messing up with the executable bits of files during checkout. However, I'm still seeing the wrong JGit behaviour using Jenkins's git-client-plugin version 1.16.1 which I reckon is build using JGit version 3.6.2.201501210735-r which, according to Git, contains the commit which was implemented to solve the issue: [~/git/other/jgit] (master)$ git tag --contains d81529029a887cbc2356d6fc8d0168bd2f031ca2 v3.6.0.201412230720-r v3.6.1.201501031845-r v3.6.2.201501210735-r v3.7.0.201502031740-rc1 v3.7.0.201502260915-r I confirmed that JGit v3.6.2.201501210735-r solved the problem by using its CLI interface to perform clones and checkouts. But in my Jenkins 1.596.1 with git-client-plugin 1.16.1 I have a freestyle job configured to clone a repository using JGit. Look that after the checkout the executable files only have the owner executable bit set, not the group and other ones: 22:45:59 Started by user Gustavo Chaves 22:45:59 [EnvInject] - Loading node environment variables. 22:45:59 Building remotely on gerrit in workspace /l/disk0/cds/jenkins-slave/workspace/test-gerrit-checkout 22:45:59 Cloning the remote Git repository 22:46:00 Receiving objects 22:46:02 Resolving deltas 22:46:04 Updating references 22:46:04 Checking out Revision 8bbf53438aa4682349d354380c7d3a664e8dfb65 (origin/master) 22:46:05 [test-gerrit-checkout] $ /bin/sh -xe /tmp/hudson7932434129893537532.sh 22:46:05 + find bin -type f -perm -0100 -not -perm 0775 -ls 22:46:05 7260014 -rwxrw-r-- 1 cds cds 1983 Apr 20 22:44 bin/email-stuff.pl 22:46:05 7260174 -rwxrw-r-- 1 cds cds 3138 Apr 20 22:44 bin/jvm-gc-log-plot 22:46:05 7260624 -rwxrw-r-- 1 cds cds 1006 Apr 20 22:44 bin/ga2csv.pl 22:46:05 7260944 -rwxrw-r-- 1 cds cds 1319 Apr 20 22:44 bin/lmstat-a-summary.pl <...> Can someone confirm that git-client-plugin 1.16.1 uses JGit v3.6.2.201501210735-r? Change By: Gustavo Chaves (21/Apr/15 2:01 AM) Resolution: Not A Defect Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-27845) Support auto install on Mac OS X
Joe Hansche commented on JENKINS-27845 Support auto install on Mac OS X ^ Using 1.610 as the plugin's parent still produces the same results. The lib/node_modules/npm/node_modules/npmlog/node_modules directory is simply missing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-27146) Deploying an applicatin w/ "no-route" fails because route deletion fails
William Gautier closed JENKINS-27146 as Fixed Deploying an applicatin w/ "no-route" fails because route deletion fails Change By: William Gautier (20/Apr/15 11:48 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-25884) configure name of manifest.yml
William Gautier closed JENKINS-25884 as Fixed configure name of manifest.yml Change By: William Gautier (20/Apr/15 11:48 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-27119) path attribute in manifest.yml is not evaluated relative to the manifest.yml file
William Gautier closed JENKINS-27119 as Fixed path attribute in manifest.yml is not evaluated relative to the manifest.yml file Change By: William Gautier (20/Apr/15 11:48 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-27845) Support auto install on Mac OS X
Joe Hansche commented on JENKINS-27845 Support auto install on Mac OS X There seems to be a problem with the installer – although it seems to be an issue with Jenkins, not with the plugin. In my case, the extracted directory structure is missing several directory contents. However, if I extract the tarball myself, the directories are there. I have confirmed (via a unit test of the plugin) that even before the plugin starts deleting anything, the missing directories are not present. This is on Mac OS X. The first example that I have run into consistently is the lib/node_modules/npm/node_modules/npmlog/node_modules directory: it is present in the tarball, and it can be extracted properly; however, it does not exist in the extracted tool directory. All the other files inside npmlog are present, it's just missing node_modules and children. I'm still trying to find a reliable way to reproduce the issue. I'll also try updating the Jenkins hpi version requirement, to see if it was an issue that has been fixed in the Jenkins core. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28022) Build description longer than 30 chars has hex zero width space added
owenmehegan created JENKINS-28022 Build description longer than 30 chars has hex zero width space added Issue Type: Bug Assignee: Daniel Beck Components: core Created: 20/Apr/15 11:29 PM Description: We use a Groovy script to write the package version into the build description of a job after it completes. Users then copy this from the Jenkins UI and paste it to perform a deploy. I have discovered occasional strange issues with this where what seems to be a valid version number is not found by our deploy system. Eventually I figured out that Jenkins is inserting a in the string if it exceeds 30 chars. This is invisible (obviously) in the UI but gets captured when the text is selected and copied/pasted (at least with Chrome on MacOS). This is a problem because this copy-paste workflow has been embedded here for several years, and a recent Jenkins upgrade has thrown this entropy into it Environment: Jenkins 1.596.1 Project: Jenkins Priority: Minor Reporter: owenmehegan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28012) "Failed to parse POMs" during archiving of poms when running maven job
Oleg Nenashev assigned JENKINS-28012 to Oleg Nenashev "Failed to parse POMs" during archiving of poms when running maven job Change By: Oleg Nenashev (20/Apr/15 11:23 PM) Assignee: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28012) "Failed to parse POMs" during archiving of poms when running maven job
Oleg Nenashev commented on JENKINS-28012 "Failed to parse POMs" during archiving of poms when running maven job Could you share the job's configuration and generated POMs? I'm still working on the reproducible scenario This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-22216) Custom Metrics with aggregation for load tests
Glenn Caccia commented on JENKINS-22216 Custom Metrics with aggregation for load tests There's also the jmeter-plugin report for performance monitoring. It would be great if the plugin could integrate with those. Specifically, the jmeter plugin "PerfMon Metrics Collector". It can be used to gather statistics for CPU, memory usage and other things and output them as JTL files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-27382) EnvInject plugin passes astrisk to Gradle plugin
Kevin Mayfield commented on JENKINS-27382 EnvInject plugin passes astrisk to Gradle plugin Problem still exists in 1.91.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Phil Miller commented on JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x The same change will need to be applied to the LTS branch, and at least a point release made, to renew access for LTS users on older Debian/Ubuntu systems. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev-plugin] (JENKINS-3197) RFE: Use AccuRev server without doing logins
Karthic Bala commented on JENKINS-3197 RFE: Use AccuRev server without doing logins Could you please provide me solution to fix this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28021) 'build' does not wait downstreams job to complete
Nicolas Labrot created JENKINS-28021 'build' does not wait downstreams job to complete Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 20/Apr/15 8:28 PM Description: I setup two freestyle jobs Job 1 and Job 2. Job 2 is a downstream job of Job 1 (Job 1 builds Job 2 as a post build action). Job 2 always fails. I setup a Workflow project with: build job: 'Job 1', propagate: true, wait: true Even if propagate and wait are set to true, my workflow project never waits for Job 2 completion and thus never fails. Environment: Jenkins 1.609 Workflow 1.5 Project: Jenkins Priority: Major Reporter: Nicolas Labrot This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.6
Magnus Sandberg closed JENKINS-27987 as Duplicate Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 Great Change By: Magnus Sandberg (20/Apr/15 8:22 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Daniel Beck commented on JENKINS-27948 Script timeout during start of configure a jenkins job Haven't had time to investigate, but you could do some of that yourself: While the form is submitted and the page is loading, repeatedly load the /threadDump URL and look for a thread named Handling POST /job/JOBNAME/configSubmit or something similar. Look where it's stuck processing for most of the time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27995) Add Contributing section to the README
dogfood commented on JENKINS-27995 Add Contributing section to the README Integrated in jenkins_main_trunk #4095 Result = SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27918) Unhelpful log warning about stapler-class
dogfood commented on JENKINS-27918 Unhelpful log warning about stapler-class Integrated in jenkins_main_trunk #4095 Result = SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23914) Invalid element added to in job causing NPE on job load
Daniel Beck commented on JENKINS-23914 Invalid element added to in job causing NPE on job load Audit Trail plugin and/or Job Config History (best use both) may allow you to determine who changed the job config in what way, when. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Jesse Glick updated JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job Change By: Jesse Glick (20/Apr/15 8:02 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27993) /pluginManager/api/json largely useless
Daniel Beck assigned JENKINS-27993 to Daniel Beck /pluginManager/api/json largely useless Change By: Daniel Beck (20/Apr/15 7:54 PM) Assignee: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27993) /pluginManager/api/json largely useless
Daniel Beck
updated JENKINS-27993
/pluginManager/api/json largely useless
Rewrote issue to address actual issue.
Change By:
Daniel Beck
(20/Apr/15 7:53 PM)
Issue Type:
Bug
Improvement
Description:
Visibility of the most important PluginWrapper @Exported getters should be increased to not serve something like the following by default:
{
code}{
"plugins":[{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{}]}
{code}
.. not helping, if you want to enumerate plugins and their versions ;)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-20211) Pairs of throttled node labels no longer seem to work starting from version 1.536
Daniel Beck commented on JENKINS-20211 Pairs of throttled node labels no longer seem to work starting from version 1.536 Anyone still experiencing this issue on 1.610+? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [next-build-number-plugin] (JENKINS-27958) Cannot reset the next build number
Daniel Beck resolved JENKINS-27958 as Not A Defect Cannot reset the next build number Enter a number. Leave out the '#'. The exception clearly tells you what's wrong. Change By: Daniel Beck (20/Apr/15 7:13 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-24248) Cannot configure Active Directory Bind DN or Bind Password
Daniel Beck resolved JENKINS-24248 as Duplicate Cannot configure Active Directory Bind DN or Bind Password Fixed as JENKINS-27763. Change By: Daniel Beck (20/Apr/15 7:19 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-proposals] (JENKINS-10185) Start job under specified AD user
Daniel Beck updated JENKINS-10185 Start job under specified AD user This request doesn't make any sense in the context of Active Directory plugin, so moving to plugin proposals. Straightforward alternative: Just set up another slave running as that user. Change By: Daniel Beck (20/Apr/15 7:17 PM) Component/s: plugin-proposals Component/s: active-directory-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-reports-plugin] (JENKINS-28020) Upgrading to 0.0.24 from 0.0.23 causes Cucumber Reports plugin to Always fail with a null pointer
Mike Corum created JENKINS-28020 Upgrading to 0.0.24 from 0.0.23 causes Cucumber Reports plugin to Always fail with a null pointer Issue Type: Bug Assignee: Unassigned Components: cucumber-reports-plugin Created: 20/Apr/15 6:59 PM Description: Upgrading from 0.0.23 to 0.0.24 causes the following stack trace every time (going back to 23 solves it). ERROR: Publisher net.masterthought.jenkins.CucumberReportPublisher aborted due to exception java.lang.NullPointerException at org.apache.tools.ant.DirectoryScanner.normalizePattern(DirectoryScanner.java:797) at org.apache.tools.ant.DirectoryScanner.setExcludes(DirectoryScanner.java:751) at net.masterthought.jenkins.CucumberReportPublisher.findJsonFiles(CucumberReportPublisher.java:59) at net.masterthought.jenkins.CucumberReportPublisher.perform(CucumberReportPublisher.java:97) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Environment: Jenkins on Linux Project: Jenkins Priority: Major Reporter: Mike Corum This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-28019) Some jobs not pulling in revisions at all
Alex Duncan created JENKINS-28019 Some jobs not pulling in revisions at all Issue Type: Bug Assignee: Niklaus Giger Components: git-parameter-plugin Created: 20/Apr/15 6:50 PM Description: Some jobs failing to pull in revisions entirely. Log lines: Apr 20, 2015 2:43:39 PM net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition generateContents INFO: generateContents contenttype PT_REVISION RemoteConfig [git://github.com/NodeBB/NodeBB.git] Here is a heap dump for the node in question as the process is hanging trying to pull in revisions: http://pastebin.com/901fpzQc Any other information can be provided on request. Thanks. Environment: Jenkins v1.5.99, git-parameter 0.4.0, Git 2.3.5, RHEL 7 Project: Jenkins Priority: Critical Reporter: Alex Duncan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-20211) Pairs of throttled node labels no longer seem to work starting from version 1.536
Dwane Pottratz commented on JENKINS-20211 Pairs of throttled node labels no longer seem to work starting from version 1.536 Looks to be working in 1.610 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27970) Issue with docker-build-publish-plugin --- build failed, but success is reported
Carlos Sanchez resolved JENKINS-27970 as Fixed Issue with docker-build-publish-plugin --- build failed, but success is reported Fixed in https://github.com/jenkinsci/docker-build-publish-plugin/pull/19 Change By: Carlos Sanchez (20/Apr/15 6:44 PM) Status: Open Resolved Assignee: Michael Neale Carlos Sanchez Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vncviewer-plugin] (JENKINS-28001) start button in Console output does not work if jenkins instance is installed behind reverse proxy (should extract host from Jenkins URL global settings)
Dimitri Tenenbaum resolved JENKINS-28001 as Fixed start button in Console output does not work if jenkins instance is installed behind reverse proxy (should extract host from Jenkins URL global settings) Thank you for your fix Thomasz! Fixed in release 1.2. Change By: Dimitri Tenenbaum (20/Apr/15 6:29 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-proposals] (JENKINS-27967) Remote trigger from Fisheye webhook
Daniel Beck updated JENKINS-27967 Remote trigger from Fisheye webhook This looks like it's firmly in the domain of plugins as it seems to have fairly limited appeal (compared to "trigger a build from a script"), and may need to be tailored to each third party tool's data. Change By: Daniel Beck (20/Apr/15 6:23 PM) Component/s: plugin-proposals Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27912) Whole job directory sometimes gets deleted including workspace and all builds
Daniel Beck commented on JENKINS-27912 Whole job directory sometimes gets deleted including workspace and all builds try creating something that will keep an otherwise useless file in each workspace open to make the unlink fail Could be as simple as opening a cmd.exe window in the .../job/foo/builds/ directory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4133) Add "Wipe Out Workspace" for /job/aProject
Daniel Beck commented on JENKINS-4133 Add "Wipe Out Workspace" for /job/aProject Alternatively, Workspace Cleanup Plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27991) Unable to POST modified config.xml in Jenkins via curl API.
Daniel Beck commented on JENKINS-27991 Unable to POST modified config.xml in Jenkins via curl API. This may be JENKINS-27548. Read those comments and try the workaround provided there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-10742) Send HTML jabber messages
kutzi commented on JENKINS-10742 Send HTML jabber messages Maybe we could start as a 1st step and change the BotCommands to return the current plain-text messages and the model data. Would still mean lot of changes in the Jabber plugin (fork), but at least a bit code reuse. In regards to templating: do yourself a favor and use something different than Jelly (e.g. Freemarker). Surely, Jelly is in widespread use in Jenkins, but it's a pita to use IMHO. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.6
Grigoriy Milman edited a comment on JENKINS-27987 Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 It looks like it is duplicate of the JENKINS-27957 Version 2.12 which has a fix for the JENKINS-27957 does not repeat the problem This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.6
Grigoriy Milman resolved JENKINS-27987 as Duplicate Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 It looks like it is duplicate of the JENKINS-27957 Version 2.12 which has a fix for the JENKINS-27957does not show the problem Change By: Grigoriy Milman (20/Apr/15 5:55 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19465) OSX Slave hangs while being launched
Mario Rincon commented on JENKINS-19465 OSX Slave hangs while being launched This issue happens to me in version 1.590. I don't know if it's fixed in the latest version, though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-27851) Failure of docker build command does not fail build step
Michael Neale resolved JENKINS-27851 as Duplicate Failure of docker build command does not fail build step Duplicate of JENKINS-27970 Change By: Michael Neale (20/Apr/15 5:33 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3-plugin] (JENKINS-24335) S3 Managed Artifacts Improve Path for Multi Configuration Builds
Tom Hughes commented on JENKINS-24335 S3 Managed Artifacts Improve Path for Multi Configuration Builds I'm also hitting this issue using a matrix build with one axis. With a job called "myjob" and choosing slaves based on labels, I end up with the following path: jobs/label=foo/build_number/artifact_name Instead, I would expect the job name to be included in the path so it doesn't conflict with other jobs: jobs/myjob/label=foo/build_number/artifact_name This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3-plugin] (JENKINS-24335) S3 Managed Artifacts Improve Path for Multi Configuration Builds
Tom Hughes assigned JENKINS-24335 to Nicolas De Loof S3 Managed Artifacts Improve Path for Multi Configuration Builds Change By: Tom Hughes (20/Apr/15 5:19 PM) Assignee: Michael Watt Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Matthew Smith commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable I am running into this problem as well. The reason I am trying to have one workspace shared across multiple jobs is due to the size of the particular depot. We can't get enough space on a slave machine to have multiple stored versions of the same code/content/art. P4 Streams would make our lives easier, but our release cadence prevents that work from getting done. What I will do in the meantime is set up a 'starter' project for the branch that updates the client workspace, then hand control off to the actual project the user meant to run. I would like to see a fix for this, we're limiting executor access to those directories by branch currently, so I am not worried about concurrent runs on the same slave node. He's a repro: in 1 job, in 1 workspace, sync a file Check in a change to that file in a separate job referencing the same workspace, trigger a build that syncs You will be able to observe the have entry for that file updates, but the file on disk will remain at rev 1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.6
Grigoriy Milman commented on JENKINS-27987 Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 We are using 2.11 It could be the same issue as in JENKINS-27957, so I will try 2.12, may be it is already fixed. I will try it today. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-plugin] (JENKINS-24989) Support Mercurial repositories
Christopher Swingler commented on JENKINS-24989 Support Mercurial repositories +1 on this. This really should be of a higher priority, this plugin isn't really complete if it doesn't support all types of repos that BitBucket does. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
mwebber commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive If you want to see the artefacts that I attempted to save, you can get a copy from http://www.opengda.org/downloads/special/archive.zip (be warned it's 2.1GB). Unzip that, and you will have what I was trying to archive. Note: job specified "files to archive" as: artifacts_to_archive/, create.product.root/products/.txt, create.product.root/products/*.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27995) Add Contributing section to the README
Kamran Mackey closed JENKINS-27995 as Fixed Add Contributing section to the README Closing since I fixed the issue. Change By: Kamran Mackey (20/Apr/15 4:12 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27995) Add Contributing section to the README
SCM/JIRA link daemon commented on JENKINS-27995 Add Contributing section to the README Code changed in jenkins User: Kamran Mackey Path: README.md http://jenkins-ci.org/commit/jenkins/1880324a27a2d60ae24bddc6ca7fa5ea15eaa800 Log: JENKINS-27995 Added contributing section to the README. Signed-off-by: Kamran Mackey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27995) Add Contributing section to the README
Kamran Mackey commented on JENKINS-27995 Add Contributing section to the README Added as of commit 1880324. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27995) Add CONTRIBUTING.md file to the Jenkins GitHub repository.
Kamran Mackey updated JENKINS-27995 Add CONTRIBUTING.md file to the Jenkins GitHub repository. Change By: Kamran Mackey (20/Apr/15 3:58 PM) Issue Type: New Feature Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27995) Add Contributing section to the README
Kamran Mackey updated JENKINS-27995 Add Contributing section to the README Change By: Kamran Mackey (20/Apr/15 3:58 PM) Summary: Add CONTRIBUTING.md file Contributing section to the Jenkins GitHub repository. README Assignee: Kamran Mackey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27995) Add CONTRIBUTING.md file to the Jenkins GitHub repository.
Kamran Mackey commented on JENKINS-27995 Add CONTRIBUTING.md file to the Jenkins GitHub repository. Yeah, I guess you're right Daniel. I guess it wouldn't be that necessary. However, maybe adding a contributing section to the README file in the repository that links to that wiki page would work instead? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
mwebber commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive In fact, I just noticed something strange. If I go to $JENKINS_HOME/jobs on the Jenkins master, and look in /builds//archive/ for the job that failed, I see all the archived files that I expect. It's worth noting that the failing job was running on a slave, but the slave was defined as the same machine as the master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
mwebber commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive It would be great to have an example of artefacts you're trying to publish Ours are a bit too large to attach here, but below is the directory structure: /exports/jenkins_home/jobs/DawnDiamond.master-create.product/builds/3053/archive]$ ls -la drwxrwsr-x. 2 dlshudson dls_dasc 4096 Apr 20 16:38 artifacts_to_archive drwxrwsr-x. 3 dlshudson dls_dasc 4096 Apr 20 16:38 create.product.root $ ls -la artifacts_to_archive/ -rw-rw-r--. 1 dlshudson dls_dasc 6152 Apr 20 16:29 materialized_head_commits.txt -rw-rw-r--. 1 dlshudson dls_dasc 345 Apr 20 16:29 materialized_targetplatform_contents.txt $ ls -la create.product.root/ drwxrwsr-x. 2 dlshudson dls_dasc 4096 Apr 20 16:40 products $ ls -la create.product.root/products/ -rw-rw-r--. 1 dlshudson dls_dasc 482936973 Apr 20 16:25 DawnDiamond-1.9.0.v20150420-1451-linux32.zip -rw-rw-r--. 1 dlshudson dls_dasc 479510056 Apr 20 16:25 DawnDiamond-1.9.0.v20150420-1451-linux64.zip -rw-rw-r--. 1 dlshudson dls_dasc 328621190 Apr 20 16:25 DawnDiamond-1.9.0.v20150420-1451-mac64.zip -rw-rw-r--. 1 dlshudson dls_dasc 488357250 Apr 20 16:25 DawnDiamond-1.9.0.v20150420-1451-windows32.zip -rw-rw-r--. 1 dlshudson dls_dasc 49490 Apr 20 16:25 DawnDiamond-1.9.0.v20150420-1451-windows64.zip -rw-rw-r--. 1 dlshudson dls_dasc21 Apr 20 16:37 product_version_number.txt -rw-rw-r--. 1 dlshudson dls_dasc 104848904 Apr 20 16:37 squish_tests.zip -rw-rw-r--. 1 dlshudson dls_dasc 459423471 Apr 20 16:25 uk.ac.diamond.dawn.site_1.7.1.v20150420-1451.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Oleg Nenashev assigned JENKINS-28013 to Oleg Nenashev Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Change By: Oleg Nenashev (20/Apr/15 3:45 PM) Assignee: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
mwebber commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive I also started seeing this after upgrading from 1.609 to 1.610. Downgrading fixed the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Oleg Nenashev commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Yes, it seems to be a regression. In JENKINS-10629 we ported the Tars handling implementation to apache-compress from a legacy snapshot of the library. It would be great to have an example of artefacts you're trying to publish. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-28003) ec2-plugin breaks with BouncyCastle 1.50
Francis Upton resolved JENKINS-28003 as Fixed ec2-plugin breaks with BouncyCastle 1.50 https://github.com/jenkinsci/ec2-plugin/pull/145 Change By: Francis Upton (20/Apr/15 3:31 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-28003) ec2-plugin breaks with BouncyCastle 1.50
Francis Upton closed JENKINS-28003 as Fixed ec2-plugin breaks with BouncyCastle 1.50 Change By: Francis Upton (20/Apr/15 3:31 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Steffan Karger commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Makes sense. Sorry for the noise. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Daniel Beck commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive That's why this can be considered a regression, and not just an incomplete fix. https://github.com/jenkinsci/jenkins/pull/1647 is a likely culprit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Jesse Glick started work on JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job Change By: Jesse Glick (20/Apr/15 3:19 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Jesse Glick updated JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job Change By: Jesse Glick (20/Apr/15 3:20 PM) Labels: form-data regression This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Steffan Karger commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive @Daniel it is very unlikely that my artifacts would be > 8GB; the artifacts generated by 1.609 are ~ 1MB. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Daniel Beck commented on JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x To clarify, Jenkins 1.609, 1.610 still cannot be installed on these older systems? Which of these did you try? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28009) Jenkins Downloads Aren't Served Over HTTPS
Daniel Beck commented on JENKINS-28009 Jenkins Downloads Aren't Served Over HTTPS INFRA-110 for the metadata, INFRA-266 for the downloads. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27995) Add CONTRIBUTING.md file to the Jenkins GitHub repository.
Daniel Beck commented on JENKINS-27995 Add CONTRIBUTING.md file to the Jenkins GitHub repository. Is this really necessary? Many smaller OSS project may only have their Github repo, so for those it definitely makes sense. But Jenkins has a web site and wiki which clearly spell out how this works (Extend Jenkins -> Developing Jenkins -> Contributing to Jenkins). If you (abstract "you") can't be bothered to read that far, maybe you shouldn't open pull requests in the first place? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Jakub Czaplicki commented on JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x Follow Alexander's solution and update the dpkg package : https://issues.jenkins-ci.org/browse/JENKINS-26240?focusedCommentId=218557&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-218557 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Daniel Beck commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Probably a regression from JENKINS-10629. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vncviewer-plugin] (JENKINS-28001) start button in Console output does not work if jenkins instance is installed behind reverse proxy (should extract host from Jenkins URL global settings)
Daniel Beck updated JENKINS-28001 start button in Console output does not work if jenkins instance is installed behind reverse proxy (should extract host from Jenkins URL global settings) Change By: Daniel Beck (20/Apr/15 3:05 PM) Summary: [vncviewer-plugin] VncViewer start button in Console output does not work if jenkins instance is installed behind reverse proxy (should extract host from Jenkins URL global settings) Component/s: vncviewer-plugin Component/s: other This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28009) Jenkins Downloads Aren't Served Over HTTPS
Daniel Beck commented on JENKINS-28009 Jenkins Downloads Aren't Served Over HTTPS as any binaries being downloaded can easily be modified on-the-fly to inject malicious code That's why they're signed. Check out jarsigner. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28009) Jenkins Downloads Aren't Served Over HTTPS
Daniel Beck resolved JENKINS-28009 as Duplicate Jenkins Downloads Aren't Served Over HTTPS Duplicates some issue in the INFRA project. The problem is the mirrors IIRC. Change By: Daniel Beck (20/Apr/15 3:04 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.
Daniel Beck commented on JENKINS-10629 Tar implimentation can't handle > 8GB and doesn't error out. May have caused JENKINS-28013. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-28015) OS X: postinstall script interprets that all uid's are taken if uid 499 is taken
Daniel Beck updated JENKINS-28015 OS X: postinstall script interprets that all uid's are taken if uid 499 is taken Change By: Daniel Beck (20/Apr/15 3:00 PM) Summary: OS X: postinstall script interprets that all uid's are taken if uid 499 is taken Component/s: packaging Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27986) Saving configuration changes on existing Jobs results in connection reset error
Elizabeth Pino updated JENKINS-27986 Saving configuration changes on existing Jobs results in connection reset error Change By: Elizabeth Pino (20/Apr/15 2:48 PM) Description: Edit existing Jenkins job, for example correcting a typo in execute shell. Press Save. 1 out of 50 times it may work. the other times result in connection to server was reset. Checked the Jenkins system log file and see the following. Can anyone help - I see the was previously reported - Apr 16, 2015 2:37:59 PM WARNING org.eclipse.jetty.util.log.JavaUtilLog warnError while serving http://cantor.swg.usma.ibm.com:8080/job/release_7.6.0.1/job/dailyregression_PORevisionSuite/configSubmit java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor674.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56) at java.lang.reflect.Method.invoke(Method.java:620) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServ
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Jesse Glick updated JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job Evidently a bug in the plugin, since the selector field value is bogus (does not mention StatusBuildSelector). How this worked before 1.610 is the question in my mind. I presume selectorList.jelly is somehow to blame; it is unclear why this specialized control even exists. Change By: Jesse Glick (20/Apr/15 2:44 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Jesse Glick assigned JENKINS-28011 to Jesse Glick Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job Change By: Jesse Glick (20/Apr/15 2:38 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28015) postinstall script interprets that all uid's are taken if uid 499 is taken
David Marmoy
updated JENKINS-28015
postinstall script interprets that all uid's are taken if uid 499 is taken
Change By:
David Marmoy
(20/Apr/15 2:36 PM)
Description:
The postinstall scipt has a line that checks for an available uid for the jenkins user and fails if no uid below 500 is found to be free. The problem is that the script only checks whether uid 499 is taken and if it is, then assumes that all other uid's below are also taken. This is not always the case.To recreate, create a user with uid 499 and afterwards attempt to install jenkins from the native osx installer. The error output can be found in /var/log/install.log. The offending lines of code can be found in https://github.com/kisielk/jenkins/blob/master/osx/scripts/postinstall-launchd-jenkins, and consists of:uid=$(dscl . -list /Users uid | sort -nrk 2 | awk '$2 < 500 {print $2 + 1; exit 0}')if [ $uid -eq 500 ]; then echo 'ERROR: All system uids are in use!' exit 1fiThe issue would be fixed if these lines were changed to something more flexible.
Workaround:Unpack the installer, find the postinstall script and manually set uid, then repack installer. See http://stackoverflow.com/a/29747480/584405
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Steffan Karger commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive For the record, I'm currently using Copy Artifact Plugin 1.35. Downgrading to 1.609 made the issue disappear again for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-28018) Generate Report button does nothing, table is still empty
Asaf M created JENKINS-28018 Generate Report button does nothing, table is still empty Issue Type: Bug Assignee: Varun Menon Components: test-results-analyzer-plugin Created: 20/Apr/15 2:17 PM Description: Installed the plugin Clicked on the a job to get to its page. Clicked "Test Results Analyzer", and got couple of button and a table without data. Clicked "Get Build Report" and nothing changed. Exception in the log shows Apr 20, 2015 5:07:55 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.jsonLoadData in /job/csi-2.19-hourly-tests/test_results_analyzer/. Reason: java.lang.refl ect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibr
[JIRA] [core] (JENKINS-27967) Remote trigger from Fisheye webhook
Jérémie Faucher-Goulet commented on JENKINS-27967 Remote trigger from Fisheye webhook I use the following URL to trigger a build remotely: [JENKINS URL]/view/job/[JOB_NAME]/build?token=[TOKEN] What I envision, is the ability to access the body of such POST request within a job's configuration... Or a way to specify conditions upon which to really start the build based on the body of the POST. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Laurent TOURREAU commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Hi I have upgraded from 1.607 to 1.610. I face the same issue. Regards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-20349) Be able to specify Unity3D path per slave without installation on master
lacostej reopened JENKINS-20349 Be able to specify Unity3D path per slave without installation on master I agree we need to update the documentation. Anyone willing to contribute a patch ? Change By: lacostej (20/Apr/15 2:04 PM) Resolution: Not A Defect Status: Resolved Reopened Assignee: Christian Weinmüllner lacostej This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Diogo Campos commented on JENKINS-24304 Enable/Disable verbose Git command logging in Jenkins build log I don't even have the "Seen branch" line in my output, but I do have hundreds of rev-parse calls. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-27456) Emulator can't connect to adb server!?
alcindo da costa edited a comment on JENKINS-27456 Emulator can't connect to adb server!? Hi, I have the same issues, i'm using the "armeabi-v7a". Jenkins log $ /var/lib/jenkins/tools/android-sdk/tools/android list target [android] Using Android SDK: /var/lib/jenkins/tools/android-sdk $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb start-server * daemon not running. starting it now on port 7125 * * daemon started successfully * $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb start-server [android] Starting Android emulator [android] Erasing existing emulator data... $ /var/lib/jenkins/tools/android-sdk/tools/emulator -ports 7123,7124 -prop persist.sys.language=fr -prop persist.sys.country=CH -avd hudson_fr-CH_480_1080x1920_android-19_armeabi-v7a_emulator -no-snapshot-load -no-snapshot-save -wipe-data -no-window -no-audio $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 connected to localhost:7124 [android] Waiting for emulator to finish booting... $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform
[JIRA] [android-emulator-plugin] (JENKINS-27456) Emulator can't connect to adb server!?
alcindo da costa commented on JENKINS-27456 Emulator can't connect to adb server!? Hi, I have the same issues, i'm using the "armeabi-v7a". Jenkins log New 'sansa.hostingaddict.ch:97 (jenkins)' desktop is sansa.hostingaddict.ch:97 Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/sansa.hostingaddict.ch:97.log $ /var/lib/jenkins/tools/android-sdk/tools/android list target [android] Using Android SDK: /var/lib/jenkins/tools/android-sdk $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb start-server * daemon not running. starting it now on port 7125 * * daemon started successfully * $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb start-server [android] Starting Android emulator [android] Erasing existing emulator data... $ /var/lib/jenkins/tools/android-sdk/tools/emulator -ports 7123,7124 -prop persist.sys.language=fr -prop persist.sys.country=CH -avd hudson_fr-CH_480_1080x1920_android-19_armeabi-v7a_emulator -no-snapshot-load -no-snapshot-save -wipe-data -no-window -no-audio $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 connected to localhost:7124 [android] Waiting for emulator to finish booting... $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools
[JIRA] [android-emulator-plugin] (JENKINS-27456) Emulator can't connect to adb server!?
alcindo da costa edited a comment on JENKINS-27456 Emulator can't connect to adb server!? Hi, I have the same issues, i'm using the "armeabi-v7a". Jenkins log Starting applications specified in /var/lib/jenkins/.vnc/xstartup Log file is /var/lib/jenkins/.vnc/sansa.hostingaddict.ch:97.log $ /var/lib/jenkins/tools/android-sdk/tools/android list target [android] Using Android SDK: /var/lib/jenkins/tools/android-sdk $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb start-server * daemon not running. starting it now on port 7125 * * daemon started successfully * $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb start-server [android] Starting Android emulator [android] Erasing existing emulator data... $ /var/lib/jenkins/tools/android-sdk/tools/emulator -ports 7123,7124 -prop persist.sys.language=fr -prop persist.sys.country=CH -avd hudson_fr-CH_480_1080x1920_android-19_armeabi-v7a_emulator -no-snapshot-load -no-snapshot-save -wipe-data -no-window -no-audio $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 connected to localhost:7124 [android] Waiting for emulator to finish booting... $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bootanim error: device offline $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb disconnect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb connect localhost:7124 $ /var/lib/jenkins/tools/android-sdk/platform-tools/adb -s localhost:7124 shell getprop init.svc.bo
[JIRA] [git-plugin] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Scott Hebert commented on JENKINS-19022 GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields Hi, I have updated http://scriptlerweb.appspot.com/script/show/326001 to support Matrix Project types. Thanks Scott This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-20349) Be able to specify Unity3D path per slave without installation on master
Steven Shipton commented on JENKINS-20349 Be able to specify Unity3D path per slave without installation on master Thanks for the clarification, changing to a directory path worked. The error message implied UNITY_WINDOWS was a path to an executable. I think my initial confusion was compounded by the fact that the values entered on the system configuration under 'Unity3d installations' are for the master and these values should be overridden per node. I don't have Unity installed on the master so was not sure an empty 'Installation directory' would be valid. It seems validation is working on the system configuration page as entering e.g. the windows path here on a non-windows master results in the following error message: 'Not a directory C:\Program Files (x86)\Unity\'. This same is not true on the node configuration page but that seems like a Jenkins issue rather than a plugin issue. The following would help prevent further user error (please consider as a feature request): Change error message from 'FATAL: Executable not found UNITY_WINDOWS' to 'directory not found UNITY_WINDOWS' A tooltip for Installation directory explaining that it does not need to be set and can be overridden per node Update to wiki documentation clarifying configuring nodes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Troy Mills commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive encountered the same issue, same stack. i/we had to rollback the jenkins.war on the master. environment wise, for us its CentOS6 64bit master and slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
