I have been using Jenkins with the TFS plugin for several years but after installing Jenkins on a new machine, it seems that the TFS plugin cannot be found in the update center. All the other plugins that I could search for seem to work but not TFS, as if it had been deleted from there. I have tried using both jenkins-lts and jenkins weekly on two separate machines (both macs).
This is the plugin I am talking about: https://github.com/jenkinsci/tfs-plugin
The old wiki page for it also seems to have been removed (I get a HTTP 403 Forbidden reply when trying to access that): http://wiki.jenkins-ci.org/display/JENKINS/Team+Foundation+Server+Plugin and the newer plugin index doesn't seem to know about this plugin: https://plugins.jenkins.io/
I have tried to look on the Jira issue tracker but couldn't find anything that seemed relevant.
Could anyone assist?
Okay so after struggling with this for a while, I figured out what had happened.
There was a security issue for the TFS plugin that hasn't been fixed: https://www.jenkins.io/security/advisory/2020-09-01/#SECURITY-1506
On top of that, it was found that the TFS SDK that is bundled with the plugin is not open source, which goes against Jenkins policy (see INFRA-2751 for more details).
This means that the plugin has been removed from the update center in this commit at the end of October 2020.
If the security issue is acceptable, the plugin can still be installed by downloading the .hpi from Github and then manually install the plugin in Jenkins: Manage Jenkins > Manage Plugins > Advanced > Upload Plugin and select the plugin file downloaded previously (Make sure to have git-plugin installed normally first so all additional dependencies are in place).
Thanks to the people on Jenkins Gitter that reminded me of the security issue as well as #ian-w on here that pointed at the actual problem.
Edit: I edited my answer to include Ian's comment.
2021-08-31: See additional details in this S/O response.
Related
I have updated my jenkins server and see the following message for some plugins. I am not sure how to fix this. I looked at the dependencies section for that plugin and I see they are already installed. Not sure what else is missing so I can see the update available. Dependency for this is Mailer which is already installed on my server.
That is frustrating but you can try uploading plugins manually.
You can download plugins from here link to plugin storage.
Of course you have to roughly see what version of the plugin goes with your jenkins version.
Once you downloaded 'proper' plugin version, you go to manage plugins, advanced tab and there you can upload the plugin file. After that restart jenkins and check changes. You should really go to manage plugins, updated plugin tab and update selected plugins...
It could be guess work, but I'm sure after a couple of guesses you'll get to the version of Jenkins you have.
You might need to upgrade jenkins.. here are all jenkins war files:
https://get.jenkins.io/war-stable/
Last but not least... don't try to fix all dependencies.. fix those you use, rest is optional.
Fore some reasons I have to use Jenkins 2.32 and I need to install some plugins there. Machine with it has no internet, so I only can upload plugin file to install it from file.
So, the problem is there any easy way to obtain required plugin for required Jenkins version with all it's dependencies?
p.s.
I can't update Jenkins - it's out of my power.
p.p.s.
I find only way to download old versions of plugin, but by this way I can't check dependencies and required jenkins version before loading.
I had such an environment before.
Warning: it's an annoying process.
Because there was no internet, we uploaded all plugins manually, i.e. looking at the plugin page (e.g. https://plugins.jenkins.io/git/) and then downloading from the archive (e.g. https://updates.jenkins.io/download/plugins/git) the .hpi file. As you have to use a relatively old version of Jenkins you may want to check the changelog of the plugin, if you have to use an older version.
In addition on each plugin page the dependencies are listed and you have to repeat the above steps for each dependency.
The only good thing is that usually Jenkins gives you hints, which dependencies are missing after you uploaded a plugin.
You can probably extract the information out of the plugin-versions.json in the Jenkins Update Center.
For more information about the layout of update center, see this document.
You may also find my previous response on jenkins failed to install plugins - docker image (with groovy scripts) helpful
My jenkins jobs started to disable by themselves when the svn checkout fails. I explored previous builds and they never disabled when failed. This new behaviour is not desired for me.
The message in the new build log is as follows:
...
One or more repository locations do not exist anymore for myJob1, project will be disabled.
The project has been disabled
ERROR: Failed to parse svn info for 'repourl'
...
I downgraded the jenkins Subversion plugin which was recently updated, and the multi scm plugin as well. However, the problem remains.
Any suggestion?
That message is coming from the Blame Subversion Plugin. Is it possible you recently installed that plugin? Or that you recently turned on SVN blame as an option?
I think this is an undocumented(?) behavior of the Subversion Plugin to automatically disable a job if the SVN URL is not valid (anymore). This behavior seems to be implemented for several years now, as this discussion from 2012 indicates. I just learned about this behavior only after moving a SVN project to a different folder which caused my project to be disabled. I did not find any information on how to disable this behavior.
Update 2021/09:
The behavior is apparently still present and there seems to be no way to disable it.
There is a corresponding feature request on the Jenkins JIRA though: JENKINS-10922
Please vote for this feature request!
I am trying to install the blueocean beta plugin for my Jenkins server.
The first thing I saw is that I was not getting the proper plugins so I have updated my plugin url to:
http://updates.jenkins-ci.org/experimental/update-center.json
Currently did a clean install without any other plugins, maybe there are some other plugins that are required for the blueocean plugin?
I am using version 2.19.4, so far my experience with Jenkins has been terrible and there does not seem to be a proper support forum so I am asking here.
Hopefully somebody can help me out.
I executed the update (http://updates.jenkins-ci.org/update-center.json), restarted Jenkins (v2.19.4) so "Blue Ocean Beta" showed up at Manage Plugins > Available and I was able to install.
I have a question about updating GitHub plugin.
Everytime I do an update plugin such as GitHub and restart the jenkins, Jenkins start crashing. when I try to access jenkins through URL in my browser, the error page shows up with some exception "class not found jenkins/model jenkins" . and then in order to make jenkins working again , I have to delete the plugin entirely from the plugins directory. I wish someone has an answer for this because I really need to make my github projects available to jenkins for build. Thanks
It is a very usual problem with Jenkins. My workaround was to either update the jenkins (where ever it is installed) and restarting the hudson service.
sometimes even restarting the service works.
often you might need to remove those plugins from within (/var/lib/hudson/plugins/) and restart the service.