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
On Mon, Oct 15, 2018 at 6:00 PM Matt Sicker wrote:
> I've thought about a JEP, yes. I'm not sure if the scope warrants it yet.
If you have to wonder, the answer is yes. :-)
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe
I've thought about a JEP, yes. I'm not sure if the scope warrants it yet.
I'm currently exploring this as a potential Outreachy mentorship project,
so it might be a bit early still.
On Mon, Oct 15, 2018 at 4:39 PM Liam Newman wrote:
> Matt,
>
> Have you considered make a JEP for this effort?
Matt,
Have you considered make a JEP for this effort? It seems like something
that would benefit from having a design document that captures how the
design was arrived at and what alternatives were considered.
-Liam N.
On Mon, Oct 15, 2018 at 2:28 PM Matt Sicker wrote:
> I've started tasking
I've started tasking out this as an epic:
https://issues.jenkins-ci.org/browse/JENKINS-54082
On Mon, Jul 30, 2018 at 10:38 AM Matt Sicker wrote:
> On Wed, Jul 25, 2018 at 6:03 PM Daniel Beck wrote:
>
>> Doesn't that just mean the listeners need to improved?
>>
>
> Either way, that would
I think this is a big +1. There were a few people who were asking about the
tool at Jenkins World last month, so the interest is pretty high.
On Mon, Oct 15, 2018 at 1:32 PM Mark Waite
wrote:
> +1 from me
>
> On Mon, Oct 15, 2018 at 2:15 PM Oleg Nenashev
> wrote:
>
>> Hi Kirill,
>>
>> Yes, the
+1 from me
On Mon, Oct 15, 2018 at 2:15 PM Oleg Nenashev
wrote:
> Hi Kirill,
>
> Yes, the project can be moved. I would even say it is a preference in this
> case. Usually we move repositories through the
> https://github.com/jenkinsci-transfer organization. If you are ready to
> do the
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
Hi Kirill,
Yes, the project can be moved. I would even say it is a preference in this
case. Usually we move repositories through the
https://github.com/jenkinsci-transfer organization. If you are ready to do
the migration, I am ready to assist.
Let's give others some time to provide feedback
I'm ready to move it to jenkinsci with no problem if it cat keep original
naming and I will have admin rights on that repo.
The process describes fork/or push model, but can it just be moved to just
have a redirect from old place?
What
On Monday, 15 October 2018 01:15:35 UTC+2, Shaun Thompson
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
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
Juseppe is widely used, and it would make sense to get it into the Jenkins
organization
I will reach out to Kirill Merkushev (the current maintainer) and ask him
whether he would like to move it to Jenkins org.
BR, Oleg
On Monday, October 15, 2018 at 5:13:46 AM UTC-7, slide wrote:
>
> It would
It would be mostly the same, there are some requirements for naming and so
forth that would be waived for a utility. Most of the process is applicable.
On Sun, Oct 14, 2018 at 10:15 PM Richard Bywater wrote:
> Would the process be the same given this isn't (I think) a plugin but more
> like a
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
*
In the config pages, there will not be a ‘build’ context variable.
What you want is to either check ‘it.descriptor’ as being the matrix
project descriptor or check ‘it’ as being the matrix project class.
But don’t even go there, in your descriptor override ‘isApplicable’ to
return false for
16 matches
Mail list logo
