I have an old settings.xml in the Azure devops agent's .m2 directory. I want to override it with new settings.xml through task group, but should not do any changes with the old settings.xml file. Because if it is worked, then we will update the old xml file.
How could we achieve the same using Azure Devops task group?
How could we achieve the same using Azure Devops task group?
I suggest that you could save the settings.xml file in Pipelines -> Library -> Secure files.
In Task Group, you could add Download secure file task and Maven task.
Download secure file task: Set the Reference Name and select the file
Maven task: Set the reference Settings.xml path: -s $(mvnSettings.secureFilePath)
Then you could create a task group.
Note: You need to set the paramter for the task group:
Default value: $(Agent.TempDirectory)/settings.xml
In this case, the old settings.xml will not be changed. When you reference this task group, it will download the new settings.xml in the secure file and reference the new settings.xml file in the maven task.
If you do not reference this task group, it can still use the old settings.xml file.
If you use maven task to build your project and authenticate with settings.xml, you could use this task twice, the 1st task uses the old settings.xml, and the 2nd task uses the new settings.xml.
In addition, you could specify the control condition to run this 2nd task only when a previous task has failed, as below. So the 2nd task will run only when the 1st maven task fails. See: Specify conditions for more details.
