[JIRA] (JENKINS-61656) Unable to install latest version on Ubuntu 12.04
Title: Message Title Joe Mihalich created an issue Jenkins / JENKINS-61656 Unable to install latest version on Ubuntu 12.04 Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-03-24 06:54 Environment: Ubuntu 12.04 Java 8 Priority: Major Reporter: Joe Mihalich I was trying to upgrade from 2.180 to 2.227 on Ubuntu 12.04. The following error was output by the installer: dpkg-deb: error: archive 'jenkins_2.227_all.deb' contains not understood data member control.tar.xz, giving up It appears, perhaps, that at some point between build 180 and 227 the jenkins build script started using a new compression format for the deb packages that older versions of apt-get/dpkg don't support? Do you know which version this started in? And is this something that was intentional, and there fore is not going to be fixed? I didn't see anywhere in the release notes anything saying support was deprecated for any ubuntu versions. apt-get install pulled down version 227, so presumably it was intended to work on 12.04? Here's my environment specifics: jmihalich@ubermedia-prod-jenkins:/var/lib/jenkins$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.5 LTS Release:12.04 Codename: precise
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Joe Mihalich commented on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat I think the pull request is out of Jenkin's hands at this point. The owner of the plugin repo has to approve the pull and merge in the changes and release a new version. Since there's been no response to the pull request we have to assume the plugin/github repo is abandoned. The only options at this point are to build the latest manually, or use another newer plugin that gives similar functionality. There are some others out there. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.1940.1582066980451%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Joe Mihalich commented on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat any idea when that's going to happen? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.13152.1576694820404%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Joe Mihalich updated an issue Jenkins / JENKINS-58211 ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat Change By: Joe Mihalich Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.885.1566924480809%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Joe Mihalich edited a comment on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat Is someone going to look into this issue? We're blocked from upgrading until this is fixed. Also if anyone has a workaround, please post it here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.868.1566924420728%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Joe Mihalich commented on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat Is someone going to look into this issue? We're blocked from upgrading until this is fixed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.858.1566924420568%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Joe Mihalich commented on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat Same error on 2.186. Rolled back to 2.180 as others did, and problem went away. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.16921.1563646860500%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Joe Mihalich edited a comment on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat Same error on 2.186. Rolled back to 2.180 as others did, and problem went away. ERROR: Step ‘[ArtifactDeployer] - Deploy the artifacts from build workspace to remote locations’ aborted due to exception: java.lang.NoSuchFieldError: SIZEat org.jruby.ext.posix.HeapStruct.(HeapStruct.java:52)at org.jruby.ext.posix.LinuxPOSIX.allocateStat(LinuxPOSIX.java:44)at org.jruby.ext.posix.LinuxPOSIX.stat(LinuxPOSIX.java:87)at com.atlassian.ant.tasks.PermissionsUtils.getPermissions(PermissionsUtils.java:21)at com.atlassian.ant.tasks.CopyWithPerms.doFileOperations(CopyWithPerms.java:75)at org.jenkinsci.plugins.artifactdeployer.service.LocalCopy$1CopyImpl.doFileOperations(LocalCopy.java:60) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.16928.1563646860649%40Atlassian.JIRA.
[JIRA] [git-plugin] (JENKINS-32174) Git Plugin not finding jobs building on branches with forward slashes
Title: Message Title Joe Mihalich commented on JENKINS-32174 Re: Git Plugin not finding jobs building on branches with forward slashes Hi, glad you were able to reproduce it. We don't usually have this case we're we're building off branches, so it's been a while since i've last had a job that tries to build a branch with slashes. So i'm not sure what versions it would have worked on. I seem to recall a while ago that this same problem existed, and it was due to a regex change in the plugin that was searching for jobs. But obviously the problem could be totally different now. Thanks for helping! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-32174) Git Plugin not finding jobs building on branches with forward slashes
Title: Message Title Joe Mihalich created an issue Jenkins / JENKINS-32174 Git Plugin not finding jobs building on branches with forward slashes Issue Type: Bug Assignee: Mark Waite Attachments: job.jpg Components: git-plugin Created: 22/Dec/15 5:21 PM Labels: jenkins git plugins branch slash Priority: Minor Reporter: Joe Mihalich I have a git repo called uberad-platform. There is a branch in this repo called: jmihalich/bidders/dynamicHosts. When i commit changes to this branch and push to the remote repo, the post receive hook makes the following curl command to the jenkins server: curl http://jenkins.ubermedia.com:8080/git/notifyCommit?url="">:uberad-platform=jmihalich/bidders/dynamicHosts. However, jenkins responds with this: No git jobs using repository: :uberad-platform and branches: jmihalich/bidders/dynamicHosts I've attached a screenshot of the relevant portion of the
[JIRA] [git-plugin] (JENKINS-32174) Git Plugin not finding jobs building on branches with forward slashes
Title: Message Title Joe Mihalich commented on JENKINS-32174 Re: Git Plugin not finding jobs building on branches with forward slashes Btw, forgot to mention versions i'm on: jenkins: 1.638 Git plugin: 2.4.0 Git client plugin: 1.19.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Joe Mihalich commented on JENKINS-20569 Polling with excluded regions dont prevent job triggered Ok, I get it. So how do i get the behavior back to not do remote polling and make it work like 1.4.0? 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Joe Mihalich commented on JENKINS-20569 Polling with excluded regions dont prevent job triggered Confirmed this works for me. Thanks for the help! 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Joe Mihalich commented on JENKINS-20569 Polling with excluded regions dont prevent job triggered I don't understand that. This feature was working fine in the 1.4.0 git plugin. Something must have been broken. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Joe Mihalich commented on JENKINS-20569 Polling with excluded regions dont prevent job triggered I am having the exact same issue with included regions not being honored. Every job on the branch that git sends gets built regardless of what's in the included regions. Was on 1.4 before this and it was working great. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20389) Merge commits trigger uneccessary builds when Include/Exclude regions are defined
Joe Mihalich commented on JENKINS-20389 Merge commits trigger uneccessary builds when Include/Exclude regions are defined I'm having the exact same issue in the 2.0 git 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/groups/opt_out.
[JIRA] [git] (JENKINS-20389) Merge commits trigger uneccessary builds when Include/Exclude regions are defined
Joe Mihalich edited a comment on JENKINS-20389 Merge commits trigger uneccessary builds when Include/Exclude regions are defined I'm having the exact same issue in the 2.0 git plugin. I have to downgrade to 1.4.0 because of this bug. I can't have the entire project building every time one file changes. Please fix this ASAP. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Joe Mihalich edited a comment on JENKINS-20569 Polling with excluded regions dont prevent job triggered I am having the exact same issue with included regions not being honored. Every job on the branch that git sends gets built regardless of what's in the included regions. Was on 1.4 before this and it was working great. I have to downgrade to 1.4.0 because of this bug. I can't have the entire project building every time one file changes. Please fix this ASAP. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18828) Jobs disappear
Joe Mihalich commented on JENKINS-18828 Jobs disappear Hi, is anyone looking into this problem? I'm stuck on build 522 and cannot upgrade. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18828) Jobs disappear
Joe Mihalich commented on JENKINS-18828 Jobs disappear Hey, anyone following this ticket. The issue here is the same as another reported issue: JENKINS-19398. Enable the javadoc plugin in jenkins, and the problem is solved. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18828) Jobs disappear
Joe Mihalich commented on JENKINS-18828 Jobs disappear This problem happened to me when i upgraded from 522 to 524 yesterday. Restoring to 522 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/groups/opt_out.
[JIRA] [core] (JENKINS-18828) Jobs disappear
Joe Mihalich edited a comment on JENKINS-18828 Jobs disappear This problem happened to me when i upgraded from 522 to 524 yesterday. Restoring to 522 fixed the problem. I also have projects with display names with spaces and dashes in them. 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/groups/opt_out.
[JIRA] (JENKINS-13593) Seems to not handle having builds in seperate folder
[ https://issues.jenkins-ci.org/browse/JENKINS-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162221#comment-162221 ] Joe Mihalich commented on JENKINS-13593: At minimum the builds directory field is completely non functional. It updates the build-directory in the master config.xml but it does not even attempt to create the jobs in that directory. The jobs are always created in the jenkins home dir/jobs. It doesn't seem like this variable is meant to specify a jobs directory. The field description in the help doesn't match the field title. This field does not work for me in builds 459-461 (minimum). I don't know if they worked before those builds. Anyway, as a work around till you figure this out, I just left the defaults alone, and deleted the jobs workspace directory, and created them again as symlinks to the drive i wanted them created on. This seems to work fine. The functionality we need for my purposes is a way to specify the directory where the workspaces go, and where the jobs go. Thanks, Joe Seems to not handle having builds in seperate folder - Key: JENKINS-13593 URL: https://issues.jenkins-ci.org/browse/JENKINS-13593 Project: Jenkins Issue Type: Bug Components: scm-sync-configuration Affects Versions: current Environment: Ubuntu 11.10 Jenkins 1.461 SCM Sync Configuration Plugin 0.0.5 Reporter: Christian Lövsund Assignee: Frédéric Camblor Attachments: jenkins.png ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.IllegalArgumentException: Err ! File [/mnt/store/jenkins/CodeGenerationMaven/builds/2012-04-25_15-39-35/build.xml] seems not to reside in [/var/lib/jenkins] ! at hudson.plugins.scm_sync_configuration.JenkinsFilesHelper.buildPathRelativeToHudsonRoot(JenkinsFilesHelper.java:12) at hudson.plugins.scm_sync_configuration.strategies.model.PatternsEntityMatcher.matches(PatternsEntityMatcher.java:21) at hudson.plugins.scm_sync_configuration.strategies.AbstractScmSyncStrategy.isSaveableApplicable(AbstractScmSyncStrategy.java:22) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.getStrategyForSaveable(ScmSyncConfigurationPlugin.java:172) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationSaveableListener.onChange(ScmSyncConfigurationSaveableListener.java:19) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:78) at hudson.model.Run.save(Run.java:1571) at hudson.maven.MavenModuleSetBuild.setMavenVersionUsed(MavenModuleSetBuild.java:388) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:581) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475) at hudson.model.Run.run(Run.java:1434) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
