Thanks for the nice explanation. I am looking for some references to use OutPut variables across stages in a classic pipeline. In the video we use the set and display task under 1 job. How do we use output variable when my set task in Job1 and recieve task in Job2.
Is there a way to pass the variable from the build pipeline to the release pipeline. In the video you set the variables in both the build pipeline then again in the release pipeline.
Not out of the box. youd have to save that value somewhere like a Variable Group or inside a file inside an artifact. On the other hand, if you use yml for build/release, you should be able to pass that value down
thanks. So without having more context, Im gonna make some assumptions. What you can do is have "placeholder" variables and have a step inside the pipeline that swaps out those placeholders with some value you stated in a variable in yml or some other variable group. I will probably make a video to cover such an idea if required
@@CodeDoge thanks for the idea, I would love to see it in video form, but I'll try it. I'll go back and watch the rest of your videos in the meantime hah
@@mollypepperpotanon8335 so maybe theres more specific way to use it conditionally, but I do something like the following : Task A - Has conditional output declared Task B - Script that picks up value from Task A and does something I think theres additional parameters in most steps that allow a task to be skipped/executed only if XYZ is true and etc. I think Id need a more specific scenario to help beyond that tho
Thanks for the video.. Its really helpful. I have one requirement like in my codeway yml file I have 3 environments like Dev stg and pro. When I run the pipeline all the environments are executing one after other. But my requirement is I want to select only specific environment to run like choice parameters same as in Jenkins. Is there any way to achieve to build specific environment. Thanks in advance
Man your channel is gold, keep it up!
big thanks for this compliment!
Thank you for this!!! :) love your channel ❤️🔥
thanks to my #1 fan
Great presentation!
thank you, hope it was helpful!
Thanks for the nice explanation. I am looking for some references to use OutPut variables across stages in a classic pipeline. In the video we use the set and display task under 1 job. How do we use output variable when my set task in Job1 and recieve task in Job2.
Is it possible to create an output variable in agent Job and use it in agent less job both in YAML and classic release pipeline?
Is there a way to pass the variable from the build pipeline to the release pipeline. In the video you set the variables in both the build pipeline then again in the release pipeline.
Not out of the box. youd have to save that value somewhere like a Variable Group or inside a file inside an artifact.
On the other hand, if you use yml for build/release, you should be able to pass that value down
Great video man. Very helpful. Do you know if there's a way to pass these pipeline variables to a nodeJS app's code?
thanks. So without having more context, Im gonna make some assumptions. What you can do is have "placeholder" variables and have a step inside the pipeline that swaps out those placeholders with some value you stated in a variable in yml or some other variable group. I will probably make a video to cover such an idea if required
@@CodeDoge thanks for the idea, I would love to see it in video form, but I'll try it. I'll go back and watch the rest of your videos in the meantime hah
@@rizhall sure I think I squeeze a quick video showing this in october/november. Hopefully its not too late by then, but do give it a shot!
Hi this is great - thank you so much - how would you use the output variable in a condition please?
you can use it with bash/powershell or any other "in file" scripting step/task.
@@CodeDoge sorry I meant in the condition clause of the pipeline
@@mollypepperpotanon8335 so maybe theres more specific way to use it conditionally, but I do something like the following :
Task A - Has conditional output declared
Task B - Script that picks up value from Task A and does something
I think theres additional parameters in most steps that allow a task to be skipped/executed only if XYZ is true and etc.
I think Id need a more specific scenario to help beyond that tho
Thanks for the video.. Its really helpful.
I have one requirement like in my codeway yml file I have 3 environments like Dev stg and pro.
When I run the pipeline all the environments are executing one after other.
But my requirement is I want to select only specific environment to run like choice parameters same as in Jenkins.
Is there any way to achieve to build specific environment.
Thanks in advance
I would recommend using stages / jobs.
I haevnt finished my yml video yet, but that would be the best way to seperate duties between environments