Skip to content

Bump Jenkins and bom version to 2.387.x #334

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

Merged
merged 1 commit into from
Jun 19, 2023

Conversation

mifitous
Copy link
Contributor

Testing done

### 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

@jetersen jetersen changed the title bom-2.387.x Bump Jenkins and bom version to 2.387.x Jun 19, 2023
@jetersen jetersen enabled auto-merge (squash) June 19, 2023 11:14
@jetersen jetersen merged commit f7d1844 into jenkinsci:master Jun 19, 2023
@jmini
Copy link
Contributor

jmini commented Jun 28, 2023

Some notes about this change:

The BOM update is requested, in order to get version 5.3.0-88.vf8787b_92d679 of the gitlab-api plugin.

According to PR jenkinsci/bom#2121 the bom bom-2.361.x will never be updated anymore. So we need to switch to a newer one.

@jetersen
Copy link
Member

jetersen commented Jun 28, 2023

@jmini
You can read more about choosing a Jenkins version baseline here:
https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants