Thanks, Editing the config.xml and then reloading removed the action. There was allot of trouble the last time we updated so that probably won't happen till we aren't busy or it totally collapses.
On Wednesday, September 24, 2014 7:03:09 PM UTC-4, Mark Waite wrote: > > > On Wed, Sep 24, 2014 at 9:06 AM, <blaze...@gmail.com <javascript:>> wrote: > >> More info >> >> Git Client Plugin >> <https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin> >> Shared library plugin for other Git related Jenkins plugins. >> 1.10.21.0.7 >> Git Parameter Plugin >> <https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Plugin> >> This plugin allows you to choose between Git tags or sha1 of your SCM >> repository so Git Plugin installed is required. >> Warning: This plugin is built for Jenkins 1.554.1 or newer. It may or may >> not work in your Jenkins. >> 0.3.20.2 >> Git Plugin <https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin> >> This plugin allows use of Git <http://git-scm.com/> as a build SCM. A >> recent Git runtime is required (1.7.9 minimum, 1.8.x recommended). Plugin >> is only tested on official git client <http://git-scm.com/>. Use exotic >> installations at your own risks. >> 2.2.61.4.0 >> >> > If I am guessing correctly, that table hints that you upgraded from git > client plugin 1.0.7 to git client plugin 1.10.2 and from git plugin 1.4.0 > to git plugin 2.2.6. That is a long jump. The git plugin transition from > version 1 to version 2 was a major transition. > > You're also running a Jenkins version which is not a long term support > version but is over a year old. > > For the specific problem you're seeing, you might try saving the job > definition from the user interface, then loading it again. There may be > some gaps in the upgrade process from a plugin version that old to the > current plugin version. > > You could also attempt to remove the git publisher section from the > config.xml file of the job (keep a backup copy of the working job > definition just in case), then attempt to add the git publisher section > again. > > You could also update to a more recent Jenkins version, preferably a long > term support version (like 1.565.2) to see if that resolves the problem > you're seeing. > > The git plugin and the git client plugin are intended to work with the > Jenkins version you're using. They are dependent on the long term support > version 1.509. However, that is a long time ago and there probably are not > many people still running 1.517. > > Thanks, > Mark Waite > > >> On Wednesday, September 24, 2014 11:04:33 AM UTC-4, blaze...@gmail.com >> wrote: >>> >>> I added the Git Publish post build action to a project and there's no >>> delete. This is a problem instead of an annoyance because all it does by >>> default is "Build step 'Git Publisher' marked build as failure" >>> How do I remove the action? >>> >>> >>> Jenkins ver. 1.517 <http://jenkins-ci.org/> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-use...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Thanks! > Mark Waite > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
