[JIRA] (JENKINS-60104) Agent to Master Access Control rule throws java exception
Title: Message Title Dennis Tran commented on JENKINS-60104 Re: Agent to Master Access Control rule throws java exception I got the same issue in Jenkins ver. 2.190.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202950.1573212865000.380.1577438340143%40Atlassian.JIRA.
[JIRA] (JENKINS-59837) java.lang.OutOfMemoryError: Compressed class space
Title: Message Title Dennis Tran created an issue Jenkins / JENKINS-59837 java.lang.OutOfMemoryError: Compressed class space Issue Type: Story Assignee: Unassigned Components: _unsorted Created: 2019-10-18 06:45 Environment: Jenkins 2.164.2 java version "1.8.0_201 Priority: Minor Reporter: Dennis Tran Apparently, my build job failed unit test, this issue happening randomly in every slave node. [INFO] Running ch.crdw.task.service.CrdhwayDraftTaskServiceTest [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.798 s - in ch.crdw.task.service.CrdhwayDraftTaskServiceTest [INFO] Running ch.crdw.cloning.service.DossierTaskServiceTest [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.173 s - in ch.crdw.cloning.service.DossierTaskServiceTest [INFO] Running ch.crdw.helper.DossierOperationHelperTest [INFO] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.829 s - in ch.crdw.helper.DossierOperationHelperTest [INFO] Running ch.crdw.helper.AbstractCockpitBuilderTest [INFO] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5 s - in ch.crdw.helper.AbstractCockpitBuilderTest [INFO] Running ch.crdw.helper.CompetenceLevelHelperTest [INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.341 s - in ch.crdw.helper.CompetenceLevelHelperTest [INFO] Running ch.crdw.helper.PropertyHelperTest [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.728 s - in ch.crdw.helper.PropertyHelperTest [INFO] Running ch.crdw.helper.ClientOnBoardingViewBeanHelperTest [ERROR] Tests run: 2, Failures: 0, Errors: 1,
[JIRA] (JENKINS-59457) all pipeline job failed after upgrade security script plugin
Title: Message Title Dennis Tran closed an issue as Won't Fix My apologies, this issue not come from security script plugin, but from Pipeline Nodes and Processes Plugin, I did not update Pipeline Groovy Plugin before update it. Jenkins / JENKINS-59457 all pipeline job failed after upgrade security script plugin Change By: Dennis Tran Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-59457) all pipeline job failed after upgrade security script plugin
Title: Message Title Dennis Tran created an issue Jenkins / JENKINS-59457 all pipeline job failed after upgrade security script plugin Issue Type: Bug Assignee: Andrew Bayer Components: script-security-plugin Created: 2019-09-20 05:02 Environment: Jenkins in Ubuntu version 2.164.2 Script security plugin 1.64 Priority: Minor Reporter: Dennis Tran After upgrading secript security plugin from version 1.57 to 1.64, all my pipeline jobs have been failed with some error: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingorg.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingPerhaps you forgot to surround the code with a step that provides this, such as: node, dockerNode at org.jenkinsci.plugins.workflow.steps.StepDescriptor.checkContextAvailability(StepDescriptor.java:266) or Groovy.lang.MissingPropertyException: No such property: buildUser for class: WorkflowScriptGroovy.lang.MissingPropertyException: No such property: buildUser for class: WorkflowScript at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458) at
[JIRA] (JENKINS-58231) Job build failed when one of domain in Active Directory unreachable
Title: Message Title Dennis Tran commented on JENKINS-58231 Re: Job build failed when one of domain in Active Directory unreachable I just facing this issues again. 14:15:16 FATAL: org.acegisecurity.AuthenticationServiceException: Failed to bind to LDAP server with the bind name/password; nested exception is javax.naming.CommunicationException: adv.aavn.local:3268 [Root exception is java.net.SocketTimeoutException: connect timed out]14:15:16java.net.SocketTimeoutException: connect timed out*14:15:16* at java.net.PlainSocketImpl.socketConnect(Native Method)14:15:16 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)14:15:16 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)14:15:16 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)14:15:16 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)14:15:16 at java.net.Socket.connect(Socket.java:589)14:15:16 at sun.reflect.GeneratedMethodAccessor20610.invoke(Unknown Source)14:15:16 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)14:15:16 at java.lang.reflect.Method.invoke(Method.java:498)14:15:16 at com.sun.jndi.ldap.Connection.createSocket(Connection.java:362)14:15:16 at com.sun.jndi.ldap.Connection.(Connection.java:215)14:15:16 Caused: javax.naming.CommunicationException: adv.aavn.local:3268 [Root exception is java.net.SocketTimeoutException: connect timed out]14:15:16 at com.sun.jndi.ldap.Connection.(Connection.java:228)14:15:16 at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137)14:15:16 at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1615)14:15:16 at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749)14:15:16 at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319)14:15:16 at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)14:15:16 at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151)14:15:16 at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:668)14:15:16 at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:599)14:15:16 at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:357)14:15:16 Caused: org.acegisecurity.AuthenticationServiceException: Failed to bind to LDAP server with the bind name/password; nested exception is javax.naming.CommunicationException: adv.aavn.local:3268 [Root exception is java.net.SocketTimeoutException: connect timed out]14:15:16 at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:360)14:15:16 at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:340)14:15:16 at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767)14:15:16 at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568)14:15:16 at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)14:15:16 at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313)14:15:16 at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228)14:15:16 at com.google.common.cache.LocalCache.get(LocalCache.java:3965)14:15:16 at
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Dennis Tran commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted I'm facing a same issue in Jenkins 2.164.2, slave is windows 10 1809, java 18.0.221. I tried to clear slave workspace directory and download new launcher as Dan Wang suggest, but no luck, this problem still occur. However, I do not understand the point "3. Use task-scheduler to process slave-agent", can you explain more detail how to do that, Dan Wang. Thanks. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164090.1437742638000.7673.1564974720899%40Atlassian.JIRA.
[JIRA] (JENKINS-58231) Job build failed when one of domain in Active Directory unreachable
Title: Message Title Dennis Tran created an issue Jenkins / JENKINS-58231 Job build failed when one of domain in Active Directory unreachable Issue Type: Story Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2019-06-27 04:17 Environment: AD plugin 2.13 Jenkins 2.164.2 Priority: Minor Reporter: Dennis Tran In Action Directory section on Configure global security, I added 3 domain, let said domain A, B, and C. Today, domain B has been down, so users could not login with LDAP account in domain B, that is definitely. But, I have no idea why some build jobs have been failed with error below. FATAL: org.acegisecurity.AuthenticationServiceException: Failed to bind to LDAP server with the bind name/password; nested exception is javax.naming.CommunicationException: 192.168.1.3:3268 [Root exception is java.net.SocketTimeoutException: connect timed out] java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.reflect.GeneratedMethodAccessor10329.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at
[JIRA] (JENKINS-52125) jenkins master: Cannot contact : java.lang.InterruptedException without heavy load or obvious network issue
Title: Message Title
Dennis Tran edited a comment on JENKINS-52125
Re: jenkins master: Cannot contact : java.lang.InterruptedException without heavy load or obvious network issue
I got the same issue in version 2.164.2. I think the build job produce a heavy load, sometimes it also encounter encountered the error {code:java}The forked VM terminated without properly saying goodbye. VM crash or System.exit called{code}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191724.1529617125000.20481.1559634180308%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52125) jenkins master: Cannot contact : java.lang.InterruptedException without heavy load or obvious network issue
Title: Message Title Dennis Tran commented on JENKINS-52125 Re: jenkins master: Cannot contact : java.lang.InterruptedException without heavy load or obvious network issue I got the same issue in version 2.164.2. I think the build job produce a heavy load, sometimes it also encounter the error The forked VM terminated without properly saying goodbye. VM crash or System.exit called 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191724.1529617125000.20472.1559634120239%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56967) Jenkins Pipeline parallel checkout fails on ECS slave
Title: Message Title Dennis Tran commented on JENKINS-56967 Re: Jenkins Pipeline parallel checkout fails on ECS slave In the agent already install git, this agent can build another build jobs. so yes, it could be a configuration issues, may be running parallel checkout need a specific configuration in git which I have no idea to figure out. 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-56967) Jenkins Pipeline parallel checkout fails on ECS slave
Title: Message Title
Dennis Tran created an issue
Jenkins / JENKINS-56967
Jenkins Pipeline parallel checkout fails on ECS slave
Issue Type:
Story
Assignee:
Mark Waite
Components:
git-plugin, pipeline
Created:
2019-04-11 08:59
Environment:
Jenkins 2.150.1 ECS plugin 1.17 Slave docker image using ubuntu 16.4 and git 2.11.0
Priority:
Minor
Reporter:
Dennis Tran
I'm using parallel stage in pipeline, but it not work with ecs container slave, there is no problem if build in native slave. Here is my pipeline script
def buildModules = ""; def buildModules = "";
try {
stage('Prepare') {
buildModules = "individualch,desk_individual,desk_individual_customer1,mobile_individual,mobile_individual_customer1,entitych,desk_entity"; mvnHome = "/usr/share/maven"
}
stage('Checkout') {
parallel desk_built_t: {
checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CheckoutOption', timeout: 120],[$class: 'CloneOption', timeout: 120]], submoduleCfg: [], userRemoteConfigs: [[credentialsId: '4f45191d-63c0-473b-8b5c-6f5621ed148a', url: 'g...@bitbucket.org:tiendung/desk_built_t.git']]])
},
portal_customization: {
checkout([$class: 'GitSCM', branches: [[name: "*/${params.portal_customization_branch}"]], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CheckoutOption', timeout: 120],[$class: 'CloneOption', timeout: 120],[$class: 'RelativeTargetDirectory', relativeTargetDir: 'portal_customization']], submoduleCfg: [], userRemoteConfigs: [[credentialsId:
[JIRA] (JENKINS-26257) java.lang.ClassCastException/NPE in Remoting while executing Maven Builder
Title: Message Title Dennis Tran commented on JENKINS-26257 Re: java.lang.ClassCastException/NPE in Remoting while executing Maven Builder I got the same issue in Jenkins 2.150.1. Disabling the automatic fingerprinting removes the exception in the log. But what is the side effect of disabling fingerprinting? (and why did it work previsously). Will disabling fingerprinting not break dependency management between projects? 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-8977) LDAP Groups with spaces in the CN don't work with ROLE_ patterns.
Title: Message Title Dennis Tran commented on JENKINS-8977 Re: LDAP Groups with spaces in the CN don't work with ROLE_ patterns. I have the same issue, is there any fix? 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-51314) Console output show many http-outgoing strange code
Title: Message Title Dennis Tran created an issue Jenkins / JENKINS-51314 Console output show many http-outgoing strange code Issue Type: Story Assignee: Unassigned Components: core Created: 2018-05-15 03:51 Environment: OS: Linux. Jenkins ver. 2.107.1 Priority: Minor Reporter: Dennis Tran Hi, So far we have some job build, the console output show strange code like below, and we have to remove '-X' option in build goal configuration to get rid of. I think it happen after I upgrade Jenkins version. any idea? // [DEBUG] http-outgoing-0 >> "j[0x5]q4/J[0x18]^di[0x86][0xbf]C_[0xd6]G[0x1d][0xd4][0x7][0xf3] [0xc7][0x14][0xdf][0x8d][0xe1][0x13][0xd8]$y|#[0x1e][0xbf][0xe6][0x81]<[0xca][0x6][0xa1]~j[0x81]3[0xbc][0x98][0xd1][0x83][0xa7][0xc5]8[0xfa]>[0xd9]edZ[0xb2][0xc][0xe0][0x5][0xab][0xf3][0x1a]M[0xb3][0xe7][0x1][0xf4][\n]" [DEBUG] http-outgoing-0 >>
[JIRA] (JENKINS-41199) Provisioned agent ECS Slave ecs-quitest failed to launch
Title: Message Title Dennis Tran created an issue Jenkins / JENKINS-41199 Provisioned agent ECS Slave ecs-quitest failed to launch Issue Type: Story Assignee: Unassigned Attachments: Capture.PNG Components: plugin-usage-plugin Created: 2017/Jan/19 4:10 AM Environment: Jenkins 2.32.1 ECS Agent 1.13.1 Labels: jenkins ecs Priority: Minor Reporter: Dennis Tran Hi support I'm using ECS for Jenkins slave, when I build test, I saw tasks running in ECS, but in Jenkins said ECS offline. The connection between jenkins and ECS is ok, please advise me how to figure out this issue. Thanks. -- Making ecs-cloud-14121d927e9f offline because it's not responding Jan 19, 2017 3:38:36 AM WARNING hudson.node_monitors.ResponseTimeMonitor$1 monitor Making ecs-cloud-3421ccae4c82 offline because it's not responding Jan 19, 2017 3:38:46 AM WARNING hudson.model.listeners.ItemListener forAll failed to send event to listener of class org.jenkinsci.plugins.pipeline.milestone.MilestoneStepExecution$CleanupJobsOnDelete java.lang.NullPointerException at org.jenkinsci.plugins.pipeline.milestone.MilestoneStepExecution$CleanupJobsOnDelete.onDeleted(MilestoneStepExecution.java:348) at hudson.model.listeners.ItemListener$4.apply(ItemListener.java:205) at hudson.model.listeners.ItemListener$4.apply(ItemListener.java:203) at
