custom image for jnlp( amazonlinux)

[Yaramada Surya tej]

Hi, I am trying to use custom image which is based on amazonlinux and 
pushed to ECR for running jenkins executors on AWS EKS. able to use 
default image ( alpine) but need help to configure in settings for using a 
custom image.

To achieve this do we need 2 custom images? one for pod and another for 
container image?


-- 
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/e1d5e4c4-c6d0-4bb8-ac87-0377f6f1be46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

calling another job from parent job

[Akshay Paturkar]

Hi All,
i am trying to call job from another job and able to do it by following 
below instructions .
https://jenkins.io/doc/pipeline/steps/pipeline-build-step/

But I am not able to see stages executed under called job.
how do we enable stages of called job to be displayed under build job stage 
?

-- 
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/d86805e3-8792-41e8-895a-d77c2e7fec40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to handle complex job dependency?

[Matt Hicks]

It doesn't have pipeline support, but the promoted builds plugin 
 can do 
this for freestyle jobs.

-- 
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/77c4c793-dbfb-4d00-b4db-a5b7c39d319f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Job Failed with "java.lang.OutOfMemoryError: unable to create new native thread" On Kuberentes cluster..

[pbasanta2002]

On Sunday, November 11, 2018 at 2:42:43 PM UTC+5:30, pbasan...@gmail.com 
wrote:
>
> Hi All,
>
> While running a job on Kuberentes Cluster 
>
> [EnvInject] - Loading node environment variables.
> Building remotely on k8s-prod-cl1-pod1-v1v5j 
> 
>  (K8S_PROD_Cl1_lab1) in workspace 
> /workspace/LayerManifestBuilder*java.lang.OutOfMemoryError: unable to create 
> new native thread*
>   at java.lang.Thread.start0(Native Method)
>   at java.lang.Thread.start(Thread.java:717)
>   at 
> hudson.remoting.AtmostOneThreadExecutor.execute(AtmostOneThreadExecutor.java:96)
>
> Caused: java.io.IOException: Remote call on JNLP4-connect connection from 
> slc13qka.us.oracle.com/10.247.120.202:35679 failed
>   at hudson.remoting.Channel.call(Channel.java:913)
>   at hudson.FilePath.act(FilePath.java:987)
> Caused: java.io.IOException: remote file operation failed: 
> /scratch/syseng/workspace/LayerManifestBuilder at 
> hudson.remoting.Channel@12301016:JNLP4-connect connection from 
> slc13qka.us.oracle.com/10.247.120.202:35679
>
>
> Need to find the reason for the failure.
>
>
>
>
> Regards,
>
> Basanta
>
>
>

-- 
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/7e469ceb-5a0a-4bbc-8c7c-13f1280a4465%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Job Failed with "java.lang.OutOfMemoryError: unable to create new native thread" On Kuberentes cluster..

[pbasanta2002]

The same job on rerun after some time passed on the same salve node.. 

On Monday, November 12, 2018 at 11:04:24 AM UTC+5:30, pbasan...@gmail.com 
wrote:
>
> Hi ,
> Thanks for your response.
>
> on Ulimit -aH , I can see one difference on container and host 
>
> Container :
> *open files  (-n) 65536*
>
> Slave Host :
> *open files  (-n) 327679*
>
>
> Will that Causeing the OOM Failure .
> Regards,
> Basanta
> On Monday, November 12, 2018 at 2:32:45 AM UTC+5:30, Jan Monterrubio wrote:
>>
>> Cn you check the ulimit for your pod? 
>>
>> https://plumbr.io/outofmemoryerror/unable-to-create-new-native-thread
>>
>>
>> On Sun, Nov 11, 2018 at 03:12  wrote:
>>
>>> Hi All,
>>>
>>> While running a job on Kuberentes Cluster 
>>>
>>> [EnvInject] - Loading node environment variables.
>>> Building remotely on k8s-prod-cl1-pod1-v1v5j 
>>> 
>>>  (K8S_PROD_Cl1_lab1) in workspace 
>>> /workspace/LayerManifestBuilder*java.lang.OutOfMemoryError: unable to 
>>> create new native thread*
>>> at java.lang.Thread.start0(Native Method)
>>> at java.lang.Thread.start(Thread.java:717)
>>> at 
>>> hudson.remoting.AtmostOneThreadExecutor.execute(AtmostOneThreadExecutor.java:96)
>>>
>>> Caused: java.io.IOException: Remote call on JNLP4-connect connection from 
>>> slc13qka.us.oracle.com/10.247.120.202:35679 failed
>>> at hudson.remoting.Channel.call(Channel.java:913)
>>> at hudson.FilePath.act(FilePath.java:987)
>>> Caused: java.io.IOException: remote file operation failed: 
>>> /scratch/syseng/workspace/LayerManifestBuilder at 
>>> hudson.remoting.Channel@12301016:JNLP4-connect connection from 
>>> slc13qka.us.oracle.com/10.247.120.202:35679
>>>
>>>
>>> Need to find the reason for the failure.
>>>
>>>
>>>
>>>
>>> Regards,
>>>
>>> Basanta
>>>
>>>
>>> -- 
>>> 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-use...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/8f49b9a0-af12-475f-8ae6-afb0436c927d%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 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/a50d0643-ca2e-43e4-9bdf-7267d83bd7db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to handle complex job dependency?

[ZillaYT]

Thanks Martin. I will explore tagging my docker images as we deploy them. 
So if I deploy dockerUrl/atrifact:1.0.0 to sandbox, I'll give it a 
dockerUrl/artifact:1.0.0-sandboxed tag. My deploy-to-staging job will then 
have to "look" for the "sandboxed" part in the tag.

Chris

On Monday, November 12, 2018 at 6:14:52 PM UTC-5, Martin d'Anjou wrote:
>
> I think you could use the Copy Artifacts 
>  plugin to 
> share a file between jobs. But managing the list of releases in a file 
> becomes hairy IMO. I do not know your specific case, but I guess it will 
> grow over time, not to millions of records, but possibly to hundreds or 
> maybe thousands. There is also the question of rollbacks in case of 
> uncontrollable mistakes (how to erase an entry from the list).
>
> You could use a shared workspace for the purpose of storing that file, 
> using the external workspace manager plugin 
> 
> .
>
> I would consider an external database of some kind and the httpRequest 
>  plugin to access it.
>
> If you push your releases to a binary repository, there could be a way to 
> store that info there too.
>
> Martin
>
> On Monday, November 12, 2018 at 9:00:36 AM UTC-5, ZillaYT wrote:
>>
>> Thanks Martin, though you just reworded my post.
>>
>> But yes one approach to consider is being able to store which, for 
>> example, versions have been run by deploy-to-sandox. IOW if 
>> deploy-to-sandbox has run with versions 1.0.0 and 1.0.4, I want to store 
>> those versions in its property file, say sandboxed_versons.properties. How 
>> will I then tell deploy-to-staging to read 
>> /.../deploy-to-sandbox/sandboxed.properties file?
>>
>> Chris
>>
>> On Saturday, November 10, 2018 at 9:35:12 PM UTC-5, Martin d'Anjou wrote:
>>>
>>> I do not know of an automated way of doing that.
>>>
>>> If I understand correctly, the release number is assigned by the 
>>> build-and-test phase, and it published the docker repo.
>>> I assume that this release number is known one way or another by the 
>>> users, since it has been published to the docker repo.
>>> This release number is an input to the other jobs. So I suggest you make 
>>> the release number an input parameter to the other jobs.
>>>
>>> When each job runs, it needs to check that the released artifact has 
>>> reached the expected "quality" level for the job. If not the jobs would 
>>> fail with some meaningful error message.
>>> The quality levels would be 1) built and tested, 2) sandbox, 3) staging, 
>>> and 4) production.
>>> In other words, deploy-to-sandbox(1.0.11) needs to check that the 
>>> artifacts 1.0.11 exists in the docker repo before it attempts to deploy to 
>>> sandbox.
>>> You also need to store the quality level somewhere persistent, maybe as 
>>> a property of the artifacts in the docker repo (if that is possible?).
>>> Artifactory supports properties, or maybe you need a database.
>>>
>>> Hope this helps at least from a conceptual point of view.
>>>
>>> Martin
>>>
>>

-- 
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/57be66d4-ad61-4e7a-b3b7-237883e83b87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Issue with spaces in string parameter

[Martin d'Anjou]

I doubt that would fix it, I was curious and try it. Jenkins trims, but it 
does not split the value on spaces.

The problem might be on how you pass the value to your python script. Can 
you share that?

Martin

On Monday, November 12, 2018 at 8:15:55 AM UTC-5, Danny Jacob wrote:
>
> Uncheck ‘trim string’ checkbox in advanced and try. It should work
>
> On Mon, 12 Nov 2018 at 3:56 PM, Raunak Kumar Gupta  > wrote:
>
>> I have a string parameter in jenkins called 'Keywords'. I set the value 
>> of Keywords = "Google,Microsoft,Uber Go". But jenkins string parameter 
>> takes only till "Google,Microsoft,Uber" and truncates "Go" automatically.
>>
>> Due to this my code runs incorrectly. Can anyone help in handling this 
>> auto-truncate issue in jenkins string parameter?
>>
>> This string parameter is used in my python code where I split the 
>> Keywords on comma(,) and use the 3 generated words for operation in my 
>> code. But jenkins is truncating "Go" automatically due to which incorrect 
>> word is processed by my code
>>
>> -- 
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/0b6b1e2b-3af2-4aa0-a485-573d2c03ec3f%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> *Best Regards,*
> *Jacob Dany*
> *contact - +65 90224437*
>
>

-- 
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/acbf5ab9-6595-4a5f-b058-d7b4c0240fbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to handle complex job dependency?

[Martin d'Anjou]

I think you could use the Copy Artifacts 
 plugin to 
share a file between jobs. But managing the list of releases in a file 
becomes hairy IMO. I do not know your specific case, but I guess it will 
grow over time, not to millions of records, but possibly to hundreds or 
maybe thousands. There is also the question of rollbacks in case of 
uncontrollable mistakes (how to erase an entry from the list).

You could use a shared workspace for the purpose of storing that file, 
using the external workspace manager plugin 

.

I would consider an external database of some kind and the httpRequest 
 plugin to access it.

If you push your releases to a binary repository, there could be a way to 
store that info there too.

Martin

On Monday, November 12, 2018 at 9:00:36 AM UTC-5, ZillaYT wrote:
>
> Thanks Martin, though you just reworded my post.
>
> But yes one approach to consider is being able to store which, for 
> example, versions have been run by deploy-to-sandox. IOW if 
> deploy-to-sandbox has run with versions 1.0.0 and 1.0.4, I want to store 
> those versions in its property file, say sandboxed_versons.properties. How 
> will I then tell deploy-to-staging to read 
> /.../deploy-to-sandbox/sandboxed.properties file?
>
> Chris
>
> On Saturday, November 10, 2018 at 9:35:12 PM UTC-5, Martin d'Anjou wrote:
>>
>> I do not know of an automated way of doing that.
>>
>> If I understand correctly, the release number is assigned by the 
>> build-and-test phase, and it published the docker repo.
>> I assume that this release number is known one way or another by the 
>> users, since it has been published to the docker repo.
>> This release number is an input to the other jobs. So I suggest you make 
>> the release number an input parameter to the other jobs.
>>
>> When each job runs, it needs to check that the released artifact has 
>> reached the expected "quality" level for the job. If not the jobs would 
>> fail with some meaningful error message.
>> The quality levels would be 1) built and tested, 2) sandbox, 3) staging, 
>> and 4) production.
>> In other words, deploy-to-sandbox(1.0.11) needs to check that the 
>> artifacts 1.0.11 exists in the docker repo before it attempts to deploy to 
>> sandbox.
>> You also need to store the quality level somewhere persistent, maybe as a 
>> property of the artifacts in the docker repo (if that is possible?).
>> Artifactory supports properties, or maybe you need a database.
>>
>> Hope this helps at least from a conceptual point of view.
>>
>> Martin
>>
>

-- 
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/5be21533-a062-4e5e-b7ad-002311a9eb31%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

SSLError

[gotviseryon]

Need urgent help.  Trying to run a job in Windows Slave and getting this 
error.  Please help.  Will post more information if needed.  Installed the 
certificate in the VM.  It's Windows Server 2016 Datacenter.


ERROR: HTTPSConnectionPool(host='URL', port=443): Max retries exceeded with 
url: /api/zipdeploy?isAsync=true (Caused by SSLError(SSLError("bad handshake: 
Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify 
failed')],)",),))
Traceback (most recent call last):
  File "C:\Program Files (x86)\Microsoft 
SDKs\Azure\CLI2\Lib\site-packages\urllib3\contrib\pyopenssl.py", line 444, in 
wrap_socket
cnx.do_handshake()
  File "C:\Program Files (x86)\Microsoft 
SDKs\Azure\CLI2\Lib\site-packages\OpenSSL\SSL.py", line 1907, in do_handshake
self._raise_ssl_error(self._ssl, result)
  File "C:\Program Files (x86)\Microsoft 
SDKs\Azure\CLI2\Lib\site-packages\OpenSSL\SSL.py", line 1639, in 
_raise_ssl_error
_raise_current_error()
  File "C:\Program Files (x86)\Microsoft 
SDKs\Azure\CLI2\Lib\site-packages\OpenSSL\_util.py", line 54, in 
exception_from_error_queue
raise exception_type(errors)
OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 
'certificate verify failed')]



-- 
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/0edc36a8-65bf-4d11-901b-118fb8ef7ede%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: Identify different Jenkins instances

[Sverre Moe]

Perhaps the best way is to define a global environment variable with 
different values for each Jenkins instance

Manage Settings > Configure System
Global properties
Environment variables

https://build-ci.company.com;8443/
JENKINS_ENVIRONMENT > PRODUCTION

https://build-ci-test.company.com;8443/
JENKINS_ENVIRONMENT > TEST

Which can be read in scripted pipeline as
env.JENKINS_ENVIRONMENT


mandag 12. november 2018 15.43.20 UTC+1 skrev Sverre Moe følgende:
>
>
> We have copied our Jenkins instance to have an identical test Jenkins.
>
> Is there a *proper* way to distinguish between production Jenkins and 
> test Jenkins within a Scripted Pipeline?
>
> We need different behaviour for some parts of our builds, like publishing 
> Yum artifacts, git tagging releases.
> This we need to check if the running Jenkins instance is either production 
> or test.
>
> I know we can check the environment variable JENKINS_URL, but that is not 
> a good solution.
> It would require us to have the both URLs defined in our shared pipeline 
> scripts.
> def environments [:] 
> environments["PRODUCTION"] = "https://build-ci.company.com:8443";
> environments["TEST"] = "https://build-ci-test.company.com:8443";
>
>

-- 
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/ea6b61d2-4ae4-4946-86de-c1a51c081697%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline: Identify different Jenkins instances

[Sverre Moe]

We have copied our Jenkins instance to have an identical test Jenkins.

Is there a *proper* way to distinguish between production Jenkins and test 
Jenkins within a Scripted Pipeline?

We need different behaviour for some parts of our builds, like publishing 
Yum artifacts, git tagging releases.
This we need to check if the running Jenkins instance is either production 
or test.

I know we can check the environment variable JENKINS_URL, but that is not a 
good solution.
It would require us to have the both URLs defined in our shared pipeline 
scripts.
def environments [:] 
environments["PRODUCTION"] = "https://build-ci.company.com:8443";
environments["TEST"] = "https://build-ci-test.company.com:8443";

-- 
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/20c2cb4a-8473-47dc-aa40-e513df77d589%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cleanup workspace before/after build

[Sverre Moe]

Hi,

Sorry, I completely forgot to respond.

I'm not sure if there is an existing reported JIRA bug for this.
https://issues.jenkins-ci.org/browse/JENKINS-15331
Not sure when this fix was release. It does seems like we are running with 
it according to the exception it throws. I recall getting a different 
exception previosuly before I added the try-catch surrounding the deleteDir.

My scripted pipeline
node(nodeName) {
unstash 'archive'
sh "tar -zxf ${projectName}.tar.gz"

try {
tool name: 'gradle-4.8', type: 'gradle'
sh "gradle ${javaOptions} --refresh-dependencies ${buildTask} 
${releaseProperty} -Pheadless"

stash allowEmpty: true, includes: "build/**/*.rpm", name: stashName

/* Archive Linux FPM packages */
archiveArtifacts allowEmptyArchive: true, artifacts: 
"build/**/*.rpm", onlyIfSuccessful: true

/* Archive Windows native executables. */
archiveArtifacts allowEmptyArchive: true, artifacts: 
"build/**/*.exe", excludes: "build/**/${projectName}/*.exe", 
onlyIfSuccessful: true
} catch (e) {
throw e
} finally {
try {
deleteDir()
} catch (e) {
println e
}
}
}


I had to wrap the deleteDir within a try-catch, because otherwise it would 
sometimes fail the build.
The downside is with this I sometimes get a workspace with pre-existing 
build artifacts.

java.io.IOException: Unable to delete 
'C:\cygwin64\home\build\jenkins\workspace\application_sverre_work-3U54DPE57F6TMOZM2O6QBWDQ2LNRU2QHAXT6INC3UPGWF2ERMXAQ\build\deploy\package\windows\application.iss'.
 
Tried 3 times (of a maximum of 3) waiting 0,1 sec between attempts.


torsdag 11. oktober 2018 10.02.54 UTC+2 skrev Baptiste Mathus følgende:
>
> What is the JIRA number number for the Windows deleteDir() bug you say 
> you're seeing? 
>
> Le jeu. 11 oct. 2018 à 09:33, Sverre Moe > 
> a écrit :
>
>> This deleteDir() does not always work on a Windows build slave.
>>
>> Using Scripted PIpeline I am declaring a node within try-catch-finally.
>> The finally will run deleteDir(), in order to delete the build workspace. 
>> This is done in order to get a fresh build each time. I cannot risk having 
>> stale data lying around from a previous builds.
>>
>> Is there some other means I can make sure that the build has a clean 
>> workspace?
>>
>> 1) Always build with clean
>> mvn clean deploy
>> gradle clean build publish
>>
>> 2) SCM configuration
>> *Clean after checkout*
>> *Clean before checkout*
>>
>> *3) Windows working deleteDir()*
>>
>> -- 
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/966a8838-f95a-4c23-ac61-e4c7356fac8d%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 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/60b50a51-2b75-4e4e-82bb-32d9f1dc99e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to handle complex job dependency?

[ZillaYT]

Thanks Martin, though you just reworded my post.

But yes one approach to consider is being able to store which, for example, 
versions have been run by deploy-to-sandox. IOW if deploy-to-sandbox has 
run with versions 1.0.0 and 1.0.4, I want to store those versions in its 
property file, say sandboxed_versons.properties. How will I then tell 
deploy-to-staging to read /.../deploy-to-sandbox/sandboxed.properties file?

Chris

On Saturday, November 10, 2018 at 9:35:12 PM UTC-5, Martin d'Anjou wrote:
>
> I do not know of an automated way of doing that.
>
> If I understand correctly, the release number is assigned by the 
> build-and-test phase, and it published the docker repo.
> I assume that this release number is known one way or another by the 
> users, since it has been published to the docker repo.
> This release number is an input to the other jobs. So I suggest you make 
> the release number an input parameter to the other jobs.
>
> When each job runs, it needs to check that the released artifact has 
> reached the expected "quality" level for the job. If not the jobs would 
> fail with some meaningful error message.
> The quality levels would be 1) built and tested, 2) sandbox, 3) staging, 
> and 4) production.
> In other words, deploy-to-sandbox(1.0.11) needs to check that the 
> artifacts 1.0.11 exists in the docker repo before it attempts to deploy to 
> sandbox.
> You also need to store the quality level somewhere persistent, maybe as a 
> property of the artifacts in the docker repo (if that is possible?).
> Artifactory supports properties, or maybe you need a database.
>
> Hope this helps at least from a conceptual point of view.
>
> Martin
>

-- 
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/74f83fca-f847-49d7-bbc5-a157feaa10cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Issue with spaces in string parameter

[Danny Jacob]

Uncheck ‘trim string’ checkbox in advanced and try. It should work

On Mon, 12 Nov 2018 at 3:56 PM, Raunak Kumar Gupta 
wrote:

> I have a string parameter in jenkins called 'Keywords'. I set the value of
> Keywords = "Google,Microsoft,Uber Go". But jenkins string parameter takes
> only till "Google,Microsoft,Uber" and truncates "Go" automatically.
>
> Due to this my code runs incorrectly. Can anyone help in handling this
> auto-truncate issue in jenkins string parameter?
>
> This string parameter is used in my python code where I split the Keywords
> on comma(,) and use the 3 generated words for operation in my code. But
> jenkins is truncating "Go" automatically due to which incorrect word is
> processed by my code
>
> --
> 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/0b6b1e2b-3af2-4aa0-a485-573d2c03ec3f%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
*Best Regards,*
*Jacob Dany*
*contact - +65 90224437*

-- 
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/CAD%2BZqMnKHt4_Kc%2BFd4t2Z%3DdceZxMFgCxs8%2BngA9V62BkitG_5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins dashboard report with customization

[trupti bhatt]

Thanks Rajendra.

I have tried following code: but throwing me compilation error:

Jenkins.instance.getAllItems(Job.class).each{ 
>   println it.name + " - " + it.class
>
>  def jobBuilds=it.getBuilds()
> //for each of such jobs we can get all the builds (or you can limit the 
> number at your convenience)
> jobBuilds.each { build ->
>   def runningSince = groovy.time.TimeCategory.minus( new Date(), 
> build.getTime() )
>   def currentStatus = build.buildStatusSummary.message
>  def cause = build.getCauses()[0]
>
>  println "Build: ${build} | Since: ${runningSince} | Status: 
> ${currentStatus} | Cause: ${cause}" 
>  // You can get all the information available for build parameters.
>   def parameters = build.getAction(ParametersAction)?.parameters
>   parameters.each {
> println "Type: ${it.class} Name: ${it.name}, Value: ${it.dump()}" 
> }
> }
>   }



Error Is :

> ERROR: Build step failed with exception
> groovy.lang.MissingPropertyException: No such property: Jenkins for class: 
> Script1
> at 
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53)
> at 
> org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:52)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:307)
> at Script1.run(Script1.groovy:1)
> at groovy.lang.GroovyShell.evaluate(GroovyShell.java:585)
> at groovy.lang.GroovyShell.evaluate(GroovyShell.java:623)
> at groovy.lang.GroovyShell.evaluate(GroovyShell.java:594)
> at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:343)
> at hudson.plugins.groovy.SystemGroovy.run(SystemGroovy.java:95)
> at hudson.plugins.groovy.SystemGroovy.perform(SystemGroovy.java:59)
> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
> at hudson.model.Build$BuildExecution.build(Build.java:206)
> at hudson.model.Build$BuildExecution.doRun(Build.java:163)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
> at hudson.model.Run.execute(Run.java:1815)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at hudson.model.ResourceController.execute(ResourceController.java:97)
> at hudson.model.Executor.run(Executor.java:429)
> Build step 'Execute system Groovy script' marked build as failure


On Thursday, November 8, 2018 at 3:49:14 PM UTC+5:30, rajendraprasad reddy 
wrote:
>
> Hi Tripti,
> You are correct there is no  plugin that can help you to create a custom 
> dashboard specified by you.
>
> All you need to write a groovy script to  access Jenkins job history and 
> prepare  report according to your need
>
>
> First get list of jobs via groovy script:
>
> Jenkins.instance.getAllItems(Job.class).each{ 
>   println it.name + " - " + it.class
>   }
>
>
> Next get each job and get build status :
> Following link has  script that can help you in that:
>
>
> https://github.com/cloudbees/jenkins-scripts/blob/master/get-build-information.groovy
>
> You need to use groovy plugin and it looks like below link.
>
>
> https://www.google.com/search?safe=active&q=jenkins+groovy+script+examples&sa=X&ved=2ahUKEwj-weOYx8TeAhXEtI8KHbCMABQQ1QIoA3oECAoQBA&biw=412&bih=660&dpr=2.63#imgrc=qnNClrZNVTUKnM
> :
>
> I know I didn't have you full solution but I hope this will give some 
> direction for to implement your requirement.
>
> Thanks
> Rajendra
>
>
>
> On Tue, 6 Nov, 2018, 15:41 trupti bhatt  
> wrote:
>
>> I want to get the jenkins report as in this template:
>>
>> [image: enter image description here] 
>> 
>>
>> so which plugin will help me to get such kind of report?
>>
>> I have tried multiple plugins, but no luck. I have tried test analyzer 
>> report, dashboard view and jenkins matrix and trends plugin. 
>>
>>
>> I think Groovy scripts may help. can anyone help me on it? 
>>
>>
>>
>>
>> Thank you,
>>
>> Trupti Bhatt
>>
>> -- 
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/291de8a3-6bf5-4d5e-ae15-625044d11aaa%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 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/msgi

Expose data with worker by 'Nodeport service' in Kubernetes plugin

[YAN-HONG WANG]

Hello all,

#
My environment:
Jenkins: 2.138.3-alpine
Kubernetes plugin: 1.13.5
#

I can create the dynamic worker pod with Kubernetes plugin.
And then it destroyed perfectly after finishing job.

But, is it possible to expose data with worker pod by *Nodeport service* 
when worker pod is *running*?

I could not see any relevant keyword in official website.
https://github.com/jenkinsci/kubernetes-plugin

Thanks very much.

Hong

-- 
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/9d76fd43-1c18-431c-936c-17ac718beae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.