Branch: refs/heads/master Home: https://github.com/jenkinsci/remote-jobs-view Commit: 41e4b1599845203950e1d4ee1f0e3e9112e8224b https://github.com/jenkinsci/remote-jobs-view/commit/41e4b1599845203950e1d4ee1f0e3e9112e8224b Author: Swamy M S <57250315+swamy-...@users.noreply.github.com> Date: 2024-02-16 (Fri, 16 Feb 2024)
Changed paths: A src/main/resources/com/sap/jenkinsci/plugin/remote_view/RemoteJobsSection Log Message: ----------- Create RemoteJobsSection Signed-off-by: Swamy M S <57250315+swamy-...@users.noreply.github.com> Commit: e1364faa4110833acf076b5f80ee74615a893477 https://github.com/jenkinsci/remote-jobs-view/commit/e1364faa4110833acf076b5f80ee74615a893477 Author: Swamy M S <57250315+swamy-...@users.noreply.github.com> Date: 2024-02-16 (Fri, 16 Feb 2024) Changed paths: A src/main/resources/com/sap/jenkinsci/plugin/remote_view/RemoteJobsSection Log Message: ----------- Create RemoteJobsSection (#17) <!-- Please describe your pull request here. --> ### Testing done <!-- Comment: Provide a clear description of how this change was tested. At minimum this should include proof that a computer has executed the changed lines. Ideally this should include an automated test or an explanation as to why this change has no tests. Note that automated test coverage is less than complete, so a successful PR build does not necessarily imply that a computer has executed the changed lines. If automated test coverage does not exist for the lines you are changing, you must describe the scenario(s) in which you manually tested the change. For frontend changes, include screenshots of the relevant page(s) before and after the change. For refactoring and code cleanup changes, exercise the code before and after the change and verify the behavior remains the same. --> ```[tasklist] ### Submitter checklist - [ ] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch! - [ ] Ensure that the pull request title represents the desired changelog entry - [ ] Please describe what you did - [ ] Link to relevant issues in GitHub or Jira - [ ] Link to relevant pull requests, esp. upstream and downstream changes - [ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue ``` <!-- Put an `x` into the [ ] to show you have filled the information. The template comes from https://github.com/jenkinsci/.github/blob/master/.github/pull_request_template.md You can override it by creating .github/pull_request_template.md in your own repository --> Compare: https://github.com/jenkinsci/remote-jobs-view/compare/389fb8cc1ca3...e1364faa4110 -- You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/remote-jobs-view/push/refs/heads/master/389fb8-e1364f%40github.com.