Branch: refs/heads/master
Home: https://github.com/jenkinsci/remote-jobs-view
Commit: 64807ce463de50dad720795579a3dc384591c2bb
https://github.com/jenkinsci/remote-jobs-view/commit/64807ce463de50dad720795579a3dc384591c2bb
Author: Swamy_M_S <[email protected]>
Date: 2023-08-05 (Sat, 05 Aug 2023)
Changed paths:
R .github/dependabot.yml
A .github/workflows/cd.yaml
R .github/workflows/cd.yml
R .mvn/extensions.xml
M .mvn/maven.config
M pom.xml
Log Message:
-----------
Security Bug Fix
Commit: 5b08cc2115affe1ee15d2986ea8741e674b1e9fc
https://github.com/jenkinsci/remote-jobs-view/commit/5b08cc2115affe1ee15d2986ea8741e674b1e9fc
Author: Swamy M S <[email protected]>
Date: 2023-08-05 (Sat, 05 Aug 2023)
Changed paths:
R .github/dependabot.yml
A .github/workflows/cd.yaml
R .github/workflows/cd.yml
R .mvn/extensions.xml
M .mvn/maven.config
M pom.xml
Log Message:
-----------
update CD flow (#8)
<!-- 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/3d5ea2599fec...5b08cc2115af
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/remote-jobs-view/push/refs/heads/master/3d5ea2-5b08cc%40github.com.