ConfigFiles 3.0 appears to be mangling config.xml
Upgraded from 2.18 to 3.0 After the upgrade, configs persist on the filesystem inside config.xml until that job is visited in the UI (presumably, config.xml is revalidated at that point and 3.0 throws the error). The attached unreadable_data message also appears in the Manage Old Data section. Old config.xml shows this comparator: New config.xml shows this comparator: I see some commits about pulling ConfigComparator out from where it used to live, but I'm not sure if that's the exact cause of what's going on here. Thanks, Mike -- 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/4f7c4a3a-e606-4c77-bfaf-4a011808bec0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. ConversionException: org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty$1 : org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty$1 Debugging information message : org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty$1 cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException cause-message : org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty$1 class : java.util.TreeSet required-type : java.util.TreeSet converter-type : com.thoughtworks.xstream.converters.collections.TreeSetConverter path : /com.cloudbees.hudson.plugins.folder.Folder/properties/org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty/configs/comparator line number : 9 ---, MissingFieldException: No field 'org.jenkinsci.plugins.configfiles.json.JsonConfig' found in class 'org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty', MissingFieldException: No field 'org.jenkinsci.plugins.configfiles.custom.CustomConfig' found in class 'org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty', MissingFieldException: No field 'org.jenkinsci.plugins.configfiles.custom.CustomConfig' found in class 'org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty', ConversionException: Could not call org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty.readResolve() : null : Could not call org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty.readResolve() : null Debugging information message : Could not call org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty.readResolve() : null cause-exception : com.thoughtworks.xstream.converters.reflection.ObjectAccessException cause-message : Could not call org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty.readResolve() : null class : org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty required-type : java.util.TreeSet converter-type : hudson.util.RobustReflectionConverter path : /com.cloudbees.hudson.plugins.folder.Folder/properties/org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty/configs line number : 75
Re: Kubernetes Plugin 1.2 Agents unable to establish connection to master, but log they can
Hi all, Can anyone please help with the following error Error from server (Forbidden): pods is forbidden: User "system:anonymous" cannot list pods in the namespace "default" Setup Kubernetes CLI (kubectl) Options: Kubernetes server endpoint -> server from config (ex: https://ip:6443) Certificate of certificate authority -> authority data Credentials -> System Credentials (Is that correct ?) I provided above details in Jenkins Kubernetes CLI Setup On Thursday, February 22, 2018 at 4:29:49 PM UTC+5:30, Carlos Sanchez wrote: > > OOMKilled has nothing to do with the host resources, but the process in > the container using more memory than available. > Try increasing the memory limits and read > https://blog.csanchez.org/2017/05/31/running-a-jvm-in-a-container-without-getting-killed/ > > On Thu, Feb 22, 2018 at 10:19 AM, > wrote: > >> Disk space and memory are all at an extremely low utilization for all of >> my hosts. So it's not real resource exhaustion. I'm thinking timeline wise >> it seems that OOMkilled state is possibly a result of kubernetes >> terminating the pod due to disconnection. >> >> >> INFO: Excess workload after pending Spot instances: 1 >> Feb 22, 2018 9:05:10 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision >> INFO: Template: Kubernetes Pod Template >> Feb 22, 2018 9:05:10 AM okhttp3.internal.platform.Platform log >> INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot >> class path? >> Feb 22, 2018 9:05:10 AM >> hudson.slaves.NodeProvisioner$StandardStrategyImpl apply >> INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 >> executors. Remaining excess workload: 0 >> Feb 22, 2018 9:05:20 AM hudson.slaves.NodeProvisioner$2 run >> INFO: Kubernetes Pod Template provisioning successfully completed. We >> have now 2 computer(s) >> Feb 22, 2018 9:05:20 AM okhttp3.internal.platform.Platform log >> INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot >> class path? >> Feb 22, 2018 9:05:20 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Created Pod: jnlp-t2c36 in namespace jenkins-test >> Feb 22, 2018 9:05:20 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (0/100): jnlp-t2c36 >> Feb 22, 2018 9:05:26 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (1/100): jnlp-t2c36 >> Feb 22, 2018 9:05:32 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (2/100): jnlp-t2c36 >> Feb 22, 2018 9:05:38 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (3/100): jnlp-t2c36 >> Feb 22, 2018 9:05:44 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (4/100): jnlp-t2c36 >> Feb 22, 2018 9:05:47 AM hudson.model.Descriptor verifyNewInstance >> WARNING: Father of ContainerEnvVar [getValue()= >> http://jenkins-test-jenkins:8080, getKey()=JENKINS_URL] and its >> getDescriptor() points to two different instances. Probably malplaced >> @Extension. See >> http://hudson.361315.n4.nabble.com/Help-Hint-needed-Post-build-action-doesn-t-stay-activated-td2308833.html >> Feb 22, 2018 9:05:50 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (5/100): jnlp-t2c36 >> Feb 22, 2018 9:05:56 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (6/100): jnlp-t2c36 >> Feb 22, 2018 9:06:02 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (7/100): jnlp-t2c36 >> Feb 22, 2018 9:06:08 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (8/100): jnlp-t2c36 >> Feb 22, 2018 9:06:14 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (9/100): jnlp-t2c36 >> Feb 22, 2018 9:06:20 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (10/100): jnlp-t2c36 >> Feb 22, 2018 9:06:26 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (11/100): jnlp-t2c36 >> Feb 22, 2018 9:06:32 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (12/100): jnlp-t2c36 >> Feb 22, 2018 9:06:38 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (13/100): jnlp-t2c36 >> Feb 22, 2018 9:06:44 AM >> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch >> INFO: Waiting for Pod to be scheduled (14/100): jnlp-t2c36 >> Feb 22, 2018 9:06:50 AM >>
Can't access wiki.jenkins.io / wiki.jenkins-ci.org -- 403 Forbidden
Hi, I'm getting random (?) 403 errors trying to access wiki today. First it was https://wiki.jenkins.io/display/JENKINS/Fingerprint+Plugin (works now), now I can't access https://wiki.jenkins.io/display/JENKINS/Amazon+ECR This is a bit of a problem as not all content is mirrored to plugins.jenkins.io What is happening? Is this some planned migration -- 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/1b1fcc6d-9c2a-4070-b749-a21dcfee2e1b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Blank HTML report in Jenkin's left hand side bar for Performance Center Reports
Hi
I am using a pipeline to connect Performance center from Jenkins. I am able
to run the tests successfully, however unable to view the report on left
hand side console in Jenkins. Its appearing blank. Please suggest if
someone has any clue about this.
Jenkin version:- 2.107.3
Microfocus Automation Plugin: 5.3
*Pipeline Job:-*
stage('RunPCTESTS'){ // The stage name
node('master'){ // The name of the node in which to run the test.
def perfResultPath
def currentBuildNo = env.BUILD_NUMBER
println currentBuildNo
pcBuild HTTPSProtocol: false, addRunToTrendReport: 'NO_TREND',
almDomain: 'DEFAULT', almPassword: 'x', almProject: 'Test',
almUserName: 'temp1', autoTestInstanceID: 'MANUAL', description: '',
pcServerName: 'nclpwnqwebx.cmp.aon.net', postRunAction:
'COLLATE_AND_ANALYZE', proxyOutPassword: '', proxyOutURL: '', proxyOutUser:
'', serverAndPort: 'http://localhost:8080', statusBySLA: false, testId:
'46', testInstanceId: '24', timeslotDurationHours: '0',
timeslotDurationMinutes: '30', trendReportId: '', vudsMode: false
perfResultPath= 'C:\\Program Files (x86)
\\Jenkins\\jobs\\RAF_PT_Pipeline\\builds\\'+currentBuildNo+'\\archive\\performanceTestsReports\\pcRun
'
println perfResultPath
publishHTML([allowMissing: false, alwaysLinkToLastBuild: false, keepAll:
true, reportDir: '', reportFiles: perfResultPath+'\\Report.html',
reportName: 'Performance Report', reportTitles: 'HTML Performance Report'])
}
}
--
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/b9315515-45cd-49b4-80e2-208a958f1573%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
How to use NodeLabel Parameter Plugin in Declarative Pipeline ?
Im trying to use the NodeLabel Parameter pluging from a declarative pipeline (https://wiki.jenkins.io/display/JENKINS/NodeLabel+Parameter+Plugin). Anyone have any ideas how to make this work ? It seems like the NodeParameter isnt even available in declarative pipelines ? -- 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/8e43a74d-e2ac-486b-9f43-574ee99677f3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
