Re: Contributing to Jenkins docker plugin

o view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDeP89g_8rYJpbTaGh9v6Y37LacE0VOW0iRWaG7wUa_Qw%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDeP89g_8rYJpbTaGh9v6Y37LacE0VOW0iRWaG7wUa_Qw%40mail.gmail.co

Re: Welcome Ewelina Wilkosz - new Jenkins Governance Board Member

o view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAMBsfbt5kOsZaC%2Bb4996a-u2_0sag1DLz7hQ4SdSH%2BK_E9c8gA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAMBsfbt5kOsZaC%2Bb4996a-u2_0sag1DLz7hQ4SdSH%2BK_E9c8gA%40mail.gmail.com?utm_medium=email

Re: Maintainer role clarification

ree. > > Cheers. > > On Thursday, February 21, 2019 at 7:18:50 PM UTC+1, nicolas de loof wrote: >> >> Hi! >> >> Over the years I've been working with Jenkins, I've come to adopt or just >> patch a few plugins. In some cases, I was only delivering a fix, not real

Re: Conditional CasC

Why not just have two distinct docker images ? Or a custom entrypoint to switch between configuration folders ? By design JCasC does not include any logic to keep being plain declarative. Le mar. 7 mai 2019 à 08:30, domi a écrit : > I’m not sure I missed something, is there any way to tell the

Re: Maintainer role clarification

+JENKINS+AND+component+%3D+timemachine-plugin> > > Would you like us to mark all these plugins for adoption and remove you as > a default assignee (or change to otheractive maintainers in some components > like Docker)? > Please do. I'd like to keep maintainer role on clever-cl

Maintainer role clarification

Hi! Over the years I've been working with Jenkins, I've come to adopt or just patch a few plugins. In some cases, I was only delivering a fix, not really adopting the plugin per-se. Many of them I've been contacted to review pull requests while I only provided a fix for a customer but don't use

Re: jenkins official kubernetes operator

> > > > I forgot to mention that plugins are separated in two groups: required by > jenkins-operator(used to configure Jenkins)(A) and required by user(B). > A: > - they are installed by jenkins-operator before Jenkins can start up > - every single change requires restart of Jenkins master

Re: jenkins official kubernetes operator

Have you checked overlap with https://github.com/VirtusLab/jenkins-operator ? I was discussing with the authors to get this contributed in jenkinsci organization. Should avoid a concurrent effort to happen on same topic. Le lun. 21 janv. 2019 à 05:54, Rick a écrit : > I'm in > > On Monday,

Re: GSoC proposal on OpenAPI REST API spec generator for Jenkins core and plugins

Le dim. 20 janv. 2019 à 03:40, martinda a écrit : > Hello, > > There is a GSoC proposal on automatically generating the Jenkins REST API > > for core and plugins, from a REST API spec generator like OpenAPI. I can

Re: jenkins official kubernetes operator

om. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/57f120ee-2691-4668-ae37-afa5ef0b8748%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/57f120ee-2691-4668-ae37-afa5ef0b8748%40googlegroups.com?utm_medium=email_source=foot

Re: A new home for Jenkins

nkinsci-dev+unsubscr...@googlegroups.com >> >> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>. >> >> To view this discussion on the web visit >> >> >> https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4z%2BQzaBc1pDtciKXH%3DMhB3vUR%3DCShiFbwy__2W6eEH_EQ

Re: jenkins official kubernetes operator

web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OYTfn4Bn_qJvtimvggJcSpHERm1m%2BTrqyV%2BVrEfYYDPg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6OYTfn4Bn_qJvtimvggJcSpHERm1m%2BTrqyV%2BVrEfYYDPg%40mail.gmail.com?utm_medium=email_source=footer> &g

Re: Any idea how to release https://github.com/jenkinsci/xstream-fork

ork` has been created by Nicolas de Loof at some point, but > > this repository has never been updated to incorporate Jenkins-specific > > patches. And I am not sure whether it has passed the full test cycle. > > There is a splitbrain between the repos, and their README files are >

JCasC requirement for plugins developers

king changes that may impact your users <https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/docs/REQUIREMENTS.md#rule-4-ping-us-in-case-of-doubts>Rule 4: ping us in case of doubts Really, if you need any assistance getting your plugin to support JCasC, want code review or an

Re: POTD: Jenkinsfile Runner

uke to do > that once the target repo is deleted > +1 > > BR, Oleg > > On Tuesday, October 2, 2018 at 5:45:38 PM UTC+2, nicolas de loof wrote: >> >> all those changes are related to my version's README.md >> <https://github.com/ndeloof/jenkinsfile-runner/c

Re: POTD: Jenkinsfile Runner

10:13 AM nicolas de loof > wrote: > > DELETE the jenkinsci/jenkinsfile-runner repository > > What about > > > https://github.com/ndeloof/jenkinsfile-runner/compare/master...jenkinsci:master > > ? That should be upstreamed first, no? > > -- > You received this

Re: POTD: Jenkinsfile Runner

milar purposes a while ago (actually >> some even weirder hacks). Obviously, a final implementation should not be >> based on Jenkins Test Harness and JenkinsRule, some Jenkins core patches >> will likely be needed. >> >> >> On Thu, Sep 6, 2018 at 3:31

jep/213 "Configuration Storage API" vs SideCar

nsParadigms") Benefit I can see doing so is that we just don't need to wait for a new jenkins-core release, this can be adopted without delay. wdyt ? -- Nicolas De Loof -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscrib

Re: Adoption of ec2-plugin

+1, this plugin need a maintainer, and it's great you can get some dedicated time for it Le mar. 18 sept. 2018 à 05:24, a écrit : > Hi, > > I would like to be maintainer of the ec2 plugin on behalf of my company > (Coveo). We have a pretty active fork (https://github.com/coveo/ec2-pl > ugin)

Re: POTD: Jenkinsfile Runner

; Let me know! >>>>>>> >>>>>>> -- >>>>>>> Kohsuke Kawaguchi >>>>>>> >>>>>> -- >>>>>> Kohsuke Kawaguchi >>>>>> >>>>> -- >>>>> Kohsuke Kawaguchi >>

credentials vs doFillxxItems collision

Hi, in a plugin I'm developing I need to let end-user configure credentials and an organisation ID selected from a list. This list is populated based on selected credentials. The issue I have is that doFillOrganisationIdItems() is invoked as form is rendered with empty credentials, seems to me

Re: service library in Jenkins

i, May 18, 2018 at 3:19 PM, nicolas de loof > <nicolas.del...@gmail.com> wrote: > > I'm not using custom-war-packager, but --commonLibFolder jenkins.war > > launcher option. > > Never heard of it, and likely does not work for this purpose. You need > an entry in `je

Re: service library in Jenkins

didn't help unfortunately. Still get NoClassDefFoundError: hudson/model/listeners/RunListener note : I'm not using custom-war-packager, but --commonLibFolder jenkins.war launcher option. Not sure this is commonly used ... 2018-05-18 18:53 GMT+02:00 nicolas de loof <nicolas.del...@gmail.

Re: service library in Jenkins

Thanks for the tip Le ven. 18 mai 2018 à 18:50, Jesse Glick <jgl...@cloudbees.com> a écrit : > On Fri, May 18, 2018 at 9:03 AM, nicolas de loof > <nicolas.del...@gmail.com> wrote: > > I'm writing an extension to jenkins that can't be packaged as a plugin > (need >

Re: Suggestion: versioning the schema for Configuration as Code

the schema at runtime... this is the > meta-schema... it says things like: Java Maps are represented by , use > the @Symbol as a , etc > > That is what the meta-schema version represents. If it changes then you > are saying the way of binding between yaml and runtime (in th

service library in Jenkins

Hi there, I'm writing an extension to jenkins that can't be packaged as a plugin (need to be ran before plugins get loaded) so I created an InitLoader as a Service @MetaInfServices public class InitListener implements InitReactorListener { @Override public void onTaskStarted(Task task)

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

users who want to rely on it can, and this doesn't close the door to an alternate approach in (near?) future. 2018-05-08 21:10 GMT+02:00 nicolas de loof <nicolas.del...@gmail.com>: > > > 2018-05-08 21:08 GMT+02:00 Liam Newman <bitwise...@gmail.com>: > >> >>

Re: Suggestion: versioning the schema for Configuration as Code

ation in yaml Would this help ? 2018-05-15 20:19 GMT+02:00 R. Tyler Croy <ty...@monkeypox.org>: > (replies inline) > > On Tue, 15 May 2018, nicolas de loof wrote: > > > 2018-05-15 0:20 GMT+02:00 Liam Newman <bitwise...@gmail.com>: > > > > > >

Re: Suggestion: versioning the schema for Configuration as Code

> or at least measure and clearly communicate how often breaks would have > occurred in the last year if CasC had been around. > Hard to tell, but probably on a regular basis. At least any time a major plugin did changed it's UI binding (DataBoundConstructor). > > -L. > >

Re: Suggestion: versioning the schema for Configuration as Code

yes indeed. But I also would like this specific seed-job support to move to job-dsl plugin, so the way this configuration element is used is directly managed by job-dsl plugin version 2018-05-13 1:36 GMT+02:00 Daniel Beck <m...@beckweb.net>: > > > On 11. May 2018, at 17:14,

Re: Suggestion: versioning the schema for Configuration as Code

onfiguration support, then have everything specific to a plugin moved to target codebase, where it can be managed in sync. 2018-05-11 23:44 GMT+02:00 nicolas de loof <nicolas.del...@gmail.com>: > > > 2018-05-11 23:02 GMT+02:00 Jesse Glick <jgl...@cloudbees.com>: > >>

Re: Suggestion: versioning the schema for Configuration as Code

2018-05-11 23:02 GMT+02:00 Jesse Glick <jgl...@cloudbees.com>: > On Fri, May 11, 2018 at 3:33 PM, nicolas de loof > <nicolas.del...@gmail.com> wrote: > > the exposed yaml model to > > configure credentials should be defined as part of credential plugin, > n

Re: Suggestion: versioning the schema for Configuration as Code

y 2018 at 17:32, Jesse Glick <jgl...@cloudbees.com> wrote: > >> On Fri, May 11, 2018 at 11:14 AM, nicolas de loof >> <nicolas.del...@gmail.com> wrote: >> > we discover "jenkins" has a "securityRealm" attribute and some >> > implementat

Re: Suggestion: versioning the schema for Configuration as Code

11 17:05 GMT+02:00 Jesse Glick <jgl...@cloudbees.com>: > On Fri, May 11, 2018 at 3:29 AM, nicolas de loof > <nicolas.del...@gmail.com> wrote: > > configuration-as-code schema depends on jenkins-core version and all > plugins > > version being installed. So generati

Re: Suggestion: versioning the schema for Configuration as Code

d before. CasC do already report unknown attributes and fail fast. But afaik there's nothing much we can offer here. 2018-05-11 9:29 GMT+02:00 nicolas de loof <nicolas.del...@gmail.com>: > not so simple : > > configuration-as-code schema depends on jenkins-core version and all >

Re: Suggestion: versioning the schema for Configuration as Code

not so simple : configuration-as-code schema depends on jenkins-core version and all plugins version being installed. So generating a "version" would be hard. Credentials syntax used in alpha is here for demonstration purpose, with minimal lines of code to provide this feature, I expect we remove

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

2018-05-08 21:08 GMT+02:00 Liam Newman : > > Just FYI: Nicolas asked a question of me in a GH comment: > https://github.com/jenkinsci/jep/commit/78bede6c731e7a85a90ca374ca1c39 > 4e219aa961#commitcomment-28894501 > > @bitwiseman Discussion on

Re: Jenkinsfile-runner + Configuration-as-Code

2018-05-01 14:59 GMT+02:00 Jesse Glick <jgl...@cloudbees.com>: > On Sat, Apr 28, 2018 at 2:46 AM, nicolas de loof > <nicolas.del...@gmail.com> wrote: > >> you still have all > >> the drawbacks of a build expressed in a weird DSL, > > > > Not my f

Re: Jenkinsfile-runner + Configuration-as-Code

me > ideas in mind, but we can try to have it somewhere else also :) ) > > On Saturday, April 28, 2018 at 8:46:18 AM UTC+2, nicolas de loof wrote: >> >> >> >> Le ven. 27 avr. 2018 à 15:46, Jesse Glick <jgl...@cloudbees.com> a >> écrit : >> >>> On

Re: Jenkinsfile-runner + Configuration-as-Code

Le ven. 27 avr. 2018 à 15:46, Jesse Glick <jgl...@cloudbees.com> a écrit : > On Fri, Apr 27, 2018 at 3:52 AM, nicolas de loof > <nicolas.del...@gmail.com> wrote: > > jenkinsfile-runner --config jenkins-dev.yaml > > This sounds useful. > > > I also have in

Jenkinsfile-runner + Configuration-as-Code

Hello there, I'm working on Jenkinsfile-runner investigating possible use-cases. A major point I've noticed with this promising tool is that most Pipeline scripts will require some initial master setup (credentials, variables, node labels, tools,

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

2018-04-18 0:42 GMT+02:00 Jesse Glick <jgl...@cloudbees.com>: > On Tue, Apr 17, 2018 at 4:45 PM, nicolas de loof > <nicolas.del...@gmail.com> wrote: > > Job class hierarchy is full of hand written JSON parsing > > I suspect such cases are fixable, which would take

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

2018-04-17 22:05 GMT+02:00 Jesse Glick <jgl...@cloudbees.com>: > On Tue, Apr 17, 2018 at 2:03 PM, nicolas de loof > <nicolas.del...@gmail.com> wrote: > > the yaml schema is for a specific version of jenkins-core + plugin. > > Any change to a plugin will change th

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

2018-04-17 17:58 GMT+02:00 Jesse Glick : > Some things that might otherwise have gotten lost in IRC. > > > About the automatic inference of symbols like `ldap` from > `hudson.security.LDAPSecurityRealm`: this seems like a nice trick to > use when prototyping the JEP, so you

Re: Draft JEP: Configuration as Code

uld watch? > > Thanks, > Eric S. > > > On Tuesday, November 7, 2017 at 3:49:59 AM UTC-6, nicolas de loof wrote: >> >> Hi, >> >> Some of you who joined Contributor Summit at Jenkins World'17 already >> know about the resurrecting effort to provide confi

Re: Accelerating Jenkins development with Jenkins Essentials

ed, 14 Feb 2018, nicolas de loof wrote: > > > Something I don't get here is why you need an external evergreen-client > to > > manage updates, and can't just get this running from within Jenkins. > > This is covered under "Alternative Approaches" here: >

Re: Accelerating Jenkins development with Jenkins Essentials

jenkins.war but won't override when used on an existing JENKINS_HOME ? And then upgrading and restarting service won't actually reflect a core upgrade ? 2018-02-14 19:26 GMT+01:00 R. Tyler Croy <ty...@monkeypox.org>: > (replies inline) > > On Wed, 14 Feb 2018, nicolas de loof wro

Re: Accelerating Jenkins development with Jenkins Essentials

2018-02-14 1:04 GMT+01:00 R. Tyler Croy : > (replies inline) > > On Thu, 08 Feb 2018, Surya Gaddipati wrote: > > > Hi, > > > > This is exciting new development. > > > > Couple of comments > > > > 1. Packaging supervisord with another executable is a docker anti > pattern. >

[configuration-as-code] JSON schema

Hi here, Just an update on configuration-as-code effort (JEP-201) I've started implementing schema generation for the configuration-as-code yaml file. it's only first iteration, so I expect some corner cases, but the main benefits is we will be able to validate this configuration without having

Re: Docker agent build script wrapper

Hi, next release of docker-plugin is going to introduce "dockerNode" keyword in pipeline, so you can create an agent from a docker image: dockerNode(dockerHost: 'unix:///var/run/docker.sock', image: 'jenkins/slave', remoteFs: '/home/jenkins') { sh 'echo "hello there"' } this is still under

Re: [configuration-as-code] Descriptors configuration

Thanks ! 2017-11-27 23:53 GMT+01:00 Jesse Glick <jgl...@cloudbees.com>: > On Fri, Nov 24, 2017 at 8:17 AM, nicolas de loof > <nicolas.del...@gmail.com> wrote: > > I'm looking if stapler can > > easily answer "does this descriptor have a global view" w

Re: [configuration-as-code] Descriptors configuration

l.jelly"); > it started working for me... > > On Friday, November 24, 2017 at 1:54:10 PM UTC+1, nicolas de loof wrote: >> >> You're right, that was a distinct (non blocking) issue. >> >> this global.jelly lookup was working for me as I had mailer plugin >> declare

Re: [configuration-as-code] Descriptors configuration

it the same issue you're talking about? > > On Friday, November 24, 2017 at 10:19:19 AM UTC+1, nicolas de loof wrote: >> >> yes indeed, for a reason I don't understand yet, >> "Jenkins.getInstance().getExtensionList(Descriptor.class)" returns an >> empty list

Re: [configuration-as-code] Descriptors configuration

be mentioned > in the documentation? > > > > On Thursday, November 23, 2017 at 3:27:19 PM UTC+1, nicolas de loof wrote: >> >> I wrote this documentation >> <https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/PLUGINS.md> >> for &g

Re: [configuration-as-code] Descriptors configuration

proach to some major plugins. 2017-11-15 16:27 GMT+01:00 nicolas de loof <nicolas.del...@gmail.com>: > this is really work in progress, i.e not even tested on my own before I > propose this in a PR :P > was just for information that I was looking into implementing a fix for > this i

Re: [configuration-as-code] Descriptors configuration

this is really work in progress, i.e not even tested on my own before I propose this in a PR :P was just for information that I was looking into implementing a fix for this idea 2017-11-15 16:24 GMT+01:00 Jesse Glick <jgl...@cloudbees.com>: > On Wed, Nov 15, 2017 at 9:51 AM, nicola

Re: [configuration-as-code] Descriptors configuration

proposed improvement to Descriptor.configure (WiP) : https://github.com/ndeloof/jenkins/tree/JENKINS-48018 *tl;dr: * provide default implementation to Descriptor#configure using databinding. reset descriptor to default values based on properties types default *or* convention to declare a public

Re: [configuration-as-code] Descriptors configuration

This is a comparable issue indeed, even this applies to updateByXml. not configure(json) https://github.com/jenkinsci/jenkins/pull/2736 is a promising approach, but is discovering attributes via reflection, while configuration-as-code is looking at ui-bound parameters. In many case they are the

Re: [configuration-as-code] Descriptors configuration

to (atomically) swap Descriptor instance in ExtensionList. Maybe this has too much impact (extensionLists Memoizer would need to be reset) ? Or maybe there's a better way to support re-configuration with @DataBound ? 2017-11-10 0:13 GMT+01:00 Jesse Glick <jgl...@cloudbees.com>: > On Thu

[configuration-as-code] Descriptors configuration

This message is a follow up for discussion on https://github.com/jenkinsci/jep/pull/31#discussion_r149598856 configuration-as-code prototype include generic mechanism to configure arbitrary jenkins component relying on @DataBound* ui-binding

Draft JEP: Configuration as Code

Hi, Some of you who joined Contributor Summit at Jenkins World'17 already know about the resurrecting effort to provide configuration-as-code for Jenkins management (JENKINS-31094) Both Praqma and CloudBees have been investigating on this topic last months, and have wrote prototypes to cover

Re: Request to become maintainer on docker-plugin

2017-09-06 16:15 GMT+02:00 Jesse Glick : > On Tue, Sep 5, 2017 at 8:28 PM, Oleg Nenashev > wrote: > > […] while it's still compatible with Docker Plugin use-cases > > One of my reservations about both the `docker-plugin` and the >

Re: Request to become maintainer on docker-plugin

3 GMT+02:00 Nigel Magnay <nigel.mag...@gmail.com>: >> >>> Please - go for it. I don't have the bandwidth these days to support it >>> in anything like a timely manner. >>> >>> On Tue, 5 Sep 2017 at 18:20, nicolas de loof <nicolas.del...@gmail.com> >>

Request to become maintainer on docker-plugin

Hi folks, docker-plugins as 20 pull requests pending for review and no new commits since Nov 16th. I volunteer to adopt this plugin. Especially I'd like to have docker-plugin support docker swarm mode, so it can distribute builds on a cluster out of the box. Github-ID: ndeloof Jenkins-ID:

Re: Status of docker-slaves-plugin

rd. > > On Mon, 10 Jul 2017 at 22:22 nicolas de loof <nicolas.del...@gmail.com> > wrote: > >> Hi Richard, >> >> We indeed aren't very active on this plugin, due to various other >> business activity >> There's various aspect of this plugin that we w

Re: Status of docker-slaves-plugin

Hi Richard, We indeed aren't very active on this plugin, due to various other business activity There's various aspect of this plugin that we want to improve, most significant one being to fabric8io/docker-client as a client library so we don't have to use external docker CLI to interact with

few broken artifacts in jenkins' maven repo

Doing some work related to plugin management, I noticed some minor issues with repo.jenkins-ci.org https://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/job-dsl/1.33/job-dsl-1.33.hpi is actually a pom.xml

lost permission to write on jenkinsci/docker-ssh-slave

Hi, I'm declared as maintainer on jenkinsci/docker-ssh-slave docker image but don't have write permission on the github repo https://github.com/jenkinsci/docker-ssh-slave not sure where to request this. IIUC https://github.com/jenkins-infra/repository-permissions-updater/tree/master/permissions

Re: maintainer requests

oh, sorry for that, I'm used with typos on my name :P 2016-11-01 20:57 GMT+01:00 Daniel Beck <m...@beckweb.net>: > > > On 01.11.2016, at 18:57, nicolas de loof <nicolas.del...@gmail.com> > wrote: > > > > I don't maintain NodeJS plugin, so feel free to take ov

Re: maintainer requests

I don't maintain NodeJS plugin, so feel free to take over 2016-11-01 18:39 GMT+01:00 Daniel Beck : > > > On 01.11.2016, at 12:58, Greg Langston wrote: > > > > Thanks guys. Anything else you need from me to finalize? > > I'd like to know which of the

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

ased on what > Jenkins deploys ? Ok with docker it is simpler to create an image with > several JDKs and the configuration file hardcoded (in that case the > challenge is to choose the docker plugin to use ..) > > > Le samedi 29 octobre 2016, nicolas de loof <nicolas.del...@gmail.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

... or rely on tool chain, that has been designed to cover this exact issue. Didn't we had this debate few days ago ? Le 29 oct. 2016 9:48 AM, "Arnaud Héritier" <aherit...@gmail.com> a écrit : > If you don't use the maven evil job type > > Le samedi 29 octobre 2016, nic

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Jenkins can require Java 8, but needs to support building arbitrary Java project, even jdk 1.0 ;) Le 29 oct. 2016 1:40 AM, "Martina" a écrit : > btw. game-of-life that we all dearly love for demos only runs with jdk7, > not jdk 8, at least the master branch does.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

Have just read Java 9 is postponed to 2017/07/27, give us some extra time to look into this 2016-10-19 7:47 GMT+02:00 nicolas de loof <nicolas.del...@gmail.com>: > @Oleg I totally agree we need to investigate java 9 support - for your > information, jenkins doesn't boot on java9

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

@Oleg I totally agree we need to investigate java 9 support - for your information, jenkins doesn't boot on java9+jigsaw, see https://github.com/x-stream/xstream/issues/74 2016-10-18 23:42 GMT+02:00 Oleg Nenashev : > Weak -1 regarding JDK8, but the opinion is not that

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

is there a jira issue to track this ? I've been running jenkins on Java 8 without issue so far, so wonder about this runtime issue. 2016-10-14 13:20 GMT+02:00 Kanstantsin Shautsou : > Jenkins still has guice-beta that randomly fails under java8. > > -- > You received

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

<m...@beckweb.net>: > > > On 14.10.2016, at 09:10, nicolas de loof <nicolas.del...@gmail.com> > wrote: > > > > About system that don't have Java 8 in official repo (RHEL5, Debian > Wheezy, Ubuntu 14.04 LTS). > > Are you saying that RHEL 6 + 7, Debian Je

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

My +1 for Java 8 (as I have been advocating for this for 2.0 already) About system that don't have Java 8 in official repo (RHEL5, Debian Wheezy, Ubuntu 14.04 LTS). Oracle do provide official JDK builds as DEB/RPM, so I can't see this as a blocker. For sure there's IT department, one need to

Re: Setting CMS or G1 as the default GC algorithm for Jenkins?

+1 2016-10-06 23:29 GMT+02:00 Samuel Van Oort : > Hi guys, > I'd like to propose that we explicitly set the Java args for the Jenkins > packages to use either Concurrent Mark Sweep or G1 as the default GC > algorithm. > > The reason for this is that Jenkins is generally

Re: Manage our forks as ... git forks

..@batmat.net> wrote: > > So, anyway, now we know. It's not possible to attach a fork afterwards > <https://twitter.com/GitHubHelp/status/783018024056029184>. > > 2016-10-03 14:52 GMT+02:00 nicolas de loof <nicolas.del...@gmail.com>: > >> I'm not sure we can

Re: Manage our forks as ... git forks

Kanstantsin Shautsou <kanstantsin@gmail.com>: > I mean utilise existing repo instead of creating new. Everything the same > that would be done in new repo, but in old. > > On Oct 3, 2016, at 15:40, nicolas de loof <nicolas.del...@gmail.com> > wrote: > > Not sure

Re: Manage our forks as ... git forks

itter to see if they have >>> an answer. Might be possible, since the contrary is and we regularly ask >>> them to "break" fork links. >>> >>> 2016-10-03 13:03 GMT+02:00 Kanstantsin Shautsou <kanstantsin.sha@gmai >>> l.com>: >>&

Re: Manage our forks as ... git forks

u <kanstantsin.sha@gmai >> l.com>: >> >>> +1 Url in top of page should be enough imho. >>> Maybe name repository `xstream-jenkins` as project do `-jenkins` >>> releases? >>> >>> On Monday, October 3, 2016 at 11:16:17 AM UTC+3, nicolas de loof w

Re: Manage our forks as ... git forks

ory under an entirely new name (like xstream-fork)? > > Other than that minor item, I think it is an interesting idea to clearly > show projects which are forks of an upstream project. > > Mark Waite > > On Fri, Sep 30, 2016 at 2:32 PM nicolas de loof <nicolas.del...@gma

Re: Docker workflow runs with user not fully configured

This indeed is required so the actual files on workspace don't get corrupted by user IDs/premissions that only exist in your container. You should configure your container to relax permission and let arbitrary user run your build tools 2016-09-02 12:05 GMT+02:00 Oliver Gondža

Re: Backporting for 2.7.1 has started

ed from one-shot-executor plugin. Not sure how @Restricted works, but seems this would block this usage, right ? Then will need to wait for a future LTS. > If it works, I think backporiting into .2 may be justified. > > 2016-06-09 18:07 GMT+02:00 nicolas de loof <nicolas.del...@gmail.co

Re: Backporting for 2.7.1 has started

Any chance for https://github.com/jenkinsci/jenkins/commit/310c952602f7241cb74454b7e7fb2be0bf3d2980 to be backported ? https://issues.jenkins-ci.org/browse/JENKINS-34923 not even released yet, so I would be fine if you answer "no way", but this is a minor code change (new event on RunListener)

Re: Trouble building Blue Ocean

I have the docker image running locally and can't see any broken link. Could you please give more details ? screenshot ? 2016-05-30 8:52 GMT+02:00 Michael Neale : > Hrm, what are some links that you see broken? I have seen it run on / > before - I wonder if the image has

Re: [Blue Ocean] New UX project for jenkins

yes indeed, see https://github.com/jenkinsci/blueocean-plugin/pull/1/files/d14ffb3f68d4b21f76bd1b800fb74c5806e97db8#r64960271 2016-05-27 18:04 GMT+02:00 Tom Fennelly : > I think Nicolas already has something cooked up and ready to go for this. > We'll let you know when

Re: Patching Groovy?

Based on the high number of forked library Jenkins do already rely on, which make maintenance a hard job to keep in sync with upstream / get patches approved, I'd prefer to postpone groovy update and wait for 2.4.7 2016-05-20 20:14 GMT+02:00 Daniel Spilker : > OK, sounds

Re: Question about the docker-pipeline plugin

using > plein Docker CLI? > > > > Le mardi 15 mars 2016 18:10:24 UTC+1, nicolas de loof a écrit : >> >> docker-pipeline does rely on docker-exec to enter a container an run >> commands inside it, so the jenkins slave remoting still applies to the >> hosti

Re: Question about the docker-pipeline plugin

docker-pipeline does rely on docker-exec to enter a container an run commands inside it, so the jenkins slave remoting still applies to the hosting node. this was inspired by Docker Custom Build Environment Plugin (aka Oki Docki plugin) Main benefit is you can run arbitrary docker image, you

Re: Maintenance of S3 Plugin

Added Jimilian as a GitHub committer for repository s3-plugin Thanks for taking care of this plugin 2016-03-15 8:19 GMT+01:00 Alex A : > Hi everyone! > > In our company we are using Jenkins and S3 plugin very hard. We already > have a lot of improvements >

Re: One-Shot Executors

we want to distinguish error due to job misconfiguration (bad docker image ID for sample) and infrastructure issue (no available resources) 2016-03-10 19:58 GMT+01:00 Suckow, Thomas J : > > > On 3/9/16, 12:40 PM, "jenkinsci-dev@googlegroups.com on behalf of Jesse > Glick"

[GSoC2016] Interested in Integration of Docker plugins

Hi ! Yoann and I, who applied as mentors on this topic, both live in Rennes, so we could easily discuss this in mode details. Our plan is to investigate how Jenkins could better rely on a Docker infrastructure. We already have some proof-of-concept code, but now need to inject into jenkins-core

Re: One-Shot Executors

some extra physical nodes. 2016-03-09 23:32 GMT+01:00 nicolas de loof <nicolas.del...@gmail.com>: > " > I do agree that certain issues should fail immediately (image not found). > Certain other issues should perform exponential backoff (Cloud > infrastructure down). Pr

Re: Updating from cloudbees docker build and publish v1.0.1 to v1.1 causes docker build failures.

looks to me the plugin didn't correctly handle legacy data migration in 1.0 dockerfilePath was used to store the build context - as there was only one possible dockerfile the variable name looked good in 1.1, support for --file was introduced by changing the meaning of this field, and adding

Re: One-Shot Executors

" I do agree that certain issues should fail immediately (image not found). Certain other issues should perform exponential backoff (Cloud infrastructure down). Provisioning limits could be annoying though, would be interesting if they could be left in the queue until Jenkins side provisioning

Re: [GSoC 2016] Integration of Docker plugins with Jenkins 2.0 features

You're right, Jenkins is higly tied to it's remoting agent. We have workaround for some calls (like launching a process) but generally speaking we need this agent running on slave. Yoann and I have developed an alternate approach based on a set of containers (aka a "pod") here one of them comes

Re: One-Shot Executors

was you (the > person that never worked on this plugin) then i would be glad to see the > list of plugins what you maintain and ensure that you also removed from all > unrelated teams. Would it be fair? Either i would request descriptions to > the Jenkins Board. > > On M

  1   2   3   4   5   >