Re: Looking to join maintainership of ec2-plugin

@Matt thanks for the offer. As per the approval of Fabrizio, I've just added you as a committer. As usual, remember this ^ is only for commit / merge access. If you wish to be able to release, you'll want to go through the PR into the release permissions repo.

Re: Jenkins participation in Outreachy

+1 definitely worth doing. Le mar. 25 sept. 2018 à 17:58, Tracy Miranda a écrit : > 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 >

Re: Commit access for ease-plugin

Hello, please file a PR in the permissions repository, and get approval from at least one of the previous maintainers. Thanks Le mar. 25 sept. 2018 à 23:19, Robert Friedman a écrit : > Hello, I would like to get commit access to the plugin > https://plugins.jenkins.io/ease-plugin. My company

Re: Adoption of ec2-plugin

e questions and I will try and >> be responsive. And welcome! >> >> On Wed, 19 Sep 2018 at 19:04, Baptiste Mathus wrote: >> >>> +1. >>> >>> Added Fabrizio to this thread, the current maintainer. >>> (And Francis, the previous maintainer

Re: Adoption of ec2-plugin

+1. Added Fabrizio to this thread, the current maintainer. (And Francis, the previous maintainer FYI, who said IIUC though he was not able to commit to much anymore, he was still interested to keep his commit rights in case this comes back). @Fabrizio, and Francis: what do you think? Seems like

[Evergreen] Update to the snapshotting / "safe upgrade" JEP 302

Hello everyone, I'm adding more thoughts about JEP 302 and the real meat I'm digging into only since some days. Thoughts and challenges around upgrading and rolling back Jenkinses automatically correctly. FYI https://github.com/jenkinsci/jep/pull/199 Again, the current WIP addition is more

Re: Pre-JEP check: Jenkins telemetry

Hello Daniel, A few thoughts: * How does this relate to JENKINS-32485 ? I seem to understand it could well cover it, apart from the required end date? * "Time period (start and end date) during which data collection is enabled on the client

Re: POTD: Jenkinsfile Runner

+1 for cleaning up. Like we recommend for plugins, it would be nice that canonical repo location is more clearly the one under jenkinsci org Le jeu. 6 sept. 2018 à 15:24, Oleg Nenashev a écrit : > Hi all, > > It seems we have a splitbrain issue in this project. > Currently there is the

Re: Jenkins: Shifting Gears

Side tracking a bit, sorry, beat with me. Not sure for others, but > suggest we don't turn this into a mega thread of everything that no one can keep track of Might also have not had the expected effect. I think mega-threads, though sometimes hard indeed to follow, also show the level of

Re: Bitbucket Branch Source Plugin Maintainer

Commit access is still only granted by the bot. As Michael said. As Antonio approved it, I just granted casz commit access to the plugin. As usual, the invitation must be accepted first so it takes effect. [23:16] <+ batmat> | jenkins-admin: hello old friend [23:16] <@jenkins-adm> | Hello

Re: Adopt a plugin

> have reached out to Lars Sjostrom Any evidence for this somewhere? This element can obviously reduce the timeout period (which BTW out of this context as it stands would not have *really* started yet as the current maintainer(s) is not in CC). Le sam. 1 sept. 2018 à 02:46, Marky Jackson a

Re: Amazon ECR plugin does to adoption

I see both wiki pages (this plugin and the subversion one) are already marked as to be adopted, so perfect. Thanks a lot for your efforts Ivan, and thanks for informing people about this! Le mer. 29 août 2018 à 12:16, Ivan Fernandez Calvo a écrit : > Hi all, > > I am not interested to maintain

Re: Proposal: Modify Plugin Adoption process to use JIRA to track adoption status

I like that idea, and I agree having a clearer way to track ongoing requests, so that they're not forgotten would be great. It's especially important IMO since people requesting to become maintainers may often be somewhat newcomers that won't necessarily dare asking twice if we miss or forget the

Re: Hangouts Chat Plugin

Hey folks, If, as you seem to, would like your work to get a bigger audience, you probably want to look into how to host it under the official Jenkins update center. We generally kindly ask people to do a best effort to add features to existing plugins, but in case this proves impractical, we

Re: Adopting jUnit Attachments Plugin

Le jeu. 9 août 2018 à 23:47, Jesse Glick a écrit : > On Thu, Aug 9, 2018 at 12:57 PM Oleg Nenashev > wrote: > > Should I also change the default assignee in JIRA? > > I have no opinion about that. Generally I find the default assignee > option to be a bad idea—you should assign an issue to

Re: Google Driver Uploader Plugin

Hello, You can file an issue in the Jenkins jira for this purpose. In the 'HOSTING' project. Google for "Jenkins hosting plugin" to find the associated docs on the wiki. Cheers! Le mer. 8 août 2018 à 18:48, Mustafa Kuloglu < mustafa.kulo...@generalmobile.com> a écrit : > Hi, > Of course we

Re: Docker Swarm plugin evolutions

Hello Gabriel, Did you consider adopting this plugin and take over its maintenance? Didn't check for that plugin, but if you didn't get an answer since long, then maybe it's time to start the process. Cheers Le mar. 14 août 2018 à 14:44, Gabriel Augendre a écrit : > Hello, > > I made several

Re: [Essentials] First Install User Experience

n Fri, 27 Jul 2018, Baptiste Mathus wrote: > > > Hello folks, > > > > For Jenkins Essentials > > <https://jenkins.io/blog/2018/04/06/jenkins-essentials/>, we want to > > provide an easy out of the box experience for running Jenkins. > > > > Currently

Re: Topic for Governance Meeting Tomorrow

Belated, but I'm all for supporting travel grants for active contributors. Mandy is in my opinion definitely eligible to that definition. Le jeu. 2 août 2018 à 12:47, Oleg Nenashev a écrit : > Hi all, > > Just to summarize the yesterday's governance meeting (log >

Re: Upcoming JEP for usage of Incrementals repository

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 wanting to consume incrementals via a proxy would need to > write tooling

Re: Error

Hello, Answered there, let's keep the discussion where the issue happens generally. Cheers Le jeu. 17 mai 2018 à 09:13, Rahul Pure a écrit : > Hi > > getting this error while apply for pull request to publish the plugin > > >

Re: [Essentials] (client) Error Telemetry logging: JEP in early draft review

. Feel free to provide feedback here or on the PR. https://github.com/jenkinsci/jep/pull/105 Thanks! Le jeu. 5 avr. 2018 à 11:02, Baptiste Mathus <m...@batmat.net> a écrit : > Submitted as https://github.com/jenkinsci/jep/pull/77 > > Thanks everyone for the feedback. > > 2018

Re: [Essentials] Error Telemetry Server API JEP Draft

rence/find a log in the system between client and server if needed?" -- Baptiste Le ven. 11 mai 2018 à 00:54, R. Tyler Croy <ty...@monkeypox.org> a écrit : > (replies inline) > > On Tue, 08 May 2018, Baptiste Mathus wrote: > > > Hello everyone, > > > >

[Essentials] Error Telemetry Server API JEP Draft

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 review: https://github.com/batmat/jep/tree/JENKINS-51140/

Re: Using JEP process for future design changes to Declarative Pipeline?

Sure, why not? I don't think JEP are designed to be limited to core. But yes definitely we need to encourage more plugin developers to go through this process for the benefit of everyone wrt to (hopefully) engagement and more fluidity once validated by more eyes. Le mer. 2 mai 2018 à 17:20,

Re: ANN: Welcome Google Summer of Code 2018 students!

Welcome folks! Le jeu. 26 avr. 2018 à 22:58, Kohsuke Kawaguchi a écrit : > Woohoo! Welcome!! > > I love that you guys are from all over the world. In the past years, I had > the pleasure of mentioning some of the GSoC projects in Jenkins World > keynotes, and other projects

Re: [Newbie] Declarative Pipeline agent/docker directive causing script.sh not found error

Please use the users ML for this kind of questions. Thanks! Le mar. 24 avr. 2018 à 22:06, Calvin a écrit : > New Item > Pipeline > Pipeline script > > pipeline { > agent { docker 'maven:3-alpine' } > stages { > stage('Example Build') { > steps

Re: AtomicFileWriterTest fails

ain! Baptiste 2018-04-19 17:08 GMT+02:00 Jonathan Bergh <bergh.jonat...@gmail.com>: > @Baptiste I am happy to do that. > > Basically we are looking at a clone and build? > > Best regards > Jonathan > (Github @trijonb) > > On Thursday, 19 April 2018 15:51:54 UTC+2, Baptist

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

Just submitted the PR as draft as https://github.com/jenkinsci/jep/pull/91 Feedback still more than welcome. Cheers 2018-04-11 18:55 GMT+02:00 Baptiste Mathus <m...@batmat.net>: > Good point. I just addressed it in the proposal and the Essentials tests. > > The proposal is

Re: AtomicFileWriterTest fails

sy with a release coming up next week and trying to >> get up and running with the project in between. >> >> best >> jonathan >> >> On Tuesday, 17 April 2018 11:19:40 UTC+2, Baptiste Mathus wrote: >>> >>> Filed as https://github.com/jenkinsci/jenkins/pu

Re: Upcoming JEP for usage of Incrementals repository

2018-04-19 13:12 GMT+02:00 Baptiste Mathus <m...@batmat.net>: > Hello, > > Finally took some time to review the JEP 305, thanks a lot again Jesse for > that big step forward, here's some feedback: > > * About using Maven CI Friendly Versions > <https://maven.apa

Re: Upcoming JEP for usage of Incrementals repository

Hello, Finally took some time to review the JEP 305, thanks a lot again Jesse for that big step forward, here's some feedback: * About using Maven CI Friendly Versions : I guess we should then add also *RequireMavenVersion* 3.5+ shouldn't we? *

Re: AtomicFileWriterTest fails

Filed as https://github.com/jenkinsci/jenkins/pull/3397 @Jonathan, I would have requested your review there too, but didn't have your GitHub handle. thanks 2018-04-17 10:57 GMT+02:00 Baptiste Mathus <m...@batmat.net>: > Fine by me. > > But then my only question left is: should w

Re: AtomicFileWriterTest fails

Fine by me. But then my only question left is: should we request INFRA to change our Windows agents on ci.jenkins.io so that they are configured differently/more like a target environment and less like a dev machine? Since, again, those tests did run correctly there and I guess we would like them

Re: External Artifact Storage

Posted a small comment/request for clarification on the merged PR, but otherwise LGTM. 2018-04-13 17:38 GMT+02:00 Carlos Sanchez : > PR submitted at https://github.com/jenkinsci/jep/pull/83 > > On Fri, Apr 13, 2018 at 5:24 PM, Oleg Nenashev > wrote: >

Re: Request to be made a maintainer of audit-trail-plugin

Hello, As Oleg said, this repo is maintained by Oliver, an active member of the community. So we would strongly prefer to get an answer from him here before moving forward. Also, in any case, the usual request timeout for taking over maintainership is two full weeks, so please be patient.

Re: Request to be made maintainer of platformlabeler plugin?

Done and done. Merged the PR, and : [09:39] <+ batmat> | jenkins-admin: make markewaite committer on platformlabeler-plugin [09:39] <@jenkins-adm> | Added markewaite as a GitHub committer for repository platformlabeler-plugin. Thanks Mark! 2018-04-11 15:32 GMT+02:00 Mark Waite

Re: AtomicFileWriterTest fails

Yeah, introduced in https://github.com/jenkinsci/jenkins/commit/4f2e2615055 / https://github.com/jenkinsci/jenkins/pull/2548 Just checked, and though the PR history is now deleted, I'm pretty sure the CI did run on Windows for this too. So there must be a reason why this works or not under some

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

Good point. I just addressed it in the proposal and the Essentials tests. The proposal is updated: https://github.com/batmat/jep/tree/JENKINS-50294/jep/ FTR, the associated PR on Essentials side: https://github.com/jenkins-infra/evergreen/pull/52 I chose to go with /instance-identity,

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

I am fine and love the general idea of giving us progressively more useful structure as we grow, to help make it easier for people to feel welcome to contribute without feeling overwhelmed. Also fine by me the meetings part, recording it makes sense indeed, for people interested, but unable to

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

2018-04-11 8:50 GMT+02:00 Ewelina Wilkosz : > Good job! > > I'll just comment what I think could be clarified, really small things... > > - "Record SIG meeting, such as via YouTube Live Streaming, and make it > publicly available. Text-based meetings can use #jenkins-meeting

Re: TODO-Plugin guidance

Cool you're trying this! Welcome! You should follow https://jenkins.io/doc/developer/tutorial/create/ then IIUC you will want to choose the (as of now) choice number 2: "2: remote -> io.jenkins.archetypes:hello-world-plugin (Skeleton of a Jenkins plugin with a POM and an example build step.)"

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

Sorry, the right link is https://github.com/batmat/jep/tree/JENKINS-50294/jep/ 2018-04-10 14:09 GMT+02:00 Baptiste Mathus <m...@batmat.net>: > Hello everyone, > > Just published the draft of the JEP for the "Essentials Instance Client > Health Checking", it is rea

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

Hello everyone, Just published the draft of the JEP for the "Essentials Instance Client Health Checking", it is ready for, and warmly welcoming, review: https://github.com/batmat/jep/blob/JENKINS-50294/README.adoc To sum up, this will be the *component* used to decide if we trigger a rollback

Re: Startup deadlock when using a GlobalConfiguration + Initializer < JOB_LOADED

AIUI, interesting to read and related: https://www.cloudbees.com/blog/jenkins-plugin-developer-case-files-episode-1-when-extensions-bites-you-posterior 2018-04-10 12:26 GMT+02:00 Julien HENRY : > My point was to clarify the specific case of GlobalConfiguration. I'm

Re: BUG REQUEST : QUALITY GATES PLUGIN SONAR

Please use the users list for such requests. Thank you Le lun. 9 avr. 2018 à 16:58, Virginia Mesa a écrit : > Hi, > > It takes a while for me to get the Sonar QG plugin. I do not know if > someone else will happen, install the new version (2.73) to see if it was >

Re: [DISCUSS] Change Jenkins default logging format

2018-04-04 18:12 GMT+02:00 Oleg Nenashev : > Hi Baptiste, > > Anyone can easily change the logging format in Jenkins by passing custom > J.U.L properties file. > Yes. But in practice, I'm convinced virtually nobody does this. > So it should not be a problem to change

[DISCUSS] Change Jenkins default logging format

Hello everyone, Having worked on more things related to Jenkins logging recently, I've had the opportunity to remember my past pain when I was operating a Jenkins instance and sending logs to an ELK cluster. Compared to almost everything else in the infrastructure, the logstash rules for Jenkins

[Essentials] (client) Error Telemetry logging: JEP in early draft review

Hello everyone, So as a followup on the recent discussions around telemetry logging for Essentials, I've drafted a JEP on this matter I would love to get feedback on: https://github.com/batmat/jep/tree/JENKINS-49805/jep/ Thanks! -- Baptiste -- You received this message because you are

Re: [Essentials] Error Telemetry logging: how to do it (was: Re: Thoughts on sending error telemetry for Jenkins Essentials)

a JSONFormatter for easier consumption/parsing by the evergreen-client, so we definitely need a place to put those. I'll start or fork a dedicated thread to discuss implementations choices. Or someone feel free to do it if having any feedback to provide. 2018-04-03 11:30 GMT+02:00 Baptiste Mathus &l

Re: [Essentials] Error Telemetry logging: how to do it (was: Re: Thoughts on sending error telemetry for Jenkins Essentials)

2018-04-02 15:27 GMT+02:00 Jesse Glick <jgl...@cloudbees.com>: > On Fri, Mar 30, 2018 at 11:15 AM, Baptiste Mathus <m...@batmat.net> wrote: > > SocketHandler is unusable for real life IMO: any loss of connection will > not be reconnected. > > So we need to develop s

[Essentials] Error Telemetry logging: how to do it (was: Re: Thoughts on sending error telemetry for Jenkins Essentials)

Hello, (Changing the subject also because I don't think it's strictly necessary for people to read the previous thread to be able to provide help/feedback here). I've started working on https://issues.jenkins-ci.org/browse/JENKINS-49805, and the tests I've done so far led me to see two possible

Re: Backporting for LTS 2.107.2 started

Late +1 for JENKINS-49737 Le 28 mars 2018 11:02, "Daniel Beck" a écrit : > On 28. Mar 2018, at 10:29, Oleg Nenashev wrote: > > Maybe we also want to backport JENKINS-49737 ("Extras Executable WAR should warn everybody that Java 9+ is not supported")

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

d require some registration), and > validate those clients based on a certificate signed by the server. If > so, you are back to a standard PKI. > > There is no magic bullet... > > > Le 27/03/2018 à 09:24, Baptiste Mathus a écrit : > > (Adding in CC Emmanuel Lécharny <htt

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

(Adding in CC Emmanuel Lécharny , who took a look at the proposal) Trying to summarize our chat on Twitter, I see two outstanding points: * Emmanuel is rightly questioning/concerned about the potential of DDoS for this JEP. Tyler, should we add something

Re: Anything wrong with storing expanded plugin data in var cache?

For context, I asked Sam to come and discuss this here after his comment on the JEP about Essentials Evergreen snapshotting system, in the part where we explain how we plan to aggressively

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

I think this is a good initiative to keep us moving forward. As the Jenkins Project keeps growing, we definitely have various people with various interests, and anything that can help people contribute without feeling they're getting spammed by dozens of "unrelated" emails seems a good idea. I'm

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

Hello everyone, Sorry for the time it took to get back here. I think I finally addressed all comments. https://github.com/batmat/jep/pull/1 is ready for another round of comments. I hope that no big thing surfaces again, though obviously there will be issues discovered later, but I feel like we

Re: Nullable single constructor parameter with declarative pipeline

Though it's possibly a bug, why use @DataBoundConstructor instead of @DataBoundSetter? I generally use the constructor for required params, and setters for optional ones. 2018-03-19 11:48 GMT+01:00 Julien HENRY : > Hi folks, > > Our SonarQube plugin has a build step

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

@Jesse The alternative I had considered too was to just have multiple volumes. But I agree having only one is also more inlined with Essentials philosophy, having only one volume to actually backup (because yes, users should still backup, JENKINS-49406 is *not* a backup system) is simpler. @James

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

data>". Any opinion about this? Any good or bad experience using those parameters to move build records and/or workspaces somewhere else on the disk? Thanks! 2018-03-14 18:55 GMT+01:00 R. Tyler Croy <ty...@monkeypox.org>: > (replies inline) > > On Wed, 14 Mar

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

Hello everyone, For Jenkins Essentials , one critical requirement is to be able to upgrade, and hence rollback in an automated manner. So, as we are committed to an open design process,

Re: having trouble with releasing to jenkins-ci.org

You committed & push the release.properties and pom.xml.releaseBackup files, delete and add them to .gitignore to never ever do it again. Also, the version in the pom.xml should always contain -SNAPSHOT in the end. Only the release plugin will remove it when releasing. Cheers 2018-03-09 4:48

Re: Query

Hello, I _think_ not. We require plugins to be open-source, and that dependencies are also available (free of charge) for contributors to work on it. We can be more specific if you provide additional details I guess. Cheers 2018-03-08 7:05 GMT+01:00 Rahul Pure : > Hi, >

Re: Role-Strategy API Questions

Hello, IIUC, this looks like a question for the users mailing list. Or are you trying to add a feature to the plugin itself? Thanks! 2018-03-05 14:43 GMT+01:00 : > Hey All! > > I was wondering what features of the API are available to use. I saw some > features like

Re: Commit access for plugin usage plugin and PR that adds version information

Timeout expired indeed, just made you committer on this plugin. To be able to release you need to file a PR on https://github.com/jenkins-infra/repository-permissions-updater/ Welcome aboard and thanks a lot for stepping up! 2018-03-01 16:49 GMT+01:00 Michał Laskowski

Re: change assembly version plugin

Feb 27, 2018 at 8:12 AM Oleg Nenashev <o.v.nenas...@gmail.com> > wrote: > >> +1 for moving forward >> >> 2018-02-27 16:11 GMT+01:00 Slide <slide.o@gmail.com>: >> >>> It's been about two weeks since I sent the original email copying lkobus &

Re: Request permission to release PRs to `cvs` plugin

+1. cvs... Le 28 févr. 2018 20:39, "Mark Waite" a écrit : > +1 > > On Wed, Feb 28, 2018 at 11:50 AM Slide wrote: > >> +1 >> >> On Wed, Feb 28, 2018 at 11:30 AM Jesse Glick >> wrote: >> >>> I would like to request GitHub

Re: Jenkinsfile and async / parallel tasks

Declarative's when block, IIUC. (Note: more a thread for the users list if we don't head over implementing something in a plugin or so). 2018-02-20 12:00 GMT+01:00 Nigel Magnay : > I have a project with a Jenkinsfile that changes a number of stages > depending on whether

Re: [Jenkins-infra] Requesting PR reviews from anyone in the jenkinsci organization

For some reason, it does not work, and wasn't before either for me. Not everywhere at least, and not being admin, I couldn't check/understand why. For instance, I still cannot request myself a review on https://github.com/ jenkinsci/configuration-as-code-plugin/pull/43 Maybe it's just because

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

LGTM. Same concern/request as Jesse, but ack that it will be processed separately, makes sense. 2018-02-19 17:44 GMT+01:00 Daniel Beck : > > > On 19. Feb 2018, at 15:57, Jesse Glick wrote: > > > > Would org membership allow people to be requested as

Re: Thoughts on sending error telemetry for Jenkins Essentials

Le 16 févr. 2018 15:51, "R. Tyler Croy" a écrit : One of the necessary details, in my opinion, to make Jenkins Essentials [0] successful is providing near-real-time error telemetry. Coupled with the "Evergreen" distribution system [1], error telemetry "post-deploy" will be

Re: Accelerating Jenkins development with Jenkins Essentials

Le 15 févr. 2018 21:29, "Baptiste Mathus" <m...@batmat.net> a écrit : +1, very exciting to make Jenkins operatable by newcomers in a matter of minutes. Having had very recently to drive a newbie to use Jenkins, even if he was very motivated, I think this is a great initiative.

Re: Accelerating Jenkins development with Jenkins Essentials

+1, very exciting to make Jenkins operatable by newcomers in a matter of minutes. Having had very recently to drive a newbie to use Jenkins, even if he was very motivated, I think this is a great initiative. The flexibility of Jenkins is a great strength for advanced users, but a real difficulty

Re: change assembly version plugin

+1 obviously. Thanks Alex! 2018-02-14 9:41 GMT+01:00 Oleg Nenashev : > +1 from me. > Let me know if you need any help with reviews. > > вторник, 13 февраля 2018 г., 22:12:06 UTC+1 пользователь slide написал: >> >> Hello, >> >> I would like to take over maintaining the

Re: Variable doubt in jelly-javascript-java for plugin development

Does this method work when called from the associated JUnit test? (BTW, this code is missing a finally block to correctly clean up resources and looks like sensitive to SQL injection attack, but let's table that for now I guess). 2018-02-06 11:45 GMT+01:00 Virginia Mesa :

Re: Commit access for plugin usage plugin and PR that adds version information

Can you please make sure to CC existing/last maintainers here as per https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess I'm sorry you found an outdated/incomplete wiki page, I'm fixing it right now. Thanks! 2018-02-05 13:58 GMT+01:00 Michał Laskowski

Re: Releasing CppNCSS plugin with JEP-200 compatibility fixes

Belated +1. 2018-02-02 11:52 GMT+01:00 Oleg Nenashev : > OK, I will proceed with the release > > четверг, 1 февраля 2018 г., 19:56:38 UTC+1 пользователь Ullrich Hafner > написал: >> >> +1 >> >> Am 01.02.2018 um 17:24 schrieb slide : >> >> +1 for sure

Re: can not login after i reset the password

Not 100% sure of your current state: can you still log in, but can't change your password. Or can't you anymore? If the former, agreed with Bobby: file an INFRA, and possibly pop in the #jenkins-infra IRC channel. If you can't login, try IRC as said, or the jenkins-infra ML I think. There's less

Re: repository-connector plugin maintainence

ea why it does not work… >> /Domi >> >> On 10 Jan 2018, at 00:22, Jae Gangemi <jgan...@gmail.com> wrote: >> >> >> thanks! >> >> adding original maintainers (as listed in wiki page) to cc list. >> >> On Tue, Jan 9, 2018 at 2:36 PM

Re: repository-connector plugin maintainence

Hello! Thank you for your interest! We've documented the process on this page: https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin To sum up, you want to put them in CC (hint: use git history, there should be a bunch of emails there in commits) here, and either they answer, or we have a

Re: Plugins dependency tree

IIUC you mean listing plugins that depend on a given plugin. Not exactly that, but there's (was? Otp right now) a page listing all extension points and their implementations. So there the data is at least already computed. Possibly then it could be made available through plugins.jenkins.io too.

Re: Jenkins Hackfest after FOSDEM

Planning as much as possible to be there too :). 爛 Le 22 déc. 2017 17:12, "Daniel Beck" a écrit : > > > On 21. Dec 2017, at 21:10, Mark Waite wrote: > > > > On 5 Feb 2018, the Monday after FOSDEM ends, the usual suspects of > Jenkins contributors

Re: Adding config when plugin updates

https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility#Hintonretainingbackwardcompatibility-Scenario:Addinganewfield ? 2017-12-10 4:26 GMT+01:00 Richard Bywater : > Hi > > I'm making a change to my plugin that will require all instances of a >

Re: Coexistence of two equal plugins

It seems to me that even if you manage to rename everything that needs to be, there'll probably still be some form of conflict on that UI part. But hard to be sure without actually checking details. BTW, if you can possibly explain what you're trying to do on which plugin, maybe you'll be able to

Re: Removing the Everyone team in the jenkinsci GitHub org

+1. A sensible move for sure. With hundreds of repos and hundreds of committers, /some/ segregation can definitely help avoid screwing up, even from non malicious users. Thanks Daniel for that cleanup 2017-11-28 11:50 GMT+01:00 Daniel Beck : > > > On 28. Nov 2017, at 11:26,

Re: Jenkins Plugin- License Policy

Le 3 nov. 2017 13:40, "Manuel Jesús Recena Soto" a écrit : Hello everyone, I hope everything going fine there. Over the last days, Víctor Martinez and me, have been working on analyzing the fulfillment of the Hosting Plugin Prerequisites

Re: Getting access to pitmutation-plugin

Hello, So I moved forward trusting the email, even if obviously it's easier to forge than a referenced GitHub conversation. But let's start with a trust relationship, hoping I'm not getting pwned :-). I made committer on that plugin, and the lead of the JIRA component. You *must* accept the

Re: Request to join skytap-cloud-plugin

@Colin I just made you committer and the JIRA lead of this plugin. You'll still need to proceed with Daniel's comment to be able to release. Welcome aboard! Thanks 2017-10-10 9:49 GMT+02:00 Baptiste Mathus <bmat...@batmat.net>: > > > 2017-10-09 23:48 GMT+02:00 Colin Henry &l

Re: Request to join skytap-cloud-plugin

> On Monday, October 9, 2017 at 2:32:38 PM UTC-7, Baptiste Mathus wrote: >> >> Hello please follow the process for taking over maintenance of a plugin >> (Google for 'Jenkins adopt a plugin' being on the phone doesn't make this >> easy for me right now). >>

Re: Request to join skytap-cloud-plugin

Hello please follow the process for taking over maintenance of a plugin (Google for 'Jenkins adopt a plugin' being on the phone doesn't make this easy for me right now). The only way to get an expedite handover is to get an explicit approval from the current maintainer(s). Can you maybe get in

Re: Build failure while trying to build the TFS plugin locally

Hello, Java 9 isn't supported yet (it will take even more time to support it for development probably). Can you please try with JDK 8? Thanks Le 9 oct. 2017 07:01, "Patrick van der Velde" a écrit : > Hi > > I've just cloned the TFS plugin so that I can make some

Re: Commit access to vstestrunner-plugin

@gmail.com> >> wrote: >> >>> Yasu is CC’d now. The user email listed in GitHub matches the last git >>> log entry’s email. >>> >>> On Tuesday, October 3, 2017, Baptiste Mathus <m...@batmat.net> wrote: >>> >>>> Hello, >>&g

Re: Transferring JenkinsPipelineUnit to Jenkins Org

\o/ Welcome and great! Thanks again everyone. 2017-10-04 19:06 GMT+02:00 Oleg Nenashev : > Hi, > > The Repository has been moved, new location is > https://github.com/jenkinsci/JenkinsPipelineUnit. > I also created a pipeline-unit-developers >

Re: CICD Pipeline

Hello, A link would have helped contextualize what you talk about. I suspect you're talking about https://jenkins.io/doc/pipeline/tour/running-multiple-steps/ ? If so, then please file a pull request with what you think would be better against https://github.com/jenkins-infra/jenkins.io more

Re: Speeding up the ATH

+1 on simply deleting flaky tests. As an ATH user myself, I see flaky tests as deeply dangerous for the morale and the trust people have in the tool. At such point that even after the quality had improved dramatically (i.e. lowered flakiness), I have to fight my own first reflex to just ignore

Re: Commit access to vstestrunner-plugin

Hello, Basically we require a best effort to contact previous maintainer. Please follow https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess Try to ping the maintainer by adding her/him in CC of this very thread (hint: emails are generally attached to commit

Re: Jenkins Pipeline job to support 'withMaven' step

@Cyrille and @Artiom, if you feel like it, that would great if you can record it so that we can then make it available to more people on Youtube or so? Thanks! 2017-10-03 10:39 GMT+02:00 : > I contacted you on hangouts. > > Thanks! > > -- > You received

Re: Transferring JenkinsPipelineUnit to Jenkins Org

FWIW, +1 all for it obviously, we've already had the opportunity to discuss this at Jenkins World. And thanks again for that move Ozan, Emmanuel & your company LesFurets. IMO the next step is to file a JIRA into the HOSTING project, linking to

Re: Checkout single file from SCM (groovy)

Probably not a dev list question. Le 21 sept. 2017 17:27, "Jesse Glick" a écrit : > On Thu, Sep 21, 2017 at 11:04 AM, Carles Capdevila Tejada > wrote: > > I've also seen that, in the SCM API > > plugin the abstract class SCMFileSystem is able to

<    1   2   3   4   5   6   7   8   9   >