Re: Request to become a maintainer for hockeyapp

Hi, +1 from me. The discussion in https://groups.google.com/forum/#!topic/jenkinsci-dev/LBSZruW0Lfs/ and pings in GitHub provide enough justification to transfer ownership IMHO, but let's see what others say Best regards, Oleg On Wednesday, May 9, 2018 at 10:48:31 AM UTC+2, Mez Pahlan

Re: Any plans for the github checks API?

The checks API looks great, but it seems like there is a disconnect between the all-in-one Pipeline of Jenkins and what the checks API expects to be working with. The examples in the article show elements such as linting, build, static analysis as separate and individually runnable things. In

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

Hi all, Cristoph has been pinged on April 20 in this thread.So yes, we can do the permission transfer. I have granted permissions to Kai-Hsiang and Tony. Kai-Hsiang is also a default assignee in JIRA now. In order to do a release, you will also need to update

Backporting for LTS 2.121.1 started

Backporting has started and the RC is scheduled for 2018-05-23. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.121.1-fixed Rejected: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.121.1-rejected --

Re: Any plans for the github checks API?

I'm not sure how the part about rerunning individual stages would work, but I could see rerunning the entire job from your github PR page. We sometimes have jobs where there are tests which fail occasionally, or 3rd party services are flakey, and in those cases just rerunning the job from

Re: Request to become maintainer of the Parameterized Remote Trigger Plugin

Hi Daniel, it seems no response from the owner, maybe we can start the process? Alexander Link於 2018年4月27日星期五 UTC+8下午2時55分19秒寫道： > > Hi, > > I collected all open review comments: > https://github.com/sap-production/parameterized-remote-trigger-plugin/issues/20 > We will check the urgency and

Re: Any plans for the github checks API?

On Thu, May 10, 2018 at 5:37 AM, Steven F wrote: > The examples in the article show elements such as linting, > build, static analysis as separate and individually runnable things. In > Jenkins 2.x Pipeline it feels like bundling these things together is more >

Re: [Essentials] Error Telemetry Server API JEP Draft

(replies inline) On Tue, 08 May 2018, Baptiste Mathus wrote: > Hello everyone, > > After defining how we would do the client side of error telemetry logging > in JEP-304 , I just > published a draft of the corresponding server side for

Suggestion: versioning the schema for Configuration as Code

I was thinking about this last week when I was working with Configuration as Code[0] and thinking about some of the concerns which I've seen voiced about the "right API for 1.0", especially around Credentials and some other (currently) gnarly syntax use-cases. As a user of docker-compose, I find

Re: Suggestion: versioning the schema for Configuration as Code

I had the same comment about Declarative Pipeline before it went 1.0—that every script should start with pipeline(1) { But to no avail. :-( -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop