[JIRA] [_test] (JENKINS-29359) unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Title: Message Title
Alexey Java updated an issue
Jenkins / JENKINS-29359
unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Change By:
Alexey Java
Itriedsamplecodeatthetopofthispage:https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test{ quote}publicclassAppTest { @RulepublicJenkinsRulej=newJenkinsRule();@Testpublicvoidfirst()throwsException{FreeStyleProjectproject=j.createFreeStyleProject();project.getBuildersList().add(newShell(echohello));FreeStyleBuildbuild=project.scheduleBuild2(0).get();System.out.println(build.getDisplayName()+completed);//TODO:changethistouseHtmlUnitStrings=FileUtils.readFileToString(build.getLogFile());assertThat(s,contains(+echohello)); } } {quote} itfailedwithexceptionwhenitcouldnotcreateafolderinside./targetbecause./targetdoesnotexistinmyprojectfolder.java.lang.Exception:Failedtoinitializeexplodedwaratorg.jvnet.hudson.test.WarExploder.getExplodedDir(WarExploder.java:49)atorg.jvnet.hudson.test.JenkinsRule.createWebServer(JenkinsRule.java:578)atCausedby:java.io.FileNotFoundException:C:\projects\jenkins-publisher-plugin\.\target\jenkins-for-test.exploding(Thesystemcannotfindthepathspecified)atjava.io.FileOutputStream.open(NativeMethod)atjava.io.FileOutputStream.init(FileOutputStream.java:221)atjava.io.FileOutputStream.init(FileOutputStream.java:110)atorg.jvnet.hudson.test.WarExploder.explode(WarExploder.java:99)atorg.jvnet.hudson.test.WarExploder.clinit(WarExploder.java:58)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are
[JIRA] [_test] (JENKINS-29359) unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Title: Message Title
Alexey Java updated an issue
Jenkins / JENKINS-29359
unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Change By:
Alexey Java
Itriedsamplecodeatthetopofthispage:https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test{quote} publicclassAppTest{@RulepublicJenkinsRulej=newJenkinsRule();@Testpublicvoidfirst()throwsException{FreeStyleProjectproject=j.createFreeStyleProject();project.getBuildersList().add(newShell(echohello));FreeStyleBuildbuild=project.scheduleBuild2(0).get();System.out.println(build.getDisplayName()+completed);//TODO:changethistouseHtmlUnitStrings=FileUtils.readFileToString(build.getLogFile());assertThat(s,contains(+echohello));}}{quote}itfailedwithexceptionwhenitcouldnotcreateafolderinside./targetbecause./targetdoesnotexistinmyprojectfolder.bq.java.lang.Exception:Failedtoinitializeexplodedwaratorg.jvnet.hudson.test.WarExploder.getExplodedDir(WarExploder.java:49)atorg.jvnet.hudson.test.JenkinsRule.createWebServer(JenkinsRule.java:578)at bq. Causedby:java.io.FileNotFoundException:C:\projects\jenkins-publisher-plugin\.\target\jenkins-for-test.exploding(Thesystemcannotfindthepathspecified)bq.bq. atjava.io.FileOutputStream.open(NativeMethod)bq.bq. atjava.io.FileOutputStream.init(FileOutputStream.java:221)bq.bq. atjava.io.FileOutputStream.init(FileOutputStream.java:110)bq.bq. atorg.jvnet.hudson.test.WarExploder.explode(WarExploder.java:99)bq.bq. atorg.jvnet.hudson.test.WarExploder.clinit(WarExploder.java:58)bq.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received
[JIRA] [_test] (JENKINS-29359) unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Title: Message Title
Alexey Java updated an issue
Jenkins / JENKINS-29359
unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Change By:
Alexey Java
Itriedsamplecodeatthetopofthispage:https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test{quote}publicclassAppTest{@RulepublicJenkinsRulej=newJenkinsRule();@Testpublicvoidfirst()throwsException{FreeStyleProjectproject=j.createFreeStyleProject();project.getBuildersList().add(newShell(echohello));FreeStyleBuildbuild=project.scheduleBuild2(0).get();System.out.println(build.getDisplayName()+completed);//TODO:changethistouseHtmlUnitStrings=FileUtils.readFileToString(build.getLogFile());assertThat(s,contains(+echohello));}}{quote}itfailedwithexceptionwhenitcouldnotcreateafolderinside./targetbecause./targetdoesnotexistinmyprojectfolder.bq.java.lang.Exception:Failedtoinitializeexplodedwar bq. atorg.jvnet.hudson.test.WarExploder.getExplodedDir(WarExploder.java:49)atorg.jvnet.hudson.test.JenkinsRule.createWebServer(JenkinsRule.java:578)atbq.Causedby:java.io.FileNotFoundException:C:\projects\jenkins-publisher-plugin\.\target\jenkins-for-test.exploding(Thesystemcannotfindthepathspecified)bq.bq. atjava.io.FileOutputStream.open(NativeMethod)bq.bq. atjava.io.FileOutputStream.init(FileOutputStream.java:221)bq.bq. atjava.io.FileOutputStream.init(FileOutputStream.java:110)bq.bq. atorg.jvnet.hudson.test.WarExploder.explode(WarExploder.java:99)bq.bq. atorg.jvnet.hudson.test.WarExploder.clinit(WarExploder.java:58)bq.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received
[JIRA] [_test] (JENKINS-29359) unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Title: Message Title
Alexey Java updated an issue
Jenkins / JENKINS-29359
unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Change By:
Alexey Java
Itriedsamplecodeatthetopofthispage:https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test{quote}publicclassAppTest{@RulepublicJenkinsRulej=newJenkinsRule();@Testpublicvoidfirst()throwsException{FreeStyleProjectproject=j.createFreeStyleProject();project.getBuildersList().add(newShell(echohello));FreeStyleBuildbuild=project.scheduleBuild2(0).get();System.out.println(build.getDisplayName()+completed);//TODO:changethistouseHtmlUnitStrings=FileUtils.readFileToString(build.getLogFile());assertThat(s,contains(+echohello));}}{quote}itfailedwithexceptionwhenitcouldnotcreateafolderinside./targetbecause./targetdoesnotexistinmyprojectfolder. bq. java.lang.Exception:Failedtoinitializeexplodedwaratorg.jvnet.hudson.test.WarExploder.getExplodedDir(WarExploder.java:49)atorg.jvnet.hudson.test.JenkinsRule.createWebServer(JenkinsRule.java:578)atCausedby:java.io.FileNotFoundException:C:\projects\jenkins-publisher-plugin\.\target\jenkins-for-test.exploding(Thesystemcannotfindthepathspecified) bq.bq. atjava.io.FileOutputStream.open(NativeMethod) bq.bq. atjava.io.FileOutputStream.init(FileOutputStream.java:221) bq.bq. atjava.io.FileOutputStream.init(FileOutputStream.java:110) bq.bq. atorg.jvnet.hudson.test.WarExploder.explode(WarExploder.java:99) bq.bq. atorg.jvnet.hudson.test.WarExploder.clinit(WarExploder.java:58) bq.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You
[JIRA] [publish-over-ssh-plugin] (JENKINS-29360) Bump jsch to fix Algorithm negotiation failed
Title: Message Title Christoph B created an issue Jenkins / JENKINS-29360 Bump jsch to fix Algorithm negotiation failed Issue Type: Bug Assignee: bap Components: publish-over-ssh-plugin Created: 11/Jul/15 6:45 AM Priority: Minor Reporter: Christoph B Recent OpenSSH servers running on ubuntu use the following key exchange algorithms KexAlgorithms curve25519-sha...@libssh.org,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 When using the current version (1.13) which uses jsch 0.1.45 the plugin will fail with the message Algorithm negotiation failed. Bumping the dependency to 0.1.53 solves the problem as i.e. diffie-hellman-group-exchange-sha256 was enabled by default in 0.1.51. I rebuilt the 1.13 version with jsch 0.1.53 and it works fine on our Jenkins cluster. Please bump this dependency.
[JIRA] [timestamper-plugin] (JENKINS-28948) Timestamper Menu should be appended to the menu bar
Title: Message Title stevengbrown commented on JENKINS-28948 Re: Timestamper Menu should be appended to the menu bar Alex - thanks for the great suggestion. I'm going to include it in the next release. 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] [_test] (JENKINS-29362) Not able to see the details of the project when going inside the project
Title: Message Title Mangal Singh created an issue Jenkins / JENKINS-29362 Not able to see the details of the project when going inside the project Issue Type: Bug Assignee: Oleg Nenashev Components: _test Created: 11/Jul/15 8:05 AM Priority: Minor Reporter: Mangal Singh Gets the following error: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/gtseq/tools/tomcat/apache-tomcat-7.0.2/webapps/jenkins/WEB-INF/lib/jenkins-core-1.619.jar!/lib/hudson/project/projectActionFloatingBox.jelly:38:74: st:include hudson.model.Run.getIDFormatter()Ljava/text/DateFormat; at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) 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:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) 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:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at
[JIRA] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Mark Waite commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result Thanks very much. I'm surprised that JGit doesn't allow HEAD:master as a valid refspec. I look forward to hearing the results of your investigation. 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] [core] (JENKINS-29300) Slave system info not available when slave temporarily offline
Title: Message Title dogfood commented on JENKINS-29300 Re: Slave system info not available when slave temporarily offline Integrated in jenkins_main_trunk #4211 [FIXED JENKINS-29300] Display system info even when slave is temporarily offline (Revision 48b909dbf03b4ab712d474596d3ea4a215209192) Result = SUCCESS ogondza : 48b909dbf03b4ab712d474596d3ea4a215209192 Files : core/src/main/resources/hudson/slaves/SlaveComputer/systemInfo.jelly test/src/test/java/hudson/cli/ComputerStateTest.java 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] [_test] (JENKINS-29359) unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Title: Message Title
Alexey Java updated an issue
Jenkins / JENKINS-29359
unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Change By:
Alexey Java
Itriedsamplecodeatthetopofthispage:https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test{quote}publicclassAppTest{@RulepublicJenkinsRulej=newJenkinsRule();@Testpublicvoidfirst()throwsException{FreeStyleProjectproject=j.createFreeStyleProject();project.getBuildersList().add(newShell(echohello));FreeStyleBuildbuild=project.scheduleBuild2(0).get();System.out.println(build.getDisplayName()+completed);//TODO:changethistouseHtmlUnitStrings=FileUtils.readFileToString(build.getLogFile());assertThat(s,contains(+echohello));}}{quote}itfailedwithexceptionwhenitcouldnotcreateafolderinside./targetbecause./targetdoesnotexistinmyprojectfolder.bq.java.lang.Exception:Failedtoinitializeexplodedwar atorg.jvnet.hudson.test.WarExploder.getExplodedDir(WarExploder.java:49)atorg.jvnet.hudson.test.JenkinsRule.createWebServer(JenkinsRule.java:578)atorg.jvnet.hudson.test.JenkinsRule.newHudson(JenkinsRule.java:530)atorg.jvnet.hudson.test.JenkinsRule.before(JenkinsRule.java:331)atorg.jvnet.hudson.test.JenkinsRule$2.evaluate(JenkinsRule.java:480)atorg.junit.rules.RunRules.evaluate(RunRules.java:18)atorg.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)atorg.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)atorg.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)atorg.junit.runners.ParentRunner$3.run(ParentRunner.java:231)atorg.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)atorg.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)atorg.junit.runners.ParentRunner.access$000(ParentRunner.java:50)atorg.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)atorg.junit.runners.ParentRunner.run(ParentRunner.java:300)atorg.junit.runner.JUnitCore.run(JUnitCore.java:157)atcom.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:78)atcom.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:212)atcom.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:68)atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)atcom.intellij.rt.execution.CommandLineWrapper.main(CommandLineWrapper.java:130)Causedby:java.io.FileNotFoundException:C:\projects\jenkins-publisher-plugin\.\target\jenkins-for-test.exploding(Thesystemcannotfindthepathspecified)atjava.io.FileOutputStream.open(NativeMethod)atjava.io.FileOutputStream.init(FileOutputStream.java:221)atjava.io.FileOutputStream.init(FileOutputStream.java:110)atorg.jvnet.hudson.test.WarExploder.explode(WarExploder.java:99)atorg.jvnet.hudson.test.WarExploder.clinit(WarExploder.java:58)bq. bq. java.lang.Exception:Failedtoinitializeexplodedwarbq.bq. atorg.jvnet.hudson.test.WarExploder.getExplodedDir(WarExploder.java:49) bq.bq. atorg.jvnet.hudson.test.JenkinsRule.createWebServer(JenkinsRule.java:578) bq.bq. at org.jvnet.hudson.test.JenkinsRule.newHudson(JenkinsRule.java:530)bq. bq. atorg.jvnet.hudson.test.JenkinsRule.before(JenkinsRule.java:331)bq.bq. atorg.jvnet.hudson.test.JenkinsRule$2.evaluate(JenkinsRule.java:480)bq.bq.
[JIRA] [timestamper-plugin] (JENKINS-29361) Timestamper side panel settings not displayed with Jenkins 1.619
Title: Message Title stevengbrown created an issue Jenkins / JENKINS-29361 Timestamper side panel settings not displayed with Jenkins 1.619 Issue Type: Bug Assignee: stevengbrown Components: timestamper-plugin Created: 11/Jul/15 7:36 AM Environment: Jenkins 1.619, Timestamper 1.7 Priority: Major Reporter: stevengbrown Bug report from Duncan Mak I'm running Jenkins 1.619 with Timestamper 1.7 and I just noticed that the panel for toggling the display is no longer rendered. Add Comment
[JIRA] [timestamper-plugin] (JENKINS-28948) Timestamper Menu should be appended to the menu bar
Title: Message Title stevengbrown commented on JENKINS-28948 Re: Timestamper Menu should be appended to the menu bar Thanks for the bug report Duncan, I've raised JENKINS-29361. 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] [timestamper-plugin] (JENKINS-29361) Timestamper side panel settings not displayed with Jenkins 1.619
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-29361 Timestamper side panel settings not displayed with Jenkins 1.619 Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed 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] [timestamper-plugin] (JENKINS-28948) Timestamper Menu should be appended to the menu bar
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28948 Timestamper Menu should be appended to the menu bar Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed 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] [timestamper-plugin] (JENKINS-29361) Timestamper side panel settings not displayed with Jenkins 1.619
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29361 Re: Timestamper side panel settings not displayed with Jenkins 1.619 Code changed in jenkins User: Steven Brown Path: src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory/script.js http://jenkins-ci.org/commit/timestamper-plugin/b254bc8fbcb9e967633769b5c219e4b9b1999d2d Log: [FIXED JENKINS-29361] Display the side panel settings with Jenkins 1.619 Compare: https://github.com/jenkinsci/timestamper-plugin/compare/bbee82c3fcd9...b254bc8fbcb9 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] [timestamper-plugin] (JENKINS-28948) Timestamper Menu should be appended to the menu bar
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28948 Re: Timestamper Menu should be appended to the menu bar Code changed in jenkins User: Steven Brown Path: src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory/script.js http://jenkins-ci.org/commit/timestamper-plugin/03756c03d2e8e42b75e1a926e4d4728926b70d62 Log: [FIXED JENKINS-28948] Display timestamp settings within the side panel 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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Kristian Kraljic commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result Seems that we will have to do in in two pulls anyways. The git-client-plugin pull and another pull for the GitPublisher. The refspec is set by the GitPublisher in line 242: PushCommand push = git.push().to(remoteURI).ref(HEAD: + mergeTarget); In line 382 the right syntax is applied to the refspec: PushCommand push = git.push().to(remoteURI).ref(refs/notes/*); Do you want to look into this, or should I propose a fix create a pull request? 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] [cloudbees-folder-plugin] (JENKINS-25326) Throttle Concurrent Builds doesn't work when builds are in cloudbees folders
Title: Message Title
Austin Ward commented on JENKINS-25326
Re: Throttle Concurrent Builds doesn't work when builds are in cloudbees folders
This seems to be occurring in Line 188 of ThrottleJobProperty.java:
if (/* not deleted /getItem(p.getParent(), p.getName()) == p / has not since been reconfigured */ p.getProperty(ThrottleJobProperty.class) == t) { categoryProjects.add(p); if (p instanceof MatrixProject t.isThrottleMatrixConfigurations()) { for (MatrixConfiguration mc : ((MatrixProject)p).getActiveConfigurations()) { categoryProjects.add((AbstractProject?,?)mc); }
} }
getItem(p.getParent(), p.getName())
Is returning Null when the AbstractProject's parent is a Folder.
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] [timestamper-plugin] (JENKINS-28948) Timestamper Menu should be appended to the menu bar
Title: Message Title stevengbrown updated an issue Jenkins / JENKINS-28948 Timestamper Menu should be appended to the menu bar Change By: stevengbrown Issue Type: Bug Improvement 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] [delivery-pipeline-plugin] (JENKINS-28837) After Successful build task stays covered by dark green progress bar color
Title: Message Title Tommy Tynj commented on JENKINS-28837 Re: After Successful build task stays covered by dark green progress bar color Merged: 57c695a1ae9525ae7bb6973fd1ee01a74a5b362d 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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Kristian Kraljic commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result I dumped the refspec to the console: Pushing HEAD to branch master at repo origin RefSpec is HEAD:master The RefSpec class of JGit mentions: /** * Parse a ref specification for use during transport operations. * p * Specifications are typically one of the following forms: * ul * licoderefs/heads/master/code/li * licoderefs/heads/master:refs/remotes/origin/master/code/li * licoderefs/heads/*:refs/remotes/origin/*/code/li * licode+refs/heads/master/code/li * licode+refs/heads/master:refs/remotes/origin/master/code/li * licode+refs/heads/*:refs/remotes/origin/*/code/li * licode+refs/pull/#42;/head:refs/remotes/origin/pr/*/code/li * licode:refs/heads/master/code/li * /ul * * @param spec *string describing the specification. * @throws IllegalArgumentException * the specification is invalid. */ Which applies that refs/heads/ is mandatory for JGit. Also checking Transport.REFSPEC_PUSH_ALL seems to apply to this pattern: refs/heads/*:refs/heads/* Therefore PUSH_ALL would have (most likely) worked, which does indeed not apply for HEAD:master. I will find out where the refspec is concatenated and try to apply a fix. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-plugin] (JENKINS-29321) Setting an invalid custom refspec with wildcards throws an exception
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-29321 Setting an invalid custom refspec with wildcards throws an exception Change By: Mark Waite Summary: Setting aninvalid customrefspecwithwildcardsthrowsanexception 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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title
Kristian Kraljic edited a comment on JENKINS-20393
Re: Git plugin 2.0 JGit implementation does not publish merge result
Idumpedtherefspectotheconsole:{noformat}PushingHEADtobranchmasteratrepooriginRefSpecisHEAD:master{noformat}The[{{RefSpec}}class|https://github.com/eclipse/jgit/blob/master/org.eclipse.jgit/src/org/eclipse/jgit/transport/RefSpec.java#L104-L122]ofJGitmentions:{code:java}/***Parsearefspecificationforuseduringtransportoperations.*p*Specificationsaretypicallyoneofthefollowingforms:*ul*licoderefs/heads/master/code/li*licoderefs/heads/master:refs/remotes/origin/master/code/li*licoderefs/heads/*:refs/remotes/origin/*/code/li*licode+refs/heads/master/code/li*licode+refs/heads/master:refs/remotes/origin/master/code/li*licode+refs/heads/*:refs/remotes/origin/*/code/li*licode+refs/pull/#42;/head:refs/remotes/origin/pr/*/code/li*licode:refs/heads/master/code/li*/ul**@paramspec*stringdescribingthespecification.*@throwsIllegalArgumentException*thespecificationisinvalid.*/{code}Whichappliesthat{{refs/heads/}}ismandatoryforJGit.Alsochecking{{Transport.REFSPEC_PUSH_ALL}}seemstoapplytothispattern:{code}refs/heads/*:refs/heads/*{code}Therefore PUSH_ALL {{REFSPEC_PUSH_ALL}} wouldhave( mostlikely _mostlikely_ )worked,whichdoesindeednotapplyfor{{HEAD:master}}.Iwillfindoutwheretherefspecis beeing concatenatedandtrytoapplyafix.
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] [_test] (JENKINS-29359) unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Title: Message Title
Alexey Java created an issue
Jenkins / JENKINS-29359
unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
_test
Created:
11/Jul/15 6:27 AM
Priority:
Minor
Reporter:
Alexey Java
I tried sample code at the top of this page: https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test
public class AppTest { @Rule public JenkinsRule j = new JenkinsRule(); @Test public void first() throws Exception
Unknown macro: { FreeStyleProject project = j.createFreeStyleProject(); project.getBuildersList().add(new Shell(echo hello)); FreeStyleBuild build = project.scheduleBuild2(0).get(); System.out.println(build.getDisplayName() + completed); // TODO}
}
it failed with exception when it could not create a folder inside ./target because ./target does not exist in my project folder.
java.lang.Exception: Failed to initialize exploded war at org.jvnet.hudson.test.WarExploder.getExplodedDir(WarExploder.java:49) at org.jvnet.hudson.test.JenkinsRule.createWebServer(JenkinsRule.java:578) at org.jvnet.hudson.test.JenkinsRule.newHudson(JenkinsRule.java:530) at org.jvnet.hudson.test.JenkinsRule.before(JenkinsRule.java:331) at
[JIRA] [cloudbees-folder-plugin] (JENKINS-25326) Throttle Concurrent Builds doesn't work when builds are in cloudbees folders
Title: Message Title
Austin Ward edited a comment on JENKINS-25326
Re: Throttle Concurrent Builds doesn't work when builds are in cloudbees folders
ThisseemstobeoccurringinLine188ofThrottleJobProperty.java: {code:java} if(/*notdeleted*/getItem(p.getParent(),p.getName())==p/*hasnotsincebeenreconfigured*/p.getProperty(ThrottleJobProperty.class)==t){categoryProjects.add(p);if(pinstanceofMatrixProjectt.isThrottleMatrixConfigurations()){for(MatrixConfigurationmc:((MatrixProject)p).getActiveConfigurations()){categoryProjects.add((AbstractProject?,?)mc);}}} {code} {code:java} getItem(p.getParent(),p.getName()) {code} IsreturningNullwhentheAbstractProject'sparentisaFolder.
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] [delivery-pipeline-plugin] (JENKINS-28837) After Successful build task stays covered by dark green progress bar color
Title: Message Title Tommy Tynj resolved as Fixed Jenkins / JENKINS-28837 After Successful build task stays covered by dark green progress bar color Change By: Tommy Tynj Status: InProgress Resolved Resolution: Fixed 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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Mark Waite commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result Could we detect this case in the JGit specific PushCommand and rewrite the push refspec to meet the JGit requirements? For example, could a private JGit refspec fixer method be called in the execute() method so that the scope of the change is limited to only the JGit specific portion of the code? I'd rather not have a more broad change when I believe the JGit implementation is the issue. I'd prefer that you continue investigating and propose a pull request so that I can continue my testing in preparation for the upcoming release of the plugin (and the git client plugin). If you can find a high confidence way to rewrite that PushCommand, then your change would likely be the last change into the git client plugin before its next release. 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] [core] (JENKINS-29359) unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-29359 unit test code on the Wiki page fails with Exception when ./target folder does not exist. Change By: Oleg Nenashev Assignee: OlegNenashev 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] [core] (JENKINS-29359) unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-29359 unit test code on the Wiki page fails with Exception when ./target folder does not exist. Yes, we expect that target exists after the build. O which core version does your plugin depend? Change By: Oleg Nenashev Component/s: core Component/s: _test Labels: testtest-harness 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
[JIRA] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Kristian Kraljic commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result Sounds great. I'm just looking into how we could parse something like HEAD:master. The right way to do it is described here, but this is kind of tedious to do manually. JGit does unfortunately not convert e.g. HEAD or master to ref/heads/master or master to refs/remotes/origin/master. HEAD must be read from git-dir/HEAD while anything else, such as master or any sha-1 hash must find a matching equivalent in the refs. Maybe RefWalk will help, I'll keep you updated about my progress. 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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Kristian Kraljic edited a comment on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result Soundsgreat.I'mjustlookingintohowwecouldparsesomethinglikeHEAD:master.Therightwaytodoitisdescribed[here|http://git-scm.com/docs/gitrevisions#_specifying_revisions],butthisiskindoftedioustodomanually.JGitdoesunfortunatelynotconverte.g.HEAD ormaster toref/heads/masterormastertorefs/remotes/origin/master onit'sown .HEADmustbereadfromgit-dir/HEADwhileanythingelse,suchasmasteroranysha-1hashmustfindamatchingequivalentintherefs.MaybeRefWalkwillhelp,I'llkeepyouupdatedaboutmyprogress. 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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title
Kristian Kraljic edited a comment on JENKINS-20393
Re: Git plugin 2.0 JGit implementation does not publish merge result
Cool.Thanksforfindingthearticle.Shawnbasicallyconfirmsmystatementfromthelastpost,itisveryhardtogetfrommasterorHEADtorefs/heads/master.AdditionallyShawnansweredthequestion,whetherthereisaneasymethodoftheRepositorytolookupthosepaths.Regardinghisstatementbq.IfsomeoneexposedthisportionoftheresolvelogicintheRepositoryclass,IthinkitwouldbeafairlysimplechangeinPushtosupportthisDIWMery.Idon'tknowifthisisavailablemeanwhilelookingatthe[git-scmdocumentation|http://git-scm.com/docs/gitrevisions#_specifying_revisions].But(_andtocometoaconclusion_),Idon'tthinkweshouldgoforaprivateJGitrefspecfixerasyousuggested,hopingthatJGitwillimplementtheDWIMerywayofparsingrefspecs.Asashorttermandeasyfix,Iwouldsuggestchanging:{code:java}PushCommandpush=git.push().to(remoteURI).ref(HEAD:+branchName);{code}In{{GItPushlisher}}to:{code:java}PushCommandpush=git.push().to(remoteURI).ref(refs/heads/+branchName+:refs/heads/+branchName);{code}ThisshouldworkforbothCLIGitandJGit.Whatdoyouthink?Ifyouagree,Iwillprovideapullrequestforthe{{git-plugin}}.:-)IalreadytestedthechangeonmyproductiveJenkinsrunningonJGit.Withsuccess!:-){noformat}+/usr/user/jenkins/tools/jgit.shcommit-a-m'Change'[master5557fa6d89452a01cca3f1e34527afa21e86af39]ChangePushingHEADtobranchmasteratrepooriginRefSpecisrefs/heads/master:refs/heads/masterOpeningconnectionCountingobjectsFindingsourcesGettingsizesCompressingobjectsWritingobjectsremote:ResolvingdeltasFinished:SUCCESS{noformat}Andindeed,the origin repositorywaschanged!
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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title
Kristian Kraljic edited a comment on JENKINS-20393
Re: Git plugin 2.0 JGit implementation does not publish merge result
Cool.Thanksforfindingthearticle.Shawnbasicallyconfirmsmystatementfromthelastpost,itisveryhardtogetfrommasterorHEADtorefs/heads/master.AdditionallyShawnansweredthequestion,whetherthereisaneasymethodoftheRepositorytolookupthosepaths.Regardinghisstatementbq.IfsomeoneexposedthisportionoftheresolvelogicintheRepositoryclass,IthinkitwouldbeafairlysimplechangeinPushtosupportthisDIWMery.Idon'tknowifthisisavailablemeanwhilelookingatthe[git-scmdocumentation|http://git-scm.com/docs/gitrevisions#_specifying_revisions].But(_andtocometoaconclusion_),Idon'tthinkweshouldgoforaprivateJGitrefspecfixerasyousuggested,hopingthatJGitwillimplementtheDWIMerywayofparsingrefspecs.Asashorttermandeasyfix,Iwouldsuggestchanging:{code:java}PushCommandpush=git.push().to(remoteURI).ref(HEAD:+branchName);{code}In{{GItPushlisher}}to:{code:java}PushCommandpush=git.push().to(remoteURI).ref(refs/heads/+branchName+:refs/heads/+branchName);{code}ThisshouldworkforbothCLIGitandJGit.Whatdoyouthink?Ifyouagree,Iwillprovideapullrequestforthe{{git-plugin}}.:-)IalreadytestedthechangeonmyproductiveJenkinsrunningonJGit.Withsuccess!:-) *happy* {noformat}+/usr/user/jenkins/tools/jgit.shcommit-a-m'Change'[master5557fa6d89452a01cca3f1e34527afa21e86af39]ChangePushingHEADtobranchmasteratrepooriginRefSpecisrefs/heads/master:refs/heads/masterOpeningconnectionCountingobjectsFindingsourcesGettingsizesCompressingobjectsWritingobjectsremote:ResolvingdeltasFinished:SUCCESS{noformat}Andindeed,therepositorywaschanged!
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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Kristian Kraljic commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result Cool. Thanks for finding the article. Shawn basically confirms my statement from the last post, it is very hard to get from master or HEAD to refs/heads/master. Additionally Shawn answered the question, whether there is an easy method of the Repository to lookup those paths. Regarding his statement If someone exposed this portion of the resolve logic in the Repository class, I think it would be a fairly simple change in Push to support this DIWMery. I don't know if this is available meanwhile looking at the git-scm documentation. But (and to come to a conclusion), I don't think we should go for a private JGit refspec fixer as you suggested, hoping that JGit will implement the DWIMery way of parsing refspecs. As a short term and easy fix, I would suggest changing: PushCommand push = git.push().to(remoteURI).ref(HEAD:+branchName); In GItPushlisher to: PushCommand push = git.push().to(remoteURI).ref(refs/heads/ + branchName + :refs/heads/ + branchName); This should work for both CLI Git and JGit. What do you think? If you agree, I will provide a pull request for the git-plugin. I already tested the change on my productive Jenkins running on JGit. With success! happy + /usr/user/jenkins/tools/jgit.sh commit -a -m 'Change' [master 5557fa6d89452a01cca3f1e34527afa21e86af39] Change Pushing HEAD to branch master at repo origin RefSpec is refs/heads/master:refs/heads/master Opening connection Counting objects Finding sources Getting sizes Compressing objects Writing objects remote: Resolving deltas Finished: SUCCESS And indeed, the repository was changed! Add Comment
[JIRA] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Mark Waite edited a comment on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result [~kriskra]I'mbiasedagainstachangeintherefspecintheGitPublisherbecausethatchangesthebehaviorforbothCLIgitandJGittodisallowuseofrefs/heads/asaprefixtothebranchname.Ibelievethereareotherplacesinthepluginwhererefs/heads/isallowedastheprefixtoabranchname.MyrationaleforthechangebeinginsidetheJGitimplementation(evenifitisfarlesselegantthanchangingGitPublisher)isthattheJGitimplementationhasneverbeenabletopushunlessauserspecificallyusedrefs/heads/masterastheirbranchname.IfthechangebreaksJGitpush,itwillnotbeanymorebrokenthanitistoday.IftheGitPublisherchangeinadvertentlybreaksausecasefor1%ofthe6+installationsoftheplugin,therewillbe 60+ 600 installationsbroken.I'mgladthechangeinGitPublisherworkedforyou.That'sagoodresult.Unfortunately,therearesomanydiverseusecasesofthegitpluginandthegitclientpluginthatI'munlikelytoallowthattypeofchangeinGitPublisher. 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] [cmakebuilder-plugin] (JENKINS-29267) CMAKE_BUILD_TOOL is deprecated in cmake version 3.0
Title: Message Title Martin Weber started work on JENKINS-29267 Change By: Martin Weber Status: Open InProgress 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] [cmakebuilder-plugin] (JENKINS-29267) CMAKE_BUILD_TOOL is deprecated in cmake version 3.0
Title: Message Title Martin Weber commented on JENKINS-29267 Re: CMAKE_BUILD_TOOL is deprecated in cmake version 3.0 Thanks for the pull request, Philipp. Unfortunately, it also changes the name of the Jenkins environment variable CMAKE_BUILD_TOOL which will (again) break users jobs. 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] [cmakebuilder-plugin] (JENKINS-29329) Visual Studio/MSBuild projects can not be built implicitly anymore
Title: Message Title Martin Weber commented on JENKINS-29329 Re: Visual Studio/MSBuild projects can not be built implicitly anymore cmake --build is not present in cmake 2.x and we want to support RHEL 7, which still is at cmake 2.6.4 IIRC. The automatic recognition of Visual Studio/MSBuild Paths is done by cmake, which does a fairly good job to find all build-tools. This plugin just parses the cmake cache file to find the actual tool to invoke, so the automatic recognition should be fixed in cmake. 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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Mark Waite commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result Kristian Kraljic I'm biased against a change in the refspec in the GitPublisher because that changes the behavior for both CLI git and JGit to disallow use of refs/heads/ as a prefix to the branch name. I believe there are other places in the plugin where refs/heads/ is allowed as the prefix to a branch name. My rationale for the change being inside the JGit implementation (even if it is far less elegant than changing GitPublisher) is that the JGit implementation has never been able to push unless a user specifically used refs/heads/master as their branch name. If the change breaks JGit push, it will not be any more broken than it is today. If the GitPublisher change inadvertently breaks a use case for 1% of the 60 000+ installations of the plugin, there will be 60+ installations broken. I'm glad the change in GitPublisher worked for you. That's a good result. Unfortunately, there are so many diverse use cases of the git plugin and the git client plugin that I'm unlikely to allow that type of change in GitPublisher. 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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Kristian Kraljic commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result Understood and agreed! I'll try to find a semi-elegant way to fix it in JGitAPIImpl. Thanks a lot for your support so far! I'll post a pull request to git-client-plugin some minutes then. 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] [cmakebuilder-plugin] (JENKINS-29267) CMAKE_BUILD_TOOL is deprecated in cmake version 3.0
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-29267 CMAKE_BUILD_TOOL is deprecated in cmake version 3.0 Change By: SCM/JIRA link daemon Status: InProgress Resolved Resolution: Fixed 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] [cmakebuilder-plugin] (JENKINS-29267) CMAKE_BUILD_TOOL is deprecated in cmake version 3.0
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29267 Re: CMAKE_BUILD_TOOL is deprecated in cmake version 3.0 Code changed in jenkins User: 15knots Path: src/main/java/de/marw/cmake/cmakecache/SimpleCMakeCacheTxt.java src/main/java/hudson/plugins/cmake/BuildToolEntryParser.java src/main/java/hudson/plugins/cmake/CmakeBuilder.java src/main/resources/hudson/plugins/cmake/CmakeBuilder/help-generator.html http://jenkins-ci.org/commit/cmakebuilder-plugin/294564856425049b316f2ba75c23fab8c50e5496 Log: [FIXED JENKINS-29267] CMAKE_BUILD_TOOL is deprecated in cmake version 3.0 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-21331) GitHub teams should be available groups for matrix based security when using GitHub OAuth plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-21331 Re: GitHub teams should be available groups for matrix based security when using GitHub OAuth plugin Code changed in jenkins User: Julien Carsique Path: pom.xml src/main/java/org/jenkinsci/plugins/GithubAuthenticationToken.java src/main/java/org/jenkinsci/plugins/GithubOAuthGroupDetails.java src/main/java/org/jenkinsci/plugins/GithubOAuthUserDetails.java src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java http://jenkins-ci.org/commit/github-oauth-plugin/7fea11475da28861ddf1f1e09add6a93a1bbfc6a Log: JENKINS-21331: include teams as groups duplicate: JENKINS-28575 Conflicts: src/main/java/org/jenkinsci/plugins/GithubAuthenticationToken.java src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java 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-28575) GitHub OAuth should include teams as groups
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28575 Re: GitHub OAuth should include teams as groups Code changed in jenkins User: Julien Carsique Path: pom.xml src/main/java/org/jenkinsci/plugins/GithubAuthenticationToken.java src/main/java/org/jenkinsci/plugins/GithubOAuthGroupDetails.java src/main/java/org/jenkinsci/plugins/GithubOAuthUserDetails.java src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java http://jenkins-ci.org/commit/github-oauth-plugin/7fea11475da28861ddf1f1e09add6a93a1bbfc6a Log: JENKINS-21331: include teams as groups duplicate: JENKINS-28575 Conflicts: src/main/java/org/jenkinsci/plugins/GithubAuthenticationToken.java src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java 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-28575) GitHub OAuth should include teams as groups
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28575 Re: GitHub OAuth should include teams as groups Code changed in jenkins User: Sam Gleske Path: pom.xml src/main/java/org/jenkinsci/plugins/GithubAuthenticationToken.java src/main/java/org/jenkinsci/plugins/GithubOAuthGroupDetails.java src/main/java/org/jenkinsci/plugins/GithubOAuthUserDetails.java src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java http://jenkins-ci.org/commit/github-oauth-plugin/bdb98e6215616b678a7c7d44da6d56f9fcda935d Log: Merge PR #41 JENKINS-28575 include GitHub teams as groups closes #36 Compare: https://github.com/jenkinsci/github-oauth-plugin/compare/24a3f6ff02ce...bdb98e621561 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] [cmakebuilder-plugin] (JENKINS-29267) CMAKE_BUILD_TOOL is deprecated in cmake version 3.0
Title: Message Title Martin Weber assigned an issue to Martin Weber Jenkins / JENKINS-29267 CMAKE_BUILD_TOOL is deprecated in cmake version 3.0 Change By: Martin Weber Assignee: MartinWeber 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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Mark Waite edited a comment on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result CouldwedetectthiscaseintheJGitspecificPushCommandandrewritethepushrefspectomeettheJGitrequirements?Forexample,couldaprivateJGitrefspecfixermethodbecalledinthe[execute()method|https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java#L1789]sothatthescopeofthechangeislimitedtoonlytheJGitspecificportionofthecode?I'drathernothaveamorebroadchangewhenIbelievetheJGitimplementationistheissue.I'dpreferthatyoucontinueinvestigatingandproposeapullrequestsothatIcancontinuemytestinginpreparationfortheupcomingreleaseoftheplugin(andthegitclientplugin).IfyoucanfindahighconfidencewaytorewritethatPushCommand,thenyourchangewouldlikelybethelastchangeintothegitclientpluginbeforeitsnextrelease. I've[mergedyourchange|https://github.com/jenkinsci/git-client-plugin/pull/172]tothemasterrepo,and[submittedatest|https://github.com/MarkEWaite/git-client-plugin/commit/e0c6d07dcf95d32c20534ee271f0a828cd2bc4be]anda[revisionofthattest|https://github.com/MarkEWaite/git-client-plugin/commit/85a496fed6f20d57288c67346535eb9fded6bf79]thatshowsthefailuretomyforkoftherepo. 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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Kristian Kraljic edited a comment on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result Soundsgreat.I'mjustlookingintohowwecouldparsesomethinglikeHEAD:master.Therightwaytodoitisdescribed[here|http://git-scm.com/docs/gitrevisions#_specifying_revisions],butthisiskindoftedioustodomanually.JGitdoesunfortunatelynotconverte.g.HEADtoref/heads/masterormastertorefs/remotes/origin/masteronit'sown.HEADmustbereadfromgit-dir/HEADwhileanythingelse,suchasmasteroranysha-1hashmustfindamatchingequivalentintherefs.MaybeRefWalkwillhelp,I'llkeepyouupdatedaboutmyprogress. I'llcontinueonthisinaboutanhour,let'sseeifwecangetafixreadytoday.:-) 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] [jira-plugin] (JENKINS-18166) Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7
Title: Message Title haocheng lee commented on JENKINS-18166 Re: Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7 Hi Andrei Tuicu, I have migrated all the SOAP API to REST API (I tried to use JIRA Java REST client if possible). However, I did not test all the functions yet because I am not using features like changing workflow. This is the branch I am working on: https://github.com/haocheng/jira-plugin/commits/migrate-soap-to-rest Any suggestion or help is appreciated. Thank you! 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] [cmakebuilder-plugin] (JENKINS-29329) Visual Studio/MSBuild projects can not be built implicitly anymore
Title: Message Title Martin Weber commented on JENKINS-29329 Re: Visual Studio/MSBuild projects can not be built implicitly anymore Could you please post the CMAKE_BUILD_TOOL to CMAKE_MAKE_PROGRAM entries from the generated CMakeCache.txt here? 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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Mark Waite commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result Thanks! Shawn Pearce (one of the JGit authors) describes why JGit does not accept HEAD:master in a mail forum from a while ago. It is an interesting read. 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] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Kristian Kraljic commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result Hey Mark, as suggested I have added a fixRefSpec() to JGitAPIImpl, which gets called in the execute method of PushCommand. I have opened a new pull request to git-client-plugin. fixRefSpec() should fix the most common refSpecs for JGit. I decided to simply map HEAD to refs/heads/master or if HEAD:branch is given to refs/heads/branch. This should do the trick for 90% of the use-cases hopefully. A quick collection of fixes: : fixed to: :refs/heads/master master fixed to: refs/heads/master:refs/heads/master :master fixed to: :refs/heads/master HEAD fixed to: refs/heads/master:refs/heads/master HEAD:master fixed to: refs/heads/master:refs/heads/master HEAD:branch fixed to: refs/heads/branch:refs/heads/branch master:master fixed to: refs/heads/master:refs/heads/master branch:branch fixed to: refs/heads/branch:refs/heads/branch master:branch fixed to: refs/heads/master:refs/heads/branch :refs/heads/master fixed to: :refs/heads/master refs/heads/master fixed to: refs/heads/master:refs/heads/master refs/heads/master:master fixed to: refs/heads/master:refs/heads/master master:refs/heads/master fixed to: refs/heads/master:refs/heads/master tags/tag fixed to: refs/tags/tag:refs/tags/tag /tags/tag fixed to: refs/tags/tag:refs/tags/tag I tested the fixing with the original version of git-plugin and it worked flawless! So I think is solution is also quite nice, I guess. Plus not having to fear 60k installations broken, is a releief for my first contribution to the Jenkins community! Could you try to run your new test case on it, to see if it's working propertly? Thanks again and have a great weekend. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received
[JIRA] [nodelabelparameter-plugin] (JENKINS-29363) Groovy Post Build and Label Parameter
Title: Message Title Daniel Beck resolved as Not A Defect This is an issue tracker, not a support site. Please ask your questions on the jenkinsci-users mailing list (as you already did), or in #jenkins on Freenode. Hint: If you want to have a Label Parameter, don't use a String Parameter. Jenkins / JENKINS-29363 Groovy Post Build and Label Parameter Change By: Daniel Beck Status: Open Resolved Assignee: DominikBartholdi Resolution: NotADefect 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
[JIRA] [nodelabelparameter-plugin] (JENKINS-29363) Groovy Post Build and Label Parameter
Title: Message Title capt edgar created an issue Jenkins / JENKINS-29363 Groovy Post Build and Label Parameter Issue Type: Patch Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin Created: 11/Jul/15 6:05 PM Labels: exception Priority: Minor Reporter: capt edgar Hi there I'm running Jenkins version 1.565.2 I'm having a strange problem when dynamically triggering downstream projects I have created a job 'Sports - Core - Scheduled' which accepts 2 parameters. One - called 'Stream' which is for our stream(Source Control stream). This is a choice parameter Two - called 'Product' which is for our products(that we build in our company). This is a Label parameter having 10 nodes(servers) associated to it. When i build this job manually, Jenkins recognises the Label parameter and automatically picks one of the free node from the label and everything works fine. We have about 300 of these sort of jobs for various streams/products scenarios for which i'm writing a Groovy script which calls all these jobs to run dynamically but the following script below is failing to recognise the label parameter and actually assigning someother node which is not even
[JIRA] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Kristian Kraljic commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result Please do so, I still havn't set-up my IDE to work with Jenkins. So I couldn't run the changes locally and had to package/upload the plugin to test. Writing and testing the test cases would be very tedious right now. Thanks in advance! 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] [jenkins-tracker] (JENKINS-29223) FXSEXT.ecf Access Violation on a Windows Slave
Title: Message Title Daniel Beck resolved as Not A Defect Check the configuration of your slave. The Slave Root Directory should be non-empty and point to an existing folder. If that doesn't help, please ask for followup advice on the jenkinsci-users mailing list or in #jenkins on Freenode. You'll have a much larger audience there. Jenkins / JENKINS-29223 FXSEXT.ecf Access Violation on a Windows Slave Change By: Daniel Beck Status: Reopened Resolved Resolution: NotADefect 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] [gradle-jpi-plugin] (JENKINS-29359) unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Title: Message Title Daniel Beck assigned an issue to Daniel Spilker This looks a lot like JENKINS-26331 and been fixed in core as https://github.com/jenkinsci/jenkins/commit/1fae8c072a1e8da360cd10dca8b82d1cd1b00968. A workaround in the Gradle JPI plugin is https://github.com/daspilker/gradle-jpi-plugin/blob/master/src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiExtension.groovy#L131...L137 but it doesn't appear to work on your system. Therefore reassigning to Gradle JPI plugin. Jenkins / JENKINS-29359 unit test code on the Wiki page fails with Exception when ./target folder does not exist. Change By: Daniel Beck Component/s: gradle-jpi-plugin Component/s: core Assignee: DanielSpilker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [git-client-plugin] (JENKINS-20393) Git plugin 2.0 JGit implementation does not publish merge result
Title: Message Title Mark Waite commented on JENKINS-20393 Re: Git plugin 2.0 JGit implementation does not publish merge result I sure can. I think I'll take your table of transformations and create a parameterized unit test to exercise each of those cases. 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] [core] (JENKINS-29359) unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Title: Message Title Alexey Java commented on JENKINS-29359 Re: unit test code on the Wiki page fails with Exception when ./target folder does not exist. my plugin depends on Jenkins Core 1.580.3 here is the source code: https://github.com/alexeyOnGitHub/jenkins-publisher-plugin/blob/ask-integration-testing/src/test/java/org/jenkinsci/plugins/jpp/BuildRunListenerIT.java I do not use Maven for builds (which would create target folder). I use Gradle instead. also, I ran this test from IDEA, which would not necessarily create target folder either. 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] [jenkins-tracker] (JENKINS-29223) FXSEXT.ecf Access Violation on a Windows Slave
Title: Message Title Daniel Beck assigned an issue to Unassigned Jenkins / JENKINS-29223 FXSEXT.ecf Access Violation on a Windows Slave Change By: Daniel Beck Assignee: DanielBeck 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] [gradle-jpi-plugin] (JENKINS-29359) unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Title: Message Title Alexey Java commented on JENKINS-29359 Re: unit test code on the Wiki page fails with Exception when ./target folder does not exist. alright, it's all clear. thanks a lot for your help. 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] [gradle-jpi-plugin] (JENKINS-29359) unit test code on the Wiki page fails with Exception when ./target folder does not exist.
Title: Message Title Alexey Java commented on JENKINS-29359 Re: unit test code on the Wiki page fails with Exception when ./target folder does not exist. adding a link to JIRA JENKINS-26331 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-21331) GitHub teams should be available groups for matrix based security when using GitHub OAuth plugin
Title: Message Title Sam Gleske resolved as Fixed Latest release fixes it. Jenkins / JENKINS-21331 GitHub teams should be available groups for matrix based security when using GitHub OAuth plugin Change By: Sam Gleske Status: Reopened Resolved Resolution: Fixed 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-21331) GitHub teams should be available groups for matrix based security when using GitHub OAuth plugin
Title: Message Title Sam Gleske commented on JENKINS-21331 Re: GitHub teams should be available groups for matrix based security when using GitHub OAuth plugin Fixed in release 0.21. 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-21458) Cannot trigger jobs by POSTing to '.../buildWithParameters' with basic auth when using github-oauth plugin
Title: Message Title Sam Gleske assigned an issue to Sam Gleske Jenkins / JENKINS-21458 Cannot trigger jobs by POSTing to '.../buildWithParameters' with basic auth when using github-oauth plugin Change By: Sam Gleske Assignee: Sam Kottler Gleske 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-21895) Latest LTS causes swarm clients fail to authenticate when using github-oauth
Title: Message Title Sam Gleske commented on JENKINS-21895 Re: Latest LTS causes swarm clients fail to authenticate when using github-oauth Since this issue is over a year old I am closing it. Try using the latest release. If it is still an issue in the latest release then file a new issue and link back to this one. 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-21895) Latest LTS causes swarm clients fail to authenticate when using github-oauth
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-21895 Latest LTS causes swarm clients fail to authenticate when using github-oauth Change By: Sam Gleske Status: Open Resolved Assignee: Sam Kottler Gleske Resolution: Fixed 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-21458) Cannot trigger jobs by POSTing to '.../buildWithParameters' with basic auth when using github-oauth plugin
Title: Message Title Sam Gleske commented on JENKINS-21458 Re: Cannot trigger jobs by POSTing to '.../buildWithParameters' with basic auth when using github-oauth plugin Fixed in release 0.21. GitHub oauth can be used as well as other means for launching builds from the API. Since this issue is over a year old I am closing it. Try using the latest release. If it is still an issue in the latest release then file a new issue and link back to this one. 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-21458) Cannot trigger jobs by POSTing to '.../buildWithParameters' with basic auth when using github-oauth plugin
Title: Message Title Sam Gleske closed an issue as Fixed Jenkins / JENKINS-21458 Cannot trigger jobs by POSTing to '.../buildWithParameters' with basic auth when using github-oauth plugin Change By: Sam Gleske Status: Open Closed Resolution: Fixed 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-17916) NullPointerException when GitHub OAuth Plugin is used
Title: Message Title Sam Gleske assigned an issue to Sam Gleske Jenkins / JENKINS-17916 NullPointerException when GitHub OAuth Plugin is used Change By: Sam Gleske Assignee: Sam Kottler Gleske 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-17916) NullPointerException when GitHub OAuth Plugin is used
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-17916 NullPointerException when GitHub OAuth Plugin is used Change By: Sam Gleske Status: Open Resolved Resolution: Fixed 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-17916) NullPointerException when GitHub OAuth Plugin is used
Title: Message Title Sam Gleske commented on JENKINS-17916 Re: NullPointerException when GitHub OAuth Plugin is used Since this issue is over a year old I am closing it. Try using the latest release. If it is still an issue in the latest release then file a new issue and link back to this one. 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-20883) Can't publish arbitrary URLs
Title: Message Title Sam Gleske commented on JENKINS-20883 Re: Can't publish arbitrary URLs Since this issue is over a year old I am closing it. Try using the latest release. If it is still an issue in the latest release then file a new issue and link back to this one. 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-20883) Can't publish arbitrary URLs
Title: Message Title Sam Gleske assigned an issue to Sam Gleske Jenkins / JENKINS-20883 Can't publish arbitrary URLs Change By: Sam Gleske Assignee: Sam Kottler Gleske 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-23673) Can't configure private projects I own when using Use Github repository permissions option
Title: Message Title Sam Gleske commented on JENKINS-23673 Re: Can't configure private projects I own when using Use Github repository permissions option Since this issue is over a year old I am closing it. Try using the latest release. If it is still an issue in the latest release then file a new issue and link back to this one. 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-20883) Can't publish arbitrary URLs
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-20883 Can't publish arbitrary URLs Change By: Sam Gleske Status: Open Resolved Resolution: Fixed 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-23673) Can't configure private projects I own when using Use Github repository permissions option
Title: Message Title Sam Gleske assigned an issue to Sam Gleske Jenkins / JENKINS-23673 Can't configure private projects I own when using Use Github repository permissions option Change By: Sam Gleske Assignee: Sam Kottler Gleske 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-24010) github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus'
Title: Message Title Sam Gleske assigned an issue to Sam Gleske Jenkins / JENKINS-24010 github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus' Change By: Sam Gleske Assignee: Sam Kottler Gleske 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-24010) github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus'
Title: Message Title Sam Gleske commented on JENKINS-24010 Re: github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus' Since this issue is old I am closing it. Try using the latest release. If it is still an issue in the latest release then file a new issue and link back to this one. Using matrix-based authorization is now documented. 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-24010) github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus'
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-24010 github oauth with 'Github Commiter Authorization Strategy' does not have a setting for allowing anonymous access to just the 'ViewStatus' Change By: Sam Gleske Status: Open Resolved Resolution: Fixed 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] [email-ext-plugin] (JENKINS-29325) Excluded Recipients Receive Notifications
Title: Message Title Alex Earl commented on JENKINS-29325 Re: Excluded Recipients Receive Notifications Can you please provide a build log and config.xml for the job? The email-ext xml file from JENKINS_HOME would also be useful. 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-24866) github-oauth does not work behind proxies nor authentication proxies
Title: Message Title Sam Gleske commented on JENKINS-24866 Re: github-oauth does not work behind proxies nor authentication proxies Since this issue is old I am closing it. Try using the latest release. If it is still an issue in the latest release then file a new issue and link back to this one. 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-25459) Authorization by Github Commiter strategy broken.
Title: Message Title Sam Gleske commented on JENKINS-25459 Re: Authorization by Github Commiter strategy broken. Since this issue is old I am closing it. Try using the latest release. If it is still an issue in the latest release then file a new issue and link back to this one. 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-24069) Improve performance by caching and reducing number of github api calls
Title: Message Title Sam Gleske resolved as Fixed The fix has been released today in version 0.21. Jenkins / JENKINS-24069 Improve performance by caching and reducing number of github api calls Change By: Sam Gleske Status: Open Resolved Resolution: Fixed 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-24069) Improve performance by caching and reducing number of github api calls
Title: Message Title Sam Gleske assigned an issue to Sam Gleske Jenkins / JENKINS-24069 Improve performance by caching and reducing number of github api calls Change By: Sam Gleske Assignee: Sam Kottler Gleske 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-23672) Jobs page load takes ages when Use Github repository permissions is checked
Title: Message Title Sam Gleske assigned an issue to Sam Gleske Jenkins / JENKINS-23672 Jobs page load takes ages when Use Github repository permissions is checked Change By: Sam Gleske Assignee: Sam Kottler Gleske 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-25459) Authorization by Github Commiter strategy broken.
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-25459 Authorization by Github Commiter strategy broken. Change By: Sam Gleske Status: Open Resolved Resolution: Fixed 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-25459) Authorization by Github Commiter strategy broken.
Title: Message Title Sam Gleske assigned an issue to Sam Gleske Jenkins / JENKINS-25459 Authorization by Github Commiter strategy broken. Change By: Sam Gleske Assignee: Sam Kottler Gleske 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] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-25791 User.impersonate throws ClassCastException when using GitHub auth Change By: Sam Gleske Status: Open Resolved Assignee: Sam Kottler Gleske Resolution: Fixed 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] [core] (JENKINS-25791) User.impersonate throws ClassCastException when using GitHub auth
Title: Message Title Sam Gleske commented on JENKINS-25791 Re: User.impersonate throws ClassCastException when using GitHub auth Since this issue is old I am closing it. Try using the latest release. If it is still an issue in the latest release then file a new issue and link back to this one. 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-23672) Jobs page load takes ages when Use Github repository permissions is checked
Title: Message Title Sam Gleske closed an issue as Duplicate Jenkins / JENKINS-23672 Jobs page load takes ages when Use Github repository permissions is checked Change By: Sam Gleske Status: Open Closed Resolution: Duplicate 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-26789) Upcoming GitHub API changes
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-26789 Upcoming GitHub API changes Change By: Sam Gleske Status: Open Resolved Resolution: Fixed 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-26789) Upcoming GitHub API changes
Title: Message Title Sam Gleske commented on JENKINS-26789 Re: Upcoming GitHub API changes The upcoming changes would have affected the plugin. The release 0.21 should resolve it. 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-26789) Upcoming GitHub API changes
Title: Message Title Sam Gleske assigned an issue to Sam Gleske Jenkins / JENKINS-26789 Upcoming GitHub API changes Change By: Sam Gleske Assignee: Sam Kottler Gleske 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-27045) Cannot use jenkins-cli with github oauth plugin
Title: Message Title Sam Gleske assigned an issue to Sam Gleske Jenkins / JENKINS-27045 Cannot use jenkins-cli with github oauth plugin Change By: Sam Gleske Assignee: Sam Kottler Gleske 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-27045) Cannot use jenkins-cli with github oauth plugin
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-27045 Cannot use jenkins-cli with github oauth plugin Change By: Sam Gleske Status: Open Resolved Resolution: Fixed 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-27045) Cannot use jenkins-cli with github oauth plugin
Title: Message Title Sam Gleske commented on JENKINS-27045 Re: Cannot use jenkins-cli with github oauth plugin Jenkins CLI no longer uses --username and --password options. It now only using SSH key authentication. Additionally, github oauth plugin 0.21 now supports using personal access tokens instead of a password for interacting with the Jenkins API. I'm going to close this as resolved. 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-14524) Slave agent authorization 401
Title: Message Title Sam Gleske resolved as Fixed Jenkins / JENKINS-14524 Slave agent authorization 401 Change By: Sam Gleske Status: Open Resolved Resolution: Fixed 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-14524) Slave agent authorization 401
Title: Message Title Sam Gleske commented on JENKINS-14524 Re: Slave agent authorization 401 Since the latest LTS release of Jenkins is 1.609.1 and it was reported to work okay in 1.590 I'm closing this as resolved. If you feel it is not resolved then feel free to re-open the issue. 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-13354) Jenkins very slow when not an admin
Title: Message Title Sam Gleske resolved as Fixed Since this issue is old I am closing it. Try using the latest release. If it is still an issue in the latest release then file a new issue and link back to this one. Jenkins / JENKINS-13354 Jenkins very slow when not an admin Change By: Sam Gleske Status: Open Resolved Resolution: Fixed 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.
