![]() If someone can suggest an alternative way to achieve that, I'm open to suggestions as well. ![]() We do use the Azure DevOps package management, but we want to keep separate feeds for snapshots and for release builds (the way tools like Nexus do), so we have to have a mechanism for automatically advancing release numbers, checking out and back in and building and publishing the packaged module to the release feed. ![]() In particular, I don't know if there is anything that offers the same functionality as the Maven release plugin. P.S.: As you may be able to tell, I'm rather a newbie as far as Azure DevOps is concerned, so I surely don't know all tricks and features of that system. I am now running out of ideas how I could get the git push call to work - is there anyone out here who can help me out? registering a "store" type Git credential helper (assuming that an authentication problem is responsible for the timeout),īut without success.disabling the maven call and calling git push directly from the script,.In order to find out what causes this problem I tried a few things, among others, Once this is set up, my Maven call script runs up to the point where the release plugin attempts to push to Git the corresponding lines in the log file read Executing: cmd.exe /X /C "git push refs/heads/master:refs/heads/master"Īfter that, nothing happens (at least, nothing gets logged) until the timeout strikes: #The operation was canceled. Azure DevOps checks out the sources in a "detached HEAD state" - to solve this problem, the setup script tasks also calls git checkout master.The standard Azure DevOps git environment doesn't have the required config values "user.email" and "user.name" set this can be solved by calling git config in a separate "Command Line Script" task prior to pushing.This involved several obstacles, most of which I was able to overcome in one way or the other: My first attempt was to call the Maven release plugin directly on the checked out sources. We are migrating existing Java/Maven projects from a Jenkins build server to an Azure DevOps build environment, and I am trying to set up a build pipeline that mimics the Jenkins "Release Staging" functionality. No matter what I try, my script always times out after printing Pushing commits to git. Can someone tell me how to set up a "Command Line Script" task within an Azure DevOps build pipeline that pushes changes to a local Git repository (in fact, the Git repository on which the pipeline is based)?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |