Re: Admin/Ownership Repo Request

Hi, I'm the OWASP ZAP Project Lead. We (the ZAP core team) really want to maintain and onwardly develop the official Jenkins ZAP plugin. jordangs (above) has been leading on this and we're very close to releasing it. What do we need to do in order to make this happen? We're open for taking over

Heads Up: JIRA DVCS integration disabled on issues.jenkins-ci.org

After a couple months of experimenting, and countless builds in ci.jenkins.io failing because rate-limits on GitHub's APIs were exceeded, I have disabled the DVCS integration from JIRA<->GitHub. According to numbers shared by GitHub Support, the JIRA integration was consuming 80%+ of our quota

Admin/Ownership Repo Request

My IRC chat is broken, it can send but not receive messages. I apologize for the double post. I was given admin access of zaproxy-plugin however it was decided that a new repo should be created since it is not a compatible update, called *zap-plugin*. I currently have write access and would

Re: How to Add Custom Build Step to behave exactly same as Execute Windows Batch Command.

If anyone can guide how the windows bactch command execution are handled from backend JAVA API. Then I may create one of my own. On Monday, 14 November 2016 13:37:49 UTC+5:30, Kul Bhushan Srivastava wrote: > > -- You received this message because you are subscribed to the Google Groups

Re: [Jenkins-infra] Heads Up: JIRA DVCS integration disabled on issues.jenkins-ci.org

(replies inline) On Tue, 15 Nov 2016, Oleg Nenashev wrote: > Cold we just use a separate GitHub account for JIRA? > This integration is generally useful. That would be against the GitHub terms of service https://help.github.com/articles/github-terms-of-service/#a-account-terms - R. Tyler

Re: Cannot deploy to Jenkins Artifactory

Hi Martin, What do you mean when you say "my settings.xml"? Is that file used by Jenkins? I hope be useful. Best regards, Rachel El sábado, 12 de noviembre de 2016, 15:16:54 (UTC+1), Martin Reinhardt escribió: > > I'm trying to deploy snapshots of my plugin ( >

Re: Access the Value of BUILD_NUMBER/PROMOTED_NUMBER

Hi, You can get that value with: build.number For example (without any really valid purpose): return (build.number > 1) Any script evaluation errors will be redirected to the application log. I hope be useful. Best regards, Rachel El lunes, 14 de noviembre de 2016, 19:18:18 (UTC+1),

Re: [Jenkins-infra] Heads Up: JIRA DVCS integration disabled on issues.jenkins-ci.org

Github quota are per users thus using a dedicated account for jira may be an option. Le mar. 15 nov. 2016 à 19:44, Arnaud Héritier a écrit : > yes, good point oleg, it was a doubt I had. The quota is by account of for > an org ? > Otherwise we create a dummy technical

Re: [Jenkins-infra] Heads Up: JIRA DVCS integration disabled on issues.jenkins-ci.org

Cold we just use a separate GitHub account for JIRA? This integration is generally useful. 2016-11-15 18:50 GMT+01:00 R. Tyler Croy : > After a couple months of experimenting, and countless builds in > ci.jenkins.io > failing because rate-limits on GitHub's APIs were

Re: Admin/Ownership Repo Request

> On 15.11.2016, at 17:26, developer.go...@gmail.com wrote: > > I currently have write access and would like admin/ownership of the > repository. Done already before I saw this. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: [Jenkins-infra] Heads Up: JIRA DVCS integration disabled on issues.jenkins-ci.org

yes, good point oleg, it was a doubt I had. The quota is by account of for an org ? Otherwise we create a dummy technical account for Jira ? On Tue, Nov 15, 2016 at 7:38 PM, Oleg Nenashev wrote: > Cold we just use a separate GitHub account for JIRA? > This integration is

Re: Someone to take over GHPRB

Circling back on this thread, while I've been able to make progress as the maintainer of this plugin, I don't think it will be a successfully maintained plugin without additional help. There are some bigger-than-a-breadbox improvements needed, such as removing deprecations brought about by Jenkins

Re: Request ownership/action for a plugin (klocwork)

We cannot grant access to repositories outside the jenkinsci GitHub organization. Which is one of the reasons why we strongly recommend that plugins be maintained in that organization. We can only grant access to https://github.com/jenkinsci/klocwork-plugin and you'd need to sync the existing

Re: Jenkins failed using Ant Copy Command

Please ask this on the jenkinsci-users list. > On 15.11.2016, at 06:26, john rainier borden > wrote: > > Hi! > > I'm trying to create a simple freestyle project to build an executable. My > build is primarily composed of ant and batch script and is ran via

Re: Request ownership/action for a plugin (klocwork)

Hi Daniel, appreciate the quick feedback and thanks for the info - that answered another question I had about why the jenkinsci repo even existed. I would prefer to use the jenkinsci repo to avoid any future issues/bottlenecks. I have made one last attempt at contacting cittools because we

Re: Request ownership/action for a plugin (klocwork)

Ok I tried contacting the other maintainer/user at cittools and his email address for Thales does not work, so I suspect he has left Thales. As there has also been an outstanding pull request since July, and our attempts to contact the people at cittools has failed, I would assume this

zaproxy-plugin weirdness and request

1. At the request of jenkins admin's, i have reverted all changes made to the jenkins zaproxy-plugin. Updated the readme to inform users that it is discontinued. If you look at cloudbees , the build's seem to be failing. It

Disabling node monitors for single use computer

Hi, I am running into an issue which I think is related to my single use computer plugin ( https://github.com/suryagaddipati/jenkins-docker-swarm-plugin), which basically creates one computer/build and deletes it after its done. This is resulting in accumulation of thousands of node monitor

Request ownership/action for a plugin (klocwork)

Hi guys, Maybe someone can help me out, but a few weeks back I posted about commit access to the Klocwork plugin, following a pull request for a colleague, and neither have been answered... We really want to push some great features out there but our hands our tied :) If anyone knows how who

Re: [Plugin] Please review PR and release jsch-plugin

Enough time I think, but I'm currently preparing the security update. Let's revisit this on Thursday/Friday. > On 15.11.2016, at 00:18, Łukasz Jąder wrote: > > Hi Daniel, > > It's been a week since your attempt - do you consider this is enough amount > of time to make me

Re: Someone to take over GHPRB

> On 15.11.2016, at 14:19, Ben Patterson wrote: > > If anyone has keen interest, please let me/this-line know and let's get you > collaborator or maintainer status. Note that you can add a comment to adopt-this-plugin in the wiki, so you can use that as a vehicle to

Re: Someone to take over GHPRB

Good point; I'll do that as well Daniel. ty On Tue, Nov 15, 2016 at 8:24 AM, Daniel Beck wrote: > > > On 15.11.2016, at 14:19, Ben Patterson wrote: > > > > If anyone has keen interest, please let me/this-line know and let's get > you collaborator or