# Regarding beginner friendly issue **URL:** \ **Category:** Community\ **Created:** [November 22, 2022, 4:25pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677 "2022-11-22T16:25:09Z")\ **Posts on this page:** 20\ **Page:** 3
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [December 8, 2022, 1:28pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/41 "2022-12-08T13:28:19Z")
@pushker001 please review the video included at > **[Add more spotbugs checks](https://www.jenkins.io/doc/developer/tutorial-improve/add-more-spotbugs-checks/)** > > Jenkins – an open source automation server which enables developers around the world to reliably build, test, and deploy their software That video series includes several different cases where pull requests are submitted. ---
**Author:** ![pushker001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pushker001/32/2793_2.png) [@pushker001](https://community.jenkins.io/u/pushker001)\ **Post date:** [December 8, 2022, 1:31pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/42 "2022-12-08T13:31:12Z")
![Screenshot (273)](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/f/ff470f9c9c9681104db08cea871381689546f339.png) See this is showing to me when I try to pull a request ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [December 8, 2022, 1:42pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/43 "2022-12-08T13:42:31Z")
You’re not following the instructions in the document. Please follow the instructions in the document. The instructions say: - Checkout a branch to perform the work ```auto git checkout -b add-spotbugs-checks master ``` - Add or modify the properties in the pom.xml file ```auto Max Low ``` - Create a pull request ```auto git add pom.xml src/spotbugs git commit -m "Increase spotbugs effort and threshold" git push origin --set-upstream add-spotbugs-checks ``` Notice that the output of the command includes the URL, which can be used to open a pull request. Copy that URL in your web browser and submit a pull request. ### Problems I see Your screenshot shows that you’re using a different branch name than is provided in the instructions. Your screenshot hints that your incorrectly named branch also contains no commits beyond the commits that are on the controller branch of the upstream repository. That likely means you didn’t push the commit from your local computer to GitHub. You may also have failed to commit it locally on your computer. ---
**Author:** ![pushker001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pushker001/32/2793_2.png) [@pushker001](https://community.jenkins.io/u/pushker001)\ **Post date:** [December 8, 2022, 1:53pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/44 "2022-12-08T13:53:35Z")
> [@MarkEWaite](#): > > - e > > ```auto > > ``` actually, i am doing all this through the video you have provided not doing from the document ---
**Author:** ![pushker001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pushker001/32/2793_2.png) [@pushker001](https://community.jenkins.io/u/pushker001)\ **Post date:** [December 8, 2022, 4:37pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/45 "2022-12-08T16:37:23Z")
![Screenshot (274)](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/6/61976c6fd208836392b4405865b22fef0e246428.png) please tell me what to do after this I was watching a video that @MarkEWaite share. my interface is different that shown in video. ---
**Author:** ![pushker001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pushker001/32/2793_2.png) [@pushker001](https://community.jenkins.io/u/pushker001)\ **Post date:** [December 8, 2022, 5:22pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/46 "2022-12-08T17:22:45Z")
![Screenshot (275)](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/8/81f694805ac5dc1a528ce3e2de7a403b9b07915e.png) I have created a pull request for what should I do next. ---
**Author:** ![pushker001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pushker001/32/2793_2.png) [@pushker001](https://community.jenkins.io/u/pushker001)\ **Post date:** [December 11, 2022, 12:50pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/47 "2022-12-11T12:50:08Z")
hey @MarkEWaite can you help me with adding contributing guide ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [December 11, 2022, 12:55pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/48 "2022-12-11T12:55:31Z")
@pushker001 you need to follow the instructions on the page of the [“Improve a plugin” tutorial](https://www.jenkins.io/doc/developer/tutorial-improve/add-a-contributing-guide/). Those instructions suggest things that you could consider including in the contributing guide. If you choose to add an item, be sure that you confirm it works (for example, coverage reporting). ---
**Author:** ![pushker001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pushker001/32/2793_2.png) [@pushker001](https://community.jenkins.io/u/pushker001)\ **Post date:** [December 13, 2022, 4:20pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/49 "2022-12-13T16:20:49Z")
![Screenshot (278)](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/4/4c122c85e5945a97f47c47bddef2b06181226c9d.png) In built-in column for running locally should I put the same command? ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [December 13, 2022, 5:00pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/50 "2022-12-13T17:00:44Z")
> [@pushker001](#): > > In built-in column for running locally should I put the same command? Thanks for including that screenshot. That page needs to be updated to include Java 17 and to remind maintainers that Java 11 is the most popular Java version for Jenkins users currently. To run a plugin locally, the command is: `mvn hpi:run` That starts a Jenkins controller with the minimum Jenkins version supported by the plugin and loads the plugin and its dependencies into that controller. Jenkins will be running on port 8080 and can be reached with the URL [http://localhost:8080/jenkins/](http://localhost:8080/jenkins/) If a plugin maintainer wants to use a different Jenkins version, they run the command: `mvn -Djenkins.version=2.375.1 hpi:run` If a plugin maintainer wants to use a different HTTP port, (as in [http://localhost:9090/jenkins](http://localhost:9090/jenkins)) they run the command: `mvn -Dport=9090 hpi:run` If a plugin maintainer wants to allow other computers to access that Jenkins controller while it is running, they run the command: `mvn -Dhost=0.0.0.0 hpi:run` See the [maven hpi plugin documentation site](https://jenkinsci.github.io/maven-hpi-plugin/) for more details. ---
**Author:** ![pushker001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pushker001/32/2793_2.png) [@pushker001](https://community.jenkins.io/u/pushker001)\ **Post date:** [December 13, 2022, 5:28pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/51 "2022-12-13T17:28:44Z")
> [@MarkEWaite](#): > > f a plugin maintainer wants to allow other computers to access that Jenkins controller while it is running, they run the command: > > `mvn -Dhost=0.0.0.0 hpi:run` # Built-on-column-plugin This plugin Adds a column on the jenkins dashboard that shows the actual node the last build was run on. # Why should you contribute You can contribute in many ways, and whatever you choose we’re grateful! Source code contribution is the obvious one but we also need your feedback and if you don’t really want to participate in the implementation directly you may still have great ideas about features we need (or should get rid of). We have our vision for the plugin and we have an experience with maintaining Jenkins instances, but the plugin is not supposed to solve only our problems. Surely we haven’t experienced all of them… That’s why we want to hear from you. Please use GitHub issues if you need to report a bug or request changes/improvements. Whenever you report a problem please provide information about: - Plugin version (Configuration as Code plugin as well any other plugin you suspect your problem to be related to) - Jenkins version - Operating system - Description! ## Run Locally Prerequisites: Java, Maven - Ensure Java 8 or 11 is available. ```auto $ java -version ``` - Ensure Maven is included in the PATH environment variable. ```auto export PATH=$PATH:/path/to/apache-maven-3.8.6/bin ``` - To run a plugin locally, the command is: ```auto mvn hpi:run ``` - That starts a Jenkins controller with the minimum Jenkins version supported by the plugin and loads the plugin and its dependencies into that controller. Jenkins will be running on port 8080 and can be reached with the URL [http://localhost:8080/jenkins/If](http://localhost:8080/jenkins/If) a plugin maintainer wants to use a different Jenkins version, they run the command: ```auto mvn -Djenkins.version=2.375.1 hpi:run ``` - If a plugin maintainer wants to use a different HTTP port, (as in [http://localhost:9090/jenkins](http://localhost:9090/jenkins)) they run the command: ```auto mvn -Dport=9090 hpi:run ``` - If a plugin maintainer wants to allow other computers to access that Jenkins controller while it is running, they run the command: ```auto mvn -Dhost=0.0.0.0 hpi:run ``` is this ok? ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [December 13, 2022, 5:34pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/52 "2022-12-13T17:34:43Z")
That looks good to me. ---
**Author:** ![pushker001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pushker001/32/2793_2.png) [@pushker001](https://community.jenkins.io/u/pushker001)\ **Post date:** [December 14, 2022, 1:38pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/53 "2022-12-14T13:38:33Z")
![Screenshot (279)](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/5/5906c98faf7544f31dc82ea94c7f491ff7279578.png) can you look at this I have created contributing.md file. Is this correct? ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [December 14, 2022, 2:27pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/54 "2022-12-14T14:27:47Z")
> [@pushker001](#): > > can you look at this I have created contributing.md file. Is this correct? Looks reasonable, though it is much more effective for me (and others) to review changes in GitHub pull requests rather than reviewing them in screenshots. No problem if there are flaws or imperfections in the pull request. We learn together and we learn by pull requests. ---
**Author:** ![pushker001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pushker001/32/2793_2.png) [@pushker001](https://community.jenkins.io/u/pushker001)\ **Post date:** [December 15, 2022, 12:55pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/55 "2022-12-15T12:55:56Z")
hey @MarkEWaite can you provide me with more plugins so I can contribute ---
**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\ **Post date:** [December 15, 2022, 1:09pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/56 "2022-12-15T13:09:40Z")
I think this one needs some TLC: [GitHub - jenkinsci/promoted-builds-plugin: Jenkins Promoted Builds Plugin](https://github.com/jenkinsci/promoted-builds-plugin) ---
**Author:** ![pushker001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pushker001/32/2793_2.png) [@pushker001](https://community.jenkins.io/u/pushker001)\ **Post date:** [December 15, 2022, 4:56pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/57 "2022-12-15T16:56:45Z")
![Screenshot (280)](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/a/abcc9de88649aeb10a5ed83f6efdec03f062fca3.png) what should I need to do in it should I add spot bug checks in it? ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [December 15, 2022, 5:23pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/58 "2022-12-15T17:23:39Z")
I think that promoted builds plugin may be a little too high visibility and high complication than you are ready to attempt @pushker001 . If you’re willing to try a few other plugins, they would give you a better experience with lower risk and as much learning as you’ll get from promoted builds. Try the following plugins instead: - Discard old builds plugin - [GitHub - jenkinsci/discard-old-build-plugin: More build discard settings for freestyle jobs](https://github.com/jenkinsci/discard-old-build-plugin/) - Skip certificate check plugin - [GitHub - jenkinsci/skip-certificate-check-plugin: Bypass HTTPS certificate checks](https://github.com/jenkinsci/skip-certificate-check-plugin) I just completed a first step on those two plugins to perform minimal modernization so that new versions could be released. They both would benefit from: - More spotbugs checks - Add a contributing guide They would also benefit from additional automated tests if you would like to learn more about writing automated tests with JUnit. ---
**Author:** ![pushker001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pushker001/32/2793_2.png) [@pushker001](https://community.jenkins.io/u/pushker001)\ **Post date:** [December 17, 2022, 12:59pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/59 "2022-12-17T12:59:24Z")
![Screenshot (281)](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/a/a7542019b2895ac3828a5fd2a5ce1b457ddec208.png) What is the problem in this build failure showing after mvn clean verify ---
**Author:** ![pushker001](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/pushker001/32/2793_2.png) [@pushker001](https://community.jenkins.io/u/pushker001)\ **Post date:** [December 17, 2022, 1:08pm UTC](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677/60 "2022-12-17T13:08:27Z")
yes sure I would love to learn about writing automated test [Previous page](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677.md?page=2) [Next page](https://community.jenkins.io/t/regarding-beginner-friendly-issue/4677.md?page=4)