[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem (described in WEBSITE-726, see [ ^ link title|https://issues. jenkins -ci . org/secure/attachment/50348/50348_jenkins. log]).However, in my case the container process was not detected at all by {{docker top}}.
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.188136.1517348633000.3188.1582185481904%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem (described in WEBSITE-726, see [ link title|https://issues. ^ jenkins -ci . org/secure/attachment/50348/50348_jenkins. log]).However, in my case the container process was not detected at all by {{docker top}}.
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.188136.1517348633000.3190.1582185481925%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem (described in WEBSITE-726, see [ title ^ jenkins.log |https://issues.jenkins-ci.org/secure/attachment/50348/50348_jenkins.log ]).However, in my case the container process was not detected at all by {{docker top}}.
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.188136.1517348633000.3119.1582185420811%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem (described in WEBSITE-726, see [ title jenkins.log| [^ https://issues. jenkins -ci . org/secure/attachment/50348/50348_jenkins. log] ] ).However, in my case the container process was not detected at all by {{docker top}}.
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.188136.1517348633000.3117.1582185361324%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem (described in WEBSITE-726, see https://issues [jenkins . log|[^ jenkins -ci . org/secure/attachment/50348/50348_jenkins. log ]] ).However, in my case the container process was not detected at all by {{docker top}}.
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.188136.1517348633000.3047.1582185300942%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem (described in WEBSITE-726, see [jenkins https://issues . log|[^ jenkins -ci . org/secure/attachment/50348/50348_jenkins. log ] ) ,] . However, in my case the container process was not detected at all by {{docker top}}.
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.188136.1517348633000.3011.1582185240777%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Gan Ainm commented on JENKINS-49278 Re: cat command in docker agents not detected correctly I encountered a similar problem (described in WEBSITE-726, see [jenkins.log|[^jenkins.log]),] However, in my case the container process was not detected at all by docker top. 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.188136.1517348633000.2975.1582185180802%40Atlassian.JIRA.
[JIRA] (JENKINS-38276) Increase size of text area for pipeline script code
Title: Message Title
Christian Höltje commented on JENKINS-38276
Re: Increase size of text area for pipeline script code
Even better: The ui-resizable-handle actually works! This CSS makes it available (with horrible colors!):
.ui-resizable-handle {
position: absolute;
bottom: 0;
background-color: #1f7313;
width: 100%;
height: 10px;
cursor: row-resize;
opacity: 0.1;
}
.ui-resizable-handle:hover {
opacity: 0.6;
}
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.174439.1474032648000.2939.1582180320798%40Atlassian.JIRA.
[JIRA] (JENKINS-54057) [JEP-302] Implement evergreen Data auto-rollback using the snapshotting system
Title: Message Title Brad Herring started work on JENKINS-54057 Change By: Brad Herring 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.194674.1539374326000.2937.1582177080277%40Atlassian.JIRA.
[JIRA] (JENKINS-61157) Jenkins automatically set entityId as https://jenkins.company.com/securityRealm/finishLogin
Title: Message Title Wai Loon Tan updated an issue Jenkins / JENKINS-61157 Jenkins automatically set entityId as https://jenkins.company.com/securityRealm/finishLogin Change By: Wai Loon Tan Environment: saml-plugin 1.1.5 jenkins 2.190.1 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.204687.1582176654000.2935.1582176720151%40Atlassian.JIRA.
[JIRA] (JENKINS-61157) Jenkins automatically set entityId as https://jenkins.company.com/securityRealm/finishLogin
Title: Message Title Wai Loon Tan created an issue Jenkins / JENKINS-61157 Jenkins automatically set entityId as https://jenkins.company.com/securityRealm/finishLogin Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2020-02-20 05:30 Environment: saml-plugin 1.1.5 Labels: SAML2 plugin 2.190.1 Priority: Minor Reporter: Wai Loon Tan I am configuring SAML2 plugin to connect to Azure Active directory. In Azure active directory, entity id is created as "jenkins-test". But when try to logon using SAML, it return this error 1) Application with identifier 'https://jenkins.company.com/securityRealm/finishLogin' was not found in the directory 'xxx'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant. 2) Upon checking saml-idp-metadata.xml, the entityId is set as "https://jenkins.company.com/securityRealm/finishLogin". 3) Nex step, editing saml-idp-metadata.xml to jenkins-test, retry the logon, same error appear, checking back saml-idp-metadata.xml, changes is reverted back to "https://jenkins.company.com/securityRealm/finishLogin". How do we set the plugin to look for "jenkins-test" as entityId instead ?
[JIRA] (JENKINS-38276) Increase size of text area for pipeline script code
Title: Message Title
Christian Höltje commented on JENKINS-38276
Re: Increase size of text area for pipeline script code
This CSS fixes it. The link to the pipeline syntax can get messy, but better than not having resize.
.ace_editor {
resize:vertical; overflow:auto !important;
}
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.174439.1474032648000.2899.1582176300918%40Atlassian.JIRA.
[JIRA] (JENKINS-61106) Load runner scenario file is getting deleted once i start executing the JOB and also Job is failing.
Title: Message Title tanmoy roy commented on JENKINS-61106 Re: Load runner scenario file is getting deleted once i start executing the JOB and also Job is failing. Hello Team, Anu further updates on this issue?? 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.204618.1581918604000.2896.1582174270207%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Pavel Zaikin commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error sreepadh chitti I think it releated to this comment as mentioned: https://issues.jenkins-ci.org/browse/JENKINS-58987?focusedCommentId=383071&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-383071 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.194307.1537972591000.2886.1582172880388%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title
Hoan Mac edited a comment on JENKINS-53794
Re: jira-trigger-plugin fails to trigger job and throws error
Also seeing the same issue: {noformat}Feb 19, 2020 9:24:19 PM WARNING org.eclipse.jetty.server.handler.ContextHandler$Context logError while org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487) at {noformat}
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.194307.1537972591000.2875.1582169940359%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title
Hoan Mac edited a comment on JENKINS-53794
Re: jira-trigger-plugin fails to trigger job and throws error
Also seeing the same issue: {noformat}Feb 19, 2020 9:24:19 PM WARNING org.eclipse.jetty.server.handler.ContextHandler$Context logError while serving https://jenkins-devops.pblbde.com/jira-trigger-webhook-receiver/ org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487) at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) at com.atlassian.jira.rest.client.internal.json.UserJsonParser.parse(UserJsonParser.java:34) at com.atlassian.jira.rest.client.internal.json.UserJsonParser.parse(UserJsonParser.java:31) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.getOptionalNestedField(IssueJsonParser.java:300) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:235) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookChangelogEventJsonParser.parse(WebhookChangelogEventJsonParser.groovy:35) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookChangelogEventJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.processEvent(JiraWebhook.groovy:63) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook$processEvent.callCurrent(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.doIndex(JiraWebhook.groovy:51) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.IndexDispatcher.dispatch(IndexDispatcher.java:27) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:456) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFil
[JIRA] (JENKINS-36720) Investigate/cleanup medium-severity FindBugs issues in the Jenkins core
Title: Message Title Raihaan Shouhell commented on JENKINS-36720 Re: Investigate/cleanup medium-severity FindBugs issues in the Jenkins core Probably due to findsecbugs we are at [java] Warnings generated: 591 right 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.172755.1468600777000.2859.1582169820163%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Hoan Mac commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error Also seeing the same issue: Feb 19, 2020 9:24:19 PM WARNING org.eclipse.jetty.server.handler.ContextHandler$Context logError while serving https://jenkins-devops.pblbde.com/jira-trigger-webhook-receiver/ org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487) at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) at com.atlassian.jira.rest.client.internal.json.UserJsonParser.parse(UserJsonParser.java:34) at com.atlassian.jira.rest.client.internal.json.UserJsonParser.parse(UserJsonParser.java:31) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.getOptionalNestedField(IssueJsonParser.java:300) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:235) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookChangelogEventJsonParser.parse(WebhookChangelogEventJsonParser.groovy:35) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookChangelogEventJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.processEvent(JiraWebhook.groovy:63) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook$processEvent.callCurrent(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.doIndex(JiraWebhook.groovy:51) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.IndexDispatcher.dispatch(IndexDispatcher.java:27) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:456) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins
[JIRA] (JENKINS-59804) Support Multibranch Pipelines
Title: Message Title Daniel Kjellin commented on JENKINS-59804 Re: Support Multibranch Pipelines Will be part of upcoming release 1.0.5 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.202534.1571228736000.2845.1582169640929%40Atlassian.JIRA.
[JIRA] (JENKINS-59804) Support Multibranch Pipelines
Title: Message Title Daniel Kjellin updated JENKINS-59804 Jenkins / JENKINS-59804 Support Multibranch Pipelines Change By: Daniel Kjellin 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.202534.1571228736000.2823.1582169581011%40Atlassian.JIRA.
[JIRA] (JENKINS-59804) Support Multibranch Pipelines
Title: Message Title Daniel Kjellin assigned an issue to Daniel Kjellin Jenkins / JENKINS-59804 Support Multibranch Pipelines Change By: Daniel Kjellin Assignee: Daniel Kjellin 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.202534.1571228736000.2811.1582169520529%40Atlassian.JIRA.
[JIRA] (JENKINS-60956) Build statuses not displaying for multiple jobs
Title: Message Title Justin Thomas updated JENKINS-60956 Jenkins / JENKINS-60956 Build statuses not displaying for multiple jobs Change By: Justin Thomas 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.204416.158077623.2809.1582166100227%40Atlassian.JIRA.
[JIRA] (JENKINS-59550) Show build queue for each particular node
Title: Message Title
Ian Williams commented on JENKINS-59550
Re: Show build queue for each particular node
How would that work if you have a pool of nodes all sharing the same label, so the job could end up on whatever node had the next free executor? The list of nodes is already long enough for us, I can't expect to see a queue for each of them and or queues can be rather big too. Where would you expect to see that? Would you only expect to see that where a label is exclusive to a node on that node page (${JENKINS_URL}/computer/node/)? That could be misleading as a job w/no label would take priority if ahead of the queue to a tied 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.202181.1569508123000.2806.1582165680174%40Atlassian.JIRA.
[JIRA] (JENKINS-61156) Regression: P4 Plugin 1.10.10 trigger doesn't run jobs
Title: Message Title William Brode commented on JENKINS-61156 Re: Regression: P4 Plugin 1.10.10 trigger doesn't run jobs We are on Jenkins 2.204.2 and P4 plugin 1.10.9 and its still working for us. So might just be 1.10.10. I'll try upgrading next week and see if it breaks on 1.10.10 for us. 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.204686.158215634.2803.1582160700274%40Atlassian.JIRA.
[JIRA] (JENKINS-59550) Show build queue for each particular node
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59550 Show build queue for each particular node Change By: Mark Waite Priority: Blocker Minor 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.202181.1569508123000.2797.1582156860696%40Atlassian.JIRA.
[JIRA] (JENKINS-59550) Show build queue for each particular node
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59550 Show build queue for each particular node Change By: Mark Waite Component/s: core Component/s: _unsorted 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.202181.1569508123000.2793.1582156860622%40Atlassian.JIRA.
[JIRA] (JENKINS-57625) I want to Perform Database operations through jenkins pipeline. Operations include CRUD operations
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-57625 I want to Perform Database operations through jenkins pipeline. Operations include CRUD operations Change By: Mark Waite 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.199554.1558591065000.2787.1582156800494%40Atlassian.JIRA.
[JIRA] (JENKINS-61156) Regression: P4 Plugin 1.10.10 trigger doesn't run jobs
Title: Message Title Tom Cramer commented on JENKINS-61156 Re: Regression: P4 Plugin 1.10.10 trigger doesn't run jobs Rough guess in the dark, maybe this change is responsible? https://github.com/jenkinsci/p4-plugin/commit/e28412ef5075755c17e96c8172adfd5a2b56905c 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.204686.158215634.2788.1582156800507%40Atlassian.JIRA.
[JIRA] (JENKINS-57255) Access denied code 128
Title: Message Title Mark Waite closed an issue as Fixed The Jenkins issue tracker is not a question and answer site. Please use the mailing lists and the chat channels for questions. Jenkins / JENKINS-57255 Access denied code 128 Change By: Mark Waite Status: Open Closed 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
[JIRA] (JENKINS-58186) Jenkins Matser Slave builds(Linux to Linux) are getting stuck after few successful builds
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-58186 Jenkins Matser Slave builds(Linux to Linux) are getting stuck after few successful builds Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce 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.200240.1561467905000.2784.1582156740230%40Atlassian.JIRA.
[JIRA] (JENKINS-2716) Authenticating via container should take roles into account
Title: Message Title Mark Waite stopped work on JENKINS-2716 Change By: Mark Waite 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.132789.1229074397000.2782.1582156680159%40Atlassian.JIRA.
[JIRA] (JENKINS-22662) A job triggered multiple times displayed incorrectly
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-22662 A job triggered multiple times displayed incorrectly Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce 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.154472.1397745675000.2780.1582156620259%40Atlassian.JIRA.
[JIRA] (JENKINS-41972) Slow page loading and page unresponsive in version 2.44
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Closing as cannot reproduce Jenkins / JENKINS-41972 Slow page loading and page unresponsive in version 2.44 Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce 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://gr
[JIRA] (JENKINS-41026) Jenkins failed to connect to GIT repository
Title: Message Title Mark Waite closed an issue as Not A Defect The Jenkins issue site is not a question and answer site. Please use the mailing lists and the chat systems for questions. Jenkins / JENKINS-41026 Jenkins failed to connect to GIT repository Change By: Mark Waite Status: Reopened 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+un
[JIRA] (JENKINS-39235) Jenkins instance unexpectedly shut down.
Title: Message Title Mark Waite closed an issue as Not A Defect Java virtual machine crash is not a Jenkins defect. Jenkins / JENKINS-39235 Jenkins instance unexpectedly shut down. Change By: Mark Waite 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://g
[JIRA] (JENKINS-61156) Regression: P4 Plugin 1.10.10 trigger doesn't run jobs
Title: Message Title Tom Cramer created an issue Jenkins / JENKINS-61156 Regression: P4 Plugin 1.10.10 trigger doesn't run jobs Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2020-02-19 23:52 Environment: Jenkins LTS 2.204.2 on Windows Server 2016 (64bit) Java 1.8.0_144-b01 p4-plugin 1.10.10 Priority: Major Reporter: Tom Cramer We use a Perforce Trigger that calls curl to POST to the /p4/change endpoint exposed by the p4-plugin. With 1.10.6, this trigger worked, and the relevant job would run. Upgrading to 1.10.10, and the trigger stopped working. In investigating the issue, 1.10.10 was still logging "doChange: Received trigger event for: ", but the usual followup log "probeJobs: P4: probing: " never appeared. Rolling the plugin back to 1.10.6 restored the ability to trigger the jenkins job. Add Comment
[JIRA] (JENKINS-38531) Config.xml of the job gets lost/deleted randomnly on jenkins restart
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-38531 Config.xml of the job gets lost/deleted randomnly on jenkins restart Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce 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.174716.1474970823000.2767.1582156380733%40Atlassian.JIRA.
[JIRA] (JENKINS-25842) User Permissions Wiped After Jenkins Restart
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-25842 User Permissions Wiped After Jenkins Restart Change By: Mark Waite Component/s: _unsorted 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.159417.1417434128000.2751.1582156320489%40Atlassian.JIRA.
[JIRA] (JENKINS-47094) Got exception when adding Jenkins windows slave.
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-47094 Got exception when adding Jenkins windows slave. Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce 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.185490.150633281.2749.1582156200275%40Atlassian.JIRA.
[JIRA] (JENKINS-44345) how to stop Jenkins job on VM
Title: Message Title Mark Waite closed an issue as Not A Defect The Jenkins mailing lists and Jenkins chat systems are the correct places for questions. Jenkins / JENKINS-44345 how to stop Jenkins job on VM Change By: Mark Waite 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
[JIRA] (JENKINS-56209) send build artifacts over SSH Failed HostName
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-56209 send build artifacts over SSH Failed HostName Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce 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.197766.1550632782000.2745.1582156080239%40Atlassian.JIRA.
[JIRA] (JENKINS-59284) After updating Jenkins, it fails to start
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59284 After updating Jenkins, it fails to start Change By: Mark Waite Component/s: core Component/s: _unsorted 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.201817.1568035735000.2742.1582155900146%40Atlassian.JIRA.
[JIRA] (JENKINS-59208) OneDataScan
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-59208 OneDataScan Change By: Mark Waite 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.201658.1567536256000.2739.1582155780576%40Atlassian.JIRA.
[JIRA] (JENKINS-59133) Primeiro Projeto
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-59133 Primeiro Projeto Change By: Mark Waite 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.201565.1567029129000.2737.1582155780542%40Atlassian.JIRA.
[JIRA] (JENKINS-50344) Failed to start Jenkins INFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
Title: Message Title Mark Waite closed an issue as Not A Defect This is a user configuration error, not a Jenkins issue. Jenkins / JENKINS-50344 Failed to start Jenkins INFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet Change By: Mark Waite 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...@g
[JIRA] (JENKINS-50359) this is showing up when i am running jenkins on tomcat
Title: Message Title Mark Waite closed an issue as Not A Defect Java 10 is not supported by Jenkins Jenkins / JENKINS-50359 this is showing up when i am running jenkins on tomcat Change By: Mark Waite 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://gro
[JIRA] (JENKINS-53033) stuck but be able to continue after aborting build
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-53033 stuck but be able to continue after aborting build Change By: Mark Waite Component/s: _unsorted 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.193021.1534243724000.2726.1582155600446%40Atlassian.JIRA.
[JIRA] (JENKINS-53241) Jenkins couldn't find web element of maven project, however it is working on local eclipse
Title: Message Title Mark Waite closed an issue as Not A Defect This is an issue in the user written test script or in the environment on the agent (sometimes because a web browser cannot be started on the agent to execute the test). Not a Jenkins issue. Jenkins / JENKINS-53241 Jenkins couldn't find web element of maven project, however it is working on local eclipse Change By: Mark Waite 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
[JIRA] (JENKINS-55863) Jenkins not working in WinXP64
Title: Message Title Mark Waite closed an issue as Cannot Reproduce No response from submitter Jenkins / JENKINS-55863 Jenkins not working in WinXP64 Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce 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/je
[JIRA] (JENKINS-51670) java.io.IOException: Failed to connect to 18.218.111.188:33083
Title: Message Title Mark Waite closed an issue as Not A Defect This is a configuration error in the user installation, not a Jenkins issue. Jenkins / JENKINS-51670 java.io.IOException: Failed to connect to 18.218.111.188:33083 Change By: Mark Waite Status: Reopened 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.
[JIRA] (JENKINS-56159) Permission error (error 5).
Title: Message Title Mark Waite closed an issue as Not A Defect Permission errors in user scripts are almost never a Jenkins bug. Jenkins / JENKINS-56159 Permission error (error 5). Change By: Mark Waite 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:/
[JIRA] (JENKINS-56464) Windows 10 64 bit. Jenkins OutOfMemory Exception with Light weight
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-56464 Windows 10 64 bit. Jenkins OutOfMemory Exception with Light weight Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce 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.198063.1551971869000.2705.1582155180410%40Atlassian.JIRA.
[JIRA] (JENKINS-59738) how to change jenkins jnpl slave resource limit
Title: Message Title Mark Waite closed an issue as Not A Defect The Jenkins issue site is not a question and answer site. Please use the mailing list or the chat channels for questions. Jenkins / JENKINS-59738 how to change jenkins jnpl slave resource limit Change By: Mark Waite 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+uns
[JIRA] (JENKINS-59837) java.lang.OutOfMemoryError: Compressed class space
Title: Message Title Mark Waite closed an issue as Not A Defect This is not a Jenkins issue. If the Java subprocess is not able to allocate memory, the tests will fail, whether they are running in Jenkins or outside Jenkins. Jenkins / JENKINS-59837 java.lang.OutOfMemoryError: Compressed class space Change By: Mark Waite 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
[JIRA] (JENKINS-60131) jenkins doesn't start and can't launch service
Title: Message Title Mark Waite started work on JENKINS-60131 Change By: Mark Waite 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.202983.1573481373000.2695.1582154940400%40Atlassian.JIRA.
[JIRA] (JENKINS-60131) jenkins doesn't start and can't launch service
Title: Message Title Mark Waite updated JENKINS-60131 Jenkins / JENKINS-60131 jenkins doesn't start and can't launch service Change By: Mark Waite 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.202983.1573481373000.2697.1582154940433%40Atlassian.JIRA.
[JIRA] (JENKINS-60131) jenkins doesn't start and can't launch service
Title: Message Title Mark Waite updated JENKINS-60131 Jenkins / JENKINS-60131 jenkins doesn't start and can't launch service Change By: Mark Waite Status: In Review Fixed but Unreleased Resolution: Cannot Reproduce 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.202983.1573481373000.2699.1582154940477%40Atlassian.JIRA.
[JIRA] (JENKINS-60131) jenkins doesn't start and can't launch service
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60131 jenkins doesn't start and can't launch service Change By: Mark Waite Component/s: core Component/s: _unsorted 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.202983.1573481373000.2691.1582154880184%40Atlassian.JIRA.
[JIRA] (JENKINS-60131) jenkins doesn't start and can't launch service
Title: Message Title Mark Waite commented on JENKINS-60131 Re: jenkins doesn't start and can't launch service Please provide more details of the problem you've seen, the conditions which might have caused the problem, and the things you've investigated to resolve the problem. 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.202983.1573481373000.2693.1582154880209%40Atlassian.JIRA.
[JIRA] (JENKINS-60183) jenkins crash after stop job
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60183 jenkins crash after stop job Change By: Mark Waite Component/s: core Component/s: _unsorted 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.203144.1573813442000.2689.1582154820317%40Atlassian.JIRA.
[JIRA] (JENKINS-60477) Jenkins job is over running while creating jar files
Title: Message Title Mark Waite closed an issue as Not A Defect The Jenkins issue tracker is not a question and answer site. Please use the mailing list or the chat systems for questions. Jenkins / JENKINS-60477 Jenkins job is over running while creating jar files Change By: Mark Waite 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-iss
[JIRA] (JENKINS-60273) Build Now link on the Edit or Console Output page
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60273 Build Now link on the Edit or Console Output page Change By: Mark Waite Component/s: core Component/s: _unsorted 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.203263.1574709241000.2683.1582154760709%40Atlassian.JIRA.
[JIRA] (JENKINS-60584) Where to remove http server header version for jenkins based on Jetty?
Title: Message Title Mark Waite closed an issue as Not A Defect The Jenkins issue tracker is not a question and answer site. Please use the mailing list or the chat systems for questions. Jenkins / JENKINS-60584 Where to remove http server header version for jenkins based on Jetty? Change By: Mark Waite 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 emai
[JIRA] (JENKINS-61139) Cannot install plugin in China
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61139 Cannot install plugin in China Change By: Mark Waite Summary: 不能安装插件 Cannot install plugin in China 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.204664.1582093612000.2669.1582154640222%40Atlassian.JIRA.
[JIRA] (JENKINS-61139) 不能安装插件
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61139 不能安装插件 Change By: Mark Waite Can't installdefault.jsongoogle replaced baiduupdates.jenkins-ci.org replaced with mirrors.tuna.tsinghua.edu.cnSome plugins can be installed, and there are still plugins that cannot be installed and it is very slow!In Chinese: 安装不了default.json google 替换了 baiduupdates.jenkins-ci.org 换成了 mirrors.tuna.tsinghua.edu.cn可以安装部分插件了，还是有安装不了的插件而且慢的很！ 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.204664.1582093612000.2667.1582154640192%40Atlassian.JIRA.
[JIRA] (JENKINS-60966) Administrative monitors global configuration long and unordered
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60966 Jenkins / JENKINS-60966 Administrative monitors global configuration long and unordered Change By: Allan BURDAJEWICZ Status: In Review 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.204429.158088555.2658.1582153680273%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Mark Waite commented on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge Thanks so much for your efforts Brian Ray! 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.198962.1556378819000.2652.1582152960229%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Brian Ray commented on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge LooseUnpeeled objects are, naturally, loose refs. Peeled[Non]Tag objects are packed refs. JGit 4.9.0+ packs all refs upon cloning. 4.8.0 and prior leaves them loose. That explains the variation in types. I'm close to having a valid test and then the patch. But the upcoming two days are booked; it may be next week before this lands in a 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.198962.1556378819000.2643.1582152180306%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Philip Aston commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin I'm seeing behaviour similar to that reported by Jim Poje above. I'm following the documented pattern, but the change list reported by $P4_CHANGELIST (when captured by the parent job and passed to as a parameter to trigger the child job) reflects more recent commits. I suspect there may have been a regression in the plugin. I'm going to downgrade (1.10.10 -> 1.9.6) and monitor over the next few days. 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.168534.1456438321000.2629.1582150620309%40Atlassian.JIRA.
[JIRA] (JENKINS-61155) can't add an ldap group if a user with the same name exists
Title: Message Title Randy Rue created an issue Jenkins / JENKINS-61155 can't add an ldap group if a user with the same name exists Issue Type: Bug Assignee: Unassigned Components: ldap-plugin Created: 2020-02-19 22:13 Priority: Minor Reporter: Randy Rue 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 "Jenkin
[JIRA] (JENKINS-61066) Schedule Jenkins job using Jenkins Rest API
Title: Message Title
Ian Williams edited a comment on JENKINS-61066
Re: Schedule Jenkins job using Jenkins Rest API
I was just investigating a separate issue regarding plugins and came across: [naginator pluginhttps plugin|https ://plugins.jenkins.io/naginator].{quote}This plugin allows you to automatically reschedule a build after a build failure.This can be useful in several cases, including:The build is dependent upon external resources, that were temporarily unavailable (DB down, network down, website down, etc).{quote}I wonder if that is the same expected behaviour? I will be investigating if it suits my needs.
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.204550.1581506364000.2615.1582147740191%40Atlassian.JIRA.
[JIRA] (JENKINS-61066) Schedule Jenkins job using Jenkins Rest API
Title: Message Title Ian Williams commented on JENKINS-61066 Re: Schedule Jenkins job using Jenkins Rest API I was just investigating a separate issue regarding plugins and came across: [naginator pluginhttps://plugins.jenkins.io/naginator]. This plugin allows you to automatically reschedule a build after a build failure. This can be useful in several cases, including: The build is dependent upon external resources, that were temporarily unavailable (DB down, network down, website down, etc). I wonder if that is the same expected behaviour? I will be investigating if it suits my needs. 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.204550.1581506364000.2611.1582147620291%40Atlassian.JIRA.
[JIRA] (JENKINS-12999) Cannot delete a "Throttle Concurrent Builds" category
Title: Message Title Basil Crow updated JENKINS-12999 Released in Throttle Concurrent Builds 2.0.2. Jenkins / JENKINS-12999 Cannot delete a "Throttle Concurrent Builds" category Change By: Basil Crow Status: Fixed but Unreleased Resolved Released As: 2.0.2 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
[JIRA] (JENKINS-49006) ConcurrentModificationException in getThrottledPipelineRunsForCategory
Title: Message Title Basil Crow updated JENKINS-49006 Released in Throttle Concurrent Builds 2.0.2. Jenkins / JENKINS-49006 ConcurrentModificationException in getThrottledPipelineRunsForCategory Change By: Basil Crow Status: Fixed but Unreleased Resolved Released As: 2.0.2 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
[JIRA] (JENKINS-54578) Cannot delete last category
Title: Message Title Basil Crow updated JENKINS-54578 Released in Throttle Concurrent Builds 2.0.2. Jenkins / JENKINS-54578 Cannot delete last category Change By: Basil Crow Status: Fixed but Unreleased Resolved Released As: 2.0.2 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
[JIRA] (JENKINS-60481) Add @Symbol to ThrottleJobProperty to expose in declarative pipeline `options`
Title: Message Title Basil Crow updated JENKINS-60481 Released in Throttle Concurrent Builds 2.0.2. Jenkins / JENKINS-60481 Add @Symbol to ThrottleJobProperty to expose in declarative pipeline `options` Change By: Basil Crow Status: Fixed but Unreleased Resolved Released As: 2.0.2 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 di
[JIRA] (JENKINS-61087) Use FlowExecutionList to calculate the number of running Pipeline jobs
Title: Message Title Basil Crow updated JENKINS-61087 Released in Throttle Concurrent Builds 2.0.2. Jenkins / JENKINS-61087 Use FlowExecutionList to calculate the number of running Pipeline jobs Change By: Basil Crow Status: Fixed but Unreleased Resolved Released As: 2.0.2 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
[JIRA] (JENKINS-60584) Where to remove http server header version for jenkins based on Jetty?
Title: Message Title Joaquim Amado started work on JENKINS-60584 Change By: Joaquim Amado 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.203710.1577247436000.2582.1582146900320%40Atlassian.JIRA.
[JIRA] (JENKINS-60584) Where to remove http server header version for jenkins based on Jetty?
Title: Message Title Joaquim Amado stopped work on JENKINS-60584 Change By: Joaquim Amado 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.203710.1577247436000.2584.1582146900348%40Atlassian.JIRA.
[JIRA] (JENKINS-61150) graphs data do not reflect the actual data shown under the data tables on the Performance Signature report
Title: Message Title Shashidhar Addaguduru updated an issue Jenkins / JENKINS-61150 graphs data do not reflect the actual data shown under the data tables on the Performance Signature report Change By: Shashidhar Addaguduru Summary: graphs data do not reflect the actual data shown under the data tables on the Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolnames 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.204680.1582123171000.2578.1582144920144%40Atlassian.JIRA.
[JIRA] (JENKINS-61150) Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolnames as well
Title: Message Title Shashidhar Addaguduru updated an issue Jenkins / JENKINS-61150 Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolnames as well Change By: Shashidhar Addaguduru Attachment: Performance Signature report - Overall-graphs.PNG Attachment: Performance Signature report - JVM - graphs.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.204680.1582123171000.2574.1582144860240%40Atlassian.JIRA.
[JIRA] (JENKINS-61150) Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolnames as well
Title: Message Title
Shashidhar Addaguduru updated an issue
Jenkins / JENKINS-61150
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolnames as well
Change By:
Shashidhar Addaguduru
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolname values as well. The Dynatrace API response json (sample) contains datapoint "poolname" in addition to PGI name as seen in below response JSON.Currently the same PGI name displaying under each of the rows on the corresponding data table on the Signature report and it is not possible to identify which poolname the row data belongs to. "dataResult": { "dataPoints": { "PROCESS_GROUP_INSTANCE-B63C48A933CE7D72, pid=0x1, poolname='PS Eden Space'": [ [ 158204226, 17256976 ], [ 158204232, 24354080 ], Might be due to this discrepancy, the data on the graphs are not reflecting the data in the tables. The graphs of all poolnames are showing same data. Attached screenshot for this issue.Another issue is that the data on Overall graphs under all TimeseriesIds are not reflecting the data under the Overall row data. Attached screenshot for this issue.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61150) Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolnames as well
Title: Message Title
Shashidhar Addaguduru updated an issue
Jenkins / JENKINS-61150
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolnames as well
Change By:
Shashidhar Addaguduru
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolname values as well. The Dynatrace API response json contains datapoint "poolname" in addition to PGI name as seen in below response JSON.Currently the same PGI name displaying under each of the rows on the corresponding data table on the Signature report and it is not possible to identify which poolname the row data belongs to. "dataResult": { "dataPoints": { "PROCESS_GROUP_INSTANCE-B63C48A933CE7D72, pid=0x1, poolname='PS Eden Space'": [ [ 158204226, 17256976 ], [ 158204232, 24354080 ], Might be due to this discrepancy, the data on the graphs are not reflecting the data in the tables. The graphs of all poolnames are showing same data. Attached screenshot for this issue.Another issue is that the data on Overall graphs under all TimeseriesIds are not reflecting the data under the Overall row data. Attached screenshot for this issue.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Ian Williams commented on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen In JENKINS-58030, Olivier Dagenais, mentioned David Staheli is now responsible for the plugin. Mentioning to see if that provides traction. Have not seen any real action on the plugin since 2018-07, which is just before MS bought GitHub. Wonder if they've just abandoned support for TFS? 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.189378.1521699501000.2560.1582143660366%40Atlassian.JIRA.
[JIRA] (JENKINS-61151) Adding "alpha" keyword to version number
Title: Message Title Dennis Gu updated JENKINS-61151 Jenkins / JENKINS-61151 Adding "alpha" keyword to version number Change By: Dennis Gu 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.204681.1582128515000.2553.1582143120247%40Atlassian.JIRA.
[JIRA] (JENKINS-61151) Adding "alpha" keyword to version number
Title: Message Title Dennis Gu started work on JENKINS-61151 Change By: Dennis Gu 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.204681.1582128515000.2552.1582143120160%40Atlassian.JIRA.
[JIRA] (JENKINS-48625) Several git repo browser URL formats are not checked or documented
Title: Message Title Rishabh Budhouliya updated JENKINS-48625 Jenkins / JENKINS-48625 Several git repo browser URL formats are not checked or documented Change By: Rishabh Budhouliya 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.187279.1513683224000.2547.1582141980350%40Atlassian.JIRA.
[JIRA] (JENKINS-48625) Several git repo browser URL formats are not checked or documented
Title: Message Title Rishabh Budhouliya commented on JENKINS-48625 Re: Several git repo browser URL formats are not checked or documented Fix for this issue: https://github.com/jenkinsci/git-plugin/pull/841 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.187279.1513683224000.2545.1582141980326%40Atlassian.JIRA.
[JIRA] (JENKINS-61154) Pipeline: Groovy 2.79 does not abort the build if a pipeline stage fails
Title: Message Title Liam Reimers created an issue Jenkins / JENKINS-61154 Pipeline: Groovy 2.79 does not abort the build if a pipeline stage fails Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2020-02-19 19:33 Environment: macOS 10.14.6 openjdk-11.0.2 Jenkins 2.220 (and 2.219) Pipeline: Groovy (workflow-cps): 2.79 Pipeline: SCM Step (workflow-scm-step): 2.10 Config File Provider Plugin (config-file-provider): 3.6.3 Pipeline: GitHub Groovy Libraries (pipeline-github-lib): 1.0 Pipeline: API (workflow-api): 2.39 GitHub plugin (github): 1.29.5 Token Macro Plugin (token-macro): 2.10 MapDB API Plugin (mapdb-api): 1.0.9.0 Structs Plugin (structs): 1.20 Role-based Authorization Strategy (role-strategy): 2.16 Conditional BuildStep (conditional-buildstep): 1.3.6 Groovy Postbuild (groovy-postbuild): 2.5 Docker Commons Plugin (docker-commons): 1.16 SSH Credentials Plugin (ssh-credentials): 1.18.1 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin (jquery-detached): 1.2.1 SCM API Plugin (scm-api): 2.6.3 PAM Authentication plugin (pam-auth): 1.6 Lockable Resources plugin (lockable-resources): 2.7 Extended Choice Parameter Plug-In (extended-choice-parameter): 0.78 Email Extension Plugin (email-ext): 2.68 Resource Disposer Plugin (resource-disposer): 0.14 Authentication Tokens API Plugin (authentication-tokens): 1.3 Plain Credentials Plugin (plain-credentials): 1.7 Git Parameter Plug-In (git-parameter): 0.9.12 Analysis Model API Plug-in (analysis-model-api): 7.0.4 Warnings Plug-in (warnings): 5.0.1 Show Build Parameters plugin (show-build-parameters): 1.0 Git client plugin (git-client): 3.1.1 SSH Build Agents plugin (ssh-slaves): 1.31.1 Pipeline: Step API (workflow-step-api): 2.22 Static Analysis Utilities (analysis-core): 1.96 Warnings Next Generation Plugin (warnings-ng): 7.3.0 Mailer Plugin (mailer): 1.30 SCM Sync Configuration Plugin (scm-sync-configuration): 0.0.10 Green Balls (greenballs): 1.15 GitHub Branch Source Plugin (github-branch-source): 2.6.0 Apache HttpComponents Client 4.x API Plugin (apache-httpcomponents-client-4-api): 4.5.10-2.0 Violation Comments to Bitbucket Server Plugin (violation-comments-to-stash): 1.114 Pipeline: Model API (pipeline-model-api): 1.5.1 xUnit plugin (xunit): 2.3.7 jQuery plugin (jquery): 1.12.4-1 Workspace Cleanup Plugin (ws-cleanup): 0.38 Matrix Authorization Strategy Plugin (matrix-auth): 2.5 External Monitor Job Type Plugin (external-monitor-job): 1.7 JUnit Plugin (junit): 1.28 bouncycastle API Plugin (bouncycastle-api): 2.18 Jackson 2 API Plugin (jackson2-api): 2.10.2 Multipl
[JIRA] (JENKINS-61146) ec2-plugin occassional traceback
Title: Message Title Tristan Hill commented on JENKINS-61146 Re: ec2-plugin occassional traceback 1.8.0_242-b08 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.204676.1582116605000.2539.1582138560286%40Atlassian.JIRA.
[JIRA] (JENKINS-59785) java.io.NotSerializableException: hudson.plugins.git.GitChangeSetList
Title: Message Title Scott Hebert commented on JENKINS-59785 Re: java.io.NotSerializableException: hudson.plugins.git.GitChangeSetList /cc Liam Newman 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.202515.1571130622000.2524.1582135740221%40Atlassian.JIRA.
[JIRA] (JENKINS-61030) Runtime results from UFT to Jenkins Console
Title: Message Title MANJU commented on JENKINS-61030 Re: Runtime results from UFT to Jenkins Console ok. Thanks for the update. Anda Sorina Laakso Have you already considered this as a Enhancement request or should i raise an enhancement request separately? 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.204504.1581330691000.2519.1582135500291%40Atlassian.JIRA.
[JIRA] (JENKINS-61146) ec2-plugin occassional traceback
Title: Message Title Benura Lasan commented on JENKINS-61146 Re: ec2-plugin occassional traceback Hello Tristan Hill. What is the jdk version you are using? 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.204676.1582116605000.2511.1582134360196%40Atlassian.JIRA.
[JIRA] (JENKINS-61152) Maintainer can't release new plugin version
Title: Message Title Franco Frangipane commented on JENKINS-61152 Re: Maintainer can't release new plugin version Thanks for your help Oleg Nenashev I just raised the submit pull request https://github.com/jenkins-infra/repository-permissions-updater/pull/1426 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.204682.1582130713000.2505.1582134180107%40Atlassian.JIRA.
[JIRA] (JENKINS-61153) Agent hangs after startup when two jobs start simultaneously
Title: Message Title
Bryan Anderson updated an issue
Jenkins / JENKINS-61153
Agent hangs after startup when two jobs start simultaneously
Change By:
Bryan Anderson
I'm seeing an intermittent issue where, on occasion, 2 jobs will start on an agent that is spun up through the ec2-plugin at the same time and get stuck. Through my reproduction steps, I'm able to get it to happen 10%-30% of the time. I'm able to reproduce it with a fresh install of jenkins, using an off the shelf AMI with no custom changes. The agent is messed up once this happens, so the only solution is to cancel the jobs, restart them, and kill the bad agent. Current plugin list: {code:java}Jenkins Version: 2.204.2--INSTALLED PLUGINS (sorted):---ace-editor (1.1)ant (1.11)antisamy-markup-formatter (1.8)apache-httpcomponents-client-4-api (4.5.10-2.0)authentication-tokens (1.3)aws-credentials (1.28)aws-java-sdk (1.11.723)bouncycastle-api (2.18)branch-api (2.5.5)build-timeout (1.19.1)cloudbees-folder (6.11.1)command-launcher (1.4)credentials (2.3.1)credentials-binding (1.21)display-url-api (2.3.2)docker-commons (1.16)docker-workflow (1.21)durable-task (1.33)ec2 (1.49.1)email-ext (2.68)git (4.1.1)git-client (3.1.1)git-server (1.9)github (1.29.5)github-api (1.106)github-branch-source (2.6.0)gradle (1.36)handlebars (1.1.1)jackson2-api (2.10.2)jdk-tool (1.4)jquery-detached (1.2.1)jsch (0.1.55.2)junit (1.28)ldap (1.21)lockable-resources (2.7)mailer (1.30)mapdb-api (1.0.9.0)matrix-auth (2.5)matrix-project (1.14)momentjs (1.1.1)node-iterator-api (1.5.0)pam-auth (1.6)pipeline-build-step (2.11)pipeline-github-lib (1.0)pipeline-graph-analysis (1.10)pipeline-input-step (2.11)pipeline-milestone-step (1.3.1)pipeline-model-api (1.5.1)pipeline-model-declarative-agent (1.1.1)pipeline-model-definition (1.5.1)pipeline-model-extensions (1.5.1)pipeline-rest-api (2.13)pipeline-stage-step (2.3)pipeline-stage-tags-metadata (1.5.1)pipeline-stage-view (2.13)plain-credentials (1.7)resource-disposer (0.14)scm-api (2.6.3)script-security (1.70)ssh-credentials (1.18.1)ssh-slaves (1.31.1)structs (1.20)subversion (2.13.1)timestamper (1.11)token-macro (2.11)trilead-api (1.0.5)variant (1.3)workflow-aggregator (2.6)workflow-api (2.39)workflow-basic-steps (2.19)workflow-cps (2.80)workflow-cps-global-lib (2.15)workflow-durable-task-step (2.35)workflow-job (2.36)workflow-multibranch (2.21)workflow-scm-step (2.10)workflow-step-api (2.22)workflow-support (3.4)ws-cleanup (0.38){code} Steps to reproduce: # Start docker container: jenkins/jenkins:2.204.2 ## {code:java}docker run -it -p 8080:8080 -p 5:5 jenkins/jenkins:2.204.2{code} # Install recommended plugins through wizard # Install "Amazon EC2 Plugin" version 1.49.1 # Configure Amazon EC2 to connect to AWS ## For AMI, I saw this with different agents, but to reproduce, you can use " !http://localhost:8081/static/7d41ff45/images/none.gif|width=1,height=16! amazon/amzn2-ami-hvm-2.0.20200207.1-x86_64-gp2 by amazon" which is "ami-0a887e401f7654935" ## Size: T2Medium (also tried m4.large) ## FS root
[JIRA] (JENKINS-61153) Agent hangs after startup when two jobs start simultaneously
Title: Message Title Bryan Anderson created an issue Jenkins / JENKINS-61153 Agent hangs after startup when two jobs start simultaneously Issue Type: Bug Assignee: FABRIZIO MANFREDI Attachments: freestyle-job__20_Console__Jenkins_.png, pipeline-job__18_Console__Jenkins_.png, Thread-dump-pipelinejob Components: ec2-plugin Created: 2020-02-19 17:34 Environment: Fresh Jenkins container (jenkins/jenkins:lts - version 2.204.2) Suggested plugins installed through wizard + ec2-plugin (specifics in description) Priority: Major Reporter: Bryan Anderson I'm seeing an intermittent issue where, on occasion, 2 jobs will start on an agent that is spun up through the ec2-plugin at the same time and get stuck. Through my reproduction steps, I'm able to get it to happen 10%-30% of the time. I'm able to reproduce it with a fresh install of jenkins, using an off the shelf AMI with no custom changes. Current plugin list: Jenkins Version: 2.204.2 -- INSTALLED PLUGINS (sorted): --- ace-editor (1.1) ant (1.11) antisamy-markup-formatter (1.8) apache-httpcomponents-client-4-api (4.5.10-2.0) authentication-tokens (1.3) aws-credentials (1.28) aws-java-sdk (1.11.723) bouncycastle-api (2.18) branch-api (2.5.5) build-timeout (1.19.1) cloudbees-folder (6.11.1) command-launcher (1.4) credentials (2.3.1) credentials-binding (1.21) display-url-api (2.3.2) docker-commons (1.16) docker-workflow (
[JIRA] (JENKINS-61152) Maintainer can't release new plugin version
Title: Message Title Oleg Nenashev commented on JENKINS-61152 Re: Maintainer can't release new plugin version https://gist.github.com/Chaser324/ce0505fbed06b947d962 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.204682.1582130713000.2493.1582133280126%40Atlassian.JIRA.
[JIRA] (JENKINS-61152) Maintainer can't release new plugin version
Title: Message Title
Franco Frangipane edited a comment on JENKINS-61152
Re: Maintainer can't release new plugin version
Hi [~oleg_nenashev] I'm not able to create a branch to then submit a pull request It seems that my github account doesn't have permissions on jenkins-infra {code:java}remote: Permission to jenkins-infra/repository-permissions-updater.git denied to foxhound91.fatal: unable to access 'https://github.com/jenkins-infra/repository-permissions-updater.git/': The requested URL returned error: 403{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.204682.1582130713000.2491.1582133160140%40Atlassian.JIRA.
[JIRA] (JENKINS-61152) Maintainer can't release new plugin version
Title: Message Title Franco Frangipane commented on JENKINS-61152 Re: Maintainer can't release new plugin version Hi Oleg Nenashev I'm not able to create a branch to then submit a pull request remote: Permission to jenkins-infra/repository-permissions-updater.git denied to foxhound91. fatal: unable to access 'https://github.com/jenkins-infra/repository-permissions-updater.git/': The requested URL returned error: 403 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.204682.1582130713000.2489.1582132980120%40Atlassian.JIRA.
[JIRA] (JENKINS-60216) Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible
Title: Message Title Paul Thevenot edited a comment on JENKINS-60216 Re: Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible I update 've updated to 2.10 as well and I've the same logs while passing parameters to child job using Active Choices Reactive Parameter. The parameter from the parent job is a string and so is the child parameter : "The parameter 'REPO' did not have the type expected by child-job. Converting to Active Choices Reactive Parameter.". What type should I use to pass my parameter instead of string? 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.203189.1574194043000.2485.1582132740403%40Atlassian.JIRA.
