I'm about to migrate Jenkins from version 2.190.3 to 2.204.6. As I know, I need to update installed plugins manually after updating Jenkins. I've got two questions here.
Does the Jenkins update affect current plug-in? or does it work the same as before updating the plug-in?
How can I find the expected side effects when I proceed with the update? Are there any tips?
Does the Jenkins update affect current plug-in? or does it work the same as before updating the plug-in?
Ans: Jenkins only update jenkin-core, it doesn't update current plugin. However, some plugin may be broken after update Jenkins-core due to incompatibility to new Jenkins-core
How can I find the expected side effects when I proceed with the update? Are there any tips?
Ans: we can not to be sure any expected side effect. So, when you proceed with the update, just go to "Manage Jenkins", it will shows you broken plugins that need to be upgraded to new version.
The recommended approach is to update all your plugins to "latest (compatible)" as possible, then upgrade Jenkins, the upgrade your plugins again.
Read the Upgrade Guide ans Change log. 2.204.6 is still very old. Recommend to 2.263.4 first as 2.277.x will break many plugins as a result of tables to divs migration.
Plugins are/must be upgraded separately from the app. Existing plugins may no longer be compatible, typically for security issues or a core plugins being decoupled. Some plugins may only work with newer core versions.
You should take a copy of your instance & config, update that and validate, then move to your real system.
Related
thanks for taking the time to read this.
I’m a graduate DevOps engineer at my organisation and I have been tasked with trying to automate a Jenkins upgrade for all our instances (RHEL 7 servers) across the estate. I have written a role in ansible which automates the update using .rpm files and have tested that the role does correctly update the application.
I otherwise have very little to no experience at all using Jenkins and don’t know a whole lot about the application itself.
In my research I have seen conflicting information about which is the best method to upgrade Jenkins, but an incremental upgrade path seems to be the best approach, or most widely advised. Some of the oldest instances of Jenkins on our estate are sitting at version 2.121.x so are quite out of date.
I have read the upgrade path guide and I’m considering upgrading to the first release of each major version of Jenkins but I really don't understand all the specific pieces of information given about the changes made to the Jenkins application and what things I should DEFINITELY be doing before installing the next major version. Should I also be updating the plugins manually from the GUI after every single upgrade step or should I update the plugins after updating to the latest version of Jenkins first?
Any advice on this is really appreciated as I really don’t know what I’m doing. Thanks a lot.
As per the instruction provided in this link renamed one of the gerrit project. However now don't see this project changes in Open, Merged, Abandoned list. Something is wrong in the process of renaming?
Our gerrit version is - 2.13 and offline indexing will impact the productivity. Online is it possible to perform this particular project and changes indexing only?
You could try these two related options:
gerrit index start
gerrit index changes
Note: your Gerrit version is really old, you should think seriously in an update to a newer one.
I'm new to Jenkins. I'm using Jenkins 2.5. I'm using the TFS plugin (https://wiki.jenkins-ci.org/display/JENKINS/Team+Foundation+Server+Plugin) 4.1.0. Whenever I run a job that gets latest from TFS, TFS first lists every workspace which is a problem because I work for a large company - it lists 5,000 workspaces. This page https://github.com/jenkinsci/tfs-plugin/pull/65/commits seems to indicate that a ShowWorkspaces flag was added, but I can't find it anywhere. Maybe this was never added. Does anyone have a way to get Jenkins to stop listing all TFS workspaces?
It's a known issue for now. And seem to be fixed until version 4.2.0
I'll most likely include a fix for this defect in version 4.2; I'll
update this issue once it's released.
Olivier Dagenais
Moreover, this flag was added successful https://github.com/jenkinsci/tfs-plugin/pull/65/commits/d56346c4b3989a3edaed547ae55ed39233743be8
I'm going to upgrade our jenkins-ci to the latest version. I'm following this wiki page (Going for the upgrade button in the "Manage jenkins page"): How to upgrade jenkins
My question is this, we have a lot of jobs that constantly run (some timed jobs, some triggered jobs). When upgrading, should (or even need) I disable all jobs before hand? If there are jobs currently running, should (or even need) i terminate them?
It depends a lot how you deployed you CI. If you installed by default (no custom settings i assume you can follow the auto procedure that you already provided in link).
When upgrading, should (or even need) I disable all jobs before hand?
When upgrading you should put your Jenkins instance in the quiet mode Configure > Manage > Quiet down, this will prevent further builds to be executed, also it will let all running builds to finish, i hope this answer to your both questions.
Speaking more about jobs, you should make a backup first in case something goes wrong.
Also you should think a lot about plugins and review them all since some of them might not work as you expect since you are upgrading to the new fresh Jenkins core. There is one plugin called plugin usage which might help you to understand your current status
I'm developing a CI (Continuous Integration) for my application.
So, I'm using Jenkins with HockeyApp (equal to TestFlyApp).
The problem is that HopckeyApp only accepts new versions of an application if it different versions from the last one added, else it gives me an error of already existing version, and no update.
I was reading about the apple tool Agvtool to update the value CFBundleShortVersionString.
My main problems are,
how to do this in Jenkins automatically.
How to update the project repository (Git in my case),for the next build it knowing which is the last version that was updated, or any other option to keep track of the last version updated.
I am trying to do this, but other approach will be accepted has well.
Thanks in advance.
It is recommended to update the CFBundleVersion and not the CFBundleShortVersionString, see http://support.hockeyapp.net/kb/how-tos/how-to-do-versioning-for-beta-versions-on-ios-or-mac
The following blog posts goes through the whole setup and also shows how to automatically update the version number using git tags: http://monitzer.com/?p=75
Here is another approach using git to update the version number: https://gist.github.com/3395649