On Tue, Mar 24, 2020 at 1:21 PM Niv Keidan wrote:
> So first, we don't want all this redundant data to be saved (just flood our
> cloud with transients is a valid solution...?? )
`transient` makes sense for most cases.
> all the data that we DO want saved, when scaled up, can increase
Hi all,
It seems that docker-java-api-plugin does not have any active maintainer
anymore.
I would like to become one, if possible.
* Plugin repo : https://github.com/jenkinsci/docker-java-api-plugin
* Pending PR : jenkinsci/docker-java-api-plugin#5
* My GitHub ID : ericcitaire
Hello everyone.
We have a plugin that extends a cloud (among other classes) and we wish for
some cloud related data to be persistent between restarts.
This data changes very often and we need to make sure we save it every time
it changes.
At the moment, we are using
Why are you not pleased with it? What is it doing? What isn't it doing?
On Tue., Mar. 24, 2020, 9:50 a.m. Niv Keidan, wrote:
> Hello everyone.
>
> We have a plugin that extends a cloud (among other classes) and we wish
> for some cloud related data to be persistent between restarts.
> This data
Hey, thanks for replying.
Ok, so our plugin implements a cloud (that is saved in config.xml when
configured by the user, which is amazing)
This cloud object, after being instantiated (either loaded on startup or
changed in configuration), creates all sorts of objects (duh), and those
are being
This is an official request to be made a co-maintainer of the plugin
anchore-container-scanner-plugin
(https://github.com/jenkinsci/anchore-container-scanner-plugin) as part of
my job function.
I have filed the following issue:
https://issues.jenkins-ci.org/browse/INFRA-2552
I have opened the
