Create Pipeline about azure-devops-go-api

[kpfaulkner]

@raboley Currently unsure. No success myself... was hoping someone at MS might be able to answer the question here.

[anythingascode]

pipeClient.CreatePipeline is not working , i am getting following error and i dont see any Path parameter.
Value cannot be null.
Parameter name: Path
exit status 1

@kpfaulkner did you able to fix the issue?

[raboley]

Was wondering if writing my pipelines in go was possible and based on this issue that seems to be most likely not true. Is that correct?

[raboley]

@raboley Currently unsure. No success myself... was hoping someone at MS might be able to answer the question here.

I switched to just writing a go cli tool that holds all business logic, and then my pipeline just installs and runs commands from that tool to minimize the logic embedded in the pipelines.

[yradsmikham]

Agreed with all the above comments. CreatePipeline does not appear to be in a mature state as it is missing: path, repository.id, repository.name, and repository.type.

Here's a blog that covers it more in detail: https://blog.johnnyreilly.com/2021/05/08/create-pipeline-with-azure-devops-api

Any update on this?

[verthais]

I've run into the issue where I try to create pipeline

func CreatePipeline(ctx *context.Context, conn *azuredevops.Connection, repository *string) (*pipelines.Pipeline, error) {
	pipeClient := pipelines.NewClient(*ctx, conn)
	name := fmt.Sprintf("%sPipeline", *repository)

	args := pipelines.CreatePipelineArgs{
		Project: project,
		InputParameters: &pipelines.CreatePipelineParameters{
			Name:   &name,
			Configuration: &pipelines.CreatePipelineConfigurationParameters{
				Type: &pipelines.ConfigurationTypeValues.Yaml,
			},
		},
	}

	respones, err := pipeClient.CreatePipeline(*ctx, args)
	if err != nil {
		return nil, err
	}

	return respones, nil
}

And I'm getting an error

YYYY/MM/DD HH:MM:SS Failed to create: pipeline Value cannot be null.
Parameter name: Path

However there is no place to specify Path for module pipelines

[AdamRussak]

same here, is it marked as an bug/error? or are we missing something?

[LTomer]

I also got the same error meesage.
Is there an estaimated time to fix this issue?