Re: jenkins-violation-comments-to-stash-plugin

Hi Tomas Bjerre, Could you please let me know whether this plugin will enable comments from static code analyzer in "Atlassian-hosted BitBucket Cloud" or only in BitBucket Server(Stash) ?. Is there anyother plugin available to enable this in "Atlassian-hosted BitBucket Cloud" the one like

Re: Decouple BuildSelector from Copy Artifact plugin into a separate repo

Hello. Thanks for the repository. I don't have so much time to participate in the development, and alexsomai is the maintainer of this plugin. I'll participate in the development only by sending a pull request. >> CopyArtifactPermissionProperty. I think it shouldn't moved to >>

Re: [Multibranch] Add some other possibilities to set the folder name of the branch project

On Mon, Jul 4, 2016 at 11:45 AM, Quentin Dufour wrote: > If the branch has a really long name, it will cause path too long execptions > on Windows (our project). Well known, JENKINS-34564, use `dir` or `ws` steps as a workaround if you cannot fix your tools. -- You

Re: help wanted: releasing to experimental update center (blue ocean)

On Mon, Jul 4, 2016 at 5:34 AM, Stephen Connolly wrote: > On the other hand the property is one of the "magic" ones whereby if > unspecified it is the parent url plus the artifactId (depending on whether > the parent url has or doesn't have a trailin / or some

Re: [Multi-Branch Project Plugin] Should it be possible to reconfigure branches?

On Fri, Jul 1, 2016 at 10:22 PM, Matthew DeTullio wrote: > I think the only way to prevent direct configuration involves using > project-based matrix authorization as your security strategy. `branch-api` does this automatically, FWIW. -- You received this message because

Re: Unable to deploy plugin

And right with the last attempt it worked : Thanks for the pointer, it seems I'm good for now. -- Andrey четверг, 7 июля 2016 г., 0:45:42 UTC+3 пользователь Andrey Pohilko написал: > > I've tried to update parent dependency to 2.x, but whole bunch of > compilation problems arise. It is

Re: Unable to deploy plugin

I've tried to update parent dependency to 2.x, but whole bunch of compilation problems arise. It is too much for me, I just wanted to release small fixes. I've tried other ideas from commits linked to INFRA-588 , but nothing changes. URL does

Re: Decouple BuildSelector from Copy Artifact plugin into a separate repo

Hello, Thank you Oleg for setting-up the repo. The first step that I'll do is to remove the deprecated features and code that was inherited from the Copy Artifact plugin. I'll create a PR as soon as I'm done with this. Afterwards, I think that we should rename the packages and classes.

Re: Decouple BuildSelector from Copy Artifact plugin into a separate repo

Hello, The code has been copied to https://github.com/jenkinsci/run-selector-plugin . I decided not to do perform a GitHub fork in order to avoid future links between two plugins in history search and Github's diff interfaces. Can convert it to fork if there are strong opinions. alexsomai and

Re: How to enable Travis CI for jenkins plugin repo

Done. > On 06.07.2016, at 11:12, Andrey Pohilko wrote: > > Can anybody help me enabling it? -- 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: JGit api changed - Handling removal of methods from an underlying API

Will do. My current goal is to investigate other ways of resolving the issue without requiring that every plugin which depends on JGit must update at the same time. For example, one of the experiments I hope to perform is to see if a dependent plugin could catch the runtime exception due to

Re: How to enable Travis CI for jenkins plugin repo

Try contact INFRA team and ask them to provide admin access to your plugin. On Wednesday, July 6, 2016 at 12:12:07 PM UTC+3, Andrey Pohilko wrote: > > Hi, > > I'm the maintainer for performance-plugin repo. > > I'm trying to use my typical approach with controlling the project quality > using

Re: [Jenkins World 2016 ] Get 20% OFF

AFAIK there is an events list for such announcements. And this list is about development https://groups.google.com/forum/#!aboutgroup/jenkinsci-dev 2016-07-06 20:20 GMT+03:00 Alyssa Tong : > My apologies this came across as spam. Just wanted to share the 20% > discount. > >

Re: [Jenkins World 2016 ] Get 20% OFF

My apologies this came across as spam. Just wanted to share the 20% discount. On Sat, Jul 2, 2016 at 12:15 PM, Samat Davletshin wrote: > Yes, a bit too similar to a TV ad selling a brand new juicer :-) > May be a less persistent message would look better for a developer

Unable to deploy plugin

Hi, I'm using the instruction from here: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org I'm running "mvn release:prepare release:perform". And getting this: [INFO] [ERROR] Failed to execute goal

Re: JGit api changed - Handling removal of methods from an underlying API

I have released Gerrit trigger 2.22.0-beta-1, thanks to a helpful contribution, with the needed JGit 4 changes for users to try out. A helpful ping when Git Plugin 3 is released to main update center would be nice, so I can do the same. /B On Wed, Jun 22, 2016 at 7:43 PM, Jesse Glick

Re: Decouple BuildSelector from Copy Artifact plugin into a separate repo

Hello, If required, I could create a clone of the plugin directly in the jenkinsci > organization and make you both plugin developers. > This would be useful. I think that the PR #71 from Copy Artifact plugin should be also merged as it is into the new repository. Afterwards, we can start

How to enable Travis CI for jenkins plugin repo

Hi, I'm the maintainer for performance-plugin repo. I'm trying to use my typical approach with controlling the project quality using GitHub+TravisCI+Codecov integration, which proven its value for me. However, I'm missing the admin right on repo to enable TravisCI for it. Can anybody help me

Re: Decouple BuildSelector from Copy Artifact plugin into a separate repo

Hi, The approach looks good to me. We really have much plugins, which may benefit from the Build Selector functionality. If required, I could create a clone of the plugin directly in the jenkinsci organization and make you both plugin developers. >From the terminology perspective, maybe makes