Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use jenkins.baseline to reduce bom update mistakes #562

Merged
merged 3 commits into from
Jan 14, 2025

Conversation

strangelookingnerd
Copy link
Contributor

Use jenkins.baseline in pom.xml

This change is proposed by the plugin archetype and makes maintenance of jenkins.version and bom a little easier.

Testing done

None. Rely on ci.jenkins.io to test it.

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

@strangelookingnerd strangelookingnerd requested a review from a team as a code owner January 14, 2025 08:42
@timja timja added the chore label Jan 14, 2025
pom.xml Outdated
@@ -37,6 +37,9 @@
<properties>
<gitHubRepo>jenkinsci/dark-theme-plugin</gitHubRepo>
<changelist>9999999-SNAPSHOT</changelist>
<!-- https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/ -->
<jenkins.baseline>2.426</jenkins.baseline>
<!-- TODO: should depend on baseline -->
<jenkins.version>2.453</jenkins.version>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you update this to corresponding LTS line instead please?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#484 set the jenkins version to 2.453 so I assume there was a reason for that?
I could bump the baseline and jenkins version to to 2.462.x instead. WDYT?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes please bump

pom.xml Outdated Show resolved Hide resolved
@timja timja enabled auto-merge (squash) January 14, 2025 11:27
@timja timja merged commit 64dd1f5 into jenkinsci:master Jan 14, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants