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.ExternalJob_DisplayName()Ljava/lang/String; > > at > hudson.model.ExternalJob$DescriptorImpl.getDisplayName(ExternalJob.java:120) > > > > > > I could update to v1650, which doesn't have the above bug and is fairly > recent. > > > > You just need to update the External Monitor Job plugin to a more recent > version, or delete it from the plugins/ directory just before upgrading. > I am already on v1.4 of this plugin, which seems the latest as per https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs I stil got the errors I mentioned when I tried upgrading to v2.5 of Jenkins. > > That issue you linked to is about something slightly different and only > affects instances that never had their global configuration saved by a user. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/qMFN2ZP6i68/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/E3A90711-6DE9-459B-9D7C-D550B89E7AE6%40beckweb.net > . > For more options, visit https://groups.google.com/d/optout. > -- 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 web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMXPLPjdUcqBEESKAHx6uHN1LG5WntLL5VU6Va-8ZbxWZ5n9Ug%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 manually installing such plugins, which were factored out of the core like "JUnit" and "Matrix project", the other plugins started to load correctly. 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.model.ExternalJob$DescriptorImpl.getDisplayName(ExternalJob.java:120) I could update to v1650, which doesn't have the above bug and is fairly recent. I'll test my upgrade to v1650 today. Thanks again for taking time to share your inputs. On Fri, May 20, 2016 at 12:27 AM, Daniel Beck wrote: > > > 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" page. Why is > that? > > It's not installed, or failed to load. Check the jenkins.log for failures > to load plugins during startup. > > > Very puzzling that "hudson.tasks.junit.JUnitParser" stuff was taken out > of Jenkins core but there doesn't seem a good way to make it re-available > for other plugins like LabeledTestGroupsPublisher that depend on it. > > Plugins can depend on other plugins. Plugins that depend on older cores > automatically get implied dependencies added to plugins that were detached > from core since then. > > If you manage your plugins manually by placing them in the plugins/ > directory, instead of having Jenkins install them using the plugin > manager/update center, this is something you just need to be aware of. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/qMFN2ZP6i68/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/E526B418-4894-4F9E-8563-5E8C5E4BA46F%40beckweb.net > . > For more options, visit https://groups.google.com/d/optout. > -- 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 web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMXPLPgXOmeWzE3mMudOMQ1P%3DZDs100C0CfmMALiOswmwwWXTg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Unable to see Jenkins' verbose mode output
On Tue, Jun 5, 2012 at 9:42 AM, Roshan Dawrani wrote: > > I am using Jenkins 1.461 with "git" plugin 1.1.18 (confirmed using > /pluginManager). > > I have run Tomcat with "-Dhudson.plugins.git.GitSCM.verbose=true", but > nowhere in the Jenkins job specific logs I am seeing the verbose output > coming from the "git" plugin classes. > Hi. Anyone please? Why such a seemingly simple thing as enabling the verbose mode for the "git" plugin does not seem to be working? Thanks. Roshan
Unable to see Jenkins' verbose mode output
Hi, I am using Jenkins 1.461 with "git" plugin 1.1.18 (confirmed using /pluginManager). I have run Tomcat with "-Dhudson.plugins.git.GitSCM.verbose=true", but nowhere in the Jenkins job specific logs I am seeing the verbose output coming from the "git" plugin classes. Could someone please let me know what I am missing? Cheers. -- Roshan http://roshandawrani.wordpress.com/
Re: Aumatically building from master but having an option to manually build a specific branch?
Hi, Here is what happens when I am launching my builds manually (correctly picks up the git revision to build) vs when it gets triggered automatically (fails to pick up the correct git revision to build): Any hints please on why it must be picking up the wrong revision to build even though it already sees it as the last successful one? === 1) *"Build Now" with specific branch name "master"* * * Last Built Revision: Revision 98561fa57ccc039a00e82503f255f3861d3686a4 (origin/master) ... Commencing build of Revision 145cefab671fb3a792b0e53c69d030bf074929a9 (origin/master) 2) *Automatically triggered, Scans all repository branches to identify the revision to build* * * Last Built Revision: Revision 145cefab671fb3a792b0e53c69d030bf074929a9 (origin/master) ... Commencing build of Revision *145cefab671fb3a792b0e53c69d030bf074929a9 *(origin/master) - picks up the same "Last Built Revision" again 3) *"Build Now" with specific branch name "master"* * * Last Built Revision: Revision 145cefab671fb3a792b0e53c69d030bf074929a9 (origin/master) ... Commencing build of Revision 2a7562a91b2862fbb34c739138fe569b49476d7f (origin/master) === Cheers. On Mon, Jun 4, 2012 at 7:43 PM, Roshan Dawrani wrote: > Hi, > > I am using Jenkins 1.461 and investigating an issue that Jenkins picks up > for us the wrong revision to build, when it scans multiple branches that we > have in our "git" repository. > > The Jenkins job is currently defined as: > == > > > > > $BRANCH > > > > > == > > When the build is manually launched for a branch (by specifying this > BRANCH parameter value), it does the build correctly, but if it is left > empty, or when the build is triggered automatically, i.e., when it scans > multiple branches to decide which revision to pick, then it always picks up > the wrong one. > > My question is: "can I configure branch specs in class="hudson.plugins.git.GitSCM">..." somehow so that it > automatically builds only from master branch, but gives me an option to use > the parameterized branch to build a specific one? > > > Regards, > -- > Roshan > http://roshandawrani.wordpress.com/ > > -- Roshan http://roshandawrani.wordpress.com/
Aumatically building from master but having an option to manually build a specific branch?
Hi, I am using Jenkins 1.461 and investigating an issue that Jenkins picks up for us the wrong revision to build, when it scans multiple branches that we have in our "git" repository. The Jenkins job is currently defined as: == $BRANCH == When the build is manually launched for a branch (by specifying this BRANCH parameter value), it does the build correctly, but if it is left empty, or when the build is triggered automatically, i.e., when it scans multiple branches to decide which revision to pick, then it always picks up the wrong one. My question is: "can I configure branch specs in ..." somehow so that it automatically builds only from master branch, but gives me an option to use the parameterized branch to build a specific one? Regards, -- Roshan http://roshandawrani.wordpress.com/
