date:20161003

[JIRA] (JENKINS-38592) pipelines data for json is getting a bit too crazy (for dashboard)

2016-10-03 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38592  
 
 
  pipelines data for json is getting a bit too crazy (for dashboard)   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Summary: 
 pipelines data for json is getting a bit too crazy  (for dashboard)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38592) pipelines data for json is getting a bit too crazy

2016-10-03 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38592  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: pipelines data for json is getting a bit too crazy   
 

  
 
 
 
 

 
 One point Vivek and I discussed: do we need the latest run of each pipeline to return everything? or could it be a summary of what we known is needed on the screen? when a pipeline detail is loaded then we do a full fetch anyway right Cliff Meyers Thorsten Scherler? Vivek also thinks making use of the tree api could be a better bet (ie only request what we know is needed).   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38678) If the JNLP port is changed to a port in use and then changed to a port not in use, a stack trace appears

2016-10-03 Thread vinc...@latombe.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe started work on  JENKINS-38678  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38677) Failure to create label in TFS

2016-10-03 Thread andrew.paul.g...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Gray created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38677  
 
 
  Failure to create label in TFS   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 redsolo  
 
 
Components: 
 tfs-plugin  
 
 
Created: 
 2016/Oct/04 5:22 AM  
 
 
Environment: 
 Windows 2012 Jenkins 2.24 tfs-plugin 5.2.1  
 
 
Labels: 
 tfs-plugin  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Andrew Gray  
 

  
 
 
 
 

 
 Since upgrading to 5.2.1 of the TFS plugin bad things have started happening: Last step is to apply label to TFS if all unit tests pass. Instead I get this more often than not: Creating label 'TPS_1927' on '$/PSD Team/TPS/TPS App' as of the current version in workspace 'Hudson-TPS-MASTER'... ERROR: Build step failed with exception java.lang.RuntimeException: java.lang.RuntimeException: Label creation failed. at hudson.plugins.tfs.model.Server.execute(Server.java:226) at hudson.plugins.tfs.TFSLabeler.perform(TFSLabeler.java:86) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Caused by: java.lang.RuntimeException: Label creation failed. at hudson.plugins.tfs.commands.LabelCommand.call(LabelCommand.java:70)

[JIRA] (JENKINS-38678) If the JNLP port is changed to a port in use and then changed to a port not in use, a stack trace appears

2016-10-03 Thread vinc...@latombe.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38678  
 
 
  If the JNLP port is changed to a port in use and then changed to a port not in use, a stack trace appears   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Oct/04 5:22 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Vincent Latombe  
 

  
 
 
 
 

 
 If a user changes the JNLP Port to a port in use and back to another port, the user is presented with a stack trace and cannot proceed. 

 
javax.servlet.ServletException: java.lang.UnsupportedOperationException
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
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.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.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
at com.cloudbees.jenkins.ha.HAHealthCheckFilter.doFilter(HAHealthCheckFilter.java:35)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)
at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:38)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter._doFilter(OfflineSecurityRealmFilter.java:90)
at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter.doFilter(OfflineSecurityRealmFilter.java:67)
at

[JIRA] (JENKINS-38678) If the JNLP port is changed to a port in use and then changed to a port not in use, a stack trace appears

2016-10-03 Thread vinc...@latombe.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vincent Latombe assigned an issue to Vincent Latombe  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38678  
 
 
  If the JNLP port is changed to a port in use and then changed to a port not in use, a stack trace appears   
 

  
 
 
 
 

 
Change By: 
 Vincent Latombe  
 
 
Assignee: 
 Vincent Latombe  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38676) git summary should show the repository URL

2016-10-03 Thread jacob.kel...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Keller created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38676  
 
 
  git summary should show the repository URL   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2016/Oct/04 5:20 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jacob Keller  
 

  
 
 
 
 

 
 When using multiple git repositories in a pipeline, the git plugin adds a sumary for each built repository that looks something like  Revision:  
 
a branch 
another branch ... 
another branch 
 (Usually only one branch, but some cases show more). This summary could benefit from adding the repository URL or a human readable name, so that users can quickly see which revision belongs to what repository. Especially true when there are multiple repositories in a single build.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-38675) gerrit trigger git summary show refspec instead of branch

2016-10-03 Thread jacob.kel...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Keller created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38675  
 
 
  gerrit trigger git summary show refspec instead of branch   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 rsandell  
 
 
Components: 
 gerrit-trigger-plugin, git-client-plugin, git-plugin  
 
 
Created: 
 2016/Oct/04 5:18 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jacob Keller  
 

  
 
 
 
 

 
 When you have multiple git projects in a pipeline build, multiple git summary bits appear in the build information when you highlight the build. These currently show something like  Revision:  
 
a built branch 
another built branch 
 When using the gerrit trigger plugin, the "built branches" only show the name of the branch from $GERRIT_BRANCH, instead of showing a refspec. Ideally when using these together, we should see the refspec instead of the branch because this is really what was built by the job.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-38592) pipelines data for json is getting a bit too crazy

2016-10-03 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38592  
 
 
  pipelines data for json is getting a bit too crazy   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 

  
 
 
 
 

 
 In many cases the piplines json for the dashboard (search results) is blowing out to 14kb for 26 "rows" of data. This isn't a huge json transfer, but when you look closer, the impact of plugins adding to actions appears to be huge, and may be the cause of some problems. As part of looking at a support ticket [~tscherler] uncovered that for 26 pipelines, there is really 20 lines of attributes that are used by the dashboard == 520 lines (roughly). However there is 10k lines in the response - this is a bit out of control. It seems that every plugin installed adds actions for every little thing, which the dashboard doesn't need. For example{noformat}"_class": "io.jenkins.blueocean.service.embedded.rest.ActionProxiesImpl","_links": {  "self": {"_class": "io.jenkins.blueocean.rest.hal.Link","href": "/blue/rest/organizations/jenkins/... (hidden)"  }},"_class": "com.cloudbees.plugins.credentials.ViewCredentialsAction","stores": {},"urlName": "credentials"  }],{noformat}is added to every pipeline (along with 100's of others).  Note also the whitespace (may be another problem).  It really depends on the plugins. Also {noformat} {"_class": "hudson.model.TextParameterDefinition","defaultParameterValue": {  "_class": "hudson.model.StringParameterValue",  "name": "jiraComment",  "value": ""},"description": "Additional info for theissue's comment","name": "jiraComment","type": "TextParameterDefinition"  },{noformat}will never be of use to the dashboard (well probably). Some questions: Is there a better query to use to make the response smaller/more compact? (even just eyeballing the reponse could be helped by not returning the metadata optionally). I expect the calculation of this is quite expensive. Could this be a source of the slowdown when people have enough/certain plugins installed?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-36823) Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles

2016-10-03 Thread bholt+jenk...@planetholt.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Holt commented on  JENKINS-36823  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Upgrade AWS SDK to 1.11.16 to enable ecs-plugin to use Task Roles   
 

  
 
 
 
 

 
 I was waiting on the AWS SDK plugin to be released, and it looks like there was finally a release a couple weeks ago. We've been using a local fork with this functionality since my original pull request was made back in August, so I'll prepare a pull request with the task role functionality sometime this week.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38506) Invalid workspace path for pipeline jobs on jenkins master

2016-10-03 Thread archie_ba...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Archibald commented on  JENKINS-38506  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Invalid workspace path for pipeline jobs on jenkins master   
 

  
 
 
 
 

 
 Thanks Mike. The 'ws' command has "worked around" the problem for the time being. Obviously this needs to be corrected.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38601) Cannot mark Multibranch Pipeline as Favorite in Blue Ocean

2016-10-03 Thread mne...@cloudbees.com (JIRA)

Title: Message Title

Michael Neale commented on JENKINS-38601

Re: Cannot mark Multibranch Pipeline as Favorite in Blue Ocean

Thanks Kseniia Nenasheva - well spotted. Currently if you favourite it from blue ocean it should search for a suitable branch (but it won't look for the default as setup in github/bitbucket, as that information isn't currently available yet). However, from your steps, it looks like favouriting it from Jenkins itself is a problem? (this may be a related bug, but not quite the same). Blue ocean can only show favourites for a branch (hence it tries to pick a default) - it can't show a favourite of what is effectively a folder. The logic should be (for blue ocean): Favourite a MB pipeline -> choose default branch as per SCM provider -> (if none available) look for master/production/default named branch -> (if none found) -> pick the first one alphabetically so there is at least one branch. What I am curious about is what is the behavior if people don't want a favourite on a branch (I need to investigate that a bit)

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

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

1 2 3 >

1 - 100 of 238 matches

Mail list logo