You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OpenRewrite team has been receptive to contributions in the past. They accepted our contribution when the archetype for the Jenkinsfile changed months ago.
Next Steps
Verify if the current recipe covers the latest archetype.
If not, decide between creating a meta-recipe or modifying the existing one.
If modifying the existing recipe, prepare a PR for the OpenRewrite repository.
Your thoughts and feedback on this approach are welcome.
Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered:
Basially it doesn't check the property by itself but the managed version of org.jenkins-ci.main:jenkins-core artifact (that is influenced by the jenkins.version property
What feature do you want to see added?
Current Situation
We are currently using the existing OpenRewrite BOM recipe for our plugin modernization efforts.
Question
Does this recipe cover the case of the latest Jenkins archetype?
Potential Actions
If the current recipe covers the latest archetype:
If the current recipe does not cover the latest archetype:
Create a meta-recipe that:
jenkins.baseline
propertyModify the existing recipe by:
Precedent
The OpenRewrite team has been receptive to contributions in the past. They accepted our contribution when the archetype for the Jenkinsfile changed months ago.
Next Steps
Your thoughts and feedback on this approach are welcome.
Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered: