So thanks for pointing that out, I had a return when i meant continue (i'm
pretty sure it was in a forEach, i just converted to a for and used
continue)
One I noticed was (cause i was curious what it does):
https://www.jenkins.io/doc/pipeline/steps/kubernetes-pipeline-arquillian-steps/
*exists*
agree would be great if they could be merged
and also the jenkins core (and winstone) CLI enhanced with a more modern
CLI library
On Tue, 22 Dec 2020 at 18:13, Slide wrote:
> Hi Everyone,
>
> Currently we have two hosting requests open (
>
Hi Everyone,
Currently we have two hosting requests open (
https://issues.jenkins.io/projects/HOSTING/issues/HOSTING-1048 and
https://issues.jenkins.io/projects/HOSTING/issues/HOSTING-1046) for CLI
tools that interact with Jenkins. I would like to get some feedback on
ideas on how to move forward
Some of these are ones that don't necessarily need an issue tracker
anywhere, like publish-over or snakeyaml-api (there may be more). Those are
component plugins that don't really require having an issue tracker of
their own. windows-cloud is a recently hosted plugin that used the new
field in the
Hi Ewelina
I extracted the components from the Jira API:
https://issues.jenkins.io/rest/api/2/project/JENKINS/components
➜ Documents cat jenkins-components.json | jq '.[] | {name, lead: .lead.name}'
| grep -B 1 "praqma"
"name": "clearcase-plugin",
"lead": "praqma"
--
"name":
Hi!
Praqma is now a part of Eficode and we want to make sure all the plugins
that are being maintained by my colleagues from both companies are getting
the attention when the new issue comes.
For that reason I have created a new jenkins.io user - *eficode* - and I'd
like to ask for help
