[JIRA] (JENKINS-55740) Pipeline not work after update
Title: Message Title Daniel Gront commented on JENKINS-55740 Re: Pipeline not work after update Radi Berkovich, I see exception in Octane in the log, is it something that fixed in v5.8.3? 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.197116.1548237537000.7613.1564897800128%40Atlassian.JIRA.
[JIRA] (JENKINS-55740) Pipeline not work after update
Title: Message Title Daniel Gront commented on JENKINS-55740 Re: Pipeline not work after update Владислав Ненашев, could you update to latest version 5.8.3? 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.197116.1548237537000.7609.1564897740193%40Atlassian.JIRA.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Sam Gleske commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Here's the fix https://github.com/jenkinsci/github-oauth-plugin/pull/115 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.198903.1556022985000.7559.1564885440807%40Atlassian.JIRA.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Sam Gleske commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page This seems to have been caused by https://github.com/jenkinsci/github-oauth-plugin/pull/109 However, PR 109 is pretty important for how impersonation works. Need to figure out a happy medium. 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.198903.1556022985000.7523.1564881421142%40Atlassian.JIRA.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Sam Gleske commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page https://github.com/jenkinsci/github-oauth-plugin/blob/github-oauth-0.32/src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java#L694-L700 is the problematic section of code Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.7521.1564880944536%40Atlassian.JIRA.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title
Sam Gleske edited a comment on JENKINS-57154
Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Okay I was able to replicate the issue. Replication steps: # Have two GitHub users. githubadmin and githubuser for example where githubadmin is a Jenkins admin and github user is a non-admin user in Jenkins. # Have both users log in and authorize with GitHub OAuth. # Configure project-based matrix authorization and add Overall:Read to githubuser and Overall:Administer to githubadmin. # IMPORTANT: On githubuser log into GitHub settings and de-authorize the OAuth app. This means Jenkins will have a token for the user but it won't be valid because the user de-authorized the app. # Using githubadmin I visited the configureSecurity page in Jenkins and got the following stack trace.{noformat}githubuser (name changed intentionally to be generic)java.lang.NullPointerException at org.jenkinsci.plugins.GithubAuthenticationToken.(GithubAuthenticationToken.java:205) at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:700) at org.jenkinsci.plugins.matrixauth.AuthorizationContainerDescriptor.doCheckName_(AuthorizationContainerDescriptor.java:140) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName(GlobalMatrixAuthorizationStrategy.java:222) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) 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 jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Sam Gleske commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Okay I was able to replicate the issue. Replication steps: Have two GitHub users. githubadmin and githubuser for example where githubadmin is a Jenkins admin and github user is a non-admin user in Jenkins. Have both users log in and authorize with GitHub OAuth. Configure project-based matrix authorization and add Overall:Read to githubuser and Overall:Administer to githubadmin. IMPORTANT: On githubuser log into GitHub settings and de-authorize the OAuth app. This means Jenkins will have a token for the user but it won't be valid because the user de-authorized the app. Using githubadmin I visited the configureSecurity page in Jenkins and got the following stack trace. githubuser (name changed intentionally to be generic) java.lang.NullPointerException at org.jenkinsci.plugins.GithubAuthenticationToken.(GithubAuthenticationToken.java:205) at org.jenkinsci.plugins.GithubSecurityRealm.loadUserByUsername(GithubSecurityRealm.java:700) at org.jenkinsci.plugins.matrixauth.AuthorizationContainerDescriptor.doCheckName_(AuthorizationContainerDescriptor.java:140) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName(GlobalMatrixAuthorizationStrategy.java:222) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) 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 jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Sam Gleske commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page I've tried a couple of ways to reproduce this locally and I'm not able to reproduce it locally. I configured plugin 0.31 and upgraded to 0.32 with no problems. I'll try another fresh install and use 0.29 since I see others reporting they're upgrading from that version. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.7379.1564879140714%40Atlassian.JIRA.
[JIRA] (JENKINS-58654) Improve performance of display-url-api-plugin (DisplayURLContext class)
Title: Message Title Olivier Lamy resolved as Fixed Jenkins / JENKINS-58654 Improve performance of display-url-api-plugin (DisplayURLContext class) Change By: Olivier Lamy Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200934.1564036508000.7377.1564877160088%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Alexander Komarov commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications No rush on my part. Also, our team switched to Mattermost since I pushed this, so this will probably be my only PR for the foreseeable future. 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.172870.1469028488000.7345.1564872780763%40Atlassian.JIRA.
[JIRA] (JENKINS-58748) Trigger builds based on gitlab comment
Title: Message Title Parichay Barpanda commented on JENKINS-58748 Re: Trigger builds based on gitlab comment Although in the Jenkins UI, you have an action to perform build now which performs a new build for the latest revision. It doesn't checks out the project. 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.201051.1564642824000.7335.1564860240042%40Atlassian.JIRA.
[JIRA] (JENKINS-58748) Trigger builds based on gitlab comment
Title: Message Title Parichay Barpanda commented on JENKINS-58748 Re: Trigger builds based on gitlab comment Presently it doesn't work for same revision as Jenkins says it is in the same revision and no changes detected. So even if Jenkins fails for some weird reason you cannot restart the build. 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.201051.1564642824000.7334.1564860060042%40Atlassian.JIRA.
[JIRA] (JENKINS-58797) getTrustedRevision always returns false for forked MRs
Title: Message Title Parichay Barpanda updated JENKINS-58797 Jenkins / JENKINS-58797 getTrustedRevision always returns false for forked MRs Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201107.1564858749000.7333.1564859880265%40Atlassian.JIRA.
[JIRA] (JENKINS-58796) Fix MR event type in GitLabMRSCMEvent
Title: Message Title Parichay Barpanda updated JENKINS-58796 Jenkins / JENKINS-58796 Fix MR event type in GitLabMRSCMEvent Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201106.156485574.7331.1564859880207%40Atlassian.JIRA.
[JIRA] (JENKINS-58748) Trigger builds based on gitlab comment
Title: Message Title Parichay Barpanda updated JENKINS-58748 Jenkins / JENKINS-58748 Trigger builds based on gitlab comment Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201051.1564642824000.7332.1564859880252%40Atlassian.JIRA.
[JIRA] (JENKINS-58797) getTrustedRevision always returns false for forked MRs
Title: Message Title Parichay Barpanda started work on JENKINS-58797 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201107.1564858749000.7330.1564858800266%40Atlassian.JIRA.
[JIRA] (JENKINS-58797) getTrustedRevision always returns false for forked MRs
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58797 getTrustedRevision always returns false for forked MRs Issue Type: Story Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-03 18:59 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda 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
[JIRA] (JENKINS-58690) Add retention strategy for Cloud
Title: Message Title Long Nguyen updated JENKINS-58690 Jenkins / JENKINS-58690 Add retention strategy for Cloud Change By: Long Nguyen Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200979.1564304727000.7328.1564857960227%40Atlassian.JIRA.
[JIRA] (JENKINS-58795) Jenkins pipeline - Getting information When Restart Stage
Title: Message Title Ahmed Itman commented on JENKINS-58795 Re: Jenkins pipeline - Getting information When Restart Stage I made an work around using groovy Regular Expressions - regexes to grep build logs, looking for " Restarted from build #\d " If i found it, it means that build is restarted and if not that's mean it is a new build not depending on another build Is their another solution ? because i think my solution is not the best and may be standard of logs will be changed in the future 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.201105.1564840375000.7326.1564856340145%40Atlassian.JIRA.
[JIRA] (JENKINS-58796) Fix MR event type in GitLabMRSCMEvent
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58796 Fix MR event type in GitLabMRSCMEvent Issue Type: Story Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-03 18:09 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda The SCM MR event impl isn't properly detecting the type of MR event. It always says type created even if it is of type updated. Add Comment
[JIRA] (JENKINS-58748) Trigger builds based on gitlab comment
Title: Message Title Parichay Barpanda started work on JENKINS-58748 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201051.1564642824000.7322.1564855810972%40Atlassian.JIRA.
[JIRA] (JENKINS-58796) Fix MR event type in GitLabMRSCMEvent
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58796 Fix MR event type in GitLabMRSCMEvent Issue Type: Story Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-03 18:09 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda The SCM MR event impl isn't properly detecting the type of MR event. It always says type created even if it is of type updated. Add Comment
[JIRA] (JENKINS-58748) Trigger builds based on gitlab comment
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-58748 Trigger builds based on gitlab comment Change By: Parichay Barpanda For example, user can comment on commits / MRs to "jenkins please rebuild" and the build is triggered. 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.201051.1564642824000.7323.1564855811004%40Atlassian.JIRA.
[JIRA] (JENKINS-58796) Fix MR event type in GitLabMRSCMEvent
Title: Message Title Parichay Barpanda started work on JENKINS-58796 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201106.156485574.7321.1564855810292%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title Sergei Parshev commented on JENKINS-58620 Re: MPL shared library logic execution caused CPS mismatch warning Jesse Glick, Devin Nusbaum - could you please check? Probably jenkins shouldn't show such messages in the job log? 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.200786.1563913328000.7319.1564855440163%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Jim Klimov commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications Thanks. I was trying to make a release yesterday, but it stumbled on older dependencies first and on newly caught findbugs then, so stalled a bit ;( 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.172870.1469028488000.7285.1564855380805%40Atlassian.JIRA.
[JIRA] (JENKINS-58790) Add System hook
Title: Message Title Parichay Barpanda updated JENKINS-58790 Jenkins / JENKINS-58790 Add System hook Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201100.1564764723000.7283.1564845480079%40Atlassian.JIRA.
[JIRA] (JENKINS-58790) Add System hook
Title: Message Title Parichay Barpanda started work on JENKINS-58790 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201100.1564764723000.7274.1564841640070%40Atlassian.JIRA.
[JIRA] (JENKINS-58795) Jenkins pipeline - Getting information When Restart Stage
Title: Message Title Ahmed Itman updated an issue Jenkins / JENKINS-58795 Jenkins pipeline - Getting information When Restart Stage Change By: Ahmed Itman Labels: pipeline 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.201105.1564840375000.7273.1564840440207%40Atlassian.JIRA.
[JIRA] (JENKINS-58795) Jenkins pipeline - Getting information When Restart Stage
Title: Message Title Ahmed Itman created an issue Jenkins / JENKINS-58795 Jenkins pipeline - Getting information When Restart Stage Issue Type: New Feature Assignee: Andrew Bayer Components: pipeline, pipeline-model-definition-plugin, pipeline-stage-view-plugin Created: 2019-08-03 13:52 Priority: Critical Reporter: Ahmed Itman When restarting a stage, in the console the follwoing output is shown Restarted from build #4, stage foobar Is there any way to access this information within the restarted build? Eg via ENV variables or globals in the Jenkinsfile? Add Comment
[JIRA] (JENKINS-39941) Empty areas in the full screen mode of Dashboard view plugin
Title: Message Title Tobias Gruetzmacher closed an issue as Fixed Jenkins / JENKINS-39941 Empty areas in the full screen mode of Dashboard view plugin Change By: Tobias Gruetzmacher Status: Resolved Closed 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.176561.147983173.7268.1564839600227%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title Mark Waite updated JENKINS-58751 Jenkins / JENKINS-58751 TAG_NAME is not populated in declarative multibranch pipeline Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect 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.201054.1564649736000.7236.1564837800304%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title Mark Waite updated JENKINS-58751 Jenkins / JENKINS-58751 TAG_NAME is not populated in declarative multibranch pipeline Change By: Mark Waite Status: Fixed but Unreleased Closed 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.201054.1564649736000.7238.1564837800328%40Atlassian.JIRA.
[JIRA] (JENKINS-33473) Groovy script with default values when job is started by timer
Title: Message Title
Alex Domoradov commented on JENKINS-33473
Re: Groovy script with default values when job is started by timer
> In hudson.model.ParameterDefinition#getDefaultParameterValue, we return the first element if the script returned any element, or an empty string (the job fails if we pass null). Doesn't work for me. I'm using the following groovy script inside Active Choices Reactive Parameter
switch (CLOUD_PROVIDER){
case "AWS":
return ['c5.xlarge:selected', 'c5.2xlarge', 'c5.4xlarge']
break
case "GCP":
return ['n1-standard-4:selected', 'n1-standard-8', 'n1-standard-16']
break
}
CLOUD_PROVIDER it's Active Choices Parameter with simple script
return ['AWS:selected', 'GCP']
But when job triggered by timer it always return empty string. Did I miss something? Active choice plugin - 2.1, Jenkins - 2.164.3
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.168887.1457683062000.7229.1564837440417%40Atlassian.JIRA.
[JIRA] (JENKINS-54959) Offer a new Unarchive installer which takes Java archive structure into account
Title: Message Title Bruno Medeiros updated an issue Jenkins / JENKINS-54959 Offer a new Unarchive installer which takes Java archive structure into account Change By: Bruno Medeiros Comment: It seems that setting the "Subdirectory of extracted archive" of the JDK tool configuration is a valid workaround:!screenshot-1.png|width=485,height=177,thumbnail! 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.195983.1543566344000.7223.1564825200816%40Atlassian.JIRA.
[JIRA] (JENKINS-54959) Offer a new Unarchive installer which takes Java archive structure into account
Title: Message Title Bruno Medeiros commented on JENKINS-54959 Re: Offer a new Unarchive installer which takes Java archive structure into account It seems that setting the "Subdirectory of extracted archive" of the JDK tool configuration is a valid workaround: 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.195983.1543566344000.7218.1564825140160%40Atlassian.JIRA.
[JIRA] (JENKINS-54959) Offer a new Unarchive installer which takes Java archive structure into account
Title: Message Title Bruno Medeiros updated an issue Jenkins / JENKINS-54959 Offer a new Unarchive installer which takes Java archive structure into account Change By: Bruno Medeiros 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.195983.1543566344000.7213.1564825020409%40Atlassian.JIRA.
[JIRA] (JENKINS-58765) why , When I launched RobotFrameWork(with library selenium) tests by Jenkins all tests are FAIL
Title: Message Title RemiCharles LageixArena updated an issue Jenkins / JENKINS-58765 why , When I launched RobotFrameWork(with library selenium) tests by Jenkins all tests are FAIL Change By: RemiCharles LageixArena Summary: why , When I launched RobotFrameWork(with library selenium) tests by Jenkins all tests that want to openbrowser (ff or chrome) are FAIL 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.201070.1564669421000.7211.1564822680122%40Atlassian.JIRA.
[JIRA] (JENKINS-58765) why , When I launched RobotFrameWork(with library selenium) tests by Jenkins all tests that want to openbrowser (ff or chrome) are FAIL
Title: Message Title RemiCharles LageixArena updated an issue Jenkins / JENKINS-58765 why , When I launched RobotFrameWork(with library selenium) tests by Jenkins all tests that want to openbrowser (ff or chrome) are FAIL Change By: RemiCharles LageixArena Summary: why jenkins But , When I launched same RobotFrameWork(with library selenium) tests by Jenkins all tests that want to openbrowser (ff or chrome) are FAIL 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.201070.1564669421000.7210.1564822680094%40Atlassian.JIRA.
[JIRA] (JENKINS-58765) why jenkins But When I launched same tests by Jenkins all tests that want to openbrowser (ff or chrome) are FAIL
Title: Message Title RemiCharles LageixArena updated an issue Jenkins / JENKINS-58765 why jenkins But When I launched same tests by Jenkins all tests that want to openbrowser (ff or chrome) are FAIL Change By: RemiCharles LageixArena Summary: why jenkins launch the build/scriptShell always with root permission? But When I launched same tests by Jenkins all tests that want to openbrowser (ff or chrome) are FAIL 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.201070.1564669421000.7209.1564822500152%40Atlassian.JIRA.
[JIRA] (JENKINS-58765) why jenkins launch the build/scriptShell always with root permission?
Title: Message Title
RemiCharles LageixArena updated an issue
Jenkins / JENKINS-58765
why jenkins launch the build/scriptShell always with root permission?
Change By:
RemiCharles LageixArena
why jenkins When I launch the build/scriptShell always robotframework-seleniumwebdriver all test are PASS.idem when I launched with root permission? CLI commande, tests are PAST. But When I launched same tests by Jenkins all tests that want to openbrowser (ff or chrome) arBut When I launched same tests by Jenkins all tests that want to openbrowser (ff or chrome) are FAILe FAIL whit the following errors{color:#c1c7d0}WebDriverException: Message: invalid argument: can't kill an exited process{color}{color:#c1c7d0}WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.){color}{color:#172b4d}you can see the complet log at the end of this page{color}anyone know a fix?thanks in advance into Configure/build/scriptShell{color:#c1c7d0}_#!/bin/bash_{color} {color:#c1c7d0}_/usr/local/bin/robot /home/ar/eclipse-workspace/ProjectRobot1/test/TestSuite1.robot_{color}but Jenkins run always this script shell with root permission. and the result is FAIL. when I launch the same command on CLI {color:#172b4d}with my user permission the result is PASS{color} {color:#c1c7d0}_/usr/local/bin/robot /home/ar/eclipse-workspace/ProjectRobot1/test/TestSuite1.robot_ {color}{color:#c1c7d0}==TestSuite1 ==MyFirstTest | PASS |--FirstSeleniumTest | PASS |--test1 ...Completed Successfuly with fireFox...Completed Successfuly with Google/Chrometest1 | PASS |--SampleLoginTest :: This is a sample login test | PASS |--The user can search for flights | PASS |--TestSuite1 | PASS |5 critical tests, 5 passed, 0 failed5 tests total, 5 passed, 0 failed==Output: /home/ar/output.xmlLog: /home/ar/log.htmlReport: /home/ar/report.html{color}this is the log when I launch the script by jenkins{color:#c1c7d0} Démarré par l'utilisateur unknown or anonymous{color}{color:#c1c7d0}Running as SYSTEM{color}{color:#c1c7d0}Building in workspace
