Thanks Mark. I created a simple change for review: 
https://github.com/jenkins-infra/jenkins.io/pull/2631

On Tuesday, October 29, 2019 at 9:57:42 AM UTC-7, Mark Waite wrote:
>
> There is a link at the bottom of each page, "Improve this page".  We 
> welcome contributions to the Jenkins pipeline documentation.
>
> Yes, you're correct that I should have said:
>
> The pipeline as code page teaches users how to automate the creation, 
>> execution, and deletion of pipeline jobs based on the creation and deletion 
>> of *branches*.
>>
>
> It depends what you mean by "a better place for finding this kind of 
> information".  The documentation on jenkins.io is a good starting point.  
> It includes tutorials, how-to guides, and reference material.  Specific 
> questions are asked and answered on mailing lists, in the chat systems, on 
> Q&A sites like stackoverflow 
> <https://stackoverflow.com/questions/tagged/jenkins-pipeline>, and in 
> blog posts on many locations.  Videos are available from YouTube and other 
> locations, including segments like the "Jenkins Minute 
> <https://jenkins.io/blog/2017/08/08/introducing-jenkins-minute/>" video 
> series.  Self-paced courses are available from CloudBees, Udemy, and other 
> online course systems.  Jenkins Pipeline Fundamentals 
> <https://standard.cbu.cloudbees.com/cloudbees-university-jenkins-pipeline-fundamentals>
>  
> from CloudBees is no charge (as one example).
>
> On Tue, Oct 29, 2019 at 9:54 AM Tim Black <[email protected] <javascript:>> 
> wrote:
>
>> Thanks Mark. Of course you're correct. My main problem and point to make 
>> here (and with Jenkins ecosystem in general) is that the documentation says 
>> you have to use multi-branch pipeline to use pipeline as code, whereas this 
>> is patently false. I see in my freestyle pipeline job configuration that 
>> there is an option when specifying the pipeline to use scm. This is clearly 
>> also pipeline as code.
>>
>> Also minor correction in your first paragraph, I believe you mean 
>> creation and deletion of branches.
>>
>> Thanks again. I'm curious to see if people have comments or feedback on 
>> Jenkins pipeline documentation. Is there a better place than where I have 
>> linked to above for finding this kind of information?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/cbb8a468-c4b3-4ee7-87ad-dc89dc19daac%40googlegroups.com
>> .
>>
>
>
> -- 
> Thanks!
> Mark Waite
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" 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-users/132a08d2-dcc9-4ff6-be75-f1078956291d%40googlegroups.com.

Reply via email to