[JIRA] (JENKINS-61038) Ability to disable source code view at master and/or project level

2020-02-10 Thread hang.d...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hang Dong created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61038  
 
 
  Ability to disable source code view at master and/or project level   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Ulli Hafner  
 
 
Components: 
 warnings-ng-plugin  
 
 
Created: 
 2020-02-11 01:53  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Hang Dong  
 

  
 
 
 
 

 
 We would like to request for an option to disable warning plugin's parsing and displaying of project source code (source code view feature); ideally having the ability to set it at instance/master level as well as project's parser level.  For very large project where we are more interest in tracking metric, we found this parse/displaying to be expensive on storage; in addition we notice view content permission is tied to job read permission (more open in our instance), instead workspace permission (limited to admin) - in our env with mix-ed repo with diff permission level but builds together, this can potentially exposes source code when we want intended to share build result/console output.     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] [workflow-plugin] (JENKINS-35447) bug on moveing pipeline projects into folder

2016-06-07 Thread hang.d...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hang Dong updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35447 
 
 
 
  bug on moveing pipeline projects into folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hang Dong 
 
 
 

Component/s:
 
 workflow-plugin 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-35447) bug on moveing pipeline projects into folder

2016-06-07 Thread hang.d...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hang Dong updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35447 
 
 
 
  bug on moveing pipeline projects into folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hang Dong 
 
 
 

Labels:
 
 pipeline 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-35447) bug on moveing pipeline projects into folder

2016-06-07 Thread hang.d...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hang Dong updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35447 
 
 
 
  bug on moveing pipeline projects into folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hang Dong 
 
 
 
 
 
 
 
 
 
 Trying out folder in jenkins 2.x, on moving a project (a pipline project to be specific) with no previous failure/instabilty, encountered a stack trace. The project did move, but none of the history made it. Perhaps lastUnstableBuild link doesn't exist for project with no prior unstable runs? Edit: tried the same with a freestyle project, that moved okey. Looks like it's likely specific to pipeline project.  {code:java}Stack tracejava.io.FileNotFoundException: /local/mnt/workspace/jenkins/build_record/pipeline-test/lastUnstableBuild (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:146) at org.apache.commons.io.FileUtils.doCopyFile(FileUtils.java:1138) at org.apache.commons.io.FileUtils.doCopyDirectory(FileUtils.java:1428) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1389) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1261) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1230) at org.apache.commons.io.FileUtils.moveDirectory(FileUtils.java:2755) at hudson.model.Job.movedTo(Job.java:683) at hudson.model.Items.move(Items.java:438) at com.cloudbees.hudson.plugins.folder.relocate.StandardHandler.doMove(StandardHandler.java:73) at com.cloudbees.hudson.plugins.folder.relocate.StandardHandler.handle(StandardHandler.java:65) at com.cloudbees.hudson.plugins.folder.relocate.DefaultRelocationUI.doMove(DefaultRelocationUI.java:121) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:813) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jett

[JIRA] [core] (JENKINS-35447) bug on moveing pipeline projects into folder

2016-06-07 Thread hang.d...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hang Dong updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35447 
 
 
 
  bug on moveing pipeline projects into folder  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hang Dong 
 
 
 

Summary:
 
 bug on moveing  pipeline  projects into folder 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [core] (JENKINS-35447) bug on moveing projects into folder

2016-06-07 Thread hang.d...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hang Dong created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35447 
 
 
 
  bug on moveing projects into folder  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Jun/07 10:26 PM 
 
 
 

Environment:
 

 Jenkins ver. 2.8 running on Ubuntu 14.04 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Hang Dong 
 
 
 
 
 
 
 
 
 
 
Trying out folder in jenkins 2.x, on moving a project (a pipline project to be specific) with no previous failure/instabilty, encountered a stack trace. The project did move, but none of the history made it.  
Perhaps lastUnstableBuild link doesn't exist for project with no prior unstable runs? 

 

Stack trace

java.io.FileNotFoundException: /local/mnt/workspace/jenkins/build_record/pipeline-test/lastUnstableBuild (No such file or directory)
	at java.io.FileInputStream.open(Native Method)
	at java.io.FileInputStream.(FileInputStream.java:146)
	at org.apache.commons.io.FileUtils.doCopyFile(FileUtils.java:1138)
	at org.apache.commons.io.FileUtils.doCopyDirectory(FileUtils.java:1428)
	at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1389)
	at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1261)
	at org.apache.commons.io.FileUtils.copyDirectory(FileUtil

[JIRA] [core] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted

2015-09-11 Thread hang.d...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hang Dong commented on  JENKINS-22932 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted  
 
 
 
 
 
 
 
 
 
 
seeing this on windows master with 1.620, when adding new node, we typically connect via jnlp link, then install as service. We hit the issue onthe service client re-connect. Perhaps this helps: due to https secured master, the first service connect won't have valid cert info (and we suspect this triggers the issue master side), we update xml with certificate info then stop/restart the service, but at this stage the master is already in a bad state (not only the new slave cannot reconnect), the master actually loses connection to all other slaves as well. Our workaround so far is restarting master... 
10:17:07 java.io.IOException: remote file operation failed: C:\JSBuilds\workspace** at hudson.remoting.Channel@1530a3e:: hudson.remoting.ChannelClosedException: channel is already closed 10:17:07 at hudson.FilePath.act(FilePath.java:987) 10:17:07 at hudson.FilePath.act(FilePath.java:969) 10:17:07 at hudson.FilePath.mkdirs(FilePath.java:1152) 10:17:07 at hudson.model.AbstractProject.checkout(AbstractProject.java:1275) 10:17:07 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) 10:17:07 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 10:17:07 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) 10:17:07 at hudson.model.Run.execute(Run.java:1741) 10:17:07 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 10:17:07 at hudson.model.ResourceController.execute(ResourceController.java:98) 10:17:07 at hudson.model.Executor.run(Executor.java:381) 10:17:07 Caused by: hudson.remoting.ChannelClosedException: channel is already closed 10:17:07 at hudson.remoting.Channel.send(Channel.java:550) 10:17:07 at hudson.remoting.Request.call(Request.java:129) 10:17:07 at hudson.remoting.Channel.call(Channel.java:752) 10:17:07 at hudson.FilePath.act(FilePath.java:980) 10:17:07 ... 10 more 10:17:07 Caused by: java.io.IOException 10:17:07 at hudson.remoting.Channel.close(Channel.java:1110) 10:17:07 at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:118) 10:17:07 at hudson.remoting.PingThread.ping(PingThread.java:126) 10:17:07 at hudson.remoting.PingThread.run(PingThread.java:85) 10:17:07 Caused by: java.util.concurrent.TimeoutException: Ping started at 1441990735275 hasn't completed by 1441990975286 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (