[JIRA] [subversion-plugin] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"

2016-02-24 Thread patrick.bi...@schaerer.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Bindy commented on  JENKINS-31455 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build instability with "ISVNAuthentication provider did not provide credentials"  
 
 
 
 
 
 
 
 
 
 
I do have the same issue as well with externals: 
Jenkins 1.648 SVN Plugin 2.5.88 
Setup Additional Credentials, but still has occasional failures. Windows 7 installed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [gerrit-trigger-plugin] (JENKINS-31773) Allow retriggering other events aside from patch-created

2016-02-24 Thread psalaberria...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Salaberria commented on  JENKINS-31773 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow retriggering other events aside from patch-created  
 
 
 
 
 
 
 
 
 
 
+1 This feature would be awesome. Is there any plan to implement it anytime soon? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33127) Wrong HTTP status code when Internal server error occurs

2016-02-24 Thread mgau...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikael Gaunin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33127 
 
 
 
  Wrong HTTP status code when Internal server error occurs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikael Gaunin 
 
 
 
 
 
 
 
 
 
 Hi,When the "Error: Exception" with a stack trace was produced, the Jenkins winstone service reported a healthy HTTP 200 status code. I believe this should have reported an HTTP 500 internal server error. Here's how the status codes should be as I see it...* HTTP 503 Service Unavailable - Jenkins is booting, please wait... * HTTP 403 forbidden - accessing resources not authorized. * HTTP 401 authorization required - accessing URLs while not authenticated. * HTTP 500 Internal server error - an internal Jenkins exception occurred.*Use case*I encounter issues when upgrading: * Folders plugin from 5.1 to 5.2.1 * Matrix Authorization Strategy Plugin from 1.2 to 1.3.{quote}hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:237) Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:935) at jenkins.model.Jenkins.(Jenkins.java:816) at hudson.model.Hudson.(Hudson.java:83) at hudson.model.Hudson.(Hudson.java:79) at hudson.WebAppMain$3.run(WebAppMain.java:225) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:924) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106) ... 8 more Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:653) at java.util.ArrayList.get(ArrayList.java:429) at hudson.ExtensionList.get(ExtensionList.java:171) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1347) at hudson.maven.PluginImpl.init(PluginImpl.java:58) ... 13 more{quote}Some additional notes: * When I disable security, the issue remains and Jenkins is unusable - https://wiki.jenkins-ci.org/display/JENKINS/Disable+security * Even when I bootstrap again and upgrade _all_ of the plugins and not just those two I still get the error.  * I have attached the console.log so you can see additional exceptions from the command line. console.log is a fresh 

[JIRA] [core] (JENKINS-33146) mail Authentication fails

2016-02-24 Thread farhan.sum...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 farhan sumbul created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33146 
 
 
 
  mail Authentication fails  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core, mailer-plugin 
 
 
 

Created:
 

 25/Feb/16 7:00 AM 
 
 
 

Environment:
 

 Jenkins 1.616  Java 1.7 
 
 
 

Labels:
 

 jenkins 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 farhan sumbul 
 
 
 
 
 
 
 
 
 
 
Mails are not being sent and below error stack appears. 
javax.servlet.ServletException: javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) 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 

[JIRA] [active-choices-plugin] (JENKINS-31849) Horizontal parameters

2016-02-24 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruno P. Kinoshita resolved as Won't Fix 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Leslie Klein sent me an e-mail to let me know that the workaround did the trick for him. Closing as won't fix. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31849 
 
 
 
  Horizontal parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Bruno P. Kinoshita 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Won't Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-30479) TFS plugin did not support version 2005

2016-02-24 Thread ronny.borch...@muehlbauer.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ronny Borchert commented on  JENKINS-30479 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: TFS plugin did not support version 2005  
 
 
 
 
 
 
 
 
 
 
Ok, then do please change the readme.md file that TFS 2005 Server is not working! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33138) Jenkins is trying to write to /

2016-02-24 Thread fatal.except...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 j p commented on  JENKINS-33138 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins is trying to write to /  
 
 
 
 
 
 
 
 
 
 
Oh- line 106, perhaps?  
  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33138) Jenkins is trying to write to /

2016-02-24 Thread fatal.except...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 j p commented on  JENKINS-33138 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins is trying to write to /  
 
 
 
 
 
 
 
 
 
 
{{   1.649 2 NORMAL true  com.cloudbees.plugins.credentials.CredentialsProvider.Create:admin com.cloudbees.plugins.credentials.CredentialsProvider.Create:jonathan com.cloudbees.plugins.credentials.CredentialsProvider.Delete:admin com.cloudbees.plugins.credentials.CredentialsProvider.Delete:jonathan com.cloudbees.plugins.credentials.CredentialsProvider.ManageDomains:admin com.cloudbees.plugins.credentials.CredentialsProvider.ManageDomains:jonathan com.cloudbees.plugins.credentials.CredentialsProvider.Update:admin com.cloudbees.plugins.credentials.CredentialsProvider.Update:jonathan com.cloudbees.plugins.credentials.CredentialsProvider.View:admin com.cloudbees.plugins.credentials.CredentialsProvider.View:jonathan hudson.model.Computer.Build:admin hudson.model.Computer.Build:jonathan hudson.model.Computer.Configure:admin hudson.model.Computer.Configure:jonathan hudson.model.Computer.Connect:admin hudson.model.Computer.Connect:jonathan hudson.model.Computer.Create:admin hudson.model.Computer.Create:jonathan hudson.model.Computer.Delete:admin hudson.model.Computer.Delete:jonathan hudson.model.Computer.Disconnect:admin hudson.model.Computer.Disconnect:jonathan hudson.model.Hudson.Administer:admin hudson.model.Hudson.Administer:jonathan hudson.model.Hudson.ConfigureUpdateCenter:admin hudson.model.Hudson.ConfigureUpdateCenter:jonathan hudson.model.Hudson.Read:admin hudson.model.Hudson.Read:jonathan hudson.model.Hudson.RunScripts:admin hudson.model.Hudson.RunScripts:jonathan hudson.model.Hudson.UploadPlugins:admin hudson.model.Hudson.UploadPlugins:jonathan hudson.model.Item.Build:admin hudson.model.Item.Build:jonathan hudson.model.Item.Cancel:admin hudson.model.Item.Cancel:jonathan hudson.model.Item.Configure:admin hudson.model.Item.Configure:jonathan hudson.model.Item.Create:admin hudson.model.Item.Create:jonathan hudson.model.Item.Delete:admin hudson.model.Item.Delete:jonathan hudson.model.Item.Discover:admin hudson.model.Item.Discover:jonathan hudson.model.Item.Read:admin hudson.model.Item.Read:jonathan hudson.model.Item.Workspace:admin hudson.model.Item.Workspace:jonathan hudson.model.Run.Delete:admin hudson.model.Run.Delete:jonathan hudson.model.Run.Update:admin hudson.model.Run.Update:jonathan hudson.model.View.Configure:admin hudson.model.View.Configure:jonathan hudson.model.View.Create:admin hudson.model.View.Create:jonathan hudson.model.View.Delete:admin hudson.model.View.Delete:jonathan hudson.model.View.Read:admin hudson.model.View.Read:jonathan   true false  false  trwebapp   trwebapp jenkinsci/jnlp-slave /home/jenkins 512 1024 false arn:aws:ecs:us-west-2:884646228300:task-definition/jenkins-slave:1   e000d1e0-d06e-4995-ab11-84656747803c arn:aws:ecs:us-west-2:884646228300:cluster/buildcluster us-west-25 0All false falseAll 0true }} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 
 

[JIRA] [cloudbees-folder-plugin] (JENKINS-33145) No page found '/hudson/security/GlobalMatrixAuthorizationStrategy/config.jelly' for class com.cloudbees.hudson.plugins.folder.Folder'

2016-02-24 Thread cdlee...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Makson Lee updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33145 
 
 
 
  No page found '/hudson/security/GlobalMatrixAuthorizationStrategy/config.jelly' for class com.cloudbees.hudson.plugins.folder.Folder'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Makson Lee 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33145) No page found '/hudson/security/GlobalMatrixAuthorizationStrategy/config.jelly' for class com.cloudbees.hudson.plugins.folder.Folder'

2016-02-24 Thread cdlee...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Makson Lee created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33145 
 
 
 
  No page found '/hudson/security/GlobalMatrixAuthorizationStrategy/config.jelly' for class com.cloudbees.hudson.plugins.folder.Folder'  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 cloudbees-folder-plugin 
 
 
 

Created:
 

 25/Feb/16 4:31 AM 
 
 
 

Environment:
 

 Jenkins 1.650  CloudBees Folders Plugin 5.2.1 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Makson Lee 
 
 
 
 
 
 
 
 
 
 
After upgraded to version 5.2.1, we got the error as shown in attachment when trying to configure a folder.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
   

[JIRA] [behave-testresults-publisher-plugin] (JENKINS-33144) behave-testresults-publisher plugin lacks documentation on how to use it

2016-02-24 Thread brianna.laug...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brianna Laugher updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33144 
 
 
 
  behave-testresults-publisher plugin lacks documentation on how to use it  
 
 
 
 
 
 
 
 
 

Change By:
 
 Brianna Laugher 
 
 
 
 
 
 
 
 
 
 There's no information about how this plugin is supposed to work. From https://github.com/jenkinsci/behave-testresults-publisher-plugin it says to use behave options {{--format=json.pretty --outfile=resultsfilenameofyourchoice.json}}I am doing this, and the output file is being kept as a build artifact and looks vaguely correct.I configured the job and added post-build step    * Publish behave results as a report  * . But I don't see anywhere how to tell the plugin what the name of my json file is. So unsurprisingly this build step fails.{ { code} [BehaveReportPublisher] Compiling Behave Html Reports ...ERROR: Build step failed with exceptionjava.lang.NullPointerException at net.jenkins.BehaveReportPublisher.perform(BehaveReportPublisher.java:63) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671) at hudson.model.Run.execute(Run.java:1766) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408)Build step 'Publish behave results as a report' marked build as failureFinished: FAILURE {code } } 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 

[JIRA] [behave-testresults-publisher-plugin] (JENKINS-33144) behave-testresults-publisher plugin lacks documentation on how to use it

2016-02-24 Thread brianna.laug...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brianna Laugher created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33144 
 
 
 
  behave-testresults-publisher plugin lacks documentation on how to use it  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Chaitanya Channella 
 
 
 

Components:
 

 behave-testresults-publisher-plugin 
 
 
 

Created:
 

 25/Feb/16 4:28 AM 
 
 
 

Environment:
 

 Jenkins ver. 1.632  Plugin version 0.0.11 
 
 
 

Labels:
 

 plugin 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Brianna Laugher 
 
 
 
 
 
 
 
 
 
 
There's no information about how this plugin is supposed to work.  
From https://github.com/jenkinsci/behave-testresults-publisher-plugin it says to use behave options --format=json.pretty --outfile=resultsfilenameofyourchoice.json 
I am doing this, and the output file is being kept as a build artifact and looks vaguely correct. 
I configured the job and added post-build step Publish behave results as a report. But I don't see anywhere how to tell the plugin what the name of my json file is. So unsurprisingly this build step fails. 
   

[JIRA] [core] (JENKINS-33138) Jenkins is trying to write to /

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-33138 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins is trying to write to /  
 
 
 
 
 
 
 
 
 
 
Please provide the file /var/lib/jenkins/config.xml. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-33143) TFS Plugin Always Rebuilding Without Change

2016-02-24 Thread robert.rochf...@constrainttec.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Rochford commented on  JENKINS-33143 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: TFS Plugin Always Rebuilding Without Change  
 
 
 
 
 
 
 
 
 
 
Does changing 

 

if (!projectPath.equalsIgnoreCase(tfsBaseline.projectPath))
 

 
to 

 

if (!getProjectPath(project.getLastBuild()).equalsIgnoreCase(tfsBaseline.projectPath))
 

 
work? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-33143) TFS Plugin Always Rebuilding Without Change

2016-02-24 Thread robert.rochf...@constrainttec.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Rochford updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33143 
 
 
 
  TFS Plugin Always Rebuilding Without Change  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robert Rochford 
 
 
 
 
 
 
 
 
 
 Hi,I've set the following:{code}Project Name =  " Src " TFS  " Project Path" =  " $/SourcePath/${JOB_NAME} "   {code}This is so I can use the Job (Project) Name to control which branch to build.Within{code:java}protected PollingResult compareRemoteRevisionWith() (TeamFoundationServerSCM.java){code}we have{code:java}if (!projectPath.equalsIgnoreCase(tfsBaseline.projectPath)){code}the two variables have the values{code:java}projectPath = $/SourcePath/${JOB_NAME}tfsBaseline.projectPath = $/SourcePath/Src{code}These are not equal, and therefore the test fails, and it always builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-33143) TFS Plugin Always Rebuilding Without Change

2016-02-24 Thread robert.rochf...@constrainttec.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Rochford updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33143 
 
 
 
  TFS Plugin Always Rebuilding Without Change  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robert Rochford 
 
 
 
 
 
 
 
 
 
 Hi,I've set the following:{ { code:java} Project Name = "Src"TFS "Project Path" = "$/SourcePath/ ${JOB_NAME}"  {code } } This is so I can use the Job (Project) Name to control which branch to build.Within{ { code:java} protected PollingResult compareRemoteRevisionWith() (TeamFoundationServerSCM.java) {code } }   we have bq. {code:java}  if (!projectPath.equalsIgnoreCase(tfsBaseline.projectPath)) {code}   the two variables  are  have the values { { code:java} projectPath = $/SourcePath/${JOB_NAME}tfsBaseline.projectPath = $/SourcePath/Src {code } }   These are not equal, and therefore the test fails, and it always builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-33143) TFS Plugin Always Rebuilding Without Change

2016-02-24 Thread robert.rochf...@constrainttec.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Rochford updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33143 
 
 
 
  TFS Plugin Always Rebuilding Without Change  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robert Rochford 
 
 
 
 
 
 
 
 
 
 Hi,I've set the following:{code :java }Project Name = "Src"TFS "Project Path" = "$/SourcePath/ ${JOB_NAME}" {code}This is so I can use the Job (Project) Name to control which branch to build.Within{code:java}protected PollingResult compareRemoteRevisionWith() (TeamFoundationServerSCM.java){code}we have{code:java}if (!projectPath.equalsIgnoreCase(tfsBaseline.projectPath)){code}the two variables have the values{code:java}projectPath = $/SourcePath/${JOB_NAME}tfsBaseline.projectPath = $/SourcePath/Src{code}These are not equal, and therefore the test fails, and it always builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-33143) TFS Plugin Always Rebuilding Without Change

2016-02-24 Thread robert.rochf...@constrainttec.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Rochford updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33143 
 
 
 
  TFS Plugin Always Rebuilding Without Change  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robert Rochford 
 
 
 
 
 
 
 
 
 
 Hi,I've set the following:{{Project Name = "Src"TFS "Project Path" = "$/SourcePath/ ${JOB_NAME}" }}This is so I can use the Job (Project) Name to control which branch to build.Within{{protected PollingResult compareRemoteRevisionWith() (TeamFoundationServerSCM.java)}}we have {{ bq. if (!projectPath.equalsIgnoreCase(tfsBaseline.projectPath)) }}   the two variables are{{projectPath = $/SourcePath/${JOB_NAME}tfsBaseline.projectPath = $/SourcePath/Src}}These are not equal, and therefore the test fails, and it always builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-33143) TFS Plugin Always Rebuilding Without Change

2016-02-24 Thread robert.rochf...@constrainttec.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Rochford updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33143 
 
 
 
  TFS Plugin Always Rebuilding Without Change  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robert Rochford 
 
 
 
 
 
 
 
 
 
 Hi,I've set the following:{{  Project Name = "Src"TFS "Project Path" = "$/SourcePath/ ${JOB_NAME}"    }}This is so I can use the Job (Project) Name to control which branch to build.Within{{  protected PollingResult compareRemoteRevisionWith() (TeamFoundationServerSCM.java)}}we have{{  if (!projectPath.equalsIgnoreCase(tfsBaseline.projectPath))}}the two variables are{{  projectPath = $/SourcePath/${JOB_NAME}tfsBaseline.projectPath = $/SourcePath/Src}}These are not equal, and therefore the test fails, and it always builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-33143) TFS Plugin Always Rebuilding Without Change

2016-02-24 Thread robert.rochf...@constrainttec.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Rochford updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33143 
 
 
 
  TFS Plugin Always Rebuilding Without Change  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robert Rochford 
 
 
 

Summary:
 
 TFS Plugin Always Rebuilding Without Change  using  
 
 
 
 
 
 
 
 
 
 Hi,I've set the following: {{ Project Name = "Src"TFS "Project Path" = "$/SourcePath/${JOB_NAME}"    }}   This is so I can use the Job (Project) Name to control which branch to build.Within {{ protected PollingResult compareRemoteRevisionWith() (TeamFoundationServerSCM.java) }} we have {{ if (!projectPath.equalsIgnoreCase(tfsBaseline.projectPath)) }}  the two variables are{{ projectPath = $/SourcePath/${JOB_NAME}tfsBaseline.projectPath = $/SourcePath/Src }} These are not equal, and therefore the test fails, and it always builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-33143) TFS Plugin Always Rebuilding Without Change using

2016-02-24 Thread robert.rochf...@constrainttec.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Rochford created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33143 
 
 
 
  TFS Plugin Always Rebuilding Without Change using   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 redsolo 
 
 
 

Components:
 

 tfs-plugin 
 
 
 

Created:
 

 25/Feb/16 3:42 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Robert Rochford 
 
 
 
 
 
 
 
 
 
 
Hi, 
I've set the following: 
Project Name = "Src" TFS "Project Path" = "$/SourcePath/$ {JOB_NAME}"   This is so I can use the Job (Project) Name to control which branch to build.  Within  protected PollingResult compareRemoteRevisionWith() (TeamFoundationServerSCM.java)  we have  if (!projectPath.equalsIgnoreCase(tfsBaseline.projectPath))  projectPath = $/SourcePath/${JOB_NAME} 
tfsBaseline.projectPath = $/SourcePath/Src 
These are not equal, and therefore the test fails, and it always builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 

[JIRA] [label-linked-jobs-plugin] (JENKINS-32445) Make Label Linked Jobs plugin compatible with Jenkins Clouds definition

2016-02-24 Thread domi.br...@free.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dominique Brice commented on  JENKINS-32445 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make Label Linked Jobs plugin compatible with Jenkins Clouds definition  
 
 
 
 
 
 
 
 
 
 
https://github.com/jenkinsci/label-linked-jobs-plugin/commits/feature/JENKINS-32445 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33139) Password reset in HudsonPrivateSecurityRealm

2016-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Dumay edited a comment on  JENKINS-33139 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Password reset in HudsonPrivateSecurityRealm  
 
 
 
 
 
 
 
 
 
 You should be able to recover with either your email address or username. A reset password link should be generated and redirect the user to a new password screen. We should never send a new password in the email.  This functionality should be disabled if no mailer is configured. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33139) Password reset in HudsonPrivateSecurityRealm

2016-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Dumay commented on  JENKINS-33139 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Password reset in HudsonPrivateSecurityRealm  
 
 
 
 
 
 
 
 
 
 
You should be able to recover with either your email address or username. A reset password link should be generated and redirect the user to a new password screen.  
We should never send a new password in the email. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [gearman-plugin] (JENKINS-33142) Gearman plugin does not provide any slave when Jenkins is configured to use the Mesos plugin

2016-02-24 Thread ricardo.ar...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ricardo Reis created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33142 
 
 
 
  Gearman plugin does not provide any slave when Jenkins is configured to use the Mesos plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Vinod Kone 
 
 
 

Components:
 

 gearman-plugin, mesos-plugin 
 
 
 

Created:
 

 25/Feb/16 1:12 AM 
 
 
 

Environment:
 

 gearman-plugin 0.1.3  mesos-plugin 0.10.1 and HEAD  mesos 0.27.1   
 
 
 

Labels:
 

 plugin 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Ricardo Reis 
 
 
 
 
 
 
 
 
 
 
Currently, I've an environment with Jenkins, mesos-plugin and gearman-plugin to provide slaves, and also, a multi-master architecture. 
From the interface, the build has occurred without any problem, however, using the python client the build has never been triggered, and also, the client wait forever (there aren't any slave running). 
Furthermore, sometimes when all the slaves are running, triggered by the interface, the gearman-plugin works very well. 
Kind regards, Reis 
 
  

[JIRA] [branch-api-plugin] (JENKINS-32670) No branch properties for multibranch pipelines

2016-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
There are no branch properties to add unless you install some additional plugins providing some. So the bug is merely that this control is shown when there are no applicable entries. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32670 
 
 
 
  No branch properties for multibranch pipelines  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Summary:
 
 Unable to Set Build Properties No branch properties for multibranch pipelines 
 
 
 

Component/s:
 
 branch-api-plugin 
 
 
 

Component/s:
 
 github-branch-source-plugin 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  

[JIRA] [azure-slave-plugin] (JENKINS-33141) Uncaught error: ConflictError: Windows Azure is currently performing an operation on this deployment that requires exclusive access

2016-02-24 Thread ty...@monkeypox.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R. Tyler Croy created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33141 
 
 
 
  Uncaught error: ConflictError: Windows Azure is currently performing an operation on this deployment that requires exclusive access  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 jenkins-azure-plugin-uncaught-error.png 
 
 
 

Components:
 

 azure-slave-plugin 
 
 
 

Created:
 

 25/Feb/16 12:32 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 R. Tyler Croy 
 
 
 
 
 
 
 
 
 
 
The build node was failing to connect and spin up a Jenkins agent, logs showed: 

 

Feb 25, 2016 12:29:14 AM com.microsoftopentechnologies.azure.remote.AzureSSHLauncher connectToSsh
SEVERE: AzureSSHLauncher: connectToSsh: Got exception while connecting to remote host. Will be trying again after 1 minute java.net.ConnectException: Connection refused
 

 
While it was waiting I went to delete the node, since it was erroneously configured and doing so resulted in the following uncaught exception 

 

java.io.IOException: Error occurred 

[JIRA] [git-plugin] (JENKINS-33140) Git plugin doesn't use refspec on the first clone/fetch

2016-02-24 Thread cuong.t...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cuong Tran updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33140 
 
 
 
  Git plugin doesn't use refspec on the first clone/fetch  
 
 
 
 
 
 
 
 
 

Change By:
 
 Cuong Tran 
 
 
 
 
 
 
 
 
 
 Our repositories have lots of references and we only need to build from a single branch from each job.  For example, I have a job with refspec +refs/heads/master:refs/remotes/origin/master.  On the first clone, it does the following:Cloning the remote Git repositoryUsing shallow cloneAvoid fetching tagsCloning repository https://github.com/foo.git > git init /tmp/jenkins/slave1/workspace/sample/smoke-test # timeout=10Fetching upstream changes from https://github.com/foo.git > git --version # timeout=10 > git -c core.askpass=true fetch --no-tags --progress https://github.com/foo.git +refs/heads/* * :refs/remotes/origin/* *  --depth=1 # timeout=10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-plugin] (JENKINS-33140) Git plugin doesn't use refspec on the first clone/fetch

2016-02-24 Thread cuong.t...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cuong Tran created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33140 
 
 
 
  Git plugin doesn't use refspec on the first clone/fetch  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 

Components:
 

 git-plugin 
 
 
 

Created:
 

 25/Feb/16 12:23 AM 
 
 
 

Environment:
 

 Jenkins ver. 1.649  Git plugin 2.4.2 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Cuong Tran 
 
 
 
 
 
 
 
 
 
 
Our repositories have lots of references and we only need to build from a single branch from each job. For example, I have a job with refspec +refs/heads/master:refs/remotes/origin/master.  
On the first clone, it does the following: 
Cloning the remote Git repository Using shallow clone Avoid fetching tags Cloning repository https://github.com/foo.git > git init /tmp/jenkins/slave1/workspace/sample/smoke-test # timeout=10 Fetching upstream changes from https://github.com/foo.git > git --version # timeout=10 > git -c core.askpass=true fetch --no-tags --progress https://github.com/foo.git +refs/heads/:refs/remotes/origin/ --depth=1 # timeout=10 
 
 
 
 
 
 
 
 
 
 
 

[JIRA] [categorized-view-plugin] (JENKINS-32071) Slow Performance with Category View Plugin

2016-02-24 Thread schristo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Christou updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32071 
 
 
 
  Slow Performance with Category View Plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steven Christou 
 
 
 
 
 
 
 
 
 
 Issue seems to be related to to AbstractLazyLoadRunMap blocking when categorised view is used. This is causing Jenkins to backup while waiting for unblock. Causing page load times to slow down.Logs:{code}2015-12-15_03:16:10.77157 "Handling GET /job/MyJob/ : http-8082-1 View/index.jelly StatusColumn/column.jelly" #17 daemon prio=5 os_prio=0 tid=0x7f236c004800 nid=0x7b79 waiting for monitor entry [0x7f239951b000]2015-12-15_03:16:10.77158java.lang.Thread.State: BLOCKED (on object monitor)2015-12-15_03:16:10.77158  at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:465)2015-12-15_03:16:10.77159  - waiting to lock <0xde0dee38> (a hudson.model.RunMap)2015-12-15_03:16:10.77159  at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:448)2015-12-15_03:16:10.77160  at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:356)2015-12-15_03:16:10.77161  at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:332)2015-12-15_03:16:10.77161  at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:274)2015-12-15_03:16:10.77162  at jenkins.model.lazy.LazyBuildMixIn.getLastBuild(LazyBuildMixIn.java:240)2015-12-15_03:16:10.77164  at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:985)2015-12-15_03:16:10.77165  at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:144)2015-12-15_03:16:10.77166  at hudson.model.Job.getIconColor(Job.java:1053)2015-12-15_03:16:10.77166  at hudson.model.AbstractProject.getIconColor(AbstractProject.java:738)2015-12-15_03:16:10.77167  at org.jenkinsci.plugins.categorizedview.GroupTopLevelItem.getIconColor(GroupTopLevelItem.java:87){code}Cause on last line.To reproduce: * 100+ build history* Slow Disk (not sure how to apply this to a test at the moment)Plugin: categorized-view:1.8Jenkins: 1.609 .4.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
 

[JIRA] [core] (JENKINS-33139) Password reset in HudsonPrivateSecurityRealm

2016-02-24 Thread k...@kohsuke.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kohsuke Kawaguchi created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33139 
 
 
 
  Password reset in HudsonPrivateSecurityRealm  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 25/Feb/16 12:02 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Kohsuke Kawaguchi 
 
 
 
 
 
 
 
 
 
 
HudsonPrivateSecurityRealm should have an option to reset the password for users who have forgotten it. According to James Dumay we don't have it yet, which is an obvious hole. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
  

[JIRA] [core] (JENKINS-33133) WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in /jenkins/job/configure. Reason: java.lang.NullPointerException

2016-02-24 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-33133 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in /jenkins/job/configure. Reason: java.lang.NullPointerException  
 
 
 
 
 
 
 
 
 
 
Well, I have open a job config, made a change and saved it. When I open the config for the same job, the issue persists. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-30479) TFS plugin did not support version 2005

2016-02-24 Thread manf...@simpligility.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manfred Moser closed an issue as Won't Fix 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
These old versions are not even mainstream supported by Microsoft. And our readme page explicitly references only newer versions. See https://github.com/jenkinsci/tfs-plugin 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30479 
 
 
 
  TFS plugin did not support version 2005  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manfred Moser 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Won't Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [analysis-core-plugin] (JENKINS-27548) Sporadic IOException: Failed to persist config

2016-02-24 Thread egues...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 eguess74 commented on  JENKINS-27548 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Sporadic IOException: Failed to persist config  
 
 
 
 
 
 
 
 
 
 
BTW can it be that this is the affecting code? https://github.com/jenkinsci/analysis-core-plugin/blob/9f8f492d2931981f91a06a8eb0123fd7d3cd1a58/src/main/java/hudson/plugins/analysis/util/SaxSetup.java#L19 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [poll-mailbox-trigger-plugin] (JENKINS-32842) Cannot override subjectContains

2016-02-24 Thread nickgre...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Grealy commented on  JENKINS-32842 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot override subjectContains  
 
 
 
 
 
 
 
 
 
 
Just an update: 
I'm just following this up with the previous committer here -> https://github.com/jenkinsci/poll-mailbox-trigger-plugin/pull/1 . 
I'll have some time to look at this issue tomorrow, and will hopefully have a new release pushed out by the weekend. 
Thanks, Nick 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [poll-mailbox-trigger-plugin] (JENKINS-33136) not reading from folder

2016-02-24 Thread nickgre...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Grealy edited a comment on  JENKINS-33136 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: not reading from folder  
 
 
 
 
 
 
 
 
 
 Hi Tod,This is definitely a bug. It's been raised here -> [https://issues.jenkins-ci.org/browse/JENKINS-32842] and I'm just following this up with the previous committer here -> [https://github.com/jenkinsci/poll-mailbox-trigger-plugin/pull/1] .I'll have some time  to look at this issue  tomorrow, and will hopefully have a new release pushed out by the weekend.Thanks,Nick 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [poll-mailbox-trigger-plugin] (JENKINS-33136) not reading from folder

2016-02-24 Thread nickgre...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Grealy commented on  JENKINS-33136 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: not reading from folder  
 
 
 
 
 
 
 
 
 
 
Hi Tod, 
This is definitely a bug. It's been raised here -> https://issues.jenkins-ci.org/browse/JENKINS-32842 and I'm just following this up with the previous committer here -> https://github.com/jenkinsci/poll-mailbox-trigger-plugin/pull/1 . 
I'll have some time tomorrow, and will hopefully have a new release pushed out by the weekend. 
Thanks, 
Nick 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [analysis-core-plugin] (JENKINS-27548) Sporadic IOException: Failed to persist config

2016-02-24 Thread egues...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 eguess74 edited a comment on  JENKINS-27548 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Sporadic IOException: Failed to persist config  
 
 
 
 
 
 
 
 
 
 Same thing here - the REST API fails to create a new job. The property cleanup doesn't seem to be doing anything. Jenkins 1.649 with latest analysis plugins I have restarted the server and as a workaround i have put xercesImpl.jar into the classpath basing on this entry here: https://blogs.oracle.com/mei/entry/java_lang_classnotfoundexception_org_apache as that seems to be the fastest and the only available fixI'll monitor if the workaround will stick. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-plugin] (JENKINS-32998) add condition to the GIT clone/pull step

2016-02-24 Thread michael_gir...@choicehotels.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 michael giroux commented on  JENKINS-32998 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: add condition to the GIT clone/pull step  
 
 
 
 
 
 
 
 
 
 
Perhaps the Git plugin is overkill for this type of job. Have you considered setting SCM to none and using a simple build step to execute a shell script that tests the parameter, and does the checkout as appropriate? 
[ "$ {parameter} 
" = "checkout" ] && git checkout ... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [core] (JENKINS-33138) Jenkins is trying to write to /

2016-02-24 Thread fatal.except...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 j p created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33138 
 
 
 
  Jenkins is trying to write to /  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 24/Feb/16 10:20 PM 
 
 
 

Environment:
 

 Jenkins Version 1.650  All plugins up to date.  Latest CentOS. Fully patched.  Jenkins installed via yum. 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 j p 
 
 
 
 
 
 
 
 
 
 
Yesterday Jenkins was great. Today all builds fail. 
Jenkins Version 1.650 All plugins up to date. Latest CentOS. Fully patched. Jenkins installed via yum.  
When trying to get console output of the job I just ran, the web console states there is no log: 
No such file: /1/log When I look at /var/log/jenkins.log: 
Feb 24, 2016 9:06:16 PM jenkins.model.PeepholePermalink updateCache WARNING: Failed to update hudson.model.FreeStyleProject@24ab29e4[rails-server] lastFailedBuild permalink for null java.io.IOException: Failed to create a temporary file in / So looking at this log I'm wondering, why is Jenkins trying to write anything to /? Is that the literal /, not a relative path? Sure looks like it. That's not OK, so how do I fix it? 
Environment vars:  
Name ↓ 

[JIRA] [core] (JENKINS-33138) Jenkins is trying to write to /

2016-02-24 Thread fatal.except...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 j p updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33138 
 
 
 
  Jenkins is trying to write to /  
 
 
 
 
 
 
 
 
 

Change By:
 
 j p 
 
 
 

Priority:
 
 Minor Critical 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jobconfighistory-plugin] (JENKINS-28413) For some jobs, changes are not displayed after certain day

2016-02-24 Thread paul.sokolov...@linaro.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Sokolovsky commented on  JENKINS-28413 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: For some jobs, changes are not displayed after certain day  
 
 
 
 
 
 
 
 
 
 
We're experiencing the same problem with the plugin version 2.12 (the latest as of now). There's no stacktrace in the log related to affect job, but behavior is the same: all changes past a particular date (2016-02-01 in our case, i.e. it started not long ago), ar enot shown on job history page (https://android-build.linaro.org/jenkins/job/JOBNAME/jobConfigHistory/). Changes are properly recorded in the filesystem. And clicking around, I found that using global "Show all configs" link (https://android-build.linaro.org/jenkins/jobConfigHistory/?filter=all), I see the latest changes done to the affected job. Just the same, I see them in "Show job configs only" (https://android-build.linaro.org/jenkins/jobConfigHistory/?filter=jobs). So, only per-job change listing is affected. 
Currently, we're aware of a single job which exhibits such behavior, but maybe there's more (but it's definitely not the case that all jobs are affected). Our server is generally public, but this particular job is private, so I can't provide a link to it (and of course, change browsing is not available to anonymous). If there any other information I can provide, let me know. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32657) cmakebuilder should allow cmake scripting

2016-02-24 Thread fifteenknots...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Weber resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32657 
 
 
 
  cmakebuilder should allow cmake scripting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Martin Weber 
 
 
 

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] [multijob-plugin] (JENKINS-31888) BuildHistoryWidget causing job page slowdowns

2016-02-24 Thread andy.ja....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Lee commented on  JENKINS-31888 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: BuildHistoryWidget causing job page slowdowns  
 
 
 
 
 
 
 
 
 
 
I'm experiencing this issue as well on 1.642.1. My stack trace is almost exactly the same; we are not using the MultiJob plugin. We've had performance issues due to large build history in the past so we automatically delete old jobs once they are more than 1000 builds old, but we'd prefer not to have to trim the history down further than that. 
Once the page finally loads (takes around 2-3 minutes) it remains fast for a while, but eventually it triggers another reload of history from disk and takes 2-3 minutes again. 
Our build.xml files are about 15 KB each and our junitResult.xml files are about 6 MB each (not sure if it's actually reading the junitResult file or not). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-33137) Per-job attributes for multibranch workflow jobs

2016-02-24 Thread j...@catnook.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jos Backus created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33137 
 
 
 
  Per-job attributes for multibranch workflow jobs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 24/Feb/16 9:50 PM 
 
 
 

Environment:
 

 Jenkins 1.649, workflow 1.13, git 2.4.2 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jos Backus 
 
 
 
 
 
 
 
 
 
 
we have multiple multibranch jobs for the same Git repo, each job doing something different, with the Stash webhook being used to trigger builds. Since the Jenkinsfile is shared in multibranch workflow job, we need a way for the Jenkinsfile to check some per-job property. The easiest (but dirty) way is to modify the Jenkinsfile to just parse the job name. Maybe the ability to set tags or environment variables on the job would be a solution? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
  

[JIRA] [analysis-core-plugin] (JENKINS-27548) Sporadic IOException: Failed to persist config

2016-02-24 Thread egues...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 eguess74 commented on  JENKINS-27548 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Sporadic IOException: Failed to persist config  
 
 
 
 
 
 
 
 
 
 
Same thing here - the REST API fails to create a new job. The property cleanup doesn't seem to be doing anything. Jenkins 1.649 with latest analysis plugins 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32657) cmakebuilder should allow cmake scripting

2016-02-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32657 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: cmakebuilder should allow cmake scripting  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: 15knots Path: src/main/java/hudson/plugins/cmake/AbstractCmakeBuilder.java src/main/java/hudson/plugins/cmake/CmakeBuilder.java http://jenkins-ci.org/commit/cmakebuilder-plugin/7d548881b1b7b91c61b9dfd4b61ebfb5bd23ccb5 Log: FIXED JENKINS-32657: (Reopened) Existing build steps will loose their cmake-argument and working directory settings. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [multijob-plugin] (JENKINS-16950) Can't remove sort of phases in multijob project

2016-02-24 Thread ten...@yahoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Hicks commented on  JENKINS-16950 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't remove sort of phases in multijob project  
 
 
 
 
 
 
 
 
 
 
The current way to remove the sort order is to remove the property called something like `["ts_direction::yourJenkinsUrl::0"]` from the sessionStorage. You can view sessionStorage via firebug or similar, or use the _javascript_ console to modify the value. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [multijob-plugin] (JENKINS-16950) Can't remove sort of phases in multijob project

2016-02-24 Thread ten...@yahoo.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Hicks edited a comment on  JENKINS-16950 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can't remove sort of phases in multijob project  
 
 
 
 
 
 
 
 
 
 The current way to remove the sort order is to remove the property called something like  `  {{ ["ts_direction::yourJenkinsUrl::0"] ` }}  from the sessionStorage. You can view sessionStorage via firebug or similar, or use the _javascript_ console to modify the value. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [poll-mailbox-trigger-plugin] (JENKINS-33136) not reading from folder

2016-02-24 Thread tod.richa...@humanify.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tod Richards created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33136 
 
 
 
  not reading from folder  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Nick Grealy 
 
 
 

Components:
 

 poll-mailbox-trigger-plugin 
 
 
 

Created:
 

 24/Feb/16 8:51 PM 
 
 
 

Environment:
 

 Jenkins: 1.642.1  plugin version: 1.020  Gmail host  centos 7 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Tod Richards 
 
 
 
 
 
 
 
 
 
 
I am trying to use the "folder" advanced email property to read emails that have been filtered into a folder (label in gmail) on my email host, but this option does not work. Mail is always read from inbox. Additionally I tried changing the "subjectContains" option. But this did not change the behavior at all, it still searched for the default value 'jenkins >'. Am I not understanding the purpose of these filter options, or is this a bug? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
   

[JIRA] [global-build-stats-plugin] (JENKINS-23836) NumberFormatException when clicking search button on Global Build Search

2016-02-24 Thread david.hin...@gmx.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Hinske commented on  JENKINS-23836 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: NumberFormatException when clicking search button on Global Build Search  
 
 
 
 
 
 
 
 
 
 
Since a newer Jenkins-Version its not possible to use the calender. 
I think its because the core started to use a newer version of the Yahoo-UI (2.9). 
I created a pull-request to update the version of the yui in the plugin, which made the calendar visible for me again in old and newer Jenkins-versions. 
https://github.com/jenkinsci/global-build-stats-plugin/pull/7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [global-build-stats-plugin] (JENKINS-27956) Jenkins Global Build Search - Cannot choose start date end date

2016-02-24 Thread david.hin...@gmx.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Hinske edited a comment on  JENKINS-27956 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins Global Build Search - Cannot choose start date end date  
 
 
 
 
 
 
 
 
 
 I think these issues are the same.  Since a newer Jenkins-Version its not possible to use the calender.I think its because the core started to use a newer version of the Yahoo-UI (2.9).I created a pull-request to update the version of the yui in the plugin, which made the calendar visible for me again in old and newer Jenkins-versions.https://github.com/jenkinsci/global-build-stats-plugin/pull/7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [global-build-stats-plugin] (JENKINS-27956) Jenkins Global Build Search - Cannot choose start date end date

2016-02-24 Thread david.hin...@gmx.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Hinske commented on  JENKINS-27956 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins Global Build Search - Cannot choose start date end date  
 
 
 
 
 
 
 
 
 
 
I think these issues are the same. Since a newer Jenkins-Version its not possible to use the calender. 
I think its because the core started to use a newer version of the Yahoo-UI (2.9). 
I created a pull-request to update the version of the yui in the plugin, which made the calendar visible for me again in old and newer Jenkins-versions. 
https://github.com/jenkinsci/global-build-stats-plugin/pull/7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [job-dsl-plugin] (JENKINS-32941) Superfluous commands for Conditional steps with configure

2016-02-24 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker commented on  JENKINS-32941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Superfluous commands for Conditional steps with configure  
 
 
 
 
 
 
 
 
 
 
https://github.com/jenkinsci/job-dsl-plugin/pull/762 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32657) cmakebuilder should allow cmake scripting

2016-02-24 Thread fifteenknots...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Weber reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Existing build steps will loose their cmake-argument and working dir settings. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32657 
 
 
 
  cmakebuilder should allow cmake scripting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Martin Weber 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [matrix-project-plugin] (JENKINS-32799) Jenkins failed to generate new Multi-configuration build page when Combination Filter includes build parameter

2016-02-24 Thread danagoye...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dana Goyette commented on  JENKINS-32799 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins failed to generate new Multi-configuration build page when Combination Filter includes build parameter  
 
 
 
 
 
 
 
 
 
 
Try accessing the value as follows, instead: this.binding.variables["VERIFIER"] 
When the parameter doesn't exist (such as in the project), you'll get null, allowing you to decide separately which combinations to show on the project and which ones to actually build. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32657) cmakebuilder should allow cmake scripting

2016-02-24 Thread fifteenknots...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Weber commented on  JENKINS-32657 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: cmakebuilder should allow cmake scripting  
 
 
 
 
 
 
 
 
 
 
Thanks for reporting the cmakeArgs/toolArgs issue. This is serious, as it causes existing buildsteps to forget part of their configuration. I´ll prepare a fix ASAP. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-plugin] (JENKINS-33135) Release repository

2016-02-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I'm not sure what you mean by "will the newer versions be released?" 
Git plugin releases are available from the Jenkins update center for the most current releases and for many previous releases. They are also available through the "update center" under "Manage Jenkins" in your Jenkins installation. 
Source code for the git plugin is available from the GitHub git plugin repository. 
An online tutorial is available to guide you as you create a plugin. 
The other files (git-plugin jar file, javadoc jar file, source code jar file, etc.) are available from the Jenkins artifactory repository. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33135 
 
 
 
  Release repository  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 

[JIRA] [workflow-plugin] (JENKINS-32727) Rerun a build with script edits

2016-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32727 
 
 
 
  Rerun a build with script edits  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 In Progress 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] [workflow-plugin] (JENKINS-32727) Rerun a build with script edits

2016-02-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32727 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Rerun a build with script edits  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsFlowExecutionTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayActionTest.java cps/pom.xml cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayAction.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayCause.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayCommand.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayFlowFactoryAction.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/steps/LoadStepExecution.java cps/src/main/js/samples.js cps/src/main/js/workflow-editor.js cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/config.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/replay/Messages.properties cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/replay/ReplayAction/diff.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/replay/ReplayAction/index.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/replay/ReplayAction/index.properties cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/replay/ReplayCause/description.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/editor/taglib cps/src/main/resources/org/jenkinsci/plugins/workflow/editor/workflow-editor.jelly demo/README.md demo/repo/Jenkinsfile demo/repo/servers.groovy multibranch/pom.xml multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/ReplayActionTest.java pom.xml http://jenkins-ci.org/commit/workflow-plugin/a62e52a222e9e74932149afd0d56986401490845 Log: Merge pull request #334 from jglick/rerun 
JENKINS-32727 Rerun a build with script edits 
Compare: https://github.com/jenkinsci/workflow-plugin/compare/a05eb6a10868...a62e52a222e9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 

[JIRA] [workflow-plugin] (JENKINS-31838) Virtual thread dump uses phony filenames

2016-02-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31838 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Virtual thread dump uses phony filenames  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/rerun/RerunAction.java http://jenkins-ci.org/commit/workflow-plugin/0b1b639e1b14feb1d488e18814487af33be2aec0 Log: Noting JENKINS-31838. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)

2016-02-24 Thread jenkins-ci.org....@mstier.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mr Cinquero updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-23697 
 
 
 
  IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)  
 
 
 
 
 
 
 
 
 
 
build log file reproducing the exception when doing a "curl http://localhost:9087/job/android/8/consoleFull" 
 
 
 
 
 
 
 
 
 

Change By:
 
 Mr Cinquero 
 
 
 

Attachment:
 
 log.txt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [matrix-auth-plugin] (JENKINS-31860) java.lang.ClassCastException: jenkins.branch.MultiBranchProject$3 cannot be cast to hudson.security.SidACL

2016-02-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31860 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.ClassCastException: jenkins.branch.MultiBranchProject$3 cannot be cast to hudson.security.SidACL  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/RerunActionTest.java http://jenkins-ci.org/commit/workflow-plugin/74d9e60f49113d5ffa26a042a3030cc8b7575019 Log: Investigating 

JENKINS-31860
, have proposed fix. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30749) Jenkins should be secure out of the box by default

2016-02-24 Thread pw...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Wolf assigned an issue to Keith Zantow 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30749 
 
 
 
  Jenkins should be secure out of the box by default  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Wolf 
 
 
 

Assignee:
 
 Keith Zantow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30749) Jenkins should be secure out of the box by default

2016-02-24 Thread pw...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Wolf started work on  JENKINS-30749 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Patrick Wolf 
 
 
 

Status:
 
 Open In 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] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-23697 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)  
 
 
 
 
 
 
 
 
 
 
This is the serialized form of console log annotators. Could you attach an affected build log to this issue as it is stored on disk? Feel free to only post an excerpt, but it should be complete, i.e. exhibit the problem when viewed in Jenkins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [active-directory-plugin] (JENKINS-3404) mix LDAP and local Hudson users

2016-02-24 Thread fed...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Federico Soria Galvarro commented on  JENKINS-3404 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: mix LDAP and local Hudson users  
 
 
 
 
 
 
 
 
 
 
This bug have any estimated date? As Alexander say make sense, for example I have external user that not exists in the active directory but I want that they can be logged. Also, and most important, if my LDAP is down I can't use Jenkins, is really useful have a local account for this circumstance. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-plugin] (JENKINS-33135) Release repository

2016-02-24 Thread daniel.j...@asf.ro (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Jipa created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33135 
 
 
 
  Release repository  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 

Components:
 

 git-plugin 
 
 
 

Created:
 

 24/Feb/16 6:00 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Daniel Jipa 
 
 
 
 
 
 
 
 
 
 
This actually is not a bug. I want to create a Jenkins plugin that depends on git-plugin, but I couldn't find the repo for the latest version. Last published version is 2.0.1 Will the newer versions be released? Thank you 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

  

[JIRA] [active-directory-plugin] (JENKINS-33134) Jenkins 1.649 / Active Directory 1.41

2016-02-24 Thread mrea...@crestron.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Reagan created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33134 
 
 
 
  Jenkins 1.649 / Active Directory 1.41  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 active-directory-plugin 
 
 
 

Created:
 

 24/Feb/16 5:57 PM 
 
 
 

Environment:
 

 Ubuntu 12.04.5 LTS \n \l   
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Michael Reagan 
 
 
 
 
 
 
 
 
 
 
Hi, 
I can log in using credentials of one user (linuxadmin) but fails with the credentials of another user (mreagan) 
Unfortunately I do not admin the Windows domain machine. 
I have included the exceptions entered into the log when the login fails 
From /var/log/jenkins/jenkins.log 
Feb 24, 2016 10:02:12 AM hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider retrieveUser WARNING: Credential exception trying to authenticate against CRESTRON.CRESTRON.COM domain org.acegisecurity.BadCredentialsException: Failed to retrieve user information for mreagan; nested exception is javax.naming.NamingException: [LDAP: error code 1 - 20D6: SvcErr: DSID-031007DB, problem 5012 (DIR_ERROR), data 0 ^@]; remaining name 'CN=Michael Reagan,OU=Engineering/Firmware,OU=HW Engineering,OU=22 Link,OU=Crestron Domain 

[JIRA] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)

2016-02-24 Thread jenkins-ci.org....@mstier.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mr Cinquero edited a comment on  JENKINS-23697 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)  
 
 
 
 
 
 
 
 
 
 Hokay, I traced down a log file producing that error and traced it further down to the exact line: {noformat} [JENKINS] Recording test results[INFO] ha:YB+LCP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEGvvmZ+X75ZekLlOVfvTjc8FPJgaGiiIGKaiG5Py84vycVD1nCA1SyAABjCCFBQCV27OjYA==[INFO] --- maven-source-plugin:2.3:jar-no-fork (attach-sources) @ android-aggregator --- {noformat}   Interestingly, I can't see the second line on my console. It only appeared after pasting it here. Every time I open that build's log in Jenkins, the exception gets logged to /var/log/jenkins.log. However, I don't get to see the exception in the frontend again ... that only seems to happen during live builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)

2016-02-24 Thread jenkins-ci.org....@mstier.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mr Cinquero edited a comment on  JENKINS-23697 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)  
 
 
 
 
 
 
 
 
 
 Hokay, I traced down a log file producing that error and traced it further down to the exact line:[JENKINS] Recording test results[INFO] ha:YB+LCP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEGvvmZ+X75ZekLlOVfvTjc8FPJgaGiiIGKaiG5Py84vycVD1nCA1SyAABjCCFBQCV27OjYA==[INFO] --- maven-source-plugin:2.3:jar-no-fork (attach-sources) @ android-aggregator ---Interestingly, I can't see the second line on my console. It only appeared after pasting it here.  Every time I open that build's log in Jenkins, the exception gets logged to /var/log/jenkins.log. However, I don't get to see the exception in the frontend again ... that only seems to happen during live builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [console-tail-plugin] (JENKINS-23697) IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)

2016-02-24 Thread jenkins-ci.org....@mstier.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mr Cinquero commented on  JENKINS-23697 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)  
 
 
 
 
 
 
 
 
 
 
Hokay, I traced down a log file producing that error and traced it further down to the exact line: 
[JENKINS] Recording test results[INFO]  ha:YB+LCP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEGvvmZ+X75ZekLlOVfvTjc8FPJgaGiiIGKaiG5Py84vycVD1nCA1SyAABjCCFBQCV27OjYA== [INFO] — maven-source-plugin:2.3:jar-no-fork (attach-sources) @ android-aggregator — 
Interestingly, I can't see the second line on my console. It only appeared after pasting it 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] [github-plugin] (JENKINS-33086) Successful build notification does not work

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-33086 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Successful build notification does not work  
 
 
 
 
 
 
 
 
 
 
Probably around here: https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/com/cloudbees/jenkins/GitHubCommitNotifier.java#L157 
As the plugin appears to not properly handle being called while a build is still running (and supposed to pretend it's finished). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [next-build-number-plugin] (JENKINS-33046) Next Build Number plugin doesn't work for Workflow or Multi-branch Workflow jobs

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-33046 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Next Build Number plugin doesn't work for Workflow or Multi-branch Workflow jobs  
 
 
 
 
 
 
 
 
 
 
These jobs aren't AbstractProjects, so https://github.com/jenkinsci/next-build-number-plugin/blob/master/src/main/java/org/jvnet/hudson/plugins/nextbuildnumber/NextBuildNumberAction.java#L94 does not apply. 
TransientActionFactory or similar is probably the better choice. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32818) Jenkins stops responding to web HTTP requests

2016-02-24 Thread mmit...@microsoft.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Mitchell commented on  JENKINS-32818 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins stops responding to web HTTP requests  
 
 
 
 
 
 
 
 
 
 
I am guessing no. That's the normal state for our instance, which uses a lot of build flow jobs. Those are just waiting around for other builds to complete so that they can either complete the build flow job, or queue a new dependent job. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32818) Jenkins stops responding to web HTTP requests

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32818 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins stops responding to web HTTP requests  
 
 
 
 
 
 
 
 
 
 
I wonder whether the 50 threads in JobInvocation.waitForCompletion (Build Flow plugin) are related… 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32932) How to set jenkins log level from maven?

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
This is an issue tracker, not a support site. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32932 
 
 
 
  How to set jenkins log level from maven?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32991) Jenkins 1.596.3 with java 1.6.24 and web logic 10.3.5, version compatibility

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
This is not a bug report, and the Jenkins project no longer contains Jenkins older than 1.642.x LTS (which requires Java 7 to run). 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32991 
 
 
 
  Jenkins 1.596.3 with java 1.6.24 and web logic 10.3.5, version compatibility  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33038) FutureImpl.cancel() doesn't cancel the linked job

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-33038 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: FutureImpl.cancel() doesn't cancel the linked job  
 
 
 
 
 
 
 
 
 
 
Great report! I always wondered why -s was broken… 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33026) exit -1073741819 Jenkins issue

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Incomplete 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Not enough information provided to investigate further. I'd check whatever plugin/tool get executed here first. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33026 
 
 
 
  exit -1073741819 Jenkins issue  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Incomplete 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33011) exit -1073741819 Jenkins issue

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Incomplete 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Not enough information provided to investigate further. I'd check whatever plugin/tool get executed here first. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33011 
 
 
 
  exit -1073741819 Jenkins issue  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Incomplete 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33133) WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in /jenkins/job/configure. Reason: java.lang.NullPointerException

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-33133 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in /jenkins/job/configure. Reason: java.lang.NullPointerException  
 
 
 
 
 
 
 
 
 
 
https://github.com/jenkinsci/jenkins/blob/jenkins-1.642.1/core/src/main/java/hudson/Functions.java#L1068 
Happens when there's a null i. 
Would be interesting to know exactly what UI element/plugin/job type/… causes this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-plugin] (JENKINS-33086) Successful build notification does not work

2016-02-24 Thread maciejt.no...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maciej Nowak commented on  JENKINS-33086 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Successful build notification does not work  
 
 
 
 
 
 
 
 
 
 
I wrote simple program that uses the same GitHub API library to update commit status (code:https://gist.github.com/Novakov/f466d8104cbd76d22516) and it worked like a charm, so the problem must lay in Jenkins or one of its plugins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [token-macro-plugin] (JENKINS-32068) Missing many variable expansion tokens in jobs

2016-02-24 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez resolved as Won't Fix 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Issue not related to token macro 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32068 
 
 
 
  Missing many variable expansion tokens in jobs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Samuel Lopez 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Won't Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33133) WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in /jenkins/job/configure. Reason: java.lang.NullPointerException

2016-02-24 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33133 
 
 
 
  WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in /jenkins/job/configure. Reason: java.lang.NullPointerException  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 24/Feb/16 5:16 PM 
 
 
 

Environment:
 

 Core: 1.642.1  Os: Ubuntu 14.04 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Samuel Lopez 
 
 
 
 
 
 
 
 
 
 
WARNING: Caught exception evaluating: h.getRelativeLinkTo(job) in /view/Brandcaster-Social/job/Brandcaster_GenerateBranchInfo/configure. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.Functions.getRelativeLinkTo(Functions.java:1068) at sun.reflect.GeneratedMethodAccessor167.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at 

[JIRA] [next-build-number-plugin] (JENKINS-33046) Next Build Number plugin doesn't work for Workflow or Multi-branch Workflow jobs

2016-02-24 Thread potatopanka...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeff Burke commented on  JENKINS-33046 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Next Build Number plugin doesn't work for Workflow or Multi-branch Workflow jobs  
 
 
 
 
 
 
 
 
 
 
No errors on reboot. And, no messages in the logs when i visit a workflow project or a multi-branch workflow sub-project (the projects auto-created under the project folder). 
Btw, it also doesn't show up in dropdown menus of the projects either (but does show up for Freestyle project dropdown menus). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33131) Some jobs disappeared after upgrade to 1.649 (from 1.647)

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The report does not contain enough information to determine what went wrong. I suggest you ask on the jenkinsci-users mailing list, or #jenkins on Freenode, for help in investigating what happened here. As it appears the files are gone completely, it does not look like it's an issue with unloadable data. Maybe the jobs were never properly copied? Anything interesting in the Jenkins logs? 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33131 
 
 
 
  Some jobs disappeared after upgrade to 1.649 (from 1.647)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ruby-runtime-plugin] (JENKINS-13467) WARNING: Failed to advertise the service to DNS multi-cast

2016-02-24 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
This is not longer happening after upgrading to the latest LTS 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-13467 
 
 
 
  WARNING: Failed to advertise the service to DNS multi-cast   
 
 
 
 
 
 
 
 
 

Change By:
 
 Samuel Lopez 
 
 
 

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] [core] (JENKINS-32597) Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32597 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace  
 
 
 
 
 
 
 
 
 
 
Nominating https://github.com/jenkinsci/jenkins/pull/1993 for LTS backporting. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32597) Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32597 
 
 
 
  Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 lts-candidate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32597) Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace

2016-02-24 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
This issue should be fixed in 1.646 with https://github.com/jenkinsci/jenkins/commit/758c0ced8586eede9ac39c2ebca0d9fc2c4d908e 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32597 
 
 
 
  Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

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] [token-macro-plugin] (JENKINS-32068) Missing many variable expansion tokens in jobs

2016-02-24 Thread lopez....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samuel Lopez commented on  JENKINS-32068 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Missing many variable expansion tokens in jobs  
 
 
 
 
 
 
 
 
 
 
Thanks Alex, 
After looking closely at the stack trace, I realized that my issue appears not to be related to token macro. 
I'll open a separate issue. 
Sam 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32597) Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace

2016-02-24 Thread kevinhcr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Cross edited a comment on  JENKINS-32597 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace  
 
 
 
 
 
 
 
 
 
 We are seeing the same issue after a recent update.As with the original reporter we are just seeing the stack trace and there do not seem to be any other issues. The jobs are working and the build nodes are staying on-line. We are seeing this over a number of different build nodes and a number of different job types. Jenkins: 1.642.1OS: CentOS release 6.5 (Final)Java: jdk1.8.0_45We are using the package from http://pkg.jenkins-ci.org/redhat-stable/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32597) Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace

2016-02-24 Thread kevinhcr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Cross commented on  JENKINS-32597 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace  
 
 
 
 
 
 
 
 
 
 
We are seeing the same issue after a recent update. 
As with the original reporter we are just seeing the stack trace and there do not seem to be any other issues. The jobs are working and the build nodes are staying on-line. 
Jenkins: 1.642.1 OS: CentOS release 6.5 (Final) Java: jdk1.8.0_45 
We are using the package from http://pkg.jenkins-ci.org/redhat-stable/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-33128) TFS Plugin - Wrong workspace folder

2016-02-24 Thread ivan.marti...@grupomost.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ivan Martinez assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33128 
 
 
 
  TFS Plugin - Wrong workspace folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ivan Martinez 
 
 
 

Assignee:
 
 redsolo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33131) Some jobs disappeared after upgrade to 1.649 (from 1.647)

2016-02-24 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33131 
 
 
 
  Some jobs disappeared after upgrade to 1.649 (from 1.647)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Labels:
 
 regression 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33131) Some jobs disappeared after upgrade to 1.649 (from 1.647)

2016-02-24 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33131 
 
 
 
  Some jobs disappeared after upgrade to 1.649 (from 1.647)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 _unsorted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33131) Some jobs disappeared after upgrade to 1.649 (from 1.647)

2016-02-24 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33131 
 
 
 
  Some jobs disappeared after upgrade to 1.649 (from 1.647)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [_unsorted] (JENKINS-33131) Some jobs disappeared after upgrade to 1.649 (from 1.647)

2016-02-24 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-33131 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Some jobs disappeared after upgrade to 1.649 (from 1.647)  
 
 
 
 
 
 
 
 
 
 
I had no time to triangulate it properly, but it definitely belongs to the Jenkins core. Routing it to that queue 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-24003) Unable to wipe out workspace

2016-02-24 Thread dant...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 dan tran edited a comment on  JENKINS-24003 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to wipe out workspace  
 
 
 
 
 
 
 
 
 
 Correction, i had to  have  go  back to 1.3.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.


  1   2   >