kerwinc / vststasks Goto Github PK

I really love the features offered by this extension however, when I tried to integrate it with my build pipelines it fails due to an inability to read the repo. Some investigation shows that the issue relates to an inability to obtain the OAuth token, but the setting needed to resolve this is not available, or does not work as intended, when using a YAML build definition. The setting to which I refer is "Allow scripts to access the OAuth token" - I had thought that if I set persistCredentials: true that it would work but alas, to no avail.

Can you confirm if there is a known workaround for this, or perhaps correct me if I am misunderstanding the configuration?

Hi, I am trying to run this task in a YAML pipeline. I have left the "Repository" value as default ($(Build.Repository.Name)) but it returns the error: Cannot validate argument on parameter 'Repository'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. I've also tried the name of the repo itself. Is there a solution to this? Thanks

Hello, I'm trying to create a new branch at the end of a yaml build pipeline, but the task raise an error:
##[debug]GET https://dev.azure.com/XXX//YYY/_apis/git/repositories/DevOps/?api-version=5.0 with 0-byte payload ##[debug]received 15653-byte response of content type text/html; charset=utf-8 Repository Id: [] ##[debug]Caught exception from task script. ##[debug]Error record: ##[debug]D:\a\_tasks\branch-maker_b15628f5-ba26-4250-8e69-fb729fbda870\0.1.3\run.ps1 : Cannot validate argument on parameter 'Repository'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. ##[debug]At line:1 char:1 ##[debug]+ . 'd:\a\_tasks\branch-maker_b15628f5-ba26-4250-8e69-fb729fbda870\0.1. ... ##[debug]+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ##[debug] + CategoryInfo : InvalidData: (:) [run.ps1], ParameterBindingValidationException ##[debug] + FullyQualifiedErrorId : ParameterArgumentValidationError,run.ps1 ##[debug] ##[debug]Script stack trace: ##[debug]at <ScriptBlock>, D:\a\_tasks\branch-maker_b15628f5-ba26-4250-8e69-fb729fbda870\0.1.3\run.ps1: line 63 ##[debug]at <ScriptBlock>, <No file>: line 1 ##[debug]at <ScriptBlock>, <No file>: line 22 ##[debug]at <ScriptBlock>, <No file>: line 18 ##[debug]at <ScriptBlock>, <No file>: line 1 ##[debug]Exception: ##[debug]System.Management.Automation.ParameterBindingValidationException: Cannot validate argument on parameter 'Repository'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. ---> System.Management.Automation.ValidationMetadataException: The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. ##[debug] at System.Management.Automation.ValidateNotNullOrEmptyAttribute.Validate(Object arguments, EngineIntrinsics engineIntrinsics) ##[debug] at System.Management.Automation.ParameterBinderBase.BindParameter(CommandParameterInternal parameter, CompiledCommandParameter parameterMetadata, ParameterBindingFlags flags) ##[debug] --- End of inner exception stack trace --- ##[debug] at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception) ##[debug] at System.Management.Automation.Interpreter.ActionCallInstruction2.Run(InterpretedFrame frame)
##[debug] at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
##[debug] at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
##[debug] at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
##[debug] at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
##[debug] at System.Management.Automation.PSScriptCmdlet.RunClause(Action1 clause, Object dollarUnderbar, Object inputToProcess) ##[debug] at System.Management.Automation.PSScriptCmdlet.DoEndProcessing() ##[debug] at System.Management.Automation.CommandProcessorBase.Complete() ##[error]Cannot validate argument on parameter 'Repository'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. ##[debug]Processed: ##vso[task.logissue type=error]Cannot validate argument on parameter 'Repository'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. ##[debug]Processed: ##vso[task.complete result=Failed]

Here is the configuration:

- task: branch-maker@0
inputs:
repository: '$(Build.Repository.Name)'
sourceBranchName: 'master'
newBranchName: 'release/$(Build.BuildNumber)'
applyBranchPolicy: true
MinimumApproverCount: '1'
creatorVoteCounts: true
checkForLinkedWorkItems: true
checkForLinkedWorkItemsType: 'optional'
checkForCommentResolution: true
enforceMergeStrategy: true
enforceMergeStrategyType: 'squashMerge'

HI ,

I have run the pipeline with this extension , pipeline got sucess. But not able to see the newly created branch under repo

Regards,
Mani

The build fails when using PullRequests to merge into master from a release branch. It sees an additional commit that is used to mark the PR merge and complains that now develop branch is behind master, although running a diff on the two branches will report that there are no differences between them.

Sorry, I have the impression of being an idiot but... how does this extension work fcs ? Can't figure it out. It's installed and I can't anything changed in my Azure DevOps environment. And I cannot find it in the documentation here either.

Thank you for your help.

Hi.
First, I'd like to thank you for making this tool it is amazing for check your branches and making your our devs follow gitflow all the time but recently we've found a problem: we recently patched our servers and removed TLS 1.0 for security concerns and the extension started to have connection issues, I check the code and figure that the tool runs under Powershell3 (Which i assume to be powershell 3.0) probably using a .net target that uses TLS 1.0 is there a work around for it to upgrade it to TLS 1.1 or 2.0 ? PS: I tried to change the binding to "Powershell" on the task.json file and it didn't work.

Thank you. (below is a stack trace of my build)

2018-10-22T16:00:37.4667844Z ##[section]Starting: Gitflow Branch Gate 2018-10-22T16:00:37.4824189Z ============================================================================== 2018-10-22T16:00:37.4824189Z Task : Gitflow Branch Gate 2018-10-22T16:00:37.4824189Z Description : Apply a set of branch commit rules to help prevent stale branches and rolling back changes. 2018-10-22T16:00:37.4824189Z Version : 1.0.4 2018-10-22T16:00:37.4824189Z Author : Kerwin Carpede 2018-10-22T16:00:37.4824189Z Help : 2018-10-22T16:00:37.4824189Z ============================================================================== 2018-10-22T16:00:38.4042863Z Project Collection: [https://tfs.ercbpo.local/tfs/ERC/] 2018-10-22T16:00:38.4042863Z Project Name: [ERC Core] 2018-10-22T16:00:38.4042863Z Build Reason: [40] 2018-10-22T16:00:38.4042863Z Build Reason: [Schedule] 2018-10-22T16:00:38.4042863Z Repository: [service-latitude-migration] 2018-10-22T16:00:38.4042863Z Current Branch: [develop] 2018-10-22T16:00:38.4042863Z Authentication Type: [OAuthToken] 2018-10-22T16:00:38.4042863Z Rules: 2018-10-22T16:00:38.4042863Z 2018-10-22T16:00:38.4042863Z 2018-10-22T16:00:38.4042863Z ReleasePrefix : releases/* 2018-10-22T16:00:38.4042863Z ReleaseBranchesMustNotBeBehindMaster : False 2018-10-22T16:00:38.4042863Z FeatureBranchLimit : 50 2018-10-22T16:00:38.4042863Z FeatureBranchesMustNotBeBehindDevelop : False 2018-10-22T16:00:38.4042863Z CurrentFeatureMustNotBeBehindMaster : True 2018-10-22T16:00:38.4042863Z HotfixPrefix : hotfixes/* 2018-10-22T16:00:38.4042863Z FeatureDaysLimit : 60 2018-10-22T16:00:38.4042863Z BranchNamesMustMatchConventions : True 2018-10-22T16:00:38.4042863Z FeaturePrefix : features/* 2018-10-22T16:00:38.4042863Z DevelopMustNotBeBehindMaster : True 2018-10-22T16:00:38.4042863Z DevelopBranch : develop 2018-10-22T16:00:38.4042863Z MustNotHaveHotfixAndReleaseBranches : False 2018-10-22T16:00:38.4042863Z ReleaseBranchesMustNotHaveActivePullRequests : False 2018-10-22T16:00:38.4042863Z FeatureBranchesMustNotBeBehindMaster : False 2018-10-22T16:00:38.4042863Z MasterBranch : master 2018-10-22T16:00:38.4042863Z MasterMustNotHaveActivePullRequests : False 2018-10-22T16:00:38.4042863Z CurrentFeatureMustNotBeBehindDevelop : True 2018-10-22T16:00:38.4042863Z ReleaseBranchLimit : 3 2018-10-22T16:00:38.4199118Z HotfixBranchesMustNotHaveActivePullRequests : False 2018-10-22T16:00:38.6386608Z ReleaseDaysLimit : 90 2018-10-22T16:00:38.6386608Z HotfixDaysLimit : 3 2018-10-22T16:00:38.6386608Z HotfixeBranchesMustNotBeBehindMaster : True 2018-10-22T16:00:38.6386608Z BypassBranchesWithNameMatchingPattern : users/* 2018-10-22T16:00:38.6386608Z HotfixBranchLimit : 3 2018-10-22T16:00:38.6386608Z 2018-10-22T16:00:38.6386608Z ##[error]The underlying connection was closed: An unexpected error occurred on a receive. 2018-10-22T16:00:38.6542862Z ##[section]Finishing: Gitflow Branch Gate

Hi,

I installed this extenion to my Azure Devops. when i try to add this task to my pipelines, add button is not appearing on this task. is this plugin supported in Azure devops latest version.

Using "Visual Studio Team Services":
I setup a build to check out my repository and ran the "Gitflow Branch Gate" and got the error "Could not find remote branch: refs/heads/master"

I did set the Authentication to be Windows Authentication. (Which our build servers run as to access the code and other resources)

Am I missing some setup?

Resurrecting Issue #3

I understand how to resolve this issue using the classic editor, but we want to use the YAML way instead. Is there a way to Allow scripts to access the OAuth token in a YAML pipeline?

We get code from a 3rd party which is what our solution is based on. We keep this in a "base" branch so we always have a fresh copy of the their code w/out modifications. It would be nice to "ignore" this branch in the "naming" conventions w/out having to turn the entire option off.

We maintain this branch outside of the gitflow scope.

Hi @kerwinc Thanks for this extension. Is there any plan to add support for support branches? Please see below link.

https://github.com/nvie/gitflow

To list/start support branches, use:

git flow support
git flow support start
For support branches, the arg must be a commit on master.

Thanks

Would be useful (required for our use) to have support for all attributes of a branch policy including "Build Validation" and "Automatically included reviewers"

The build summary report needs to show the branch name and days stale.

Dear @kerwinc Is it possible to support GitflowBranchGate on Linux self-hosted agents? We have installed PowerShell on Ubuntu 22 LTS, but unfortunately, we are getting general errors pointing to issues with Operating System compatibility.
##[error]The current operating system is not capable of running this task. That typically means the task was written for Windows only. For example, written for Windows Desktop PowerShell. Finishing: GitflowBranchGate
Does the current version supports non-windows agents and if yes what are additional requirements that must be fulfilled (installed) on the agent to support the process?

:~$ powershell -v PowerShell 7.3.6

@kerwinc this is an awesome vstask!
Currently this is scanning all branches, is there a way to target just the current branch? Builds are failing because of other branches that has nothing to do with the current PR. Additional settings perhaps?

when branches name is so large the errors isn't clear