Re: Ready for adoption android-emulator-plugin

Sure, I would organize a fast call in Teams (MS) or zoom. Please use the email nfalco79athotmail.com Il giorno lunedì 26 settembre 2022 alle 19:45:22 UTC+2 bvera...@cloudbees.com ha scritto: > Nikolas, > > I may not be the perfect adopter, but I'd like to try. > Would you have a little bit of

[Co-Adoption]

Hi, I would like to co-maintain the dependency-check-plugin, which already has a maintainer since 9 months but is still all blocked and the maintainer @danile42 does not respond to any of the open PRs (old and new) that have been stucked there for 1 year . To solve the situation in my company

Ready for adoption android-emulator-plugin

Hi I'm the maintainer of android-emulator-plugin. I asked to maintain this plugin when my company was interested to develop application for android. I spent some time to move this plugin into the pipeline world but after less than 6 mounts the company decide to abandon the android project so I

Re: Jelly headache, page that include other page

THANKS It seems was the cause why the url did change (but not the reason why in develop mode works). Copy/Paste from NodeJSInstaller descriptor to the new one, I did not see that method. The reason of that getId method is because of > Obtained the updated data file for

Jelly headache, page that include other page

Hi, I have an issue in NodeJS plugin with feature https://issues.jenkins.io/browse/JENKINS-64646 Everytime I try to fix an issue for that feature in develop mode (hpi:run) all works like a charm, but when I release and install the hpi in a jenkins I have different behaviors. The feature ask

Re: Adoption of android-emulator-plugin

Could you also mark me as component lead for android-emulator-plugin in JIRA? So I will be notified on new issue Il giorno domenica 12 aprile 2020 09:22:32 UTC+2, Oleg Nenashev ha scritto: > > Thanks all! Access is granted. > Nikolas, you will also need to request the release permissions in a >

Re: Adoption of android-emulator-plugin

Done. PR available here: https://github.com/jenkins-infra/repository-permissions-updater/pull/1487 Il giorno domenica 12 aprile 2020 09:22:32 UTC+2, Oleg Nenashev ha scritto: > > Thanks all! Access is granted. > Nikolas, you will also need to request the release permissions in a > separate pull

Re: Adoption of android-emulator-plugin

Thank very much Chris, I will do my best. Il giorno sabato 11 aprile 2020 12:13:22 UTC+2, Christopher ha scritto: > > Hi there, > > On Sat, 11 Apr 2020, at 00:46, Oleg Nenashev wrote: > > Thanks for your interest! I will ping Chris to get his response. > > Let's also start counting the 2-week

Adoption of android-emulator-plugin

Hi, I would adopt the android emulator plugin https://github.com/jenkinsci/android-emulator-plugin/ That plugin is not marked for adoption but seem fall in abandoned case. Last commit is on Dicember 2017, there are valid PRs that have no response and a long list of issues on JIRA without

Re: Adoption of dtkit-plugin

No push is denied for jenkinsci/libdtkit repository "remote: Permission to jenkinsci/libdtkit.git denied to nfalco79." The same for jenkinsci/dtkit-plugin Il giorno lunedì 8 aprile 2019 16:10:58 UTC+2, Oleg Nenashev ha scritto: > > Hi, > > It should be fixed now. Merging a PR is not enough

Re: Adoption of dtkit-plugin

The PR to manage permissions for Artifactory has been merged but I do not have yet permissions to push to github repository jenkinsci/dtkit-plugin Anyone can help? Il giorno domenica 10 marzo 2019 10:49:24 UTC+1, Oleg Nenashev ha scritto: > > The ownership transfer looks good to me. > I am also

Re: Adoption of dtkit-plugin

Guys any chance to finalize this? I have pending work blocked because I can not push on repositories Il giorno domenica 3 marzo 2019 17:36:09 UTC+1, Nikolas Falco ha scritto: > > Hi, xunit-plugin is developed on top the dtkit-plugin libraries. > dtkit-plugin was develop by the same author of

Re: Adoption of dtkit-plugin

PR for infra repository available here: https://github.com/jenkins-infra/repository-permissions-updater/pull/1058 Feel free to approve and merge. Thanks in advance! -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Re: Adoption of dtkit-plugin

Any comments? Any news? Any doubts? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on

Adoption of dtkit-plugin

Hi, xunit-plugin is developed on top the dtkit-plugin libraries. dtkit-plugin was develop by the same author of xunit plugin. I need to update the library that dtkit-plugin use and to adapt the code to use new APIs. In discussion to adopt xunit-plugin, Jesse Glick suggested to transform the

Re: Enable code coverage report for Jenkins plugin

Ok, do you know who is allowed to do it? Il giorno venerdì 4 maggio 2018 20:41:54 UTC+2, Matt Sicker ha scritto: > > Oh sorry, I don't seem to have access to that. I can only view them myself > as well. > > On Fri, May 4, 2018 at 12:29 PM, 'Nikolas Falco' via Jenkins Develo

Re: Adopting xUnit plugin

Please also make me the default recipient on JIRA for xUnit component otherwise I'm not advised on new ticket -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email

Re: Enable code coverage report for Jenkins plugin

Hi, Matt any news about enable repos on Travis? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this

Re: Enable code coverage report for Jenkins plugin

yes, those repos -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit

Enable code coverage report for Jenkins plugin

Hi, recently I see some Jenkins plugins use double CI. One from Jenkinsfile and the other from .travis.xml. From what I can see travis CI is used only to publish coverage report to site like coveralls.io or codecov.io. The CI based on Jenkinsfile seem (quick check on

Re: Adopting xUnit plugin

ì 2 maggio 2018 18:13:14 UTC+2, Oleg Nenashev ha scritto: > > Yes, that's what I meant in "DTKit could be made such API plugin, but I do > not exactly understand what it does in Jenkins now." > > > On Wed, May 2, 2018 at 6:08 PM, 'Nikolas Falco' via Jenkins Developers

Re: Adopting xUnit plugin

Falco' via Jenkins Developers > <jenkin...@googlegroups.com > wrote: > > So you suggest to move code from DTKit into xUnit plugin > > IIUC the recommendation was simply to take the existing library and > repackage it as a plugin (with no user-facing features). That al

Re: Adopting xUnit plugin

request has been submitted - >>> https://github.com/jenkins-infra/repository-permissions-updater/pull/668 >>> >>> Il giorno mercoledì 11 aprile 2018 23:48:35 UTC+2, Andrew Bayer ha >>> scritto: >>>> >>>> That'd be fine by me

Re: [Jenkins-infra] Fwd: Ldap Maintenance: 2018/04/28 - 1PM UTC

I can not login to JIRA issue tracker. I got this "Sorry, a communication error occurred while trying to contact the remote authentication server." on https://issues.jenkins-ci.org/login.jsp?os_destination=%2Fdefault.jsp Same (quite the same) exception with on https://accounts.jenkins.io/login

Re: Adopting xUnit plugin

Good news, a pull request has been submitted - https://github.com/jenkins-infra/repository-permissions-updater/pull/668 Il giorno mercoledì 11 aprile 2018 23:48:35 UTC+2, Andrew Bayer ha scritto: > > That'd be fine by me. > > A. > > On Mon, Apr 9, 2018 at 6:35 AM, 'Nikolas

Adopting xUnit plugin

I know that the xUnit plugin was already adopted on 15/11/2017 (https://groups.google.com/forum/#!searchin/jenkinsci-dev/xunit%7Csort:date/jenkinsci-dev/RROnSHD36-A/u4DcVHygAQAJ) Jimilian, one month ago had ask news about movement on the plugin (for example pending PRs already approved by

Re: Path environment variable not set by SimpleBuildWrapper.Context.env() on Windows slave

@15knots this issue is not caused by the envinject plugin (I had try this when I got the issue). As you can see in the JIRA bug the issue is a Jenkins Core class (Run.java) and in the sequence that it use to constructs a new EnvVars for the current node. In the chain of enviroments pouring

Re: Repository access nodejs-plugin

29, 'Nikolas Falco' via Jenkins Developers < > jenkin...@googlegroups.com > wrote: > > > > Any news? > > I granted you commit access. > > Could you clarify whether you're interested in taking over maintainership > (without Greg apparently)? If so, please tel

Re: How to remove "plugin is up for adoption" warning message from wiki plugin page

Thanks very much -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit

How to remove "plugin is up for adoption" warning message from wiki plugin page

Hi, I've a question. I'm the current mainaiter of NodeJS plugin. I already release two new versions but the Wiki page of Plugin continue to show warning message: "*This plugin is up for adoption.* Want to help improve this plugin?"

Need a code review for node-js plugin

Hi, I have complete the work of a PR by other guy done one year ago to fix issue JENKINS-26828. Since it is my first serius commit as mantainer, could anyone please make a code review on the last commit in the branch https://github.com/jenkinsci/nodejs-plugin/commits/feature/JENKINS-26828 ? I

Re: Repository access nodejs-plugin

ok Daniel, let's continue here. Let me know about any updates. >From other thread Il giorno giovedì 17 novembre 2016 10:20:19 UTC+1, Daniel Beck ha scritto: > > Hi Nikolas, > > Sorry about that -- I confused your

Re: maintainer requests

I'm sorry but I think there are no chances of coordinate with Greg Langston the Node JS plugin. If there are requests of other guys that show interest to co-maintainer the Node JS are welcome. Please let me know in original post https://groups.google.com/forum/#!topic/jenkinsci-dev/wpC8zcrhkjg

Re: maintainer requests

I have no changed my opinion If there is a chance to have a co-mantainer for PR code review or interchange opinions without open a new thread every time I need, it would be great by here lacks a response since 8 days, and it's only a response yes/no. Il giorno mercoledì 9 novembre 2016

Re: maintainer requests

Seems there is no response. Could we finalise please abot NodeJS? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: maintainer requests

Hi, I've request write access for NodeJS+Plugin to resolve some issues. So is it a problem if we maintain toghether the NodeJS plugin? Il giorno venerdì 21 ottobre 2016 23:08:52 UTC+2, Greg Langston ha scritto: > > https://wiki.jenkins-ci.org/display/JENKINS/NodeJS+Plugin >

Re: Repository access nodejs-plugin

Hi guys any news? Il giorno lunedì 17 ottobre 2016 18:33:59 UTC+2, Nikolas Falco ha scritto: > > Hi, > I've made a PR 28 > days ago to resolve an issue of nodejs-plugin. > > Seems that repository is no more mantained, so I've read these >

Repository access nodejs-plugin

Hi, I've made a PR 28 days ago to resolve an issue of nodejs-plugin. Seems that repository is no more mantained, so I've read these page for rules on how to post a