Re: Docker workflow runs with user not fully configured

On Wed, Sep 7, 2016 at 3:58 PM, Samuel Van Oort wrote: > Nobody is trying to hide bugs from you or shoot holes > in the docker-workflow plugin, there are just some cases where docker.inside > isn't a good mapping to what is needed Understood, but if there is something the

Re: Docker workflow runs with user not fully configured

> It is not “known” to me, the plugin maintainer, so as I wrote in PR > 57: if there is a concrete, small, easily reproducible test case that > demonstrates something that does not work which you feel should, > please file it. > To clarify: I'm not saying that this is a result of a

Re: State of Xcode plugin??

Contacting hi was somewhat recently ... and I totally can appreciate maintainer's busy schedules (as I myself are also a maintainer on some plugins) ... some PRs are 4 yrs old, so doubt they're applicable any more, but some would be very useful and have been waiting 8 months. On Wednesday, 7

Re: State of Xcode plugin??

There is a process for these situation, but when did you contact them? Maintainers are often busy, Have you created issues and/or submitted pull requests to fix existing issues? On Tuesday, September 6, 2016 at 10:37:33 AM UTC-7, Brantone wrote: > > Curious as to the current state of Xcode

Jenkins Email Matrix on Dashboard

Hi Team, Is there anyway I show email matrix in the Jenkins Dashboard? I have a project with 5 different jobs. Each job triggers emails on success/failure. Now, I want a dashboard implementation where I could show the list of users who received the email from a particular job and timeline of

Re: Docker workflow runs with user not fully configured

On Wed, Sep 7, 2016 at 12:10 PM, Samuel Van Oort wrote: > this is a known issue around how > docker.inside is implemented. It is not “known” to me, the plugin maintainer, so as I wrote in PR 57: if there is a concrete, small, easily reproducible test case that

Re: Docker workflow runs with user not fully configured

Oliver, Apologies for the delayed response, but this is a known issue around how docker.inside is implemented. It was very painful when setting up the docker image. This is why the docs and workflow script for the docker image don't use docker.inside --

Pipeline AWS elastic beanstalk deploy

Hi All, would it be interesting to have a wrapper around the elastic beanstalk plugin so that it could be used from a pipeline step? If so and if in fact this does not exist I'm happy to code it. Thanks -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: JaCOCO plugin - Cannot see the jacoco plugin in Pipeline Snippet Generator.

Found a solution. Using the syntax given in this JIRA worked. https://issues.jenkins-ci.org/browse/JENKINS-37221 Thank you! On Wednesday, September 7, 2016 at 2:56:58 PM UTC+5:30, swaidy...@accelaero.com wrote: > > I know the current jacoco plugin doesn't support code coverage reports in >

JaCOCO plugin - Cannot see the jacoco plugin in Pipeline Snippet Generator.

I know the current jacoco plugin doesn't support code coverage reports in Pipeline. But i saw there is some work done in https://issues.jenkins-ci.org/browse/JENKINS-27120 with the PR https://github.com/jenkinsci/jacoco-plugin/pull/66 which is merged in to master. I built two jacoco.hpi from

Re: Plugin site prototype

Wondering if that should be somehow expressed in the hpi itself, or if it's fine/a feature to have it outside. I guess having it in the project itself would have an advantage: if a plugin goes from user-facing to only library-plugin (or the contrary), that could be expressed per version. Great

Re: [SPAM Low] [Proposal] - Release Jenkins 2.7.4 on this week

The test results[1] looks good. I am pushing the RC at the moment for manual retesting. Once confirmed, I am ok to get that released. FYI, I suggest[2] to have an explicit link type for issue that introduced another one. So hopefully, such situation will be lot less likely to reoccur. [1]