[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance when using 'grep' After the latest updates I got the problem again. Besides, all my automatic build weren't restartet The list of updates: Jira 3.0.10 -> 3.0.11 Oracle Java SE Development Kit Installer 1.3->1.4 Script Security 1.67->1.68 Warnings Next Generation 7.2.0->7.2.1 Jenkins v2.190.3 Lat*'s see what happens after a service restart... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201861.156818559.6086.1574674020060%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance when using 'grep' Change By: Christoph Fetzer Environment: jenkins ver 2.176.3jenkins ver 2.190.1 jenkins ver 2.190.3 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201861.156818559.6087.1574674080260%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance when using 'grep' Change By: Christoph Fetzer Component/s: core Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201861.156818559.6088.1574674320126%40Atlassian.JIRA.
[JIRA] (JENKINS-60244) Jenkins performance is slow while running Automation scripts .
Title: Message Title Ranjan Bhuyan commented on JENKINS-60244 Re: Jenkins performance is slow while running Automation scripts . Did you get a chance to look into attached file . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203226.1574344764000.6090.1574674680706%40Atlassian.JIRA.
[JIRA] (JENKINS-60261) ClassNotFoundException when adding a DocLinksPublisher post-build action
Title: Message Title John Young created an issue Jenkins / JENKINS-60261 ClassNotFoundException when adding a DocLinksPublisher post-build action Issue Type: Bug Assignee: sogabe Components: doclinks-plugin Created: 2019-11-25 09:40 Environment: Windows 10, Jenkins v2.190.3, using Chrome 78.0.3904.108, java version "1.8.0_181", DocLinks plugin 0.6.1 Labels: doclink Priority: Minor Reporter: John Young Steps to Reproduce Add a post-build action 'Publish documents'. Enter 'Title', 'Directory to archive', and Index file'. Click 'Save' button. The following stack trace appears and when I look for the added step it is missing. java.lang.ClassNotFoundException: hudson.maven.MavenModule at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1383) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1336) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1083) at java.lang.ClassLoader.loadClass(Unknown Source) Caused: java.lang.NoClassDefFoundError: hudson/maven/MavenModule at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateG
[JIRA] (JENKINS-60197) Support macOS applications upload
Title: Message Title Em Jot commented on JENKINS-60197 Re: Support macOS applications upload It works without any issues for me. Thanks for doing a great job Mez Pahlan Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203167.1574075366000.6094.1574674980253%40Atlassian.JIRA.
[JIRA] (JENKINS-60262) Jenkins AppCenter Plugin cannot used
Title: Message Title Guogang Gao created an issue Jenkins / JENKINS-60262 Jenkins AppCenter Plugin cannot used Issue Type: Bug Assignee: Mez Pahlan Components: appcenter-plugin Created: 2019-11-25 10:08 Priority: Minor Reporter: Guogang Gao I write the path to app ，when I build, a wrong came that File found matching pattern: apks\ford.apk Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Uwe Brackenhoff created an issue Jenkins / JENKINS-60263 Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. Issue Type: Bug Assignee: Ulli Hafner Attachments: installed_plugins.txt Components: warnings-ng-plugin Created: 2019-11-25 10:15 Environment: Jenkins ver. 2.190.3; list of plugins attached; java.vendor AdoptOpenJDK; java.runtime.version 11.0.5+10; sun.management.compiler HotSpot 64-Bit Tiered Compilers; OS Win7x64pro Labels: plugin Priority: Minor Reporter: Uwe Brackenhoff Hallo, I'm sorry to bother you agin, but even after update to 7.2.1 im still facing the following error: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. at io.jenkins.plugins.analysis.core.util.ModelValidation.ensureValidId(ModelValidation.java:91) at io.jenkins.plugins.analysis.core.steps.RecordIssuesStep.setId(RecordIssuesStep.java:549) Caused: java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.jenkinsci.plugins.structs.describable.Setter$1.set(Setter.java:
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title
Uwe Brackenhoff updated an issue
Jenkins / JENKINS-60263
Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Change By:
Uwe Brackenhoff
Hallo,h4. I'm sorry to bother you agin, but even after update to 7.2.1 im still facing the following error:java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. at io.jenkins.plugins.analysis.core.util.ModelValidation.ensureValidId(ModelValidation.java:91) at io.jenkins.plugins.analysis.core.steps.RecordIssuesStep.setId(RecordIssuesStep.java:549) Caused: java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.jenkinsci.plugins.structs.describable.Setter$1.set(Setter.java:33) at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:429) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:331) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:269) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at jdk.internal.reflect.GeneratedMethodAccessor433.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:160) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:157) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:158) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:162) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:132) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) Caused: java.lang.IllegalArgumentException: Could not instantiate{id=Build_Binary, name=Build Binary, sourceCodeEncodin
[JIRA] (JENKINS-58353) New jenkins job doesn't get added to the Dashboard view using Python Jenkins
Title: Message Title
Máté Csanády commented on JENKINS-58353
Re: New jenkins job doesn't get added to the Dashboard view using Python Jenkins
Hi Vineeth! I've fonund a workaround. I know, that it's not the solution, but solves your problem, while there is no fix for the bug. I run a groovy script on the server, that adds the job under the specified view. My code:
view = "MyView"
job = "MyJob"
try:
script = "import jenkins.model.Jenkins\nJenkins jenkins = Jenkins.getInstance()\nmyView = hudson.model.Hudson.instance.getView(\"" + view + "\")\nmyView.doAddJobToView(\"" + job + "\")"
server.run_script(script)
save = "import jenkins.model.Jenkins\nJenkins jenkins = Jenkins.getInstance()\njenkins.save()"
server.run_script(save)
except Exception, e:
print("Cannot add job under the specified view\n" + str(e).decode("utf-8"))
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200468.1562310678000.6110.1574677560171%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title
Uwe Brackenhoff updated an issue
Jenkins / JENKINS-60263
Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Change By:
Uwe Brackenhoff
Hallo,h4. I'm sorry to bother you agin, but even after update to 7.2.1 im still facing the following error:java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. at io.jenkins.plugins.analysis.core.util.ModelValidation.ensureValidId(ModelValidation.java:91) at io.jenkins.plugins.analysis.core.steps.RecordIssuesStep.setId(RecordIssuesStep.java:549)Caused: java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.jenkinsci.plugins.structs.describable.Setter$1.set(Setter.java:33) at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:429) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:331) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:269) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at jdk.internal.reflect.GeneratedMethodAccessor433.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:160) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:157) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:158) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:162) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:132) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) Caused: java.lang.IllegalArgumentException: Could not instantiate{id=Build_Binary, name=Build Binary, sourceCodeEncoding=UTF-8, enabledForFailure=true, aggregatingResults=true, tools=[@groovyScript(id=Bui
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title
Uwe Brackenhoff updated an issue
Jenkins / JENKINS-60263
Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Change By:
Uwe Brackenhoff
Hallo,h4. I'm sorry to bother you agin, but even after update to 7.2.1 im still facing the following error:java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. at io.jenkins.plugins.analysis.core.util.ModelValidation.ensureValidId(ModelValidation.java:91) at io.jenkins.plugins.analysis.core.steps.RecordIssuesStep.setId(RecordIssuesStep.java:549)Caused: java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.jenkinsci.plugins.structs.describable.Setter$1.set(Setter.java:33) at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:429) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:331) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:269) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at jdk.internal.reflect.GeneratedMethodAccessor433.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:160) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:157) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:158) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:162) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:132) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) Caused: java.lang.IllegalArgumentException: Could not instantiate{id=Build_Binary, name=Build Binary, sourceCodeEncoding=UTF-8, enabledForFailure=true, aggregatingResults=true, tools=[@groovyScript(id=Bui
[JIRA] (JENKINS-58353) New jenkins job doesn't get added to the Dashboard view using Python Jenkins
Title: Message Title Vineeth Karkad commented on JENKINS-58353 Re: New jenkins job doesn't get added to the Dashboard view using Python Jenkins Hi Máté! Phew, this is awesome! I will try it out and update you on how it goes..Thanks a bunch, really appreciate it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200468.1562310678000.6115.1574677860255%40Atlassian.JIRA.
[JIRA] (JENKINS-60251) multibranch streams don't allow lightweight checkout?
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60251 multibranch streams don't allow lightweight checkout? Change By: Karl Wirth Attachment: image-2019-11-25-10-52-29-460.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203241.1574477155000.6119.1574679180175%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Ulli Hafner commented on JENKINS-60263 Re: Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. I added a help text in the latest version: The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (i.e., the ID must match `[a-z0-9][a-z0-9-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used. You must not use upper case characters since they will resolve to the same URL as lowercase ones. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.6121.1574679300800%40Atlassian.JIRA.
[JIRA] (JENKINS-60264) Running a multibranch pipeline job results in missing workspace error
Title: Message Title
Daniel Estermann created an issue
Jenkins / JENKINS-60264
Running a multibranch pipeline job results in missing workspace error
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
image-2019-11-25-12-00-07-262.png, image-2019-11-25-12-00-29-961.png, image-2019-11-25-12-00-35-176.png
Components:
workflow-durable-task-step-plugin
Created:
2019-11-25 11:01
Environment:
jenkins-core 2.205 workflow-durable-task-step 2.35
Priority:
Major
Reporter:
Daniel Estermann
I build my own Jenkins image and check it's sanity by starting in in a docker container and trying to login to it. I achieve this using the following Jenkinsfile:
stages {
stage('Build Jenkins Master Image') {
steps {
sh(
script: """
cd Jenkins-Master
docker pull jenkins:latest
docker build --rm -t ${IMAGE_TAG} .
"""
)
}
}
stage('Image sanity check') {
steps {
withCredentials([string(credentialsId: 'CASC_VAULT_TOKEN', variable: 'CASC_VAULT_TOKEN'),
usernamePassword(credentialsId: 'Forge_service_account', passwordVariable: 'JENKINS_PASSWORD', usernameVariable: 'JENKINS_LOGIN')]) {
sh(
script: "
[JIRA] (JENKINS-60264) Running a multibranch pipeline job results in missing workspace error
Title: Message Title
Daniel Estermann updated an issue
Jenkins / JENKINS-60264
Running a multibranch pipeline job results in missing workspace error
Change By:
Daniel Estermann
I build my own Jenkins image and check it's sanity by starting in in a docker container and trying to login to it. I achieve this using the following Jenkinsfile:{code}stages {stage('Build Jenkins Master Image') {steps {sh( script: """ cd Jenkins-Master docker pull jenkins:latest docker build --rm -t ${IMAGE_TAG} . """)}}stage('Image sanity check') {steps {withCredentials([string(credentialsId: 'CASC_VAULT_TOKEN', variable: 'CASC_VAULT_TOKEN'), usernamePassword(credentialsId: 'Forge_service_account', passwordVariable: 'JENKINS_PASSWORD', usernameVariable: 'JENKINS_LOGIN')]) {sh( script: """ docker run -e CASC_VAULT_TOKEN=${CASC_VAULT_TOKEN} \ --name jenkins \ -d \ -p 8080:8080 ${IMAGE_TAG} mvn -Djenkins.test.timeout=${GLOBAL_TEST_TIMEOUT} -B -f Jenkins-Master/pom.xml test """)}}}{code}The test is successful, but the build fails with the following log:{code}[2019-11-25T10:33:38.333Z] Nov 25, 2019 11:33:37 AM ch.ti8m.forge.jenkins.logintest.LocalhostJenkinsRule before[2019-11-25T10:33:38.333Z] INFO: Waiting for Jenkins instance... (response code 503)[2019-11-25T10:33:43.628Z] Nov 25, 2019 11:33:42 AM ch.ti8m.forge.jenkins.logintest.LocalhostJenkinsRule before[2019-11-25T10:33:43.628Z] INFO: Waiting for Jenkins instance... (response code 503)[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Push Jenkins Master Image)Stage "Push Jenkins Master Image" skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // ansiColor[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // timestamps[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: missing workspace /data/ci/workspace/orge_ti8m-ci-2.0_main-instance_8 on srvzh-jenkinsnode-tst-005Finished: FAILURE{code}As I debug in {{workflow-durable-task-step}} I notice a strange behavior. My breakpoint is set to [DurableTaskStep.java#L386|https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/bbc10c7ef26ba70cd2e85b3b3105c12ee9ec9692/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java#L386], when it halts there, it means {{ws.isDirectory()}} } returned {{false}}. But during this break in debugger I evaluate {{ws.isDirectory()}} manually and it returns {{true}}. !image-2019-11-25
[JIRA] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title Samuel Zihlmann commented on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed I had the same problem with some feature branches, but after setting 'Branch Specifier' with 'refs/heads/feature/...' and not only 'feature/...' everything works fine now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.148793.1366035236000.6125.1574680021703%40Atlassian.JIRA.
[JIRA] (JENKINS-60251) multibranch streams don't allow lightweight checkout?
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60251 multibranch streams don't allow lightweight checkout? Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203241.1574477155000.6198.1574680080475%40Atlassian.JIRA.
[JIRA] (JENKINS-60251) multibranch streams don't allow lightweight checkout?
Title: Message Title Karl Wirth commented on JENKINS-60251 Re: multibranch streams don't allow lightweight checkout? Hi Adam Smith -Thanks for your interest in the plugin. A couple of questions Can you please send me a screenshot of the 'Branch Sources' section of your multibranch job configuration page. For a streams depot I would expect something like: Also just to double check. Have you changed the name of your depot in the above Jenkinsfile? Perforce by default comes with a 'classic' depot called 'depot' that you cannot create streams under. Streams can only be created under a depot of type 'stream'. You can check this by running 'p4 depots'. The reason I'm pointing this out is that we use different code for streams and classic depots. If the code for a streams was used against a classic depot we would sync everything. Finally can you send me the version of p4-plugin and Jenkins you are using. Thanks in advance, Karl Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203241.1574477155000.6194.1574680080287%40Atlassian.JIRA.
[JIRA] (JENKINS-60251) multibranch streams don't allow lightweight checkout?
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-60251 multibranch streams don't allow lightweight checkout? Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203241.1574477155000.6196.1574680080321%40Atlassian.JIRA.
[JIRA] (JENKINS-60244) Jenkins performance is slow while running Automation scripts .
Title: Message Title Oleg Nenashev commented on JENKINS-60244 Re: Jenkins performance is slow while running Automation scripts . Yes. It does not provide any information about the system setup and agent setup. If you are unable to collect this data on your own, consider using https://plugins.jenkins.io/support-core Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203226.1574344764000.6200.1574680740199%40Atlassian.JIRA.
[JIRA] (JENKINS-60265) Kubernetes plugin: java.net.MalformedURLException: unknown protocol
Title: Message Title davidkarlsen created an issue Jenkins / JENKINS-60265 Kubernetes plugin: java.net.MalformedURLException: unknown protocol Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-11-25 11:26 Environment: CloudBees Jenkins Enterprise 2.176.4.3-rolling Plugin version: 1.18.3 Priority: Minor Reporter: davidkarlsen When I click "test connection" from the master configuration page it works fine, but when scheduling a build I get: [Bitbucket] Build result notified java.net.MalformedURLException: unknown protocol: proxy.evry.com at java.net.URL.(URL.java:600) at java.net.URL.(URL.java:490) at java.net.URL.(URL.java:439) at io.fabric8.kubernetes.client.utils.HttpClientUtils.getProxyUrl(HttpClientUtils.java:212) at io.fabric8.kubernetes.client.utils.HttpClientUtils.createHttpClient(HttpClientUtils.java:145) at io.fabric8.kubernetes.client.utils.HttpClientUtils.createHttpClient(HttpClientUtils.java:63) at io.fabric8.kubernetes.client.BaseClient.(BaseClient.java:51) at io.fabric8.kubernetes.client.BaseClient.(BaseClient.java:43) at io.fabric8.kubernetes.client.DefaultKubernetesClient.(DefaultKubernetesClient.java:84) at org.csanchez.jenkins.plugins.kubernetes.PodTemplateUtils.parseFromYaml(PodTemplateUtils.java:517) at org.csanchez.jenkins.plugins.kubernetes.PodTemplateUtils.validateYamlContainerNames(PodTemplateUtils.java:554) at org.csanchez.jenkins.plugins.kubernetes.PodTemplateUtils.validateYamlContainerNames(PodTemplateUtils.java:544) at org.csanchez.jenkins.plugins.kubernetes.pipeline.PodTemplateStepExecution.start(PodTemplateStepEx
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59311 Re: Poor performance when using 'grep' After the latest updates I got the problem again. Besides, all my automatic build weren't restartet The list of updates:Jira 3.0.10 -> 3.0.11 Oracle Java SE Development Kit Installer 1.3->1.4 Script Security 1.67->1.68 Warnings Next Generation 7.2.0->7.2.1Jenkins v2.190.3 Lat*'s see what happens It runs quickly again after a service restart. .. So I guess, it's an issue of the update procedure or the implementation as a windows service?Which components do these belong to for a correct assignment of the job? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201861.156818559.6202.1574681640065%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Uwe Brackenhoff updated an issue Jenkins / JENKINS-60263 Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. Change By: Uwe Brackenhoff Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.6210.1574682001885%40Atlassian.JIRA.
[JIRA] (JENKINS-60266) Add a Jenkins.CONFIGURE permission to be able to configure Jenkins without ADMINISTER
Title: Message Title A. Jard created an issue Jenkins / JENKINS-60266 Add a Jenkins.CONFIGURE permission to be able to configure Jenkins without ADMINISTER Issue Type: New Feature Assignee: A. Jard Components: core Created: 2019-11-25 11:47 Priority: Minor Reporter: A. Jard I create this Jira to follow the work in progress about "Sensible permission" related to the JEP that is in draft status for now and can be found here https://github.com/jenkinsci/jep/pull/249 The main goal is to have a new permission called `Jenkins.CONFIGURE` to allow management of Jenkins. All sensible or security related items are restricted to `Jenkins.ADMINISTER`. The draft PR with this new permission implementation will be proposed soon, I will update this Jira when it's done. Add Comment
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Uwe Brackenhoff commented on JENKINS-60263 Re: Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. Thank you for your response. I saw the regex within the check-ins, but didn't realize that cases actually do matter. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.6224.1574682540111%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Uwe Brackenhoff updated an issue Jenkins / JENKINS-60263 Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. Change By: Uwe Brackenhoff Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.6226.1574682960201%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Uwe Brackenhoff edited a comment on JENKINS-60263 Re: Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. May I ask for the reason of this retriction restriction ? I just realized the [http://jenkins.url/Project/100/Build_Binary] has been working. I also see that [http://jenkins.url/Project/100/build_binary|http://jenkins.url/Project/100/Build_Binary] is not resolved so my guess is that I will loose previous result history by chaning the ID. Am I right? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.6232.1574683621721%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Uwe Brackenhoff commented on JENKINS-60263 Re: Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. May I ask for the reason of this retriction? I just realized the http://jenkins.url/Project/100/Build_Binary has been working. I also see that http://jenkins.url/Project/100/build_binary is not resolved so my guess is that I will loose previous result history by chaning the ID. Am I right? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.6230.1574683621609%40Atlassian.JIRA.
[JIRA] (JENKINS-60267) Shorthand git step doesn't handle commit hashes
Title: Message Title
Jeff MacLoue created an issue
Jenkins / JENKINS-60267
Shorthand git step doesn't handle commit hashes
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-11-25 12:09
Environment:
OS: Linux 64-bit Jenkins: 2.190.3 Git plugin: 4.0.0
Labels:
pipeline git-plugin
Priority:
Minor
Reporter:
Jeff MacLoue
Despite git step description states that "this step is shorthand for the generic SCM step", it behaves differently when specifying commit hash as a branch to checkout. Consider the following pipeline:
repo = 'https://github.com/jmacloue/mypwgen-pl.git'
branch = 'ad0f6e4'
pipeline {
agent any
stages {
stage("GitSCM") {
steps {
checkout([$class: 'GitSCM',
userRemoteConfigs: [[url: repo]],
branches: [[name: branch]],
])
}
}
stage("shorthand") {
steps {
git url: repo, branch: branch
}
}
}
}
Though the stages should be identical according to docs, the second stage fails:
[JIRA] (JENKINS-39287) Ability to select from existing credentials list at runtime
Title: Message Title Karl Wirth commented on JENKINS-39287 Re: Ability to select from existing credentials list at runtime Potential workaround - this article suggests credentials can be built on the fly: https://support.cloudbees.com/hc/en-us/articles/217708168-create-credentials-from-groovy Alternative workaround: If the slave already contains P4PORT, P4SERVER and P4TRUST, could it have a new variable created called P4_CREDENTIAL that could be used in the script? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175718.1477521864000.6237.1574683920457%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Uwe Brackenhoff edited a comment on JENKINS-60263 Re: Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. May I ask for the reason of this restriction? I just realized the [http://jenkins.url/Project/100/Build_Binary] has been working. I also see that [http://jenkins.url/Project/100/build_binary|http://jenkins.url/Project/100/Build_Binary] is not resolved so my guess is that I will loose previous result history by chaning changing the ID. Am I right? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.6241.1574684460260%40Atlassian.JIRA.
[JIRA] (JENKINS-60266) Add a Jenkins.CONFIGURE permission to be able to configure Jenkins without ADMINISTER
Title: Message Title A. Jard updated an issue Jenkins / JENKINS-60266 Add a Jenkins.CONFIGURE permission to be able to configure Jenkins without ADMINISTER Change By: A. Jard I create this Jira to follow the work in progress about "Sensible permission" related to the JEP that is in draft status for now and can be found here [https://github.com/jenkinsci/jep/pull/249]The main goal is to have a new permission called `Jenkins.CONFIGURE` to allow management of Jenkins. All sensible or security related items are restricted to `Jenkins.ADMINISTER`.The draft PR with this new permission implementation will be proposed soon, I will update this Jira when it's done. Feedback are welcome, you can also see the announcement on the dev list: https://groups.google.com/forum/#!topic/jenkinsci-dev/lThSifB8G4k Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop r
[JIRA] (JENKINS-60266) Add a Jenkins.CONFIGURE permission to be able to configure Jenkins without ADMINISTER
Title: Message Title A. Jard updated an issue Jenkins / JENKINS-60266 Add a Jenkins.CONFIGURE permission to be able to configure Jenkins without ADMINISTER Change By: A. Jard I create this Jira to follow the work in progress about "Sensible permission" related to the JEP that is in draft status for now and can be found here [https://github.com/jenkinsci/jep/pull/249]The main goal is to have a new permission called `Jenkins.CONFIGURE` to allow management of Jenkins. All sensible or security related items are restricted to `Jenkins.ADMINISTER`.The draft PR with this new permission implementation will be proposed soon, I will update this Jira when it's done.Feedback are welcome, you can also see the announcement on the dev list: is https:// groups github . google. com/ forum jenkinsci / #!topic jenkins / jenkinsci-dev pull / lThSifB8G4k 4374 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issue
[JIRA] (JENKINS-53101) Add Declarative support
Title: Message Title
red der commented on JENKINS-53101
Re: Add Declarative support
wait I was hoping environment { CREDS = credentials('id-for-an-aws-cred') } would inject environment variables named AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY for you like withCredentials does. Is that what we want? So you dont have to manually add them with string interpolation?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193097.1534521044000.6268.1574687520326%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Ulli Hafner commented on JENKINS-60263 Re: Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. Actually the restriction is there to avoid problems when users by mistake mix upper and lower case characters, this is very often a problem on servers that run on Windows. Here files A and a are treated as the same file. I'm not sure whether this is a real problem with urls in Jenkins. Is your Jenkins running on Windows? I think I can loosen that again and enable upper case characters as well. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.6270.1574687760264%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Uwe Brackenhoff commented on JENKINS-60263 Re: Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. Yes, it is running on windows. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.6272.1574687880203%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Ulli Hafner commented on JENKINS-60263 Re: Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. Ah, good too see. So when your server is running on Windows and the URL `Build_Binary` is working, but the URL `Build_Binary` not, then a restriction on lower case is not required indeed. => I will add uppercase as valid again. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.6281.1574688420110%40Atlassian.JIRA.
[JIRA] (JENKINS-56392) classic -> blue-ocean links to subfolder jobs are wrong
Title: Message Title Björn Pedersen updated an issue Jenkins / JENKINS-56392 classic -> blue-ocean links to subfolder jobs are wrong Change By: Björn Pedersen Summary: classic -> blue-ocean links from classic do not use https to subfolder jobs are wrong Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197982.1551715632000.6283.1574688780145%40Atlassian.JIRA.
[JIRA] (JENKINS-60267) Shorthand git step doesn't handle commit hashes
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60267 Shorthand git step doesn't handle commit hashes Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203255.1574683768000.6287.1574689620262%40Atlassian.JIRA.
[JIRA] (JENKINS-60267) Shorthand git step doesn't handle commit hashes
Title: Message Title Mark Waite commented on JENKINS-60267 Re: Shorthand git step doesn't handle commit hashes I'll update the documentation to further reinforce that the git step does not have all the functionality of the checkout step and that it does not have the same behaviors as the checkout step in all cases. I won't modify the behavior of the git step. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203255.1574683768000.6285.1574689620236%40Atlassian.JIRA.
[JIRA] (JENKINS-57544) statistics gatherer plugin - no audit for steps/stages in scripted pipeline
Title: Message Title Brian Gregg commented on JENKINS-57544 Re: statistics gatherer plugin - no audit for steps/stages in scripted pipeline I'm seeing the same issue with 2.0.3. Is there a workaround or any more information on this? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199452.1558253483000.6290.1574691000335%40Atlassian.JIRA.
[JIRA] (JENKINS-59455) CheckFilterTest failing on environment.txt
Title: Message Title Evaristo Gutierrez commented on JENKINS-59455 Re: CheckFilterTest failing on environment.txt Summarizing the changes proposed by Ramon Leon and myself in https://github.com/jenkinsci/support-core-plugin/pull/200: Use the first available env variable, and not path, to be sure it's available. Wait for the created agent to be online. Considerate '\0' (NUL character) as a character that appears to mark the end of a line, and so it must not make files containing it to be considered as binary files. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202048.1568948997000.6292.1574691540373%40Atlassian.JIRA.
[JIRA] (JENKINS-60268) Allow "Atlassian Jira Software Cloud Plugin" to be stateful
Title: Message Title Fábio Beck created an issue Jenkins / JENKINS-60268 Allow "Atlassian Jira Software Cloud Plugin" to be stateful Issue Type: Bug Assignee: Rafal Myslek Attachments: Jenkinsfile Components: atlassian-jira-software-cloud-plugin Created: 2019-11-25 14:21 Priority: Minor Reporter: Fábio Beck Creating this on behalf of the customers: vradhakrish...@foundationmedicine.com jh...@foundationmedicine.com sagra...@foundationmedicine.com Could you please get in touch with these customers to let them know you receive their feature request? They also informed me that they couldn't create an account on your service desk. Description: I have attached a sample Jenkins file and the workflow we follow is explained below. Please let me know if you have any questions. It will be a great help if you could include this feature as this is going to help us immensely. Thanks for all your help. "Developer1" creates Git Feature Branch1 (FB1) is associated with JIRA-1234. Commit message includes JIRA-1234 After creating PR against FB1, get approved and then merged to master That triggers a Jenkins build which builds our application and deploys to our DEV environment. Let's call this build as Build1 "Developer2" follows the same process for Git Feature Branch2 (FB2) associated with JIRA-6789. Commit message includes JIRA-6789. PR->approval->merge to master-> triggers build (Build2)->Deploys to DEV environment. Keep in mind that FB2 includes the code for FB1 as well. Via JenkinsFile,
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Ulli Hafner started work on JENKINS-60263 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.6298.1574691964158%40Atlassian.JIRA.
[JIRA] (JENKINS-60263) Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not.
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60263 Warnings-NG 7.2.1: java.lang.IllegalArgumentException: An ID must be a valid URL, but 'Build_Binary' is not. Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/276 Labels: plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203250.1574676933000.6300.1574691965199%40Atlassian.JIRA.
[JIRA] (JENKINS-60269) There is a case sensitive search in extensible choice parameter.
Title: Message Title Kaviraj Palanisamy created an issue Jenkins / JENKINS-60269 There is a case sensitive search in extensible choice parameter. Issue Type: Bug Assignee: Unassigned Components: extensible-choice-parameter-plugin Created: 2019-11-25 14:26 Priority: Minor Reporter: Kaviraj Palanisamy While searching extensible choice paramter, it should be in case sensitive search Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60269) There is a case sensitive search in extensible choice parameter.
Title: Message Title Kaviraj Palanisamy updated an issue Jenkins / JENKINS-60269 There is a case sensitive search in extensible choice parameter. Change By: Kaviraj Palanisamy While searching extensible choice paramter, it should be in is case sensitive search . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203258.1574691999000.6302.1574692080691%40Atlassian.JIRA.
[JIRA] (JENKINS-60246) The issue is very pressing
Title: Message Title Oleg Nenashev updated JENKINS-60246 Please use another Jira service for practice. https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue Jenkins / JENKINS-60246 The issue is very pressing Change By: Oleg Nenashev Status: In Progress Fixed but Unreleased Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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...@googlegro
[JIRA] (JENKINS-39287) Ability to select from existing credentials list at runtime
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-39287 Ability to select from existing credentials list at runtime Change By: Karl Wirth Assignee: Paul Allen Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175718.1477521864000.6308.1574692200270%40Atlassian.JIRA.
[JIRA] (JENKINS-60269) There is a case sensitive search in extensible choice parameter.
Title: Message Title Kaviraj Palanisamy updated an issue Jenkins / JENKINS-60269 There is a case sensitive search in extensible choice parameter. Change By: Kaviraj Palanisamy Attachment: Screen Shot 2019-11-25 at 8.00.22 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203258.1574691999000.6311.1574692260069%40Atlassian.JIRA.
[JIRA] (JENKINS-60269) There is a case sensitive search in extensible choice parameter.
Title: Message Title Kaviraj Palanisamy updated an issue Jenkins / JENKINS-60269 There is a case sensitive search in extensible choice parameter. Change By: Kaviraj Palanisamy Attachment: Screen Shot 2019-11-25 at 8.01.03 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203258.1574691999000.6312.1574692380170%40Atlassian.JIRA.
[JIRA] (JENKINS-56392) classic -> blue-ocean links to subfolder jobs are wrong
Title: Message Title Björn Pedersen commented on JENKINS-56392 Re: classic -> blue-ocean links to subfolder jobs are wrong https://github.com/jenkinsci/blueocean-plugin/pull/2042 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197982.1551715632000.6314.1574693701011%40Atlassian.JIRA.
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Bradley Wangia updated JENKINS-59752 Jenkins / JENKINS-59752 Add support for ephemeral OS disk Change By: Bradley Wangia Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202475.1570808392000.6321.1574694363221%40Atlassian.JIRA.
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Bradley Wangia started work on JENKINS-59752 Change By: Bradley Wangia Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202475.1570808392000.6317.1574694363068%40Atlassian.JIRA.
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Bradley Wangia commented on JENKINS-59752 Re: Add support for ephemeral OS disk Jie Shen I saw you approved/merged my PR into dev ... Is there a release process/schedule? Anything I need to do to this ticket to get it into the next release? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202475.1570808392000.6325.1574694540272%40Atlassian.JIRA.
[JIRA] (JENKINS-60270) Warnings-NG: recordIssue attribute 'name' probalby ignored
Title: Message Title Uwe Brackenhoff created an issue Jenkins / JENKINS-60270 Warnings-NG: recordIssue attribute 'name' probalby ignored Issue Type: Bug Assignee: Ulli Hafner Attachments: active.txt, Untitled.png, Untitled2.png Components: warnings-ng-plugin Created: 2019-11-25 16:08 Environment: Jenkins ver. 2.190.3; list of plugins attached; java.vendor AdoptOpenJDK; java.runtime.version 11.0.5+10; sun.management.compiler HotSpot 64-Bit Tiered Compilers; OS Win7x64pro Priority: Minor Reporter: Uwe Brackenhoff Hallo, The documentation of the attribute 'name' shows: name (optional) You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used. But as you can see within the attached Untitled.png, this is not working. The Jenkins script used is: recordIssues( id: 'Build_Binary', name: 'Build Binary', sourceCodeEncoding: 'UTF-8', enabledForFailure: true, aggregatingResults: true, tools: [ groovyScript( id: 'Build_Binary_SubProj1', name: 'Build Binary SubProj1', parserId: 'myParser', pattern:'Outputs SubProj1Build.log', reportEncoding:'UTF-8' ), groovyScript( id: 'Build_Binary_SubProj2', name: 'Build Binary SubProj2', parserId: 'myParser', pattern:'Outputs SubProj2Build.log', reportEncoding:'UTF-8' ), groovyScript( id: 'Build_Binary_SubProj3', name: 'Build Binary SubProj3', parserId: 'myParser', pattern:'Outputs SubProj3Build.log', reportEncoding:'UTF-8' ), groovyScript( id: 'Build_Binary_SubProj4', name: 'Bu
[JIRA] (JENKINS-60115) NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0
Title: Message Title Liam Newman commented on JENKINS-60115 Re: NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0 Fixed by https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/363 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202962.1573259182000.6343.1574699340821%40Atlassian.JIRA.
[JIRA] (JENKINS-60115) NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0
Title: Message Title Liam Newman updated JENKINS-60115 Jenkins / JENKINS-60115 NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0 Change By: Liam Newman Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202962.1573259182000.6341.1574699340773%40Atlassian.JIRA.
[JIRA] (JENKINS-46819) combine plain text and html options into one
Title: Message Title Alex Earl closed an issue as Incomplete Jenkins / JENKINS-46819 combine plain text and html options into one Change By: Alex Earl Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185172.1505229128000.6348.1574700780660%40Atlassian.JIRA.
[JIRA] (JENKINS-43403) Pipeline withEnv changes not observable in email-ext groovy template
Title: Message Title Alex Earl closed an issue as Incomplete Jenkins / JENKINS-43403 Pipeline withEnv changes not observable in email-ext groovy template Change By: Alex Earl Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180646.1491512064000.6360.1574700842040%40Atlassian.JIRA.
[JIRA] (JENKINS-60220) Multibranch pipeline with Helix Swarm source doesn't sync to latest
Title: Message Title Paul Allen commented on JENKINS-60220 Re: Multibranch pipeline with Helix Swarm source doesn't sync to latest Hi Guys, just back from vacation so may need a bit of time to get up speed on this issue... Using 'head' (the latest change on that branch) might be an alternative, but there could be side effects if the 'head' is newer than the shelf/review. The P4 plugin may need to perform a resolve step (forcing the accept of the shelve's content) - I seem to remember writing something like this, but can't remember if it was released or in a dev branch. I'll take a look and refresh myself on the Swarm review part of the code. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203193.1574213884000.6377.1574701020205%40Atlassian.JIRA.
[JIRA] (JENKINS-60271) Allow selection of field(s) for Issue selector display
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-60271 Allow selection of field(s) for Issue selector display Issue Type: New Feature Assignee: Unassigned Components: jira-plugin Created: 2019-11-25 17:30 Priority: Minor Reporter: Mark Bidewell Sometimes it would be useful to use a different Jira issue field or fields and the title in the issue selector dropdown. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60220) Multibranch pipeline with Helix Swarm source doesn't sync to latest
Title: Message Title William Brode commented on JENKINS-60220 Re: Multibranch pipeline with Helix Swarm source doesn't sync to latest Good point on needing to resolve. I hadn't considered how that makes things more complicated. But as you mentioned the best way to handle it is probably to just take the shelved content (as opposed to trying to do some safe resolve or something). I suppose another option would be to fail? Return an error saying a resolve is required so the person can resolve it locally and change the files in the review. That may actually be better - since they will have to resolve before submitting anyways. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203193.1574213884000.6396.1574703780316%40Atlassian.JIRA.
[JIRA] (JENKINS-58034) Pipeline job is being shown on two executors (master and node) while inside p4step
Title: Message Title Karl Wirth commented on JENKINS-58034 Re: Pipeline job is being shown on two executors (master and node) while inside p4step I hit a brick wall with this one. Cannot see any activity on the Perforce side and unable to find a generic tracing that tells me what a node (slave or master) is up to. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200053.1560720825000.6400.1574704140128%40Atlassian.JIRA.
[JIRA] (JENKINS-60241) Dynamic messages in build failure causes
Title: Message Title
Stephen Humphries commented on JENKINS-60241
Re: Dynamic messages in build failure causes
If you haven't seen it, the "${1,1}" placeholder syntax might be helpful to you: https://wiki.jenkins.io/display/JENKINS/Build+Failure+Analyzer#BuildFailureAnalyzer-Placeholdersindescription .
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203223.1574339787000.6404.1574704200185%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title Karl Wirth commented on JENKINS-60213 Re: P4 environment variables non-reentrant After discussing with the developers I tried the nightly with a different variable fix but same behavior: Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.6406.1574704260394%40Atlassian.JIRA.
[JIRA] (JENKINS-59698) file crippled during deploy
Title: Message Title Nitin Biradar commented on JENKINS-59698 Re: file crippled during deploy The changes from this PR (mostly pulled from Azure App Service Plugin) has helped fix the issue - https://github.com/jenkinsci/azure-function-plugin/pull/17 . Jie Shen - Could you please look at this ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202398.1570524247000.6409.1574704260497%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title
Karl Wirth edited a comment on JENKINS-60213
Re: P4 environment variables non-reentrant
After discussing with the developers I tried the nightly with a different variable fix but same behavior: {code:java}#30[JENKINS-60213-ConcurrentVariables] $ /bin/bash /tmp/jenkins6285754148517933441.sh==WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariablesP4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-0EXECUTOR NUMBER: 0==#31[JENKINS-60213-ConcurrentVariables] $ /bin/bash /tmp/jenkins6285754148517933441.sh==WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariablesP4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-0EXECUTOR NUMBER: 0==#32[JENKINS-60213-ConcurrentVariables] $ /bin/bash /tmp/jenkins6285754148517933441.sh==WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariablesP4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-0EXECUTOR NUMBER: 0=={code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issue
[JIRA] (JENKINS-60251) multibranch streams don't allow lightweight checkout?
Title: Message Title Adam Smith commented on JENKINS-60251 Re: multibranch streams don't allow lightweight checkout? Good morning Karl, I apologize for taking your time on this. I discovered my own misconfiguration late this same night and planned to update the ticket this morning. You beat me to the punch! Under the "Advanced" dropdown, I selected "Preview Only" as the populate option which produced my desired behavior. I'll close this now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203241.1574477155000.6413.1574705345068%40Atlassian.JIRA.
[JIRA] (JENKINS-60251) multibranch streams don't allow lightweight checkout?
Title: Message Title Adam Smith closed an issue as Not A Defect Jenkins / JENKINS-60251 multibranch streams don't allow lightweight checkout? Change By: Adam Smith Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203241.1574477155000.6415.1574705345104%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title James Bateman commented on JENKINS-60213 Re: P4 environment variables non-reentrant Looks like your copy-and-paste went wrong, all the example in your last message are exactly the same Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.6417.1574705580239%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title James Bateman edited a comment on JENKINS-60213 Re: P4 environment variables non-reentrant Looks like your copy-and-paste went wrong, all the example in your last [ message |https://issues are exactly the same (basically there is no way that each job can use the same bash script – i . jenkins-ci e . org * / browse tmp / JENKINS-60213?focusedCommentId=380489&page=com jenkins6285754148517933441 . atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-380489] are exactly the same sh*) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.6419.1574705880128%40Atlassian.JIRA.
[JIRA] (JENKINS-59350) Remove mission-control-view tests from ATH
Title: Message Title Andrey Shevtsov assigned an issue to Andrey Shevtsov Jenkins / JENKINS-59350 Remove mission-control-view tests from ATH Change By: Andrey Shevtsov Assignee: Andrey Shevtsov Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201901.1568377932000.6422.1574706660288%40Atlassian.JIRA.
[JIRA] (JENKINS-60272) Stuck on Installing Plugins/Upgrades
Title: Message Title Rares Vernica created an issue Jenkins / JENKINS-60272 Stuck on Installing Plugins/Upgrades Issue Type: Bug Assignee: Unassigned Components: update-sites-manager-plugin Created: 2019-11-25 18:37 Priority: Minor Reporter: Rares Vernica See bellow for what I did. It has been like this for more that 10 minutes. Installing Plugins/Upgrades Preparation Checking internet connectivity Checking update center connectivity Success LDAP Downloaded Successfully. Will be activated during the next boot Pipeline: Stage Tags Metadata Downloaded Successfully. Will be activated during the next boot
[JIRA] (JENKINS-60273) Build Now link on the Edit or Console Output page
Title: Message Title Rares Vernica created an issue Jenkins / JENKINS-60273 Build Now link on the Edit or Console Output page Issue Type: Improvement Assignee: Unassigned Components: _unsorted Created: 2019-11-25 19:14 Priority: Minor Reporter: Rares Vernica During the job creation process, I spend a lot of time tweaking the Build > Execute shell steps. I make small edits and then I run the job to see if it worked. I end up needing three tabs open: Edit job Trigger Build Now Console output It would be nice to have a Build Now link on the job edit page or on the console output page. This way I can get away with two tabs. Add Comment
[JIRA] (JENKINS-49202) ChangeLogSet.Entry does not expose getComment to get entire commit message
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-49202 ChangeLogSet.Entry does not expose getComment to get entire commit message Change By: Jesse Glick Labels: newbie-friendly stalled-pr Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188039.1516983734000.6427.1574709420424%40Atlassian.JIRA.
[JIRA] (JENKINS-41604) Unique exception for input step abort
Title: Message Title Devin Nusbaum commented on JENKINS-41604 Re: Unique exception for input step abort Given JENKINS-41272 went with the approach of exposing the causes as JSON to avoid having to whitelist all causes as well, I think it would make sense to take the same approach here. If anyone still wants to work on it, I would file a new PR to add new methods to FlowInterruptedException similar to the approach in https://github.com/jenkinsci/workflow-support-plugin/pull/78. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178423.148589741.6440.1574710743269%40Atlassian.JIRA.
[JIRA] (JENKINS-41604) Unique exception for input step abort
Title: Message Title Devin Nusbaum updated JENKINS-41604 Jenkins / JENKINS-41604 Unique exception for input step abort Change By: Devin Nusbaum Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178423.148589741.6450.1574710743450%40Atlassian.JIRA.
[JIRA] (JENKINS-41604) Unique exception for input step abort
Title: Message Title Devin Nusbaum stopped work on JENKINS-41604 Change By: Devin Nusbaum Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178423.148589741.6460.1574710744148%40Atlassian.JIRA.
[JIRA] (JENKINS-41604) Unique exception for input step abort
Title: Message Title Jesse Glick commented on JENKINS-41604 Re: Unique exception for input step abort exposing the causes as JSON to avoid having to whitelist all causes as well That is also in line with what I proposed as an api step. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178423.148589741.6462.1574711880380%40Atlassian.JIRA.
[JIRA] (JENKINS-60258) NullPointerException using EC2-plugin version 1.46.1
Title: Message Title
ovi craciun updated an issue
Jenkins / JENKINS-60258
NullPointerException using EC2-plugin version 1.46.1
Change By:
ovi craciun
Jenkins log shows this error when it is trying to provision a windows jenkins slave:{code:java}SlaveTemplate{ami='ami-0782a9361d328f5fb', labels='windows'}. Attempting to provision slave needed by excess workload of 1 unitsNov 24, 2019 1:10:00 PM SEVERE hudson.triggers.SafeTimerTask runTimer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@462f29b7 failedjava.lang.NullPointerException at hudson.plugins.ec2.EC2SpotSlave.getSpotRequest(EC2SpotSlave.java:123) at hudson.plugins.ec2.EC2Cloud.countCurrentEC2Slaves(EC2Cloud.java:482) at hudson.plugins.ec2.EC2Cloud.getPossibleNewSlavesCount(EC2Cloud.java:552) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:570) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:615) at hudson.plugins.ec2.NoDelayProvisionerStrategy.apply(NoDelayProvisionerStrategy.java:47) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:332) at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:63) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:821) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){code}I tried changing various configuration settings but did not manage to get around this error.Any clues what can I do?thank you *Later edit:*After restarting jenkins now, in the logs I can see this error which seems very much related:{code:java}Started EC2 alive slaves monitorNov 25, 2019 7:55:16 PM SEVERE hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtExceptionA thread (EC2 alive slaves monitor thread/202) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.NullPointerException at hudson.plugins.ec2.EC2SpotSlave.getSpotRequest(EC2SpotSlave.java:123) at hudson.plugins.ec2.EC2SpotSlave.isSpotRequestDead(EC2SpotSlave.java:144) at hudson.plugins.ec2.EC2SpotSlave.isAlive(EC2SpotSlave.java:60) at hudson.plugins.ec2.EC2SlaveMonitor.removeDeadNodes(EC2SlaveMonitor.java:49) at hudson.plugins.ec2.EC2SlaveMonitor.execute(EC2SlaveMonitor.java:40) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101) at java.lang.Thread.run(Unknown Source){code}
[JIRA] (JENKINS-59448) Distinct jenkins userids for same AD user
Title: Message Title William Brode commented on JENKINS-59448 Re: Distinct jenkins userids for same AD user Félix Belzunce Arcos any luck on this one? I think this issue causes the Matrix Authorization plugin not to work as intended. If I add permissions for a specific user "domainName\userName" - but the user then logs in using "userName@domainName" they won't have the permissions I gave them. I think if we fix this issue then hopefully both logins would use the same user that I gave permissions to. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202033.1568905412000.6476.1574713140263%40Atlassian.JIRA.
[JIRA] (JENKINS-28043) Reload configs of all jobs in folder
Title: Message Title John Beckerle commented on JENKINS-28043 Re: Reload configs of all jobs in folder Issue still present: core version 2.190.2 Folder plugin: org.jenkins-ci.plugins:cloudbees-folder:6.9 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162242.1429721391000.6478.1574713800391%40Atlassian.JIRA.
[JIRA] (JENKINS-56553) Make ProxyConfiguration compatible with JCasC
Title: Message Title Tim Jacomb updated JENKINS-56553 Jenkins / JENKINS-56553 Make ProxyConfiguration compatible with JCasC Change By: Tim Jacomb Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198167.1552551032000.6492.1574714100688%40Atlassian.JIRA.
[JIRA] (JENKINS-56553) Make ProxyConfiguration compatible with JCasC
Title: Message Title Tim Jacomb closed an issue as Fixed Jenkins / JENKINS-56553 Make ProxyConfiguration compatible with JCasC Change By: Tim Jacomb Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198167.1552551032000.6493.1574714100729%40Atlassian.JIRA.
[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title Valentin Delaye updated an issue Jenkins / JENKINS-60274 Unable to use plugin with private Bitbucket repositories Change By: Valentin Delaye Hi!We are trying to use this plugin, but we have issue to configure it with private repositories (starting with ~).It seems at some point the plugin "replace" the ~username by the full display name. Which obviously doesn't work.To reproduce- Configure a standard pipeline with a private repo (screenshot config_work.png). Configuration is validated- Save the pipelineThe pipeline cannot build and when we want to configure it again it seems that the "Display" name of the user was replaced on the configuration (build_status.png) and after_save.pngWe don't have this problem with standard Bitbucket project .Thanks.Valentin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title Valentin Delaye created an issue Jenkins / JENKINS-60274 Unable to use plugin with private Bitbucket repositories Issue Type: Bug Assignee: Kristy Hughes Attachments: after_save.png, build_status.png, config_work.png Components: atlassian-bitbucket-server-integration-plugin Created: 2019-11-25 20:50 Environment: jenkins:2.190.1 atlassian-bitbucket-server-integration:1.0.3 bitbucket-server:5.12 Priority: Major Reporter: Valentin Delaye Hi! We are trying to use this plugin, but we have issue to configure it with private repositories (starting with ~). It seems at some point the plugin "replace" the ~username by the full display name. Which obviously doesn't work. To reproduce Configure a standard pipeline with a private repo (screenshot config_work.png). Configuration is validated Save the pipeline The pipeline cannot build and when we want to configure it again it seems that the "Display" name of the user was replaced on the configuration (build_status.png) and after_save.png We don't have this problem with standard Bitbucket project
[JIRA] (JENKINS-59665) Rework sorting for Uninstall columns of Installed in Plugin Manager
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59665 Rework sorting for Uninstall columns of Installed in Plugin Manager Change By: Oleg Nenashev Labels: lts-candidate newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.6512.1574716680848%40Atlassian.JIRA.
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59631 Adding different colors to history table and data filter Change By: Oleg Nenashev Labels: newbie-friendly user-experience Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202313.1570043107000.6520.1574716741108%40Atlassian.JIRA.
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-59631 Adding different colors to history table and data filter Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Released As: Jenkins 2.105 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202313.1570043107000.6525.1574716741203%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for Uninstall columns of Installed in Plugin Manager
Title: Message Title Oleg Nenashev updated JENKINS-59665 Jenkins / JENKINS-59665 Rework sorting for Uninstall columns of Installed in Plugin Manager Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.105 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.6504.1574716680724%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for Uninstall columns of Installed in Plugin Manager
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59665 Rework sorting for Uninstall columns of Installed in Plugin Manager Change By: Oleg Nenashev Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.6508.1574716680791%40Atlassian.JIRA.
[JIRA] (JENKINS-59508) sidebar link names are not truncated causing funky rendering
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59508 sidebar link names are not truncated causing funky rendering Change By: Oleg Nenashev Labels: UX lts-candidate newbie-friendly ui Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202130.1569325102000.6537.1574716800658%40Atlassian.JIRA.
[JIRA] (JENKINS-6722) Show agent error status on Dashboard
Title: Message Title Oleg Nenashev resolved as Fixed It was released in Jenkins 2.205. Thanks Ilia Zasimov! Jenkins / JENKINS-6722 Show agent error status on Dashboard Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Released As: Jenkins 2.205 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribe
[JIRA] (JENKINS-6722) Show agent error status on Dashboard
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-6722 Show agent error status on Dashboard Change By: Oleg Nenashev Summary: Show slave agent error status on Dashboard Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136817.1276001051000.6528.1574716741254%40Atlassian.JIRA.
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-59631 Adding different colors to history table and data filter Change By: Oleg Nenashev Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202313.1570043107000.6516.1574716740984%40Atlassian.JIRA.
[JIRA] (JENKINS-59508) sidebar link names are not truncated causing funky rendering
Title: Message Title Oleg Nenashev resolved as Fixed It was released in Jenkins 2.205. It is marked as rfe there, but still looks lone a potential LTS candidate Jenkins / JENKINS-59508 sidebar link names are not truncated causing funky rendering Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Released As: Jenkins 2.205 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56553) Make ProxyConfiguration compatible with JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56553 Make ProxyConfiguration compatible with JCasC Change By: Oleg Nenashev Released As: Jenkins 2.205 (core fix), 1.24 (JCasC workaround) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198167.1552551032000.6547.1574716860677%40Atlassian.JIRA.
