Status: Resolved (View Workflow)
We use a pipeline to automate the release of a sequence of projects.
These are Maven projects that depend on each other (with a version specified for each dependency).
This sequence of projects needs to be consistent on the version numbers.
So, before releasing one of the projects, we need to modify the versions of its dependencies on the previous projects, to use the version numbers that were just released.
And we need to commit the modified pom.xml file
Currently, the only way I found is to call a command-line (with "bat" or "sh") that does the commit.
It works, but relies on a local SCM client and prevents from using the Jenkins credentials for the SCM authentication
It would much easier and cleaner to have a "commit" step like the already-existing "checkout" step
JENKINS-28335 Pipeline step to run Git commands with credentials & tool
- In Review
|Field||Original Value||New Value|
|Link||This issue duplicates JENKINS-28335 [ JENKINS-28335 ]|
|Resolution||Duplicate [ 3 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
Is JENKINS-28335 really a duplicate?
It seems to cover what would be needed for git, but not for other scm, like svn