LTS 1.466.1 RC1 testing
Locked
LTS 1.466.1 RC1 testing
 
|
Hi,
LTS 1.466.1 RC1 is now available for download [1], thus we can start testing. As usual, I would like to ask for your help. If you stage RC in you stage environment or just download RC and try to run it, please drop a note on wiki page [2], shortly describe what you tested, where it was done (OS, JDK version) and the result. Feel free to add new tests or repeating test which was already done by someone else in different env. - it is also very useful as some bug can appear only on e.g. one OS but not on other etc. Any test is very helpful, especially in case of new major LTS RC. Thanks in advance Vojta [1] http://mirrors.jenkins-ci.org/ [2] https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.466.x+RC+Testing |
Re: LTS 1.466.1 RC1 testing
|
I installed the release candidate and cannot seem to checkout with the latest release of the Git plugin. Has anyone else successfully used Git plugin 1.1.21 with a new installation of Jenkins 1.466.1 RC1? I had seen the same problem with an existing installation and rolled back to 1.1.20 on that existing installation. Unfortunately, it is not that simple with a new installation. Mark Waite
|
Re: LTS 1.466.1 RC1 testing
|
|
More details in case it helps. If I install Jenkins 1.466.1 and the latest Git plugin, 1.1.21, and define a job using the command line interface create-job command and a config.xml, it fails to clone with messages: Fetching upstream changes from git://markwaite2.markwaite.net/git/WorkManager.git ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. If I install Jenkins 1.466.1 and If I copy the git.hpi file for Git plugin version 1.1.20 into the plugins directory as git.bak, restart Jenkins, and downgrade the plugin to 1.1.20, then the same jobs that were failing to find a revision are now able to find that revision and run the job to completion. The only change I recognize between the failure case and the success case is the version of the Git plugin. Any suggestions of other steps I should take to further isolate the problem? Mark Waite
|
Re: Re: LTS 1.466.1 RC1 testing
|
|
In reply to this post by Mark Waite
Hi Mark,
thanks for spotting it! I tested 1.466.1 RC1 with git plugin 1.1.21 and everything works fine for me. You probably suffer from JENKINS-13007 [1], the last comment under this issue also states that this issue start to appear on linux since 1.1.21. It obviously appear only on some machines, but I have currently no idea what triggers this problem. In 1.1.21 was one commit related to this issue [2], but it should affect only windows machines... Just for sure, could you please go to $JENKINS_HOME/script and run following command: Functions.isWindows() if Jenkins for some strange reason thinks that it runs on windows? Thanks Vojta [1] https://issues.jenkins-ci.org/browse/JENKINS-13007 [2] https://github.com/jenkinsci/git- plugin/commit/85afc7b0e64dd18c2807373880d1a8e2824fffbc On Friday 20 July 2012 20:21:58 Mark Waite wrote: > I installed the release candidate and cannot seem to checkout with the > latest release of the Git plugin. Has anyone else successfully used Git > plugin 1.1.21 with a new installation of Jenkins 1.466.1 RC1? > > I had seen the same problem with an existing installation and rolled back to > 1.1.20 on that existing installation. Unfortunately, it is not that > simple with a new installation. > > Mark Waite > > >________________________________ > > > > From: Vojtech Juranek <[hidden email]> > > > >To: [hidden email]; [hidden email] > >Sent: Friday, July 20, 2012 5:04 PM > >Subject: LTS 1.466.1 RC1 testing > > > >Hi, > >LTS 1.466.1 RC1 is now available for download [1], thus we can start > >testing. As usual, I would like to ask for your help. If you stage RC in > >you stage environment or just download RC and try to run it, please drop a > >note on wiki page [2], shortly describe what you tested, where it was done > >(OS, JDK version) and the result. > > > >Feel free to add new tests or repeating test which was already done by > >someone else in different env. - it is also very useful as some bug can > >appear only on e.g. one OS but not on other etc. > > > >Any test is very helpful, especially in case of new major LTS RC. > > > >Thanks in advance > >Vojta > > > >[1] http://mirrors.jenkins-ci.org/ > >[2] https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.466.x+RC+Testing |
Re: Re: LTS 1.466.1 RC1 testing
|
|
I don't have a $JENKINS_HOME/script directory accessible from the login user (jenkins) which runs the Jenkins process on Debian or on Oracle Linux. I'm also not sure how to execute Functions.IsWindows(). Is that invoking a groovy script from the web browser rather than from an operating system shell outside Jenkins ? If so, do I need to install a groovy plugin, or is there a tutorial which could suggest how to invoke that script? The VNC plugin is checked to not run VNC on Windows, and VNC definitely runs on the master node, so I'm reasonably confident that some part of the Jenkins infrastructure knows that the machine is not Windows. The "system information" screen (http://localhost:8080/systemInfo) shows os.name as "Linux" and os.arch as "amd64", so I think the Java runtime knows it is on Linux. Mark Waite
|
Re: Re: LTS 1.466.1 RC1 testing
|
|
In reply to this post by Vojtech Juranek
You mentioned that you tested 1.466.1 RC1. I'm using the operating system package manager to install those builds. On Debian, I installed following the instructions at http://pkg.jenkins-ci.org/debian-stable-rc/ On Oracle Linux, I installed following the instructions at http://pkg.jenkins-ci.org/redhat-stable-rc/ Both of them installed a Jenkins version Jenkins ver. 1.466.1-SNAPSHOT
(rc-07/12/2012 03:57 GMT-kohsuke). Is that the same version you're testing as 1.466.1 RC1? Mark Waite
|
Re: Re: LTS 1.466.1 RC1 testing
|
|
In reply to this post by Vojtech Juranek
I used the script console at http://localhost:8080/script to run the command Functions.isWindows() and it reports Result: false
|
Re: Re: Re: LTS 1.466.1 RC1 testing
|
|
Thanks for verifying. So now I really have no idea where the problem could
be:-( And yes, I also tested with 1.466.1-SNAPSHOT (rc-07/12/2012 03:57 GMT- kohsuke), namely rpm package downloaded from http://pkg.jenkins-ci.org/redhat- stable-rc/ On Saturday 21 July 2012 15:04:17 Mark Waite wrote: > I used the script console at http://localhost:8080/script to run the > command Functions.isWindows() and it reports Result: false > >________________________________ > > > > From: Vojtech Juranek <[hidden email]> > > > >To: [hidden email] > >Sent: Saturday, July 21, 2012 3:00 PM > >Subject: Re: Re: LTS 1.466.1 RC1 testing > > > >Hi Mark, > >thanks for spotting it! > > > >I tested 1.466.1 RC1 with git plugin 1.1.21 and everything works fine for > >me. You probably suffer from JENKINS-13007 [1], the last comment under > >this issue also states that this issue start to appear on linux since > >1.1.21. It obviously appear only on some machines, but I have currently no > >idea what triggers this problem. > > > >In 1.1.21 was one commit related to this issue [2], but it should affect > >only windows machines... Just for sure, could you please go to > >$JENKINS_HOME/script and run following command: > >Functions.isWindows() > >if Jenkins for some strange reason thinks that it runs on windows? > > > >Thanks > >Vojta > > > >[1] https://issues.jenkins-ci.org/browse/JENKINS-13007 > >[2] https://github.com/jenkinsci/git- > >plugin/commit/85afc7b0e64dd18c2807373880d1a8e2824fffbc > > > >On Friday 20 July 2012 20:21:58 Mark Waite wrote: > >> I installed the release candidate and cannot seem to checkout with the > >> latest release of the Git plugin. Has anyone else successfully used Git > >> plugin 1.1.21 with a new installation of Jenkins 1.466.1 RC1? > >> > >> I had seen the same problem with an existing installation and rolled back > >> to 1.1.20 on that existing installation. Unfortunately, it is not that > >> simple with a new installation. > >> > >> Mark Waite > >> > >> >________________________________ > >> > > >> > From: Vojtech Juranek <[hidden email]> > >> > > >> >To: [hidden email]; [hidden email] > >> >Sent: Friday, July 20, 2012 5:04 PM > >> >Subject: LTS 1.466.1 RC1 testing > >> > > >> >Hi, > >> >LTS 1.466.1 RC1 is now available for download [1], thus we can start > >> >testing. As usual, I would like to ask for your help. If you stage RC in > >> >you stage environment or just download RC and try to run it, please drop > >> >a > >> >note on wiki page [2], shortly describe what you tested, where it was > >> >done > >> >(OS, JDK version) and the result. > >> > > >> >Feel free to add new tests or repeating test which was already done by > >> >someone else in different env. - it is also very useful as some bug can > >> >appear only on e.g. one OS but not on other etc. > >> > > >> >Any test is very helpful, especially in case of new major LTS RC. > >> > > >> >Thanks in advance > >> >Vojta > >> > > >> >[1] http://mirrors.jenkins-ci.org/ > >> >[2] https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.466.x+RC+Testing |
sonar error: Cannot execute mojo: sonar
|
In reply to this post by Mark Waite
Hi,
I am trying to run sonar for a test build, but getting the following error. Any suggestions on how to resolve this ? This project has a build.xml (ant driven) but NO pom.xml, and i think sonar supports ant. [INFO] Cannot execute mojo: sonar. It requires a project with an existing pom.xml, but the build is not using one. [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot execute mojo: sonar. It requires a project with an existing pom.xml, but the build is not using one. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot execute mojo: sonar. It requires a project with an existing pom.xml, but the build is not using one. at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:414) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1 second [INFO] Finished at: Sun Jul 22 00:17:30 EDT 2012 [INFO] Final Memory: 4M/238M [INFO] ------------------------------------------------------------------------ Sonar analysis completed: FAILURE Build step 'Sonar' changed build result to FAILURE Build step 'Sonar' marked build as failure Notifying upstream projects of job completion Finished: FAILURE |
Re: LTS 1.466.1 RC1 testing
|
In reply to this post by Vojtech Juranek
It could be https://issues.jenkins-ci.org/browse/JENKINS-14480, probably nothing wrong with Jenkins. Mark, could you check if you have repository/branchname in the "Branch to build" setting?
-- Sami Vojtech Juranek <[hidden email]> kirjoitti 22.7.2012 kello 3.37: > Thanks for verifying. So now I really have no idea where the problem could > be:-( > And yes, I also tested with 1.466.1-SNAPSHOT (rc-07/12/2012 03:57 GMT- > kohsuke), namely rpm package downloaded from http://pkg.jenkins-ci.org/redhat- > stable-rc/ > > > On Saturday 21 July 2012 15:04:17 Mark Waite wrote: >> I used the script console at http://localhost:8080/script to run the >> command Functions.isWindows() and it reports Result: false >>> ________________________________ >>> >>> From: Vojtech Juranek <[hidden email]> >>> >>> To: [hidden email] >>> Sent: Saturday, July 21, 2012 3:00 PM >>> Subject: Re: Re: LTS 1.466.1 RC1 testing >>> >>> Hi Mark, >>> thanks for spotting it! >>> >>> I tested 1.466.1 RC1 with git plugin 1.1.21 and everything works fine for >>> me. You probably suffer from JENKINS-13007 [1], the last comment under >>> this issue also states that this issue start to appear on linux since >>> 1.1.21. It obviously appear only on some machines, but I have currently no >>> idea what triggers this problem. >>> >>> In 1.1.21 was one commit related to this issue [2], but it should affect >>> only windows machines... Just for sure, could you please go to >>> $JENKINS_HOME/script and run following command: >>> Functions.isWindows() >>> if Jenkins for some strange reason thinks that it runs on windows? >>> >>> Thanks >>> Vojta >>> >>> [1] https://issues.jenkins-ci.org/browse/JENKINS-13007 >>> [2] https://github.com/jenkinsci/git- >>> plugin/commit/85afc7b0e64dd18c2807373880d1a8e2824fffbc >>> >>> On Friday 20 July 2012 20:21:58 Mark Waite wrote: >>>> I installed the release candidate and cannot seem to checkout with the >>>> latest release of the Git plugin. Has anyone else successfully used Git >>>> plugin 1.1.21 with a new installation of Jenkins 1.466.1 RC1? >>>> >>>> I had seen the same problem with an existing installation and rolled back >>>> to 1.1.20 on that existing installation. Unfortunately, it is not that >>>> simple with a new installation. >>>> >>>> Mark Waite >>>> >>>>> ________________________________ >>>>> >>>>> From: Vojtech Juranek <[hidden email]> >>>>> >>>>> To: [hidden email]; [hidden email] >>>>> Sent: Friday, July 20, 2012 5:04 PM >>>>> Subject: LTS 1.466.1 RC1 testing >>>>> >>>>> Hi, >>>>> LTS 1.466.1 RC1 is now available for download [1], thus we can start >>>>> testing. As usual, I would like to ask for your help. If you stage RC in >>>>> you stage environment or just download RC and try to run it, please drop >>>>> a >>>>> note on wiki page [2], shortly describe what you tested, where it was >>>>> done >>>>> (OS, JDK version) and the result. >>>>> >>>>> Feel free to add new tests or repeating test which was already done by >>>>> someone else in different env. - it is also very useful as some bug can >>>>> appear only on e.g. one OS but not on other etc. >>>>> >>>>> Any test is very helpful, especially in case of new major LTS RC. >>>>> >>>>> Thanks in advance >>>>> Vojta >>>>> >>>>> [1] http://mirrors.jenkins-ci.org/ >>>>> [2] https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.466.x+RC+Testing |
Re: sonar error: Cannot execute mojo: sonar
|
In reply to this post by Kamal Ahmed
Hi Kamal,
The configuration for Sonar plugin is explained here: http://docs.codehaus.org/display/SONAR/Activate+Sonar+on+Jenkins+job Check topics "Activate Sonar analysis on non-Maven jobs" and "Activate Sonar analysis by Ant task" It should help. Andrey On Sat, Jul 21, 2012 at 10:30 PM, Kamal Ahmed <[hidden email]> wrote:
|
Re: LTS 1.466.1 RC1 testing
|
|
In reply to this post by Sami Tikka
That is the issue. Thanks for the suggestion! I was confident the problem was in the plugin, not in jenkins core, since switching back to the old plugin was able to make it work again. I assume this is still a "showstopper" for the release of the 1.466.1 long term support version, since many, many Jenkins users depend on the Git plugin and this bug makes Git plugin 1.1.21 incompatible with previous versions and incompatible with the help which is included with the plugin. Mark Waite
|
Re: Re: LTS 1.466.1 RC1 testing
|
|
Sami, thanks for clarifying what is the root cause of this issue, it's caused
by 3b1ad20200 [1], which should fixed checking out branches containing "/" in the branch name [2]. Mark, this is not a show stopper for LTS release. Git plugin is not bundled with the Jenkins core and you can do the upgrade to 1.466.1 without upgrading Git plugin to 1.1.21. The idea behind LTS is to provide some stable release which includes also some basics testing of most popular plugin against this release. I try to test with the most up-to-date plugin release, but it's not mandatory to use the latest version. I.e. the output of the testing will be something like the report "upgrade to 1.466.1 is fine, all latest plugin as well except git plug. In git 1.1.21 is a regression and you should update to 1.1.20" In fact IIRC we never experienced such situation, that a serious regression was find in a plugin during LTS testing. Maybe I should create separate topics how to present this results to the community in some well-arranged way [1] https://github.com/jenkinsci/git- plugin/commit/3b1ad202004ec3617f2023e147868876bea2e305 [2] https://issues.jenkins-ci.org/browse/JENKINS-14026 On Sunday 22 July 2012 07:31:38 Mark Waite wrote: > That is the issue. Thanks for the suggestion! I was confident the problem > was in the plugin, not in jenkins core, since switching back to the old > plugin was able to make it work again. > > I assume this is still a "showstopper" for the release of the 1.466.1 long > term support version, since many, many Jenkins users depend on the Git > plugin and this bug makes Git plugin 1.1.21 incompatible with previous > versions and incompatible with the help which is included with the plugin. > > Mark Waite > > >________________________________ > > > > From: Sami Tikka <[hidden email]> > > > >To: "[hidden email]" <[hidden email]> > >Cc: "[hidden email]" <[hidden email]> > >Sent: Saturday, July 21, 2012 11:50 PM > >Subject: Re: LTS 1.466.1 RC1 testing > > > >It could be https://issues.jenkins-ci.org/browse/JENKINS-14480, probably > >nothing wrong with Jenkins. Mark, could you check if you have > >repository/branchname in the "Branch to build" setting? > > > >-- Sami > > > >Vojtech Juranek <[hidden email]> kirjoitti 22.7.2012 kello 3.37: > >> Thanks for verifying. So now I really have no idea where the problem > >> could > >> be:-( > >> And yes, I also tested with 1.466.1-SNAPSHOT (rc-07/12/2012 03:57 GMT- > >> kohsuke), namely rpm package downloaded from > >> http://pkg.jenkins-ci.org/redhat- stable-rc/ > >> > >> On Saturday 21 July 2012 15:04:17 Mark Waite wrote: > >>> I used the script console at http://localhost:8080/script to run the > >>> command Functions.isWindows() and it reports Result: false > >>> > >>>> ________________________________ > >>>> > >>>> From: Vojtech Juranek <[hidden email]> > >>>> > >>>> To: [hidden email] > >>>> Sent: Saturday, July 21, 2012 3:00 PM > >>>> Subject: Re: Re: LTS 1.466.1 RC1 testing > >>>> > >>>> Hi Mark, > >>>> thanks for spotting it! > >>>> > >>>> I tested 1.466.1 RC1 with git plugin 1.1.21 and everything works fine > >>>> for > >>>> me. You probably suffer from JENKINS-13007 [1], the last comment under > >>>> this issue also states that this issue start to appear on linux since > >>>> 1.1.21. It obviously appear only on some machines, but I have currently > >>>> no > >>>> idea what triggers this problem. > >>>> > >>>> In 1.1.21 was one commit related to this issue [2], but it should > >>>> affect > >>>> only windows machines... Just for sure, could you please go to > >>>> $JENKINS_HOME/script and run following command: > >>>> Functions.isWindows() > >>>> if Jenkins for some strange reason thinks that it runs on windows? > >>>> > >>>> Thanks > >>>> Vojta > >>>> > >>>> [1] https://issues.jenkins-ci.org/browse/JENKINS-13007 > >>>> [2] https://github.com/jenkinsci/git- > >>>> plugin/commit/85afc7b0e64dd18c2807373880d1a8e2824fffbc > >>>> > >>>> On Friday 20 July 2012 20:21:58 Mark Waite wrote: > >>>>> I installed the release candidate and cannot seem to checkout with the > >>>>> latest release of the Git plugin. Has anyone else successfully used > >>>>> Git > >>>>> plugin 1.1.21 with a new installation of Jenkins 1.466.1 RC1? > >>>>> > >>>>> I had seen the same problem with an existing installation and rolled > >>>>> back > >>>>> to 1.1.20 on that existing installation. Unfortunately, it is not > >>>>> that > >>>>> simple with a new installation. > >>>>> > >>>>> Mark Waite > >>>>> > >>>>>> ________________________________ > >>>>>> > >>>>>> From: Vojtech Juranek <[hidden email]> > >>>>>> > >>>>>> To: [hidden email]; [hidden email] > >>>>>> Sent: Friday, July 20, 2012 5:04 PM > >>>>>> Subject: LTS 1.466.1 RC1 testing > >>>>>> > >>>>>> Hi, > >>>>>> LTS 1.466.1 RC1 is now available for download [1], thus we can start > >>>>>> testing. As usual, I would like to ask for your help. If you stage RC > >>>>>> in > >>>>>> you stage environment or just download RC and try to run it, please > >>>>>> drop > >>>>>> a > >>>>>> note on wiki page [2], shortly describe what you tested, where it was > >>>>>> done > >>>>>> (OS, JDK version) and the result. > >>>>>> > >>>>>> Feel free to add new tests or repeating test which was already done > >>>>>> by > >>>>>> someone else in different env. - it is also very useful as some bug > >>>>>> can > >>>>>> appear only on e.g. one OS but not on other etc. > >>>>>> > >>>>>> Any test is very helpful, especially in case of new major LTS RC. > >>>>>> > >>>>>> Thanks in advance > >>>>>> Vojta > >>>>>> > >>>>>> [1] http://mirrors.jenkins-ci.org/ > >>>>>> [2] > >>>>>> https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.466.x+RC+Testing |
Re: Re: LTS 1.466.1 RC1 testing
|
|
That seems sensible to me. The issue is in the plugin, not the core. Delaying the release of the core will not help fix the plugin. I'm not clear how a new user installing Jenkins LTS will be able to choose the 1.1.20 release of the git plugin. I had to download it separately, name it appropriately (replace .hpi with .bak), copy it into the plugins directory, then restart Jenkins. Once that was done, Jenkins core recognized there was a 1.1.20 available for downgrade. Those steps seem too complicated for the otherwise elegant and easy to administer Jenkins system. I guess the best solution is to have a new version of the Git plugin released to fix the
problem... Mark Waite
|
Re: Re: Re: LTS 1.466.1 RC1 testing
|
|
> I'm not clear how a new user installing Jenkins LTS will be able to choose > the 1.1.20 release of the git plugin. I had to download it separately, > name it appropriately (replace .hpi with .bak), copy it into the plugins > directory, then restart Jenkins. Once that was done, Jenkins core > recognized there was a 1.1.20 available for downgrade. Those steps seem > too complicated for the otherwise elegant and easy to administer Jenkins > system. agree, I filed a jira requets for it [1] > I guess the best solution is to have a new version of the Git plugin > released to fix the problem... yes, this would be of course the best solution [1] https://issues.jenkins-ci.org/browse/JENKINS-14530 |
«
Return to Jenkins users
|
1 view|%1 views
Loading...
| Powered by Nabble | Edit this page |