Re: Proposal: New twitter contributors

(replies inline) On Thu, 02 Jan 2020, Oleg Nenashev wrote: > Update here: We are still waiting for permissions to be granted by Tyler. > IIUC the current setup, the Tweetdeck permission management is done through > his > account, and that the permission transfer cannot be performed by other >

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

(replies inline) On Tue, 19 Nov 2019, Oleg Nenashev wrote: > As you probably know, there is ongoing work on automating Jenkins Core > releases > within the Jenkins infrastructure. Apart from Linux and Windows distributions, > there is also a OS X installer which is being produced for each

Re: [Jenkins-infra] Requesting Admin access in the jenkins-infra organization

(replies inline) On Fri, 01 Nov 2019, Oleg Nenashev wrote: > > I do not understand how come we have such repos there, but it is enough for > me to dismiss my request for full administrative access. I do not want such > kind of responsibility ATM, because my laptop is not configured for such

wiki.jenkins.io is now effectively in read-only mode

Our primary wiki has been struggling lately without sufficient or motivation from anybody in the infrastructure team to fix it or keep it alive. We have also seen increased spam attacks, which must be pain-stakingly cleaned up. As a stop-gap measure I have restricted adding pages, comments, and

Re: 2019 Elections: List of nominees

(replies inline) On Wed, 09 Oct 2019, Kohsuke Kawaguchi wrote: > As per [1]the post, here's the nominees to various positions: Thanks to Tracy and Kohsuke for pushing this along, we're definitely overdue :) -- GitHub: https://github.com/rtyler GPG Key ID:

Re: Trademark sublicense request: Jenkins Master Class

(replies inline) On Wed, 09 Oct 2019, Parker Ennis wrote: > On behalf of CloudBees, I’d like to request permission to use the following > name with ‘Jenkins’ in it: > > • Jenkins Master Class > > "Jenkins Master Class" will be a series of educational webinars hosted by > CloudBees

Ongoing partial outage on ci.jenkins.io

I'm writing this to let you all know that we're experiencing on on-going partial outage on ci.jenkins.io which is affecting the ability of the system to process pull requests and merges to plugins, core, etc. Starting sometime yesterday (2019-08-14), all attempts to provision Azure VM agents

Re: Jenkins GSoC Budget update + JEP-8 confirmation for 2019

(replies inline) On Wed, 31 Jul 2019, Oleg Nenashev wrote: > There would be a number of requests to get all the topics covered, and it > would > require a lot of overhead in the developer mailing list. Last year we have > suggested [4]JEP-8 which basically lets GSoC org admins to manage and

Re: ANN : Jenkins Governance meeting on July 31st

Thanks for sending the announcement Oleg, I'll be there :) On Mon, 22 Jul 2019, Oleg Nenashev wrote: > Hi all, > > As you probably know, Jenkins Governance meetings have been inactive for a > while. It is not a big problem for Jenkins LTS releases and SIG updates, they > work well in the

Re: What keeps CI tests from running on this Jenkinsci repository?

(replies inline) On Fri, 12 Jul 2019, 'Benjamin Beggs' via Jenkins Developers wrote: > Terrific, if you can do that it would be great. :) Sorted: https://ci.jenkins.io/job/Plugins/job/enhanced-old-build-discarder-plugin/ -- GitHub: https://github.com/rtyler GPG Key ID:

Re: What keeps CI tests from running on this Jenkinsci repository?

(replies inline) On Fri, 12 Jul 2019, 'Benjamin Beggs' via Jenkins Developers wrote: > Does anyone know why CI tests aren't running on pull requests for this > repository? > [1]https://github.com/jenkinsci/enhanced-old-build-discarder > > I've added a Jenkinsfile to the source root directory on

Re: Why don't disable DNS Multicast by default?

(replies inline) On Sun, 26 May 2019, Daniel Beck wrote: > > > > On 17. May 2019, at 12:08, Francisco Javier Fernandez > > wrote: > > > > I'm wondering if it's worth to change the default behaviour and disable it, > > so anyone who wants this feature enabled should use the > >

Re: Is there Python support for ci.jenkins.io plugin builds?

(replies inline) On Thu, 16 May 2019, Chris Kilding wrote: > I was able to substitute in the fabric8 Docker Maven Plugin to run Moto. It > seems to work fine on the Linux build agent, but the Windows agent doesn’t > like > it (no Docker host or docker.sock available.) > > Is there another

Re: Is there Python support for ci.jenkins.io plugin builds?

(replies inline) On Wed, 15 May 2019, Chris Kilding wrote: > Yep, that sounds reasonable. (I had suspected as much - there would be no end > to the possible system packages that plugin developers might want.) > > Do the ‘docker’-labelled Jenkins agents support the usual ‘dockerfile’ >

Re: Is there Python support for ci.jenkins.io plugin builds?

(replies inline) On Wed, 15 May 2019, Chris Kilding wrote: > My plugin uses an external dependency, Moto (the AWS mock server) for its > integration tests. > > Moto is written in Python, installed with Pip, in a virtualenv. It can be used > either directly (where we must do the pip install

Re: Request the access permission of repo jenkins.io

(replies inline) On Wed, 15 May 2019, Rick wrote: > I can see I'm a member of copy-editors. But I still cannot merge any PRs of > jenkins-infra/[1]jenkins.io As Olivier mentioned, copy-editors do have write permissions to this repo, but the branch protection was preventing that group from

Re: Request the access permission of repo jenkins.io

(replies inline) On Sun, 12 May 2019, Rick wrote: > Hi team, > > I would like to request the access permission of repo [1]jenkins.io. > I'm the leader of [2]Chinese Localization SIG. I believe it will be helpful to > review and merge PRs which is related to the Chinese Localization SIG faster.

Re: [INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

(replies inline) On Thu, 02 May 2019, Jesse Glick wrote: > On Thu, May 2, 2019 at 9:12 AM Oleg Nenashev wrote: > > The releases are distributed from GitHub, so they are more stable even if > > we continue downloading JDKs by URL. > > It ought to be easy to configure the (nginx?) mirror

Re: Request for Admin permission on https://github.com/jenkinsci/

Sounds good to me, prepare to be cursed with more responsibility. :) -- GitHub: https://github.com/rtyler GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this

ANN: Jenkins is joining the Continuous Delivery Foundation

We have already discussed this quite a bit in prior meetings and email threads, but today the news was made official and the Continuous Delivery Foundation (CDF) was launched. See Kohsuke's blog on the topic: https://jenkins.io/blog/2019/03/12/cdf-launch/ I'm very excited for our future

Re: jaxen

Archival in GitHub sounds reasonable to me, I presume we won't do anything in Artifactory? If everybody's fine with this, either an Infra ticket, or one of the other github admins can take care of this easily. -- GitHub: https://github.com/rtyler GPG Key ID:

Re: [DISCUSS] Switching to CentOS for Jenkins Docker base image

(replies inline) On Wed, 27 Feb 2019, Olblak wrote: > But I am wondering, instead of going with Centos why not using this PPA > with ubuntu? > This would imply a smaller breaking change I do not believe that Jenkins should rely on any PPA

Re: [DISCUSS] Switching to CentOS for Jenkins Docker base image

(replies inline) On Tue, 26 Feb 2019, Matt Sicker wrote: > Based on the details regarding Debian and Ubuntu's poor maintenance of JDK > packages, I'd support using a different distro like CentOS. That certainly > pushes myself away from defaulting to ubuntu or debian for Java Docker > images.

Re: Proposal: Automating dependency management for repositories inside the jenkinsci org

I'm game for experimenting with this :D On Thu, 21 Feb 2019, Oleg Nenashev wrote: > Dear all, > > I would like to follow-up on the Dependabot request from Jesse Glick in > INFRA-1975 . Dependabot > is a service for

Re: Request for Input: 2 weeks comment period for moving to the CDF

(replies inline) On Mon, 11 Feb 2019, Kohsuke Kawaguchi wrote: > This is the formal call for input for the decision to move the Jenkins > project to the newly forming Continuous Delivery Foundation. (I was told > that my earlier attempt >

Re: 2 weeks comment period (was: Re: A new home for Jenkins)

(replies inline) On Fri, 08 Feb 2019, Kohsuke Kawaguchi wrote: > In FOSDEM, we organized a BOF session in which we talked a bit more about > the CDF among 20-40 people who gathered. The response was good. > > Attached is the charter of the CDF >

Re: Jenkins in Outreachy May 2019 round?

(replies inline) On Mon, 11 Feb 2019, Tracy Miranda wrote: > The application period for the next round of Outreachy internships will > open in a week on Monday, February 18. > > Timeline is roughly: > Feb 18 - Mar 12: Communities sign up &

Re: Too many job in ci.jenkins.io

(replies inline) On Fri, 08 Feb 2019, Kohsuke Kawaguchi wrote: > This excessive rebuilding behaviour also causes lots of ops overhead by > eating up disk space. The disk space issues we experience are due to unaddressed scalability tickets in Jenkins Pipeline, we would be seeing them

Re: A new home for Jenkins

(replies inline) On Wed, 16 Jan 2019, Oliver Gond??a wrote: > Those are interesting news. Are we expecting to partner with existing > communities around existing CD projects as a part of CDF? Are some of them > on board with this vision or do we expect they will join us provided this > turns out

Re: Trademark sublicense requests: Jenkins Workshops

Looks reasonable to me with the "by CloudBees" suffixes On Fri, 14 Dec 2018, Tracy Miranda wrote: > Hi all, > > On behalf of CloudBees, I would like to request the permission to use the > following names that use ???Jenkins???: > > 1. Jenkins CI/CD Workshop by CloudBees > This is the name for

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

(replies inline) On Mon, 03 Dec 2018, Tracy Miranda wrote: > This sounds great. > > My preference for structure would be as 1 SIG (called Outreach or Outreach > & Advocacy) which is an umbrella for initiatives like GSoC, Outreachy, > Hacktoberfest. > > GSoC, Outreachy should maintain their own

Defining a privacy policy for Jenkins project collected data

Howdy everybody! We recently shipped weekly releases which implement the telemetry collection described by JEP-214 [0]. Behind the scenes of JEP-214, I have implemented and deployed a tool called Uplink[1] for capturing and making this telemetry data accessible to Jenkins project developers.

Re: Trademark sublicense request: TechMatrix Jenkins Platform Package

(evil top post!) This looks reasonable to me, and I've got no problem with an umbrella of "TechMatrix Jenkins Platform Package for X" so long as it's a legitimate Jenkins under there :) On Wed, 03 Oct 2018, Kohsuke Kawaguchi wrote: > On behalf of TechMatrix, Inc. I???d like to request the

Re: Add trilead-ssh2 component to the CI

i've enabled this here: https://ci.jenkins.io/job/jenkinsci-libraries/job/trilead-ssh2/ Having trouble resolving the ticket at the moment. On Wed, 03 Oct 2018, kuisathaverat wrote: > thx Jesse, I will do > > El mar., 2 oct. 2018 a las 17:42, Jesse Glick () > escribió: > > > On Tue, Oct 2,

Re: Jenkins in Hacktoberfest 2018?

(replies inline) On Mon, 01 Oct 2018, Oleg Nenashev wrote: > Hi all, > > We are live: https://jenkins.io/blog/2018/10/01/hacktoberfest/ > Let the hacking commence! Excellent work! Thanks for leading the charge Oleg, I'm looking forward to some fun hacking from everybody this month :) --

Re: Jenkins participation in Outreachy

(replies inline) On Thu, 27 Sep 2018, Andrew Bayer wrote: > Strong +1. If we have the cash available to approve the budget now, we > should definitely move forward. And if we don't, well, we should fundraise > specifically for that anyway. We definitely have ample budget for an Outreachy

Re: Jenkins participation in Outreachy

(replies inline) On Tue, 25 Sep 2018, Tracy Miranda wrote: > Hi all, > > Not sure if folks have come across the Outreachy > programme but it is one of the leading > initiatives around for getting more marginalised folks involved with open > source projects. It is

Looking forward to the Contributor Summit in SF on Monday!

I hope everybody on this list within driving distance of downtown San Francisco joins the Contributor Summit this coming Monday (17th) https://jenkinscontributorsummitsf.eventbrite.com/ (note: you don't have to buy a ticket to DevOps World Jenkins World to attend, but you must register above

Re: Unmaintained -- New Relic Deployment Notifier Plugin

(replies inline) On Thu, 13 Sep 2018, blueelvis wrote: > Hello, > > There is a plugin over here > called > > which hasn't been maintained for a long time. I tried to contact the owner > but didn't receive any

Re: Community channel on Gitter

(replies inline) On Thu, 13 Sep 2018, Tracy Miranda wrote: > We have a jenkins-community channel on irc which is a bit in decline with > low volume of discussion and spam-filled. I would like to suggest we > deprecate that channel and instead start up a Gitter channel for community > oriented

Re: Pre-JEP check: Jenkins telemetry

(replies inline) On Mon, 20 Aug 2018, Jesse Glick wrote: > On Fri, Aug 17, 2018 at 4:28 PM Daniel Beck wrote: > > When I first brought up this idea with Tyler a few months ago, IIRC the > > response (from him and/or Baptiste) was there's nothing we can > > realistically share. > > OK. I hope

Re: Growing community via a stronger Twitter presence

el & Mark for the feedback so far. > > > > I've updated the JEP based on this: > > https://github.com/jenkinsci/jep/pull/176 > > > > Please review and let me know any further thoughts. > > > > Tracy > > > > On Mon, Aug 13, 2018 at 8:22 PM, R

Re: Renaming Jenkins Essentials to 'Evergreen'

(replies inline) On Wed, 15 Aug 2018, Jesse Glick wrote: > On Tue, Aug 14, 2018 at 6:04 PM R. Tyler Croy wrote: > > The key aspect of it is _not_ the selection of > > plugins, but rather how those plugins get out there to users. > > That just means you are concealing one

Renaming Jenkins Essentials to 'Evergreen'

ook forward to chatting with many of you about Evergreen at DevOps World - Jenkins World San Francisco coming up soon :D Cheers -R Tyler Croy -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group

Re: Bill of Materials

(replies inline) On Tue, 07 Aug 2018, Oleg Nenashev wrote: > Hi Tyler, > > Thanks for the feedback! > > > > I believe the only think which needs to be resolved which is likely just an > > obsolete part of the example YAML. The root `status` key in the YAML for a > > "realized" BOM I don't

Re: Bill of Materials

(replies inline) On Mon, 06 Aug 2018, Oleg Nenashev wrote: > Hi all, > > Status update: By now Custom War Packager has been released in 1.0, and > there are also many updates in Evergreen. IMHO it is a good time to get > this story over the fence. Thanks for working to drive this to

Re: Topic for Governance Meeting Tomorrow

(replies inline) On Wed, 01 Aug 2018, Daniel Beck wrote: > FWIW https://wiki.jenkins.io/display/JENKINS/Travel+Grant+Program is still > around, even though nobody has applied in the last few years. It doesn't go > up to 2000 USD though. Weighing in with my crumbled board member hat on, I'm

Re: Upcoming JEP for usage of Incrementals repository

(replies inline) On Thu, 17 May 2018, Baptiste Mathus wrote: > Le mer. 16 mai 2018 à 13:14, James Nord a écrit : > > > So the objection I have is that as it stands in JEP-305 the versions are > > releases and these are expected to be garbage collected. > > > > Anyone also

Re: Suggestion: versioning the schema for Configuration as Code

(replies inline) On Tue, 15 May 2018, nicolas de loof wrote: > 2018-05-15 0:20 GMT+02:00 Liam Newman : > > > > > Putting all that aside (as that is not the original point of this thread), > > the original suggestion was to include a version field in the CasC YAML. > > You

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: Bill of Materials

(replies inline) On Mon, 30 Apr 2018, Jesse Glick wrote: > On Fri, Apr 27, 2018 at 12:54 PM, R. Tyler Croy <ty...@monkeypox.org> wrote: > > why not just have the full artifact URL listed > > in the Bill of Materials? For example: > > > > plugins: > >

Re: Bill of Materials

ns Essentials perspective, all I really need is an artifact ID and URL for the artifact, but I'm not sure if that's all that's needed for the other use-cases here. Just thought I would raise the question since I don't feel like I understand how to go from the Bill of Materials to binaries right now.

Re: [Essentials] Defining the client/server "update lifecycle"

A heads up on this thread, this work has become a Draft JEP: https://github.com/jenkinsci/jep/tree/master/jep/307 Of particular note since I last updated this thread is the security section which has come after a plethora of reading and reasoning on my part :)

Re: External Artifact Storage

(replies inline) On Fri, 13 Apr 2018, Carlos Sanchez wrote: > PR submitted at https://github.com/jenkinsci/jep/pull/83 Related to this work is this pull request which implements extensions to VirtualFile, which I would consider very key to this work:

Re: [Essentials] Defining the client/server "update lifecycle"

(replies inline) On Wed, 18 Apr 2018, R. Tyler Croy wrote: > > Howdy! I've been working this week to define the Jenkins Essentials > client<->server contracts for handling the _actual_ updates of Jenkins > Essentials. > > To help me organize my thoughts, I sketched ou

[Essentials] Defining the client/server "update lifecycle"

Howdy! I've been working this week to define the Jenkins Essentials client<->server contracts for handling the _actual_ updates of Jenkins Essentials. To help me organize my thoughts, I sketched out a quick draft of a JEP yesterday afternoon which can be viewed here.

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

(replies inline) On Tue, 17 Apr 2018, Oleg Nenashev wrote: > Hi, > > We are starting GSoC meetings next week. If you need somebody to dry-run > the SIG infrastructure, sign us up :) > > Reasoning: Having recorded GSoC sessions would be definitely helpful so > that we can share meetings with

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

(replies inline) On Wed, 11 Apr 2018, Ewelina Wilkosz wrote: > I must say I only briefly scanned the part with all the jenkinsci-foo and > sig-foo :( it seemed like a lot indeed. I like the rest of the document > though! but this part was almost verwhelming... > that's why I asked about SIG

Re: Upcoming JEP for usage of Incrementals repository

(replies inline) On Fri, 13 Apr 2018, Jesse Glick wrote: > Filed a draft request: > > https://github.com/jenkinsci/jep/pull/84 Jesse this is a very thorough and well-thought out document! Thank you so much for putting the effort into it. I understand that you have prototyped this work with

Re: Jenkins External Artifact Storage core changes in LTS

(replies inline) On Fri, 13 Apr 2018, Oliver Gond??a wrote: > On 2018-04-13 18:23, Carlos Sanchez wrote: > > Hi Oliver, > > > > There are some changes for core that would be really helpful to have in > > hands of people for testing sooner than later > > > >

Heads up! Jenkins is on YouTube, with more videos coming soon!

The Jenkins project has been on YouTube for a while, but I recently transitioned our channel to a "Brand Account", which means we can share permissions to post videos _much_ more easily: https://www.youtube.com/c/jenkinscicd I am hoping that we can share access, not only for the Jenkins

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

(replies inline) On Thu, 22 Mar 2018, R. Tyler Croy wrote: > > I have been looking at some of the great things the Kubernetes community has > been doing for ideas we can borrow, and one idea which really sticks out is: > Special Interest Groups (SIGs) > <https://git

Re: [Essentials] Instance Health Checking JEP: ready for first review

(replies inline) On Tue, 10 Apr 2018, Jesse Glick wrote: > I for one would find it easier to comment on a PR, but IIRC JEP > editors have discouraged this for some reason > > > ???Healthness??? is not a word???it is just ???health???. > > > I would suggest

Re: [Essentials] RFC: first cut at registration and authentication for Jenkins Essentials

://github.com/jenkins-infra/evergreen/pull/42 Since Kohsuke has added me as the BDFL delegate for this JEP, once the appropriate review has finished, I expect to mark JEP-303 as 'Accepted' by mid-next week. Thanks for all your feedback and help on this one! Cheers - R Tyler Croy -- You received

Re: HEADSUP: Breaking change for Docker Pipelines coming on ci.jenkins.io

(replies inline) On Mon, 02 Apr 2018, R. Tyler Croy wrote: > > I have put this off as long as I feel prudent, but later this week I will be > upgrading the Docker Pipeline plugin on ci.jenkins.io from 1.14 to 1.15.1 > which > will break Docker Pipelines which rely on the impl

Re: [DISCUSS] Change Jenkins default logging format

rsonal experience as an Operator, compact and easily parseable (sed/awk/perl) one-line logs are HUGELY valuable and worth any temporary heartburn some people may experience with their existing hacks. Cheers - R. Tyler Croy -- Code: <htt

Re: HEADSUP: Breaking change for Docker Pipelines coming on ci.jenkins.io

(replies inline) On Mon, 02 Apr 2018, Jesse Glick wrote: > On Mon, Apr 2, 2018 at 9:52 AM, R. Tyler Croy <ty...@monkeypox.org> wrote: > > If you have a Jenkinsfile in ci.jenkins.io that relies on > > docker.image().inside() or the equivalent in Declarative Pipeline, that &g

HEADSUP: Breaking change for Docker Pipelines coming on ci.jenkins.io

up out. If you have a Jenkinsfile in ci.jenkins.io that relies on docker.image().inside() or the equivalent in Declarative Pipeline, that Pipeline may *break* starting on Thursday, April 5th. Cheers - R. Tyler Croy -- Code: <

Re: [Essentials] RFC: first cut at registration and authentication for Jenkins Essentials

substantial progress on the implementation work, so I have proposed my JEP document for numbering and Draft status in this pull request: https://github.com/jenkinsci/jep/pull/74 Thanks for providing feedback everybody! Cheers - R. Tyler Croy

Re: [Essentials] RFC: first cut at registration and authentication for Jenkins Essentials

, the login flow is re-initiated rather than the registration flow, so I'm not sure I understand where the Man-in-the-Middle for expiry concern would come in. Perhaps something is getting lost in translation here on my end? Thanks for acting as a proxy Baptiste, and

Re: [Essentials] RFC: first cut at registration and authentication for Jenkins Essentials

requests the same, which requires a client registration and identity to kick the process off. You're absolutely right that the 'Alternative Approaches" section doesn't list this and should, I'll update shortly. Cheers - R. Tyler Croy -

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

(replies inline) On Mon, 26 Mar 2018, Daniel Beck wrote: > > > On 22. Mar 2018, at 22:04, R. Tyler Croy <ty...@monkeypox.org> wrote: > > > > I think we already have some groups, which are almost informal SIGs, such as > > Security, GSoC, Infra, etc. The asp

[Essentials] RFC: first cut at registration and authentication for Jenkins Essentials

that I'm not going to show you all just yet :) But suffice it to say, the approach generally works, just needs more tests ;) Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero&g

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

(replies inline) On Wed, 21 Mar 2018, R. Tyler Croy wrote: > Just a heads up in case anybody on this thread is interested, I've put a > hangout on the Jenkins project calendar to discuss this topic further on > Friday: > > <https://calendar.google.com/

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

(replies inline) On Thu, 22 Mar 2018, Jesse Glick wrote: > On Thu, Mar 22, 2018 at 5:04 PM, R. Tyler Croy <ty...@monkeypox.org> wrote: > > Regularly scheduled and published meetings. I can easily imagine re-using > > #jenkins-meeting or our public YouTube channel for

Request for comments: Special Interest Groups (SIGs) for the Jenkins project

ussions and contributions? If there's strong interest, I'm happy to take point on writing a Process JEP. Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: r

Re: GSOC - Office Hours 3-23-18

believe is 11pm in his/our timezone :) - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net

Re: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome

nks a lot. > > > > 2018-03-16 16:10 GMT+01:00 Jesse Glick <jgl...@cloudbees.com>: > > > >> On Wed, Mar 14, 2018 at 1:55 PM, R. Tyler Croy <ty...@monkeypox.org> > >> wrote: > >> > core and plugin upgrades can result in > >> &g

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

- R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-ke

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

better than > Liam's Cyclomatic Complexity metric because it directly tracks runtime > operations, not just code structure. I have notions how we'd accomplish > this. > > On Friday, March 16, 2018 at 6:55:58 PM UTC-4, Andrew Bayer wrote: > > > > It???s a normal step

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

with the Groovy sandbox disable * Time spent in script{} block Thanks for the ideas abayer! Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jab

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

(replies inline) On Fri, 16 Mar 2018, Daniel Beck wrote: > > > On 16. Mar 2018, at 21:28, R. Tyler Croy <ty...@monkeypox.org> wrote: > > > > * What are other metrics which would positively impact the development of > > Jenkins? > > Assuming the E

[Essentials] Collecting usage telemetry from Jenkins Pipeline

[2] https://issues.jenkins-ci.org/browse/JENKINS-49852 Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --rec

Re: [Essentials] Using non default locations for builds and workspaces (was: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome)

ystem, but rather contained in the single mounted volume, e.g.: docker run -v /srv/jenkins:/var/jenkins_home jenkins/evergreen So long as we're mounting everything through a single volume mount for the container, my concerns/requirements for JEP-301 are met. Does that make sense to you Ba(p

Re: [JENKINS-49406] Evergreen snapshotting data safety system pre-JEP: feedback welcome

severe failure for the project, and thus we need to prevent against irreversible modifications to files causing runtime failures for the Jenkins Essentials installation. Overall, I think this looks quite reasonable. I look forward to seeing the i

Re: Thoughts on sending error telemetry for Jenkins Essentials

for the ideas and feedback everybody! Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426

Re: Thoughts on sending error telemetry for Jenkins Essentials

self. Right now my primary focus is on automating the collection of useful telemetry about the system in aggregate. Once that is in place I'm happy to entertain further iterations to gather more fine-grained information. - R. Tyler Croy --

Re: Thoughts on sending error telemetry for Jenkins Essentials

(replies inline) On Sat, 17 Feb 2018, Baptiste Mathus wrote: > Le 16 févr. 2018 15:51, "R. Tyler Croy" <[1]ty...@monkeypox.org> a écrit : > > > One of the necessary details, in my opinion, to make Jenkins Essentials > [0] > successful is provid

Re: Using 'outside collaborators' to manage permissions on GitHub

epositories-in-your-organization/ > 5: https://help.github.com/articles/about-team-discussions/ > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails f

Re: Request for participation: Jenkins Security Officer candidates

ard#Officers> For more information about Jenkins CERT or our responsible disclosure policies, please see: https://jenkins.io/security/ Thanks Daniel for your continued work to make Jenkins more secure \o/ On Fri, 08 Dec 2017, R. Tyler Croy wrote: > Time flies when you're having fun, and or,

Re: Thoughts on sending error telemetry for Jenkins Essentials

(replies inline) On Fri, 16 Feb 2018, Jesse Glick wrote: > On Fri, Feb 16, 2018 at 9:51 AM, R. Tyler Croy <ty...@monkeypox.org> wrote: > > I currently define "error telemetry" to include: > > > > * Uncaught exceptions which cause the Evil Jenkins

Thoughts on sending error telemetry for Jenkins Essentials

e's something I'm missing. [0] https://github.com/jenkinsci/jep/tree/master/jep/300 [1] https://github.com/jenkinsci/jep/tree/master/jep/300#auto-update [2] For example: https://itmonitor.zenoss.com/is-your-performance-normal-how-do-you-know/ [3] ht

Re: Evergreen packaging for Jenkins Essentials

; and then we can see where that takes us. Thanks for the feedback Carlos! Cheers - R. Tyler Croy -- Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp:

Re: Accelerating Jenkins development with Jenkins Essentials

n should be "small" and just have enough code inside the container to reach out to the Evergreen hosted service layer and ask for the latest (core + plugins) before starting Jenkins. Succintly put, this would mean jenkins/evergreen would not ship with a jenkins.war. Ho

Re: Accelerating Jenkins development with Jenkins Essentials

at there's a future on the horizon filled with Kubernetes :) As to the concern about the image mutability, the evergreen-client would only be effectively changing content in the mapped `/var/jenkins_home` which must by the very nature of Jenkins be mutable. I'll update JEP-301 to make that more expl

Re: Evergreen packaging for Jenkins Essentials

(replies inline) On Wed, 14 Feb 2018, Jesse Glick wrote: > On Tue, Feb 13, 2018 at 7:03 PM, R. Tyler Croy <ty...@monkeypox.org> wrote: > > I have been thus far deriving jenkins/evergreen from > > jenkins/jenkins simply to inherit some scripts, permissions, and other bits.

Re: Accelerating Jenkins development with Jenkins Essentials

nd provide feedback. The way I am interpreting your overall feedback, and please correct me if I'm wrong, is that the direction is promising but want to encourage good fundamentals on the implementation. Anywho, thanks again :) - R. Tyler Croy ---

Re: Evergreen packaging for Jenkins Essentials

de thoughtful feedback. I'll try to improve on my delay times, work responsibilities, you know the drill. *looks wearily at google calendar* I'll try to land some updates to the prototype and these design documents with your feedback tomorrow (Feb 14th). Cheers - R. Tyler Croy ---

Re: Proposal: Add optional "Released as" and "Stage Release" states to JIRA

9 danielbeck or ogondza seem to be obvious candidates since they handle the core JIRA crap, but they didn't reply so far. Maybe you or ulli? 04:40 I don't think I spend enough time in JENKINS to rightfully quality, sorry 05:50 np - R. Tyler Croy --

  1   2   3   4   >