[JIRA] (JENKINS-61312) Unable to seed a pipeline job which has the BbS SCM step
Title: Message Title PJ created an issue Jenkins / JENKINS-61312 Unable to seed a pipeline job which has the BbS SCM step Issue Type: Bug Assignee: Kristy Hughes Attachments: groovy-bbs-scm.txt Components: atlassian-bitbucket-server-integration-plugin, job-dsl-plugin Created: 2020-03-03 17:25 Environment: Jenkins- 2.204.2 BitBucket-Server-Integration Plugin: 1.1.0 job-dsl-plugin: 1.76 Priority: Blocker Reporter: PJ Unable to Seed a pipeline job when replacing the following in the groovy for the scm definition step and receive the following error When editing the job using the Jenkins UI and updating the all the appropriat fields, everything works perfectly. Just that the seed-job fails to read the groovy file to create a job. Attached is my groovy code for the SCM step. Could you please advice if this is an issue with the dsl-plugin or with the Bitbucket-Server-Integration Plugin ? Build Error: [hudson.AbortException: (job.groovy, line 50) No signature of method: javaposse.jobdsl.dsl.helpers.ScmContext.Bbs() is applicable for argument types: ($_run_closure1$_closure4$_closure6$_closure7$_closure8) values: [$_run_closure1$_closure4$_closure6$_closure7$_closure8@71df7e4c] Possible solutions: is(java.lang.Object), any(), git(groovy.lang.Closure), git(java.lang.String), hg(java.lang.String), rtc(groovy.lang.Closure)]
[JIRA] (JENKINS-61312) Unable to seed a pipeline job which has the BbS SCM step
Title: Message Title PJ updated an issue Jenkins / JENKINS-61312 Unable to seed a pipeline job which has the BbS SCM step Change By: PJ Attachment: groovy-bbs-scm.txt Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.204895.1583256305000.3883.1583256360671%40Atlassian.JIRA.
[JIRA] (JENKINS-61312) Unable to seed a pipeline job which has the BbS SCM step
Title: Message Title
PJ updated an issue
Jenkins / JENKINS-61312
Unable to seed a pipeline job which has the BbS SCM step
Change By:
PJ
Unable to Seed a pipeline job when replacing the following in the groovy for the git scm definition step with Bbs (as attached) and receive the following error When editing the job using the Jenkins UI and updating the all the appropriat fields, everything works perfectly. Just that the seed-job fails to read the groovy file to create a job. Attached is my groovy code for the SCM step.Could you please advice if this is an issue with the dsl-plugin or with the Bitbucket-Server-Integration Plugin ? {code:java}Build Error: [hudson.AbortException: (job.groovy, line 50) No signature of method: javaposse.jobdsl.dsl.helpers.ScmContext.Bbs() is applicable for argument types: ($_run_closure1$_closure4$_closure6$_closure7$_closure8) values: [$_run_closure1$_closure4$_closure6$_closure7$_closure8@71df7e4c] Possible solutions: is(java.lang.Object), any(), git(groovy.lang.Closure), git(java.lang.String), hg(java.lang.String), rtc(groovy.lang.Closure)]{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61006) AWS EC2 plugin failing to connect to Windows Slave
Title: Message Title PJ commented on JENKINS-61006 Re: AWS EC2 plugin failing to connect to Windows Slave HI FABRIZIO MANFREDI Could you please update on this ? We are seeing the same errors even after updating the plugin to the latest 1.50.1 version. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.204476.1581025948000.20469.1588368720146%40Atlassian.JIRA.
[JIRA] (JENKINS-61006) AWS EC2 plugin failing to connect to Windows Slave
Title: Message Title Parameswaran Jayaraman created an issue Jenkins / JENKINS-61006 AWS EC2 plugin failing to connect to Windows Slave Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-02-06 21:52 Environment: Jenkins - 2.204.2 ec2-plugin - 1.49.1 Labels: ec2-plugin Priority: Minor Reporter: Parameswaran Jayaraman Jenkins EC2 Plugin fails to launch Windows Slave after upgrading the plugin version from 1.46.1 to 1.49.1. While the Linux agents come up perfectly, the Windows agents fail to come up and fail with the below error. I believe this issue is due to the update of the smbj version as mentioned in the release notes. In order to get my agents working, I had to revert to the previous version of the plugin (1.46.1). Please investigate and advise on the fix. WARNING h.plugins.ec2.win.WinConnection#ping: Failed to verify connectivity to Windows slave java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) at java.net.SocketInputStream.read(SocketInputStream.java:141) at com.hierynomus.smbj.transport.tcp.direct.DirectTcpPacketReader.readFully(DirectTcpPacketReader.java:70) at com.hierynomus.smbj.transport.tcp.direct.DirectTcpPacketReader.readTcpHeader(DirectTcpPacketReader.java:59) at com.hierynomus.smbj.transport.tcp.direct.DirectTcpPacketReader.doRead(DirectTcpPacketReader.java:48) Caused: com.hierynomus.protocol.transport.TransportException at com.hierynomus.smbj.transport.tcp.direct.DirectTcpPacketReader.doRead(DirectTcpPacketReader.java:53) at com.hierynomus.smbj.transport.Pa
[JIRA] (JENKINS-61006) AWS EC2 plugin failing to connect to Windows Slave
Title: Message Title
PJ updated an issue
Jenkins / JENKINS-61006
AWS EC2 plugin failing to connect to Windows Slave
Change By:
PJ
Jenkins EC2 Plugin fails to launch Windows Slave after upgrading the plugin version from 1.46.1 to 1.49.1. While the Linux agents come up perfectly, the Windows agents fail to come up and fail with the below error. I believe this issue is due to the update of the smbj version as mentioned in the release notes. In order to get my agents working, I had to revert to the previous version of the plugin (1.46.1). Please investigate and advise on the fix. {code:java} WARNING h.plugins.ec2.win.WinConnection#ping: Failed to verify connectivity to Windows slave java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) at java.net.SocketInputStream.read(SocketInputStream.java:141) at com.hierynomus.smbj.transport.tcp.direct.DirectTcpPacketReader.readFully(DirectTcpPacketReader.java:70) at com.hierynomus.smbj.transport.tcp.direct.DirectTcpPacketReader.readTcpHeader(DirectTcpPacketReader.java:59) at com.hierynomus.smbj.transport.tcp.direct.DirectTcpPacketReader.doRead(DirectTcpPacketReader.java:48) Caused: com.hierynomus.protocol.transport.TransportException at com.hierynomus.smbj.transport.tcp.direct.DirectTcpPacketReader.doRead(DirectTcpPacketReader.java:53) at com.hierynomus.smbj.transport.PacketReader.readPacket(PacketReader.java:70) at com.hierynomus.smbj.transport.PacketReader.run(PacketReader.java:48) Caused: com.hierynomus.smbj.common.SMBRuntimeException at com.hierynomus.smbj.common.SMBRuntimeException$1.wrap(SMBRuntimeException.java:27) at com.hierynomus.smbj.common.SMBRuntimeException$1.wrap(SMBRuntimeException.java:21) at com.hierynomus.protocol.commons.concurrent.Promise.deliverError(Promise.java:95) at com.hierynomus.smbj.connection.OutstandingRequests.handleError(OutstandingRequests.java:88) at com.hierynomus.smbj.connection.Connection.handleError(Connection.java:465) at com.hierynomus.smbj.transport.PacketReader.run(PacketReader.java:54) Caused: java.util.concurrent.ExecutionException at com.hierynomus.protocol.commons.concurrent.PromiseBackedFuture.get(PromiseBackedFuture.java:60) at com.hierynomus.protocol.commons.concurrent.CancellableFuture.get(CancellableFuture.java:84) at com.hierynomus.protocol.commons.concurrent.Futures.get(Futures.java:38) Caused: com.hierynomus.protocol.transport.TransportException at com.hierynomus.protocol.transport.TransportException$1.wrap(TransportException.java:29) at com.hierynomus.protocol.transport.TransportException$1.wrap(TransportException.java:23) at com.hierynomus.protocol.commons.concurrent.Futures.get(Futures.java:43) at com.hierynomus.smbj.connection.Connection.sendAndReceive(Connection.java:305) at com.hierynomus.smbj.connection.Connection.initiateSessionSetup(Connection.java:244) at com.hierynomus.smbj.connection.Connection.authenticate(Connection.java:181) Caused: com.hierynomus.smbj.common.SMBRuntimeException at co
