[JIRA] [git-client-plugin] (JENKINS-32712) Job with Git polling "succeeds" with "no changes" although the Git polling failed
Title: Message Title Thorsten Kahler commented on JENKINS-32712 Re: Job with Git polling "succeeds" with "no changes" although the Git polling failed Waiting for a code change to reach integration while it's stuck on the Git server ain't nice. So IMO there should at least be the option to mark a build as failed or unstable, if the Git polling failed. Suppressing such failures might be configurable via "Additional Behaviours". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-30243) NoClassDefFoundError during startup (Template Project plugin 1.5)
Title: Message Title Thorsten Kahler updated an issue Jenkins / JENKINS-30243 NoClassDefFoundError during startup (Template Project plugin 1.5) Change By: Thorsten Kahler Environment: Jenkins 1.609.2Java(TM) SE Runtime Environment (build 1.7.0_71-b14)CentOS Template Project plugin 1.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-30243) NoClassDefFoundError during startup (Template Project plugin 1.5)
Title: Message Title Thorsten Kahler commented on JENKINS-30243 Re: NoClassDefFoundError during startup (Template Project plugin 1.5) The Multiple SCMs Plugin is not installed. We don't use SCM configurations from template jobs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-30243) NoClassDefFoundError during startup (Template Project plugin 1.5)
Title: Message Title Thorsten Kahler commented on JENKINS-30243 Re: NoClassDefFoundError during startup (Template Project plugin 1.5) Here's the complete plugin list: All changes plugin 1.3 AnsiColor 0.4.1 Authorize Project 1.1.0 Build Blocker Plugin 1.7.1 Build Pipeline Plugin 1.4.7 build timeout plugin 1.15 Checkstyle Plug-in 3.42 Copy Artifact Plugin 1.35.2 Credentials Plugin 1.22 Dashboard View 2.9.6 disk-usage plugin 0.25 Downstream build view 1.9 Email Extension Plugin 2.40.5 Environment Injector Plugin 1.92.1 Favorite 1.16 GIT client plugin 1.19.0 Git Parameter Plug-In 0.4.0 GIT plugin 2.4.0 Green Balls 1.14 Groovy 1.27 Groovy Postbuild 2.2.1
[JIRA] [template-project-plugin] (JENKINS-30243) NoClassDefFoundError during startup
Title: Message Title Thorsten Kahler created an issue Jenkins / JENKINS-30243 NoClassDefFoundError during startup Issue Type: Bug Assignee: huybrechts Components: template-project-plugin Created: 01/Sep/15 12:08 PM Environment: Jenkins 1.609.2 Java(TM) SE Runtime Environment (build 1.7.0_71-b14) CentOS Labels: plugin startup Priority: Minor Reporter: Thorsten Kahler After upgrading the Template Project Plugin from 1.4.2 to 1.5 following error is thrown during startup of Jenkins: PM WARNING hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error Failed to instantiate Key[type=hudson.plugins.templateproject.ProxySCM$DescriptorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, java.lang.NoClassDefFoundError: org/jenkinsci/plugins/multiplescms/MultiSCMRevisionState at
[JIRA] [template-project-plugin] (JENKINS-30243) NoClassDefFoundError during startup
Title: Message Title Thorsten Kahler commented on JENKINS-30243 Re: NoClassDefFoundError during startup When opening the configuration of a project that uses a template build step the following NPE is thrown: PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: h.getRelativeLinkTo(job) in /view/YaS/job/typo3-yas-checkout/configure. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.Functions.getRelativeLinkTo(Functions.java:1052) at sun.reflect.GeneratedMethodAccessor116.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsString(ExpressionSupport.java:46) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.buildAttributes(ReallyStaticTagLibrary.java:111) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:95) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:81) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:124) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at
[JIRA] [template-project-plugin] (JENKINS-30243) NoClassDefFoundError during startup (Template Project plugin 1.5)
Title: Message Title Thorsten Kahler updated an issue Jenkins / JENKINS-30243 NoClassDefFoundError during startup (Template Project plugin 1.5) Change By: Thorsten Kahler Summary: NoClassDefFoundError during startup (Template Project plugin 1.5) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
Thorsten Kahler commented on JENKINS-14483 Remaining Xvfb processes in matrix jobs Hi Zoran, this is the error message (in matrix job) after installing your latest snapshot version: Started by user Thorsten Kahler [EnvInject] - Preparing an environment for the job. [EnvInject] - Jenkins system variables are kept. [EnvInject] - Jenkins build variables are kept. [EnvInject] - [ERROR] - SEVERE ERROR occurs: null Finished: FAILURE This might be a compatibility issue with our outdated Jenkins version 1.434? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
Thorsten Kahler commented on JENKINS-14483 Remaining Xvfb processes in matrix jobs Hi Zoran, still the same error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
Thorsten Kahler commented on JENKINS-14483 Remaining Xvfb processes in matrix jobs Hi Zoran, I'm sorry but it still doesn't work I think Xvfb shouldn't be started with the matrix job itself but only with every configuration - and stopped there as well. For a standalone Jenkins your current approach might work if Xvfb would not be stopped with configuration jobs (see excerpts from console log below). But as mentionend before with a master-slave setup IMHO the only way would be to start and stop Xvfb with the configuration jobs. Cheers, Thorsten Output of my latest test: Matrix job: Xvfb starting$ /usr/bin/Xvfb :60 -screen 0 1024x768x24 -fbdir /... [EnvInject] - Preparing an environment for the job. [EnvInject] - Jenkins system variables are kept. [EnvInject] - Jenkins build variables are kept. Couldn't open RGB_DB '/usr/share/X11/rgb' _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root [EnvInject] - Injecting as environment variables the properties content # ... error opening security policy file /usr/lib64/xserver/SecurityPolicy [EnvInject] - Variables injected successfully. Deleting project workspace... done Triggering configuration_1 FreeFontPath: FPE "unix/:7100" refcount is 2, should be 1; fixing. Couldn't open RGB_DB '/usr/share/X11/rgb' error opening security policy file /usr/lib64/xserver/SecurityPolicy FreeFontPath: FPE "unix/:7100" refcount is 2, should be 1; fixing. Couldn't open RGB_DB '/usr/share/X11/rgb' error opening security policy file /usr/lib64/xserver/SecurityPolicy FreeFontPath: FPE "unix/:7100" refcount is 2, should be 1; fixing. Triggering configuration_2 configuration_2 completed with result FAILURE Finished: FAILURE configuration_1 (touchstone build): gnoring Matrix job, Matrix build (the parent of this job) should have started Xvfb [EnvInject] - Using environment variables injected by the matrix job. Deleting project workspace... done No emails were triggered. [configuration_1] $ /bin/bash -le /tmp/hudson3288844765556768259.sh [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties file path '/.../confiugration_1/build_environment.properties' [EnvInject] - Variables injected successfully. # ... # doing deployment of PHP app # running some Jasmine smoke tests # ... Xvfb stopping Archiving artifacts # ... configuration_2: Ignoring Matrix job, Matrix build (the parent of this job) should have started Xvfb [EnvInject] - Using environment variables injected by the matrix job. Deleting project workspace... done No emails were triggered. [confiugration_2] $ /bin/bash -le /tmp/hudson4841252131230113695.sh [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties file path '/.../confiugration_2/build_environment.properties' [EnvInject] - Variables injected successfully. # ... # doing deployment of PHP app # trying to run some Jasmine smoke tests: Call smoketest (product) for URL http://configuration_2.domain/ Using the ci-smoketest profile... webkit_server: cannot connect to X server :60 F-webkit_server: cannot connect to X server :60 F (::) failed steps (::) # error message 1 scenario (1 failed) 2 steps (1 failed, 1 skipped) 0m30.454s Build step 'Use builders from another project' marked build as failure Xvfb stopping Archiving artifacts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
Thorsten Kahler commented on JENKINS-14483 Remaining Xvfb processes in matrix jobs Hi Zoran, I justed tested the new version with following observations (according to console log) on Jenkins 1.434: Xvfb is only started with matrix job Xvfb is stopped with configuration jobs The result is that the first configuration works fine and properly stops the Xvfb process. But then there's no available X server for the following configuration jobs and so they fail (message: webkit_server: cannot connect to X server :16; F-webkit_server: cannot connect to X server :16). I've only tested on a standalone Jenkins server but I think that this behaviour will fail especially in master-slave setups: if Xvfb is started on the master and the configuration jobs run on a slave every job will fail. Sorry for the bad news Cheers, Thorsten This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
Thorsten Kahler
commented on JENKINS-14483
Remaining Xvfb processes in matrix jobs
Hi Zoran,
I tried version 1.0.3-SNAPSHOT (private-07/21/2012 12:32-zregvart) on Jenkins 1.434 without success: Xvfb is still started on the matrix build too.
console output:
...
Ignoring Matrix build, waiting for Matrix jobs to follow
Xvfb starting$ /usr/bin/Xvfb :2 -screen 0 1024x768x24 -fbdir ${JENKINS_HOME}/2012-07-23_16-22-104384832168309393644xvfb
...
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
Thorsten Kahler updated JENKINS-14483 Remaining Xvfb processes in matrix jobs Change By: Thorsten Kahler (19/Jul/12 7:58 AM) Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14483) Remaining Xvfb processes in matrix jobs
Thorsten Kahler created JENKINS-14483 Remaining Xvfb processes in matrix jobs Issue Type: Bug Assignee: zregvart Components: matrix, xvfb Created: 18/Jul/12 12:24 PM Description: Enabling the Xvfb plugin on matrix jobs starts a Xvfb server for the job itself and one for each configuration. The Xvfb servers for the configurations are stoppd properly, but the Xvfb server for the job itself keeps running when the job finishes. This ends up in locked screens and a vast number of directories. We experienced that on a master only instance as well as in master-slave mode. Xvfb plugin version 1.0.2 Project: Jenkins Labels: plugin Priority: Major Reporter: Thorsten Kahler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
