Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example top-level/consuming pipelines? #39

Open
Liquidream opened this issue Nov 24, 2023 · 2 comments
Open

Example top-level/consuming pipelines? #39

Liquidream opened this issue Nov 24, 2023 · 2 comments

Comments

@Liquidream
Copy link

Hi there,

Firstly, thank you very much for creating this project. I am still fairly new to YAMP pipelines (and definitely new to templates), so this resource has been very helpful in my learnings.

One thing that would certainly help me, would be if there were examples of actually consuming these templates at the top-level, so that you can see example parameters being passed to the job templates, etc. (unless they are already present and I missed them?)

The reason I ask is because it took me WAY longer than I care to admit that it seems the jobs/dotnetcore_build_publish_job.yml template is intended to have the projectName parameter passing PRE-replacing the .'s for _'s (then it restores it internally for paths, etc.)

Either way, thanks in advance for your time.

@JFolberth
Copy link
Owner

Thanks @Liquidream that is a great callout and one I am attempting to get better at. Ideally I'd have documentation for each parent level stage; however, I struggle with this though, attempt to where I can.

I try to leverage this repository across all my public projects and have started to include the fully expanded yaml file to help assist with this. For this specific example: https://github.com/JFolberth/ToDo_AzureDeploymentEnvironment/blob/main/YAML/azure-pipelines-expanded.yml That being said I have not been linking back to this repository to show an example of usage.

Does this help in understanding/learning at all? If so I can track this as a feature to go back and add the references.

@Liquidream
Copy link
Author

Liquidream commented Nov 30, 2023

Hi @JFolberth,
Thanks for getting back to me.

Yeah, I think the expanded example is useful (so thanks for that). But by being expanded, it no longer shows how your parent/main pipeline is calling the templates (and their params), which was where I was coming from.

That's ok though, as I appreciate it would take a lot of time to also include these in your repo. Just thoguht I'd reach out in case you had an example or two already available. Not to worry.

Thanks again 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants