Yes, Anderson, the Jenkins DSL was where I thought I would start.
That will be interesting to cover as Kotlin becomes more supported as 
another language in addition to Groovy to write build scripts in.

When you say scaling I think of spinning up a collection of containers for 
a test grid. It looks like you are also referring to multi-project builds 
and using the same binary artifacts for multiple projects. Is that what you 
are saying? I definitely want to cover multi-project builds whether in the 
introduction course or the advanced course.

I definitely want to cover artifact storage integrations. The storage 
integrations I am thinking of consists of JFrog's Artifactory, Sonatype's 
Nexus, and Docker's Docker Registry. I hadn't thought of Amazon's S3, so 
I'll add that to the list.

I don't want to go too extensively into examples on one point though I want 
to give a broad overview and rich selection of what successful products and 
teams use in our industry to automate integration and delivery processes.

On Thursday, May 26, 2016 at 4:53:10 AM UTC-6, Anderson Goulart wrote:
>
> Hi,
>
> I don't know if is pertinent, but here are my suggestions:
>
> Jenkinsfile DSL 
>
> Scaling (what are the design options for managing multiple projects? How 
> to share code between them? )
>
> Integrations (like pushing artifacts to S3)
>
>
> -- global
>
> On 25/05/2016 16:47, Kent Johnson wrote:
>
> Hi all, I am making a course on how to use Jenkins with the Pipeline 
> plugin to automate continuous integration and builds. 
> My goal is to make having a short, low-noise, high-reliability feedback 
> loop a practical possibility for the average developer.
> I am thinking this means that I would show how to use Docker to spin up 
> Jenkins locally and a test-grid locally as well as how to create or plug 
> into an existing enterprise Jenkins Pipeline build system.
>
> See this Github repo for the TOC:  
> <https://github.com/kentoj/jenkins-pipeline-course>
> https://github.com/kentoj/jenkins-pipeline-course
>
> Though I have used the Pipeline plugin (back when it was called the 
> Workflow plugin) I am not familiar with even a small fraction of the best 
> use cases for it.
>
> Will you, the other community members, help me put together a good table 
> of contents or outline for a solid three to four hour course on how people 
> could use and benefit from Jenkins with the Pipeline plugin?
>
> I understand there are many ways to use Jenkins and the Pipeline so I am 
> having to pick a small scope to begin with, though I would like to go as 
> deep as showing test reports, running tests on test grids, and doing a 
> build for every pushed branch to a repo.
>
> I would greatly appreciate any contributions to the TOC. Please submit any 
> suggestions or criticism as an issue or a pull request.
>
> I believe we can create a great course together with the time I have to 
> make it and the knowledge of this community.
> -- 
> 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 jenkinsci-use...@googlegroups.com <javascript:>.
> To view this discussion on the web visit 
> <https://groups.google.com/d/msgid/jenkinsci-users/353ea3a4-cbf6-4adc-8947-a76040714c20%40googlegroups.com?utm_medium=email&utm_source=footer>
> https://groups.google.com/d/msgid/jenkinsci-users/353ea3a4-cbf6-4adc-8947-a76040714c20%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/26002c5c-d870-4d6c-b535-177c3df228a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to