[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head Hi, We are facing this issue frequently is there any workaround or any fix. Our Jenkins version 2.204.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.196374.1545361815000.9328.1584603780655%40Atlassian.JIRA.
[JIRA] (JENKINS-60823) Display message on login screen for those who dont have access to Jenkins
Title: Message Title Senthilkumar Palanisamy created an issue Jenkins / JENKINS-60823 Display message on login screen for those who dont have access to Jenkins Issue Type: New Feature Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2020-01-20 11:48 Environment: Jenkins ver. 2.190.1 Priority: Minor Reporter: Senthilkumar Palanisamy Team, Please can you help me here, we are looking for an option/message in Jenkins if login failed. Currently we are seeing below message: Access Denied is missing the Overall/Read permission Is there any way we can include below message along with that default message Contact : XYZ user for access to Jenkins Thanks Senthil Add Comment
[JIRA] (JENKINS-46722) alwaysLinkToLastBuild not linking to last job result
Title: Message Title Senthilkumar Palanisamy edited a comment on JENKINS-46722 Re: alwaysLinkToLastBuild not linking to last job result Hi,We are also facing same issue for failed build HTML publish is not creating any link in Jenkins Project level, we have to enable alwaysLinkToLastBuild: true,keepAll: true,In order to see in particular build , Please can i know is there any other workaround to see HTML publish result in project level or any permanent fix.Thanks 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.185068.1504796587000.3576.1575980220472%40Atlassian.JIRA.
[JIRA] (JENKINS-60350) Recover Deleted Dashboard view in jenkins main page
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-60350 Re: Recover Deleted Dashboard view in jenkins main page Hi Tobias Gruetzmacher Many Thanks for your information. 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.203367.1575372289000.11733.1575437520159%40Atlassian.JIRA.
[JIRA] (JENKINS-60350) Recover Deleted Dashboard view in jenkins main page
Title: Message Title Senthilkumar Palanisamy updated an issue Jenkins / JENKINS-60350 Recover Deleted Dashboard view in jenkins main page Change By: Senthilkumar Palanisamy Team,Please can you help me here:We have removed Dashboard view on our Jenkins Main page. Is it possible to recover accidentally removed views in JenkinsOur Jenkins Version 2.190.2 ThanksSenthil 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.203367.1575372289000.7.1575372362197%40Atlassian.JIRA.
[JIRA] (JENKINS-60350) Recover Deleted Dashboard view in jenkins main page
Title: Message Title Senthilkumar Palanisamy created an issue Jenkins / JENKINS-60350 Recover Deleted Dashboard view in jenkins main page Issue Type: Story Assignee: Tobias Gruetzmacher Components: dashboard-view-plugin Created: 2019-12-03 11:24 Priority: Minor Reporter: Senthilkumar Palanisamy Team, Please can you help me here: We have removed Dashboard view on our Jenkins Main page. Is it possible to recover accidentally removed views in Jenkins Our Jenkins Version 2.190.2 Add Comment This
[JIRA] (JENKINS-46722) alwaysLinkToLastBuild not linking to last job result
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-46722 Re: alwaysLinkToLastBuild not linking to last job result Hi, We are also facing same issue for failed build HTML publish is not creating any link in Jenkins Project level, we have to enable alwaysLinkToLastBuild: true, keepAll: true, In order to see in particular build is there any other workaround to see in project level or any permanent fix. Thanks 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.185068.1504796587000.9259.1575021420391%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Senthilkumar Palanisamy updated an issue Jenkins / JENKINS-57304 Multiple "idle" entries on Build Executor Status for non-existant executors Change By: Senthilkumar Palanisamy Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.5889.1566280440480%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-57304 Re: Multiple "idle" entries on Build Executor Status for non-existant executors Hi Team, We are also seeing the same behavior listing more number of executor and using Jenkins version 2.176.2 recently upgraded. Seeing same in chrome and firefox. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.5891.1566280440510%40Atlassian.JIRA.
[JIRA] (JENKINS-56634) ERROR: Error fetching remote repo 'origin'
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-56634 Re: ERROR: Error fetching remote repo 'origin' Hi Mark Waite Thanks for your kind information and directing the queries,please can i know and help where these kind of queries i can post Thanks in Advance. Regards Senthil. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56634) ERROR: Error fetching remote repo 'origin'
Title: Message Title Senthilkumar Palanisamy created an issue Jenkins / JENKINS-56634 ERROR: Error fetching remote repo 'origin' Issue Type: Story Assignee: Mark Waite Components: git-plugin Created: 2019-03-20 11:57 Labels: git slaves Priority: Minor Reporter: Senthilkumar Palanisamy Team, Please can you help and provide any solutions and suggestions. We have integrated Jenkins with BitBucket. We don't have Physical slaves and slaves will be creating On-demand ( auto creation during builds are trigger). Here we are seeing frequently below error, " ERROR: Error fetching remote repo 'origin' In Physical slave we can clean the workspace and reboot to fix but slaves which are all creating on-demand how to avoid this issue any fix for this. Our jenkins version 2.138.2 Git Plugin version-->3.9.3 Thanks Senthil
[JIRA] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed Team, We are also facing the same issue Job started triggering due to SCM continuously, but no actual change in code. Please can we know if any workaround or any fix is available. Jenkins version --->2.89.4 Git Plugin version --> 3.9.1 Thanks Senthil Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40837) Rebuild pull request job in jenkins throws error
Title: Message Title Senthilkumar Palanisamy created an issue Jenkins / JENKINS-40837 Rebuild pull request job in jenkins throws error Issue Type: Bug Assignee: ragesh_nair Attachments: rebuild.png Components: rebuild-plugin Created: 2017/Jan/05 12:02 PM Environment: Jenkins version --> Jenkins ver. 1.651.1 Rebuild plugin version ---> 1.25 Priority: Minor Reporter: Senthilkumar Palanisamy Hi, I am facing one issue on Jenkins job. We have one pull request job when we try to click the option "Rebuild" we are getting Stack trace issue. Please see below Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/net/sgpvm158/fs0/.jenkins-linux/plugins/rebuild/WEB-INF/lib/classes.jar!/com/sonyericsson/rebuild/RebuildAction/parameterized.jelly:90:117: Error setting property 'class', exception - org.apache.commons.beanutils.ConversionException: No value specified for 'Class' at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-38860 Re: Git plugin using local config to update submodules We have checked this option "Recursively update submodules" in job configuration page. Where we have to mention the command "git submodule deinit" please can you correct me. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38860) Git plugin using local config to update submodules
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-38860 Re: Git plugin using local config to update submodules Hi, Please can i know is there any other work around to fix this issue "stderr: error: pathspec 'ProjectA/testrepo' did not match any file(s) known to git." This is really blocking our all builds. As of now we are wiping out our workspace to ignore this error every time. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37419) Git plugin checking out non-existent submodule from different branch
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-37419 Re: Git plugin checking out non-existent submodule from different branch Hi We are also facing same issue stderr: error: pathspec 'ProjectA/testrepo' did not match any file(s) known to git. Please can some one help here how to fix this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
