Re: [GSOC 2016] Support core plugin improvements

Hello Arnaud, Maybe you can do a quick JIRA KT at the next public office hours? As Oleg mentioned, it would make more sense if all the students are online, because we'll use Jira in one way or another. Regards, Alex On Mon, Jun 6, 2016 at 4:53 PM Arnaud Héritier wrote: > I did it this morning

Re: [GSoC2016] External Workspace Manager plugin development

I'd like to announce that an alpha version of the External Workspace Manager plugin has been released last week! It's public available for testing. You may find additional info on the blog post announcing the release: https://jenkins.io/blog/2016/06/30/ewm-alpha-version/ If you get the chance t

Re: R Plugin dependency

Hi, To answer your question, I think that the correct groupId for the R plugin is org.biuno.r, so the dependency would be: org.biouno.r r 0.2 But I don't know, isn't an easier way to achieve what you need? without writing a new plugin? Just a thought. Regards, Alex On Friday,

Decouple BuildSelector from Copy Artifact plugin into a separate repo

Hello, Currently I'm working to add more features to the External Workspace Manager plugin . One of the features that I need is to allow the user to choose a specific build from the upstream job. For this, I was thinking to integr

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 rena

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. Regards

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

Hello everyone, I have some concerns about how a specific build from the upstream job should be selected in the case of the plugin that I am currently developing: https://github.com/jenkinsci/external-workspace-manager-plugin. Please note that the plugin focus is mainly on Pipeline jobs. Based o

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

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 "Jenki

Re: Run Selector Plugin beta release

I've added two Jira issues for using the @Symbol annotation. - one for the Run Selector plugin https://issues.jenkins-ci.org/browse/JENKINS-37052 - and the other one for WS Cleanup plugin https://issues.jenkins-ci.org/browse/JENKINS-37054 Is it any particular Epic for @Symbol mig

Re: [GSoC2016] External Workspace Manager plugin development

Hello everyone, I'd like to make a new announcement: a beta version of the External Workspace Manager Plugin has been released. A summary of the features added to the previous alpha version: - Support for the Run Se

Re: [GSoC2016] External Workspace Manager plugin development

Hello, A few days ago I've released the External Workspace Manager Plugin version 1.0.0: https://wiki.jenkins-ci.org/display/JENKINS/External+Workspace+Manager+Plugin Usage examples and explanations are on the plugin's documentation page

Re: Pipeline steps reference not listing the external workspace manager plugin steps

Hello, Good point Martin. For example, I've seen that the *selectRun* step from the Run Selector Plugin is referenced on that list. AFAIK I haven't done anything different on the Run Selector than on the External Workspace Manage

Re: Interested in building your plugin on ci.jenkins.io?

Hello, I'd like to have one of my plugins, the run-selector-plugin , to be built on ci.jenkins.io too. From what I've seen, now it uses the GitHub Org plugin for this, so when I have the Jenkinsifle in the repository, the project should be auto