Re: GSoC 2019 - Remoting project ideas
Hi, After checking through Oleg's suggestions, I am thinking we can move it forward with 2 projects this year: - Project 1: Update Remoting over Kafka to support K8s - Current demo setup is using Docker compose, and I think K8s is more popular nowadays, maybe we can somehow integrate this. And if this setup is done, maybe auto provisioning of Kafka cluster can be more convinient? - Project 2: Integrating Remoting messaging with Prometheus monitoring - By this you mean we will do this for JNLP agents monitoring? To replace the traditional monitoring we are having in Jenkins master? I suggest we can rename it to "Integrating remoting with monitoring tools", because there are many monitoring tools out there (not only Prometheus), and we let the student choose one? We can also make the plugin generic such that user can integrate Jenkins with any monitoring system of their choice (but Im not sure it's doable). I can be the mentor for Project 1 (because I understand about remoting over Kafka), and can help for project 2 with other mentors (I think we need to have someone with deep understanding of remoting for this project). On Fri, Jan 4, 2019 at 8:44 AM Pham Vu Tuan wrote: > Hi, I am happy to help as a mentor for GSoC this year. I will try to check > the details and get back to you about my ideas asap. I will join the GSoC > weekly meeting from next week so that we can discuss about this topic. > (Sorry for not attending the meeting last month, I was a bit busy + > holiday period). > > On Fri, Jan 4, 2019 at 7:33 AM Jeff Thompson > wrote: > >> These sound like good projects. It would be nice to get a GSoC project >> going in Remoting. Last year’s project was a very good, productive one. >> >> At this time I don’t know that I can commit to being a primary mentor but >> I could help out some. >> >> Jeff Thompson >> >> On Jan 3, 2019, at 4:00 AM, Oleg Nenashev wrote: >> >> I have also added the Jenkins Developers mailing list to Cc so that we >> can get more inputs and ideas >> >> On Thu, Jan 3, 2019 at 11:20 AM Oleg Nenashev >> wrote: >> >>> Hi all, >>> >>> Just to follow-up on the Remoting topic, it would be great to have a >>> GSoC project idea for Remoting this year. You were interested in mentoring >>> a project in the area, so it would be great to get your feedback. >>> >>> One of the ideas I have is to continue improving Remoting over Kafka to >>> improve Remoting behavior in Docker and K8s environments. Examples: >>> >>>- Cloud API implementation for Kafka agents >>>- Simplify JAR cache warmup while building agent images >>>- Update Remoting over Kafka to improve support of Kubernetes there >>> - Descriptions >>> - Connector logic using credentials from K8s >>> - Automatic provisioning of the Kafka cluster from the plugin >>> - etc. >>>- Create reference K8s specks and Helm charts for Remoting over >>>Kafka system >>>- Integrate Remoting messaging with Prometheus monitoring >>>- ... >>> >>> WDYT? If you are interested in such idea, we could create a project idea >>> draft together. I might not be available to be a mentor this year, but I >>> will be happy to be a technical advisor in this project. >>> >>> Best regards, >>> Oleg >>> >>> >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BAh5bq16W96xRf-Jpu7bXWj7MBtZ8g125Ug4qfgZfEfcevcng%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: GSoC 2019 - Remoting project ideas
Hi, I am happy to help as a mentor for GSoC this year. I will try to check the details and get back to you about my ideas asap. I will join the GSoC weekly meeting from next week so that we can discuss about this topic. (Sorry for not attending the meeting last month, I was a bit busy + holiday period). On Fri, Jan 4, 2019 at 7:33 AM Jeff Thompson wrote: > These sound like good projects. It would be nice to get a GSoC project > going in Remoting. Last year’s project was a very good, productive one. > > At this time I don’t know that I can commit to being a primary mentor but > I could help out some. > > Jeff Thompson > > On Jan 3, 2019, at 4:00 AM, Oleg Nenashev wrote: > > I have also added the Jenkins Developers mailing list to Cc so that we can > get more inputs and ideas > > On Thu, Jan 3, 2019 at 11:20 AM Oleg Nenashev > wrote: > >> Hi all, >> >> Just to follow-up on the Remoting topic, it would be great to have a GSoC >> project idea for Remoting this year. You were interested in mentoring a >> project in the area, so it would be great to get your feedback. >> >> One of the ideas I have is to continue improving Remoting over Kafka to >> improve Remoting behavior in Docker and K8s environments. Examples: >> >>- Cloud API implementation for Kafka agents >>- Simplify JAR cache warmup while building agent images >>- Update Remoting over Kafka to improve support of Kubernetes there >> - Descriptions >> - Connector logic using credentials from K8s >> - Automatic provisioning of the Kafka cluster from the plugin >> - etc. >>- Create reference K8s specks and Helm charts for Remoting over Kafka >>system >>- Integrate Remoting messaging with Prometheus monitoring >>- ... >> >> WDYT? If you are interested in such idea, we could create a project idea >> draft together. I might not be available to be a mentor this year, but I >> will be happy to be a technical advisor in this project. >> >> Best regards, >> Oleg >> >> >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BAh5bp0Zy3P%3DNKW9hG50A4dVF98MKyBwTOxvM0%2BuRu7j%3DznWQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins participation in Outreachy
Hi, I am interested to join as a mentor. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8c6aff99-25a8-4509-81fb-a071ce56f3dd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[GSoC 2018] Jenkins Remoting over Message Bus/Queue Introduction
Hi all, My name is Vu Tuan, and I am participating in Jenkins Google Summer of Code this year as a student. My project is Jenkins Remoting over Message Bus/Queue <https://jenkins.io/projects/gsoc/2018/remoting-over-message-bus/> . Some background about this project: - Current versions of Jenkins Remoting are based on the TCP protocol. If it fails, the agent connection and the build fails as well. There are also issues with traffic prioritization and multi-agent communications, which impact Jenkins stability and scalability. - This project aims an update of Remoting and Jenkins in order to add support of a popular message queue/bus technology (RabbitMQ or Kafka) as a fault-tolerant communication layer in Jenkins. Currently we are in the first phase of the project and I am going to implement a PoC in this first phase. The messaging technology used is Apache Kafka, and the deliverable for the first phase will be in Docker compose with multiple services and components involved. If you are interested, we have a gitter <https://gitter.im/jenkinsci/remoting> chat for this project. The weekly meeting schedule is: - Every Tuesday, 02:00-03:00 PM UTC - Every Friday, 02:00-03:00 PM UTC I am looking forward to contributing to Jenkins community this summer. Best regards, Pham Vu Tuan -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/22237593-3392-4a88-9267-634c8827b50b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [GSoc 2018] [Student Introduction] Jenkins Remoting over Message Bus/Queue
Hi, I put my draft proposal for GSoC here https://docs.google.com/document/d/17vmPvDtMbHT7nTKRlGReFRgOtwVImhgsETLOGPW9Rso/edit?usp=sharing. I would like to receive reviews and comments about my draft proposal before the submission deadline. Thanks, Pham Vu Tuan On Friday, March 9, 2018 at 1:26:37 AM UTC+8, Oleg Nenashev wrote: > > You still have not exposed "-p" option as proposed above. > I kindly recommend to move this prototyping discussion to a separate > thread so it does not pollute the project proposal discussion. > > Thanks in advance, > Oleg > > On Thu, Mar 8, 2018 at 6:22 PM, Pham Vu Tuan > wrote: > >> I resolved the JNLP warning message by passing env variable in Docker run. >> But I still encountered "Connection refused" error although I exposed the >> port 5 in the Dockerized master. >> >> >> <https://lh3.googleusercontent.com/-uWdhI7tOugo/WqFwLaBUgRI/Bqw/VTxe3Hm-Hvo4wVSLH8Yxkv-h9KxkxnYmACLcBGAs/s1600/Screen%2BShot%2B2018-03-09%2Bat%2B1.16.20%2BAM.png> >> >> >> <https://lh3.googleusercontent.com/-0UATDrdXx6M/WqFwP3F2xVI/Bq0/bBnAmaEg4yQnqpvW5sCpPcigLHqTn7abACLcBGAs/s1600/Screen%2BShot%2B2018-03-09%2Bat%2B1.16.57%2BAM.png> >> My command to start the agent is: "docker run -e >> JNLP_PROTOCOL_OPTS='-Dorg.jenkinsci.remoting.engine.JnlpProtocol3.disabled=false' >> >> jenkins/jnlp-slave -url http://localhost:8080 abcd test-node". >> Any ideas on this? >> >> On Friday, March 9, 2018 at 12:13:56 AM UTC+8, Oleg Nenashev wrote: >>> >>> Hi Pham, >>> >>> In order to connect an agent to the Dockerized master, you need to >>> expose the port for the agent (make the Agent port fixed in security >>> settings + use "-p" option to expose it). >>> I am not sure how BlueOcean image is configured, the standard Jenkins >>> Docker image has it documented here: >>> https://github.com/jenkinsci/docker#usage >>> >>> Hopefully it helps, >>> Oleg >>> >>> P.S: I'd guess it's another case of WEBSITE-474 >>> <https://issues.jenkins-ci.org/browse/WEBSITE-474>, right? >>> >>> >>> >>> On Thu, Mar 8, 2018 at 4:59 PM, Pham Vu Tuan >>> wrote: >>> >>>> Hello, >>>> >>>> I am trying to setup the master and agent in my local machine. Server >>>> setup is fine, I used https://hub.docker.com/r/jenkinsci/blueocean/. >>>> But when I tried to connect an agent to it using >>>> https://hub.docker.com/r/jenkins/jnlp-slave/ by this command "docker >>>> run jenkins/jnlp-slave -url http://localhost:8080 abcd test-node" , I >>>> encountered some problems: >>>> >>>> - Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS >>>> to alter the behavior => Athough I set the env variable in the docker >>>> container for the server, I still encountered this warning message, am I >>>> missing to set it somewhere? >>>> - Not sure if this is related to the above issue, then I cannot connect >>>> the agent to server >>>> >>>>> SEVERE: Failed to connect to >>>>> http://localhost:8080/tcpSlaveAgentListener/: Connection refused >>>>> (Connection refused) >>>>> java.io.IOException: Failed to connect to >>>>> http://localhost:8080/tcpSlaveAgentListener/: Connection refused >>>>> (Connection refused) >>>>> at >>>>> org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:199) >>>>> at hudson.remoting.Engine.innerRun(Engine.java:518) >>>>> at hudson.remoting.Engine.run(Engine.java:469) >>>> >>>> Could someone help me with this setup issue? >>>> >>>> Regards, >>>> Pham Vu Tuan >>>> >>>> On Monday, March 5, 2018 at 12:31:29 AM UTC+8, Oleg Nenashev wrote: >>>>> >>>>> Hi all, >>>>> >>>>> Since we have several students interested in this project, I propose >>>>> to spend some time at office hours on Wednesday in order to discuss it. >>>>> >>>>> From what I see, everybody in this thread can attend during the >>>>> APAC/Europe timeslot, right? If yes, let's just talk about the project >>>>> there. >>>>> >>>>> BR, Oleg >>>>> >>>>> On Sunda
Re: [GSoc 2018] [Student Introduction] Jenkins Remoting over Message Bus/Queue
I resolved the JNLP warning message by passing env variable in Docker run. But I still encountered "Connection refused" error although I exposed the port 5 in the Dockerized master. <https://lh3.googleusercontent.com/-uWdhI7tOugo/WqFwLaBUgRI/Bqw/VTxe3Hm-Hvo4wVSLH8Yxkv-h9KxkxnYmACLcBGAs/s1600/Screen%2BShot%2B2018-03-09%2Bat%2B1.16.20%2BAM.png> <https://lh3.googleusercontent.com/-0UATDrdXx6M/WqFwP3F2xVI/Bq0/bBnAmaEg4yQnqpvW5sCpPcigLHqTn7abACLcBGAs/s1600/Screen%2BShot%2B2018-03-09%2Bat%2B1.16.57%2BAM.png> My command to start the agent is: "docker run -e JNLP_PROTOCOL_OPTS='-Dorg.jenkinsci.remoting.engine.JnlpProtocol3.disabled=false' jenkins/jnlp-slave -url http://localhost:8080 abcd test-node". Any ideas on this? On Friday, March 9, 2018 at 12:13:56 AM UTC+8, Oleg Nenashev wrote: > > Hi Pham, > > In order to connect an agent to the Dockerized master, you need to expose > the port for the agent (make the Agent port fixed in security settings + > use "-p" option to expose it). > I am not sure how BlueOcean image is configured, the standard Jenkins > Docker image has it documented here: > https://github.com/jenkinsci/docker#usage > > Hopefully it helps, > Oleg > > P.S: I'd guess it's another case of WEBSITE-474 > <https://issues.jenkins-ci.org/browse/WEBSITE-474>, right? > > > > On Thu, Mar 8, 2018 at 4:59 PM, Pham Vu Tuan > wrote: > >> Hello, >> >> I am trying to setup the master and agent in my local machine. Server >> setup is fine, I used https://hub.docker.com/r/jenkinsci/blueocean/. But >> when I tried to connect an agent to it using >> https://hub.docker.com/r/jenkins/jnlp-slave/ by this command "docker run >> jenkins/jnlp-slave -url http://localhost:8080 abcd test-node" , I >> encountered some problems: >> >> - Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS >> to alter the behavior => Athough I set the env variable in the docker >> container for the server, I still encountered this warning message, am I >> missing to set it somewhere? >> - Not sure if this is related to the above issue, then I cannot connect >> the agent to server >> >>> SEVERE: Failed to connect to >>> http://localhost:8080/tcpSlaveAgentListener/: Connection refused >>> (Connection refused) >>> java.io.IOException: Failed to connect to >>> http://localhost:8080/tcpSlaveAgentListener/: Connection refused >>> (Connection refused) >>> at >>> org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:199) >>> at hudson.remoting.Engine.innerRun(Engine.java:518) >>> at hudson.remoting.Engine.run(Engine.java:469) >> >> Could someone help me with this setup issue? >> >> Regards, >> Pham Vu Tuan >> >> On Monday, March 5, 2018 at 12:31:29 AM UTC+8, Oleg Nenashev wrote: >>> >>> Hi all, >>> >>> Since we have several students interested in this project, I propose to >>> spend some time at office hours on Wednesday in order to discuss it. >>> >>> From what I see, everybody in this thread can attend during the >>> APAC/Europe timeslot, right? If yes, let's just talk about the project >>> there. >>> >>> BR, Oleg >>> >>> On Sunday, March 4, 2018 at 7:48:47 AM UTC+1, ajm...@g.rit.edu wrote: >>>> >>>> I am Amit Magar a graduate student pursuing masters in Computer Science >>>> from Rochester Institute of Technology. I am specializing in Computer >>>> Networks and Artificial Intelligence. I have 8 years formal education in >>>> Computer Science. >>>> >>>> I have 3 years of professional works experience at Accenture. >>>> Currently, I am working at Genex Services, Pensylvania as Intern in >>>> Advanced Analytics. >>>> >>>> In my work experience I worked on Integration of heterogeneous >>>> services, packaged and legacy applications (more than 20 applications) >>>> using Enterprise Service Bus, Web Services, and JMS queue. Our Continuous >>>> Integration stack (DevOps) included Jenkins, GIT, Chef Server and Nexus so >>>> I have good knowledge of these Tools. I am well versed in Java, >>>> SoftwarPython, XML and Docker technologies too. I have closely worked on >>>> each phase of Software development life cycle. >>>> >>>> I always wanted to do open source contribution, my long-term goal is >>>> to become a co
Re: [GSoc 2018] [Student Introduction] Jenkins Remoting over Message Bus/Queue
Hello, I am trying to setup the master and agent in my local machine. Server setup is fine, I used https://hub.docker.com/r/jenkinsci/blueocean/. But when I tried to connect an agent to it using https://hub.docker.com/r/jenkins/jnlp-slave/ by this command "docker run jenkins/jnlp-slave -url http://localhost:8080 abcd test-node" , I encountered some problems: - Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior => Athough I set the env variable in the docker container for the server, I still encountered this warning message, am I missing to set it somewhere? - Not sure if this is related to the above issue, then I cannot connect the agent to server > SEVERE: Failed to connect to http://localhost:8080/tcpSlaveAgentListener/: > Connection refused (Connection refused) > java.io.IOException: Failed to connect to > http://localhost:8080/tcpSlaveAgentListener/: Connection refused > (Connection refused) > at > org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:199) > at hudson.remoting.Engine.innerRun(Engine.java:518) > at hudson.remoting.Engine.run(Engine.java:469) Could someone help me with this setup issue? Regards, Pham Vu Tuan On Monday, March 5, 2018 at 12:31:29 AM UTC+8, Oleg Nenashev wrote: > > Hi all, > > Since we have several students interested in this project, I propose to > spend some time at office hours on Wednesday in order to discuss it. > > From what I see, everybody in this thread can attend during the > APAC/Europe timeslot, right? If yes, let's just talk about the project > there. > > BR, Oleg > > On Sunday, March 4, 2018 at 7:48:47 AM UTC+1, ajm...@g.rit.edu wrote: >> >> I am Amit Magar a graduate student pursuing masters in Computer Science >> from Rochester Institute of Technology. I am specializing in Computer >> Networks and Artificial Intelligence. I have 8 years formal education in >> Computer Science. >> >> I have 3 years of professional works experience at Accenture. Currently, >> I am working at Genex Services, Pensylvania as Intern in Advanced Analytics. >> >> In my work experience I worked on Integration of heterogeneous services, >> packaged and legacy applications (more than 20 applications) using >> Enterprise Service Bus, Web Services, and JMS queue. Our Continuous >> Integration stack (DevOps) included Jenkins, GIT, Chef Server and Nexus so >> I have good knowledge of these Tools. I am well versed in Java, >> SoftwarPython, XML and Docker technologies too. I have closely worked on >> each phase of Software development life cycle. >> >> I always wanted to do open source contribution, my long-term goal is to >> become a contributor(Github) open source code. I think GSoC >> is good platform to start open source contribution where I will mentorship >> from experience open source contributor and will get chance interact with >> open source community which will be helpful for future contribution in open >> source. >> >> Jenkins caught my attention because I have used Jenkins before for >> Continuous Integration.I have gone through the detailed information of >> "Jenkins Remoting over Message Bus/Queue" project. I am particularly >> interested in "Jenkins Remoting over Message Bus/Queue" Because my previous >> work experience in Java, JMS queues will be helpful here and I will be able >> actively to contribute from day 1. >> >> You can find more information about me on below links, >> Linkedin: https://www.linkedin.com/in/amit-magar >> Github: https://github.com/AmitJMagar >> >> I would like to request mentors to give me some guidance here as well as >> in office hour to formulate a good proposal. >> >> Thanks and Regard, >> Amit Magar >> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9bc7adfe-b171-4767-822a-2c8ee3a6ac3e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [GSoc 2018] [Student Introduction] Jenkins Remoting over Message Bus/Queue
Hi, Thank you Oleg and Jesse for providing me useful details. I will try to get started and get back to you soon with my ideas. Regards, Pham Vu Tuan On Wednesday, February 14, 2018 at 4:23:13 PM UTC+7, Oleg Nenashev wrote: > > Thanks for the interest! > I will try to provide a detailed writeup about the project. > > Generally, the idea is to replace current communication layer by a pure > message bus implementation. Below you can find some things from the top of > my head: > >- All communications between master and agent happen over the message >bus > - Jenkins agents and masters can connect to a message bus. > - The topology is TBD, it may be either embedded message bus > (Jenkins master as a host) or an external service. The latter one is > preferable IMHO > - Jenkins agents query connection metadata over the bus. > - Current implementations query metadata from an HTTP/HTTPs > endpoint before connection. Getting rid of that would help > - Command transport for message bus is implemented (as Jesse > mentioned). > - It would include transparent support of command invocation, RMI, > classloading and data streaming > - We utilize message bus features to make connections over >Remoting more stable > - Fault tolerance > - The messaging layer survives short network outages > - Nice2Have: We use multiple message bus hosts so they do not > become a bottleneck > - Traffic/Request prioritization > - Currently we have an issue with logging/file transfer > messaging overloading the channel and blocking system commands. We > could > use message bus features to prevent that > - TBD: More efficient data streaming > - Implementation: > - Executable for the agent side > - Jenkins plugin, which provides the master-side logic and serves > the agent executable > - We have a reference implementation for demos >- E.g: a set of Docker images, which bring up a Jenkins cluster with a > master and several agents (e.g. with Kubernetes or Docker Compose) > - It may be somehow aligned with other ongoing activities (e.g. the > demo could be built on the top of EverGreen distro) > <https://github.com/jenkinsci/jep/tree/master/jep/300> > - TBD: a PoC for Master <=> Master communication > - In Jenkins project we have some master => master plugins like > Parameterized Remote Trigger. We could try to use a message bus to > deliver > messages between masters >- TBD: Streaming agent logs to a log storage over the message bus >- TBD: Remoting autoupdate over message bus > - Message bust engine could be a bootstrap library, which loads > Remoting library from the master after establishing the connection. > - In Jenkins project we often see issues with update Remoting > versions on the agent side. Although it would be great to solve the > issue > on the Remoting side, usage of such bootstrap could be a quick win > > Best regards, > Oleg > > вторник, 13 февраля 2018 г., 16:53:00 UTC+1 пользователь Jesse Glick > написал: >> >> On Tue, Feb 13, 2018 at 9:49 AM, Pham Vu Tuan >> wrote: >> > I am quite interested in project >> > "Jenkins Remoting over Message Bus/Queue" and want to understand more >> about >> > the project. >> >> Probably Oleg will give you some depth but to get started >> understanding the background, look at subclasses of: >> >> >> https://github.com/jenkinsci/remoting/blob/master/src/main/java/hudson/remoting/CommandTransport.java >> >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/394e00b8-5516-4e92-90c0-2fd5e01ab5ae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[GSoc 2018] [Student Introduction] Jenkins Remoting over Message Bus/Queue
Hi, My name is Pham Vu Tuan. I am currently studying my final year in Computer Science at Nanyang Technological University from Singapore. I am going to graduate in May and looking to do some coding activities to get busy this summer. I have some experiences as a back-end developer through my interships before. My familiar programming languages are Java, Python and Go. I am familiar with Jenkins as a CI server in my work, I hope I can contribute some to Jenkins. Currenty, I am quite interested in project "Jenkins Remoting over Message Bus/Queue" and want to understand more about the project. I think I can learn some interesting things by doing this project. I am a user of RabbitMQ in my recent company, so I have a basic knowledge about this queue messaging technology. Currently, I haven't had any idea/proposal yet, hope it will come along the way with the support of our Jenkins community. I can be found on LinkedIn: https://www.linkedin.com/in/phamvutuan/ and Github: https://github.com/pvtuan10. I am looking forward to having some contributions to Jenkins community. Regards, Pham Vu Tuan -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ec445ea4-0567-4e68-b7ad-274ceea24956%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
