Re: Link to "Bitbucket Pipeline for Blue Ocean" in Plugin Manager doesn't work

https://issues.jenkins-ci.org/browse/JENKINS-47943 Thanks. -- 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. To vie

Re: Link to "Bitbucket Pipeline for Blue Ocean" in Plugin Manager doesn't work

Report the bug to https://issues.jenkins-ci.org/ * . *Good instructions for effective Jenkins bug reporting at https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue Mark Waite On Wed, Nov 8, 2017 at 12:41 PM itchymuzzle wrote: > Suc

Link to "Bitbucket Pipeline for Blue Ocean" in Plugin Manager doesn't work

Successfully installed plugin. The link for the text of name of the plugin does work [https://wiki.jenkins-ci.org/display/JENKINS/Blue+Ocean+Plugin/blueocean-bitbucket-pipeline] Get page not found.

Jenkins Plugin Manager Page | Stack Trace errored out

Hi, My Jenkins version 1.580 I have tried to open plugin manager page ...Which is showing Stack Trace error page and below it lists plugins available for update. Not able to navigate tables -> Installed or Available PFA log. Please show me some light - which causes this issue. Regards,

Re: Jenkins Plugin Manager: "This plug cannot be enabled / It has one or more dependencies" – but the dependencies cannot be fulfilled

On 09.04.2016, at 10:19, Wojtek wrote: > - some of them (2/3 of the list) are still greyed out (inactive) which > basically means they are not loaded/funcioning. > > Ticking some of those makes others change from "inactive" state (being greyed > out) to active (so I can check/uncheck them). >

Re: Jenkins Plugin Manager: "This plug cannot be enabled / It has one or more dependencies" – but the dependencies cannot be fulfilled

Actually I've played a bit with it and it looks like the plugins are enabled afterall - sorry for the confussion. Wojtek On Sat, Apr 9, 2016 at 10:19 AM, Wojtek wrote: > I've run into this JENKINS-32340 page, but even when I delete all the > files with ".disabled" suffix and restart Jenkins the

Re: Jenkins Plugin Manager: "This plug cannot be enabled / It has one or more dependencies" – but the dependencies cannot be fulfilled

I've run into this JENKINS-32340 page, but even when I delete all the files with ".disabled" suffix and restart Jenkins the result is following: - all plugins are enabled (have a tick next to the name) - some of them (2/3 of the list) are still greyed out (inactive) which basically means they ar

Re: Jenkins Plugin Manager: "This plug cannot be enabled / It has one or more dependencies" – but the dependencies cannot be fulfilled

This is a known issue on the configuration UI we're tracking as JENKINS-32340. The workaround right now is to delete the files named PLUGINNAME.jpi.disabled in JENKINS_HOME/plugins, then restart Jenkins. 1: https://issues.jenkins-ci.org/browse/JENKINS-32340 On 24.11.2015, at 10:50, Jochen Hayek

Re: Jenkins Plugin Manager: "This plug cannot be enabled / It has one or more dependencies" – but the dependencies cannot be fulfilled

Hi, I've run today into exactly the same issue (Jenkins 1.656). Basically it looks like the sate checking is wrong - I wasn't able to select "Static Analysis Collector Plug-in" but many required it (it was greyed out because of missing dependencies). I've fiddled a bit and found out that it's po

Re: Jenkins Plugin Manager: "This plug cannot be enabled / It has one or more dependencies" – but the dependencies cannot be fulfilled

Can you post which version of Jenkins you use and which plugins (if there are not too many)? -- 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+u

Jenkins Plugin Manager: "This plug cannot be enabled / It has one or more dependencies" – but the dependencies cannot be fulfilled

Hi there! I am experiencing the same problem as described by philm88 here: http://echelog.com/logs/browse/jenkins/1444600800 In my case no restoring of a backup is involved, and I don't think that particular issue is related. In the installed plugins page, the enabled box is ticked, but greyed

RE: plugin manager

, Dick Sent: Thursday, March 19, 2015 11:12 AM To: jenkinsci-users@googlegroups.com Subject: RE: plugin manager It means that the newer version of jenkins has newer versions of those “build-it” plugins and as long as they are marked a “pinned”, they will not be updated. To update them to the

RE: plugin manager

-users@googlegroups.com] On Behalf Of Ashish Yadav Sent: Thursday, March 19, 2015 10:59 AM To: jenkinsci-users@googlegroups.com Subject: plugin manager I just changed my Jenkins from v1.583 to LTS 1.596.1 and am getting a warning on the manage jenkins page. This version of Jenkins comes with new

plugin manager

I just changed my Jenkins from v1.583 to LTS 1.596.1 and am getting a warning on the manage jenkins page. This version of Jenkins comes with new versions of the following plugins that are currently pinned in the plugin manager. It is recommended to upgrade them to at least the version bundled

Re: Javadoc plugin 1.0 displaying error in plugin manager

: > > From: jieryn >To: Jenkins Users >Sent: Friday, May 31, 2013 9:33 AM >Subject: Re: Javadoc plugin 1.0 displaying error in plugin manager > > >Greetings, > >On Fri, May 31, 2013 at 9:11 AM, Kamal Ahmed wrote: >> question is how come javadoc, which is a

Re: Javadoc plugin 1.0 displaying error in plugin manager

Greetings, On Fri, May 31, 2013 at 9:11 AM, Kamal Ahmed wrote: > question is how come javadoc, which is a core plugin, depending on testswarm? There is absolutely no evidence that you have ever reported that even remotely links javadoc, or the Jenkins Javadoc Plugin, to the issue. So unless you

Re: Javadoc plugin 1.0 displaying error in plugin manager

question is how come javadoc, which is a core plugin, depending on testswarm ? > > From: jieryn >To: Jenkins Users >Sent: Friday, May 31, 2013 8:25 AM >Subject: Re: Javadoc plugin 1.0 displaying error in plugin manager > > >Gree

Re: Javadoc plugin 1.0 displaying error in plugin manager

Greetings, On Fri, May 31, 2013 at 8:09 AM, Kamal Ahmed wrote: > any idea how to resolve this ? Uninstall the TestSwarm plugin. -- 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,

Javadoc plugin 1.0 displaying error in plugin manager

I installed jenkins LTS 1.501.1 via rpm, on centos 6.4 then upgraded some plugins, and start getting VERY Slow performance, so i manually removed some plugins , dont remember wich ones. Now i uninstalled and reinstalled the rpm, and then copied the core hpi files to /var/lib/jenkins/plugins/ b

Re: Problems when updating plugins manually and via Plugin Manager

The slightly longer answer is that there is code in Jenkins to migrate the files to the new extension, but it can get confused so safest is to follow what your Jenkins looks to be doing so that you don't keep re-invoking the migration code (which is designed to run once, but each time you put a .hp

Re: Problems when updating plugins manually and via Plugin Manager

If your $JENKINS_HOME/plugins has files called .jpi then RENAME the .hpi files to .jpi *before* copying them into $JENKINS_HOME/plugins IOW use the naming convention that your Jenkins is using. On 7 May 2013 20:03, Tony P wrote: > Hi, > > I have been having quite a bit of trouble manually inst

Problems when updating plugins manually and via Plugin Manager

Hi, I have been having quite a bit of trouble manually installing plugin updates and would like to pose a theory. I have a system behind firewalls without internet access, it was originally created in a different environment WITH internet access and copied here. When I download the latest plu

Problems updating plugins manually and via "Plugin Manager"

ed. I saw somewhere that if you update via Plugin Manager the files are *.jpi but if you download and install manually they are *.hpi My working theory is that I am correct to delete the *.jpi files and the problem is the inconsistency between *.jpi and *.hpi. I am downloading from https://up

Plugin Manager Issues

Setting up a jenkins instance behind a proxy as the host doesn't have access to the internet. Both the Updates and the Available tabs come up empty. Under advanced settings I've set Server to the FQDN of our proxy as well as the port. I've left user name and password blank (though jenkins fi

Jenkins 1.496 on Windows Server 2008: Update Plugin Manager does not work

Jenkins 1.496 on Windows Server 2008 runs so far. But if I go to *Plugin Manager / Advanced *and try to update the plugin information from the update center URL (press "*Check now*") the following page displays "*Checking Updates...*" but nothing happens and final

Re: Plugin Manager Updates does not display any updates

One more thing when I press the check now button on the Advanced Tab under Plugin Manager it just says Checking Updates... but just sits there and never comes back Here is what the log file reports Aug 13, 2012 11:26:02 AM hudson.model.UpdateSite doPostBack INFO: Obtained the latest update

Re: Plugin Manager Updates does not display any updates

on where the Plugin Manager is not > showing any plugin updates. > > This is what I have on Update Site under the Advanced Tab under Plugin > Manager Section > > http://updates.jenkins-ci.org/update-center.json > > Jenkins Version is 1.460 > Running on Ubuntu > > Has anyone seen this issue? > > Thanks >

Plugin Manager Updates does not display any updates

Hello Folks. I am running into the following situation where the Plugin Manager is not showing any plugin updates. This is what I have on Update Site under the Advanced Tab under Plugin Manager Section http://updates.jenkins-ci.org/update-center.json Jenkins Version is 1.460 Running on