Re: JenkinsRule and docker

On Thu, Apr 25, 2019 at 7:06 PM Ullrich Hafner wrote: > Is someone already writing integration tests that use agents that are > provided by a docker container and has an example to share? Various plugins use the `docker-fixtures` library for this. For example, with `DockerClassRule` it is

Re: JenkinsRule and docker

If you already depend on the git plugin, you could consider using TestGtiRepo from the git plugin tests as somewhat of a convenience class for a git repository. If you already depend on the git client plugin, you could consider using CliGitCommand as a convenience method to perform calls to

github app approval for jenkinsci org?

Who should I contact about getting a GitHub app approval for jenkinsci org. Feel overkill firing off to the mailing list and inside Jira, it will just be lost in the sea. The specific app in question is: https://github.com/apps/settings

Re: JenkinsRule and docker

We have some integrations tests for Vault, I would imagine it could be very similar to a git docker container. https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/plugin/src/test/java/io/jenkins/plugins/casc/vault On Friday, April 26, 2019 at 1:06:03 AM UTC+2, Ullrich Hafner

Re: JenkinsRule and docker

We have some integrations tests for Vault UI, I would imagine it could be very similar to a git docker container. https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/plugin/src/test/java/io/jenkins/plugins/casc/vault On Friday, April 26, 2019 at 1:06:03 AM UTC+2, Ullrich

JenkinsRule and docker

I’m currently trying to write some integration tests with Jenkins test harness (i.e. JenkinsRule) that were previously part of ATH. For some of the ATH concepts I did not yet find a counterpart in our integration tests. Is someone already writing integration tests that use agents that are

Re: OpenLab Testing

It certainly looks pretty neat, and their infrastructure for testing could be great for testing more complicated plugin setups. On Thu, Apr 25, 2019 at 3:38 PM Kohsuke Kawaguchi wrote: > > In my recent trip to Jenkins User Conference China, I met with folks from > Huawei who are behind the

OpenLab Testing

In my recent trip to Jenkins User Conference China, I met with folks from Huawei who are behind the OpenLab Testing project . The way I understood it, it's basically a community and free compute resources for integration testing open-source solutions. I think their

Re: CD.Foundation Update

Hi Tracy, One small bit of feedback from me (I'm on the Jakarta EE, JCP & AdoptOpenJDK boards). It's pretty std practice these days to also make the governing board minutes available (with one or two redactions if really necessary) - something worth raising. Cheers, Martijn On Tue, 23 Apr

Re: Infrastructure issues

On Thu, Apr 25, 2019 at 3:58 AM pallen wrote: > > https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fp4-plugin/detail/PR-97/1/pipeline https://issues.jenkins-ci.org/browse/INFRA-2075 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: Not inheriting Overall/* permissions

On Wed, Apr 24, 2019 at 7:17 PM Daniel Beck wrote: > What is the correct behavior for authorization realms here? Should Overall/* > permissions be inherited by all ACLs? It should not really matter since any code even calling `hasPermission` / `checkPermission` against a permission using

Re: Infrastructure issues

I think you'll get better visibility on the jenkins-infra mailing list, or the INFRA project in Jira. > On 25. Apr 2019, at 09:58, pallen wrote: > > Hi Guys, > > I have been running into a few infrastructure related issues when building > the p4-plugin. > > >

Jenkins 2.164.3 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2019-05-08. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.164.3/jenkins.war Thanks! -- oliver -- You received this

Infrastructure issues

Hi Guys, I have been running into a few infrastructure related issues when building the p4-plugin. https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fp4-plugin/detail/PR-97/1/pipeline Is it possible to get a slightly better Windows resource as some of my polling tests fail due to