[JIRA] [credentials] (JENKINS-25176) I can't store the private key in job configure page
Mark Waite commented on JENKINS-25176 I cant store the private key in job configure page I cannot duplicate the problem in the case I tested. Here are the steps I tried install Jenkins 1.583 in a container on my Ubuntu 14.04 Linux machine. install Git plugin on that Jenkins instance, and restart define a new job, and configure it to use git for SCM enter a valid, secured git repository and confirm that it warns about it not being accessible use the Add button from firefox 33.0 and from google chrome stable and add a credential choose the newly added credential from the drop down list (newly added credential was not made the chosen credential after it was added) save the job This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Kanstantsin Shautsou reopened JENKINS-18138 Value is not stored as parameter for later use Entered value must be stored without modification Change By: Kanstantsin Shautsou (17/Oct/14 6:58 AM) Resolution: NotADefect Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [label-linked-jobs] (JENKINS-25188) Orphaned jobs do not show jobs without label when all nodes set to Labe restrictions
Herbert Quartel created JENKINS-25188 Orphaned jobs do not show jobs without label when all nodes set to Labe restrictions Issue Type: Bug Assignee: Dominique Brice Components: label-linked-jobs Created: 17/Oct/14 7:36 AM Description: When all nodes in Jenkins are configured with Usage : Only run jobs with Label restrictions, then jobs without a label are not shown in the Labels Dashboard under orphaned jobs. I think these jobs should be listed under orphanded jobs, since these jobs will remain waiting. Environment: Jenkins ver. 1.583 , label linked ver. 2.0.4 Project: Jenkins Labels: plugin job gui user-experience Priority: Major Reporter: Herbert Quartel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [label-linked-jobs] (JENKINS-25188) Orphaned jobs do not show jobs without label when all nodes set to Label restrictions
Herbert Quartel updated JENKINS-25188 Orphaned jobs do not show jobs without label when all nodes set to Label restrictions Change By: Herbert Quartel (17/Oct/14 7:36 AM) Summary: Orphanedjobsdonotshowjobswithoutlabelwhenallnodessetto Labe Label restrictions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-25189) Incorrect promotions when using several criteria promotions with the option When the following downstream projects build successfully
Félix Belzunce Arcos created JENKINS-25189 Incorrect promotions when using several criteria promotions with the option When the following downstream projects build successfully Issue Type: Bug Assignee: Unassigned Components: promoted-builds Created: 17/Oct/14 9:01 AM Description: To reproduce this bug you need to: Create two different promotion processes in the same job, creating in both as criteria "When the following downstream projects build successfully" In the promotion process A, fill a project that exists on Jenkins. In the promotion process B, fill a project which doesn't exist. Then the result is that both promotions happens even in the promotion process B where the project didn't exist. Project: Jenkins Priority: Minor Reporter: Félix Belzunce Arcos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11097) Jobs get aborted with Command close created as cause in the stacktrace
wbauer commented on JENKINS-11097 Jobs get aborted with Command close created as cause in the stacktrace This issue is fairly new and looks similar: https://issues.jenkins-ci.org/browse/JENKINS-24761 I see this sporadically on a 1.572 master (RHEL 6.5) and our Windows slaves, Linux and Mac slaves are fine. Was not able to pinpoint how, when or why yet . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-24761) Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
wbauer commented on JENKINS-24761 Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown I see this as well, master is RHEL 6.5 linux jenkins version 1.572 and only windows slaves are affected (look s like they loose connection sporadically). Mac and Linux slaves are fine. I was not able to consistently reproduce or pinpoint how, when or why this happens yet - due to time constraints. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber] (JENKINS-25190) Jabber Plugin not working after Upgrade to 1.584
R. H. created JENKINS-25190 Jabber Plugin not working after Upgrade to 1.584 Issue Type: Bug Assignee: kutzi Components: jabber Created: 17/Oct/14 9:52 AM Description: I have the problem that after the upgrade to Jenkins 1.584 the Jabber notification isn't working anymore. After restart i get the following messages in the log: Failed to scout hudson.plugins.jabber.im.transport.JabberPublisher java.lang.UnsupportedClassVersionError: org/jivesoftware/smack/Roster$SubscriptionMode : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:643) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:756) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) at hudson.plugins.jabber.im.transport.JabberPublisherDescriptor.clinit(JabberPublisherDescriptor.java:75) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:270) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:677) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:337) at hudson.ExtensionList.load(ExtensionList.java:300) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.iterator(ExtensionList.java:143) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:336) at hudson.ExtensionList.load(ExtensionList.java:300) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.get(ExtensionList.java:158) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1203) at hudson.maven.PluginImpl.init(PluginImpl.java:58) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:885) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) And the Plugin isn't loading anymore. Project: Jenkins Labels: Jabber Priority: Critical Reporter: R. H. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [xcode] (JENKINS-22130) keychain with the same name already exists error with developer profile import
Younes Nouri Soltan commented on JENKINS-22130 keychain with the same name already exists error with developer profile import It worked for me too. security delete-keychain jenkins-jobName The problem is that if the build crashes for any other reason it removes the jobName and on the next build Let's say that the other problem was causing the crash has been fixed 'security delete-keychain jenkins-jobName' tries to remove jobName which has been removed on last build already and therefore it crashes again since it can't find the jobName. Is there anyway to ensure that jobName does extist before trying to delete it? Or any other ideas please? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode] (JENKINS-22130) keychain with the same name already exists error with developer profile import
Younes Nouri Soltan edited a comment on JENKINS-22130 keychain with the same name already exists error with developer profile import It worked for me too. security delete-keychain jenkins-jobName The problem is that if the build crashes (for any other reason) it removes the jobName and on the next build (Let's say that the other problem was causing the crash has been fixed) 'security delete-keychain jenkins-jobName' tries to remove jobName which has been removed on last build already and therefore it crashes again since it can't find the jobName. Is there anyway to ensure that jobName does exist before trying to delete it? Or any other ideas please? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Leandro Lucarella commented on JENKINS-24954 Test PASSed comments added even if Published Jenkins URL Cool! Thanks a lot! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
Daniel Beck commented on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher The linked fix should only affect use of Basic Auth, which isn't part of regular login procedure. Weird. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Daniel Beck commented on JENKINS-18138 Value is not stored as parameter for later use Kanstantsin Shautsou Could you explain in more detail why you're reopening this, what the problem is? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24752) NodeProvisioner algorithm is suboptimal for fast one-off cloud
stephenconnolly commented on JENKINS-24752 NodeProvisioner algorithm is suboptimal for fast one-off cloud https://github.com/jenkinsci/jenkins/pull/1433 is a refactoring of NodeProvisioner that makes the strategy plugable This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter] (JENKINS-25182) HTTP 400 bad request error occurs, while integrate the jira test result reporter plugin with Jenkins tool v1.58.
Praveen Lakshmanan updated JENKINS-25182 HTTP 400 bad request error occurs, while integrate the jira test result reporter plugin with Jenkins tool v1.58. Change By: Praveen Lakshmanan (17/Oct/14 11:16 AM) Description: IveconfiguredjiratestresultreporterpluginwithJenkins,afterbuildgetsfailedImfacingHTTP400badrequesterrorissue.Versions:Jenkinsver.1.580JiraTestResultReporterplugin1.0.5JIRA:6.4ConsoleOutput:[JiraTestResultReporter][DEBUG][JiraTestResultReporter][DEBUG]CreatingissueinprojectQAAatURLhttps://guidanz.atlassian.net/rest/api/2/issue/[JiraTestResultReporter][INFO]Reportingissue.[JiraTestResultReporter][DEBUG]statusLine:HTTP/1.1400BadRequest[JiraTestResultReporter][DEBUG]statusCode:400ERROR:PublisherJiraTestResultReporter.JiraReporterabortedduetoexceptionjava.lang.RuntimeException:[JiraTestResultReporter][ERROR]Failed:HTTPerrorcode:400 atJiraTestResultReporter.JiraReporter.createJiraIssue(JiraReporter.java:188) atJiraTestResultReporter.JiraReporter.perform(JiraReporter.java:108) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) athudson.model.Build$BuildExecution.post2(Build.java:183) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) athudson.model.Run.execute(Run.java:1770) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240)Noemailsweretriggered.Finished:FAILURE Forreferencecheckattachedconfiguredscreenshots. Attachment: postbuildconif.jpg Attachment: JIRAconfigure.jpeg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Kanstantsin Shautsou commented on JENKINS-18138 Value is not stored as parameter for later use This plugin is injecting variables in form of artifactname+tail, so when artifactname has dash this variable become unusuable for shell. If i'm entering input value name as KEY then it must be a KEY, no magic substitution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
您好：提供税据办理.;刘会计13713547301 扣Q:3050319691
ih 2014-10-17 -- 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] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Daniel Beck commented on JENKINS-18138 Value is not stored as parameter for later use This plugin is injecting variables in form of artifactname+tail, so when artifactname has dash this variable become unusuable for shell. It uses the parameter name for it, not the artifact name. If i'm entering input value name as KEY then it must be a KEY, no magic substitution. As they say in Wikipedia: citation needed. Its behavior is documented in the inline help, and the ParameterDefinition Javadoc only states: The actual meaning and the purpose of parameters are entirely up to users, so what the concrete parameter implmentation is pluggable. Write subclasses in a plugin and put Extension on the descriptor to register them. FWIW If you want parameter name = env variable set with input, that's a minor improvement at best, not a blocker bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Kanstantsin Shautsou edited a comment on JENKINS-18138 Value is not stored as parameter for later use This plugin is injecting variables in form of artifactname+tail. If i'm entering input value name as KEY then it must be a KEY, no magic substitution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Ivalid Object ID in remoting module
Steven Craft
commented on JENKINS-23271
Intermittent Ivalid Object ID in remoting module
I have Jenkins running on a Windows server, and nearly all the jobs running on OSX slaves. I have the same problem as this, although I don't use Clearcase, I use Mercurial, and it happens during the source control part of the job.
Code $ /usr/local/bin/hg showconfig paths.default
Code $ /usr/local/bin/hg pull --rev default
Code $ /usr/local/bin/hg update --clean --rev default
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
Code $ /usr/local/bin/hg log --rev . --template {node}
Code $ /usr/local/bin/hg log --rev . --template {rev}
Code $ /usr/local/bin/hg log --rev e602dc169d029778c53905f0fc6815f18696ec5e
Code $ /usr/local/bin/hg log --template "changeset node='{node}' author='{author|xmlescape}' rev='{rev}' date='{date}'msg{desc|xmlescape}/msgadded{file_adds|stringify|xmlescape}/addeddeleted{file_dels|stringify|xmlescape}/deletedfiles{files|stringify|xmlescape}/filesparents{parents}/parents/changeset\n" --rev default:0 --follow --prune e602dc169d029778c53905f0fc6815f18696ec5e --encoding UTF-8 --encodingmode replace
FATAL: Invalid object ID 38179 iota=38180
java.lang.IllegalStateException: Invalid object ID 38179 iota=38180
at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:304)
at hudson.remoting.ExportTable.get(ExportTable.java:288)
at hudson.remoting.Channel.getExportedObject(Channel.java:596)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:301)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:290)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:249)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:695)
Caused by: java.lang.Exception: Object was recently deallocated
#38179 (ref.0) : hudson.Launcher$RemoteLaunchCallable$1
Created at Fri Oct 17 12:24:08 BST 2014
at hudson.remoting.ExportTable$Entry.init(ExportTable.java:91)
at hudson.remoting.ExportTable.export(ExportTable.java:266)
at hudson.remoting.Channel.export(Channel.java:592)
at hudson.remoting.Channel.export(Channel.java:583)
at hudson.remoting.Channel.export(Channel.java:553)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1137)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1100)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:695)
Released at Fri Oct 17 12:24:08 BST 2014
at hudson.remoting.ExportTable$Entry.release(ExportTable.java:125)
at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:332)
at hudson.remoting.Channel.unexport(Channel.java:600)
at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38)
at hudson.remoting.Channel$2.handle(Channel.java:475)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)
Caused by: Command hudson.remoting.UnexportCommand@5a5d0d74 created at
at hudson.remoting.Command.init(Command.java:67)
at hudson.remoting.Command.init(Command.java:50)
at hudson.remoting.UnexportCommand.init(UnexportCommand.java:33)
at hudson.remoting.RemoteInvocationHandler.finalize(RemoteInvocationHandler.java:229)
at
[JIRA] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use
Kanstantsin Shautsou updated JENKINS-18138 Value is not stored as parameter for later use Change By: Kanstantsin Shautsou (17/Oct/14 11:34 AM) Priority: Blocker Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-25191) Git plugin does not correctly record built revision on failed merge
Wannes Sels created JENKINS-25191 Git plugin does not correctly record built revision on failed merge Issue Type: Bug Assignee: Wannes Sels Components: git Created: 17/Oct/14 12:14 PM Description: If the plugin has to merge with multiple branches, and at least 1 merge succeeds and 1 fails, then the revision of the last successful merge is recorded as lastBuiltRevision, but not the original (marked) revision. Because the original revision is not recognized as already built, polling will trigger another build, resulting in an infinite loop. Environment: git plugin 2.2.6 Project: Jenkins Priority: Minor Reporter: Wannes Sels This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
Daniel Beck commented on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher Well, the reverse proxy auth bit was missing from the description. So there's actually a simple workaround? Just don't use Apache for authentication? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Daniel Beck updated JENKINS-23271 Intermittent Invalid Object ID in remoting module Change By: Daniel Beck (17/Oct/14 12:31 PM) Summary: Intermittent Ivalid Invalid ObjectIDinremotingmodule This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-25192) Trigger are always run after finalize
William Bernardet created JENKINS-25192 Trigger are always run after finalize Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 17/Oct/14 12:35 PM Description: We are currently trying to trigger a build as post action using parameters from a property file generated in the workspace during the build. As last post action the job uses the workspace cleanup plugin. The issue is that the cleanup is done before the triggering. Which leads to never trigger the sub build... So the following setting is the plugin doesn't make sense with the "Parameters from a property" option. https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/main/java/hudson/plugins/parameterizedtrigger/BuildTrigger.java#L41 Would it be possible to change the returned value to false to the notifier gets executed in correct order... Project: Jenkins Priority: Critical Reporter: William Bernardet This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall commented on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher I don't think that's a good idea. We now have our development setup in such a way that 4 (Jenkins, Gerrit, wiki and bugtraker) sites share the same authentication mechanism. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall commented on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher I did actually mention in the environment description that authentication is done by Apache and passed on to Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18198) Concurrent Build completion is blocked by in-progress earlier Build # of same build.
Daniel Beck
resolved JENKINS-18198 as Not A Defect
Concurrent Build completion is blocked by in-progress earlier Build # of same build.
With a simple "sleep a random time between 0 and 200 seconds, then finish" project that builds in parallel, build #3 and #6 finished before #1, #2, #4 and #5, without waiting for them. This was on Jenkins 1.584.
The behavior you're seeing is very likely controlled by the configured post-build steps. For a long time, email sending (both Mailer and email-ext IIRC) blocked build completion because it wanted to make sure to use the correct subject ("Failed" vs. "Still Failing"). AFAIK this was changed, leading to potentially slightly wrong email subjects.
Not a core bug, and more information on the job configuration is needed to investigate further. Issues should be filed against the responsible post-build action plugins.
Change By:
Daniel Beck
(17/Oct/14 12:42 PM)
Status:
Open
Resolved
Resolution:
NotADefect
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16220) With Concurrent Builds enabled, faster builds won't fully complete until slower builds are done.
Daniel Beck updated JENKINS-16220 With Concurrent Builds enabled, faster builds wont fully complete until slower builds are done. Change By: Daniel Beck (17/Oct/14 12:42 PM) Component/s: postbuild-task This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-merge-request-jenkins] (JENKINS-25193) Use HTTP(s) URL option not visible
Tomas Kislan created JENKINS-25193 Use HTTP(s) URL option not visible Issue Type: Bug Assignee: Unassigned Attachments: jenkins-gitlab-merge-request-builder.png Components: gitlab-merge-request-jenkins Created: 17/Oct/14 12:44 PM Description: Option to use HTTP urls instead of SSH is not visible in job configuration Environment: Jenkins ver. 1.584 Gitlab merge request builder 1.2.2 Linux gold 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Project: Jenkins Priority: Minor Reporter: Tomas Kislan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16220) With Concurrent Builds enabled, faster builds won't fully complete until slower builds are done.
Daniel Beck
resolved JENKINS-16220 as Not A Defect
With Concurrent Builds enabled, faster builds wont fully complete until slower builds are done.
The behavior you're seeing is deliberate by the configured post-build steps. For a long time, email sending (both Mailer and email-ext IIRC) blocked build completion because it wanted to make sure to use the correct subject ("Failed" vs. "Still Failing"). AFAIK this was changed, leading to potentially slightly wrong email subjects.
Unless the post-build steps are provided by core (and actually have no reason to wait), this is not a core bug, and more information on the job configuration is needed to investigate further. Separate issues should be filed against the responsible post-build action plugins so their authors can investigate further. Some post-build actions may well need this synchronization, while for others, it provides less value than faster build completion.
Change By:
Daniel Beck
(17/Oct/14 12:45 PM)
Status:
Open
Resolved
Resolution:
NotADefect
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall edited a comment on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher I don't think that's a good idea. We now have our development environment setup in such a way that 4 (Jenkins, Gerrit, wiki and bugtraker) sites share the same authentication mechanism. Changing that would result in a lot of broken URLs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16143) Jenkins escapes 2 dollar signs in the Parameterized Build fields
Daniel Beck commented on JENKINS-16143 Jenkins escapes 2 dollar signs in the Parameterized Build fields This appears to not be a bug. Compare the parameter values $JENKINS_URL and $$JENKINS_URL. Jenkins internally resolves placeholders in variables, and dollars are used for that. $$ is an escaped $. I could offer better documentation though, as this behavior does not seem to be documented in the String Parameter's inline help, but should be. WDYT? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
Daniel Beck commented on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher Right, sorry about that. Steps to reproduce looked so complete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16143) Jenkins escapes 2 dollar signs in the Parameterized Build fields
Daniel Beck
commented on JENKINS-16143
Jenkins escapes 2 dollar signs in the Parameterized Build fields
Relevant Groovy system script (a build step added by Groovy plugin):
def build = Thread.currentThread().executable
def tl = new hudson.util.LogTaskListener(java.util.logging.Logger.getLogger("foo"), java.util.logging.Level.INFO)
println build.getEnvironment(tl).get("STR1")
println build.getEnvironment(tl).get("STR2")
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-25192) Trigger are always run after finalize
Daniel Beck updated JENKINS-25192 Trigger are always run after finalize AFAIU the problem is that only after finalization, the build result is unmodifiable (which is a requirement of "Trigger when build is:"). Reducing priority due to straightforward workaround: Do not delete the file with the parameters. Workspace Cleanup is extremely configurable. Change By: Daniel Beck (17/Oct/14 1:08 PM) Priority: Critical Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-25192) Trigger are always run after finalize
Daniel Beck updated JENKINS-25192 Trigger are always run after finalize Appears to not be a bug, but deliberate. Change By: Daniel Beck (17/Oct/14 1:09 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10912) Browser/JS memory leak in dashboard
Danny Staple
commented on JENKINS-10912
Browser/JS memory leak in dashboard
I've seen this here too.
The partial fix with innerHtml (which is the same as this stack overflow thing here: http://stackoverflow.com/a/3785323/490188) perhaps plus Douglas Crockford's purge method might mitigate this.
My simpler and brute force fix is a GreaseMonkey script:
if(location.pathname.indexOf('config') == -1) {
//Reload every hour
window.setTimeout(function() {location.reload()}, 1000 * 60 * 60)
}
Which will do for some of our extreme feedback monitors, or accidentally leaving it open overnight in a browser tab.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11851) More options for default parameters
Daniel Beck commented on JENKINS-11851 More options for default parameters Please submit suggested code changes as pull requests on GitHub. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11854) Getting the original name of the file parameter as a parameter as well
Daniel Beck resolved JENKINS-11854 as Cannot Reproduce Getting the original name of the file parameter as a parameter as well The original file name is provided in an environment variable of the same name as the parameter. Change By: Daniel Beck (17/Oct/14 1:13 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-994) Gui for bulk delete of builds
Daniel Beck updated JENKINS-994 Gui for bulk delete of builds Change By: Daniel Beck (17/Oct/14 1:13 PM) Component/s: plugin-proposals This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-994) Gui for bulk delete of builds
Daniel Beck commented on JENKINS-994 Gui for bulk delete of builds it's not a G UI, but Jenkins CLI supports it: https://ci.jenkins-ci.org/cli/command/delete-builds This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17805) Naming a Jenkins installation
Daniel Beck updated JENKINS-17805 Naming a Jenkins installation Change By: Daniel Beck (17/Oct/14 1:15 PM) Component/s: plugin-proposals This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-25192) Trigger are always run after finalize
William Bernardet commented on JENKINS-25192 Trigger are always run after finalize I guess it is deliberate, but one thing that annoys me is that we define some order of execution for the publisher/notifier in job config, and this runAfterFinilized affects it. From an end user prospective it is pretty difficult to find it out as it does not reflect from ui. So one option is also to raise a bug on the workspace cleanup to run after finalize, so if it is the last one in the list, then it really gets executed as the last one This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-25194) Private key with passphrase does not seem to work
Jesse Glick created JENKINS-25194 Private key with passphrase does not seem to work Issue Type: Bug Assignee: Nicolas De Loof Components: git-client Created: 17/Oct/14 1:46 PM Description: I have been unable to get CliGitAPIImpl to work with a private key with passphrase on a Linux slave to connect to a nonpublic Git repository. (Selecting the option to load from the default location, ~/.ssh/id_dsa.) I always get Permission denied (publickey). I verified that GIT_SSH and SSH_ASKPASS are being set and that the files they point to have the expected contents (by patching the plugin to not delete these files in its finally block). Indeed when I log in to the slave, set these variables to the same files, and run git clone repo, it works fine. If I set the job to use JGit rather than CLI git, it also works fine, so I do not think I am just using the wrong credentials. I also tested with a private key (specific file on master) with no passphrase. This worked fine (with both JGit and CLI). I thought one explanation was that ssh thought it was running from a terminal (even though it should not be) and so ignored SSH_ASKPASS. Indeed to interactively verify the GIT_SSH / SSH_ASKPASS combination you have to prefix the git command with setsid if you want the passphrase script to be consulted. But I see the same problem even when I patch the plugin to prefix all git commands with setsid. So https://github.com/jenkinsci/git-client-plugin/commit/4b4d59d29894ac6eccab969561d2df5207a88f60 is not working for me, for unknown reasons. Whether or not it is working for others, I would suggest a simplifying change to CliGitAPIImpl: rather than relying on SSH_ASKPASS, decrypt the private key in Java code (I think there is code for this in one of the libraries available to this plugin) and save that to the keyfile. Note that GitPluginTest in acceptance-test-harness does not seem to test passphrases. (Nor does it test private keys that are not entered directly but loaded from a file on master, another important use case.) Project: Jenkins Labels: ssh Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-25194) Private key with passphrase does not seem to work
Daniel Beck resolved JENKINS-25194 as Duplicate Private key with passphrase does not seem to work Duplicates JENKINS-20879. Change By: Daniel Beck (17/Oct/14 1:49 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25019) updateSecureSessionFlag fails to set secure cookie flag
Jesse Glick updated JENKINS-25019 updateSecureSessionFlag fails to set secure cookie flag Change By: Jesse Glick (17/Oct/14 1:53 PM) Labels: lts-candidate security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Atlassian Expert - Urgent Requirement
Pelease let uw know of your intrest asap.. Atlassian Expert Client: Best Buy Location: MN Duration: 2 years Rate: Best Atlassian Expert: Experience technician knowledgeable in implementing and supporting Atlassian Products (JIRA, Confluence, Green Hopper, BitBucket, Crucible, etc.). The individual will assist the maintain the Atlassian environment and provide guidance to the development teams in the right use of the tools. The resource will be knowledgeable in installation, configuration, administration and best practices on various Atlassian products. -- Thanks, Chris John Resource Manager IGEN LABS, INC. Falls Church, Virginia, VA 22043 Direct : 631-440-6752 Email : chrisj...@igenlabsinc.com Web: www.igenlabsinc.com -- 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.
