profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/timja/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Tim Jacomb timja @KainosSoftwareLtd UK Software engineer and development best practices advocate.

hub4j/github-api 791

Java API for GitHub

jenkinsci/acceptance-test-harness 111

Acceptance tests cases for Jenkins and its plug-ins based on selenium and docker.

jenkinsci/azure-ad-plugin 22

Authentication and Authorization with Azure AD

jenkinsci/azure-container-agents-plugin 16

Azure Container Agents Plugin for Jenkins

jenkinsci/azure-artifact-manager-plugin 3

Jenkins Azure artifact manager plugin

jenkinsci/platformlabeler-plugin 3

Jenkins Platform Labeler plugin

pull request commentjenkinsci/junit-plugin

Upgrade trends and detail views to Bootstrap 5

Everything in this plugin is inherited, probably from when it was split from core.

I’ll try take a peek at this soon and see if I can find a way forward

uhafner

comment created time in 11 minutes

pull request commentjenkinsci/configuration-as-code-plugin

feat: Allow reloading configuration with Overall/Manage permission

But since one can only set a single permission there, either there's a way to create a composite permission

The work around is to make that link available to Overall/Read which is Jenkins.READ in the code.

quilicicf

comment created time in 2 hours

PR closed jenkinsci/junit-plugin

Update TestResult.java

<!-- Please describe your pull request here. -->

  • [ ] 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 -->

+2 -2

1 comment

1 changed file

mehuldmehta

pr closed time in 2 hours

pull request commentjenkinsci/junit-plugin

[JENKINS-34217] add option to disable historical statistics gathering…

Ok. thanks.

As I said before, I've a huge number of junit tests. Moreover, stdout/stderr of such tests can be huge too...

Therefore, I can't switch to a database if the policy is to keep results forever.

It now deletes them when the job or build is deleted https://github.com/jenkinsci/junit-sql-storage-plugin/releases/tag/99.v79279ea1504d

XavierRaynaud

comment created time in 2 hours

push eventjenkinsci/configuration-as-code-plugin

dependabot[bot]

commit sha 62b81d7ac472ceb90be347a8ed8d20ce96e55691

Bump bouncycastle-api from 2.17 to 2.21 (#1651) Bumps [bouncycastle-api](https://github.com/jenkinsci/bouncycastle-api-plugin) from 2.17 to 2.21. - [Release notes](https://github.com/jenkinsci/bouncycastle-api-plugin/releases) - [Changelog](https://github.com/jenkinsci/bouncycastle-api-plugin/blob/master/docs/CHANGELOG.md) - [Commits](https://github.com/jenkinsci/bouncycastle-api-plugin/compare/bouncycastle-api-2.17...bouncycastle-api-2.21) --- updated-dependencies: - dependency-name: org.jenkins-ci.plugins:bouncycastle-api dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

push time in 2 hours

delete branch jenkinsci/configuration-as-code-plugin

delete branch : dependabot/maven/org.jenkins-ci.plugins-bouncycastle-api-2.21

delete time in 2 hours

PR merged jenkinsci/configuration-as-code-plugin

Bump bouncycastle-api from 2.17 to 2.21 dependencies

Bumps bouncycastle-api from 2.17 to 2.21. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jenkinsci/bouncycastle-api-plugin/releases">bouncycastle-api's releases</a>.</em></p> <blockquote> <h2>2.21</h2> <h2>📦 Dependency updates</h2> <ul> <li>Update to BouncyCastle library to 1.69 (<a href="https://github-redirect.dependabot.com/jenkinsci/bouncycastle-api-plugin/issues/44">#44</a>) <a href="https://github.com/jtnord"><code>@​jtnord</code></a></li> </ul> <h2>2.20</h2> <p>Various updates to keep the plugin current.</p> <h2>🚀 New features and improvements</h2> <ul> <li>Added jenkins.bouncycastle.prioritizeJceProvider system property (<a href="https://github-redirect.dependabot.com/jenkinsci/bouncycastle-api-plugin/issues/29">#29</a>) <a href="https://github.com/thomasgl-orange"><code>@​thomasgl-orange</code></a>. This is considered experimental.</li> </ul> <h2>📦 Dependency updates</h2> <ul> <li>Bump plugin from 4.15 to 4.16 (<a href="https://github-redirect.dependabot.com/jenkinsci/bouncycastle-api-plugin/issues/34">#34</a>) <a href="https://github.com/dependabot"><code>@​dependabot</code></a></li> </ul> <h2>👻 Maintenance</h2> <ul> <li>General plugin updates (<a href="https://github-redirect.dependabot.com/jenkinsci/bouncycastle-api-plugin/issues/32">#32</a>) <a href="https://github.com/jeffret-b"><code>@​jeffret-b</code></a></li> <li>ignore CRLF when comparing PEM contents in tests (<a href="https://github-redirect.dependabot.com/jenkinsci/bouncycastle-api-plugin/issues/30">#30</a>) <a href="https://github.com/thomasgl-orange"><code>@​thomasgl-orange</code></a></li> </ul> <h2>2.19</h2> <p>Incomplete release. Not posted to Artifactory.</p> <h2>bouncycastle-api-2.18</h2> <p>Update bouncycastle to 1.64.</p> <h2>📦 Dependency updates</h2> <ul> <li>Update bouncycastle to 1.64 (<a href="https://github-redirect.dependabot.com/jenkinsci/bouncycastle-api-plugin/issues/25">#25</a>) <a href="https://github.com/res0nance"><code>@​res0nance</code></a></li> </ul> <h2>📝 Documentation updates</h2> <ul> <li>Move the plugin documentation from Wiki to GitHub (<a href="https://github-redirect.dependabot.com/jenkinsci/bouncycastle-api-plugin/issues/26">#26</a>) <a href="https://github.com/oleg-nenashev"><code>@​oleg-nenashev</code></a></li> </ul> <h2>👻 Maintenance</h2> <ul> <li>Configure incrementals (<a href="https://github-redirect.dependabot.com/jenkinsci/bouncycastle-api-plugin/issues/28">#28</a>) <a href="https://github.com/jeffret-b"><code>@​jeffret-b</code></a></li> <li>Enable Release Drafter in the repository (<a href="https://github-redirect.dependabot.com/jenkinsci/bouncycastle-api-plugin/issues/27">#27</a>) <a href="https://github.com/oleg-nenashev"><code>@​oleg-nenashev</code></a></li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/jenkinsci/bouncycastle-api-plugin/blob/master/docs/CHANGELOG.md">bouncycastle-api's changelog</a>.</em></p> <blockquote> <h1>Release Notes (archive)</h1> <h3>New versions</h3> <p>See <a href="https://github.com/jenkinsci/bouncycastle-api-plugin/releases">GitHub Releases</a> for recent versions.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jenkinsci/bouncycastle-api-plugin/commit/718bea8d1ac776b947bbbb0a4a1e50a70121f6d9"><code>718bea8</code></a> [maven-release-plugin] prepare release bouncycastle-api-2.21</li> <li><a href="https://github.com/jenkinsci/bouncycastle-api-plugin/commit/578780b62fd0ad4c8287deeaac636bbd08cdc668"><code>578780b</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/jenkinsci/bouncycastle-api-plugin/issues/44">#44</a> from jtnord/update-bc-version</li> <li><a href="https://github.com/jenkinsci/bouncycastle-api-plugin/commit/edb0d5c21e6725fe70475d5bbbd3c6f177808b38"><code>edb0d5c</code></a> use a property to make updating easier</li> <li><a href="https://github.com/jenkinsci/bouncycastle-api-plugin/commit/2ddb7bcce2622a7b95e07dbbc6ed1a539e6d7239"><code>2ddb7bc</code></a> Update to BC 1.69</li> <li><a href="https://github.com/jenkinsci/bouncycastle-api-plugin/commit/8fd4c5a5950d76904a7297ed36276f7d82802a82"><code>8fd4c5a</code></a> [maven-release-plugin] prepare for next development iteration</li> <li><a href="https://github.com/jenkinsci/bouncycastle-api-plugin/commit/aea609aa845c6fd32b232382297616a5e66c9085"><code>aea609a</code></a> [maven-release-plugin] prepare release bouncycastle-api-2.20</li> <li><a href="https://github.com/jenkinsci/bouncycastle-api-plugin/commit/b451f9f7c1adb955d33af4f2e3f46766ffd8e55e"><code>b451f9f</code></a> [maven-release-plugin] prepare for next development iteration</li> <li><a href="https://github.com/jenkinsci/bouncycastle-api-plugin/commit/c7c202f49cb542e9e7d08ab2678ee05ba6fad270"><code>c7c202f</code></a> [maven-release-plugin] prepare release bouncycastle-api-2.19</li> <li><a href="https://github.com/jenkinsci/bouncycastle-api-plugin/commit/ec41f38ccb6a6500f0426e58c9dd81feabcbfbc2"><code>ec41f38</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/jenkinsci/bouncycastle-api-plugin/issues/34">#34</a> from jenkinsci/dependabot/maven/org.jenkins-ci.plugins...</li> <li><a href="https://github.com/jenkinsci/bouncycastle-api-plugin/commit/8e8b1cd688f78bb4e5615e05d3c04bb0bb0da4da"><code>8e8b1cd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/jenkinsci/bouncycastle-api-plugin/issues/33">#33</a> from jenkinsci/dependabot/maven/org.assertj-assertj-co...</li> <li>Additional commits viewable in <a href="https://github.com/jenkinsci/bouncycastle-api-plugin/compare/bouncycastle-api-2.17...bouncycastle-api-2.21">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

+2 -2

1 comment

1 changed file

dependabot[bot]

pr closed time in 2 hours

push eventjenkinsci/configuration-as-code-plugin

Daniel Brereton

commit sha f114533609152f1cd03320cd364784f5da580ef3

Clarified Built-In and GitHub Authorizations for Global Matrix Auth Plugin (#1642) Co-authored-by: Oleg Nenashev <o.v.nenashev@gmail.com>

view details

push time in 2 hours

PR merged jenkinsci/configuration-as-code-plugin

Clarified Built-In and GitHub Authorizations for Global Matrix Auth Plugin

<!-- Please describe your pull request here. -->

Your checklist for this pull request

🚨 Please review the guidelines for contributing to this repository.

  • [x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side) and not your master branch!
  • [x] Ensure that the pull request title represents the desired changelog entry
  • [x] Please describe what you did
  • Link to relevant issues in GitHub or in Jenkins JIRA
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Did you provide a test-case? That demonstrates feature works or fixes the issue.

Description

When persisting Jenkins configuration-as-code, I found it quite difficult to locate information on this plugin's exact available formatting/options. I did some digging and found the official docs for github oauth that make reference to github-based methods of auth within the project-based matrix auth. that this doc refers to: https://plugins.jenkins.io/github-oauth/. I felt that this information was important enough to replicate, and that provision of a source in what must be more than an edge case would be of use to others.

+16 -0

6 comments

1 changed file

dbeezt

pr closed time in 2 hours

push eventjenkinsci/jenkins

Basil Crow

commit sha 6d80eac7e12e81fa8279f1c9daa384f55a2ce3eb

Backport logging-related `AntClassLoader` fixes to our fork (#5650) - commit 189ad7e59 bz-62764 Add a debug log message when we skip invalid path elements from the `AntClassLoader`'s classpath - commit 008f1c8be Embrace `StringUtils#getStackTrace` - commit 13c01b296 Improve skipping of non-zips

view details

push time in 2 hours

PR merged jenkinsci/jenkins

Backport logging-related `AntClassLoader` fixes to our fork ready-for-merge developer

See Ant Bug 62764. A straightforward backport of the following commits from Ant 1.10.6 to our forked copy of AntClassLoader:

Proposed changelog entries

Developer: AntClassloader will now ignore files that are part of the classpath but not zip files when scanning for resources. It used to throw an exception.

Proposed upgrade guidelines

N/A

Submitter checklist

  • [x] (If applicable) Jira issue is well described
  • [x] Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change). Examples
    • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
  • [x] Appropriate autotests or explanation to why this change has no tests
  • [x] For dependency updates: links to external changelogs and, if possible, full diffs

<!-- For new API and extension points: Link to the reference implementation in open-source (or example in Javadoc) -->

Desired reviewers

@mention

<!-- Comment: If you need an accelerated review process by the community (e.g., for critical bugs), mention @jenkinsci/code-reviewers -->

Maintainer checklist

Before the changes are marked as ready-for-merge:

  • [ ] There are at least 2 approvals for the pull request and no outstanding requests for change
  • [ ] Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
  • [ ] Changelog entries in the PR title and/or Proposed changelog entries are correct
  • [ ] Proper changelog labels are set so that the changelog can be generated automatically
  • [ ] If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
  • [ ] If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).
+44 -2

1 comment

1 changed file

basil

pr closed time in 2 hours

push eventjenkinsci/jenkins

Tomek Szmytka

commit sha 5f89d4d832ce7bc5294c772bb542cdd685a0a762

[JENKINS-64666] document urls (#5652)

view details

push time in 2 hours

PR merged jenkinsci/jenkins

[JENKINS-64666] document urls ready-for-merge bug

<!-- Comment: A great PR typically begins with the line below. Replace XXXXX with the numeric part of the issue's id you created on JIRA. Please note that if you want your changes backported into LTS, you will need to create a JIRA ticket for it. Read https://www.jenkins.io/download/lts/#backporting-process for more. --> See JENKINS-64666. Document modules with project urls. This will allow /about page to build correct links.

<!-- Comment: If the issue is not fully described in the ticket, add more information here (justification, pull request links, etc.).

  • We do not require JIRA issues for minor improvements.
  • Bugfixes should have a JIRA issue (backporting process).
  • Major new features should have a JIRA issue reference. -->

Proposed changelog entries

Provide working "Help About" links for Jenkins CLI, Jenkins core, and Jenkins war

<!-- Comment: The changelogs will be integrated by the core maintainers after the merge. See the changelog examples here: https://www.jenkins.io/changelog/ -->

Proposed upgrade guidelines

N/A

Submitter checklist

  • [x] (If applicable) Jira issue is well described
  • [x] Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change). Examples
    • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
  • [x] Appropriate autotests or explanation to why this change has no tests
  • [x] For dependency updates: links to external changelogs and, if possible, full diffs

<!-- For new API and extension points: Link to the reference implementation in open-source (or example in Javadoc) -->

Maintainer checklist

Before the changes are marked as ready-for-merge:

  • [x] There are at least 2 approvals for the pull request and no outstanding requests for change
  • [x] Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
  • [x] Changelog entries in the PR title and/or Proposed changelog entries are correct
  • [x] Proper changelog labels are set so that the changelog can be generated automatically
  • [x] If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
  • [x] If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).
+4 -0

1 comment

4 changed files

tszmytka

pr closed time in 2 hours

PullRequestReviewEvent

PR merged jenkinsci/junit-sql-storage-plugin

Bump flyway-core from 7.12.0 to 7.12.1 dependencies java

Bumps flyway-core from 7.12.0 to 7.12.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/flyway/flyway/releases">flyway-core's releases</a>.</em></p> <blockquote> <h2>Flyway 7.12.1</h2> <p>See <a href="https://flywaydb.org/documentation/learnmore/releaseNotes#7.12.1">https://flywaydb.org/documentation/learnmore/releaseNotes#7.12.1</a></p> <p>CLI artifact available <a href="https://repo1.maven.org/maven2/org/flywaydb/flyway-commandline/7.12.1/">here</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/flyway/flyway/commit/7b4e34b879b782555c7410698114c98a5f337ba1"><code>7b4e34b</code></a> Fix <a href="https://github-redirect.dependabot.com/flyway/flyway/issues/3111">#3111</a>: add target=next</li> <li><a href="https://github.com/flyway/flyway/commit/7ec393785de9e8bfee811b768d369133df2b4765"><code>7ec3937</code></a> Change Redgate update check request</li> <li><a href="https://github.com/flyway/flyway/commit/7bcb14764c99bcc274ab8430e2f34e9475caca2d"><code>7bcb147</code></a> Introduce Redgate update check</li> <li><a href="https://github.com/flyway/flyway/commit/c36800d6c565a564e93e32cbf58c0a4b1040cfa8"><code>c36800d</code></a> Don't set classloaders externally</li> <li><a href="https://github.com/flyway/flyway/commit/83a052e353c128d0d03bdec47b15271a53e65d47"><code>83a052e</code></a> Fix <a href="https://github-redirect.dependabot.com/flyway/flyway/issues/3245">#3245</a>: limit yugabyte's select version</li> <li>See full diff in <a href="https://github.com/flyway/flyway/compare/flyway-7.12.0...flyway-7.12.1">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

+1 -1

0 comment

1 changed file

dependabot[bot]

pr closed time in 2 hours

delete branch jenkinsci/junit-sql-storage-plugin

delete branch : dependabot/maven/org.flywaydb-flyway-core-7.12.1

delete time in 2 hours

push eventjenkinsci/junit-sql-storage-plugin

dependabot[bot]

commit sha f6c83309d2011bbe2924fa79b33582d5956f72a9

Bump flyway-core from 7.12.0 to 7.12.1 (#114) Bumps [flyway-core](https://github.com/flyway/flyway) from 7.12.0 to 7.12.1. - [Release notes](https://github.com/flyway/flyway/releases) - [Commits](https://github.com/flyway/flyway/compare/flyway-7.12.0...flyway-7.12.1) --- updated-dependencies: - dependency-name: org.flywaydb:flyway-core dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

push time in 2 hours

push eventjenkinsci/junit-sql-storage-plugin

dependabot[bot]

commit sha 2fefe176ffd581beeb51542d23f3346b33fdd4c6

Bump error_prone_annotations from 2.8.0 to 2.8.1 (#113) Bumps [error_prone_annotations](https://github.com/google/error-prone) from 2.8.0 to 2.8.1. - [Release notes](https://github.com/google/error-prone/releases) - [Commits](https://github.com/google/error-prone/compare/v2.8.0...v2.8.1) --- updated-dependencies: - dependency-name: com.google.errorprone:error_prone_annotations dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

push time in 2 hours

PR merged jenkinsci/junit-sql-storage-plugin

Bump error_prone_annotations from 2.8.0 to 2.8.1 dependencies java

Bumps error_prone_annotations from 2.8.0 to 2.8.1. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/google/error-prone/commit/3f51efd605d071f6be0e439c350aac2c5b65109b"><code>3f51efd</code></a> Release Error Prone 2.8.1</li> <li><a href="https://github.com/google/error-prone/commit/fb208dddb4346f74a95d4af34d366838a61003d0"><code>fb208dd</code></a> Use <code>nexus-staging-maven-plugin</code> to release to maven central from maven</li> <li><a href="https://github.com/google/error-prone/commit/b660308b5b99821b36dbbbbbdc09096546a887fe"><code>b660308</code></a> Handle more cases in <code>ReturnMissingNullable</code>.</li> <li><a href="https://github.com/google/error-prone/commit/cc5ef9efe296bd63c8c7553a7ff48ecf8b4a8705"><code>cc5ef9e</code></a> Fix typo in the "The Problem" paragraph.</li> <li><a href="https://github.com/google/error-prone/commit/4c57125a9b64812dc19302809854743e7393634e"><code>4c57125</code></a> All <code>forEach</code> on subtypes of <code>Collection</code></li> <li><a href="https://github.com/google/error-prone/commit/6a63b5713958c51e4e8f7c135720b9e84fca9309"><code>6a63b57</code></a> Discourage looping over the result of <code>toCharArray()</code></li> <li><a href="https://github.com/google/error-prone/commit/4e91cb4ddddc57ea2e0dc145e1cbe667fcbae375"><code>4e91cb4</code></a> Automatic code cleanup.</li> <li><a href="https://github.com/google/error-prone/commit/de0b0178d9131207399077767939a31c1aa67398"><code>de0b017</code></a> Add a flag to configure the default nullness annotation</li> <li><a href="https://github.com/google/error-prone/commit/c5218edd27c8d9e9e2068bd00b78d8cbee23ffbd"><code>c5218ed</code></a> Add suggested fixes for OptionalOfRedundantMethod</li> <li><a href="https://github.com/google/error-prone/commit/91416d5169157c94f5c3acfb8cb1c41fce0864a0"><code>91416d5</code></a> Remove removed tests from <code>TEST_DEPS</code>, and add assertions to prevent recurrence.</li> <li>See full diff in <a href="https://github.com/google/error-prone/compare/v2.8.0...v2.8.1">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

+1 -1

0 comment

1 changed file

dependabot[bot]

pr closed time in 2 hours

delete branch jenkinsci/junit-sql-storage-plugin

delete branch : dependabot/maven/com.google.errorprone-error_prone_annotations-2.8.1

delete time in 2 hours

delete branch timja/terraform-provider-azurerm

delete branch : static-site-custom-domain

delete time in 2 hours

PR closed timja/terraform-provider-azurerm

New resource: static_site_custom_domain

Fixes https://github.com/terraform-providers/terraform-provider-azurerm/issues/11971

Blocked on https://github.com/Azure/azure-sdk-for-go/issues/14690

+754 -19

0 comment

12 changed files

timja

pr closed time in 2 hours

delete branch timja/jenkins-junit-postgresql-plugin

delete branch : enable-cd

delete time in 2 hours

push eventjenkinsci/junit-sql-storage-plugin

Tim Jacomb

commit sha 79279ea1504d18cb5ac5dde1dc319a6263d72c84

Enable CD (#112)

view details

push time in 2 hours

delete branch timja/intellij-community

delete branch : feature/IDEA-205103-maven-archetype-sorting

delete time in 3 hours

PR closed JetBrains/intellij-community

IDEA-205103 Sort maven archetype versions

Use maven version sorting instead of lexicographical order

Closes IDEA-205103

+127 -11

1 comment

13 changed files

timja

pr closed time in 3 hours

pull request commentJetBrains/intellij-community

IDEA-205103 Sort maven archetype versions

🤷

timja

comment created time in 3 hours

delete branch timja/jenkins-infra-charts

delete branch : ci.jenkins.io

delete time in 3 hours

PR closed jenkins-infra/charts

Reviewers
Add ci.jenkins.io chart on-hold

TODO / questions:

  • [ ] azure vm agents config
  • [ ] ec2 plugin config
  • [ ] update tool versions to match whats currently on ci.jenkins.io
  • [ ] re-review config and make sure nothings changed since config was last retrieved
  • [ ] provision CI cluster - I assume we don't want this running on publick8s?
  • [ ] enable other cluster tools to CI cluster (loki, grafana etc)
  • [ ] move Infra folder to infra.ci - folder credentials are a pain with JCasC, might be better to just move it to infra.ci
  • [ ] charts secrets need creating
  • [ ] might need a pilot address for when this first gets started rather than ci.jenkins.io?
  • [ ] Tuning JVM options?
  • [ ] enable production config, currently commented out
  • [ ] lock plugin versions?

(I'll need help with most of this, getting the current config and charts secrets)

cc @MarkEWaite @olblak @oleg-nenashev

This can be tested locally on minikube with:

helmfile -f clusters/cik8s.yaml apply

note you'll need some secrets I used:

secrets/config/ci/jenkins/secrets.yaml

secrets:
    LDAP_SERVER: abcd
    LDAP_ROOT_DN: defgh
    LDAP_MANAGER_DN: aa
    LDAP_MANAGER_PASSWORD: abcd
    GITHUB_USERNAME: ***
    GITHUB_PASSWORD: ******
    AZURE_CLIENT_ID: abcd
    AZURE_CLIENT_SECRET: defg
    AZURE_SUBSCRIPTION_ID: ****
    AZURE_TENANT_ID: ****
    AZURE_VMAGENT_USERNAME: aaaa
    AZURE_VMAGENT_PASSWORD: adssad
    K8S_SSH_PUBLIC_KEY: aaaa
    STAGING_K8S_SSH_PUBLIC_KEY: adasdas
    INCREMENTALS_PUBLISHER: asdasd
    DOCKER_HUB_CONFIG_BYTES: ewogICJhdXRocyIgOiB7CiAgfSwKICAiY3JlZHNTdG9yZSIgOiAiZGVza3RvcCIsCiAgInN0YWNrT3JjaGVzdHJhdG9yIiA6ICJzd2FybSIsCiAgIkh0dHBIZWFkZXJzIiA6IHsKICAgICJVc2VyLUFnZW50IiA6ICJEb2NrZXItQ2xpZW50LzE5LjAzLjUgKGRhcndpbikiCiAgfSwKICAiZXhwZXJpbWVudGFsIiA6ICJkaXNhYmxlZCIKfQo=
    DATADOG_API_KEY: abcd
    EMAIL_USERNAME: abcd
    EMAIL_PASSWORD: defg

+549 -15

0 comment

9 changed files

timja

pr closed time in 3 hours