[JIRA] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title Tadej Janež commented on JENKINS-34268 Re: Lock multiple resources using the Pipeline lock step Antonio Muñiz, oh, I see. Still, it would be great if one could set properties/environement variables for each resource and they would then be accessible within the lock execution block. Or it that possible already? 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-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title Tadej Janež commented on JENKINS-34268 Re: Lock multiple resources using the Pipeline lock step David Haney, I think the problem you mention would be solved by pursuing merging PR #20 tracked by JENKINS-31437. 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] [github-branch-source-plugin] (JENKINS-35668) Support configuring parameterized build
Title: Message Title Tadej Janež updated an issue Jenkins / JENKINS-35668 Support configuring parameterized build Change By: Tadej Janež It would be very useful if projects created with the GitHub Branch Source Plugin had a way to configure a [ parameterized build |https://wiki . jenkins-ci.org/display/JENKINS/Parameterized+Build]. In my use case, I'm building a project that needs the "glue" project to run the End-to-End tests. The parameter would represent the "glue" project's branch to use when performing a git checkout. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-branch-source-plugin] (JENKINS-35668) Support configuring parameterized build
Title: Message Title Tadej Janež created an issue Jenkins / JENKINS-35668 Support configuring parameterized build Issue Type: Bug Assignee: Jesse Glick Components: github-branch-source-plugin Created: 2016/Jun/13 11:22 AM Priority: Minor Reporter: Tadej Janež It would be very useful if projects created with the GitHub Branch Source Plugin had a way to configure a parameterized build. In my use case, I'm building a project that needs the "glue" project to run the End-to-End tests. The parameter would represent the "glue" project's branch to use when performing a git checkout. Add Comment
[JIRA] [lockable-resources-plugin] (JENKINS-29208) Enhancement: add field for environment variables to the resource configuration
Title: Message Title Tadej Janež commented on JENKINS-29208 Re: Enhancement: add field for environment variables to the resource configuration Is this the same as JENKINS-31437? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-oauth-plugin] (JENKINS-27118) Exception due to https://api.github.com/repos/owner/repo/collaborators not found
Title: Message Title Tadej Janež commented on JENKINS-27118 Re: Exception due to https://api.github.com/repos/owner/repo/collaborators not found I've updated to the latest LTS version of Jenkins (1.609.1) and the latest version of all the plugins and the issue still remains... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [github-oauth-plugin] (JENKINS-27118) Exception due to https://api.github.com/repos/owner/repo/collaborators not found
Tadej Janež created JENKINS-27118 Exception due to https://api.github.com/repos/owner/repo/collaborators not found Issue Type: Bug Assignee: Sam Kottler Components: github-oauth-plugin Created: 25/Feb/15 9:48 AM Description: I'm seeing the following exception when a certain user tries to log-in via the GitHub OAuth plugin: Feb 25, 2015 8:57:19 AM SEVERE org.jenkinsci.plugins.GithubAuthenticationToken hasRepositoryPermission an exception was thrown java.util.concurrent.ExecutionException: java.io.FileNotFoundException: https://api.github.com/repos/genialis/genesis/collaborators at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111) at com.google.common.util.concurrent.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:132) at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2381) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764) at org.jenkinsci.plugins.GithubAuthenticationToken.hasRepositoryPermission(GithubAuthenticationToken.java:161) at org.jenkinsci.plugins.GithubRequireOrganizationMembershipACL.hasRepositoryPermission(GithubRequireOrganizationMembershipACL.java:246) at org.jenkinsci.plugins.GithubRequireOrganizationMembershipACL.hasPermission(GithubRequireOrganizationMembershipACL.java:92) at hudson.security.ACL.hasPermission(ACL.java:68) at hudson.model.AbstractItem.hasPermission(AbstractItem.java:504) at jenkins.model.Jenkins.getItem(Jenkins.java:2321) at hudson.model.Hudson.getJob(Hudson.java:142) at sun.reflect.GeneratedMethodAccessor300.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) 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 org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at
[JIRA] [github-oauth-plugin] (JENKINS-27118) Exception due to https://api.github.com/repos/owner/repo/collaborators not found
Tadej Janež updated JENKINS-27118 Exception due to https://api.github.com/repos/owner/repo/collaborators not found This is the screen a user gets when this exception happens. Change By: Tadej Janež (25/Feb/15 10:10 AM) Attachment: JenkinsGitHubOAuthpluginproblem.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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.
