Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

Hi, The student is free to propose different solutions and different implementations in the proposal they submit. Another approach for this type of coding project is to use OpenAPI (but it probably did not exist

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

Hi Martin, Are we going to rewrite codes by using any one of the 3 plugins or write from scratch?? If its going to be from scratch, I find that its always best to cover all aspects of Jenkins to be covered under REST API. Similar to Bitbucket APIs, like connecting the configuration till

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

On Sat, Jan 26, 2019 at 1:42 PM martinda wrote: > What about JFrog's artifactory plugin, it uses a workflow-cps dependency...? And has had numerous problems as a result. > "GlobalVariable" exists but plugin developers should not use it? No, generally not.

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

> > At a minimum, use no `GlobalVariable`s or any > other `workflow-cps` dep, and use the `Step` API as it was designed > What about JFrog's artifactory plugin, it uses a workflow-cps dependency

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

On Wed, Jan 16, 2019 at 9:43 PM martinda wrote: > bitbucketClient.withServer(url: “foo://bitbucket”, project: project, repo: > repo, crendentialsId: “mybitbucket”) { Whatever you are writing here, it is not a `Step`. A step is a function (implemented for purposes of Groovy as a method with the

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

This looks good and yes, the step can have multiple methods. > On Jan 16, 2019, at 6:43 PM, martinda wrote: > > I am re-working the 3 REST API GSoC proposals... > > How does this example look like in terms of respecting the current execution > engine requirements: > >

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

I am re-working the 3 REST API GSoC proposals... How does this example look like in terms of respecting the current execution engine requirements: bitbucketClient.withServer(url: “foo://bitbucket”, project: project, repo: repo, crendentialsId: “mybitbucket”) { def response =

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

On Tue, Jan 8, 2019 at 9:17 AM Martin d'Anjou wrote: > So you are really saying that Jenkins needs a new type of execution engine in > order to support plugins that return non-simple data. No no, I am saying that Jenkins needs a new type of execution engine, and the proposed replacement would

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

> > > Besides not existing? So you are really saying that Jenkins needs a new type of execution engine in order to support plugins that return non-simple data. This is way beyond my level of expertise. Has anything been attempted or discussed in that area? > If you are limiting yourself to

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

On Sat, Jan 5, 2019 at 12:23 AM martinda wrote: >>> e.g. jenkinsRest.api().systemApi().version() -> return the version number >>> as a String? > > so is there a way forward for plugins of that type (those that intent to wrap > REST APIs of external services)? Besides not existing? At a

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

On Monday, December 31, 2018 at 9:34:58 AM UTC-5, Jesse Glick wrote: > > On Fri, Dec 28, 2018 at 5:49 PM martinda > wrote: > >> burden efforts to produce an alternate execution engine > > > > The two execution engines I know of are the scripted pipeline and the > descriptive pipeline. Is

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

On Fri, Dec 28, 2018 at 5:49 PM martinda wrote: >> burden efforts to produce an alternate execution engine > > The two execution engines I know of are the scripted pipeline and the > descriptive pipeline. Is there talks about a newer one? No, that is the same execution engine—`workflow-cps`

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

I have marked the google docs for all three as being discussed here. We may have to pull out those proposals if they prove to be problematic. burden efforts to produce an alternate execution engine > The two execution engines I know of are the scripted pipeline and the descriptive pipeline. Is

Re: [GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

I am afraid my immediate reaction to both this and the Artifactory REST plugin proposal is that we would be better off without such plugins. As an “emeritus maintainer” of `workflow-cps` I can say that this kind of feature is rather risky and prone to weird bugs, and would burden efforts to

[GSOC] Jenkins REST API Client Pipeline Wrapper Plugin Proposal

Hi, We currently have a Google Summer of Code proposal aimed at wrapping a Jenkins REST API Client into a Jenkins Pipeline Plugin. There are a few jenkins rest api clients which can be used to