On Thu, Oct 21, 2021 at 3:47 PM Baptiste Mathus wrote:
> Care to elaborate what you mean and how that would work? IIUC, what you're
> describing would quite entail refactoring all existing "xyz-plugin
> developer" groups on GitHub side?
> And as you know we currently have close to no notion of
On Wed, Oct 20, 2021 at 10:05 AM Oleg Nenashev
wrote:
>
>- What would everyone say about introducing dependency on
>testcontainers into Jenkins Test Harness directly?
>
> Why would you need that when you can already add such a test dep yourself?
>
>- Should we go ahead and deprecate
Sounds good, could probably have one for the Jenkins core team too in RPU.
On Thu, 21 Oct 2021 at 14:47, Baptiste Mathus wrote:
>
>
> Le jeu. 21 oct. 2021 à 13:58, 'Daniel Beck' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> a écrit :
>
>>
>>
>> On Thu, Oct 21, 2021 at 1:47 PM
Le jeu. 21 oct. 2021 à 13:58, 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> a écrit :
>
>
> On Thu, Oct 21, 2021 at 1:47 PM 'jn...@cloudbees.com' via Jenkins
> Developers wrote:
>
>> Additionally to make RPU easier, we are planning to add support for
>> groups of users
Darin Pope and I have been live streaming a series of small steps to
improve a plugin while preparing to adopt the plugin. We'd like to adopt
the TestNG result reporter plugin so that we can use it to show how the
plugin bill of materials makes plugin maintenance easier.
Plugin:
On Thu, Oct 21, 2021 at 1:47 PM 'jn...@cloudbees.com' via Jenkins
Developers wrote:
> Additionally to make RPU easier, we are planning to add support for groups
> of users so that we would just need to modify a single "group definition
> file" to update permissions in artifactory.
>
Sounds
While I don't know yet how it would work with our existing tooling, I am in
favor of that approach and that would also be useful for other companies as
well
On Thursday, 21 October 2021 at 13:47:24 UTC+2 jn...@cloudbees.com wrote:
> Hi all,
>
> CloudBees has a number of plugins in jenkins-ci
Hi all,
CloudBees has a number of plugins in jenkins-ci organisation that we are
maintainers of.
Currently when our internal teams change we need to modify multiple GitHub
repo settings and associated permissions RPU. This is cumbersome (and
error prone) for us, and for the reviewers of the
2.317 looks good to me. No objections w.r.t 2.318 too, but we do not know a
full scope yet.
Personally I would be happy to get Winstone BOM into it
(https://github.com/jenkinsci/winstone/pull/172), but I do not think it is
a justification on its own.
This patch is just a quality of life
ullrich...@gmail.com schrieb am Mittwoch, 20. Oktober 2021 um 17:03:02
UTC+2:
> As Jim already mentioned, you should use the Git Client Plugin to access
> the Git repositories. If you need an example on how to use that you can
> look into the tests of the Git Client Plugin (
>
10 matches
Mail list logo
