Closed rohit-kapoor1 closed 2 years ago
@aleksandr-m Could you please help us here? Our production systems will get impacted if this does not get resolved by this week.
You should probably add custom settings and repo parameters to argLine
as well.
Hi everyone,
We are facing a blocker due to the release:finish goal not working. I have provided detailed description of the issue below. Please help us identify the root cause of our build failures.
Background
My team was previously using jgitflow-plugin previously for managing tagging and releases from the Jenkins CI server. Recently, we performed an upgrade to the CI/CD process and are now using the gitflow-maven-plugin. After the migration we have been facing issues while running the commands for this plugin.
Versions and System details
Jenkins: 2.332.1 OS: Windows Server 2016 Jenkins job type: Maven Project Nexus: Nexus Repository Manager OSS 2.14.13-01
Project structure
We have two kinds of projects: master and child. Child projects utilize artifacts from the master(base repo). All the artefacts are pushed to Nexus Repository Manager deployed in the same network. We have individual jobs to build all these projects(downstream jobs). All the downstream jobs are working fine. We have a separate job to cut releases, which is using this plugin, and is failing miserably. This is the maven structure for the master repo:
We use the following commands for our tagging and release functionality:
Issue
When we try to run the release:finish goal on a master build(master repo), it fails. The same is building successfully when we run it for a child project.
Build Error
Parent POM of the master repo