Re: Proposal: Pipeline Authoring SIG

[Oleg Nenashev]

GSoC is about coding, so it should be specific kind of documentarion.
W.r.t. pure docs, we will have better news soon. Stay tuned for
announcements :)

Regarding GSoC, we are looking for proposals and mentors for the next year.
Any idea will be appreciated. For example, I will submit 2 proposals soon:

- Promoted Builds Plugin equivalent for Pipeline. With new APIs, CLIs, flow
definitions and extensions
- PipelineDoc. GroovyDoc extension for Pipeline + IDE integration

Have potential menrors for rhese ideas, but more folks will be more than
welcome :)

BR, Oleg


On Fri, Nov 9, 2018, 22:19 Kristin Whetstone  For at least improving the documentation, we're looking at turning some of
> that into a GSoC project
> .
> That could definitely be expanded to cover more areas here too.  Comments
> and mentors appreciated!
>
> On Monday, October 15, 2018 at 5:12:13 AM UTC-4, Andrew Bayer wrote:
>>
>> I’d like to propose the creation of a “Pipeline Authoring” SIG, with
>> myself as the lead. The focus of this SIG would be on improving all aspects
>> of the user experience around authoring Jenkins Pipeline. This includes:
>> * Syntax and structure
>> * Extensibility, code reuse, and code sharing
>> * Testability
>> * Documentation
>> * Tooling for Pipeline authors (like Snippet Generator, Directive
>> Generator, IDE integration, etc)
>> * Best practices (including tooling for gentle nudges in the direction of
>> best practices)
>> * Examples/"starter Jenkinsfiles" for various scenarios, etc
>>
>> While at Jenkins World I was able to discuss this idea with a number of
>> people.  Response was universally positive. Here are a few examples:
>>
>> * Steven Terrana (from Booz Allen) has done work on code sharing and
>> reuse in (https://github.com/boozallen/sdp-pipeline-framework) and is
>> interested in making some form of that available to the Jenkins community.
>> * Austin Witt (from HomeAway) has created on a groovy testing framework
>> for Jenkins Pipeline (https://github.com/homeaway/jenkins-spock/)
>> * Liam Newman (from CloudBees) has written and edited quite a bit of
>> documentation for  Jenkins Pipeline and provided feedback on the design on
>> a number of Pipeline feature.  He expressed a desire to continue expanding
>> and improving on that documentation.
>> * And Kohsuke basically demanded that we do this. =)
>>
>> While this is not a large group, it was enough to convince me that this
>> is an area that deserve a SIG. There is strong interest from a number of
>> people  number and the area is also not covered by existing SIGs.
>>
>> If you’d like to be part of the initial group of participants, please
>> respond on this thread. Other feedback and suggestion are also welcome. I
>> will create the appropriate SIG pages and channels in a few days.  We can
>> start figuring out where to focus our efforts first and can schedule the
>> group’s regular meetings to start some time after DevOps World - Jenkins
>> World in Nice
>> 
>> .
>>
>> A.
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/nJ1XWyzBMSw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/3dd2137d-0c26-48e1-87f5-d3fd31cc9d83%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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCR2431MYri-013Uj2Q5PdE5Nb_5pBU2avJcFjw0Qgc5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[Kristin Whetstone]

For at least improving the documentation, we're looking at turning some of 
that into a GSoC project 
.
  
That could definitely be expanded to cover more areas here too.  Comments 
and mentors appreciated!

On Monday, October 15, 2018 at 5:12:13 AM UTC-4, Andrew Bayer wrote:
>
> I’d like to propose the creation of a “Pipeline Authoring” SIG, with 
> myself as the lead. The focus of this SIG would be on improving all aspects 
> of the user experience around authoring Jenkins Pipeline. This includes: 
> * Syntax and structure
> * Extensibility, code reuse, and code sharing
> * Testability
> * Documentation
> * Tooling for Pipeline authors (like Snippet Generator, Directive 
> Generator, IDE integration, etc)
> * Best practices (including tooling for gentle nudges in the direction of 
> best practices)
> * Examples/"starter Jenkinsfiles" for various scenarios, etc
>
> While at Jenkins World I was able to discuss this idea with a number of 
> people.  Response was universally positive. Here are a few examples:
>
> * Steven Terrana (from Booz Allen) has done work on code sharing and reuse 
> in (https://github.com/boozallen/sdp-pipeline-framework) and is 
> interested in making some form of that available to the Jenkins community. 
> * Austin Witt (from HomeAway) has created on a groovy testing framework 
> for Jenkins Pipeline (https://github.com/homeaway/jenkins-spock/) 
> * Liam Newman (from CloudBees) has written and edited quite a bit of 
> documentation for  Jenkins Pipeline and provided feedback on the design on 
> a number of Pipeline feature.  He expressed a desire to continue expanding 
> and improving on that documentation.
> * And Kohsuke basically demanded that we do this. =) 
>  
> While this is not a large group, it was enough to convince me that this is 
> an area that deserve a SIG. There is strong interest from a number of 
> people  number and the area is also not covered by existing SIGs. 
>
> If you’d like to be part of the initial group of participants, please 
> respond on this thread. Other feedback and suggestion are also welcome. I 
> will create the appropriate SIG pages and channels in a few days.  We can 
> start figuring out where to focus our efforts first and can schedule the 
> group’s regular meetings to start some time after DevOps World - Jenkins 
> World in Nice 
> 
> .
>
> A.  
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3dd2137d-0c26-48e1-87f5-d3fd31cc9d83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[夏润泽]

I'm interested 

在 2018年10月15日星期一 UTC+8下午5:12:13，Andrew Bayer写道：
>
> I’d like to propose the creation of a “Pipeline Authoring” SIG, with 
> myself as the lead. The focus of this SIG would be on improving all aspects 
> of the user experience around authoring Jenkins Pipeline. This includes: 
> * Syntax and structure
> * Extensibility, code reuse, and code sharing
> * Testability
> * Documentation
> * Tooling for Pipeline authors (like Snippet Generator, Directive 
> Generator, IDE integration, etc)
> * Best practices (including tooling for gentle nudges in the direction of 
> best practices)
> * Examples/"starter Jenkinsfiles" for various scenarios, etc
>
> While at Jenkins World I was able to discuss this idea with a number of 
> people.  Response was universally positive. Here are a few examples:
>
> * Steven Terrana (from Booz Allen) has done work on code sharing and reuse 
> in (https://github.com/boozallen/sdp-pipeline-framework) and is 
> interested in making some form of that available to the Jenkins community. 
> * Austin Witt (from HomeAway) has created on a groovy testing framework 
> for Jenkins Pipeline (https://github.com/homeaway/jenkins-spock/) 
> * Liam Newman (from CloudBees) has written and edited quite a bit of 
> documentation for  Jenkins Pipeline and provided feedback on the design on 
> a number of Pipeline feature.  He expressed a desire to continue expanding 
> and improving on that documentation.
> * And Kohsuke basically demanded that we do this. =) 
>  
> While this is not a large group, it was enough to convince me that this is 
> an area that deserve a SIG. There is strong interest from a number of 
> people  number and the area is also not covered by existing SIGs. 
>
> If you’d like to be part of the initial group of participants, please 
> respond on this thread. Other feedback and suggestion are also welcome. I 
> will create the appropriate SIG pages and channels in a few days.  We can 
> start figuring out where to focus our efforts first and can schedule the 
> group’s regular meetings to start some time after DevOps World - Jenkins 
> World in Nice .
>
> A.  
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/541fc21a-186b-4c65-bfc1-c489591e9dc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[steventerrana]

Hey Andrew,

Excited to see this being kicked off.  Let me know how I can help! 


On Monday, October 15, 2018 at 5:12:13 AM UTC-4, Andrew Bayer wrote:
>
> I’d like to propose the creation of a “Pipeline Authoring” SIG, with 
> myself as the lead. The focus of this SIG would be on improving all aspects 
> of the user experience around authoring Jenkins Pipeline. This includes: 
> * Syntax and structure
> * Extensibility, code reuse, and code sharing
> * Testability
> * Documentation
> * Tooling for Pipeline authors (like Snippet Generator, Directive 
> Generator, IDE integration, etc)
> * Best practices (including tooling for gentle nudges in the direction of 
> best practices)
> * Examples/"starter Jenkinsfiles" for various scenarios, etc
>
> While at Jenkins World I was able to discuss this idea with a number of 
> people.  Response was universally positive. Here are a few examples:
>
> * Steven Terrana (from Booz Allen) has done work on code sharing and reuse 
> in (https://github.com/boozallen/sdp-pipeline-framework) and is 
> interested in making some form of that available to the Jenkins community. 
> * Austin Witt (from HomeAway) has created on a groovy testing framework 
> for Jenkins Pipeline (https://github.com/homeaway/jenkins-spock/) 
> * Liam Newman (from CloudBees) has written and edited quite a bit of 
> documentation for  Jenkins Pipeline and provided feedback on the design on 
> a number of Pipeline feature.  He expressed a desire to continue expanding 
> and improving on that documentation.
> * And Kohsuke basically demanded that we do this. =) 
>  
> While this is not a large group, it was enough to convince me that this is 
> an area that deserve a SIG. There is strong interest from a number of 
> people  number and the area is also not covered by existing SIGs. 
>
> If you’d like to be part of the initial group of participants, please 
> respond on this thread. Other feedback and suggestion are also welcome. I 
> will create the appropriate SIG pages and channels in a few days.  We can 
> start figuring out where to focus our efforts first and can schedule the 
> group’s regular meetings to start some time after DevOps World - Jenkins 
> World in Nice .
>
> A.  
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/53df0f13-2af1-4360-b259-150a736f835a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[Oleg Nenashev]

I'm in

On Friday, October 19, 2018 at 9:10:50 AM UTC+2, Jon Brohauge wrote:
>
> I'll be there at the Contributor Summit.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/754c98bc-352e-416b-8d50-cfc6710d4244%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[Jon Brohauge]

I'll be there at the Contributor Summit.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/14792b76-b1ae-4ca8-9ce8-39b57be1e4b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[me]

I'm interested in following this group as well. 

On Monday, October 15, 2018 at 2:12:13 AM UTC-7, Andrew Bayer wrote:
>
> I’d like to propose the creation of a “Pipeline Authoring” SIG, with 
> myself as the lead. The focus of this SIG would be on improving all aspects 
> of the user experience around authoring Jenkins Pipeline. This includes: 
> * Syntax and structure
> * Extensibility, code reuse, and code sharing
> * Testability
> * Documentation
> * Tooling for Pipeline authors (like Snippet Generator, Directive 
> Generator, IDE integration, etc)
> * Best practices (including tooling for gentle nudges in the direction of 
> best practices)
> * Examples/"starter Jenkinsfiles" for various scenarios, etc
>
> While at Jenkins World I was able to discuss this idea with a number of 
> people.  Response was universally positive. Here are a few examples:
>
> * Steven Terrana (from Booz Allen) has done work on code sharing and reuse 
> in (https://github.com/boozallen/sdp-pipeline-framework) and is 
> interested in making some form of that available to the Jenkins community. 
> * Austin Witt (from HomeAway) has created on a groovy testing framework 
> for Jenkins Pipeline (https://github.com/homeaway/jenkins-spock/) 
> * Liam Newman (from CloudBees) has written and edited quite a bit of 
> documentation for  Jenkins Pipeline and provided feedback on the design on 
> a number of Pipeline feature.  He expressed a desire to continue expanding 
> and improving on that documentation.
> * And Kohsuke basically demanded that we do this. =) 
>  
> While this is not a large group, it was enough to convince me that this is 
> an area that deserve a SIG. There is strong interest from a number of 
> people  number and the area is also not covered by existing SIGs. 
>
> If you’d like to be part of the initial group of participants, please 
> respond on this thread. Other feedback and suggestion are also welcome. I 
> will create the appropriate SIG pages and channels in a few days.  We can 
> start figuring out where to focus our efforts first and can schedule the 
> group’s regular meetings to start some time after DevOps World - Jenkins 
> World in Nice .
>
> A.  
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e33dac7b-9a35-498a-9c7f-382ae3c0b4ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[Andrew Bayer]

Oh, and here's the registration link for the Contributor Summit -
https://www.eventbrite.com/e/jenkins-contributor-summit-nice-tickets-48353733318

A.

On Tue, Oct 16, 2018 at 5:00 PM Christian C.  wrote:

> I'm interested =)
>
> On Tuesday, October 16, 2018 at 4:20:21 PM UTC+2, Andrew Bayer wrote:
>>
>> Hey, interested people who'll be in Nice next week - will you be
>> attending the Contributor Summit on Tuesday? I'm thinking of trying to
>> schedule a breakout for Pipeline Authoring SIG in the afternoon on Tuesday
>> if there's sufficient interest.
>>
>> A.
>>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/fb667cb3-c195-487b-aca2-adca3cd49396%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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOZ7WYVm_W4M2RwQTkm6MCQMdgY6X2_w4EV%3Ds%3DAbSSsX-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[Christian C.]

I'm interested =)

On Tuesday, October 16, 2018 at 4:20:21 PM UTC+2, Andrew Bayer wrote:
>
> Hey, interested people who'll be in Nice next week - will you be attending 
> the Contributor Summit on Tuesday? I'm thinking of trying to schedule a 
> breakout for Pipeline Authoring SIG in the afternoon on Tuesday if there's 
> sufficient interest.
>
> A.
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/fb667cb3-c195-487b-aca2-adca3cd49396%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[Andrew Bayer]

Hey, interested people who'll be in Nice next week - will you be attending
the Contributor Summit on Tuesday? I'm thinking of trying to schedule a
breakout for Pipeline Authoring SIG in the afternoon on Tuesday if there's
sufficient interest.

A.

On Tue, Oct 16, 2018 at 11:53 AM Christian C.  wrote:

> Hi all!
>
> On Monday, October 15, 2018 at 11:12:13 AM UTC+2, Andrew Bayer wrote:
>>
>> If you’d like to be part of the initial group of participants, please
>> respond on this thread.
>>
>
> I'd be happy to join up in Nice next week @ Jenkins World! =)
> We use a competely dockerized config-as-code (jcasc) Jenkins and shared
> (Declarative) pipeline.
>
> Any efforts to simplify development of this/testing is of great interest!
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/dd60a117-11b4-4af6-b010-9b1c93c02653%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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOYSESg7gp%2BvaV1xpmraw3EoLY-o1Xc0Vy8XbhTv2OKRWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[Christian C.]

Hi all!

On Monday, October 15, 2018 at 11:12:13 AM UTC+2, Andrew Bayer wrote:
>
> If you’d like to be part of the initial group of participants, please 
> respond on this thread.
>

I'd be happy to join up in Nice next week @ Jenkins World! =)
We use a competely dockerized config-as-code (jcasc) Jenkins and shared 
(Declarative) pipeline.

Any efforts to simplify development of this/testing is of great interest!

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/dd60a117-11b4-4af6-b010-9b1c93c02653%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[Baptiste Mathus]

+1. Pipeline is now a critical component and a Jenkins sub-ecosystem on its
own so it makes sense to have something dedicated to handle it and its
future.

I guess you should include https://github.com/jenkinsci/JenkinsPipelineUnit
?

Le mar. 16 oct. 2018 à 09:58, Andrew Bayer  a
écrit :

> That would be fantastic - better documentation on jenkins.io and in
> Jenkins itself in as many languages as possible is great. =)
>
> A.
>
> On Tue, Oct 16, 2018 at 9:50 AM arch  wrote:
>
>> I could provide Chinese Pipeline documents or translation.
>>
>> On Tue, Oct 16, 2018 at 3:39 PM Andrew Bayer 
>> wrote:
>>
>>> Definitely! Both Liam and myself will be at Nice.
>>>
>>> A.
>>>
>>> On Mon, Oct 15, 2018 at 9:03 PM Jon Brohauge 
>>> wrote:
>>>
 Andrew,

 Very interesting idea. Been desperately trying to test my vars/ groovy
 scripts with varying degrees of success. I'd love to contribute where I
 can. Maybe we can meet up at Jenkins World in Nice?

 Regards
 Jon Brohauge

 --
 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 jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/61a94328-5957-4ba6-a148-1c8c7b545009%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 Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOY2eX-Q7_E2%2B1bsZ2oxbp9ujKgS6xV4vqW79TAkvYAGEA%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF6B3NCTRc22mq4KdLmXjvt4e7PYM2hyQaEydwAteUpgw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOYAwmn4GOaNhzr1Hs7pdD%2BqkERNDE8QVAwkZHySyh5CQA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7tNO6Uw357_%2BM9RU9_r8o9utkYXiYbHX26RWYgxK8YeQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[arch]

I could provide Chinese Pipeline documents or translation.

On Tue, Oct 16, 2018 at 3:39 PM Andrew Bayer  wrote:

> Definitely! Both Liam and myself will be at Nice.
>
> A.
>
> On Mon, Oct 15, 2018 at 9:03 PM Jon Brohauge 
> wrote:
>
>> Andrew,
>>
>> Very interesting idea. Been desperately trying to test my vars/ groovy
>> scripts with varying degrees of success. I'd love to contribute where I
>> can. Maybe we can meet up at Jenkins World in Nice?
>>
>> Regards
>> Jon Brohauge
>>
>> --
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/61a94328-5957-4ba6-a148-1c8c7b545009%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 Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOY2eX-Q7_E2%2B1bsZ2oxbp9ujKgS6xV4vqW79TAkvYAGEA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF6B3NCTRc22mq4KdLmXjvt4e7PYM2hyQaEydwAteUpgw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[Andrew Bayer]

Definitely! Both Liam and myself will be at Nice.

A.

On Mon, Oct 15, 2018 at 9:03 PM Jon Brohauge  wrote:

> Andrew,
>
> Very interesting idea. Been desperately trying to test my vars/ groovy
> scripts with varying degrees of success. I'd love to contribute where I
> can. Maybe we can meet up at Jenkins World in Nice?
>
> Regards
> Jon Brohauge
>
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/61a94328-5957-4ba6-a148-1c8c7b545009%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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOY2eX-Q7_E2%2B1bsZ2oxbp9ujKgS6xV4vqW79TAkvYAGEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[arch]

Great idea.

On Tue, Oct 16, 2018 at 4:32 AM  wrote:

> I'm definitely interested in being part of this as well.
>
>
> On Monday, October 15, 2018 at 2:12:13 AM UTC-7, Andrew Bayer wrote:
>>
>> I’d like to propose the creation of a “Pipeline Authoring” SIG, with
>> myself as the lead. The focus of this SIG would be on improving all aspects
>> of the user experience around authoring Jenkins Pipeline. This includes:
>> * Syntax and structure
>> * Extensibility, code reuse, and code sharing
>> * Testability
>> * Documentation
>> * Tooling for Pipeline authors (like Snippet Generator, Directive
>> Generator, IDE integration, etc)
>> * Best practices (including tooling for gentle nudges in the direction of
>> best practices)
>> * Examples/"starter Jenkinsfiles" for various scenarios, etc
>>
>> While at Jenkins World I was able to discuss this idea with a number of
>> people.  Response was universally positive. Here are a few examples:
>>
>> * Steven Terrana (from Booz Allen) has done work on code sharing and
>> reuse in (https://github.com/boozallen/sdp-pipeline-framework) and is
>> interested in making some form of that available to the Jenkins community.
>> * Austin Witt (from HomeAway) has created on a groovy testing framework
>> for Jenkins Pipeline (https://github.com/homeaway/jenkins-spock/)
>> * Liam Newman (from CloudBees) has written and edited quite a bit of
>> documentation for  Jenkins Pipeline and provided feedback on the design on
>> a number of Pipeline feature.  He expressed a desire to continue expanding
>> and improving on that documentation.
>> * And Kohsuke basically demanded that we do this. =)
>>
>> While this is not a large group, it was enough to convince me that this
>> is an area that deserve a SIG. There is strong interest from a number of
>> people  number and the area is also not covered by existing SIGs.
>>
>> If you’d like to be part of the initial group of participants, please
>> respond on this thread. Other feedback and suggestion are also welcome. I
>> will create the appropriate SIG pages and channels in a few days.  We can
>> start figuring out where to focus our efforts first and can schedule the
>> group’s regular meetings to start some time after DevOps World - Jenkins
>> World in Nice .
>>
>> A.
>>
>> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/5e9e96e9-2960-4e6c-b11c-71f3a31e8146%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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTEHqr%3DKvngujjEvgYnLRjeT0PNCmMmsj-_Dfgni0XOteg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[ben]

I'm definitely interested in being part of this as well. 

On Monday, October 15, 2018 at 2:12:13 AM UTC-7, Andrew Bayer wrote:
>
> I’d like to propose the creation of a “Pipeline Authoring” SIG, with 
> myself as the lead. The focus of this SIG would be on improving all aspects 
> of the user experience around authoring Jenkins Pipeline. This includes: 
> * Syntax and structure
> * Extensibility, code reuse, and code sharing
> * Testability
> * Documentation
> * Tooling for Pipeline authors (like Snippet Generator, Directive 
> Generator, IDE integration, etc)
> * Best practices (including tooling for gentle nudges in the direction of 
> best practices)
> * Examples/"starter Jenkinsfiles" for various scenarios, etc
>
> While at Jenkins World I was able to discuss this idea with a number of 
> people.  Response was universally positive. Here are a few examples:
>
> * Steven Terrana (from Booz Allen) has done work on code sharing and reuse 
> in (https://github.com/boozallen/sdp-pipeline-framework) and is 
> interested in making some form of that available to the Jenkins community. 
> * Austin Witt (from HomeAway) has created on a groovy testing framework 
> for Jenkins Pipeline (https://github.com/homeaway/jenkins-spock/) 
> * Liam Newman (from CloudBees) has written and edited quite a bit of 
> documentation for  Jenkins Pipeline and provided feedback on the design on 
> a number of Pipeline feature.  He expressed a desire to continue expanding 
> and improving on that documentation.
> * And Kohsuke basically demanded that we do this. =) 
>  
> While this is not a large group, it was enough to convince me that this is 
> an area that deserve a SIG. There is strong interest from a number of 
> people  number and the area is also not covered by existing SIGs. 
>
> If you’d like to be part of the initial group of participants, please 
> respond on this thread. Other feedback and suggestion are also welcome. I 
> will create the appropriate SIG pages and channels in a few days.  We can 
> start figuring out where to focus our efforts first and can schedule the 
> group’s regular meetings to start some time after DevOps World - Jenkins 
> World in Nice .
>
> A.  
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5e9e96e9-2960-4e6c-b11c-71f3a31e8146%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[Jon Brohauge]

Andrew,

Very interesting idea. Been desperately trying to test my vars/ groovy 
scripts with varying degrees of success. I'd love to contribute where I 
can. Maybe we can meet up at Jenkins World in Nice?

Regards
Jon Brohauge

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/61a94328-5957-4ba6-a148-1c8c7b545009%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[Liam Newman]

Andrew,

Thanks for taking the lead on this. 

As noted, I'm eager to talk about documenting pipeline, but talking more 
about best practices and public examples.  One example would be, 
github.com/mozilla/fxapom (and the related shared library).  I'll loop the 
maintainers of that into this thread.  

-L.

On Monday, October 15, 2018 at 2:12:13 AM UTC-7, Andrew Bayer wrote:
>
> I’d like to propose the creation of a “Pipeline Authoring” SIG, with 
> myself as the lead. The focus of this SIG would be on improving all aspects 
> of the user experience around authoring Jenkins Pipeline. This includes: 
> * Syntax and structure
> * Extensibility, code reuse, and code sharing
> * Testability
> * Documentation
> * Tooling for Pipeline authors (like Snippet Generator, Directive 
> Generator, IDE integration, etc)
> * Best practices (including tooling for gentle nudges in the direction of 
> best practices)
> * Examples/"starter Jenkinsfiles" for various scenarios, etc
>
> While at Jenkins World I was able to discuss this idea with a number of 
> people.  Response was universally positive. Here are a few examples:
>
> * Steven Terrana (from Booz Allen) has done work on code sharing and reuse 
> in (https://github.com/boozallen/sdp-pipeline-framework) and is 
> interested in making some form of that available to the Jenkins community. 
> * Austin Witt (from HomeAway) has created on a groovy testing framework 
> for Jenkins Pipeline (https://github.com/homeaway/jenkins-spock/) 
> * Liam Newman (from CloudBees) has written and edited quite a bit of 
> documentation for  Jenkins Pipeline and provided feedback on the design on 
> a number of Pipeline feature.  He expressed a desire to continue expanding 
> and improving on that documentation.
> * And Kohsuke basically demanded that we do this. =) 
>  
> While this is not a large group, it was enough to convince me that this is 
> an area that deserve a SIG. There is strong interest from a number of 
> people  number and the area is also not covered by existing SIGs. 
>
> If you’d like to be part of the initial group of participants, please 
> respond on this thread. Other feedback and suggestion are also welcome. I 
> will create the appropriate SIG pages and channels in a few days.  We can 
> start figuring out where to focus our efforts first and can schedule the 
> group’s regular meetings to start some time after DevOps World - Jenkins 
> World in Nice .
>
> A.  
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9c3d4ec0-0c98-4cc0-91d6-dd9db08c42f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.