Re: Run Selector Plugin beta release

Use `successful` not `Successful` to match APIs like `lastSuccessfulBuild` (de-camel-cased). -- 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: Run Selector Plugin beta release

You should add `@Symbol`s to the various selector descriptors, so that def runWrapper = runSelector job: 'upstream-project-name', selector: [$class: 'StatusRunSelector', buildStatus: 'Successful'] could be written as def runWrapper = runSelector job: 'upstream-project-name', selector:

Re: Run Selector Plugin beta release

On Thu, Jul 28, 2016 at 10:42 AM, Alexandru Somai wrote: > I've added a Pipeline step: runSelector, which selects a specific > run from a given project name Probably `selectRun` would be a more natural step name—a verb. -- You received this message because you are

Re: problem after upgrading to Jenkins 1.625.3 from 1.625.1

On Thu, Jul 28, 2016 at 8:47 AM, Ido Gadiel wrote: > java.lang.NoClassDefFoundError: > org/jenkinsci/main/modules/sshd/SshCommandFactory Try adding a dep on the `sshd` module. Not sure why going from 1.642.1 to 1.642.3 would necessitate that. You can grep the changes

Re: Plugin extensions

On Thu, Jul 28, 2016 at 4:54 AM, Ioannis Canellos wrote: > I'd like to be able to change that defaults (both config and behavior), > just by installing an additional plugin. >From a UI standpoint this is generally a bad idea. -- You received this message because you are

Re: Most reliable way to get the build number of the build just executed using JS/jQuery

If you have control over the jobs and job triggering, you could add a parameter to the job that contains a UUID. You can then obtain the uuid of the builds easily and identify the builds. Or write your own plugin that adds the UUID as build action on execution. Something like the Job Run UUID

Re: Download stats no longer showing on some plugin-wikis

Am Donnerstag, 28. Juli 2016, 12:16:12 schrieb Kanstantsin Shautsou: > Maybe reset cache? Seems to be fixed now. At least, they are showing for the plubin maintained by me. > > >> Missing in > > >> > > >>

Re: Download stats no longer showing on some plugin-wikis

Maybe reset cache? On Thursday, July 28, 2016 at 1:12:46 AM UTC+3, Daniel Beck wrote: > > It was. > > It's fixed now, but we cache aggressively, so may require adding a query > string to the URL to circumvent the cache. > > > On 27.07.2016, at 17:29, Daniel Beck > wrote:

Re: Jenkins As service not able to connect to Git Lab through SSH

Once you added JGit to the system, then the job definition will have an additional choice added in the "Git" section. Use that choice to switch from "Default" to "jgit". You mentioned the .ssh directory on the computer. That should be irrelevant for a service, particularly since a service

Re: Jenkins As service not able to connect to Git Lab through SSH

No passphrase used for the private key. I have added JGit . *My git config file as below* *[core]* * repositoryformatversion = 0* * bare = false* * symlinks = false* * ignorecase = true* *filemode = true* *logallrefupdates = true* *precomposeunicode = true* *[remote "origin"]* *

Re: Run Selector Plugin beta release

> > >- Moreover, I've added a Pipeline step: *runSelector,* which selects a >specific run from a given project name, and returns a *BuildWrapper* > object. > > It's a *RunWrapper* object here. Typo. -- You received this message because you are subscribed to the Google Groups

Run Selector Plugin beta release

Hello everyone, I'd like to announce that I've released a beta version of the Run Selector Plugin . What does this plugin? - It offers the build selection strategies that used to be (actually still are) in the Copy Artifact Plugin

problem after upgrading to Jenkins 1.625.3 from 1.625.1

Hi I am developing a plugin and created few tests to check it. I used to run the tests with 1.642.1 and it all worked fine. Recently, I changed the version to 1.642.3 (or higher, 1.642.3 for example) and got Exception after the creation of JenkinsRule (JenkinsRule rule = new JenkinsRule();)

Re: Plugin Tests Memory Usage (Maybe jenkins rule)

So, we're getting inconsistent behavior, but definitely still seeing out of memory errors. Correct? On Tuesday, July 19, 2016 at 12:11:33 AM UTC-7, Gavin Mogan wrote: > > Across the board, openjdk 7, Oracle 7, Java 8 > > After adding the perm size and concurrency I still have 100℅ fail on

Re: Jenkins As service not able to connect to Git Lab through SSH

It appears from the output that you've defined an RSA private key credential in Jenkins and that you selected that credential as part of the job definition. That's good. It also looks like you're using the command line git implementation (rather than JGit). That's generally the preferred git

Re: Plugin extensions

A lot of examples are already part of core. If you are looking for a plugin that provides an extension point: https://github.com/jenkinsci/warnings-plugin Here one can create a new plug-in that just contains a new parser (sub-class of

Re: Plugin extensions

Extension Point. What else? :) https://wiki.jenkins-ci.org/display/JENKINS/Defining+a+new+extension+point Le 28 juil. 2016 10:54 AM, "Ioannis Canellos" a écrit : > I want to create a plugin that assume some default configuration and > behavior. > > I'd like to be able to

Plugin extensions

I want to create a plugin that assume some default configuration and behavior. I'd like to be able to change that defaults (both config and behavior), just by installing an additional plugin. In flat classpath I could use java.util.ServiceLoader to implement something like that. What is the

Jenkins As service not able to connect to Git Lab through SSH

Building in workspace C:\Program Files (x86)\Jenkins\jobs\ApiV1\workspace > C:\Program Files\Automation\Git\bin\git.exe rev-parse --is-inside-work-tree > # timeout=10 Fetching changes from the remote Git repository > C:\Program Files\Automation\Git\bin\git.exe config remote.origin.url >