[JIRA] (JENKINS-57165) Jenkins job fails on Agent with error java.lang.OutOfMemoryError: Java heap space
Title: Message Title Nikita Porwal created an issue Jenkins / JENKINS-57165 Jenkins job fails on Agent with error java.lang.OutOfMemoryError: Java heap space Issue Type: Task Assignee: Giuseppe Landolfi Components: slave-setup-plugin Created: 2019-04-24 05:42 Environment: Windows 7/10 Priority: Major Reporter: Nikita Porwal The Jenkins job on Agent machine fails at the end with below error: FATAL: Remote call on JNLP4-connect connection from failedFATAL: Remote call on JNLP4-connect connection from failedAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:1085) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:510) at hudson.model.Run.execute(Run.java:1810) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)java.lang.OutOfMemoryError: Java heap space at java.lang.String.(String.java:814) at java.lang.String.substring(String.java:2673) at org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:177) at org.jvnet.winp.WinProcess.getEnvironmentVariables(WinProcess.java:146) at hudson.util.ProcessTree$WindowsOSProcess.getEnvironmentVariables2(ProcessTree.java:591) at hudson.util.ProcessTree$WindowsOSProcess.hasMatchingEnvVars2(ProcessTree.java:603) at hudson.util.ProcessTree$WindowsOSProcess.access$700(ProcessTree.java:495) at hudson.util.ProcessTree$Windows.hasMatchingEnvVars(ProcessTree.java:679) at
[JIRA] (JENKINS-54091) Messages with ampersands are HTML escaped
Title: Message Title Martin Reinhardt commented on JENKINS-54091 Re: Messages with ampersands are HTML escaped really sure? RocketChat latest release version is 0.74.3: https://github.com/RocketChat/Rocket.Chat/releases/tag/0.74.3 and latest plugin is 1.4.3. Could you check with latest plugin version, at least Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Rohit Goel commented on JENKINS-57156 Re: p4 plugin : Invalid credentials Thanks Joel for providing the information. I was able to get it working by adding the jvm option -Duser.home to /var/lib/jenkins Appreciate the prompt replies. -Rohit Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55826) Add '-f' to 'p4 client -d' with cleanup/p4cleanup
Title: Message Title Hokwang Lee commented on JENKINS-55826 Re: Add '-f' to 'p4 client -d' with cleanup/p4cleanup released. please close. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57164) Allow Users to include/exclude paths from Multibranch SCM Triggering
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-57164 Allow Users to include/exclude paths from Multibranch SCM Triggering Issue Type: New Feature Assignee: Unassigned Components: branch-api-plugin, scm-api-plugin Created: 2019-04-24 03:40 Priority: Minor Reporter: Allan BURDAJEWICZ It would be great to have a branch build strategy to specify path(s) to include/exclude when deciding to trigger a job. Something similar to what https://github.com/jenkinsci/ignore-committer-strategy-plugin does. Add Comment
[JIRA] (JENKINS-57116) Version 1.15.1 does not create pods
Title: Message Title Martin Reinhardt assigned an issue to Carlos Sanchez Jenkins / JENKINS-57116 Version 1.15.1 does not create pods Change By: Martin Reinhardt Assignee: Martin Reinhardt Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57116) Version 1.15.1 does not create pods
Title: Message Title Martin Reinhardt updated JENKINS-57116 Jenkins / JENKINS-57116 Version 1.15.1 does not create pods Change By: Martin Reinhardt Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57116) Version 1.15.1 does not create pods
Title: Message Title
Martin Reinhardt commented on JENKINS-57116
Re: Version 1.15.1 does not create pods
actually with 1.15.2 it's still not working:
WARNING: Error in provisioning; agent=KubernetesSlave name: nodejs-h53r0, template=PodTemplate{inheritFrom='', name='nodejs', namespace='', instanceCap=2, idleMinutes=120, label='nodejs nvm', serviceAccount='jenkins-slaves', nodeSelector='', nodeUsageMode=NORMAL, workspaceVolume=EmptyDirWorkspaceVolume [memory=false], volumes=[SecretVolume [mountPath=/home/jenkins/nexus-jenkins-auth, secretName=nexus-jenkins-auth, defaultMode=null], SecretVolume [mountPath=/home/jenkins/sonar-jenkins-auth, secretName=sonar-jenkins-auth, defaultMode=null], EmptyDirVolume [mountPath=/tmp, memory=false]], containers=[ContainerTemplate{name='jnlp', image='docker-registry.default.svc:5000/ci-devtools/jenkins-slave-nodejs', alwaysPullImage=true, workingDir='/tmp', command='', args='${computer.jnlpmac} ${computer.name}', ttyEnabled=true, resourceRequestCpu='200m', resourceRequestMemory='2Gi', resourceLimitCpu='1', resourceLimitMemory='4Gi', envVars=[KeyValueEnvVar [getValue()=/home/jenkins, getKey()=HOME]], livenessProbe=org.csanchez.jenkins.plugins.kubernetes.ContainerLivenessProbe@c599987}], yamls=[]}
io.fabric8.kubernetes.client.KubernetesClientException: An error has occurred.
at io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:64)
at io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:53)
at io.fabric8.kubernetes.client.utils.Serialization.unmarshal(Serialization.java:238)
at io.fabric8.kubernetes.client.utils.Serialization.unmarshal(Serialization.java:191)
at io.fabric8.kubernetes.client.utils.Serialization.unmarshal(Serialization.java:178)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.unmarshal(OperationSupport.java:495)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.load(BaseOperation.java:331)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.load(BaseOperation.java:67)
at org.csanchez.jenkins.plugins.kubernetes.PodTemplateUtils.parseFromYaml(PodTemplateUtils.java:509)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
at org.csanchez.jenkins.plugins.kubernetes.PodTemplateBuilder.build(PodTemplateBuilder.java:201)
at org.csanchez.jenkins.plugins.kubernetes.PodTemplate.build(PodTemplate.java:718)
at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:103)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
[JIRA] (JENKINS-55363) Support different SSH providers
Title: Message Title Thai Pham commented on JENKINS-55363 Re: Support different SSH providers Ivan Fernandez Calvo, I didn't try it as it seems to be against the general recommendations. I doubt that it improve anything as I don't have any issue when I use the `ec2` plugin which I believe doesn't use the `ssh-slaves-plugin` to connect to the slaves. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31314) Running asynchronous code inside a @NonCPS method should fail cleanly
Title: Message Title Jesse Glick updated JENKINS-31314 Jenkins / JENKINS-31314 Running asynchronous code inside a @NonCPS method should fail cleanly Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57163) Using timestamps prevents parallel thread's catch block from executing sleep
Title: Message Title
Ben Kraft updated an issue
Jenkins / JENKINS-57163
Using timestamps prevents parallel thread's catch block from executing sleep
Change By:
Ben Kraft
Some strange interaction between parallel, timestamps, sleep, and try/catch is causing our groovy {{catch}} block to stop executing after a {{sleep}}. The code below provides the smallest repro I've found: we have a background thread which sets up {{timestamps}} and then sleeps for a while; in the foreground we sleep a bit less, then catch any exception, sleeping in the {{catch}} block. If the exception is raised (I've just been aborting the job) the part of the {{catch}} block after the {{sleep}} never executes. Sample log output is below; we expect to see a line saying "slept", but it never shows up.As far as I can tell, each part of the script below is required to reproduce the issue. In particular, removing the timestamps in the background thread causes the {{catch}} to execute as expected. (Note that removing that {{timestamps}} and adding one around {{body}} or around the toplevel job does not reproduce!) Similarly, various other code instead of the {{sleep(1)}} executes just fine. I'm not sure what's going wrong, but it sure seems to me like a bug in some part of how jenkins groovy translates and interprets this code!Groovy script:{code}def wrap(Closure body) {parallel("_watchdog": {timestamps {echo("started background sleep");sleep(600);echo("finished background sleep");}},"main": {body();},"failFast": true,);}wrap {try {echo("started sleep");sleep(60);echo("finished sleep");} catch (e) {echo("Caught error: ${e}")sleep(1);echo("slept")throw e;}echo("should never get here");}{code}Output:{code}Started by user Ben KraftRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] parallel[Pipeline] { (Branch: _watchdog)[Pipeline] { (Branch: main)[Pipeline] timestamps[Pipeline] {[Pipeline] echostarted sleep[Pipeline] sleepSleeping for 1 min 0 sec[Pipeline] echo10:39:27 started background sleep[Pipeline] sleep10:39:27 Sleeping for 10 minAborted by Ben Kraft[Pipeline] echoCaught error: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException[Pipeline] sleepSleeping for 1 sec[Pipeline] }[Pipeline] // timestamps[Pipeline] }Failed in branch _watchdog[Pipeline] }Failed in branch main[Pipeline] // parallel[Pipeline] End of Pipelineorg.jenkinsci.plugins.workflow.steps.FlowInterruptedException at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.cancel(CpsBodyExecution.java:244) at org.jenkinsci.plugins.workflow.steps.BodyExecution.cancel(BodyExecution.java:76) at org.jenkinsci.plugins.workflow.cps.steps.ParallelStepExecution.stop(ParallelStepExecution.java:67) at org.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.checkAllDone(ParallelStep.java:147) at
[JIRA] (JENKINS-41294) Support Bitbucket Cloud in Blue Ocean
Title: Message Title Jeremy H commented on JENKINS-41294 Re: Support Bitbucket Cloud in Blue Ocean Is OAuth still looking to be supported? Any idea where I can track progress of this feature? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57163) Using timestamps prevents parallel thread's catch block from executing sleep
Title: Message Title
Ben Kraft created an issue
Jenkins / JENKINS-57163
Using timestamps prevents parallel thread's catch block from executing sleep
Issue Type:
Bug
Assignee:
Steven G Brown
Components:
timestamper-plugin, workflow-basic-steps-plugin, workflow-cps-plugin
Created:
2019-04-24 01:23
Environment:
Jenkins 2.169 Ubuntu 18.04.2 OpenJDK 1.8.1_191 Plugins: Pipeline 2.6 Pipeline Basic Steps 2.15 Pipeline Groovy 2.67 Timestamper 1.9 (also broken on 1.8.10)
Priority:
Major
Reporter:
Ben Kraft
Some strange interaction between parallel, timestamps, sleep, and try/catch is causing our groovy catch block to stop executing after a sleep. The code below provides the smallest repro I've found: we have a background thread which sets up timestamps and then sleeps for a while; in the foreground we sleep a bit less, then catch any exception, sleeping in the catch block. If the exception is raised (I've just been aborting the job) the part of the catch block after the sleep never executes. Sample log output is below; we expect to see a line saying "slept", but it never shows up. As far as I can tell, each part of the script below is required to reproduce the issue. In particular, removing the timestamps in the background thread causes the catch to execute as expected. Similarly, various other code instead of the sleep(1) executes just fine. I'm not sure what's going wrong, but it sure seems to me like a bug in some part of how jenkins groovy translates and interprets this code! Groovy script:
def wrap(Closure body) {
parallel(
"_watchdog": {
timestamps {
[JIRA] (JENKINS-57162) Additional build args not taken into account for image name for pipeline Dockerfile
Title: Message Title
Bert JW Regeer created an issue
Jenkins / JENKINS-57162
Additional build args not taken into account for image name for pipeline Dockerfile
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-workflow-plugin, pipeline
Created:
2019-04-24 01:16
Labels:
pipeline docker-build-step docker
Priority:
Blocker
Reporter:
Bert JW Regeer
In https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/69e6f4af23665b6aee29fb050056463149122a82/pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/DockerPipelineFromDockerfileScript.groovy#L68 the hash for the the image to be built is computed, however this not properly take into account that we may use the same Dockerfile just with different build arguments to change the resulting image.
// Work-around for Jenkins not killing/removing older queued jobs
for (int i = 0; i < (BUILD_NUMBER as int); i++) {milestone()}
// What follows is the actual pipeline that we want Jenkins to go and build, along with all of the stages
pipeline {
options {
timeout(time: 1, unit: 'HOURS')
timestamps()
}
agent none;
stages {
stage("Unit Testing") {
parallel {
stage("Python 3.7") {
agent {
dockerfile {
filename 'Dockerfile.jenkins'
additionalBuildArgs '--build-arg TAG=3.7'
label 'docker'
}
}
steps {
sh 'tox
[JIRA] (JENKINS-47179) Can't use milestone with parallel stages in Declarative
Title: Message Title
Ashu Goel commented on JENKINS-47179
Re: Can't use milestone with parallel stages in Declarative
Any updates on this one? We have a parallel stage in which we deploy multiple services in their own stages. In each stage, we first prompt the user for input and then proceed to deploy. I'd like to be able to stick a milestone between each input and subsequent deploy: ``` stage("Deploy") { parallel { stage("Deploy Service 1") { steps { waitUntil { script { input "Want to deploy service 1?" milestone() echo "Deploying service 1" } } } stage("Deploy Service 2") { steps { waitUntil { script { input "Want to deploy service 2?" milestone() echo "Deploying service 2" } } } } ``` But am receiving the same "Using a milestone step inside parallel is not allowed" error.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47179) Can't use milestone with parallel stages in Declarative
Title: Message Title
Ashu Goel edited a comment on JENKINS-47179
Re: Can't use milestone with parallel stages in Declarative
Any updates on this one? We have a parallel stage in which we deploy multiple services in their own stages. In each stage, we first prompt the user for input and then proceed to deploy. I'd like to be able to stick a milestone between each input and subsequent deploy: ``` {code:java} stage("Deploy") { parallel { stage("Deploy Service 1") { steps { waitUntil { script { { input "Want to deploy service 1?" milestone() echo "Deploying service 1" } } } stage("Deploy Service 2") { steps { waitUntil { script { { input "Want to deploy service 2?" milestone() echo "Deploying service 2" } } } } {code} ``` But am receiving the same "Using a milestone step inside parallel is not allowed" error.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34973) RejectedAccessException thrown but no pending script approval added
Title: Message Title leemeador commented on JENKINS-34973 Re: RejectedAccessException thrown but no pending script approval added Same thing happens when the rejected code is in the initialization code to give a @Field its value. I suspect it becomes a static variable and the exception gets swallowed because its in the initialization for the class or called from inside, so to speak, the constructor. I used a line like this at the top of the script @Field List list = [''] * 21 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43353) Ability to abort all previous running builds
Title: Message Title
Brandon Squizzato edited a comment on JENKINS-43353
Re: Ability to abort all previous running builds
[~jglick]'s solution worked well for me until recently, when passing milestones started to take awhile. Passing the milestones used to happen very quickly but now for whatever reason it takes a second or so to pass each milestone. When your build number is 100+, obviously this can cause a big delay trying to pass each milestone created in the loop.So I've started to go with an approach like this: {{def buildNumber = env.BUILD_NUMBER as int}}{{ if (buildNumber > 1) milestone(buildNumber - 1)}}{{milestone(buildNumber)}}The result here would be:Build 1 runs and creates milestone 0, and milestone 1While build 1 is running, build 2 fires. It has milestone 1 and milestone 2Since build 2 passes milestone 1, it causes build #1 to abort.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56833) Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=10000
Title: Message Title Gavin Mogan closed an issue as Fixed Feel free to re-open after 1.15 is out Jenkins / JENKINS-56833 Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=1 Change By: Gavin Mogan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56833) Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=10000
Title: Message Title Gavin Mogan commented on JENKINS-56833 Re: Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=1 Yea we found out that every job/stage start/top will refresh the computers stuff. JENKINS-56773 has a fix, just needs to be merged. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42614) Pipeline support in EnvInject
Title: Message Title Charles Choi edited a comment on JENKINS-42614 Re: Pipeline support in EnvInject In pipeline "Properties Content",Path=$Path;$JAVA\\bin;C: \\ Program Files (x86)\\PuTTY;C:\\NGS\\bin;C:\\Python27;C:\\Python27 \\ Scripts$Path is not evaluated.How to "Inject environment variables" using pipeline syntax? I would like to see workarounds documentation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42614) Pipeline support in EnvInject
Title: Message Title Charles Choi commented on JENKINS-42614 Re: Pipeline support in EnvInject In pipeline "Properties Content",Path=$Path;$JAVA\\bin;C:Program Files (x86)\\PuTTY;C:\\NGS\\bin;C:\\Python27;C:\\Python27Scripts $Path is not evaluated. How to "Inject environment variables" using pipeline syntax? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56714) Add unit tests for IssuesChartPortlet
Title: Message Title Ulli Hafner closed an issue as Won't Fix Jenkins / JENKINS-56714 Add unit tests for IssuesChartPortlet Change By: Ulli Hafner Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56725) Add unit tests for AggregatedTrendAction
Title: Message Title Ulli Hafner assigned an issue to Ulli Hafner Jenkins / JENKINS-56725 Add unit tests for AggregatedTrendAction Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56725) Add unit tests for AggregatedTrendAction
Title: Message Title Ulli Hafner closed an issue as Won't Fix Jenkins / JENKINS-56725 Add unit tests for AggregatedTrendAction Change By: Ulli Hafner Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56880) blue ocean tests page shows stale data after clicked
Title: Message Title Gavin Mogan commented on JENKINS-56880 Re: blue ocean tests page shows stale data after clicked So I don't fully understand your scenario, but as simple triage, I think its related to https://issues.jenkins-ci.org/browse/JENKINS-46193 which will be fixed next release. If its not fixed, we'll look deeper into it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Joel Brown commented on JENKINS-57156 Re: p4 plugin : Invalid credentials The default location for the tickets file is $user.home/.p4tickets. Check the Manage Jenkins -> System Information for "user.dir". Is it /home/jenkins? To change, ask your IT to change OS user jenkins home dir to be /var/lib/jenkins. Or you can alter your jenkins startup to change it, set jvm option -Duser.home=/var/lib/jenkins and make sure the jenkins process OS user (typically 'jenkins') can r/w file in that dir. Or you also can point to a file, start jvm with -DticketPath=/some/path/to/p4tickets.txt (same r/w requirement) Where you set these java system props depends on your jenkins seutp. For example, add the -D to /etc/default/jenkins within JAVA_ARGS. Restart jenkins to pick it up. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57161) ec2 plugin locks queue until excessWorkload is 0
Title: Message Title Kevin Boschert created an issue Jenkins / JENKINS-57161 ec2 plugin locks queue until excessWorkload is 0 Issue Type: Bug Assignee: FABRIZIO MANFREDI Attachments: add_many_removes_thread_dump.txt, ec2-test.png, ecs-test.png, Jenkinsfile.stress_test Components: ec2-plugin Created: 2019-04-23 19:28 Environment: Jenkins 2.172 (from the jenkins/jenkins:2.172 docker image) ec2 1.42 durable-task 1.29 Labels: ec2 Queue Priority: Major Reporter: Kevin Boschert We have periods where we enqueue a burst of jobs (> 100) and need to spin up approximately that many workers. When this happens, the ec2 plugin appears to be taking out a substantial number of locks on the Queue, which prevents builds from being processed out of the Queue and assigned to an executor. We see the number of available executors go up until the excessWorkload is under the NodeProvisioner's thresholdMargin, at which point the Queue locks are released, and jobs are assigned to the executors. In cases where we need to spin up 100s of workers, we can see the Queue locked for a fairly long time (> 15 minutes). During the time that the Queue has been locked, if any of our EC2 workers reach the specified idle timeout, Jenkins.updateComputerList (which is called during Jenkins.addNode) will decide it needs to remove those workers, despite having a large Queue that we're in the middle
[JIRA] (JENKINS-56955) Uninstalling Blueocean Plugin 1.4.0 plugin doesnt resolve dependency errors
Title: Message Title Gavin Mogan commented on JENKINS-56955 Re: Uninstalling Blueocean Plugin 1.4.0 plugin doesnt resolve dependency errors how did you remove it? Your error says you are trying to load something that isn't there, which sounds right for removing random files. https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean/pom.xml#L23-L128 is the list of plugins the blueocean package installs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56977) Input "ChoiceParameterDefinition" with same name make the UI bug (select wrong choice when clicked)
Title: Message Title Gavin Mogan closed an issue as Cannot Reproduce Feel free to re-open if you can provide a sample test case. Jenkins / JENKINS-56977 Input "ChoiceParameterDefinition" with same name make the UI bug (select wrong choice when clicked) Change By: Gavin Mogan Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56977) Input "ChoiceParameterDefinition" with same name make the UI bug (select wrong choice when clicked)
Title: Message Title Gavin Mogan updated an issue Jenkins / JENKINS-56977 Input "ChoiceParameterDefinition" with same name make the UI bug (select wrong choice when clicked) Change By: Gavin Mogan Attachment: Peek 2019-04-23 12-10.gif Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56977) Input "ChoiceParameterDefinition" with same name make the UI bug (select wrong choice when clicked)
Title: Message Title
Gavin Mogan commented on JENKINS-56977
Re: Input "ChoiceParameterDefinition" with same name make the UI bug (select wrong choice when clicked)
I'm not sure what the problem is here, the example you have doesn't work on its own. I got as far as
pipeline {
agent any
stages {
stage("Hello") {
steps {
script {
def userInput = input(
id: 'userInput', message: "mytest",
parameters: [
[$class: 'ChoiceParameterDefinition', choices: "${VAR_1}", name: 'config']
])
VAR_2 = "${userInput}"
}
}
}
}
}
but thats missing VAR_1 Is this using declarative syntax? or the other one. I tried reproducing it on ci.blueocean.io but couldn't (set var_1 to "a\nb\nc\n") https://ci.blueocean.io/blue/organizations/jenkins/Gavin%20Folder%2FJENKINS-56977%20-%20multiline%20choice/activity
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57098) JSON Exchange format for import/export?
Title: Message Title Ulli Hafner assigned an issue to Ulli Hafner Jenkins / JENKINS-57098 JSON Exchange format for import/export? Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57009) java.lang.NegativeArraySizeException for long console output
Title: Message Title Gavin Mogan updated an issue Jenkins / JENKINS-57009 java.lang.NegativeArraySizeException for long console output Change By: Gavin Mogan Component/s: core Component/s: blueocean-plugin Component/s: logaction Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56772) Git branch with slashes are double encoded (Jenkins core and blue ocean)
Title: Message Title Gavin Mogan closed an issue as Cannot Reproduce Jenkins / JENKINS-56772 Git branch with slashes are double encoded (Jenkins core and blue ocean) Change By: Gavin Mogan Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56772) Git branch with slashes are double encoded (Jenkins core and blue ocean)
Title: Message Title Gavin Mogan commented on JENKINS-56772 Re: Git branch with slashes are double encoded (Jenkins core and blue ocean) https://github.com/cb-gmogan-test/mbtest is my test repo I'm going to close this for now saying unable to reproduce, but if you can reproduce it, especially in a repo we can use to test with (maybe its with a different scm (git, bitbucket, etc)) feel free to re-open. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Song Koh commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. DISTRIB_ID=LinuxMint DISTRIB_RELEASE=19.1 DISTRIB_CODENAME=tessa DISTRIB_DESCRIPTION="Linux Mint 19.1 Tessa" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Song Koh what OS and version are you using? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Song Koh commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Adrien, I think your commit 063512b6bce8ee4960c95d1ad8985bb2d0b84a36 will fix the init.d/jenkins issue. I am using debian package jenkins 2.174 I will limp along with with the the patch until the commit shows up on our end. We must have more than a 4 day lag. Everything else seems to be working for me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57098) JSON Exchange format for import/export?
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-57098 JSON Exchange format for import/export? Change By: Ulli Hafner Labels: help-wanted newbie-friendly Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56324) Age does not look correct for new issues when compared with a reference build
Title: Message Title Ulli Hafner updated JENKINS-56324 Jenkins / JENKINS-56324 Age does not look correct for new issues when compared with a reference build Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54736) Show errors of pmd.xml file
Title: Message Title Ulli Hafner updated JENKINS-54736 Jenkins / JENKINS-54736 Show errors of pmd.xml file Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54736) Show errors of pmd.xml file
Title: Message Title Ulli Hafner started work on JENKINS-54736 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54010) Support two levels of parallelity in stages
Title: Message Title Rishi Thakkar commented on JENKINS-54010 Re: Support two levels of parallelity in stages Is there any progress on this task? My team has a highly parallel flow that requires multiple layers of nested parallels. It would make life easier for debugging purposes if this feature were implemented. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. agreed, the java problem seems fixed, but yeah i have no idea what's going on now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Adrien Lecharpentier commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Joe Mihalich it seems we have the exact same setup, the same versions and all. But I can start Jenkins. What's bothering me is that we don't see why in your case (or I don't know where to look). I just edited the /etc/init.d/jenkins manually each time, but as we could see, the problem is not in the Java version anymore. So I guess my patched is fixing the problem but you are facing a new one. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57160) How to download latest non-maven artifact from JFrog artifactory?
Title: Message Title Farooq Khan created an issue Jenkins / JENKINS-57160 How to download latest non-maven artifact from JFrog artifactory? Issue Type: Bug Assignee: Eyal Ben Moshe Components: artifactory-plugin Created: 2019-04-23 17:35 Priority: Major Reporter: Farooq Khan I am trying to download latest non-maven artifact from artifactory using File Spec in jenkins pipeline. it works if there is onyl one file but if there are multiple files with different versions appended to their names then how to identify the latest file and download it using file spec? Add Comment
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich edited a comment on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. This is a totally vanilla 18.04 VirtualBox VM install. I'm not sure how we're seeing different things happening... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title
Joe Mihalich edited a comment on JENKINS-57096
Re: The latest debian installers 2.164+ do not work with java 11.
One other piece of info just so we make sure we're in sync... {code:java}jmihalich@ubuntu1804-jm:~$ lsb_release -aNo LSB modules are available.Distributor ID: UbuntuDescription:Ubuntu 18.04.2 LTSRelease:18.04Codename: bionic jmihalich@ubuntu1804-jm:~$ sudo dpkg -l | grep jdkii openjdk-11-jdk:amd64 11.0.2+9-3ubuntu1~18.04.3 amd64OpenJDK Development Kit (JDK)ii openjdk-11-jdk-headless:amd64 11.0.2+9-3ubuntu1~18.04.3 amd64OpenJDK Development Kit (JDK) (headless)ii openjdk-11-jre:amd64 11.0.2+9-3ubuntu1~18.04.3 amd64OpenJDK Java runtime, using Hotspot JITii openjdk-11-jre-headless:amd64 11.0.2+9-3ubuntu1~18.04.3 amd64OpenJDK Java runtime, using Hotspot JIT (headless) {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. This is a totally vanilla 18.04 install. I'm not sure how we're seeing different things happening... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52396) Integration with Blue Ocean?
Title: Message Title lee hurley commented on JENKINS-52396 Re: Integration with Blue Ocean? +1. Created an account just to say that. We can't fully upgrade to blue ocean without p4 support, and i'd love to be able to. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. One other piece of info just so we make sure we're in sync... jmihalich@ubuntu1804-jm:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title
Joe Mihalich edited a comment on JENKINS-57096
Re: The latest debian installers 2.164+ do not work with java 11.
Here's a list of all the dependency packages: {code:java}jmihalich@ubuntu1804-jm:~$ sudo dpkg -l | grep 'daemon\|adduser\|procps\|psmisc\|net-tools'ii acpid 1:2.0.28-1ubuntu1 amd64Advanced Configuration and Power Interface event daemonii adduser 3.116ubuntu1 all add and remove users and groupsii cron 3.0pl1-128.1ubuntu1amd64process scheduling daemon ii daemon 0.6.4-1build1 amd64turns other processes into daemonsii dbus 1.12.2-1ubuntu1amd64simple interprocess messaging system (daemon and utilities)ii dmeventd 2:1.02.145-4.1ubuntu3 amd64Linux Kernel Device Mapper event daemonii libprocps6:amd64 2:3.3.12-3ubuntu1.1amd64library for accessing process information from /procii lxd 3.0.3-0ubuntu1~18.04.1 amd64Container hypervisor based on LXC - daemonii net-tools 1.60+git20161116.90da8a0-1ubuntu1 amd64NET-3 networking toolkitii openvpn 2.4.4-2ubuntu1.1 amd64virtual private network daemonii procps 2:3.3.12-3ubuntu1.1amd64/proc file system utilitiesii psmisc 23.1-1ubuntu0.1amd64utilities that use the proc file system ii rsyslog 8.32.0-1ubuntu4amd64reliable system and kernel logging daemon ii thermald 1.7.0-5ubuntu2 amd64Thermal monitoring and controlling daemonii udev 237-3ubuntu10.20 amd64/dev/ and hotplug management daemon {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title
Joe Mihalich edited a comment on JENKINS-57096
Re: The latest debian installers 2.164+ do not work with java 11.
also, i tried this with the stable release 2.164.2 and had the same issue. I Then i also repackaged the jenkins deb packages (both 2.174 and 2.164.2) with the new jenkins file in it, so i don't have to replace the file after it fails. I did this via:{code:java}dpkg-deb -R and dpkg-deb -build{code}and I'm still getting the same issue. Joe
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. also, i tried this with the stable release 2.164.2 and had the same issue. I repackaged the jenkins deb packages (both 2.174 and 2.164.2) with the new jenkins file in it, so i don't have to replace the file after it fails via: dpkg-deb -R and dpkg-deb -build and I'm still getting the same issue. Joe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title
Joe Mihalich edited a comment on JENKINS-57096
Re: The latest debian installers 2.164+ do not work with java 11.
also, i tried this with the stable release 2.164.2 and had the same issue. I repackaged the jenkins deb packages (both 2.174 and 2.164.2) with the new jenkins file in it, so i don't have to replace the file after it fails . I did this via:{code:java}dpkg-deb -R and dpkg-deb -build{code}and I'm still getting the same issue. Joe
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Here's a list of all the dependency packages: jmihalich@ubuntu1804-jm:~$ sudo dpkg -l | grep 'daemon\|adduser\|procps\|psmisc\|net-tools' ii acpid 1:2.0.28-1ubuntu1 amd64Advanced Configuration and Power Interface event daemon ii adduser 3.116ubuntu1 all add and remove users and groups ii cron 3.0pl1-128.1ubuntu1amd64process scheduling daemon ii daemon0.6.4-1build1 amd64turns other processes into daemons ii dbus 1.12.2-1ubuntu1amd64simple interprocess messaging system (daemon and utilities) ii dmeventd 2:1.02.145-4.1ubuntu3 amd64Linux Kernel Device Mapper event daemon ii libprocps6:amd64 2:3.3.12-3ubuntu1.1amd64library for accessing process information from /proc ii lxd 3.0.3-0ubuntu1~18.04.1 amd64Container hypervisor based on LXC - daemon ii net-tools 1.60+git20161116.90da8a0-1ubuntu1 amd64NET-3 networking toolkit ii openvpn 2.4.4-2ubuntu1.1 amd64virtual private network daemon ii procps2:3.3.12-3ubuntu1.1amd64/proc file system utilities ii psmisc23.1-1ubuntu0.1amd64utilities that use the proc file system ii rsyslog 8.32.0-1ubuntu4amd64reliable system and kernel logging daemon ii thermald 1.7.0-5ubuntu2 amd64Thermal monitoring and controlling daemon ii udev 237-3ubuntu10.20 amd64/dev/ and hotplug management daemon Add Comment
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich updated an issue Jenkins / JENKINS-57096 The latest debian installers 2.164+ do not work with java 11. Change By: Joe Mihalich Comment: oh, is it just 'daemon' ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich updated an issue Jenkins / JENKINS-57096 The latest debian installers 2.164+ do not work with java 11. Change By: Joe Mihalich Comment: what daemon package are we talking about? Can you give me the exact deb package name so i can check? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. what daemon package are we talking about? Can you give me the exact deb package name so i can check? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. oh, is it just 'daemon' ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Adrien Lecharpentier commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. there's no log file that's what I feared. Not really a surprise, as the instance never started correctly. I tested, again, from a newly installation of Ubuntu Server without any default set, installing only openjdk-11-jdk and jenkins latest (2.174 when I write this). It failed with the default /etc/init.d/jenkins but as soon as I changed it for the patched version of the PR, it worked dirrectly. In my case, installing the jenkins package also installed the daemon package. Is it possible this package is missing in your case? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title
Joe Mihalich commented on JENKINS-57096
Re: The latest debian installers 2.164+ do not work with java 11.
I added a set -x to the jenkins script, here's the output.
jmihalich@ubuntu1804-jm:~$ sudo /etc/init.d/jenkins start
+ PATH=/bin:/usr/bin:/sbin:/usr/sbin
+ DESC=@@SUMMARY@@
+ NAME=@@ARTIFACTNAME@@
+ SCRIPTNAME=/etc/init.d/@@ARTIFACTNAME@@
+ '[' -r /etc/default/@@ARTIFACTNAME@@ ']'
+ DAEMON=/usr/bin/daemon
+ DAEMON_ARGS='--name=@@ARTIFACTNAME@@ --inherit --env=JENKINS_HOME= --output= --pidfile='
++ type -p java
+ JAVA=/usr/bin/java
+ '[' -n '' ']'
+ '[' '' = yes ']'
+ SU=/bin/su
+ '[' '!' -x /usr/bin/daemon ']'
+ '[' '' = false ']'
+ '[' -z /usr/bin/java ']'
+ JAVA_ALLOWED_VERSIONS=("18" "110")
++ sed -n ';s/.* version "\(.*\)\.\(.*\)\..*".*/\1\2/p;'
++ /usr/bin/java -version
+ JAVA_VERSION=110
+ [[ 18 110 =~ 110 ]]
+ echo 'Correct java version found'
Correct java version found
+ '[' -r /etc/default/locale ']'
+ . /etc/default/locale
++ LANG=en_US.UTF-8
+ export LANG LANGUAGE
+ . /lib/init/vars.sh
++ TMPTIME=0
++ SULOGIN=no
++ DELAYLOGIN=no
++ UTC=yes
++ VERBOSE=no
++ FSCKFIX=no
++ '[' -f /etc/default/rcS ']'
++ unset EDITMOTD
++ unset RAMRUN
++ unset RAMLOCK
++ '[' -r /proc/cmdline ']'
+++ cat /proc/cmdline
++ for ARG in $(cat /proc/cmdline)
++ case $ARG in
++ for ARG in $(cat /proc/cmdline)
++ case $ARG in
++ for ARG in $(cat /proc/cmdline)
++ case $ARG in
++ for ARG in $(cat /proc/cmdline)
++ case $ARG in
++ '[' '' ']'
+ . /lib/lsb/init-functions
+++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
++ for hook in $(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)
++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
++ . /lib/lsb/init-functions.d/20-left-info-blocks
++ for hook in $(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 2>/dev/null)
++ '[' -r /lib/lsb/init-functions.d/40-systemd ']'
++ . /lib/lsb/init-functions.d/40-systemd
+++ _use_systemctl=0
+++ '[' -d /run/systemd/system ']'
+++ prog=jenkins
+++ service=jenkins.service
systemctl -p LoadState --value show jenkins.service
+++ state=loaded
+++ '[' loaded = masked ']'
+++ '[' 10073 -ne 1 ']'
+++ '[' -z '' ']'
+++ case $(readlink -f "$0") in
readlink -f /etc/init.d/jenkins
+++ '[' loaded '!=' not-found ']'
+++ _use_systemctl=1
systemctl -p CanReload --value show jenkins.service
+++ '[' no = no ']'
+++ '[' start = reload ']'
+++ '[' 1 = 1 ']'
+++ set +e
+++ set +u
+++ '[' xstart = xstart -o xstart = xstop -o xstart = xrestart -o xstart = xreload -o xstart = xforce-reload -o xstart = xtry-restart -o xstart = xstatus ']'
+++ systemctl_redirect /etc/init.d/jenkins start
+++ local s
+++ local rc
+++ local prog=jenkins
+++ local command=start
+++ case "$command" in
+++ s='Starting jenkins (via systemctl)'
+++ service=jenkins.service
systemctl is-system-running
+++ OUT=degraded
+++ '[' degraded '!=' degraded ']'
+++ '[' start = status ']'
+++ log_daemon_msg 'Starting jenkins (via systemctl)' jenkins.service
+++ '[' -z 'Starting jenkins (via systemctl)' ']'
+++ log_daemon_msg_pre 'Starting jenkins (via systemctl)' jenkins.service
+++ log_use_fancy_output
+++ TPUT=/usr/bin/tput
+++ EXPR=/usr/bin/expr
+++ '[' -t 1 ']'
+++ '[' xxterm-256color '!=' x ']'
+++ '[' xxterm-256color '!=' xdumb ']'
+++ '[' -x /usr/bin/tput ']'
+++ '[' -x /usr/bin/expr ']'
+++ /usr/bin/tput hpa 60
+++ /usr/bin/tput setaf 1
+++ '[' -z ']'
+++ FANCYTTY=1
+++ case "$FANCYTTY" in
+++ true
+++ echo -n '[] '
[] +++ '[' -z
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. There's no log file on /var/log/jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32087) Configure JIRA credentials at the Job configuration level
Title: Message Title Mathieu Delrocq started work on JENKINS-32087 Change By: Mathieu Delrocq Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32087) Configure JIRA credentials at the Job configuration level
Title: Message Title Mathieu Delrocq assigned an issue to Mathieu Delrocq Jenkins / JENKINS-32087 Configure JIRA credentials at the Job configuration level Change By: Mathieu Delrocq Assignee: Mathieu Delrocq Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Adrien Lecharpentier commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. ok, so there is no additional details here. Would you have a /var/log/jenkins/jenkins.log file to share? I'm not sure you should have one.. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich edited a comment on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. jmihalich@ubuntu1804-jm:~$ journalctl -xe -- – Defined-By: systemd -- – Support: [ http://www.ubuntu.com/support ] -- – -- Unit UNIT has finished shutting down.Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent (ssh-agent emulation). -- – Subject: Unit UNIT has finished shutting down -- – Defined-By: systemd -- – Support: [ http://www.ubuntu.com/support ] -- – -- Unit UNIT has finished shutting down.Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). -- – Subject: Unit UNIT has finished shutting down -- – Defined-By: systemd -- – Support: [ http://www.ubuntu.com/support ] -- – -- Unit UNIT has finished shutting down.Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG network certificate management daemon. -- – Subject: Unit UNIT has finished shutting down -- – Defined-By: systemd -- – Support: [ http://www.ubuntu.com/support ] -- – -- Unit UNIT has finished shutting down.Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache (restricted). -- – Subject: Unit UNIT has finished shutting down -- – Defined-By: systemd -- – Support: [ http://www.ubuntu.com/support ] -- – -- Unit UNIT has finished shutting down.Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache. -- – Subject: Unit UNIT has finished shutting down -- – Defined-By: systemd -- – Support: [ http://www.ubuntu.com/support ] -- – -- Unit UNIT has finished shutting down.Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Reached target Shutdown. -- – Subject: Unit UNIT has finished start-up -- – Defined-By: systemd -- – Support: [ http://www.ubuntu.com/support ] -- – -- Unit UNIT has finished starting up. -- – -- The start-up result is RESULT.Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Starting Exit the Session... -- – Subject: Unit UNIT has begun start-up -- – Defined-By: systemd -- – Support: [ http://www.ubuntu.com/support ] -- – -- Unit UNIT has begun starting up.Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Received SIGRTMIN+24 from PID 8881 (kill).Apr 23 15:55:13 ubuntu1804-jm systemd[1]: user@0.service: Killing process 8881 (kill) with signal SIGKILL.Apr 23 15:55:13 ubuntu1804-jm systemd[1]: Stopped User Manager for UID 0. -- – Subject: Unit user@0.service has finished shutting down -- – Defined-By: systemd -- – Support: [ http://www.ubuntu.com/support ] -- – -- Unit user@0.service has finished shutting down.Apr 23 15:55:13 ubuntu1804-jm systemd[1]: Removed slice User Slice of root. -- – Subject: Unit user-0.slice has finished shutting down -- – Defined-By: systemd -- – Support: [ http://www.ubuntu.com/support ] -- – -- Unit user-0.slice has finished shutting down.Apr 23 15:55:14 ubuntu1804-jm jenkins[8814]: ...fail!Apr 23 15:55:14 ubuntu1804-jm systemd[1]: jenkins.service: Control process exited, code=exited status=7Apr 23 15:55:14 ubuntu1804-jm systemd[1]: jenkins.service: Failed with result 'exit-code'.Apr 23 15:55:14 ubuntu1804-jm systemd[1]: Failed to start LSB: Start @@PRODUCTNAME@@ at boot time. -- – Subject: Unit jenkins.service has failed -- – Defined-By: systemd -- – Support: [ http://www.ubuntu.com/support ] -- – -- Unit jenkins.service has failed. -- – -- The result is RESULT.Apr 23 15:55:14 ubuntu1804-jm sudo[8782]: pam_unix(sudo:session): session closed for user rootApr 23 15:58:46 ubuntu1804-jm systemd-timesyncd[447]:
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. jmihalich@ubuntu1804-jm:~$ journalctl -xe – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent (ssh-agent emulation). – Subject: Unit UNIT has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). – Subject: Unit UNIT has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG network certificate management daemon. – Subject: Unit UNIT has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache (restricted). – Subject: Unit UNIT has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache. – Subject: Unit UNIT has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Reached target Shutdown. – Subject: Unit UNIT has finished start-up – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished starting up. – -- The start-up result is RESULT. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Starting Exit the Session... – Subject: Unit UNIT has begun start-up – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has begun starting up. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Received SIGRTMIN+24 from PID 8881 (kill). Apr 23 15:55:13 ubuntu1804-jm systemd[1]: user@0.service: Killing process 8881 (kill) with signal SIGKILL. Apr 23 15:55:13 ubuntu1804-jm systemd[1]: Stopped User Manager for UID 0. – Subject: Unit user@0.service has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit user@0.service has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[1]: Removed slice User Slice of root. – Subject: Unit user-0.slice has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit user-0.slice has finished shutting down. Apr 23 15:55:14 ubuntu1804-jm jenkins[8814]: ...fail! Apr 23 15:55:14 ubuntu1804-jm systemd[1]: jenkins.service: Control process exited, code=exited status=7 Apr 23 15:55:14 ubuntu1804-jm systemd[1]: jenkins.service: Failed with result 'exit-code'. Apr 23 15:55:14 ubuntu1804-jm systemd[1]: Failed to start LSB: Start @@PRODUCTNAME@@ at boot time. – Subject: Unit jenkins.service has failed – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit jenkins.service has failed. – -- The result is RESULT. Apr 23 15:55:14 ubuntu1804-jm sudo[8782]: pam_unix(sudo:session): session closed for user root Apr 23 15:58:46 ubuntu1804-jm systemd-timesyncd[447]: Network configuration changed, trying to establish connection. Apr 23 15:58:46 ubuntu1804-jm systemd-networkd[647]: enp0s8: DHCP: No routes received from DHCP server: No data available Apr 23 15:58:46 ubuntu1804-jm systemd-timesyncd[447]: Synchronized to time server
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Adrien Lecharpentier commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. thank you Joe Mihalich. So the java version is correctly parsed, the sed _expression_ is correct. The problem must be after that The fact that the /var/lib/jenkins is empty is not a real surprise, as the instance didn't start once, there is no "jenkins-home" (which is the purpose of the folder). Could you please provide me the output of journalctl -xe? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56723) Add unit tests for IssueDifference
Title: Message Title Ulli Hafner updated JENKINS-56723 Jenkins / JENKINS-56723 Add unit tests for IssueDifference Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Hi, here's the output you requested: jmihalich@ubuntu1804-jm:~$ sudo /etc/init.d/jenkins start JAVA_VERSION = 110 Correct java version found [] Starting jenkins (via systemctl): jenkins.serviceJob for jenkins.service failed because the control process exited with error code. See "systemctl status jenkins.service" and "journalctl -xe" for details. failed! jmihalich@ubuntu1804-jm:~$ ls -la /var/lib/jenkins total 8 drwxr-xr-x 2 jenkins jenkins 4096 Apr 22 15:09 . drwxr-xr-x 36 root root 4096 Apr 23 15:49 .. I want to repeat again that, for whatever reason, after running sudo apt-get install jenkins, and it fails, the /var/lib/jenkins directory is empty. (see above). That is most likely why jetty startup is failing. Joe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Rohit Goel commented on JENKINS-57156 Re: p4 plugin : Invalid credentials Hi Karl, Its set to /var/lib/jenkins. I have tried changing to some other location as well (with chmod -R 777), but no difference -Rohit Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Rohit Goel updated an issue Jenkins / JENKINS-57156 p4 plugin : Invalid credentials Change By: Rohit Goel Attachment: image-2019-04-23-21-24-06-898.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Adrien Lecharpentier commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Song Koh thank you. I know it was included in the original post, but I thought I fixed it with the PR I filled. Could you please make sure you are using the same /etc/init.d/jenkins context as in https://github.com/jenkinsci/packaging/pull/117? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Song Koh commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Just for the record, the original post already had this info... "The second problem is, the value of JAVA_VERSION after that command with java 11 installed is: "110 2019-01-15". So that command is completely broken for java 11." Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Song Koh commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Sure. The output is... - Found an incorrect Java version Java version found: 110 2019-01-15 Aborting - Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57159) Improve JobConfigHistory to support managed files
Title: Message Title Tim Bradt created an issue Jenkins / JENKINS-57159 Improve JobConfigHistory to support managed files Issue Type: New Feature Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2019-04-23 15:12 Environment: Cloudbees Core Managed Master 2.138.2.2-rolling OS unknown - whatever Cloudbees uses Job Configuration History Plugin 2.18.3 Using Chrome for web browser Priority: Major Reporter: Tim Bradt The JobConfigHistory plugin works for jobs as well as system configuration. The other primary component that serves a good chunk of our configuration is the managed files, which this plugin does not currently support, and we feel that pain. It would be extremely useful to have this. Add Comment
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Karl Wirth commented on JENKINS-57156 Re: p4 plugin : Invalid credentials Hi Rohit Goel, what is 'Home directory' set to in your Jenkins setup? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57156 p4 plugin : Invalid credentials Change By: Karl Wirth Attachment: image-2019-04-23-16-02-31-176.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57158) Pipeline is green but shows red in stage view
Title: Message Title Jeff Care created an issue Jenkins / JENKINS-57158 Pipeline is green but shows red in stage view Issue Type: Bug Assignee: Sam Van Oort Attachments: green_red.JPG, support_2019-04-23_14.58.31.zip Components: pipeline-stage-view-plugin Created: 2019-04-23 15:02 Priority: Minor Reporter: Jeff Care We had a build complete successfully; it shows green when viewing the details for that particular build and in the list of builds for that job. However, in the stage view for the job, that particular build shows red. Screenshot attached. Add Comment
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-57156 p4 plugin : Invalid credentials Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57157) Global Tools fail to update automatic installs
Title: Message Title Josiah Eubank created an issue Jenkins / JENKINS-57157 Global Tools fail to update automatic installs Issue Type: Bug Assignee: Sonar Team Components: sonar, workflow-basic-steps-plugin Created: 2019-04-23 14:55 Environment: Jenkins 2.173, Pipeline Basic Steps 2.15, Sonarqube Scanner for Jenkins 2.8.1 Labels: tools sonarqube update pipeline automatic-install Priority: Minor Reporter: Josiah Eubank When a tool is upgraded versions or the automatic installer is changed, Jenkins does not update the tool installed on the build agent. For example, the Sonarqube plugin installs its scanner as a Global Tool with an automatic installer from maven (populated dropdown). If you change versions, the new version does not overwrite the previous version on the build agent. Current workaround is to manually delete the tools directory from every build agent when upgrading any tools. Expected behavior: either install the tool to a version specific directory based on the source (zip file name, maven version, etc) or overwrite the generic directory with whichever version is specified in Global Tool Configuration (either upgrade or downgrade)
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Rohit Goel created an issue Jenkins / JENKINS-57156 p4 plugin : Invalid credentials Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-04-23 14:51 Environment: Jenkins home directory is set to /var/lib/jenkins Priority: Blocker Reporter: Rohit Goel I am trying to setup Jenkins with P4 plugin on RHEL. Jenkins is up and running but when I try to add credentials using perforce password, it fails with the below error. I believe I know the reason - there is nothing called /home/jenkins and it cannot be created as the user "home" are managed by our IT team. It seems like the plugin is trying to do something at "/home/jenkins" and fails. How can I specify some other location instead ? Apr 23, 2019 8:13:02 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connect SEVERE: P4: Unable to login: com.perforce.p4java.exception.ConnectionException: com.perforce.p4java.exception.ConfigException: java.nio.file.AccessDeniedException: /home/jenkins Apr 23, 2019 8:13:02 PM org.jenkinsci.plugins.p4.client.ConnectionHelper INFO: P4: Unable to login: com.perforce.p4java.exception.ConnectionException: com.perforce.p4java.exception.ConfigException: java.nio.file.AccessDeniedException: /home/jenkins Apr 23, 2019 8:13:02 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry SEVERE: P4: Connection retry: 1 Apr 23, 2019 8:13:02 PM org.jenkinsci.plugins.p4.client.ConnectionHelper INFO: P4: Connection retry: 1 Apr 23, 2019 8:13:05 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry SEVERE: P4: Invalid credentials. Giving up... Apr 23, 2019 8:13:05 PM org.jenkinsci.plugins.p4.client.ConnectionHelper INFO: P4: Invalid credentials. Giving up...
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title William F edited a comment on JENKINS-56890 Re: IOException: "cannot find current thread" looking at the class methods where "threads" (a TreeMap) is accessed: https://github.com/jenkinsci/workflow-cps-plugin/blob/ master f610f0bcf732b13ff542dd4f716d9520988f99a7 /src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThreadGroup.java# L176 L186 - L195 L205 I see that there is an attempt to ensure that all "put" calls are executed within the same thread -- but AFAICT there is no such logic for "get".Given that TreeMap is NOT a thread-safe class, if calls to "threads.put" and "threads.get" are interleaved, it is entirely possible to get "null" when invoking "get" for a key that has been "put" in another thread.Even without interleaved execution, I believe it would be possible to get such behavior simply via invoking "put" and "get" in different threads without any synchronization constructs, in terms of the Java Memory Model (but my own memory regarding the JMM is pretty hazy).In other words, from a glance, it really just looks like "threads" is being manipulated in a non-threadsafe manner. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title Michał Czech commented on JENKINS-56890 Re: IOException: "cannot find current thread" Jenkins 2.164.1: 15:55:20 ERROR during Build: java.io.IOException: cannot find current thread*15:55:20* at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:300)15:55:20 at org.jenkinsci.plugins.workflow.cps.CpsBodySubContext.doGet(CpsBodySubContext.java:88)15:55:20 at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:67)15:55:20 at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Callback.finished(BindingStep.java:254)15:55:20 at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution2$Callback2.finished(BindingStep.java:162)15:55:20 at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:140)15:55:20 at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57085) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-57085 Stack Traces with complex file names cannot be deserialized by XStream Offhand it sounds like groovy-cps is creating poor bytecode, and XStream is also behaving poorly. Ideally both would be fixed. Probably best to focus on groovy-cps to start with, since getting fixes into upstream XStream could take a while. (We have a fork anyway, but I would rather not add to the diff.) Change By: Jesse Glick Component/s: workflow-cps-plugin Labels: pipeline xstream Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46124) EnvStep convert map to list
Title: Message Title jerry wiltse commented on JENKINS-46124 Re: EnvStep convert map to list Did anyone ever file a separate issue to create an overload of withEnv which takes a Map? Indeed, the overload to pass a Map would be convenient for us as well. I assumed the reason for the current signature was that Groovy's underlying string helper function "execute()" takes a String[] called envp for environment variables, so withEnv was designed in such a way that the env vars could just be passed through without a type conversion. Otherwise, I can't imagine why it was designed this way. Of note, it seems the GDSL file currently says it takes a Map, which appears to be simply incorrect. method(name: 'withEnv', type: 'Object', params: [overrides:Map, body:'Closure'], doc: 'Set environment variables') Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Adrien Lecharpentier commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Song Koh could you please apply what I asked in my previous comment and provide me the same output so I can see what I missed in the sed _expression_? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov commented on JENKINS-56976 Re: WAIT ERROR even though when JESINTERFACELEVEL is 2 forgot to add extra space for rc processing. Kindly retest. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-56976 WAIT ERROR even though when JESINTERFACELEVEL is 2 Change By: Alexander Shcherbakov Attachment: zos-connector-extra-space.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Nitya R commented on JENKINS-56976 Re: WAIT ERROR even though when JESINTERFACELEVEL is 2 i have uploaded the latest log - RC0_log_v2.txt The build failed with CC_Wait_error, but it did not write the spool log multiple times like the previous version. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Nitya R updated an issue Jenkins / JENKINS-56976 WAIT ERROR even though when JESINTERFACELEVEL is 2 Change By: Nitya R Attachment: RC0_log_v2.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57001) Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun
Title: Message Title Padmapriya Balasundaram commented on JENKINS-57001 Re: Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun Oleg Nenashev We have applied Whitelisting to the plugins( Build flow and dsl plugins) .PFA screenshot. Also can you please exactly say in which file(Path) we need to apply this whitelisting Suppress the entire whitelist by using "-Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57001) Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun
Title: Message Title Padmapriya Balasundaram started work on JENKINS-57001 Change By: Padmapriya Balasundaram Status: Reopened In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57001) Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun
Title: Message Title Padmapriya Balasundaram updated an issue Jenkins / JENKINS-57001 Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun Change By: Padmapriya Balasundaram Attachment: image-2019-04-23-19-01-29-934.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57155) Not able to connect to aws EKS
Title: Message Title venkatesh kristipati created an issue Jenkins / JENKINS-57155 Not able to connect to aws EKS Issue Type: Bug Assignee: Carlos Sanchez Attachments: image-2019-04-23-18-43-01-574.png Components: kubernetes-plugin Created: 2019-04-23 13:16 Environment: Kubernetes Plugin Labels: plugin kuberenetes-plugin Priority: Minor Reporter: venkatesh kristipati Hi Team, I am using jenkins kubernetes plugin for deploying and building for EKS cluster. But i am not able to use cross EKS cluster by creating a kubernetes cloud in kubernetes plugin. if there is any possibility please update me to configure that I am not able to accesses AWS EKS using jenkins kubernetes plugin. These are the below errors that are occurred while using this. !image-2019-04-23-18-43-01-574.png|thumbnail!
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Henrik Skupin commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Daniel Beck thank you for bringing this up. It's actually not my job to make such a decision, so I will leave it up to the release managers to decide. I will clearly reference your last comment, so that they are aware of the situation for Jenkins users. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57001) Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun
Title: Message Title Padmapriya Balasundaram updated JENKINS-57001 Jenkins / JENKINS-57001 Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun Change By: Padmapriya Balasundaram Resolution: Duplicate Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43322) Nested view should be also searchable by name
Title: Message Title Baptiste Mathus updated JENKINS-43322 Jenkins / JENKINS-43322 Nested view should be also searchable by name Change By: Baptiste Mathus Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
