Re: What compression algorithm is used by the pipeline zip step, and is it tunable?

2019-12-04 Thread Tim Black
Thanks Björn. We're currently on a single master, and I definitely will 
take performance into consideration when we scale. We're looking into 
installing and ind integrating with Artifactory in the coming months, which 
should help with managing artifacts, but I suspect there will still be the 
issue of "who does the compression"..

Many of our artifacts are already compressed entities, but I have confirmed 
that zipping everything (using Jenkins zip) shrinks them by more than half, 
so I'm definitely on the right track..

On Monday, December 2, 2019 at 11:09:19 PM UTC-8, Björn Pedersen wrote:
>
> Hi,
>
> I would probably try to compress on the agent before even trying to 
> transfer the large data to the master. This avoids load on the master a) 
> due to transfer and b) due to compression.
> And if the artifacts get really huge, consider storing them  independent 
> from jenkins (S3, maven-style repo, whatever matches your use-case).
>
>
> Björn
>
> Am Montag, 2. Dezember 2019 20:56:02 UTC+1 schrieb Tim Black:
>>
>> Our projects produce large artifacts that now need to be compressed, and 
>> I'm considering my alternatives. The zip step 
>> 
>>  
>> would be a nice non-plugin solution but I'm curious what compression 
>> technique this uses. The documentation page linked above doesn't show any 
>> options that pertain to compression tuning.
>>
>> I've also seen the Compress Artifacts Plugin 
>> , but I can't 
>> tell from its docs either whether the algo is tunable. Also I'd rather not 
>> depend on another plugin.
>>
>> If neither of the above work, I'll simply use sh step to call xz, gzip, 
>> bzip, or the like, from my linux-based master.
>>
>> Thanks for your consideration,
>> Tim Black
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/64c5c8bf-f5fe-4c2c-b4a8-e048928edf62%40googlegroups.com.


Re: How to add SSH public key to local user ?

2019-12-04 Thread Ivan Fernandez Calvo
Could you give more details of your use case? When you said `local user` it 
is local to master or agent? also it depends what would be the use that you 
make of the key (git, ssh, ...)

El martes, 3 de diciembre de 2019, 18:15:14 (UTC), Dropveter escribió:
>
> Hi,
>
> My current quest is to figure out how to add an SSH public key to a local 
> user.
> After searching multiple sources on the internet, I still have not been 
> able to find any helpful information on this.
>
> My preferred method would be using the 'Configuration-as-Code' plugin, but 
> I am happily willing to settle for a Groovy script.
>
> Help is greatly appreciated!
>
> Mark
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2b1f56c9-262b-4c8b-b62d-467c5242a9d4%40googlegroups.com.


ENV via entrypoint in Docker images on Kubernetes cloud

2019-12-04 Thread Steffen Seckler
Hi,

I am setting some environment variables via the entrypoint of a dockerfile. 
These variables can be set at earliest during the startup of the container, 
as they include the cpuid.

I have confirmed that the entrypoint is executed at the startup of the 
container, however, inside of the `sh` commands (of the container() steps) 
the environment variables are no longer visible.

My current workaround is using sth. like:

sh 'entrypoint.sh ccache -s'


which then sets the correct env. Does anyone know, what a proper way of 
using such environment variables would be using Jenkins (+Kubernetes) 
plugin?

Or as another question, how exactly are these 'sh' commands executed on the 
container, i.e., how does the jnlp container execute the sh commands on the 
build environment containers? 


Thanks for the help!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0e1eea53-24ba-437e-ba8f-bf4940721834%40googlegroups.com.


Re: How to identify the compatibility plugins?

2019-12-04 Thread 'Björn Pedersen' via Jenkins Users
You should check 
https://jenkins.io/blog/2019/05/30/becoming-contributor-newbie-tickets/ and 
https://github.com/jenkinsci/jenkins/pull/3985:

return isCompatibleWithInstalledVersion() && !isForNewerHudson() && 
!isForNewerJava() 
&& 
isNeededDependenciesCompatibleWithInstalledVersion(cache) && 
!isNeededDependenciesForNewerJenkins(cache) && !
isNeededDependenciesForNewerJava(); 

is the main code used.


Am Dienstag, 3. Dezember 2019 12:16:10 UTC+1 schrieb YanJun Shi:
>
> But I see the function name is ` checkPluginsWithoutWarnings  ` for 
> compatible. 
>
> On Tue, Dec 3, 2019 at 3:05 PM 'Björn Pedersen' via Jenkins Users <
> jenkins...@googlegroups.com > wrote:
>
>> Hi,
>>
>> Am Dienstag, 3. Dezember 2019 08:00:10 UTC+1 schrieb YanJun Shi:
>>>
>>> Hi, everybody
>>> 
>>>   When I use Jenkins, I find that the effect of selecting 'all' and 
>>> 'compatibility' in 'plugins manager' is the same, I want to know how to 
>>> distinguish between compatible plugins. HI
>>>
>>
>> In most cases this expected. Only for very ancient, unmaintained plugins  
>> or if using a rather old jenkins you may find a incompatibility. 
>> Case 1: plugin depends on an now removed other plugin 
>> Case 2: the plugin requires a newer jenkins core than you are using
>>
>> So if you keep everythign up-to-date, almost any current plugin should be 
>> compatible.
>>
>> Björn
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkins...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/61b3457a-8dc0-4f1f-9fb0-fa050b923d40%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Shi Yanjun(yJunS)
> Blog:https://github.com/yJunS
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4b2ef536-5a57-464c-9024-b49000936e3e%40googlegroups.com.