Re: Docker workflow runs with user not fully configured

[Jesse Glick]

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 plugin could be doing
better, I would like to have it filed. Or if it is not feasible to
change the Jenkins behavior, perhaps the documentation could clarify
and emphasize those limitations.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0B%2BASL5Hz97xsn9DpOZEphRsikOYr%3D39S6K7ccNcq%3Dmg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker workflow runs with user not fully configured

[Samuel Van Oort]

 

> 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 *problem* with how 
docker.inside is implemented, just that there is a bad interaction between 
the fairly reasonable implementation and what packaging needs to work fully 
(more than normal).  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 so another approach is 
best used, and this is one.

FWIW there's no guaranteed, comprehensive way to create and fully configure 
a user at runtime across all containers. When needed that is best handled 
within the container builds (or with helper scripts if you need to control 
the created user at runtime).  Containers may contain stripped-down 
distributions without the normal user management facilities (or with very 
feature-limited versions if core utilities are not included).  At this 
point I don't assume that *anything* exists and works in a base image until 
I see it run successfully.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/17f23bfe-4719-43c0-a51a-f1fdb5e9bab1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: State of Xcode plugin??

[Brantone]

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 September 2016 11:05:40 UTC-7, Liam Newman wrote:
>
> 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 plugin. Although there was a 
>> recent merge last month, there hasn't been a release in almost a year and a 
>> list of PRs piling up.
>> I've attempted to contact current maintainer about helping out, but have 
>> not heard word back.
>> Is there a process for such a situation??
>> With changes in Jenkins 2.x and Xcode 8, would be a shame for the plugin 
>> to get further behind.
>>
>> Cheers
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2202b3c1-c250-49c6-bb56-42e100c32661%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: State of Xcode plugin??

[Liam Newman]

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 plugin. Although there was a 
> recent merge last month, there hasn't been a release in almost a year and a 
> list of PRs piling up.
> I've attempted to contact current maintainer about helping out, but have 
> not heard word back.
> Is there a process for such a situation??
> With changes in Jenkins 2.x and Xcode 8, would be a shame for the plugin 
> to get further behind.
>
> Cheers
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9c4d9514-eaf8-4ffd-8210-b33704ae2e5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Email Matrix on Dashboard

[Milan Chawla]

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 the email.

Any help in implementing this would be really appreciated.

Thanks & Regards,
Milan Chawla

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/b31446d5-0ab4-47ad-a3fc-bbe85c40395e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker workflow runs with user not fully configured

[Jesse Glick]

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
demonstrates something that does not work which you feel should,
please file it.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2Yy0dqzga7Vc91Q4nL4sE6t64Dpy-WXMXW0wx36qwD%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker workflow runs with user not fully configured

[Samuel Van Oort]

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 
-- https://github.com/jenkinsci/packaging/blob/master/docker/README.md
When using the packaging image in Jenkins builds, we have to invoke Docker 
manually (or run with arguments) rather than using the inside command. 

The sudo-able packaging test images use a different approach, by applying 
templating to Docker files and rebuilding so you can always have a 
correctly permissioned user. 

After some tinkering, I hit upon a much better way to do this, by 
dynamically creating a user within the container on the fly (which is also 
granted sudo permissions within the container).   There's a PR out for 
this: https://github.com/jenkinsci/packaging/pull/54

It's still pending review from someone though, but it's been tested out and 
works (was actually used for something small).  If it gets the community 
nod, we could merge and have a more robust system (the approach you use 
requires having a local user created). 

Hope that helps clarify somewhat!

Sam




On Friday, September 2, 2016 at 6:06:08 AM UTC-4, ogondza wrote:
>
> I am tying to get jenkinsci/packaging to work from Pipeline using 
> docker-workflow-plugin: 
>
> ``` 
>  builder = docker.build 'jenkins-packaging-builder:0.1' 
>  builder.inside { 
>  sh "make rpm ..." 
>  } 
> ``` 
>
> All seems well except that rpmbuild comaplins at a couple of places: no 
> $HOME is defined, the uid/gid for generated files does not exist in the 
> system. 
>
> The problem is the pluign instructs docker to "use" user with uid/gid 
> matching the outer user (so filesystem can be shared) but the user 
> account does not exist inside. It seems that docker "creates" the user 
> to come extend but it is not fully configured causing tools to fail in 
> weird ways. 
>
> I guess I can switch to use the container as root somehow or update the 
> image to create some user for this purpose but this seems like an 
> inherent struggle with the approach. What is the best practice here? 
>
> In case it is relevant I am using docker 1.10.3 and 
> docker-workflow-plugin 1.6. 
>
> Thanks 
> -- 
> oliver 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/232b7b90-bbb5-4f57-85ee-b8892833f10b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline AWS elastic beanstalk deploy

[Ricardo Espirito Santo]

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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5f07d64e-c60f-4ac6-9398-4dbadd7a7f9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[swaidyarathna via Jenkins Developers]

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 
> 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 both master branch and mheinzerling_2.1.0 
> branch but I don't see the jacoco comes into the Pipeline Snippet 
> Generator.
> Can some one help me to sort this out? Thank you very much. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/fdf5e718-0d93-44d2-b8b0-e708cc2f62d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[swaidyarathna via Jenkins Developers]

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 both master branch and mheinzerling_2.1.0 
branch but I don't see the jacoco comes into the Pipeline Snippet Generator.
Can some one help me to sort this out? Thank you very much. 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/cc6cfd63-706f-4fdf-9f33-fa78f1aebf79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin site prototype

[Baptiste Mathus]

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 work BTW!

-- Baptiste

2016-09-06 10:51 GMT+02:00 Robert Sandell :

>
>
> On Tue, Sep 6, 2016 at 2:21 AM, Daniel Beck  wrote:
>
>>
>> > On 01.09.2016, at 21:43, Gus Reiber  wrote:
>> >
>> > At the moment, we lack any sort of metadata to make that distinction,
>> but I think that would help the site greatly.
>>
>
>
>>
>> We could introduce the 'library' category of plugins and add a special
>> meaning to that.
>>
>
> It already exists https://wiki.jenkins-ci.org/label/JENKINS/plugin-library
>
>
>>
>> However I wouldn't make that hide the plugin -- there may be legitimate
>> uses to want to learn about it -- just deemphasize it (e.g. lower ranking)
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/515693DD-6F7E-47FB-B753-C44D2E5A6EDF%40beckweb.net.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Robert Sandell
> *Software Engineer*
> *CloudBees Inc.*
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CALzHZS2GhXLz31m2XDjiVfgdcv2Am
> TRPCJ4qLGGVs-UhKXXH2g%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7f6W%2BOquvPzOVNvT7e4GG%2BGiBWy5DEi771%3DqkHw4gjLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[ogondza]

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] 
https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness-stable-2.7/1/
[2] https://issues.jenkins-ci.org/browse/INFRA-915

--
oliver

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2cef2e9a-2620-4254-8418-ddcb8ab6a86b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.