Re: Some questions on plugin development

> On 20. Dec 2017, at 20:04, Jochen Wiedmann wrote: > > No annotations, or something like that? https://jenkins.io/doc/developer/extensibility/ explains this and links to relevant Javadoc (the developer docs on jenkins.io are work in not-much-progress, but this is

Re: December 20 project meeting

> On 6. Dec 2017, at 19:16, Daniel Beck <m...@beckweb.net> wrote: > > If you have a topic for the next project meeting, be sure to add it to the > agenda well before the evening of December 20, otherwise we might miss it and > will only be able to discuss it next year. It

Re: Jenkins crawler does not update Sonarqube scanner for MSBuild versions

> On 19. Dec 2017, at 11:05, Thomas Vérin wrote: > > We've released new versions of the Sonarqube scanner for msbuild, they are > available as versions in github. > https://github.com/SonarSource/sonar-scanner-msbuild/releases > > But the json file generated by

Re: Proposal: Release Break during holiday season

> On 19. Dec 2017, at 01:29, Oleg Nenashev wrote: > > Just to make sure, do we plan to spin 2.89.3 and 2.89.4 according to this > plan? There was an out-of-order release of 2.89.2, but I'd guess it does not > change the 2.89.x lifetime for major releases. > > If yes,

December 20 project meeting

Hi everyone, In our meeting today we agreed that we're going to skip the project meeting on December 20 unless someone has an agenda item for it, since there won't be an LTS status to discuss at that time. If you have a topic for the next project meeting, be sure to add it to the agenda well

Re: Request to add myself as a contributor to our Jenkins plugin

> On 5. Dec 2017, at 12:12, eugen.horov...@whitesourcesoftware.com wrote: > > Hi, > I'm working in WhiteSource as a software developer. > I would like to join as a contributor to whiteSource Jenkins plugin . > Please give me access to whitesource-plugin > This is my

Re: Team/repo associations cleanup: You may have lost some permissions today

> On 3. Dec 2017, at 20:21, Joseph P wrote: > > Don't know why I was on so many repos, that I have never touched when looking > that INFRA-1421  As I wrote -- wrong team/repo associations. You are a member of a team (or teams) that used to have access to many unrelated

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 1. Dec 2017, at 17:06, Stephen Connolly > wrote: > > Now you’ve got me all competitive... how far was I off Jesse? You can look forward to 68 emails from GitHub ;-) -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 29. Nov 2017, at 14:52, Daniel Beck <m...@beckweb.net> wrote: > > Details TBD. I currently plan to make people collaborators with write access. > This will need to be cleaned up some time in the future, but speculatively > granting additional permissions (most per-r

Re: Team/repo associations cleanup: You may have lost some permissions today

> On 28. Nov 2017, at 14:59, Daniel Beck <m...@beckweb.net> wrote: > > These three repos have so many team associations that they break the GitHub > UI (90-130 teams each), so I'm in contact with GitHub support to fix them: > emmacoveragecolumn-plugin > matrix-reloaded

'Core' team permissions cleanup

Hi everyone, As part of an effort to clean up the permissions in the jenkinsci GitHub organization[1][2], the following users have been removed from the 'Core' team that grants access to repos like jenkinsci/jenkins, developer tools, or various bundled libraries: albers b2jrock bap2000

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 30. Nov 2017, at 00:17, Kanstantsin Shautsou > wrote: > > Kohsuke, do you publicly approve that jenkins is not the bazaar anymore? Could we please keep this thread focused on the specific proposed initiative? -- You received this message because you are

Re: Jenkins 2.89.1 LTS RC testing started

> On 23. Nov 2017, at 12:44, Daniel Beck <m...@beckweb.net> wrote: > > https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.89.1-fixed are the > backported fixes. We missed https://issues.jenkins-ci.org/browse/JENKINS-47909 because it was kept open. https://github.com

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 29. Nov 2017, at 09:56, Ullrich Hafner wrote: > > Seems that I still can push changes to my repositories but I cannot access > the settings anymore (e.g., edit the description, view the collaborators). AFAICT you never were. I've looked into this about a year

Re: Remote Parameterized Trigger Plugin

if you have questions about taking over the plugin you could ask > Daniel Beck (https://github.com/daniel-beck). I'm reading :-) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop recei

Re: Team/repo associations cleanup: You may have lost some permissions today

Oliver, I don't understand what you're asking for. > On 28. Nov 2017, at 20:26, Oliver Gondža wrote: > > Some of these are maintained by us, please grant access to olivergondza for: > > - exclude-matrix-parent You already have write via Everyone, unchanged from yesterday.

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 28. Nov 2017, at 16:46, Jesse Glick wrote: > > I was just unclear on why you think we cannot > detect maintainer-like actions (merging PRs, cutting releases) with > decent confidence. Note that the GH API doesn't work just based on Git data (in fact, those are

Team/repo associations cleanup: You may have lost some permissions today

Hi everyone, In preparation for the larger Everyone permissions cleanup[1] I wrote a script determining collaborators/contributors for every plugin. Reviewing its output, I found ~40 repos that had broken team/repo associations, i.e. per-repo teams that grant access to repositories other than

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 28. Nov 2017, at 11:26, Robert Sandell wrote: > > A mid sized pr normally sits around 5 commits, so does one merged pr count as > five contributions? > I think so (perhaps unless squashed?). Note that this does not grant additional commit access to people who

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 28. Nov 2017, at 04:58, Kohsuke Kawaguchi wrote: > > If this change inadvertently remove somebody's commit access, presumably we > expect people to follow this and mail this list? Or just email this list in panic/rage without following a guide ;-) That's why I plan to

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 28. Nov 2017, at 03:39, Mark Waite wrote: > > I won't remove "Everyone" from the git-client-plugin or the git-plugin until > after you've made the change, since removing that group would remove write > permission for key people (Stephen, Jesse, Sam, Liam,

Re: Removing the Everyone team in the jenkinsci GitHub org

> On 28. Nov 2017, at 01:39, Richard Bywater wrote: > > Should a plugin maintainer have full admin access to the repo? Reason I ask > is that I recently took over as maintainer for the HTML publisher plugin but > don't have any access outside of committing etc. As the

Removing the Everyone team in the jenkinsci GitHub org

Hi everyone, For a long time, we didn't really manage GitHub permissions for plugins: We just added new repos and contributors to the 'Everyone' team, giving everyone access to everything, and that was it. Contrary to its name, it doesn't actually include _everyone_, at least not anymore:

Re: How to get notification on me plugin issues?

> On 26. Nov 2017, at 18:15, Martin Weber wrote: > > Username:15knots > Plugin ID: cmakebuilder Done: [2017-11-26 18:39:20]Changing default assignee of subcomponent cmakebuilder-plugin to 15knots [2017-11-26 18:39:25]Default assignee set to 15knots --

Re: How to get notification on me plugin issues?

> On 26. Nov 2017, at 18:01, Martin Weber wrote: > > Looks like I am NOT assigned by default. Could this be caused by > discrepancies > between the pom and my account on jenkins-ci? This typically happens during component creation but might be missed for example when you

Re: Jenkinsfile: how to make it install a tool for tests?

> On 26. Nov 2017, at 17:06, Martin Weber wrote: > > I recently added a Jenkinsfile to build my plugin. > > Now, when https://ci.jenkins.io runs the build, most of the tests fail, since > these required to have cmake installed. > > How can I tell

Re: How to get notification on me plugin issues?

> On 26. Nov 2017, at 17:10, Martin Weber wrote: > > is it possible to make issues.jenkins-ci.org automatically send email- > notification to a/the plugin maintainer, if a new issue arrives? Maintainers are typically the default assignee for their plugin, and you should

Re: Jenkins 2.89.1 LTS RC testing started

> On 23. Nov 2017, at 11:20, Patrick van Dissel wrote: > > Where can I find the changelog of this LTS RC release? https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.89.1-fixed are the backported fixes. Besides that, there's no user changelog (or upgrade guide)

Re: Unable to upload snapshot of teamconcert-plugin 401 Unauthorized error

> On 21. Nov 2017, at 15:27, Lakshmi Narasimhan Vaikuntam > wrote: > > Any reasons for this to happen? Please see https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues -- You received this message because you are

Re: Propose a workaround of missing multiple security realm feature

> On 20. Nov 2017, at 10:24, Stephen Connolly > wrote: > > In group membership is going to be tricky (not impossible) as you will need > to know which delegate realm the group came from and only match against users > from that same realm. > > In general the

Re: Proposal: Release Break during holiday season

> On 16. Nov 2017, at 23:02, Andres Rodriguez wrote: > > IIRC in the last couple of years (at least) there have been a small break of > the normal release cycles during the holiday season. Correct -- 2015/2016 we delayed 1.642.1 for two weeks, and 2016/2017 we

Re: Adopting xUnit plugin

> On 14. Nov 2017, at 21:44, Andrew Bayer wrote: > > ...but could someone with ownership rights for > github.com/jenkinsci/xunit-plugin update the repo description to > https://plugins.jenkins.io/xunit? Thanks. Done. -- You received this message because you are

Re: Adopting xUnit plugin

> On 14. Nov 2017, at 18:50, Andrew Bayer wrote: > > I guess I'll take it? =) GitHub and Jenkins infra usernames are both abayer. > Thanks! This is another one of Gregory's plugins, thanks for taking over! File a PR in

Re: [configuration-as-code] Descriptors configuration

> On 13. Nov 2017, at 20:26, Jesse Glick wrote: > >> >> if I UNCHECK the optional property, no "authentication" value >> is posted to JSON form, and I don't get SMTPAuthentication reset to null in >> my descriptor. > > Unfortunately your `configure` override must start

Re: JEP proposal: Removing user-facing scripting features from core

> On 13. Nov 2017, at 17:40, R. Tyler Croy wrote: > > What impact does this have on the Script Console or the CLI, both of which > expose scripting functionality? The "Script Console" and groovy/groovysh CLI commands (and more) would be moved into a plugin, so OOTB,

JEP proposal: Removing user-facing scripting features from core

Hi everyone, This is a pre-JEP check[1]: Would https://github.com/jenkinsci/jenkins/pull/3006 (the goal, rationale etc., not the implementation details) have a chance as a JEP, or is it a waste of time? Thanks, Daniel 1: https://github.com/jenkinsci/jep/tree/master/jep/1#discussion -- You

Re: Request to be a maintainer for the IvyTrigger Plugin

> On 10. Nov 2017, at 20:16, Bergquist, Brett wrote: > > https://wiki.jenkins.io/display/JENKINS/IvyTrigger+Plugin > > I have privately emails Gregory Boissinot about becoming a maintainer but > have not heard back. Here is what I had sent Gregory > > … > I have

Re: stack trace in configure system (docker, plugin development)

> On 10. Nov 2017, at 17:12, Ewelina Wilkosz wrote: > > And I don't understand where it comes from... Complete newbie here. Anyone > willing to help with troubleshooting? Judging from your Dockerfile, I expect that to already be in the file at

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

> On 10. Nov 2017, at 17:54, Daniel Beck <m...@beckweb.net> wrote: > > this is just spam And the text is just copied and pasted from a quora.com answer from 2011. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" g

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

> On 10. Nov 2017, at 16:53, jxpea...@godaddy.com wrote: > > since you asked They didn't, this is just spam. Just check where the 'Jenkins' link leads. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and

Re: Help with jenkinsci failure

> On 10. Nov 2017, at 00:37, Steve Christou wrote: > > It looks like an issue with the downloading of the jenkins war for testing: Probably https://issues.jenkins-ci.org/browse/INFRA-1398 Possibly https://issues.jenkins-ci.org/browse/INFRA-1386 -- You received this

Re: Request for plugin ownership - SLOCCount Plugin

> On 8. Nov 2017, at 11:55, Ivaïlo Marinkov wrote: > > The pull request I created at Daniel's request has been approved and merged > after the original maintainer, Michal, said he was OK with the plugin having > a new maintainer. > > What are the next steps needed before I am

Re: Cannot Create Account

> On 4. Nov 2017, at 00:59, Andrew Armaneous wrote: > > However, every time I've tried to create an account, I've run into a > connection timeout exception with a Java stack trace output to the browser. Known issue tracked as

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

> On 27. Oct 2017, at 21:03, Liam Newman wrote: > > I believe JEP-1 is on the agenda for the next governance meeting. Please > review the PR and any propose fixes/changes now. > A reminder: the meeting time is specified in UTC, which for the US and most of Europe at

Re: Ansible Plugin maintainers membership request

> On 26. Oct 2017, at 17:30, Emilio Escobar wrote: > > Can I get permissions for merging and releasing > https://wiki.jenkins.io/display/JENKINS/Ansible+Plugin ? I can work close to > the current maintainer jcsirot if he agree. > > I have asked before at

Re: Caught: groovy.lang.MissingPropertyException: No such property: executable for class: java.lang.Thread

> On 2. Nov 2017, at 21:34, Neel Desai wrote: > > Where I am doing wrong? The standalone Groovy program you wrote knows absolutely nothing about Jenkins internals. 'executable' is specific to threads representing executors in Jenkins. -- You received this message

Re: Request for plugin ownership - SLOCCount Plugin

> On 24. Oct 2017, at 20:34, Иво Маринков wrote: > > I've been trying to get some changes into the SLOCCount Plugin > (https://wiki.jenkins.io/display/JENKINS/SLOCCount+Plugin). > I was told the plugin was looking for a maintainer Could you provide a reference for this? While

Re: GCloud SDK Plugin Maintainence

> On 23. Oct 2017, at 23:10, phanikumar wrote: > > Please let me know your comments on this. No opinion, but if you wish to take over, please make sure to include the maintainer in this thread in Cc. The process described in

Re: Ansible Plugin maintainers membership request

> On 26. Oct 2017, at 17:30, Emilio Escobar wrote: > > I can work close to the current maintainer jcsirot if he agree. Please include the current maintainer in such threads. Not everyone (unfortunately) reads the dev list. -- You received this message because you are

Re: Request to join scm-sync-configuration plugin

> On 25. Oct 2017, at 10:54, guiller.pal wrote: > > Didn't get any respose from the actual maintainers. Shall we wait more time > or can we proceed further? > Please file a PR to https://github.com/jenkins-infra/repository-permissions-updater/ as described in the

Re: Solved security problems in PostBuildScript Plugin

> On 30. Oct 2017, at 19:32, Daniel Heid wrote: > > And I volunteer in adopting the plugin to maintain it. I already solved three > issues. Great! I responded in https://github.com/jenkinsci/postbuildscript-plugin/pull/15 what the next steps are. Sorry for the delay. --

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

> On 31. Oct 2017, at 11:12, Robert Sandell wrote: > > Thoughts? > If it's relevant enough and not just implementation detail, it can always be added by the author even in the current format. But expecting a complete list of added/deprecated/removed APIs will just

Re: Solved security problems in PostBuildScript Plugin

> On 30. Oct 2017, at 15:59, Jesse Glick wrote: > > Why not just use the Groovy Postbuild plugin, which has comparable > functionality (IIUC) but is long since secured, and better maintained? Doesn't replace the regular 'shell' script feature of the plugin though. --

Re: How to persist Global config Data

> On 26. Oct 2017, at 20:30, phanikumar wrote: > > I am unable to view the > data when I go to configuration for next time. But still, I am able to > access the field value. do you have a method `public String getGcloudpath()`? (Note capitalization, needs to

Publishing security advisories without fix

Hi everyone, About a year ago I established a policy that we would publish security advisories if there's no expectation of getting them fixed through our private process. https://jenkins.io/security/#vulnerabilities-in-plugins Today, I did that once again, in a somewhat popular plugin, and

Re: Commit access to vstestrunner-plugin

> On 5. Oct 2017, at 18:40, Erik Goughnour wrote: > > I did read the link. I had actually read it (along with quite a bit of the > rest of the documentation) before I created the PR that I was trying to > merge. There is evidence of this. Notice I tagged the PR per

Re: Request to join claim plugin

> On 19. Oct 2017, at 19:43, Arnaud wrote: > > I plan to merge a fix to the https://jenkins.io/security/advisory/2017-04-10/ > vulnerability as well as at least one other enhancement. This is one of the plugins that allow Overall/Administer users to do something that

Re: Whitelisting whole dependency for script-security

> On 19. Oct 2017, at 12:25, Oliver Gondža wrote: > > which is always the case when run during build. https://plugins.jenkins.io/authorize-project ? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe

Re: Request to join skytap-cloud-plugin

> On 13. Oct 2017, at 01:19, Colin Henry wrote: > > Relevant information: my issue is I am unable to sign up for an account in > the first place, I don't have an existing account. I am trying to cut a new > build of the Skytap plugin after fixing a few bugs(now merged) that

Re: Request to join scm-sync-configuration plugin

> On 11. Oct 2017, at 09:48, guiller.pal wrote: > > My name is Guillermo Palacio and i'm in charge of jenkins in my company. > > I would like to maintain the scm-sync-configuration plugin, as it seems > nobody is taking care of it. > > I have tried to create a Jenkins

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

> On 11. Oct 2017, at 21:03, Jesse Glick wrote: > > As an aside, it just occurred to me that JENKINS-41745 is something > that I would have done as a JEP had that existed at the time. Having > the templates and structure in place would have made it easier to > write up the

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

> On 5. Oct 2017, at 18:01, R. Tyler Croy wrote: > > There has been a tremendous amount of productive discussion, with a lot of > helpful editing work by Liam. I think the process is ready for an approval in > a > Governance meeting, so I'm going to put the proposal on the

Re: Request to join skytap-cloud-plugin

> On 10. Oct 2017, at 17:51, Colin Henry wrote: > > Caused by: javax.mail.AuthenticationFailedException: 535 Authentication > failed: account disabled > > at > com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:826) Tracked as

Re: Request to join skytap-cloud-plugin

> On 9. Oct 2017, at 23:20, Colin Henry wrote: > > I am taking over responsibility for Tom Milligan at Skytap for the Jenkins > plugin: Skytap-cloud-plugin. > > please add me as a contributor to the repository. > > My GitHub username is jchenry. > Probably best to file

Re: Request to join Jenkins CERT team

> On 5. Oct 2017, at 19:12, wfollon...@cloudbees.com wrote: > > I would like to request access to join the Jenkins CERT team. > > • GitHub 2-factor auth enabled: yes > • Signed CLA: > https://github.com/jenkinsci/infra-cla/tree/master/collected/icla/wfollonier > • GitHub

Re: Transferring JenkinsPipelineUnit to Jenkins Org

> On 3. Oct 2017, at 23:57, Ozan Günalp wrote: > > So is everyone ok with me creating a ticket on the Hosting project even > though it is not a plugin hosting request ? Seems pointless given the discussion having taken place here. This thread gave people plenty of time

Re: Request to join as a contributor to WhiteSource Jenkins plugin

> On 27. Sep 2017, at 07:44, raz.nit...@whitesourcesoftware.com wrote: > > I'm working in WhiteSource as a software developer. > I would like to join as a contributor to whiteSource Jenkins plugin . > Please give me access to whitesource-plugin > This is my GitHub username : raznitzan4 > I

Re: Request to join Jenkins CERT team

> On 26. Sep 2017, at 17:40, Devin Nusbaum wrote: > > I would like to request access to join the Jenkins CERT team. Welcome aboard! For context, Devin is an engineer at CloudBees working on the team that regularly contributes security fixes. -- You received this

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

> On 27. Sep 2017, at 12:06, Oleg Nenashev wrote: > > If there is a consensus in the mailing list, no strict need to involve the > governance meeting from the technical PoV. The only purpose of the governance > meeting here is to... > • Act as a arbiter when

Re: Transferring JenkinsPipelineUnit to Jenkins Org

> On 27. Sep 2017, at 11:45, Oleg Nenashev wrote: > > discussion at the Governance meeting today so that anybody can provide > feedback Nobody bothered to speak up in this thread for the past week, so I don't think this is necessary. -- You received this message

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

> On 27. Sep 2017, at 11:36, Oleg Nenashev wrote: > > Regarding the process, some minor comments... > • I would expect Delegates to be discussed in the mailing list before > the JEP submission, so it just needs approval at the governance meeting. TBH the group of

Re: Commit access to vstestrunner-plugin

> On 25. Sep 2017, at 01:39, Erik Goughnour wrote: > > Can I get access to vstestrunner-plugin? Please make sure to include the current/previous maintainers in this request to give them a chance to respond, if they're still around. It doesn't look like there's a lot

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

> On 19. Sep 2017, at 19:12, R. Tyler Croy wrote: > > While I had hoped we might be able to get some consensus in time for > tomorrow's > project meeting There was none, it is (and always has been) scheduled for next week, September 27. Just general FYI to prevent

Re: repo access for non plugin stuff

> > On 20. Sep 2017, at 22:31, James Nord wrote: > > In order to demonstrate the changes in Jenkins I would like to be able to > push a snapshot of stapler to our repo so the PR can consume it. > Any registered user can deploy any snapshot. (This was changed shortly

Re: Transferring JenkinsPipelineUnit to Jenkins Org

> On 20. Sep 2017, at 12:18, Ozan Günalp wrote: > > We naturally want to make sure that current maintainers and LesFurets Org > stay collaborators on the project. Orgs cannot be orgs of other orgs, but if we make you team maintainers, you can add or remove

Re: access jenkins from remote nginx

Please don't ask user questions on the developers list. > On 18. Sep 2017, at 10:14, pritha ghosh wrote: > > Hi, > > My Jenkins server and nginx server is in 2 different machine in the same > intranet. the nginx web server is exposed to the internet via a domain

Re: matrix-auth maintainership

> On 14. Sep 2017, at 12:55, Daniel Beck <m...@beckweb.net> wrote: > > I plan to release a 2.0 shortly once I've had time to finish all these > changes. I released matrix-auth 2.0-beta-1. Changelog: https://wiki.jenkins.io/display/JENKINS/Matrix+Authorizati

Re: Request to become a maintainer of Google Storage Plugin

> On 16. Sep 2017, at 00:12, 'Alexandra Goultiaeva' via Jenkins Developers > wrote: > > I have accepted the invitation. And I can see myself in the list of members, > and I can see that I'm listed as on the google-storage-plugin Developers team. > > Still

Re: Jenkins 2.73.1 LTS RC testing started

> On 14. Sep 2017, at 18:50, Daniel Beck <m...@beckweb.net> wrote: > > We have some new information on the issue Mark discovered during testing: > > https://issues.jenkins-ci.org/browse/JENKINS-46754 (latest comments) > > Oliver, would you support integrating a fi

Re: Jenkins 2.73.1 LTS RC testing started

> On 14. Sep 2017, at 07:42, ogondza wrote: > > Agreed on the meeting the release will be cut with the regression compared to > 2.60 line (with remoting 3.10) and Jenkins docker container will be updated > not to be impacted. The proper fix will target 2.73.2. We have some

matrix-auth maintainership

Hi everyone, Unless someone objects, I'll take over maintainership of the matrix-auth plugin. Mathias Nyman already approved me as uploader, but also mentioned he had just scratched an itch, which makes the plugin effectively unmaintained (or somewhat collectively maintained). I'd like to

Re: Jenkins 2.73.1 LTS RC testing started

> On 13. Sep 2017, at 16:06, Jesse Glick wrote: > > IIUC we can simply patch the image to either have a writable `$HOME`, > or specify an explicit `-workDir`, so that most users are not > affected—right? > Right now, I don't think 2.73.1 is ready for release due to this

Re: Jenkins 2.73.1 LTS RC testing started

> On 13. Sep 2017, at 12:11, Vincent Latombe wrote: > > Docker environment Is this going to be a problem in the official Jenkins Docker images? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe

Re: "Processing environment for ${pluginName}"

> On 12. Sep 2017, at 04:52, Justin Harringa wrote: > > Is this a plugin or Jenkins in general? > Not a dev list question, please ask on the users list (and if you do, include a full list of installed plugins and versions to help the search). -- You received this

Re: Wiki page seems to be having some kind of caching issues

> On 11. Sep 2017, at 13:29, Daniel Anechitoaie wrote: > > My main concern is that page at > https://plugins.jenkins.io/osf-builder-suite-for-sfcc-deploy does't seem to > get updated. > https://issues.jenkins-ci.org/browse/WEBSITE-378 has been merged into staging a

Re: Jira - Confirmed status

> On 11. Sep 2017, at 08:26, Richard Bywater wrote: > > An "ideal" workflow (well, one that is slightly easier to work with) in my > mind would be something like Open->Confirmed->In Progress->Resolved->Closed. > Similarly if it wasn't really an issue, something like

Re: Jenkins mark usage request from TechMatrix

> On 10. Sep 2017, at 00:15, Oleg Nenashev wrote: > > Have I missed the change? Safe to assume a typo, I fixed the wiki page. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and

Re: How are pages from https://plugins.jenkins.io/plugin generated?

> On 10. Sep 2017, at 00:02, Daniel Anechitoaie wrote: > > How are pages from https://plugins.jenkins.io/plugin generated? > Where is the content pulled from? Is it taken from its wiki page? >

Re: Request to join Jenkins Security Team

> On 28. Aug 2017, at 19:29, Christopher Orr wrote: > > I'd like to request to join the security team. > I've got all the prerequisites listed (2FA, CLA, nickname on IRC). Thanks, and welcome aboard! Ping me on IRC and I'll finish setting you up. -- You received this message

Re: Request to join Jenkins CERT team

> On 3. Sep 2017, at 00:28, Steve Christou wrote: > > I would like to request access to the Jenkins CERT team. Great to have you on board -- ping me on IRC and I'll finish setting everything up :-) (For context, we talked about this last week when we met around Jenkins

Re: How to edit plugin information page on https://plugins.jenkins.io

> On 7. Sep 2017, at 16:33, Tomasz Jurkiewicz > wrote: > > I see that indeed there are plugin pages on wiki.jenkins.io, but - how do I > set connection between a wiki page and a plugin? > (ie, how the system knows which wiki page belongs to which plugins?) > This

Re: How to edit plugin information page on https://plugins.jenkins.io

> On 7. Sep 2017, at 16:37, Slide wrote: > > Each plugin wiki page has some metadata similar to below: > > {jenkins-plugin-info:pluginId=token-macro|src=github} For the plugin site, that's just being stripped out. -- You received this message because you are

Re: release of new version of a plugin already built by ci.jenkins.io

> On 7. Sep 2017, at 11:46, Thomas Max wrote: > > Why is there no way to publish a new version of a plugin since it was already > built there. It makes no sense to built it on the ci if I need to build it > manually on my machine once again anyway. We still need

Re: Plugin/core version installation statistics

> On 19. Jul 2017, at 17:52, Daniel Beck <m...@beckweb.net> wrote: > > Note that there's no directory index at > https://stats.jenkins.io/pluginversions/ (yet) -- my plan is to add links to > plugins.jenkins.io and make that the default entry point. Thank

Re: How does the plugins.jenkins.io page work?

> On 5. Sep 2017, at 02:11, Daniel Beck <m...@beckweb.net> wrote: > > https://issues.jenkins-ci.org/browse/WEBSITE-378 To clarify, I think it's fixed, but not deployed. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers&qu

Re: How does the plugins.jenkins.io page work?

> On 4. Sep 2017, at 15:39, MarionD wrote: > > 1) Is the wiki content supposed to be displayed on this page? Yes. > 2) If so, is it automatic or is there anything special to do? Currently, our > plugin page is not showing much information >

Re: Need REST API for fetching data from Jenkins Plugins

> On 25. Aug 2017, at 11:04, Gaurav Rai wrote: > > I'm working on getting data from Jenkins using Remote Access API. > I'm able to get Jenkins Build history using it. But in one of case, I need to > get data from Jenkins Plugin "summary_report" > > is there a way to get

Re: Asking for commiter access to amazon-ecs-plugin

> On 24. Aug 2017, at 22:09, Surya yaramada` wrote: > > Can I get any updates on this? > There's no need for multiple emails per day. Give him a week or so. Jan may well be on vacation. -- You received this message because you are subscribed to the Google Groups

Re: group archives empty / banned content

> On 24. Aug 2017, at 12:39, James Nord wrote: > > Is it there? The reason I ask is that I am sure that I raised a JIRA the > other day - yet JIRA now says I did not and has no recollection of it. Its > done this before to me and I would love to prove that I am not

Re: Debugging an action that does not show summary.jelly

> On 24. Aug 2017, at 00:19, Ullrich Hafner wrote: > > I'm currently struggling with an Action that does not show the associated > summary.jelly on a build page. (All my other actions do show it). The action > correctly is shown in the sidepanel, just the summary is

<    2   3   4   5   6   7   8   9   10   11   >