[samples] consistent main block for pipeline samples
See original GitHub issueFeature Area
/area samples
What feature would you like to see?
I’d like to see a consistent main block for pipeline samples.
What is the use case or pain point?
Make samples easy to use with just python xxxx.py
.
Is there a workaround currently?
- Use
dsl-compile
to compile a sample and run it - Edie the sample or copy the sample elsewhere to inject a
kfp.Client()
call
Love this idea? Give it a 👍. We prioritize fulfilling features with the most 👍.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Data Pipeline Architecture: Building Blocks, Diagrams, and ...
You can execute sample pipeline templates, or start building your own, in Upsolver SQLake for free.
Read more >Pipeline Syntax - Jenkins
Blocks must only consist of Sections, Directives, Steps, or assignment statements. A property reference statement is treated as a no-argument method invocation.
Read more >Using Function Specialization to Build Pipeline Variants
The sample uses various function constant values to create specialized functions that sample ... The notifyBlock block builds the three render pipelines.
Read more >Declarative Pipeline With Jenkins - DZone Refcardz
Underneath the hood, there are a few things agent causes to happen: All the steps contained within the block are queued for execution...
Read more >Generate constant value - Simulink - MathWorks
The output of the block has the same dimensions and elements as the Constant value parameter. If you specify for this parameter a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I suggest we keep v1_legacy mode as the default compilation mode for now. Some samples need to be updated, and some v2 compatible bugs needs to be fixed before it’s ready to be the default mode in our sample.
We have warning saying that v2 compatible is in beta state and many features may not work as expected. I think by the time we feel like we can remove this warning, then v2 compatible mode can be the default.
This issue has been automatically closed because it has not had recent activity. Please comment “/reopen” to reopen it.