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

[Kul Bhushan Srivastava]

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 
"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 
https://groups.google.com/d/msgid/jenkinsci-dev/76d6ddbf-14a2-405d-8197-f2dd549e8248%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Disabling node monitors for single use computer

[Surya Gaddipati]

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 threads in 
BLOCKED state. I suspect these threads don't go away once the computer goes 
away. 

I was curious if there is a way to either disable these monitors 
entirely Jenkins wide or disable them for computer type perhaps a method 
'needsMonitoring()' on Computer. 

eg: 

"Monitoring thread for Response Time started on Mon Nov 14 20:55:26 UTC 2016" 
#43777 daemon prio=5 os_prio=0 tid=0x2aab5f376800 nid=0x1f4b waiting for 
monitor entry [0x2aabd4e3b000]
   java.lang.Thread.State: BLOCKED (on object monitor)
at hudson.remoting.Channel.send(Channel.java:577)
- waiting to lock <0x000548779748> (a hudson.remoting.Channel)
at hudson.remoting.Request.callAsync(Request.java:205)
at hudson.remoting.Channel.callAsync(Channel.java:823)
at 
hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:75)
at 
hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:57)
at 
hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:305)




-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/d6fe40a8-2112-4b3e-ab7e-b49aab8d20bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

zaproxy-plugin weirdness and request

[JordanGS]

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 is failing because it cannot resolve 
dependencies, this is expected.

Module Builds
 Official OWASP Zed Attack Proxy Jenkins Plugin (didn’t run) 
[image: Failed] 

 ZAProxy Plugin 

I am unsure why it saying "Official OWASP Zed Attack Proxy Jenkins Plugin" 
because that label should be removed??

---

2.

As discussed in IRC, can we discontinue distribution of the current plugin 
but still allow existing users of the plugin to use the current version 
while we expect migration to zap-plugin 
.

I have updated the Wiki 
and the README 
 in accordance with 
deprecating a plugin.

3.

Can someone with voice please change the description under 
https://issues.jenkins-ci.org/ for the component zap-plugin

jenkins-admin: set description of zap-plugin to "The Official OWASP ZAP 
Jenkins Plugin extends the functionality of the ZAP security tool into a CI 
Environment."

---

Thank you. :)

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/d796c010-15ec-4b1b-b0f8-cad9bb5cc972%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Access the Value of BUILD_NUMBER/PROMOTED_NUMBER

[Rachel Moreno]

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), avinash@gmail.com 
escribió:
>
> Hi Folks,
>
> I am using Promoted Build plugin. And using some custom groovy scripts to 
> validate the build! I wanted to access the value of BUILD_NUMBER from the 
> groovy script. Can anyone suggest me how i can achieve this?
>
> Another thing i am writing println statement in this groovy script but its 
> no where getting logged. Any suggestion to debug the script flow how can i 
> log the info ?
>
> Thanks  
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/c4de646f-f15e-4d66-ad5a-299e2ccd25bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot deploy to Jenkins Artifactory

[Rachel Moreno]

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 (
> https://github.com/jenkinsci/rocketchatnotifier-plugin) to Artifactory, 
> but always getting 401 errors:
>
>
> [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ 
> rocketchatnotifier ---
> Downloading: 
> https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/rocketchatnotifier/0.2.2-SNAPSHOT/maven-metadata.xml
> Downloaded: 
> https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/rocketchatnotifier/0.2.2-SNAPSHOT/maven-metadata.xml
>  (769 B at 0.6 KB/sec)
> Uploading: 
> https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/rocketchatnotifier/0.2.2-SNAPSHOT/rocketchatnotifier-0.2.2-20161112.135149-2.hpi
> Uploading: 
> https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/rocketchatnotifier/0.2.2-SNAPSHOT/rocketchatnotifier-0.2.2-20161112.135149-2.pom
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 21.366 s
> [INFO] Finished at: 2016-11-12T14:51:55+01:00
> [INFO] Final Memory: 50M/874M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on 
> project rocketchatnotifier: Failed to deploy artifacts: Could not transfer 
> artifact 
> org.jenkins-ci.plugins:rocketchatnotifier:hpi:0.2.2-20161112.135149-2 from/to 
> maven.jenkins-ci.org (https://repo.jenkins-ci.org/snapshots/): Failed to 
> transfer file: 
> https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/rocketchatnotifier/0.2.2-SNAPSHOT/rocketchatnotifier-0.2.2-20161112.135149-2.hpi.
>  Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
>
> I added the server id to my settings.xml and the credentials. I can manual 
> deploy via https://repo.jenkins-ci.org/webapp/.
>
> Any idea's what I'm doing wrong?
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/a0c73b9c-b26f-4f82-83c3-a4658f9083b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[R. Tyler Croy]

(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 Croy

--
 Code: 
  Chatter: 

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/20161115205112.GN3000%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: Admin/Ownership Repo Request

[Daniel Beck]

> 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 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 
https://groups.google.com/d/msgid/jenkinsci-dev/240A185E-D73E-404C-B8D0-520B8072B792%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

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

[Arnaud Héritier]

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 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 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 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 and unfortunately hitting these rate limits
> mean
> builds have been intermittently failing for pull requests and branches in
> ci.jenkins.io.
>
>
> If you're interested in seeing this integration re-enabled, I encourage
> you to
> contact Atlassian support and help them fix their plugin to hammer the API
> less
> than it does now.
>
>
>
> Cheers
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> --
>
> ___
> Jenkins-infra mailing list
> jenkins-in...@lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>
>
> --
> 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
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCPAaQXyEOX_f1YcGw9uXLvV8MnEW9aB4h88GitEViPuw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU--EJFuo3-e7h96Gza24nBS_GM6oqd9KC9QrkiwNGue2xA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Arnaud Héritier]

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 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 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 and unfortunately hitting these rate limits
>> mean
>> builds have been intermittently failing for pull requests and branches in
>> ci.jenkins.io.
>>
>>
>> If you're interested in seeing this integration re-enabled, I encourage
>> you to
>> contact Atlassian support and help them fix their plugin to hammer the
>> API less
>> than it does now.
>>
>>
>>
>> Cheers
>> - R. Tyler Croy
>>
>> --
>>  Code: 
>>   Chatter: 
>>
>>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
>> --
>>
>> ___
>> Jenkins-infra mailing list
>> jenkins-in...@lists.jenkins-ci.org
>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>>
>>
> --
> 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 https://groups.google.com/d/
> msgid/jenkinsci-dev/CAPfivLCPAaQXyEOX_f1YcGw9uXLvV8MnEW9aB4h88GitEVi
> Puw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_nUsn6YLu0oiyfw%2B%3DB3%2BrAXe%2Br_LO8SvRTvzBaCp-iCw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Oleg Nenashev]

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 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 and unfortunately hitting these rate limits
> mean
> builds have been intermittently failing for pull requests and branches in
> ci.jenkins.io.
>
>
> If you're interested in seeing this integration re-enabled, I encourage
> you to
> contact Atlassian support and help them fix their plugin to hammer the API
> less
> than it does now.
>
>
>
> Cheers
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> --
>
> ___
> Jenkins-infra mailing list
> jenkins-in...@lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCPAaQXyEOX_f1YcGw9uXLvV8MnEW9aB4h88GitEViPuw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 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 and unfortunately hitting these rate limits mean
builds have been intermittently failing for pull requests and branches in
ci.jenkins.io.


If you're interested in seeing this integration re-enabled, I encourage you to
contact Atlassian support and help them fix their plugin to hammer the API less
than it does now.



Cheers
- R. Tyler Croy

--
 Code: 
  Chatter: 

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/20161115175043.GL3000%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: Admin/Ownership Repo Request

[Simon Bennetts]

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 an existing plugin or starting a new one (eg 
zap-plugin).

Many thanks,

Simon Bennetts


On Tuesday, 15 November 2016 16:26:54 UTC, develop...@gmail.com wrote:
>
> 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 like admin/ownership of the 
> repository.
>
> Reason's as follows
>
>1. manage the team (to allow other devs have write access)
>2. Manage the features (Wiki's,restrictions, issues)
>3. Types of merges
>4. Manage web hooks
>
> Is there any reason or policy to give me write access but not 
> admin/ownership?
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/6b6b99a2-db56-4056-8da5-f244cfa2bf6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Admin/Ownership Repo Request

[developer . goran]

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 like admin/ownership of the 
repository.

Reason's as follows

   1. manage the team (to allow other devs have write access)
   2. Manage the features (Wiki's,restrictions, issues)
   3. Types of merges
   4. Manage web hooks

Is there any reason or policy to give me write access but not 
admin/ownership?

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/a257ceca-42ce-44e2-ab89-7fb2b99af85e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Someone to take over GHPRB

[Ben Patterson]

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 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 look for co-maintainer:
>
> https://wiki.jenkins-ci.org/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-
> HowcanImarkapluginforadoption%3F
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/iHBzu1sBOmI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/BDF8BF41-700E-457A-A853-A4A85EFE6A6C%40beckweb.net.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/CAAT-2mV62-NAr4gUR9qm0bfgm%3DCebigEJGTFqg0sVPUBS7rWxw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Someone to take over GHPRB

[Daniel Beck]

> 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 look for co-maintainer:

https://wiki.jenkins-ci.org/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-HowcanImarkapluginforadoption%3F

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/BDF8BF41-700E-457A-A853-A4A85EFE6A6C%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Someone to take over GHPRB

[Ben Patterson]

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 2.0, etc. If anyone has keen interest, please let
me/this-line know and let's get you collaborator or maintainer status.



On Tue, Sep 27, 2016 at 4:57 PM, Ben Patterson 
wrote:

> Well, my two cents is indeed to do things by the book in GitHub-land for
> the reasons that you mentioned (e.g., forks are still linked, etc.) But
> perhaps if that's going to be a protracted or painful process, it's worth
> reconsidering.
>
> On Tue, Sep 27, 2016 at 4:54 PM, Daniel Beck  wrote:
>
>>
>> > On 27.09.2016, at 22:09, Ben Patterson  wrote:
>> >
>> > It sounds good to me. FWIW I had submitted an issue to the 'current'
>> parent repo; I assume GH would only make the switch if all parties agree.
>>
>> Breaking the connection shouldn't need that -- we could delete the repo,
>> create a new one, then push --mirror to get a similar effect.
>>
>> That said, maybe inverting the link, making jenkinci's the root of the
>> network, would be preferable? Otherwise it's disconnected from all existing
>> forks.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/jenkinsci-dev/iHBzu1sBOmI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/9CCB5398-6D4E-4C60-AC9D-48604129CE27%40beckweb.net.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/CAAT-2mV2RpY%2B84onhi4sYF%2BTs78DaJ81Dj2X7U9FQstYROBiNw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Jacob Larfors]

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 repository 
is no longer taken care of...

What options do we have? Can we make the jenkinsci repository the "main" 
one and we will get our commits there? There arent really any valid PRs/FRs 
in Jira, and the few that are we could look to transfer or fix, as we quite 
actively work on this plugin and have been shipping hpi files for the past 
few years to avoid this mess and bottleneck of waiting for cittools.

Thanks for the help.

Jacob

On Tuesday, 15 November 2016 14:59:06 UTC+2, Jacob Larfors wrote:
>
> 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 tried contacting the owner of the repository for some time now 
> (gboissinot) with no luck.
>
> Should this not work, is there some way we can push our commits to the 
> jenkinsci repository and make this the one linked in Jenkins (i.e. make the 
> cittools repo redundant)? I assume that can be done without needing 
> cittools, but I will await a response from them out of courtesy.
>
> Thanks,
> Jacob
>
> On Tuesday, 15 November 2016 14:46:39 UTC+2, Daniel Beck wrote:
>>
>> 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 commits over. This however will not 
>> transfer existing issues and PRs in the cittools repo. IOW, it's a giant 
>> clusterfuck thanks to maintainers maintaining elsewhere. 
>>
>> I recommend you contact cittools and coordinate what to do with them. I 
>> can then transfer the repo as needed, and delete the one in jenkinsci that 
>> appears to have never been used. 
>>
>> > On 15.11.2016, at 12:58, Jacob Larfors  wrote: 
>> > 
>> > 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 to contact to get some action or even to apply 
>> for a transferral of ownership for a plugin that would be great. 
>> > 
>> > This is the plugin in question: 
>> https://github.com/cittools/klocwork-plugin 
>> > 
>> > My github account: jlarfors 
>> > 
>> > Thanks for the help! 
>> > 
>> > Jacob 
>> > 
>> > -- 
>> > 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-de...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/973c8a41-aac1-4c5f-a76e-5091bb8f3cee%40googlegroups.com.
>>  
>>
>> > For more options, visit https://groups.google.com/d/optout. 
>>
>>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/afe264e9-b0d9-463e-b964-9b892aa3b70f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Jacob Larfors]

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 tried contacting the owner of the repository for some time now 
(gboissinot) with no luck.

Should this not work, is there some way we can push our commits to the 
jenkinsci repository and make this the one linked in Jenkins (i.e. make the 
cittools repo redundant)? I assume that can be done without needing 
cittools, but I will await a response from them out of courtesy.

Thanks,
Jacob

On Tuesday, 15 November 2016 14:46:39 UTC+2, Daniel Beck wrote:
>
> 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 commits over. This however will not 
> transfer existing issues and PRs in the cittools repo. IOW, it's a giant 
> clusterfuck thanks to maintainers maintaining elsewhere. 
>
> I recommend you contact cittools and coordinate what to do with them. I 
> can then transfer the repo as needed, and delete the one in jenkinsci that 
> appears to have never been used. 
>
> > On 15.11.2016, at 12:58, Jacob Larfors > 
> wrote: 
> > 
> > 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 to contact to get some action or even to apply 
> for a transferral of ownership for a plugin that would be great. 
> > 
> > This is the plugin in question: 
> https://github.com/cittools/klocwork-plugin 
> > 
> > My github account: jlarfors 
> > 
> > Thanks for the help! 
> > 
> > Jacob 
> > 
> > -- 
> > 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-de...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/973c8a41-aac1-4c5f-a76e-5091bb8f3cee%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/5ba62706-bc9a-44c5-bdd3-c821a10b4c7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins failed using Ant Copy Command

[Daniel Beck]

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 jenkins. 
> 
> It was able to build the binary but my problem is the build is failing when 
> copying to a shared/mapped drive. 
> 
> see error below
> 
> "Attempt to copy Folder\dist\file.exe to \\shareddrive\file.exe using NIO 
> Channels failed due to 'failed to create the parent directory for 
> \\shareddrive\file.ex'. Falling back to streams. "
> 
> I have a separate buildbox that is windows 7 and is working fine, the issue 
> is only happening on my 2 Windows 2008 server. My jenkins account have write 
> permissions on the shared drive.
> 
> am i missing something? Any response are greatly appreciated.
> 
> thanks,
> John
> 
> -- 
> 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 
> https://groups.google.com/d/msgid/jenkinsci-dev/bd21ab4c-e764-4322-8aaf-cf639b8bce22%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/46DFAEF5-AE06-4905-90EA-8E0767E41708%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

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

[Daniel Beck]

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 commits over. This however will not transfer 
existing issues and PRs in the cittools repo. IOW, it's a giant clusterfuck 
thanks to maintainers maintaining elsewhere.

I recommend you contact cittools and coordinate what to do with them. I can 
then transfer the repo as needed, and delete the one in jenkinsci that appears 
to have never been used.

> On 15.11.2016, at 12:58, Jacob Larfors  wrote:
> 
> 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 to contact to get some action or even to apply for a 
> transferral of ownership for a plugin that would be great.
> 
> This is the plugin in question: https://github.com/cittools/klocwork-plugin
> 
> My github account: jlarfors
> 
> Thanks for the help!
> 
> Jacob
> 
> -- 
> 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 
> https://groups.google.com/d/msgid/jenkinsci-dev/973c8a41-aac1-4c5f-a76e-5091bb8f3cee%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/D0995CB1-0D80-4E25-BEB1-35D1CABEA7CD%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

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

[Daniel Beck]

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 the maintainer,
> or maybe we should wait one more week?
> 
> 
> W dniu poniedziałek, 7 listopada 2016 21:52:27 UTC+1 użytkownik Daniel Beck 
> napisał:
> Hi Zoran,
> 
> There were repeated attempts to contact you via GitHub, and it appears you've 
> stopped maintaining the jsch-plugin.
> 
> (See https://github.com/jenkinsci/jsch-plugin/pull/2 and the linked PR in 
> ssh-credentials-plugin)
> 
> Are you okay with us making Łukasz the new maintainer of the plugin?
> 
> Daniel
> 
>> Begin forwarded message:
>> 
>> From: Łukasz Jąder 
>> Subject: Re: [Plugin] Please review PR and release jsch-plugin
>> Date: 5. November 2016 um 23:16:00 MEZ
>> To: Jenkins Developers 
>> Reply-To: jenkin...@googlegroups.com
>> 
>> Hello Jenkins Admins,
>> 
>> Please grant me push / commit access to 
>> https://github.com/jenkinsci/jsch-plugin .
>> 
>> -- 
>> 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-de...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/c105513b-16f1-4dc7-bbad-6e6ccc39bf9e%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/88B03532-84B2-4A9B-9B33-E1B813778E6C%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

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 to contact to get some action or even to apply for 
a transferral of ownership for a plugin that would be great.

This is the plugin in question: https://github.com/cittools/klocwork-plugin

My github account: jlarfors

Thanks for the help!

Jacob

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-dev/973c8a41-aac1-4c5f-a76e-5091bb8f3cee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.