[JIRA] (JENKINS-36881) Promotion build Plugin does not work with jobs which are nested in Jenkins folder FOLDER

2019-01-22 Thread lopez....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Lopez commented on  JENKINS-36881  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Promotion build Plugin does not work with jobs which are nested in Jenkins folder FOLDER
 

  
 
 
 
 

 
 Hello We are seeing the same issue. Could you  please share the workaround steps? Thank you kindly. Sam  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54499) Loosing connection to Docker container

2018-11-06 Thread lopez....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Lopez updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54499  
 
 
  Loosing connection to Docker container   
 

  
 
 
 
 

 
Change By: 
 Samuel Lopez  
 
 
Environment: 
 Jenkins  2.138.1 Running on Ubuntu 16.04Docker Plugin: 1.1.5 Docker version: 17.09.0-ce, build afdb6d4   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54499) Loosing connection to Docker container

2018-11-06 Thread lopez....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Lopez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54499  
 
 
  Loosing connection to Docker container   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Nicolas De Loof  
 
 
Components: 
 docker-plugin  
 
 
Created: 
 2018-11-06 20:34  
 
 
Environment: 
 Jenkins 2.138.1 Running on Ubuntu 16.04  Docker Plugin: 1.1.5
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Samuel Lopez  
 

  
 
 
 
 

 
 Hello We are seeing the following issue:   ERROR: Build step failed with exception java.lang.NullPointerException: no workspace from node io.jenkins.docker.DockerTransientNode[1604-JDK8-1uywz3thf] which is computer DockerComputer{name=1604-JDK8-1uywz3thf, slave=io.jenkins.docker.DockerTransientNode[1604-JDK8-1uywz3thf]} and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:88) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:945) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:896) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1815) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Execute shell' marked build as failure ERROR: Failed to parse POMs java.io.IOException: Backing channel '1604-JDK8-1uywz3thf' is disconnected. at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214) at 

[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down

2018-11-06 Thread lopez....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Lopez commented on  JENKINS-53468  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Since 1.27 update Channel is closing or has closed down   
 

  
 
 
 
 

 
 Hello Folks,   We are also observing this issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-53395) Multiple copies of the same job clubber workspace

2018-09-03 Thread lopez....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Lopez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53395  
 
 
  Multiple copies of the same job clubber workspace   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Nicolas De Loof  
 
 
Components: 
 docker-plugin  
 
 
Created: 
 2018-09-03 19:33  
 
 
Environment: 
 Jenkins: 2.121.1  Ubuntu: 16.04  Docker Plugin: 1.1.5  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Samuel Lopez  
 

  
 
 
 
 

 
 So we have created a Docker image to do the builds and configured Jenkins to use it. Our goal is to use this image to do as many of the builds as possible. All seems ok, Jenkins is able to spin the image and run builds in them, the issue we are facing is that if we trigger the same job around the same time they cripple each other because Jenkins is not allocating workspaces for the different copies of the job, the way it does when we ran it on a regular slave. So on a regular slave as long as we have allow concurrent builds bit set on, Jenkins will create directories under the workspace with names line jobName@2, jobName@3, etc. That is the behavior we are not seen we running in a docker container. All docker  containers have volume amount to /home/jenkins/workspace. Any help would be very much appreciated. Thanks /Sam        
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-53103) Pipeline does not pass environment variables to JobDsl

2018-08-17 Thread lopez....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Lopez updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53103  
 
 
  Pipeline does not pass environment variables to JobDsl   
 

  
 
 
 
 

 
Change By: 
 Samuel Lopez  
 

  
 
 
 
 

 
 Hello Folks,I have a regular Freestyle job that uses Process  Job DSLs step to run a  Groovy script.The Groovy script  references ${WORKSPACE} with out any issues. If I try to do the same from a  declarative pipeline the groovy scripts is not able to resolve ${WORKSPACE}line 24) No such property: WORKSPACE for class:I have looked at this issuehttps://issues.jenkins-ci.org/browse/JENKINS-44128but  that solution does not work because  additionalParameters is not supported by the  current DSL*!image-2018-08-17-10-27-26-034.png!*  WorkflowScript: 99: Invalid parameter "additionalParameters", did you mean "additionalClasspath"? @ line 99, column 21. additionalParameters: [message: 'foo'] ^1 error   Thanks in advance for the help/Sam   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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-53103) Pipeline does not pass environment variables to JobDsl

2018-08-17 Thread lopez....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Lopez updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53103  
 
 
  Pipeline does not pass environment variables to JobDsl   
 

  
 
 
 
 

 
Change By: 
 Samuel Lopez  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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-53103) Pipeline does not pass environment variables to JobDsl

2018-08-17 Thread lopez....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Lopez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53103  
 
 
  Pipeline does not pass environment variables to JobDsl   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Spilker  
 
 
Attachments: 
 image-2018-08-17-10-27-26-034.png  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2018-08-17 17:28  
 
 
Environment: 
 Jenkins: 2.121.1  OS: Ubuntu 16.04  DSL Plugin: 1.63  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Samuel Lopez  
 

  
 
 
 
 

 
 Hello Folks, I have a regular Freestyle job that uses Process  Job DSLs step to run a  Groovy script. The Groovy script  references ${WORKSPACE} with out any issues.   If I try to do the same from a  declarative pipeline the groovy scripts is not able to resolve ${WORKSPACE} line 24) No such property: WORKSPACE for class: I have looked at this issue https://issues.jenkins-ci.org/browse/JENKINS-44128 but  that solution does not work because  additionalParameters is not supported by the  current DSL    Thanks in advance for the help /Sam    
 

  
 
 
 
 

 
 
 

 
   

[JIRA] (JENKINS-45650) CLI known_hosts support fails on non-standard SSH ports

2018-08-09 Thread lopez....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Lopez commented on  JENKINS-45650  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CLI known_hosts support fails on non-standard SSH ports   
 

  
 
 
 
 

 
 Hello Folks,   We are seeing this issue as well on: Jenkins 2.121.1 Running on  Ubuntu 16.04 SSH Plugin 2.6.1   /Sam  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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-38905) Issue when implementing Junit: Publish test results report via Pipeline

2016-10-11 Thread lopez....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Lopez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38905  
 
 
  Issue when implementing Junit: Publish test results report via Pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 junit-plugin  
 
 
Created: 
 2016/Oct/11 4:42 PM  
 
 
Environment: 
 Jenkins ver 2.19.1  Ubuntu 14.04  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Samuel Lopez  
 

  
 
 
 
 

 
 java.lang.UnsupportedOperationException: no known implementation of interface jenkins.tasks.SimpleBuildStep is named junit at org.jenkinsci.plugins.structs.describable.DescribableModel.resolveClass(DescribableModel.java:417) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:371) at org.jenkinsci.plugins.structs.describable.DescribableModel.buildArguments(DescribableModel.java:313) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:257) at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:195) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:181) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:126) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:109) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1280) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1174) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1024) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:16) at WorkflowScript.run(WorkflowScript:72) at __cps.transform__(Native 

[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring

2016-03-04 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-32441 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SEVERE: Failed Loading plugin monitoring  
 
 
 
 
 
 
 
 
 
 
Hello and thanks for the update. We did find a third party log4j .jar file that was causing the problem. Once removed the monitoring plugin loaded successfully  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary

2016-03-04 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-28652 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary  
 
 
 
 
 
 
 
 
 
 
Thanks, On my side it looks like using the Mvn plugin at 0.7.5 fixes my issue 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary

2016-02-29 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-28652 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary  
 
 
 
 
 
 
 
 
 
 
Seeing similar issue here: 
Jacoco: 2.0.0 Jenkins: 1.642.1 OS: Ubuntu 14.04 
While reading execution data-file: /jenkins/job/105/jacoco/execFiles/exec6/jacoco.exec java.io.IOException: Incompatible version 1006. at org.jacoco.core.data.ExecutionDataReader.readHeader(ExecutionDataReader.java:127) at org.jacoco.core.data.ExecutionDataReader.readBlock(ExecutionDataReader.java:107) at org.jacoco.core.data.ExecutionDataReader.read(ExecutionDataReader.java:87) at hudson.plugins.jacoco.ExecutionFileLoader.loadExecutionData(ExecutionFileLoader.java:92) at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:132) at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:102) at hudson.plugins.jacoco.JacocoBuildAction.getResult(JacocoBuildAction.java:227) at hudson.plugins.jacoco.JacocoBuildAction.getCoverageRatios(JacocoBuildAction.java:247) 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:606) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring

2016-02-25 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-32441 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SEVERE: Failed Loading plugin monitoring  
 
 
 
 
 
 
 
 
 
 
It may be monitoring itself: monitoring/WEB-INF/lib monitoring/WEB-INF/lib/monitoring.jar monitoring/WEB-INF/lib/slf4j-api-1.6.3.jar monitoring/WEB-INF/lib/javamelody-core-1.58.0.jar monitoring/WEB-INF/lib/itext-2.1.7.jar monitoring/WEB-INF/lib/jrobin-1.5.9.jar monitoring/WEB-INF/licenses.xml 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-33133) WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in /jenkins/job/configure. Reason: java.lang.NullPointerException

2016-02-24 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-33133 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in /jenkins/job/configure. Reason: java.lang.NullPointerException  
 
 
 
 
 
 
 
 
 
 
Well, I have open a job config, made a change and saved it. When I open the config for the same job, the issue persists. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [token-macro-plugin] (JENKINS-32068) Missing many variable expansion tokens in jobs

2016-02-24 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez resolved as Won't Fix 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Issue not related to token macro 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32068 
 
 
 
  Missing many variable expansion tokens in jobs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Samuel Lopez 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Won't Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-33133) WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in /jenkins/job/configure. Reason: java.lang.NullPointerException

2016-02-24 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33133 
 
 
 
  WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in /jenkins/job/configure. Reason: java.lang.NullPointerException  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 24/Feb/16 5:16 PM 
 
 
 

Environment:
 

 Core: 1.642.1  Os: Ubuntu 14.04 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Samuel Lopez 
 
 
 
 
 
 
 
 
 
 
WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in /view/Brandcaster-Social/job/Brandcaster_GenerateBranchInfo/configure. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.Functions.getRelativeLinkTo(Functions.java:1068) at sun.reflect.GeneratedMethodAccessor167.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 

[JIRA] [ruby-runtime-plugin] (JENKINS-13467) WARNING: Failed to advertise the service to DNS multi-cast

2016-02-24 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
This is not longer happening after upgrading to the latest LTS 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-13467 
 
 
 
  WARNING: Failed to advertise the service to DNS multi-cast   
 
 
 
 
 
 
 
 
 

Change By:
 
 Samuel Lopez 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [token-macro-plugin] (JENKINS-32068) Missing many variable expansion tokens in jobs

2016-02-24 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-32068 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing many variable expansion tokens in jobs  
 
 
 
 
 
 
 
 
 
 
Thanks Alex, 
After looking closely at the stack trace, I realized that my issue appears not to be related to token macro. 
I'll open a separate issue. 
Sam 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [token-macro-plugin] (JENKINS-32068) Missing many variable expansion tokens in jobs

2016-02-23 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Hello Alex, 
I am still having this problem. 
Jenkins Core: 1.642.1 OS: Ubuntu 14.04 
I have open a job configuration and the exception is thrown. Then I made a change in the job configuration and save it. When I tried to open the job configuration after I save it, the issue persists. 
Thanks for the help Sam 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32068 
 
 
 
  Missing many variable expansion tokens in jobs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Samuel Lopez 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

[JIRA] [token-macro-plugin] (JENKINS-32068) Missing many variable expansion tokens in jobs

2016-02-23 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-32068 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing many variable expansion tokens in jobs  
 
 
 
 
 
 
 
 
 
 
Have upgraded Jenkins to 1.642.1 and still see this is issue 
I have edited a job configuration and save it. Yet next time I open the configuration the issue persists.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring

2016-02-23 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-32441 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SEVERE: Failed Loading plugin monitoring  
 
 
 
 
 
 
 
 
 
 
Here is the list of currently installed plugins 
ant Ant Plugin 1.2  ldap LDAP Plugin 1.11  subversion Subversion Plug-in 2.5.7  javadoc Javadoc Plugin 1.3  translation Translation Assistance plugin 1.12  cvs CVS Plug-in 2.11 (2.12)  ssh-slaves SSH Slaves plugin 1.10  external-monitor-job External Monitor Job Type Plugin 1.4  pam-auth PAM Authentication plugin 1.2  maven-plugin Maven Integration plugin 2.12.1  active-directory Active Directory plugin 1.41  description-setter description setter plugin 1.10  greenballs Green Balls 1.15  built-on-column built-on-column 1.1  lastfailureversioncolumn Last Failure Version Column 1.1  lastsuccessversioncolumn Last Success Version Column 1.1  log-parser Log Parser Plugin 2.0  mstest MSTest plugin 0.19  multiple-scms Multiple SCMs plugin 0.5  next-build-number Next Build Number Plugin 1.1 (1.3)  show-build-parameters Show Build Parameters plugin 1.0  m2release Maven Release Plug-in Plug-in 0.14.0  ws-cleanup Workspace Cleanup Plugin 0.28  confluence-publisher Confluence Publisher 1.8  hudson-pview-plugin Hudson Personal View 1.8  testng-plugin TestNG Results Plugin 1.10  ivy Ivy Plugin 1.26  backup Backup plugin 1.6.1  publish-over-ssh Publish Over SSH 1.13 jira JIRA plugin 2.1  dashboard-view Dashboard View 2.9.7  artifactory Artifactory Plugin 2.3.1 (2.4.7)  xunit xUnit plugin 1.99 (1.100)  email-ext Email Extension Plugin 2.40.5 (2.41.2)  testlink TestLink Plugin 3.11  envfile Environment File Plugin 1.2  envinject Environment Injector Plugin 1.92.1  analysis-core Static Analysis Utilities 1.75  findbugs FindBugs Plug-in 4.63  ssh SSH plugin 2.4  warnings Warnings Plug-in 4.51  promoted-builds promoted builds plugin 2.24.1 (2.25)  htmlpublisher HTML Publisher plugin 1.10 (1.11)  nested-view Nested View Plugin 1.14  mercurial Mercurial plugin 1.54  environment-script Environment Script Plugin 1.2.2  extended-choice-parameter Extended Choice Parameter Plug-In 0.56  android-lint Android Lint Plugin 2.2  jobConfigHistory Job Configuration History Plugin 2.12  preSCMbuildstep Pre SCM BuildStep Plugin 0.3  jacoco JaCoCo plugin 2.0.0 (2.0.1)  credentials Credentials Plugin 1.18 (1.25)  ssh-credentials SSH Credentials Plugin 1.11  copyartifact Copy Artifact Plugin 1.37  mailer Mailer Plugin 1.16  job-dsl Job DSL 1.43  saferestart Safe Restart Plugin 0.3  token-macro Token Macro Plugin 1.12.1  violations Violations plugin 0.7.11  parameterized-trigger Parameterized Trigger plugin 2.30  config-file-provider Config File Provider Plugin 2.10.0  ssh-agent SSH Agent Plugin 1.9  scm-api SCM API Plugin 1.0  analysis-collector Static Analysis Collector Plug-in 1.46  checkstyle Checkstyle Plug-in 3.44  build-timeout build timeout plugin 1.15.1 (1.16)  pmd PMD Plug-in 3.43  run-condition Run Condition Plugin 1.0  fail-the-build-plugin Fail The Build Plugin 1.0  buildgraph-view buildgraph-view 1.1.1  jquery jQuery plugin 1.11.2-0  build-pipeline-plugin Build Pipeline Plugin 1.4.9  conditional-buildstep conditional-buildstep 1.3.3  jenkins-multijob-plugin Multijob plugin 1.20  port-allocator Port Allocator Plug-in 1.8  hockeyapp HockeyApp Plugin 1.2.0 (1.2.1)  xcode-plugin Xcode integration 1.4.9  testflight Testflight Plugin 1.3.9  jobtemplates jobtemplates 1.0  template-project Template Project plugin 1.5.1 (1.5.2)  groovy Groovy 1.29  sbt sbt plugin 1.5  rundeck Rundeck plugin 3.5.1  scripttrigger scripttrigger 0.32  kpp-management-plugin Keychains and Provisioning Profiles Management 1.0.0  antisamy-markup-formatter OWASP Markup Formatter Plugin 1.3  windows-slaves Windows Slaves Plugin 1.1  rebuild Rebuilder 1.25  mapdb-api MapDB API Plugin 1.0.6.0  matrix-auth Matrix Authorization Strategy Plugin 1.2  jquery-ui jQuery UI plugin 1.0.2  

[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring

2016-02-22 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-32441 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SEVERE: Failed Loading plugin monitoring  
 
 
 
 
 
 
 
 
 
 
Thanks for the reply 
We have quite a few plugins, is there a particular set I should be looking at? Yes it happens when I restart Jenkins 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [token-macro-plugin] (JENKINS-32068) Missing many variable expansion tokens in jobs

2016-01-21 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-32068 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing many variable expansion tokens in jobs  
 
 
 
 
 
 
 
 
 
 
Seeing the same issue here; 
Jenkins 1.625.1 OS: Ubuntu 14.04 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring

2016-01-13 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32441 
 
 
 
  SEVERE: Failed Loading plugin monitoring  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 monitoring-plugin 
 
 
 

Created:
 

 13/Jan/16 7:15 PM 
 
 
 

Environment:
 

 Ubuntu 14.04  Jenkins Core 1.625.3  
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Samuel Lopez 
 
 
 
 
 
 
 
 
 
 
Unable to install/load Monitoring plugin 1.58.0 
SEVERE: Failed Loading plugin monitoring java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:441) at hudson.PluginManager$2$1$1.run(PluginManager.java:371) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:905) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoSuchMethodError: net.bull.javamelody.Log4JAppender.setThreshold(Lorg/apache/log4j/Priority;)V at net.bull.javamelody.Log4JAppender.(Log4JAppender.java:42) at 

[JIRA] [mercurial-plugin] (JENKINS-29311) Deprecated call to Run.getEnvironment

2016-01-13 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-29311 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Deprecated call to Run.getEnvironment  
 
 
 
 
 
 
 
 
 
 
Hello, Any idea when this fix will be released? Thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jobconfighistory] (JENKINS-20571) WARNING: Caught exception evaluating: it.showBadge() and it.oldConfigsExist()

2013-11-15 Thread lopez....@gmail.com (JIRA)














































Samuel Lopez
 commented on  JENKINS-20571


WARNING: Caught exception evaluating: it.showBadge() and it.oldConfigsExist()















Well the issue started with 2.5
I have put it back and my original warning seems to be gone but now getting this:

WARNING: Skipping a non-existent field targetType
com.thoughtworks.xstream.converters.reflection.MissingFieldException: No field 'targetType' found in class 'hudson.plugins.jobConfigHistory.JobConfigBadgeAction'
at com.thoughtworks.xstream.converters.reflection.FieldDictionary.field(FieldDictionary.java:94)
at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.getFieldType(PureJavaReflectionProvider.java:157)
at hudson.util.RobustReflectionConverter.determineType(RobustReflectionConverter.java:399)
at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:271)
at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71)
at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85)
at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:61)
at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333)
at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275)
at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222)



























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







-- 
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/groups/opt_out.


[JIRA] [jobconfighistory] (JENKINS-20571) WARNING: Caught exception evaluating: it.showBadge() and it.oldConfigsExist()

2013-11-15 Thread lopez....@gmail.com (JIRA)














































Samuel Lopez
 commented on  JENKINS-20571


WARNING: Caught exception evaluating: it.showBadge() and it.oldConfigsExist()















And I can't get jobs to report their Configuration History



























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







-- 
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/groups/opt_out.


[JIRA] (JENKINS-13467) WARNING: Failed to advertise the service to DNS multi-cast

2012-04-16 Thread lopez....@gmail.com (JIRA)
Samuel Lopez created JENKINS-13467:
--

 Summary: WARNING: Failed to advertise the service to DNS 
multi-cast 
 Key: JENKINS-13467
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13467
 Project: Jenkins
  Issue Type: Bug
  Components: jenkins-plugin-runtime
Affects Versions: current
 Environment: Jenkins ver. 1.459 on Linux CentOS 6
Reporter: Samuel Lopez
Assignee: Sami Tikka
Priority: Minor


WARNING: Failed to advertise the service to DNS multi-cast
java.net.MalformedURLException
at java.net.URL.init(URL.java:617)
at java.net.URL.init(URL.java:480)
at java.net.URL.init(URL.java:429)
at hudson.DNSMultiCast.init(DNSMultiCast.java:45)
at jenkins.model.Jenkins.init(Jenkins.java:787)
at hudson.model.Hudson.init(Hudson.java:81)
at hudson.model.Hudson.init(Hudson.java:77)
at hudson.WebAppMain$2.run(WebAppMain.java:217)
Caused by: java.lang.NullPointerException
at java.net.URL.init(URL.java:522)
... 7 more
Apr 13, 2012 12:25:26 AM hudson.WebAppMain$2 run
INFO: Jenkins is fully up and running


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira