Chat for people who just starting contributing to Jenkins or want to do so. https://jenkins.io/participate/
Hi, just a little question : I've updated the index.jelly of the conventional-commit-plugin (https://github.com/jenkinsci/conventional-commits-plugin/blob/main/src/main/resources/index.jelly) but the description in the search result of the plugins.jenkins.io page is not updated. Is I missed something ?
5 replies
Stéphane Philippart: I'd have to check the code but I believe that comes from pom.xml, the description field?
Also, this channel is for people wanting to contribute to jenkins, you'll get far more support in the main jenkinsci/jenkins channel
Doc is at https://docs.google.com/document/d/1PKYIpPlRVGsBqrz0Ob1Cv3cefOZ5j2xtGZdWs27kLuw/edit#heading=h.hvd0nm6pz5o4 . We're still working to convert it into a tutorial on www.jenkins.io. Video series that covers many of the topics begins at https://youtu.be/Fev8KfFsPZE . Links to the second and third sessions of that video series are available in the description of the video. Fourth session will be next week
For https://github.com/orgs/jenkinsci/teams/oracle-cloud-infrastructure-compute-plugin-developers/members, I want to invite sindhusri16 and pcbajpai
@chhaosh: okay bot has added them to the repo, i'm checking the code to see if that invites them to the org too
@chhaosh: can you confirm they were invited to the org not just the repo?
Thanks a lot for your help @halkeye:g4v.dev
question around jenkins-ec2 plugin. I see the the image type available for launch is a drop down list. However, not all image type are available in the list. For ex. dl1 type is not listed. Is there way to specify the required image type?
https://github.com/jenkinsci/ec2-plugin
https://github.com/jenkinsci/ec2-plugin
@sg3629: this channel is for people wanting to contribute to jenkins. For general usage help I recommend jenkinsci/jenkins channel, or community.jenkins.io (also I don't know)
One of them to commit, and one of them will assist in release process.
Okay for now leave the repo name and GitHub ids and @timja or myself will take care of it (I'm going to bed though)
@sindhusri16
For https://github.com/orgs/jenkinsci/teams/oracle-cloud-infrastructure-compute-plugin-developers/members, these are the github ids of the members I'd like to invite:
dsavithr and jayarajg123
The repo is https://github.com/jenkinsci/oracle-cloud-infrastructure-compute-plugin
dsavithr and jayarajg123
The repo is https://github.com/jenkinsci/oracle-cloud-infrastructure-compute-plugin
@sindhusri16 ^^
I am new to this Jenkins world and software development, I am tryin to start a build, for deployment to salesforce from Jenkins, I installed a custom tool plugin. For that, I am trying to add a custom tool: gobal tool configuration, add custom tool and fill out the details "name", "installation directory" etc, but I don't see "installation directory" field. I wanted to enter the "salesforce CLI path". I hope this makes sense.
@CodeAccount1: this channel is for working on jenkins project itself (or plugins). Not for asking for help. For that I recommend the main jenkinsci/jenkins gitter channel, or community.jenkins.io
that being said, the tools pipeline directive will extract your tools on your agent, and will return a path for you to use, so you don't need to add the path to it. The example pipeline shows how its used with maven
For does who want to deploy latest Jenkins with Cloud Agent in a kubernetes cluster can now use our internal official way how to deploy Jenkins. Enjoy.
https://github.com/IssTech/jenkins-install
https://github.com/IssTech/jenkins-install
You need to create a pull request (from your forked repository) to get your changes integrated. Or are you requesting to take ownership of that plugin?
BTW: we are not only guys.
Hi there ! I'm working on a plugin and using the
mvn hpi:run command to run/debug it. I was wondering, this is spawning me a single instance jenkins, is there a way to spawn nodes as well ?
or should I just spawn agents with docker and connect them to my dev instance ?
No, this is not possible. This is one of the reasons that I am using a "real" Jenkins instance to debug my plugins. I am using a docker based installation: https://github.com/uhafner/warnings-ng-plugin-devenv
In this installation I have a debug port open for the agents and for the controller.
but I guess you're loosing the debugger capabilities ?
oh no, I'm wrong (reading your documentation)