Re: Log location and WEBROOT changed after Jenkins upgrade

Il 02/05/2022 21:44, Mark Waite ha scritto: Based on https://issues.jenkins.io/browse/JENKINS-68313, it appears that the CentOS 7 implementation of systemd does not support the '%C' specifier.  Replace it with the text for the cache directory on your operating system. Thank you very much Mar

Re: Log location and WEBROOT changed after Jenkins upgrade

On Monday, May 2, 2022 at 1:14:45 PM UTC-6 you wrote: > Hello, > I recently upgraded Jenkins from 2.263.4/2.303.3 to 2.332.2 on three > CentOS 7 machines, using the official jenkins.io packages from the > redhat-stable repository. > While Jenkins (since years!) always saved its log as /var/log

Log location and WEBROOT changed after Jenkins upgrade

Hello, I recently upgraded Jenkins from 2.263.4/2.303.3 to 2.332.2 on three CentOS 7 machines, using the official jenkins.io packages from the redhat-stable repository. While Jenkins (since years!) always saved its log as /var/log /jenkins/jenkins.log, now it sends all log messages to syslog (

Re: Jenkins upgrade from 2.250 to 2.275

I was able to switch from Jenkins weekly to LTS (2.250 to 2.277.3) . After the upgrade, the Save option is not working. I'm receiving this error: This page isn't working, didn't send any data. ERR_EMPTY_RESPONSE. Any suggestions? Thanks in Advance. On Wednesday, June 9, 2021 at 3:17:31 PM UTC-4

Re: Jenkins upgrade from 2.250 to 2.275

Thank you.I will try. On Tuesday, June 8, 2021 at 7:56:55 AM UTC-4 jn...@cloudbees.com wrote: > you can just switch the war. > Make sure you do not go to a lower version though. in other words if you > are on 2.275 you could use 2.289.1 but you use 2.292 then you will have to > wait for the

Re: Jenkins upgrade from 2.250 to 2.275

you can just switch the war. Make sure you do not go to a lower version though. in other words if you are on 2.275 you could use 2.289.1 but you use 2.292 then you will have to wait for the next LTS to be released above that (which will be about 3 months time). On Monday, May 31, 2021 at 6:3

Re: Jenkins upgrade from 2.250 to 2.275

Thank you Björn . I will look into this. Are there any steps I need to consider before migrating from weekly versions to LTS or just download the war and replace it with the current war file? Really appreciate your help ! On Monday, May 31, 2021 at 2:51:24 AM UTC-4 ice...@googlemail.com wrote:

Re: Jenkins upgrade from 2.250 to 2.275

BTW, if you don't want to do too frequent updates (upgrade each week and check for all changes each time), I would consider switching to the LTS series (2.277.1 in your case). Then such changes would be easier to find in the LTS changelog. Björn Björn Pedersen schrieb am Montag, 31. Mai 2021 u

Re: Jenkins upgrade from 2.250 to 2.275

Hi, it seems you did not upgrade all plugins as well. These effects are caused by the tables-to-div migrations. See https://www.jenkins.io/doc/developer/views/table-to-div-migration/ for more details... Björn s.p...@gmail.com schrieb am Montag, 31. Mai 2021 um 02:52:14 UTC+2: > After I upgr

Jenkins upgrade from 2.250 to 2.275

After I upgraded Jenkins from 2.250 to 2.275, I noticed that the UI for the Jobs configuration looks different. The section for Source Code Management/Build Triggers/Build Environment/build/Post-build actions are missing at the top of the job configuration page and I see a couple of Artifactory

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Yes, there is only one file to update the remoting.jar. If you install the remoting process as a service the update is done by the service see https://github.com/jenkinsci/windows-slave-installer-module and https://github.com/winsw/winsw/blob/master/doc/installation.md#winsw-installation-guide If

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Thanks for the suggestions guys. I copied the new agent.jar to the machine when using the new version. I am executing it on demand from the command line. How would I update the remoting.jar on the slave? As far as I can tell there is only one .jar used on the slave and that is the one you down

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Remember that JNLP agents do not update the remoting jar if are not configured to do that, on Jenkins Core 2.248 there is a change on the remoting version, I bet you can bump the version to 2.247 without issues. To upgrade to 2.248+ you would need to upgrade the remoting jar on the JNLP agents.

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Hello, although I found nothing in the LTS upgrade guide... Did you get the current slave.jar from the new master ? Otherwise you might have a compatibility issue between new master and old slaves, Regards Martin Minimos schrieb am Montag, 15. Februar 2021 um 14:30:53 UTC+1: > So I rolled th

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

So I rolled the version back and the issue has gone away. I will need to do a incremental upgrade of the WAR to find out which version breaks the functionality On Friday, 12 February 2021 at 15:13:30 UTC Minimos wrote: > > Thanks I'll take a look at the information. > > I am using .Net 4.5 so s

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Thanks I'll take a look at the information. I am using .Net 4.5 so should not be an issue, but there is an interesting point re JNLP. I'll go through the document and double check everything. In the meantime do others have any other pointers? On Friday, 12 February 2021 at 14:55:58 UTC Mark Wa

Re: Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

The Jenkins 2.249.1 upgrade guide notes that Microsot.NET 2.0 support has been removed. See https://www.jenkins.io/doc/upgrade-guide/2.249/#upgrading-to-jenkins-lts-2-249-1 in case that affects your installation. On Fri, Feb 12, 2021 at 7:49 AM 'Minimos' via Jenkins Users < jenkinsci-users@google

Jenkins Upgrade 2.235.1 to 2.263.3 All Nodes Can't Connect

Hi, We recently updated Jenkins as per the subject line on our Windows boxes All plugins were updated at the same time, however we can no longer get our nods to communicate with the master. A Java Io exception of Connection time Out is displayed. There have been no changes to our firewall or

Re: Jenkins Upgrade

Thanks Devin/Mark. I will try disabling jqs-monitoring first to see if the issue goes away. yes, we are using Tomcat and I will try with Jetty too. Thanks M.Madhu On Mon, Mar 30, 2020 at 2:23 PM Devin Nusbaum wrote: > From a quick look at the thread dumps, I think that the main problem is >

Re: Jenkins Upgrade

>From a quick look at the thread dumps, I think that the main problem is that >JQSMonitoring (from Job/Queue/Slaves Monitoring Plugin) ends up loading builds >in its constructor, which is invoked during Jenkins startup because it is a >RootAction >

Re: Jenkins Upgrade

I'm afraid that it is much more difficult for anyone to assist with a problem that can't be duplicated. On Mon, Mar 30, 2020 at 12:42 PM M.Madhusudana Reddy wrote: > Thanks Mark. I can definitely try that. > > But again as I mentioned early, If I kill the process and start the > jenkins JVM(with

Re: Jenkins Upgrade

Thanks Mark. I can definitely try that. But again as I mentioned early, If I kill the process and start the jenkins JVM(with the same JAVA version), I may not see this issue. This is intermittent and I need to keep trying with the restarts to reproduce the issue. Thanks M.Madhu On Mon, Mar 30,

Re: Jenkins Upgrade

Any chance you can duplicate the same problem on Java 8 update 242 (the current release)? Java 8 u121 was released in Jan 2017. Significant changes were made to Java 8 in update 161 (WIkipedia says " 21 Security fixes, 3 new features, 9 changes and 1 bug fix from 8u152."). Update 231 (Oct 2019)

Re: Jenkins Upgrade

I dumped the thread dump into one of the thread dump analysis tool and the tool is reporting on Dead Lock. Thread CpsStepContext.isReady [#4] is in deadlock with thread Finalizing set up Thanks M.Madhu On Mon, Mar 30, 2020 at 12:45 PM M.Madhusudana Reddy wrote: > Ok. I am able to reproduce th

Re: Jenkins Upgrade

Please note that AdoptOpenJDK produces both OpenJDK builds (i.e. HotSpot JVM) and OpenJ9 + OpenJDK class library builds. Cheers, Martijn On Thu, 12 Mar 2020 at 17:05, M.Madhusudana Reddy wrote: > Thanks for the update Mark. > > I believe we tried with AdoptOpenJDK and ran into same issue but I

Re: Jenkins Upgrade

Thanks for the update Mark. I believe we tried with AdoptOpenJDK and ran into same issue but I will confirm that and let you know. Thanks M.Madhu On Thu, Mar 12, 2020 at 9:15 AM Mark Waite wrote: > FYI IBM openJ9 is not supported by the Jenkins project. Initial testing > has found no showsto

Re: Jenkins Upgrade

FYI IBM openJ9 is not supported by the Jenkins project. Initial testing has found no showstoppers, but IBM OpenJ9 introduces a very significant difference between what you're running and what is used and tested by people in the Jenkins project. The Jenkins Platform SIG

Re: Jenkins Upgrade

Do you have the full thread dump from a tool like jstack? If so, please attach it to this thread, or paste it somewhere like gist.github.com or pastebin.com and then paste a link to it here. > On Mar 11, 2020, at 14:11, M.Madhusudana Reddy wrote: > > Hi Team, > > We

Jenkins Upgrade

Hi Team, We upgraded our jenkins instance from 2.107.3 to 2.204.3 and sometimes we notice that jenkins master is taking lot of time to come up and jenkins UI/application is unresponsive. I took a thread dump while we ran into this issue and noticed that application is suffering from deadlock.

Re: Jenkins upgrade from 2.73.3 to 2.138 deleted all views

lugins on top of 2.73 and then download 2.138 war and restart? >> Please correct my Jenkins upgrade process. Till now i was just downloading >> latest war and restart

Re: Jenkins upgrade from 2.73.3 to 2.138 deleted all views

response to my issue. > > I will explain how i am upgrading first. I downloaded the 2.138 war and > restarted Jenkins. is it correct way to upgrade? OR do i need to first > upgrade all plugins on top of 2.73 and then download 2.138 war and restart? > Please correct my Jenkins u

Re: Jenkins upgrade from 2.73.3 to 2.138 deleted all views

all plugins on top of 2.73 and then download 2.138 war and restart? OR Download 2.138 and restartJjenkins and then upgrade all plugins on top of 2.138? Please correct my Jenkins upgrade process. Till now i did many upgrades but i was just downloading latest war and restarting Jenkins was working

Re: Jenkins upgrade from 2.73.3 to 2.138 deleted all views

correct my Jenkins upgrade process. Till now i was just downloading latest war and restarting Jenkins was working. Regarding issues from log, i can below errors from log

Re: Jenkins upgrade from 2.73.3 to 2.138 deleted all views

I had issues when I did the upgrade for the LTS but updating the plugins to the latest versions available resolved that for me. Have you tried that? On Tuesday, March 26, 2019 at 7:24:37 AM UTC-7, Roshan Chandekar wrote: > > Hi All, > > Need help. I am trying to upgrade the jenkins from 2.73.1 to

Re: Jenkins upgrade from 2.73.3 to 2.138 deleted all views

Please don't hijack threads on the mailing list. Your question is very different from the original question being asked. On Tue, Mar 26, 2019 at 8:37 AM Suguna Sai wrote: > I am using jenkins 2.150.2 while installing npm getting below sub module > error. > > + npm install @angular/cli > npm ERR!

Re: Jenkins upgrade from 2.73.3 to 2.138 deleted all views

I am using jenkins 2.150.2 while installing npm getting below sub module error. + npm install @angular/cli npm ERR! path /jenkins/workspace/Project/repo/development/node_modules/angular-material npm ERR! code EISGIT npm ERR! git /jenkins/workspace/Project/repo/development/node_modules/angular-mate

Re: Jenkins upgrade from 2.73.3 to 2.138 deleted all views

Are you sure that you've installed the same plugins on the 2.138.4 installation as you had on the 2.73.1 installation? Have you placed all the files from the 2.73.1 JENKINS_HOME in the 2.138.4 JENKINS_HOME? Have you read the Jenkins log from the 2.138.4 installation as it starts, in case there ar

Jenkins upgrade from 2.73.3 to 2.138 deleted all views

Hi All, Need help. I am trying to upgrade the jenkins from 2.73.1 to 2.138.4. But it deleted all my views and all jobs showing under "All" tab. please let me know if someone fixed this issue. I tried the upgrade from 2.107 and there as well same issue. -- You received this message because you

Re: Jenkins Upgrade - Lost everything

Can you explain a little as to how you did so for other people to benefit? On Mon, May 14, 2018 at 9:38 AM 江南 wrote: > Thanks I managed to solve this. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and

Re: Jenkins Upgrade - Lost everything

Thanks I managed to solve this. -- 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 view this discussion on the we

Re: Jenkins Upgrade - Lost everything

Is the JENKINS_HOME set correctly for your new installation? If it is not set to c:\Jenkins, then Jenkins will use the default, which is the USERDIR\.jenkins. On Mon, May 14, 2018, 07:11 江南 wrote: > Hi, > > I have upgraded my jenkins to 2.121 but after I restart is asking me to > setup everythin

Jenkins Upgrade - Lost everything

Hi, I have upgraded my jenkins to 2.121 but after I restart is asking me to setup everything from beginning so I did. I created new account and new project in http://localhost:8080/. But when I check the C:\jenkins folder I can only see all my old projects in the workspace folder and user acco

Re: Slow loading of job configuration page after Jenkins upgrade

Just in case anyone runs into the same issue. I figured out that it was one of my Chrome extensions that was causing the slow load. Sorry, I didn't narrow it down to which one. I came about this by opening Jenkins in incognito mode. Opening the configure screen for a job was quick in this mode.

Re: Slow loading of job configuration page after Jenkins upgrade

Here's a thread dump shared in gist: https://gist.github.com/t3knoid/398bd00684ea5841c223ebcfed8a1c44 On Tuesday, November 7, 2017 at 3:14:49 PM UTC-5, Daniel Beck wrote: > > > > On 3. Nov 2017, at 19:42, t3knoid > > wrote: > > > > I tried that and I am at a lost as how to interpret the stac

Re: Slow loading of job configuration page after Jenkins upgrade

> On 3. Nov 2017, at 19:42, t3knoid wrote: > > I tried that and I am at a lost as how to interpret the stack. This happened > after updating to v2.87 and some of the plugins. I know this info is not much > help, but I'd appreciate how can I go about getting more info on how to > troubleshoot

Re: Slow loading of job configuration page after Jenkins upgrade

Not sure about the gc log. I thought it was a memory issue first. So I increased memory but that did not make a difference. I see the issue on other installations as well. This must be something to do with a plug-in. I am going to roll back and see if the behavior goes back to normal. On Friday

Re: Slow loading of job configuration page after Jenkins upgrade

I would look into your gc, first. Does jenkins write a garbage collection log? I don't remember. You may need to just give it more memory. On Friday, November 3, 2017 at 12:42:01 PM UTC-6, t3knoid wrote: > > I've recently upgraded Jenkins and plug-ins. After doing so, now every job > configurat

Re: Slow loading of job configuration page after Jenkins upgrade

BTW, the slow load also happens when creating a new free style project or a maven project. However, the slowness does not appear creating a pipeline project. On Friday, November 3, 2017 at 2:42:01 PM UTC-4, t3knoid wrote: > > I've recently upgraded Jenkins and plug-ins. After doing so, now every

Slow loading of job configuration page after Jenkins upgrade

I've recently upgraded Jenkins and plug-ins. After doing so, now every job configuration page loads very slow. Some at least 7-8 minutes. I've read that I need to profile the running java process with something like jstack to see which thread is taking a long time to complete. I tried that and I

Re: Agents not connecting after 2.60.3 Jenkins upgrade

Yes, the build agents are using jre1.8.0_144. Same version as the master. Thanks, Eddie -- 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+unsubsc

Re: Agents not connecting after 2.60.3 Jenkins upgrade

Are your build agents all running JRE 8? If not, they won't connect to Jenkins 2.60 and later. Java 8 is required. Mark Waite On Wednesday, October 25, 2017 at 1:19:00 PM UTC-6, edward.b...@sovos.com wrote: > > Hello, > > > > I am attempting to upgrade Jenkins on one of our sandboxes to the

Agents not connecting after 2.60.3 Jenkins upgrade

Hello, I am attempting to upgrade Jenkins on one of our sandboxes to the latest LTS version (2.73.2). The issue I have encountered is after upgrading, our build agents have all lost their connection to the master. I tried this a couple different ways to find out when the issue starts.

Re: Jenkins Upgrade Wizard fails from 1.609.3 -> 2.46.2

> On 15. May 2017, at 13:40, sweeney wrote: > > But there's over 100 of them and I was hoping that there was a small number > of metapackages I could install to achieve the same result as the failed > install wizard. My alternative is to verify/install over 100 packages by > hand. You're j

Re: Jenkins Upgrade Wizard fails from 1.609.3 -> 2.46.2

On Thursday, May 4, 2017 at 12:49:53 PM UTC+1, Daniel Beck wrote: > > > > On 03.05.2017, at 17:51, sweeney > wrote: > > > > I can see no way to easily upgrade to the latest Jenkins 2 goodies. Any > advice? > > These plugins are available on the Jenkins plugin manager. Just check the > 'avai

Re: Jenkins Upgrade Wizard fails from 1.609.3 -> 2.46.2

> On 03.05.2017, at 17:51, sweeney wrote: > > I can see no way to easily upgrade to the latest Jenkins 2 goodies. Any > advice? These plugins are available on the Jenkins plugin manager. Just check the 'available' tab and install from there. -- You received this message because you are sub

Re: Jenkins upgrade from 1.651 to latest LTS 2.32.X

> On 20.03.2017, at 12:54, mtnj...@gmail.com wrote: > > can you please guide us through the steps or important prerequites before > doing it. > Have you read https://jenkins.io/doc/upgrade-guide/ ? -- You received this message because you are subscribed to the Google Groups "Jenkins Users"

Jenkins upgrade from 1.651 to latest LTS 2.32.X

Hi All, We are planning to upgrade jenkins from 1.651 to latest LTS version(2.32.X). can you please guide us through the steps or important prerequites before doing it. and do we need any intermediate version or we can directly go to latest 2.32 version from 1.651 version. As this jenkins we

Re: credential plugin disappears after Jenkins upgrade to 1.658

Jenkins restarts. From: on behalf of Prasu S Reply-To: "jenkinsci-users@googlegroups.com" Date: Tuesday, February 21, 2017 at 11:24 AM To: Jenkins Users Subject: Re: credential plugin disappears after Jenkins upgrade to 1.658 I have plugins directory back up , Can I copy the plugin from

Re: credential plugin disappears after Jenkins upgrade to 1.658

I have plugins directory back up , Can I copy the plugin from the backup or do I have to install different plugin version like 1.22. Please help. Appreciate any help. I see these errors in the log: *** SEVERE: Failed Inspecting plugin D:\Build\Jenkins\apps\jenki

Re: credential plugin disappears after Jenkins upgrade to 1.658

> On 21.02.2017, at 18:13, Prasu S wrote: > > java.io.IOException: Failed to expand > D:\Build\Jenkins\apps\jenkins\jenkins_home\plugins\credentials.jpi > My guess is that the plugin zip file is corrupt. Redownload and replace. -- You received this message because you are subscribed to the

Re: credential plugin disappears after Jenkins upgrade to 1.658

Daniel Thanks for the quick response. I have plugins directory back up , Can I copy the plugin from the backup or do I have to install different plugin version like 1.22. Please help. Appreciate your response. I see these errors in the log: *** SEVERE: Failed Insp

Re: credential plugin disappears after Jenkins upgrade to 1.658

> On 21.02.2017, at 15:22, Prasu S wrote: > > I upgraded Jenkins from 1.607 to 1.658 , after the upgrade credentials plugin > 1.18 is missing. Due to this, we are not able to get code from Github. When > I tried to re-install the same version(1.18) , it is still not showing under > installed

credential plugin disappears after Jenkins upgrade to 1.658

I upgraded Jenkins from 1.607 to 1.658 , after the upgrade credentials plugin 1.18 is missing. Due to this, we are not able to get code from Github. When I tried to re-install the same version(1.18) , it is still not showing under installed plugin list. How can I recover credential plugin. An

Re: Jenkins Upgrade | Migration path is 1.585 -> LTS 2.32.1

Thank you both, yes, I'm seeing some problem with plugins in this case. Regards Vikrant On Monday, 6 February 2017 06:07:16 UTC, Vikrant Kaushik wrote: > > Dear All, > > This weekend I'm planning to upgrade my Jenkins as per below Migration > plan: > > 1.585 -> LTS 2.32.1 > > Request all of you

Re: Jenkins Upgrade | Migration path is 1.585 -> LTS 2.32.1

Also see upgrade guides being posted on the jenkins.io side. There should not be serious update blockers, but backup and testing are always recommended. Likely you will be afftected by some security fixes, which change the default behavior n some cases. понедельник, 6 февраля 2017 г., 7:49:10 UT

Jenkins Upgrade | Migration path is 1.585 -> LTS 2.32.1

You will have to confirm that the plugins you use are compatible with the newer version of Jenkins. I would recommend backing up, creating a test server from the. backup then upgrading all the plugins on the backup Jenkins to see what breaks. -- You received this message because you are subscr

Jenkins Upgrade | Migration path is 1.585 -> LTS 2.32.1

Dear All, This weekend I'm planning to upgrade my Jenkins as per below Migration plan: 1.585 -> LTS 2.32.1 Request all of you to please advise if I'm able to directly upgrade 1.585 to LTS 2.32.1 Regards Vikrant -- You received this message because you are subscribed to the Google Groups "J

Re: Jenkins Upgrade from 1.651.3 to 2.7.4

> On 20.11.2016, at 11:39, zevik wrote: > > having hard times to find a detailed upgrade guide So what you're saying is that you looked neither on http://jenkins-ci.org/changelog-stable nor on https://jenkins.io/doc/ ? -- You received this message because you are subscribed to the Google Gro

Jenkins Upgrade from 1.651.3 to 2.7.4

Hi all, I'm going to upgrade my Jenkins server and having hard times to find a detailed upgrade guide. Especially I wonder when moving to Jenkins 2.x *how to make sure the jobs will remain intact, we have many complex jobs.* Any resource will be helpful. Thanks! -- You received this message bec

Re: Jenkins upgrade from 1.608 to 2.9-1.1 version on CentOS release 6.8 (Final).

> > > > > > > > *From:* jenkins...@googlegroups.com [mailto: > jenkins...@googlegroups.com ] *On Behalf Of *Eric Pyle > *Sent:* October-26-16 12:36 > *To:* jenkins...@googlegroups.com > *Subject:* Re: Jenkins upgrade from 1.608 to 2.9-1.1 version on

RE: Jenkins upgrade from 1.608 to 2.9-1.1 version on CentOS release 6.8 (Final).

: October-26-16 12:36 To: jenkinsci-users@googlegroups.com Subject: Re: Jenkins upgrade from 1.608 to 2.9-1.1 version on CentOS release 6.8 (Final). I'm assuming your new Jenkins version is installed in the same location as the old one. Have you looked at the Jenkins logs to see if there are

Re: Jenkins upgrade from 1.608 to 2.9-1.1 version on CentOS release 6.8 (Final).

I'm assuming your new Jenkins version is installed in the same location as the old one. Have you looked at the Jenkins logs to see if there are some errors reported which may be preventing your jobs from loading? Eric On 10/26/2016 12:11 PM, Kaushal Shriyan wrote: Hi, I have installed jenki

Jenkins upgrade from 1.608 to 2.9-1.1 version on CentOS release 6.8 (Final).

Hi, I have installed jenkins-2.9-1.1.noarch on CentOS release 6.8 (Final). I have imported the jenkins folder from the old server which is running jenkins-1.608-1.1.noarch. I have restarted the jenkins 2.9-1.1 version, But i do not see the workspace,jobs,users and nodes which i populated it fr

Re: Jenkins upgrade

Appreciate your response Raju.I tried to stop the tomcat server and restart it . Did not work. On Tuesday, July 19, 2016 at 3:19:37 AM UTC-4, Saggam Raju wrote: > Hi, > > 1. Could you please stop tomcat server(catalina.sh stop/service tomcat > stop). > 2. Take backup of old jenkins war file fr

Re: Jenkins upgrade

Hi, 1. Could you please stop tomcat server(catalina.sh stop/service tomcat stop). 2. Take backup of old jenkins war file from tomcat/webaspps(tar czf jenkins.backup jenkins.war) and also take backup of jenkins home directory. 3. Now copy your latest jenkins version to tomcat/webapps directory a

Jenkins upgrade

I'm upgrading Jenkins from 1.607 version to 1.645 . I replaced the old war file with 1.645 war file and restarted Jenkins Tomcat and also rebooted the server but I still see old version. I tried the same steps on our test instance back in April it worked fine . Why the new version is not getting

Jenkins upgrade

I'm upgrading Jenkins from 1.607 version to 1.645 . I replaced the old war file with 1.645 war file and restarted Jenkins Tomcat and also rebooted the server but I still see old version. I tried the same steps on our test instance back in April it worked fine . Why the new version is not getting

Re: Jenkins Upgrade: hudson.tasks.junit.JUnitParser not found in latest Jenkins 2.5 (ref by labeled-test-groups-publisher-plugin)

On Fri, May 20, 2016 at 4:12 PM, Daniel Beck wrote: > > > On 20.05.2016, at 03:35, Roshan Dawrani wrote: > > > > I couldn't update to v2.5 though, due to > https://issues.jenkins-ci.org/browse/JENKINS-34013, which is still open > > > > java.lang.NoSuchMethodError: > hudson.model.Messages.Externa

Re: Jenkins Upgrade: hudson.tasks.junit.JUnitParser not found in latest Jenkins 2.5 (ref by labeled-test-groups-publisher-plugin)

> On 20.05.2016, at 03:35, Roshan Dawrani wrote: > > I couldn't update to v2.5 though, due to > https://issues.jenkins-ci.org/browse/JENKINS-34013, which is still open > > java.lang.NoSuchMethodError: > hudson.model.Messages.ExternalJob_DisplayName()Ljava/lang/String; > at > hudson.mod

Re: Jenkins Upgrade: hudson.tasks.junit.JUnitParser not found in latest Jenkins 2.5 (ref by labeled-test-groups-publisher-plugin)

Thank you for replying, Daniel. This is how I finally did it y'day - downloaded the HPI files of the plugins that were not being shown due to their dependency on a minimum version of Jenkins and uploaded them to Jenkins /plugins directory using the "Advanced" UI of the plugin manager. After manuall

Re: Jenkins Upgrade: hudson.tasks.junit.JUnitParser not found in latest Jenkins 2.5 (ref by labeled-test-groups-publisher-plugin)

> On 19.05.2016, at 14:33, roshan wrote: > > However, as noted here in > https://issues.jenkins-ci.org/browse/JENKINS-23263?focusedCommentId=209734&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-209734, > I can't see the "JUnit Plugin" if I go to "Manage Plugins"

Re: Jenkins Upgrade: hudson.tasks.junit.JUnitParser not found in latest Jenkins 2.5 (ref by labeled-test-groups-publisher-plugin)

The Jenkins release change log (v1.577) seems to say that junit stuff was taken out from the core into a separate plugin. However, as noted here in https://issues.jenkins-ci.org/browse/JENKINS-23263?focusedCommentId=209734&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#com

Jenkins Upgrade: hudson.tasks.junit.JUnitParser not found in latest Jenkins 2.5 (ref by labeled-test-groups-publisher-plugin)

Hi, I am trying to upgrade my Jenkins setup (from v1.4.x to v2.5) and running into this error "java.lang.ClassNotFoundException: hudson.tasks.junit.JUnitParser" among others. I checked and found that this class used to be in jenkins-core-1.471.jar However, I don't find it now in jenkins-core-2

Re: Bitbucket plugin bug after Jenkins upgrade to 2.3

I had a similar issue at the end of the jobs: FATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to org.jenkinsci.plugins.BitbucketAuthenticationTokenjava.lang.ClassCastException : or

Re: Bitbucket plugin bug after Jenkins upgrade to 2.3

Done. https://issues.jenkins-ci.org/browse/JENKINS-34792 thanks On 13 May 2016 at 11:30, Daniel Beck wrote: > > > On 13.05.2016, at 11:15, herbert.fisc...@crossengage.io wrote: > > > > Any idea what it is? > > Please file a bug so this can get looked at. > > In the meantime, set the system prop

Re: Bitbucket plugin bug after Jenkins upgrade to 2.3

> On 13.05.2016, at 11:15, herbert.fisc...@crossengage.io wrote: > > Any idea what it is? Please file a bug so this can get looked at. In the meantime, set the system property hudson.model.User.SECURITY_243_FULL_DEFENSE to false, that should work around it. -- You received this message beca

Bitbucket plugin bug after Jenkins upgrade to 2.3

Hi, I started getting these errors inside a Maven build, after the upgrade to 2.3: ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.comjava.lang.ClassCastException :

Tag this build unusable as credentials menu is empty after Jenkins upgrade

Has anyone else seen this problem? I've just upgraded my Jenkins installation from 1.625.3 to 1.642.3, and upgraded all my installed plugins to match. Everything seems fine except that I can no longer use "Tag this build" in jobs that checked out their sources from svn. The "Credentials for ta

On Windows Jenkins upgrade takes VERY long time.

It has been upgrading itself for 4-5 hours already. Is this normal behaviour? The progress bar seems to move from time to time. -- 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,

Re: Jenkins Upgrade Installation Constraints and Risks

Noted! Thanks!!! Sent from my iPhone > On Jan 23, 2016, at 12:37 PM, Mark Waite wrote: > > Since you spent a long time on a single version, you should probably upgrade > to a long term support version (currently 1.642.1) rather than to a weekly > version. LTS versions have additional testin

Re: Jenkins Upgrade Installation Constraints and Risks

Since you spent a long time on a single version, you should probably upgrade to a long term support version (currently 1.642.1) rather than to a weekly version. LTS versions have additional testing and tend to be supported longer (though none of them are supported for 5 years). Mark Waite On Sat

Re: Jenkins Upgrade Installation Constraints and Risks

Thank you this has been most helpful and I will be sure to come back with any questions if I encounter any issues! Sent from my iPhone > On Jan 23, 2016, at 8:35 AM, Baptiste Mathus wrote: > > Hi, > > Basically, yes, there are obviously many risks doing a fast-forward of almost > 5 years, m

Re: Jenkins Upgrade Installation Constraints and Risks

Hi, Basically, yes, there are obviously many risks doing a fast-forward of almost 5 years, maybe even more with a project as active as Jenkins :). BUT, depending on your environment (how many jobs, nodes, exotic configs, unmaintained/custom plugins...), this may not be a so big issue in the end.

Jenkins Upgrade Installation Constraints and Risks

Good morning, I have two basic questions. I am not sure if this is the correct group for these questions, if not please let me know where to pose these questions. We are using Jenkins as a stand-alone application on our UNIX server. 1. Other than Java 7 and above, are there any System Requireme

Re: LDAP plugin, warning after Jenkins upgrade v1.638

In case you are having difficulty the change in question was: Turned the group membership lookup into a strategy. That changed the configuration format of the LDAP security realm. This is normally not a big deal... as long as you do not roll back the plugin... if you roll the plugin back to versi

Re: LDAP plugin, warning after Jenkins upgrade v1.638

Click the plugin name and then scroll down. On 26.11.2015, at 08:57, Lavr L wrote: > Hi > > I upgraded Jenkins to last release 1.638 and now I have the following warning > for LDAP plugin: > Warning: the new version of this plugin claims to use a different settings > format than the installed

LDAP plugin, warning after Jenkins upgrade v1.638

Hi I upgraded Jenkins to last release 1.638 and now I have the following warning for LDAP plugin: *Warning: the new version of this plugin claims to use a different settings format than the installed version. Jobs using this plugin may need to be reconfigured, and/or you may not be able to clea

After Jenkins upgrade to latest 1.6 version Jenkin url sometimes becomes inaccessible

Hi All, We recently followed below steps during this Jenkins upgrade from version 1.56 to latest 1.6 1. Browsed to "Manage Jenkins" link and clicked "download/upgrade" 2. The latest .war file was downloaded but was not able to copy itslef or overwrite in to the final de

Re: Jenkins Upgrade/Install in OSx/Mac Yoshomite

Not sure where you've seen 2.2.0 as that isn't a Jenkins version number. IMHO easiest way to manage Jenkins on MacOS is to install via homebrew but others might have other better ways. Richard. On Wed, 8 Jul 2015 at 11:31 jairaj kamal wrote: > Hi, > > I have current Jenkins in my Mac running o

Jenkins Upgrade/Install in OSx/Mac Yoshomite

Hi, I have current Jenkins in my Mac running on Yosemite with version 1.569 and now see the latest version in market as 2.2.0, what is the way to upgrade Jenkins and move jobs from one to another ? I come to know that in some version there is automatic update (via "Manage Jenkins" link) but in

  1   2   >