Re: Publish EZ-Templates plugin

[Marc Carter]

#1
ez-templates-1.1 was deployed to the repo on Dec 14th ...
  http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/ez-templates/
... but it's plugin info on the wiki page is blank ...
  https://wiki.jenkins-ci.org/display/JENKINS/EZ+Templates+Plugin
... and it doesn't appear in the update center...
  https://updates.jenkins-ci.org/download/plugins/

What did I miss?

#2
Can I have admin on jenkinsci/ex-templates-plugin please

-- 
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/b7bdf2ab-1b3b-49e3-849c-cac431360f76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Is there any way to post message from slave to Jenkins job console

[Hari Praswin]

Hi,

I'm in need of posting info about ongoing test plan and test case from 
slave to jenkins job console in order to see the clear progress of the 
build.

Is there any way to access jenkins job console from slave, if so please 
share your thoughts.

Thanks,
Ari

-- 
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/22c22d54-c113-4ca4-b050-c950e6a60b38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for hosting: CPWR-PDS-download

[Christopher Orr]

Good question.  CC'd Chad, who emailed me asking about the status here.

If it doesn't make sense to combine them, I think the plugins seem ready
to fork.

-Chris


On 14/12/15 16:24, Andrew Bayer wrote:
> Out of curiosity, would it make more sense to combine these into one
> compuware-download plugin rather than splitting it into two plugins? It
> seems like it'd make things a bit simpler for users.
> 
> A.
> 
> On Mon, Dec 14, 2015 at 9:40 AM, cpwr_jenkins
> mailto:chad.seip...@compuware.com>> wrote:
> 
> We have changed the artifacts to compuware-pds-download and
> compuware-endevor-download. Please let us know if there is any more
> issues!

-- 
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/5670A522.8000901%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

['Yoann Dubreuil' via Jenkins Developers]

Hi Surya,

Thanks for your reply, I've a few questions below.

On Tue, Dec 15, 2015 at 4:43 PM, Surya Gaddipati 
wrote:

> Hi Yoann,
> Thank you for your response.
>
> >  I was wondering what was missing to rewrite a simplified version of it.
>
> So here are couple of things that I found needed to be changed
>
> 1. changed to use spotify-docker api client instead of command line, I
> needed it to talk to docker-swarm to allocated nodes
>

AFAICT, you can use a swarm endpoint with docker CLI,  you don't need a
special API for this. The docker API is a fast moving target, so wrapping
the CLI was convenient for experimenting.


> 2. Slaves are allocated based on job label not job property, much like
> cloud plugins
>

We had that feature in mind too, but didn't implement it yet.


> 3. We didn't need to run builds in another image/side image ect, we use
> docker-compose to run builds.
>

That's interesting, I don't understand why you need a docker slave then ?
Is it just to run a SCM checkout and then call docker-compose to do the
build ? I imagine that you are bind mounting the docker socket in the slave
node so you can run docker-compose?


> 4. Had to remove couple of hacks like this
> ,
> since we don't store builds on disk.
>
5. We didn't need jenkins user mounting .
>

Not sure to understand, do you mean that you don't need to tie a docker
volume to a container?


>
> This plugin simply allocates a new slave via jnlp/docker api calls. There
> is no extra magic.
>

Ok, so you just want a simple docker slave to be able to use docker-compose.

The fundamental idea behind our plugin was to replace the process startup
API with docker. Because in the end, what you want to do to build a
software is to run some commands in a controlled environment. Currently,
Jenkins achieves this by allocating a build slave, by installing all the
tools you need in it and by calling execve. This is exactly what Docker is
for. From my POV, Docker is an a API to launch a process in a controlled
environment. The container story is not interesting here. That's why I
don't think the Jenkins Cloud model fits well, Docker is not a way to
provide a slave from a light VM system. It is convenient but it's not the
optimal way to integrate Docker and Jenkins (again, my POV).

You use case it not that far, the difference is instead of starting a
random process from Jenkins after the checkout, you start docker-compose.

Feel free to correct me if I'm wrong. I really would like to understand
your use case well so I can understand the gap with existing plugins.


>
> Surya
>
>
>
>
> On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
>>
>> This is not a hosting request. I am hoping to get some feedback on the
>> plugin and see if its worth hosting/merging into other plugins.
>>
>> Details are in the readme of the project
>> https://github.com/suryagaddipati/jenkins-docker-slaves
>>
>>
>> Pls, let me know if you have any questions.
>>
>> Surya
>>
>> --
> 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/57db95e2-f8df-4015-9d91-3705a852aa3d%40googlegroups.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/CAFWoUpSg7Gwz1sh8ZubVFAanbkRyOes58vrvcS95mjaSB9UvFw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: CRX Content Package Deployer Plugin

[Mark Adamcin]

Hi Dean,

If you are building an hpi/jpi file and uploading it manually, you probably
have to restart the jenkins instance for the plugin to be activated.

I test it using mvn hpi:run, which runs a local jenkins instance with the
plugin already installed.

Mark Adamcin
http://adamcin.net/

On Tue, Dec 15, 2015 at 7:44 AM, Dean Anderson 
wrote:

> Has anyone downloaded the source code, built the code and SUCCESSFULLY
> deployed the code into Jenkins?
>
> I can download the code and get it to build.  Then, I can successfully
> install the plugin into Jenkins.
>
> However, for some reason it doesn't show up as an available plugin when
> I select "This build is parameterized", then click on Add Parameter.
>
> If I download the plugin from
> https://wiki.jenkins-ci.org/display/JENKINS/CRX+Content+Package+Deployer+Plugin
>  everything
> seems to work fine and it does show up when I click "Add Parameter" as
> described above.
>
> Any thoughts or suggestions are greatly appreciated.
>
> Thank you.
>
> -Dean
>
> --
> 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/CAHjWn6GFHRRZhV8xf%2BDP5fTgFo83M1On10Q1T3o3-%3DsBmqdF%3Dg%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/CACw%2B4smxLVUhzH2qDwuk6P92GEMezbuboZ3%2B80J9G1ie4zrisw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Surya Gaddipati]

> Do you think that the cloud API *ought* to be good enough for docker 
containers ? 

Not quite sure what you mean. But yea cloud api should support single use 
throwaway slaves that are tied to a single build. 

On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
>
> This is not a hosting request. I am hoping to get some feedback on the 
> plugin and see if its worth hosting/merging into other plugins.
>
> Details are in the readme of the project 
> https://github.com/suryagaddipati/jenkins-docker-slaves 
>
>
> Pls, let me know if you have any questions.
>
> Surya
>
>

-- 
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/dc03f38b-d7c3-4fab-a1e6-cebc42de2bd5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Nigel Magnay]

>
>
>
> nigelm,
>
> It uses queue listener to look for a label and add a slave .
>
> Docker has many, many load balancing tools , docker swarm for example. You
> can simply point jenkins to your swarm instance for docker.
>
> I see no reasons why Jenkins would be doing load balancing with docker
> containers when there are much more advanced/sophisticated solutions out
> there.
>
>
​Oh, that's easy - because you may not be using swarm. You may have docker
hosts that are unable​ to participate in a single swarm. You may have
slaves that aren't docker that you'd also like to use.

I think this is besides the point I was trying to make. I'll invert your
question. Do you think that the cloud API *ought* to be good enough for
docker containers ?

-- 
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/CAPYP83Rad8%2BtKTFv7cwUWcwYhdkcgkLA1Bf0JA1oXC2bK6zyqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: create-text-file plugin - New hosting reuest

[Daniel Beck]

On 15.12.2015, at 17:06, Sanketh P B  wrote:

> could you please provide commit access for the same?

I did. You just need to accept the invitation into the jenkinsci organization 
by GitHub.

-- 
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/0E64F267-5F45-48CD-95BC-7B0FE2DC67FE%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Nigel Magnay]

I haven't fully grokked how the alternative launch scheme works (I assume
it's operating as a launcher higher up the food chain). I don't know if
this is giving you options of controlling the build environment before it
is launched based on the build it is about to execute.

I would imagine you could add a similar launcher into (say) docker-plugin.
90% of this stuff is the same (UI to capture user settings); the heavy
lifting is deferred to a library anyway (e.g docker-java); there's only
really a tiny difference in each (cloud api implementation, launcher).

The cloud API is "sufficient" (in that bar the point above) it allows the
lifecycle you need. There's plenty of people using it that way. That's not
so say that it doesn't have problems. What's a touch depressing is ISTM
that the non-cloud-API approach is eventually going to come full-circle and
re-implement all the same stuff the cloud API is supposed to :-/ E.g:
balancing between hosts based on their current active workload. I would
have though that the two things you mention (pause before starting,
attaching start logs to the relevant build) ought to be solveable in the
core -- that way *all* cloud provisioners would benefit..





On Tue, Dec 15, 2015 at 4:31 PM, Surya Gaddipati 
wrote:

> So, do you agree that  cloud api is not good enough for docker containers ?
>
> On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
>>
>> This is not a hosting request. I am hoping to get some feedback on the
>> plugin and see if its worth hosting/merging into other plugins.
>>
>> Details are in the readme of the project
>> https://github.com/suryagaddipati/jenkins-docker-slaves
>>
>>
>> Pls, let me know if you have any questions.
>>
>> Surya
>>
>> --
> 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/0c0844f7-8c5f-410a-9781-ca1c04588686%40googlegroups.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/CAPYP83R66g%2BKbFDaUx-45kMrHrOydNCRjCrvRy10nhVSgTZW5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Surya Gaddipati]

nigelm, 

nigelm,

It uses queue listener to look for a label and add a slave . 

Docker has many, many load balancing tools , docker swarm for example. You 
can simply point jenkins to your swarm instance for docker. 

I see no reasons why Jenkins would be doing load balancing with docker 
containers when there are much more advanced/sophisticated solutions out 
there. 

Surya
On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
>
> This is not a hosting request. I am hoping to get some feedback on the 
> plugin and see if its worth hosting/merging into other plugins.
>
> Details are in the readme of the project 
> https://github.com/suryagaddipati/jenkins-docker-slaves 
>
>
> Pls, let me know if you have any questions.
>
> Surya
>
>

-- 
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/912ea3b4-255e-4e4c-affd-24c3cd260ead%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Surya Gaddipati]

So, do you agree that  cloud api is not good enough for docker containers ?

On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
>
> This is not a hosting request. I am hoping to get some feedback on the 
> plugin and see if its worth hosting/merging into other plugins.
>
> Details are in the readme of the project 
> https://github.com/suryagaddipati/jenkins-docker-slaves 
>
>
> Pls, let me know if you have any questions.
>
> Surya
>
>

-- 
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/0c0844f7-8c5f-410a-9781-ca1c04588686%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Core PR - review

[Surya Gaddipati]

Hi All,

Is there anything I can do get this PR reviewed.

https://github.com/jenkinsci/jenkins/pull/1934 

This is blocking us from running Load Balanced Jenkins ( without shared 
disk).

Surya

-- 
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/b8ec67cd-f7b7-4d8d-9777-b9570d8e764f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Kanstantsin Shautsou]

> On Dec 15, 2015, at 19:17, Surya Gaddipati  wrote:
> 
> >So what is your problem around Cloud API based provisioning?
> 
> 1. Delay in provisioning -> There is no technical reason user has to deal 
> with this.  This is totally a problem we can solve .
> 2.  Container booting logs should be available to user via build logs, since 
> allocation of container is part of the build. This is not currently possible.
>From Jenkins architecture when job is in queue it just an item and there is no 
>build objects. Probably you can copy provisioning logs into build in launcher 
>onAcceptedTasks() step. Or optionally it should be possible attach slave log 
>to build object as action and provide log from separate link (imho is good 
>enough).
> 
> Surya
> 
> On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
> This is not a hosting request. I am hoping to get some feedback on the plugin 
> and see if its worth hosting/merging into other plugins.
> 
> Details are in the readme of the project
> https://github.com/suryagaddipati/jenkins-docker-slaves 
> 
> 
> 
> Pls, let me know if you have any questions.
> 
> Surya
> 
> 
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/ruikEEsF_bc/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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/87834380-5694-41d4-bbb2-25ce55640b12%40googlegroups.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/1416E24A-E20D-4362-AF2B-F8FED50335AB%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: (another) docker slaves plugin - review request

[Surya Gaddipati]

>So what is your problem around Cloud API based provisioning?

1. Delay in provisioning -> There is no technical reason user has to deal 
with this.  This is totally a problem we can solve . 
2.  Container booting logs should be available to user via build logs, 
since allocation of container is part of the build. This is not currently 
possible. 

Surya

On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
>
> This is not a hosting request. I am hoping to get some feedback on the 
> plugin and see if its worth hosting/merging into other plugins.
>
> Details are in the readme of the project 
> https://github.com/suryagaddipati/jenkins-docker-slaves 
>
>
> Pls, let me know if you have any questions.
>
> Surya
>
>

-- 
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/87834380-5694-41d4-bbb2-25ce55640b12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin hosting request

[Sanketh P B]

Sure, I agree with you. We could enhance the existing plugin. 
@Leonardo Kobus: Please provide your inputs on how to proceed.

Thanks,
Sanketh

On Monday, December 14, 2015 at 1:32:22 PM UTC+5:30, Oleg Nenashev wrote:
>
> In general we try to avoid creation of new plugins wherever it is 
> possible. IMHO it makes sense to consider integrating the functionality 
> into a single plugin^ because they are very close. I agree that the 
> existing plugin does not cover all your case, but it could be solved by the 
> plugin extension and renaming.
>
> I've added Leonardo Kobus (maintainer of change-assembly-version-plugin) 
> to Cc.
>
> воскресенье, 13 декабря 2015 г., 16:46:14 UTC+3 пользователь Sanketh P B 
> написал:
>>
>> Dear Oleg Nenashev,
>>
>> This plugin offers support for frequently performed operations (change in 
>> product version, file version and copyright info) on .Net, managed .Net and 
>> C++ assembly information in a easy way. The other concentrates on .Net only 
>> and for updating versions. Kindly suggest your thoughts, I feel this could 
>> be separate plugins.
>>
>> Best Regards,
>> Sanketh
>>
>> On Sunday, December 13, 2015 at 2:42:07 AM UTC+5:30, Oleg Nenashev wrote:
>>>
>>> Hi Sanketh,
>>>
>>> How the plugin differs from 
>>> https://github.com/jenkinsci/change-assembly-version-plugin ?
>>> From what I see it would be better to update that plugin instead of 
>>> creating the new one
>>>
>>> Best regards,
>>> Oleg Nenashev
>>>
>>> пятница, 11 декабря 2015 г., 18:29:12 UTC+3 пользователь Sanketh P B 
>>> написал:

 Dear All,

 Any updates here? Is this pending due to any changes required?

 Thanks,
 Sanketh



-- 
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/67b4c403-e466-46d3-a279-282673a180c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Kanstantsin Shautsou]

Hi, that’s wrong info about docker-plugin. docker-plugin support:
- provisioning jenkins slaves
- building/publish images (duplicated/duplicates docker-build-publish-plugin)
- Docker container controls
All functionality is written via docker-java library layer.

> On Dec 15, 2015, at 18:59, Surya Gaddipati  wrote:
> 
> Hi Kanstantsin ,
> 
> Use case is exactly this 
> https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin
> 
> 
> 
> "The aim of the docker plugin is to be able to use a docker host to 
> dynamically provision a slave, run a single build, then tear-down that slave."
> 
> 
> 
> But without going through Jenkins Cloud Api.
> 
> 
> 
> Surya
> 
> 
> On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
> This is not a hosting request. I am hoping to get some feedback on the plugin 
> and see if its worth hosting/merging into other plugins.
> 
> Details are in the readme of the project
> https://github.com/suryagaddipati/jenkins-docker-slaves 
> 
> 
> 
> Pls, let me know if you have any questions.
> 
> Surya
> 
> 
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/ruikEEsF_bc/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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/d5035c31-39ec-4c34-94f8-457f2ed555bd%40googlegroups.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/378EE395-4CD2-471F-815D-21AD872D6A5A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: (another) docker slaves plugin - review request

[Kanstantsin Shautsou]

So what is your problem around Cloud API based provisioning? It’s jenkins Cloud 
API implementation (probably the best in FOSS plugins).
There are some issues for provisioning delay (that is not fully right described 
in ndeloof’s plugin README).

Could you definitely describe what exactly you want achieve?

> On Dec 15, 2015, at 18:59, Surya Gaddipati  wrote:
> 
> Hi Kanstantsin ,
> 
> Use case is exactly this 
> https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin
> 
> 
> 
> "The aim of the docker plugin is to be able to use a docker host to 
> dynamically provision a slave, run a single build, then tear-down that slave."
> 
> 
> 
> But without going through Jenkins Cloud Api.
> 
> 
> 
> Surya
> 
> 
> On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
> This is not a hosting request. I am hoping to get some feedback on the plugin 
> and see if its worth hosting/merging into other plugins.
> 
> Details are in the readme of the project
> https://github.com/suryagaddipati/jenkins-docker-slaves 
> 
> 
> 
> Pls, let me know if you have any questions.
> 
> Surya
> 
> 
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/ruikEEsF_bc/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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/d5035c31-39ec-4c34-94f8-457f2ed555bd%40googlegroups.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/19452734-54C7-4CC5-9C90-08CBEB05C1A8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: create-text-file plugin - New hosting reuest

[Sanketh P B]

Thanks for forking it.

I am unable to commit to 
https://github.com/jenkinsci/text-file-operations-plugin.git, could you 
please provide commit access for the same?

Error:
remote: Permission to jenkinsci/text-file-operations-plugin.git denied to 
sankethpb.
fatal: unable to access 
'https://github.com/jenkinsci/text-file-operations-plugin.git/': The 
requested URL returned error: 403

Thanks and Best Regards,
Sanketh

On Monday, December 14, 2015 at 5:40:05 AM UTC+5:30, Daniel Beck wrote:
>
> Forked into https://github.com/sankethpb/text-file-operations-plugin 
>
> I also created a component of the same name on issues.jenkins-ci.org. 
>
> Remember to set a  in the pom.xml that points to a 
> wiki.jenkins-ci.org plugin page, and to add the  element to tag your 
> releases. 
>
> On 13.12.2015, at 14:13, Sanketh P B > 
> wrote: 
>
> > Dear Team, 
> > Changed artifact id as per recommendation. 
> > 
> > GitHub url: https://github.com/sankethpb/text-file-operations-plugin.git 
> > Name of plugin: text-file-operations-plugin 
> > GitHub username and jenkins-ci.org user name: sankethpb 
> > Description: Provides a build step to create a new text file, overwrite, 
> append to end of file or insert at beginning of file. File can be saved in 
> any extension. 
> > 
> > 
> > 
> > Kindly provide the required access to host this plugin. 
> > 
> > 
> > 
> > Thanks, 
> > Sanketh 
> > 
> > On Sunday, December 13, 2015 at 2:37:50 AM UTC+5:30, Oleg Nenashev 
> wrote: 
> > Hi Sanketh, 
> > 
> > I don't see any requirements regarding the group ID. 
> > So IMHO the current approach is acceptable. 
> > 
> > BTW my recommendation would be to adjust the plugin ID. Since you 
> support not only "createFile" operations, maybe a wider 
> "text-file-operations-plugin" would be better 
> > 
> > пятница, 11 декабря 2015 г., 18:27:37 UTC+3 пользователь Sanketh P B 
> написал: 
> > Any updates here? 
> > 
> > -- 
> > 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-de...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/9f920825-45db-4be6-98f1-7c614bcfddd5%40googlegroups.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/442336d8-0236-4f46-b1bb-37ae7c1704a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Surya Gaddipati]

Hi Kanstantsin ,

Use case is exactly 
this https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin 


"The aim of the docker plugin is to be able to use a docker host to 
dynamically provision a slave, run a single build, then tear-down that 
slave." 


But without going through Jenkins Cloud Api. 


Surya

On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
>
> This is not a hosting request. I am hoping to get some feedback on the 
> plugin and see if its worth hosting/merging into other plugins.
>
> Details are in the readme of the project 
> https://github.com/suryagaddipati/jenkins-docker-slaves 
>
>
> Pls, let me know if you have any questions.
>
> Surya
>
>

-- 
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/d5035c31-39ec-4c34-94f8-457f2ed555bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Kanstantsin Shautsou]

Surya, could you describe your use case because it seems that you want two 
orthogonal features in one?

> On Dec 15, 2015, at 18:47, Surya Gaddipati  wrote:
> 
> Hi nigelm,
> 
> The important difference between this and all other docker slaves plugin is 
> that this doesn't use jenkins' cloud api for the reasons listed here 
> 
> 
> On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
> This is not a hosting request. I am hoping to get some feedback on the plugin 
> and see if its worth hosting/merging into other plugins.
> 
> Details are in the readme of the project
> https://github.com/suryagaddipati/jenkins-docker-slaves 
> 
> 
> 
> Pls, let me know if you have any questions.
> 
> Surya
> 
> 
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/ruikEEsF_bc/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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/64c4afda-60ea-4d3c-9e9a-17a9dec91ce1%40googlegroups.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/5DCF1CCA-8A6C-4E9F-9E13-158000B0FBD9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: (another) docker slaves plugin - review request

[Surya Gaddipati]

Hi Yoann,
Thank you for your response. 

>  I was wondering what was missing to rewrite a simplified version of it.

So here are couple of things that I found needed to be changed

1. changed to use spotify-docker api client instead of command line, I 
needed it to talk to docker-swarm to allocated nodes
2. Slaves are allocated based on job label not job property, much like 
cloud plugins
3. We didn't need to run builds in another image/side image ect, we use 
docker-compose to run builds. 
4. Had to remove couple of hacks like this 
,
 
since we don't store builds on disk.
5. We didn't need jenkins user mounting .

This plugin simply allocates a new slave via jnlp/docker api calls. There 
is no extra magic. 

Surya




On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
>
> This is not a hosting request. I am hoping to get some feedback on the 
> plugin and see if its worth hosting/merging into other plugins.
>
> Details are in the readme of the project 
> https://github.com/suryagaddipati/jenkins-docker-slaves 
>
>
> Pls, let me know if you have any questions.
>
> Surya
>
>

-- 
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/57db95e2-f8df-4015-9d91-3705a852aa3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Surya Gaddipati]

Hi nigelm, 

The important difference between this and all other docker slaves plugin is 
that this doesn't use jenkins' cloud api for the reasons listed here 

 

On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
>
> This is not a hosting request. I am hoping to get some feedback on the 
> plugin and see if its worth hosting/merging into other plugins.
>
> Details are in the readme of the project 
> https://github.com/suryagaddipati/jenkins-docker-slaves 
>
>
> Pls, let me know if you have any questions.
>
> Surya
>
>

-- 
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/64c4afda-60ea-4d3c-9e9a-17a9dec91ce1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Kanstantsin Shautsou]

> On Dec 15, 2015, at 18:43, Surya Gaddipati  wrote:
> 
> Hi Yoann,
> Thank you for your response.
> 
> >  I was wondering what was missing to rewrite a simplified version of it.
> 
> So here are couple of things that I found needed to be changed
> 
> 1. changed to use spotify-docker api client instead of command line, I needed 
> it to talk to docker-swarm to allocated nodes
Binary wrapping is solution that CloudBees choose for their plugins and seems 
this plugin follow it to have compatibility. Before they released first 
*docker* plugins i proposed to cooperate work on some library but they rejected 
it.
> 2. Slaves are allocated based on job label not job property, much like cloud 
> plugins
Thats feature and required to have ability to specify container from job 
(imagine that you can’t request admin to change images).
> 3. We didn't need to run builds in another image/side image ect, we use 
> docker-compose to run builds.
Ok, it just one of features.
> 4. Had to remove couple of hacks like this 
> ,
>  since we don't store builds on disk.
> 5. We didn't need jenkins user mounting .
> 
> This plugin simply allocates a new slave via jnlp/docker api calls. There is 
> no extra magic.
> 
> Surya
P.S. i’m working on having ability to share slave configuration between Cloud 
configuration and Job Properties. Also with future docker-java release it will 
be possible to run remoting with pipes (spotify doesn’t support it afaik, dunno 
why you so want enforce plugins to use it). But that will be in 
yet-another-docker-plugin.
> 
> 
> 
> 
> On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
> This is not a hosting request. I am hoping to get some feedback on the plugin 
> and see if its worth hosting/merging into other plugins.
> 
> Details are in the readme of the project
> https://github.com/suryagaddipati/jenkins-docker-slaves 
> 
> 
> 
> Pls, let me know if you have any questions.
> 
> Surya
> 
> 
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/ruikEEsF_bc/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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/57db95e2-f8df-4015-9d91-3705a852aa3d%40googlegroups.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/34912DB1-1FD6-411B-94E9-630315893DB2%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

CRX Content Package Deployer Plugin

[Dean Anderson]

Has anyone downloaded the source code, built the code and SUCCESSFULLY
deployed the code into Jenkins?

I can download the code and get it to build.  Then, I can successfully
install the plugin into Jenkins.

However, for some reason it doesn't show up as an available plugin when
I select "This build is parameterized", then click on Add Parameter.

If I download the plugin from
https://wiki.jenkins-ci.org/display/JENKINS/CRX+Content+Package+Deployer+Plugin
everything
seems to work fine and it does show up when I click "Add Parameter" as
described above.

Any thoughts or suggestions are greatly appreciated.

Thank you.

-Dean

-- 
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/CAHjWn6GFHRRZhV8xf%2BDP5fTgFo83M1On10Q1T3o3-%3DsBmqdF%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Signup for jenkins-ci.org vs the spam problem

[R. Tyler Croy]

(replies inline)

On Tue, 15 Dec 2015, chefffe wrote:

> I just tried to sign up for Jenkin's Jira, so I was forwarded to the sign 
> up page
> https://jenkins-ci.org/account/signup
> 
> I filled out the form and send it to the server, there I got the response 
> that you have an ongoing spam problem, I should post here.
> 
> > Oops!
> >
> > Due to the spam problem, we need additional verification for your sign-up 
> > request. Please contact jenkinsci-dev
> >
> 
> This is what I want to do. I should have two requests pending, both User 
> IDs would be chefffe.
> 

Looking the user up I see:

"ID chefffe is already taken. Perhaps you already have an account imported 
from
legacy java.net? You may try resetting the password."


The email on the account does match your email. I've gone ahead and sent a
password reset email, which you should receive shortly.



- R. Tyler Croy

--
 Code: 
  Chatter: 

  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
--

-- 
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/20151215152053.GG23766%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: Signup for jenkins-ci.org vs the spam problem

[Larry Shatzer, Jr.]

Created, you should have gotten an email.

-- Larry

On Tue, Dec 15, 2015 at 4:55 AM, chefffe  wrote:

> I just tried to sign up for Jenkin's Jira, so I was forwarded to the sign
> up page
> https://jenkins-ci.org/account/signup
>
> I filled out the form and send it to the server, there I got the response
> that you have an ongoing spam problem, I should post here.
>
>> Oops!
>>
>> Due to the spam problem, we need additional verification for your sign-up
>> request. Please contact jenkinsci-dev
>>
>
> This is what I want to do. I should have two requests pending, both User
> IDs would be chefffe.
>
> Thanks for your help!
>
> --
> 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/ee6d0b30-db27-4a1d-aeeb-2d2a14735973%40googlegroups.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/CAPr6TnQiQ2i5JtrX%2BigfgGFc982xdZhfc_fwac%2BtKdFYLUpu_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Nigel Magnay]

> I agree that independent Docker slave makes sense.
> IIRC such functionality is provided by one of existing Docker plugins, but
> I'm not sure. There're too many of them :(
>
> If no, I would vote for integrating the proposal into Docker-plugin if
> there is no showstoppers.
>
>
​docker-plugin already allows starting / stopping images. You may have
additional fields (e.g volumes) that it perhaps does not expose.

​I believe docker-build-step also does this.

-- 
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/CAPYP83SVBbAN6qJj5SSPAy4OSJJoxUJBMFcfBfEFFuSbbX_Urg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Best practices for integration of credentials in a plugin

[Stephen Connolly]

IMHO you should be looking by *interface* i.e. you want any credential that
implements both PasswordCredentials and StandardCredentials.

You should not be looking for a specific implementation type.

If you look for a concrete implementation class then you prevent somebody
implementing an external credential store that returns a different
implementation type

On 15 December 2015 at 14:25, Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> wrote:

> Jean-Christophe,
>
> so I would say use the Plain Credential plugin. A plain text password is
> *never* the answer.
>
> I agree that the field name can be vague, but we can discuss about it with
> Jesse or create a quick PR.
>
> -- Adrien
>
> Le mar. 15 déc. 2015 à 14:58, jcsirot  a écrit :
>
>> Hi Adrien,
>>
>> Well, there is no real issue with the Plain Credential Plugin but I find
>> that the label "secret text" used by this plugin when creating a new
>> credential entry is a little bit vague. Using a simple password field would
>> also work but I prefer using a credential item in order to avoid password
>> in plain text when the ansible plugin is used within a workflow job.
>>
>>
>> Le lundi 14 décembre 2015 16:58:02 UTC+1, Adrien Lecharpentier a écrit :
>>
>>> Jean-Christophe,
>>>
>>> I would say using the Plain Credential Plugin if you only need a
>>> "secured" field for the vault. What is the issue with it? Maybe it is
>>> possible to improvement it?
>>>
>>> Best regards.
>>>
>>> Le lun. 14 déc. 2015 à 15:13, jcsirot  a écrit :
>>>
>> Hello,

 I am working on the integration of the ansible vault feature (i.e.
 password protected configuration files) in the ansible plugin. I want to
 give the possibility to select the password from the credential plugin
 dropdown box. So I see 3 possibilities to do that :

 1. Use the SSHUserPassword from the SSH Credential plugin. The username
 is then ignored. It works but I find this solution ugly.

 2. Depend on a plugin which provides a password-only credential
 provider. For instance the Plain Credential plugin. But I think this
 provides a poor user experience.

 3. Implement a dedicated credential provider in the Ansible plugin.
 This is probably the best solution regarding the user experience but it
 duplicates some code.

 Is there any solution I missed or is there some good practices to
 follow here.

 Thanks in advance for your feedback.

 --
 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-de...@googlegroups.com.
>>>
>>>
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/524089f5-4005-4720-af20-9c7b0580e61f%40googlegroups.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/023fe378-f4fb-4e8c-b70a-f6870b971b10%40googlegroups.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/CAKwJSvydr3-W2fWuNu%2BPGmMVfO6TvTkBWeruuE09MzBTG7PsTQ%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/CA%2BnPnMz84M%3DxapKL%2BnPTV3xG7kZ3UPSiv_RbtTqUrGV8B4GZmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Best practices for integration of credentials in a plugin

[Adrien Lecharpentier]

Jean-Christophe,

so I would say use the Plain Credential plugin. A plain text password is
*never* the answer.

I agree that the field name can be vague, but we can discuss about it with
Jesse or create a quick PR.

-- Adrien

Le mar. 15 déc. 2015 à 14:58, jcsirot  a écrit :

> Hi Adrien,
>
> Well, there is no real issue with the Plain Credential Plugin but I find
> that the label "secret text" used by this plugin when creating a new
> credential entry is a little bit vague. Using a simple password field would
> also work but I prefer using a credential item in order to avoid password
> in plain text when the ansible plugin is used within a workflow job.
>
>
> Le lundi 14 décembre 2015 16:58:02 UTC+1, Adrien Lecharpentier a écrit :
>
>> Jean-Christophe,
>>
>> I would say using the Plain Credential Plugin if you only need a
>> "secured" field for the vault. What is the issue with it? Maybe it is
>> possible to improvement it?
>>
>> Best regards.
>>
>> Le lun. 14 déc. 2015 à 15:13, jcsirot  a écrit :
>>
> Hello,
>>>
>>> I am working on the integration of the ansible vault feature (i.e.
>>> password protected configuration files) in the ansible plugin. I want to
>>> give the possibility to select the password from the credential plugin
>>> dropdown box. So I see 3 possibilities to do that :
>>>
>>> 1. Use the SSHUserPassword from the SSH Credential plugin. The username
>>> is then ignored. It works but I find this solution ugly.
>>>
>>> 2. Depend on a plugin which provides a password-only credential
>>> provider. For instance the Plain Credential plugin. But I think this
>>> provides a poor user experience.
>>>
>>> 3. Implement a dedicated credential provider in the Ansible plugin. This
>>> is probably the best solution regarding the user experience but it
>>> duplicates some code.
>>>
>>> Is there any solution I missed or is there some good practices to follow
>>> here.
>>>
>>> Thanks in advance for your feedback.
>>>
>>> --
>>> 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-de...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/524089f5-4005-4720-af20-9c7b0580e61f%40googlegroups.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/023fe378-f4fb-4e8c-b70a-f6870b971b10%40googlegroups.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/CAKwJSvydr3-W2fWuNu%2BPGmMVfO6TvTkBWeruuE09MzBTG7PsTQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

['Yoann Dubreuil' via Jenkins Developers]

Hi Surya,

As one of the author of https://github.com/ndeloof/docker-slaves-plugin , I
was wondering what was missing to rewrite a simplified version of it.

Maybe we could work together to improve this plugin instead?

Yoann.


On Tue, Dec 15, 2015 at 2:29 PM, Kanstantsin Shautsou <
kanstantsin@gmail.com> wrote:

> Yes, i'm working on such thing in my new plugin, will notify when will
> have something working.
>
> On Monday, December 14, 2015 at 6:41:26 PM UTC+3, Surya Gaddipati wrote:
>>
>> Hi Oleg,
>> Thank you for your feedback.
>>
>> Looks like DockerPlugin uses Jenkins clound api ( link
>> 
>> )
>>
>> This plugin uses QueueListener to provision slaves .
>>
>> Can these two approaches be integrated together ?
>>
>> Surya
>>
>> On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
>>>
>>> This is not a hosting request. I am hoping to get some feedback on the
>>> plugin and see if its worth hosting/merging into other plugins.
>>>
>>> Details are in the readme of the project
>>> https://github.com/suryagaddipati/jenkins-docker-slaves
>>>
>>>
>>> Pls, let me know if you have any questions.
>>>
>>> Surya
>>>
>>> --
> 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/fb9c00be-ad78-48c6-955b-7485e44d20c7%40googlegroups.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/CAFWoUpTg%3D_Eyg0YNgGT%3DqPS%2BLXY9p9Dhp1xizHtQJ5FD1GjG-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Best practices for integration of credentials in a plugin

[jcsirot]

Hi Adrien,

Well, there is no real issue with the Plain Credential Plugin but I find 
that the label "secret text" used by this plugin when creating a new 
credential entry is a little bit vague. Using a simple password field would 
also work but I prefer using a credential item in order to avoid password 
in plain text when the ansible plugin is used within a workflow job.

Le lundi 14 décembre 2015 16:58:02 UTC+1, Adrien Lecharpentier a écrit :
>
> Jean-Christophe,
>
> I would say using the Plain Credential Plugin if you only need a "secured" 
> field for the vault. What is the issue with it? Maybe it is possible to 
> improvement it?
>
> Best regards.
>
> Le lun. 14 déc. 2015 à 15:13, jcsirot > a 
> écrit :
>
>> Hello,
>>
>> I am working on the integration of the ansible vault feature (i.e. 
>> password protected configuration files) in the ansible plugin. I want to 
>> give the possibility to select the password from the credential plugin 
>> dropdown box. So I see 3 possibilities to do that :
>>
>> 1. Use the SSHUserPassword from the SSH Credential plugin. The username 
>> is then ignored. It works but I find this solution ugly.
>>
>> 2. Depend on a plugin which provides a password-only credential provider. 
>> For instance the Plain Credential plugin. But I think this provides a poor 
>> user experience.
>>
>> 3. Implement a dedicated credential provider in the Ansible plugin. This 
>> is probably the best solution regarding the user experience but it 
>> duplicates some code.
>>
>> Is there any solution I missed or is there some good practices to follow 
>> here.
>>
>> Thanks in advance for your feedback.
>>
>> -- 
>> 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-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/524089f5-4005-4720-af20-9c7b0580e61f%40googlegroups.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/023fe378-f4fb-4e8c-b70a-f6870b971b10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: (another) docker slaves plugin - review request

[Kanstantsin Shautsou]

Yes, i'm working on such thing in my new plugin, will notify when will have 
something working.

On Monday, December 14, 2015 at 6:41:26 PM UTC+3, Surya Gaddipati wrote:
>
> Hi Oleg, 
> Thank you for your feedback. 
>
> Looks like DockerPlugin uses Jenkins clound api ( link 
> 
> )
>
> This plugin uses QueueListener to provision slaves . 
>
> Can these two approaches be integrated together ?
>
> Surya
>
> On Sunday, December 13, 2015 at 12:53:44 PM UTC-6, Surya Gaddipati wrote:
>>
>> This is not a hosting request. I am hoping to get some feedback on the 
>> plugin and see if its worth hosting/merging into other plugins.
>>
>> Details are in the readme of the project 
>> https://github.com/suryagaddipati/jenkins-docker-slaves 
>>
>>
>> Pls, let me know if you have any questions.
>>
>> Surya
>>
>>

-- 
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/fb9c00be-ad78-48c6-955b-7485e44d20c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Signup for jenkins-ci.org vs the spam problem

[chefffe]

I just tried to sign up for Jenkin's Jira, so I was forwarded to the sign 
up page
https://jenkins-ci.org/account/signup

I filled out the form and send it to the server, there I got the response 
that you have an ongoing spam problem, I should post here.

> Oops!
>
> Due to the spam problem, we need additional verification for your sign-up 
> request. Please contact jenkinsci-dev
>

This is what I want to do. I should have two requests pending, both User 
IDs would be chefffe.

Thanks for your help!

-- 
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/ee6d0b30-db27-4a1d-aeeb-2d2a14735973%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: automatic behavior after job fails on a node

['Robert Sandell' via Jenkins Developers]

There is a todo in the Build Failure Analyser plugin to add steps to take
in case a specific failure cause is found. But we never got around to
implementing it.
If you are interested you're welcome to taking a crack at it.

https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer

/B

On Mon, Dec 14, 2015 at 7:17 PM, oliver gondža  wrote:

> https://wiki.jenkins-ci.org/display/JENKINS/Adaptive+disconnector+plugin
> is here to prevent some of that putting slave temporarily offline in case
> some of the monitors is triggered. Most notably full workspace, temp dir.
>
> If you implement your check as Jenkins monitor, it will integrate nicely.
>
> --
> 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/op.x9nbrwrssbfict%40localhost.localdomain
> .
>
> 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/CALzHZS3%3Dzx3FKOe9sN6nsSQbDewB04coGAn6XqB2xYD1oq7g%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.