Well, by samples I meant whatever existing implementations e.g.

https://github.com/jenkinsci/pipeline-utility-steps-plugin

public class ReadYamlStep extends AbstractStepImpl {}
public class ReadPropertiesStep extends AbstractStepImpl {}
...

I checked many plugins listed as pipeline compatible:
https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md

and was not able to find a single one that wouldn't use the deprecated API.

Without knowing the Jenkins internal processing logic and facing outdated 
plugin implementations that's a pain to develop. Salt documentation looks 
like heavenly revelations now when comparing to Jenkins' docs.

The following sentence 
from 
https://github.com/jenkinsci/workflow-step-api-plugin/#writing-pipeline-steps

"You will also need to enumerate the types of contextual objects you are 
treating as required."

Enumerate how? What contextual objects? Treating as required by what... 
 reminds me:
"Who, or why, or which, or *what*, Is the Akond of SWAT?" - just kidding.

On Wednesday, February 22, 2017 at 12:13:03 PM UTC-5, Jesse Glick wrote:
>
> On Wed, Feb 22, 2017 at 12:02 PM, sohl <[email protected] <javascript:>> 
> wrote: 
> > This is misleading. 
>
> Right, deleted. 
>
> > Sample implementations all use deprecated API 
> > (extends AbstractStepDescriptorImpl). 
>
> Sorry, which sample implementations? 
>
> > Are there are any samples of directly implementing "StepDescriptor" and 
> how 
> > to handle the 'Execution' class? 
>
> Most of `workflow-basic-steps`, though in some cases 
> `AbstractStepExecutionImpl` is still used for reasons of compatibility 
> with builds started using earlier plugin versions. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/22ffa527-bf1a-4da8-82cb-9cef9b3c23b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to