date:20180219

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-47584  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Result screen not refreshing with error "Cannot read property 'self' of undefined"   
 

  
 
 
 
 

 
 James Dumay yes it seems very different from the toLowerCase on an undefined pointer.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49630) Unable to view configuration of some projects after upgrade to 2.107

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-49630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to view configuration of some projects after upgrade to 2.107   
 

  
 
 
 
 

 
 Vivek Pandey not sure why our Blue Ocean preloader is running in this case - this appears to be rendering a classic jelly page. Something strange going on?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-47584) Result screen not refreshing with error "Cannot read property 'self' of undefined"

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47584  
 
 
  Result screen not refreshing with error "Cannot read property 'self' of undefined"   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2 , Blue Ocean 1.5 - beta 1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-47584) Result screen not refreshing with error "Cannot read property 'self' of undefined"

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-47584  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Result screen not refreshing with error "Cannot read property 'self' of undefined"   
 

  
 
 
 
 

 
 Vivek Pandey the last report by Jesús Lunar Pérez looks like a SSE problem. An event is coming in, updating the run information but we might not have a reference... perhaps the bunker here needs to be more resiliant to those problems? WDYT Josh McDonald?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-47897) Blue Ocean pipeline view shows stages and steps from previous build, until given step starts

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-47897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean pipeline view shows stages and steps from previous build, until given step starts   
 

  
 
 
 
 

 
 John Hus theres nothing like that right now. We'd be happy to accept a PR for that if you or someone else had the time.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Vivek Pandey - Jim Klimov has provided some HARs and a support bundle, so it should be possible to see the problem he is experiencing now.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49347  
 
 
  BlueOcean unusably slow, maybe related to having a lot of builds stored in history   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Resolution: 
 Duplicate  
 
 
Status: 
 Resolved Reopened  
 
 
Assignee: 
 Vivek Pandey  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49347  
 
 
  BlueOcean unusably slow, maybe related to having a lot of builds stored in history   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 Blue Ocean 1.5 - beta 1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41488) Pipeline view automatically scrolls down

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay edited a comment on  JENKINS-41488  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline view automatically scrolls down   
 

  
 
 
 
 

 
 [~kordzik] yes, it automatically scrolls there on a failed run by design. I'd need to get some more feedback from users before we went ahead and changed this behaviour. Also, hello  - great to see that you're a Blue Ocean user now  :)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41488) Pipeline view automatically scrolls down

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-41488  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline view automatically scrolls down   
 

  
 
 
 
 

 
 Dariusz Kordonski yes, it automatically scrolls there on a failed run by design. I'd need to get some more feedback from users before we went ahead and changed this behaviour.  Also, hello   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48588) Artifacts uploaded to S3 does not show up in Blue Ocean

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-48588  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifacts uploaded to S3 does not show up in Blue Ocean   
 

  
 
 
 
 

 
 Ben Dean I stand corrected then  We use the standard API for retrieving the artifacts, perhaps the display of the S3 artifacts is custom somehow? Would be worth someone investigating.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49638) "Perform build step" doesn't work as timeout action

2018-02-19 Thread olka_suhoversh...@mail.ru (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olga Sukhovershina closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49638  
 
 
  "Perform build step" doesn't work as timeout action   
 

  
 
 
 
 

 
Change By: 
 Olga Sukhovershina  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49638) "Perform build step" doesn't work as timeout action

2018-02-19 Thread olka_suhoversh...@mail.ru (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olga Sukhovershina created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49638  
 
 
  "Perform build step" doesn't work as timeout action   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 build-timeout-plugin  
 
 
Created: 
 2018-02-20 05:10  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Olga Sukhovershina  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to

[JIRA] (JENKINS-49637) Simplify BlueOcean JS development experience

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49637  
 
 
  Simplify BlueOcean JS development experience   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ivan Meredith  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2018-02-20 03:48  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Vivek Pandey  
 

  
 
 
 
 

 
 Currently there are multiple JS modules in BlueOcean. The development experience/release process of these JS modules, specially jenkins-design-language and blueocean-core-js. Key goals of this ticket should be: 
 
Simplified development process so that current pain of releasing and patching package.json across blueocean frontend modules are minimized 
External plugin developers, who extend/build on top of BlueOcean should get npm released version with each blueocean release (including beta) 
 Deliverables: 
 
Design/proposal document 
Working code with implementation and release process 
Migration document (good to discuss it during design phase)

[JIRA] (JENKINS-49636) git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vishal Agrawal updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49636  
 
 
  git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set   
 

  
 
 
 
 

 
Change By: 
 Vishal Agrawal  
 

  
 
 
 
 

 
 We're using Atlassian Bitbucket Jenkins Hook to notify Jenkins' job when a pull request is merged into develop branch. When Bitbucket notifies  of a new commit in develop to the  Jenkins ' job , it builds with CommitHookCause and builds the job  in develop branch . When user manually starts the same job (at some other time), it's built with UserIdCause. The following is GIT_COMMIT, GIT_PREVIOUS_SUCCESSFUL_COMMIT and cause from our build server. As you can see build 76 was started by user 1. It picked the last successful build commit from build #67, build 77 was trigger by commit into develop branch, but it picked the previous successful commit id from build #75. We update the JIRA stories with version # built by our Jenkins' job and these anomalies in picking the previous-successful-commit..current-commit is causing duplicate updates.*How can we configure Jenkins/git-plugin so it'll disregard the build cause when selecting the previously successful commit id?* 67:SCMTrigger (Polling based) 67:GIT_COMMIT=70bbdc7efe052d8beb7902fbba03395d95c7a568 67:GIT_PREVIOUS_SUCCESSFUL_COMMIT=3b578961d0865f45b4660bd7514c3fcb3f2768c3...75:CommitHookCause=f6b0004af4520123ab8ed71540574cdf96fc01a9 75:GIT_COMMIT=28cf5f0ef1b6de4b33aa60b6ec73e15bf62cf0dd 75:GIT_PREVIOUS_SUCCESSFUL_COMMIT=28cf5f0ef1b6de4b33aa60b6ec73e15bf62cf0dd76:UserIdCause=user1 76:GIT_COMMIT=*f6b0004af4520123ab8ed71540574cdf96fc01a9* 76:GIT_PREVIOUS_SUCCESSFUL_COMMIT=70bbdc7efe052d8beb7902fbba03395d95c7a56877:CommitHookCause=d4e6ccba275b4682a823a3ce73c7368da9a50223 77:GIT_COMMIT=d4e6ccba275b4682a823a3ce73c7368da9a50223 77:GIT_PREVIOUS_SUCCESSFUL_COMMIT=28cf5f0ef1b6de4b33aa60b6ec73e15bf62cf0dd78:CommitHookCause=75407f7d73d83713109b54ea88d35f9d794e0939 78:GIT_COMMIT=75407f7d73d83713109b54ea88d35f9d794e0939 78:GIT_PREVIOUS_SUCCESSFUL_COMMIT=d4e6ccba275b4682a823a3ce73c7368da9a5022379:CommitHookCause=2a34ceb69cfefde4cc155a9c623075354d78bb1a 79:GIT_COMMIT=2a34ceb69cfefde4cc155a9c623075354d78bb1a 79:GIT_PREVIOUS_SUCCESSFUL_COMMIT=75407f7d73d83713109b54ea88d35f9d794e093980:CommitHookCause=7f46b3de48cbbbd462701b83f95917be25d7e4bb 80:GIT_COMMIT=7f46b3de48cbbbd462701b83f95917be25d7e4bb 80:GIT_PREVIOUS_SUCCESSFUL_COMMIT=2a34ceb69cfefde4cc155a9c623075354d78bb1a81:CommitHookCause=d65e92608f97722859efcbc0bc6a5d8811464457 81:GIT_COMMIT=d65e92608f97722859efcbc0bc6a5d8811464457 81:GIT_PREVIOUS_SUCCESSFUL_COMMIT=7f46b3de48cbbbd462701b83f95917be25d7e4bb82:CommitHookCause=d65e92608f97722859efcbc0bc6a5d8811464457 82:GIT_COMMIT=d65e92608f97722859efcbc0bc6a5d8811464457 82:GIT_PREVIOUS_SUCCESSFUL_COMMIT=d65e92608f97722859efcbc0bc6a5d881146445783:CommitHookCause=8317e80df2166b1c2295c9ea638155a157cd68e1 83:GIT_COMMIT={color:#ff}8317e80df2166b1c2295c9ea638155a157cd68e1{color} 83:GIT_PREVIOUS_SUCCESSFUL_COMMIT=d65e92608f97722859efcbc0bc6a5d881146445784:UserIdCause=user2

[JIRA] (JENKINS-49636) git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vishal Agrawal commented on  JENKINS-49636  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set   
 

  
 
 
 
 

 
 Mark Waite, there is a single branch (develop) involved in this issue. When a PR in Bitbucket is merged into develop branch, a commit in develop branch is notified by Bitbucket to Jenkins which then builds the job from develop branch. This is what I referred to as CommitHookCause reason (from build.xml file). The issue occurs when the same job is built manually (Build # 76, 84 above) or based on the SCM polling (Build # 67).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49630) Unable to view configuration of some projects after upgrade to 2.107

2018-02-19 Thread ralph.go...@dslextreme.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ralph Goers edited a comment on  JENKINS-49630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to view configuration of some projects after upgrade to 2.107   
 

  
 
 
 
 

 
 Digging further we see that select.js updateListBox is calling hudson-behavior.js findFollowingTR which is returning undefined, causing the subsequent code to fail.See [^image-2018-02-19-12-03-57-775.png]I am also noticing that the number of div.credentials-select-control items seems to vary each time I run it. It will contain anywhere from 4 to 6 items. I have no idea why that would change. I should also add that we see the same _javascript_ error on other pages but only ones with the credentials selection seem to fail to completely load.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49636) git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set

2018-02-19 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-49636  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set   
 

  
 
 
 
 

 
 I assume from your description of multiple branches that you have a single job which is used to process multiple branches. Can you confirm that is the case? You might try an experiment using a job per branch, either by defining the specific jobs for each branch (if a few static branches are involved), or by using a multi-branch Pipeline with a Jenkinsfile in each branch. That seems like it might reduce the risk of confusion from branch changes.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49636) git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set

2018-02-19 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49636  
 
 
  git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49636) git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vishal Agrawal updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49636  
 
 
  git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set   
 

  
 
 
 
 

 
Change By: 
 Vishal Agrawal  
 

  
 
 
 
 

 
 We're using Atlassian Bitbucket Jenkins Hook to notify Jenkins' job when a pull request is merged into develop branch. When Bitbucket notifies Jenkins' job, it builds with CommitHookCause and builds the job. When user manually starts the same job (at some other time), it's built with UserIdCause. The following is GIT_COMMIT, GIT_PREVIOUS_SUCCESSFUL_COMMIT and cause from our build server. As you can see build 76 was started by user 1. It picked the last successful build commit from build #67, build 77 was trigger by commit into develop branch, but it picked the previous successful commit id from build #75. We update the JIRA stories with version # built by our Jenkins' job and these anomalies in picking the previous-successful-commit..current-commit is causing duplicate updates.*How can we configure Jenkins/git-plugin so it'll disregard the build cause when selecting the previously successful commit id?* 67:SCMTrigger (Polling based)67:GIT_COMMIT=70bbdc7efe052d8beb7902fbba03395d95c7a56867:GIT_PREVIOUS_SUCCESSFUL_COMMIT=3b578961d0865f45b4660bd7514c3fcb3f2768c3...75:CommitHookCause=f6b0004af4520123ab8ed71540574cdf96fc01a975:GIT_COMMIT=28cf5f0ef1b6de4b33aa60b6ec73e15bf62cf0dd75:GIT_PREVIOUS_SUCCESSFUL_COMMIT=28cf5f0ef1b6de4b33aa60b6ec73e15bf62cf0dd76:UserIdCause=user176:GIT_COMMIT= * f6b0004af4520123ab8ed71540574cdf96fc01a9 * 76:GIT_PREVIOUS_SUCCESSFUL_COMMIT=70bbdc7efe052d8beb7902fbba03395d95c7a56877:CommitHookCause=d4e6ccba275b4682a823a3ce73c7368da9a5022377:GIT_COMMIT=d4e6ccba275b4682a823a3ce73c7368da9a5022377:GIT_PREVIOUS_SUCCESSFUL_COMMIT=28cf5f0ef1b6de4b33aa60b6ec73e15bf62cf0dd78:CommitHookCause=75407f7d73d83713109b54ea88d35f9d794e093978:GIT_COMMIT=75407f7d73d83713109b54ea88d35f9d794e093978:GIT_PREVIOUS_SUCCESSFUL_COMMIT=d4e6ccba275b4682a823a3ce73c7368da9a5022379:CommitHookCause=2a34ceb69cfefde4cc155a9c623075354d78bb1a79:GIT_COMMIT=2a34ceb69cfefde4cc155a9c623075354d78bb1a79:GIT_PREVIOUS_SUCCESSFUL_COMMIT=75407f7d73d83713109b54ea88d35f9d794e093980:CommitHookCause=7f46b3de48cbbbd462701b83f95917be25d7e4bb80:GIT_COMMIT=7f46b3de48cbbbd462701b83f95917be25d7e4bb80:GIT_PREVIOUS_SUCCESSFUL_COMMIT=2a34ceb69cfefde4cc155a9c623075354d78bb1a81:CommitHookCause=d65e92608f97722859efcbc0bc6a5d881146445781:GIT_COMMIT=d65e92608f97722859efcbc0bc6a5d881146445781:GIT_PREVIOUS_SUCCESSFUL_COMMIT=7f46b3de48cbbbd462701b83f95917be25d7e4bb82:CommitHookCause=d65e92608f97722859efcbc0bc6a5d881146445782:GIT_COMMIT=d65e92608f97722859efcbc0bc6a5d881146445782:GIT_PREVIOUS_SUCCESSFUL_COMMIT=d65e92608f97722859efcbc0bc6a5d881146445783:CommitHookCause=8317e80df2166b1c2295c9ea638155a157cd68e183:GIT_COMMIT= {color:#ff} 8317e80df2166b1c2295c9ea638155a157cd68e1 {color} 83:GIT_PREVIOUS_SUCCESSFUL_COMMIT=d65e92608f97722859efcbc0bc6a5d881146445784:UserIdCause=user284:GIT_COMMIT=37a622daba5dd76a45e345cd4bfb31750f2ede4f84:GIT_PREVIOUS_SUCCESSFUL_COMMIT= *

[JIRA] (JENKINS-49636) git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vishal Agrawal created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49636  
 
 
  git-plugin GIT_PREVIOUS_SUCCESSFUL_COMMIT incorrectly set   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2018-02-20 01:55  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Vishal Agrawal  
 

  
 
 
 
 

 
 We're using Atlassian Bitbucket Jenkins Hook to notify Jenkins' job when a pull request is merged into develop branch.  When Bitbucket notifies Jenkins' job, it builds with CommitHookCause and builds the job. When user manually starts the same job (at some other time), it's built with UserIdCause.  The following is GIT_COMMIT, GIT_PREVIOUS_SUCCESSFUL_COMMIT and cause from our build server. As you can see build 76 was started by user 1. It picked the last successful build commit from build #67, build 77 was trigger by commit into develop branch, but it picked the previous successful commit id from build #75.  We update the JIRA stories with version # built by our Jenkins' job and these anomalies in picking the previous-successful-commit..current-commit is causing duplicate updates. How can we configure Jenkins/git-plugin so it'll disregard the build cause when selecting the previously successful commit id?   67:SCMTrigger (Polling based) 67:GIT_COMMIT=70bbdc7efe052d8beb7902fbba03395d95c7a568 67:GIT_PREVIOUS_SUCCESSFUL_COMMIT=3b578961d0865f45b4660bd7514c3fcb3f2768c3 ... 75:CommitHookCause=f6b0004af4520123ab8ed71540574cdf96fc01a9 75:GIT_COMMIT=28cf5f0ef1b6de4b33aa60b6ec73e15bf62cf0dd 75:GIT_PREVIOUS_SUCCESSFUL_COMMIT=28cf5f0ef1b6de4b33aa60b6ec73e15bf62cf0dd 76:UserIdCause=user1 76:GIT_COMMIT=f6b0004af4520123ab8ed71540574cdf96fc01a9 76:GIT_PREVIOUS_SUCCESSFUL_COMMIT=70bbdc7efe052d8beb7902fbba03395d95c7a568 77:CommitHookCause=d4e6ccba275b4682a823a3ce73c7368da9a50223 77:GIT_COMMIT=d4e6ccba275b4682a823a3ce73c7368da9a50223 77:GIT_PREVIOUS_SUCCESSFUL_COMMIT=28cf5f0ef1b6de4b33aa60b6ec73e15bf62cf0dd 78:CommitHookCause=75407f7d73d83713109b54ea88d35f9d794e0939 78:GIT_COMMIT=75407f7d73d83713109b54ea88d35f9d794e0939

[JIRA] (JENKINS-49596) User session memory leak

2018-02-19 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-49596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User session memory leak   
 

  
 
 
 
 

 
 Code changed in jenkins User: olivier lamy Path: src/java/winstone/HostConfiguration.java src/java/winstone/cmdline/Option.java http://jenkins-ci.org/commit/winstone/36ab8d1ec18a118d4a0f17a1e996eb294cc44589 Log: JENKINS-49596 session cache is never cleaned Signed-off-by: olivier lamy  Compare: https://github.com/jenkinsci/winstone/compare/4e556fcaa53e^...36ab8d1ec18a  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-48571  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs   
 

  
 
 
 
 

 
 R. Tyler Croy so far this looks like jobs created by blue ocean (before the fix) and jobDSLs without an id set get this, but as for the github organisation folder - are you seeing it there ? (it may have a related issue)   Stephen Connolly do you know if github organisation folders could be bitten by this, not setting the id correctly?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-48571  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs   
 

  
 
 
 
 

 
 Leandro Narosky Tristan Lewis Alex Suter Ygor Almeida Sorry for the drawn out things.  For users of JobDSL the solution/work around is to always set an id for the SCM, something like:  

 

source {
 github {
 //github
 id "owner-${project_folder}:repo-${project_name}" 

 This will then correct the behavior. Does this work for you? (similarly for other SCMs) If the jobs were created via some other way, then opening the config and saving it (no change needed) will fix it, and blue ocean has been patched to set the id correctly.    See Sam Gleske's last comment here: https://issues.jenkins-ci.org/browse/JENKINS-46290?focusedCommentId=329162=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-329162 and his fix here: https://github.com/samrocketman/jervis/commit/e4cd6324ff22c3593d7e6feab88dff79e516e14b for an example of a jobDSL using it.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-46290) Project checkout fails (ERROR: Could not determine exact tip revision of master)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46290  
 
 
  Project checkout fails (ERROR: Could not determine exact tip revision of master)   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Status: 
 Reopened Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49610) The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale edited a comment on  JENKINS-49610  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned   
 

  
 
 
 
 

 
 [~abayer] Now blue ocean is being fixed - the main thing for this is *probably* to have an obnoxious SEVERE error that an id isn't set (aimed at jobDSL users).    I'll confirm with other users that this was the issue (mostly they seem to be jobDSL users)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-46290) Project checkout fails (ERROR: Could not determine exact tip revision of master)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-46290  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Project checkout fails (ERROR: Could not determine exact tip revision of master)   
 

  
 
 
 
 

 
 great - I might close this as a duplicate, but Sam Gleske's comment above is handy! thanks  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49616) Estimated time remaining NA

2018-02-19 Thread pe...@bruin.sg (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 uncletall commented on  JENKINS-49616  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Estimated time remaining NA   
 

  
 
 
 
 

 
 The jobs are different kind of pipeline jobs.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49616) Estimated time remaining NA

2018-02-19 Thread pe...@bruin.sg (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 uncletall updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49616  
 
 
  Estimated time remaining NA   
 

  
 
 
 
 

 
Change By: 
 uncletall  
 
 
Attachment: 
 2018-02-20 08_16_37-Dashboard [Jenkins].png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49620) Anchore report exception

2018-02-19 Thread swa...@anchore.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-49620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore report exception   
 

  
 
 
 
 

 
 Zoltan Medovarszky, I see that you've listed the anchore plugin version as 1.0.13. Can you please confirm that the failed attempt to open the report resulted from anchore plugin version 1.0.13 or newer? I ask because version 1.0.13 removed the use of guava (com.google.common.collect.*) libraries but the stack trace in your description contains a reference to it.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-24329) Golang release json needs to be updated

2018-02-19 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-24329  
 
 
  Golang release json needs to be updated
 

  
 
 
 
 

 
Change By: 
 SCM/JIRA link daemon  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-24329) Golang release json needs to be updated

2018-02-19 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-24329  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Golang release json needs to be updated
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Beck Path: golang.groovy http://jenkins-ci.org/commit/crawler/654bc74bafebccbedb310c134b3b29bb7bcb63dc Log: Merge pull request #69 from orrc/fix-golang-version [FIXED JENKINS-24329] Fix golang crawler for double-digit versions Compare: https://github.com/jenkins-infra/crawler/compare/f9dd1e350526...654bc74bafeb  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-24329) Golang release json needs to be updated

2018-02-19 Thread ch...@orr.me.uk (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Orr commented on  JENKINS-24329  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Golang release json needs to be updated
 

  
 
 
 
 

 
 Thanks for reporting this. You can feel free to open a new issue, rather than reusing one that wasn't really related. I've submitted a PR here: https://github.com/jenkins-infra/crawler/pull/69  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-48571  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs   
 

  
 
 
 
 

 
 BlueOcean PR: https://github.com/jenkinsci/blueocean-plugin/pull/1662. Its been merged to master.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49634) Wrong escaping of quotes in the Setup Wizard

Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49634  
 
 
  Wrong escaping of quotes in the Setup Wizard   
 

  
 
 
 
 

 
Change By: 
 Manuel Recena Soto  
 
 
Labels: 
 lts-candidate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49634) Wrong escaping of quotes in the Setup Wizard

Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto updated  JENKINS-49634  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49634  
 
 
  Wrong escaping of quotes in the Setup Wizard   
 

  
 
 
 
 

 
Change By: 
 Manuel Recena Soto  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-41051) withRegistry is not doing a "docker login"

2018-02-19 Thread michael.er...@contactimpact.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Ermer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41051  
 
 
  withRegistry is not doing a "docker login"   
 

  
 
 
 
 

 
Change By: 
 Michael Ermer  
 
 
Comment: 
 Docker 1.17+ no longer supports ~/.dockercfg so jenkins needs to create ~/.docker/config.json from now on.https://github.com/moby/moby/commit/18c9b6c6455f116ae59cde8544413b3d7d294a5e  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-24329) Golang release json needs to be updated

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joey Geiger edited a comment on  JENKINS-24329  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Golang release json needs to be updated
 

  
 
 
 
 

 
 This needs to be updated in the crawler for the [golang matcher|https://github.com/jenkins-infra/crawler/blob/master/golang.groovy#L35]  in the crawler . {code:java}go(?:\.go)?(\d(?:\.\d{1,})*)\.(?:([^-]+)-([^-]+)(?:-(.+))?)\.(?:tar\.gz|zip){code}  If you add the\{1,}to the digit capture, it seems to work.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49634) Wrong escaping of quotes in the Setup Wizard

Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49634  
 
 
  Wrong escaping of quotes in the Setup Wizard   
 

  
 
 
 
 

 
Change By: 
 Manuel Recena Soto  
 
 
Attachment: 
 JENKINS-49634.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49634) Wrong escaping of quotes in the Setup Wizard

Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49634  
 
 
  Wrong escaping of quotes in the Setup Wizard   
 

  
 
 
 
 

 
Change By: 
 Manuel Recena Soto  
 
 
Attachment: 
 JENKINS-49634  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-24329) Golang release json needs to be updated

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joey Geiger edited a comment on  JENKINS-24329  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Golang release json needs to be updated
 

  
 
 
 
 

 
 This needs to be updated in the crawler for the  [  golang matcher |https://github.com/jenkins-infra/crawler/blob/master/golang.groovy#L35]  in the crawler. {code:java}go(?:\.go)?(\d(?:\.\d{1,})*)\.(?:([^-]+)-([^-]+)(?:-(.+))?)\.(?:tar\.gz|zip){code}  If you add the\{1,}to the digit capture, it seems to work.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49634) Wrong escaping of quotes in the Setup Wizard

Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49634  
 
 
  Wrong escaping of quotes in the Setup Wizard   
 

  
 
 
 
 

 
Change By: 
 Manuel Recena Soto  
 
 
Attachment: 
 JENKINS-49634  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-24329) Golang release json needs to be updated

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joey Geiger edited a comment on  JENKINS-24329  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Golang release json needs to be updated
 

  
 
 
 
 

 
 This needs to be updated in the crawler for the golang matcher in the crawler.  {code:java}go(?:\.go)?(\d(?:\.\d{1,})*)\.(?:([^-]+)-([^-]+)(?:-(.+))?)\.(?:tar\.gz|zip){code}  If you add the \  {1,}   to the digit capture, it seems to work.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49635) Permit VirtualFile to serve external file contents

2018-02-19 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-49635  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49610) The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-49610  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned   
 

  
 
 
 
 

 
 Now blue ocean is being fixed - the main thing for this is probably to have an obnoxious SEVERE error that an id isn't set (aimed at jobDSL users).   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-24329) Golang release json needs to be updated

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joey Geiger commented on  JENKINS-24329  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Golang release json needs to be updated
 

  
 
 
 
 

 
   

 

go(?:\.go)?(\d(?:\.\d{1,})*)\.(?:([^-]+)-([^-]+)(?:-(.+))?)\.(?:tar\.gz|zip)
 

   If you add the  {1,}  to the digit capture, it seems to work.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49635) Permit VirtualFile to serve external file contents

2018-02-19 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49635  
 
 
  Permit VirtualFile to serve external file contents   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 core  
 
 
Created: 
 2018-02-19 22:56  
 
 
Labels: 
 api  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 Extracting a comment from JENKINS-25224: 

VirtualFile as written is not quite flexible enough, because it assumes that the master should be in charge of retrieving file contents (as bytestreams) and serving them to the client. What we found was necessary also for making an ArtifactManager based on, say, S3 was to allow VirtualFile to optionally designate a replacement URL that would be served directly to clients. (DirectoryBrowserSupport would need to call the new method.)
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-49634) Wrong escaping of quotes in the Setup Wizard

Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49634  
 
 
  Wrong escaping of quotes in the Setup Wizard   
 

  
 
 
 
 

 
Change By: 
 Manuel Recena Soto  
 
 
Summary: 
 Wrong escaping of quotes in  properties files  the Setup Wizard  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49634) Wrong escaping of quotes in properties files

Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto assigned an issue to Manuel Recena Soto  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49634  
 
 
  Wrong escaping of quotes in properties files   
 

  
 
 
 
 

 
Change By: 
 Manuel Recena Soto  
 
 
Assignee: 
 Manuel Recena Soto  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49634) Wrong escaping of quotes in properties files

Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto started work on  JENKINS-49634  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Manuel Recena Soto  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49634) Wrong escaping of quotes in properties files

Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Recena Soto created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49634  
 
 
  Wrong escaping of quotes in properties files   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-02-19 22:18  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Manuel Recena Soto  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins

[JIRA] (JENKINS-49298) Using "t" key switches focus to search box, when running a build with param entry field on blue ocean home page

2018-02-19 Thread npa...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolae Pascu updated  JENKINS-49298  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49298  
 
 
  Using "t" key switches focus to search box, when running a build with param entry field on blue ocean home page   
 

  
 
 
 
 

 
Change By: 
 Nicolae Pascu  
 
 
Status: 
 In Review Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49609) Feature Request - Support SAML too

2018-02-19 Thread dev.la...@elnarion.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 D. Lauer commented on  JENKINS-49609  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Feature Request - Support SAML too   
 

  
 
 
 
 

 
 Thank you for your feature request! There was no need for SAML in the past, but i will think about it in future versions.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-44981) Developer can see node steps within the step listing

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey assigned an issue to Josh McDonald  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44981  
 
 
  Developer can see node steps within the step listing   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Assignee: 
 Andrew Bayer Josh McDonald  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-44697) Blueocean activity view for job has wrong status for pipeline with lots of stages

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey assigned an issue to Josh McDonald  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44697  
 
 
  Blueocean activity view for job has wrong status for pipeline with lots of stages   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Assignee: 
 Josh  Taylor  McDonald  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-44697) Blueocean activity view for job has wrong status for pipeline with lots of stages

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey assigned an issue to Josh Taylor  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44697  
 
 
  Blueocean activity view for job has wrong status for pipeline with lots of stages   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Assignee: 
 Andrew Bayer Josh Taylor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48820) Blue Ocean plug-in causes stack overflow for big pipeline jobs

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48820  
 
 
  Blue Ocean plug-in causes stack overflow for big pipeline jobs   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Critical Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-45334) REGRESSION "input parameter not support go to classic link" does not work

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45334  
 
 
  REGRESSION "input parameter not support go to classic link" does not work   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Critical Major  
 

  
 
 
 
 

 
 *Scope** Fix so that the link is valid* Add a test*Original request* In case BO does not support some parameters you will be redirected to classic. That redirect does not work. The href is empty.You can test with https://github.com/scherler/jenkins-testfiles the  `JENKINS-40617` branch provides an example for input in a pipeline.  When you go into the detail view of the pipeline you will see the link on a paused for input biuild.  !Screenshot from 2017-07-06 12-33-52.png|thumbnail! BTW the parametrized unsupported like  `JENKINS-40617-param`  branch still works as expected.  !Screenshot from 2017-07-06 12-44-33.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-46571) Update URL scheme to remove URL encoding issues

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46571  
 
 
  Update URL scheme to remove URL encoding issues   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 Blue Ocean  1.5  -  Candidates  beta 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-45334) REGRESSION "input parameter not support go to classic link" does not work

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45334  
 
 
  REGRESSION "input parameter not support go to classic link" does not work   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 Blue Ocean  1.5  -  Candidates  beta 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-45614) Activity tab is really slow

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45614  
 
 
  Activity tab is really slow   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2, Blue Ocean  1.5  -  Candidates  beta 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48820) Blue Ocean plug-in causes stack overflow for big pipeline jobs

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48820  
 
 
  Blue Ocean plug-in causes stack overflow for big pipeline jobs   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 Blue Ocean  1.5  -  Candidates  beta 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-24329) Golang release json needs to be updated

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joey Geiger edited a comment on  JENKINS-24329  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Golang release json needs to be updated
 

  
 
 
 
 

 
 Sorry to re-open, but this has become an issue again.With the release of Go 1.10, the JSON is no longer parsed correctly. {code:java}"name": "Go 1","variants": [{ "arch": "amd64", "os": "10.darwin", "url": "https://dl.google.com/go/go1.10.darwin-amd64.tar.gz" }, { {code} The os is combining the version and os name.The UI only shows Go 1 as the downloadable version, but based on the OS, it doesn't look like it will properly work. This will also fail once go1.10.x is  release  released  as well.Here's a link to the full JSON. [ https://jenkins-updates.cloudbees.com/updates/org.jenkinsci.plugins.golang.GolangInstaller.json ]  Thank you.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48571  
 
 
  checkout scm fails silently after "Could not determine exact tip revision of " in logs   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-24329) Golang release json needs to be updated

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joey Geiger edited a comment on  JENKINS-24329  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Golang release json needs to be updated
 

  
 
 
 
 

 
 Sorry to re-open, but this has become an issue again.With the release of Go 1.10, the JSON is no longer parsed correctly.  {code:java} "name": "Go 1",  "variants": [ \ {    "arch": "amd64",    "os": "10.darwin",    "url": "https://dl.google.com/go/go1.10.darwin-amd64.tar.gz"   },  \ {    {code}  The os is combining the version and os name.The UI only shows Go 1 as the downloadable version, but based on the OS, it doesn't look like it will properly work. This will also fail once go1.10.x is release as well. Here's a link to the full JSON.  https://jenkins-updates.cloudbees.com/updates/org.jenkinsci.plugins.golang.GolangInstaller.json  Thank you.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-24329) Golang release json needs to be updated

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joey Geiger reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Sorry to re-open, but this has become an issue again. With the release of Go 1.10, the JSON is no longer parsed correctly.   "name": "Go 1", "variants": [{ "arch": "amd64", "os": "10.darwin", "url": "https://dl.google.com/go/go1.10.darwin-amd64.tar.gz" }, {   The os is combining the version and os name. The UI only shows Go 1 as the downloadable version, but based on the OS, it doesn't look like it will properly work. This will also fail once go1.10.x is release as well. Thank you.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-24329  
 
 
  Golang release json needs to be updated
 

  
 
 
 
 

 
Change By: 
 Joey Geiger  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-48571  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs   
 

  
 
 
 
 

 
 >If BlueOcean updates a job, it needs to round-trip the existing id if and only if the SCMSource type remains the same, otherwise it will trigger a rebuild storm on restart. BlueOcean doesn't update a job. Even using API, if they try to create a new job for a gihub/bitbucket/git repo, it errors out if there is job with same name exists. Once user creates a blueocean pipeline job, at most they can do is to trigger re-indexing. So a simple solution of creating a blueocean specific id should be ok.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-29579) auto installation of tools only available to master: unnecessary stacktrace and slow

2018-02-19 Thread eric.st-am...@opal-rt.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric St-Amand commented on  JENKINS-29579  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: auto installation of tools only available to master: unnecessary stacktrace and slow   
 

  
 
 
 
 

 
 Is this issue going to be resolved at some point ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48868) blue ocean dashboard taking more than 50s to load.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-48868  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: blue ocean dashboard taking more than 50s to load.   
 

  
 
 
 
 

 
 Joshua Hoblitt Right, need to check how GitHub commits appear on JIRA. Michael Neale do you know how to get commits appear on JIRA tickets? I think if we at least update JIRA with PR being worked on is not bad either.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49620) Anchore report exception

2018-02-19 Thread nu...@anchore.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Nurmi commented on  JENKINS-49620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore report exception   
 

  
 
 
 
 

 
 Hi Zoltan Medovarszky  We are looking into the issue you've reported and will communicate progress here - from the description we're assuming that new jobs are rendering properly and the issue appears to be triggered when loading the reports for jobs that ran before the LTS upgrade <- if this is an incorrect assumption let us know!   Best, -Dan  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48868) blue ocean dashboard taking more than 50s to load.

2018-02-19 Thread j...@hoblitt.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joshua Hoblitt commented on  JENKINS-48868  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: blue ocean dashboard taking more than 50s to load.   
 

  
 
 
 
 

 
 That sounds very plausible and being related to favorites would explain why my production env seems slower than test instances. No code was attached to the ticket – is jira supposed to be doing that for the blueocean repo?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49633) Filenames are no longer shown under Summary of Changes - View Detail

2018-02-19 Thread barn...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Barnish updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49633  
 
 
  Filenames are no longer shown under Summary of Changes - View Detail   
 

  
 
 
 
 

 
Change By: 
 Andrew Barnish  
 

  
 
 
 
 

 
 After the upgrade to p4-plugin 1.8.5 we are no longer seeing "Submitted files" listed when following the link "Summary Of Changes - View Detail" ** This only seems to affect new builds.Builds from before the upgrade are still showing "Submitted files" correctly.It seems like it could be caused by the fix for  -  JENKINS-48845 -  or  - JENKINS-47602 -  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49633) Filenames are no longer shown under Summary of Changes - View Detail

2018-02-19 Thread barn...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Barnish created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49633  
 
 
  Filenames are no longer shown under Summary of Changes - View Detail   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Paul Allen  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2018-02-19 19:27  
 
 
Environment: 
 Jenkins 2.89.4  p4-plugin 1.8.5  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Andrew Barnish  
 

  
 
 
 
 

 
 After the upgrade to p4-plugin 1.8.5 we are no longer seeing "Submitted files" listed when following the link "Summary Of Changes - View Detail"** This only seems to affect new builds. Builds from before the upgrade are still showing "Submitted files" correctly. It seems like it could be caused by the fix for JENKINS-48845 or JENKINS-47602  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-37515) RFE: input() blocks the executor in Declarative, add a stage attribute instead?

2018-02-19 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Seems like it was already implemented in JENKINS-48379.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37515  
 
 
  RFE: input() blocks the executor in Declarative, add a stage attribute instead?   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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

[JIRA] (JENKINS-45725) Jenkins shutdown error: java.lang.ClassNotFoundException: org.eclipse.jetty.http.pathmap.MappedResource

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45725  
 
 
  Jenkins shutdown error: java.lang.ClassNotFoundException: org.eclipse.jetty.http.pathmap.MappedResource
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 _unsorted  
 
 
Component/s: 
 core  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49630) Unable to view configuration of some projects after upgrade to 2.107

2018-02-19 Thread ralph.go...@dslextreme.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ralph Goers edited a comment on  JENKINS-49630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to view configuration of some projects after upgrade to 2.107   
 

  
 
 
 
 

 
 Digging further we see that select.js updateListBox is calling hudson-behavior.js findFollowingTR which is returning undefined, causing the subsequent code to fail.See  https://issues.jenkins-ci.org/secure/attachment/41529/ [^ image-2018-02-19-12-03-57-775.png ]I am also noticing that the number of div.credentials-select-control items seems to vary each time I run it. It will contain anywhere from 4 to 6 items. I have no idea why that would change.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-45725) Jenkins shutdown error: java.lang.ClassNotFoundException: org.eclipse.jetty.http.pathmap.MappedResource

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-45725  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins shutdown error: java.lang.ClassNotFoundException: org.eclipse.jetty.http.pathmap.MappedResource
 

  
 
 
 
 

 
 Sorry, I have missed the update. I cannot say what is exactly in your POM without looking at the parent POM you have hidden, but you likely want to align JTH version with the new Jetty version. The JTH you use as a dependency it pretty old. If you use new Jenkins parent POMs, they will help you to avoid such conflicts, because Maven Enforcer Plugin is configured to run there  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49630) Unable to view configuration of some projects after upgrade to 2.107

2018-02-19 Thread ralph.go...@dslextreme.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ralph Goers edited a comment on  JENKINS-49630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to view configuration of some projects after upgrade to 2.107   
 

  
 
 
 
 

 
 Digging further we see that select.js updateListBox is calling hudson-behavior.js findFollowingTR which is returning undefined, causing the subsequent code to fail. ! See https://issues.jenkins-ci.org/secure/attachment/41529/ image-2018-02-19-12- 06 03 - 02 57 - 174 775 .png !  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-48868) blue ocean dashboard taking more than 50s to load.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-48868  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: blue ocean dashboard taking more than 50s to load.   
 

  
 
 
 
 

 
 Joshua Hoblitt, sorry not enough info in this ticket.   Tl;dr version:  Fix was to return run summary in latestRun instead of full Run object graph. See https://github.com/jenkinsci/blueocean-plugin/pull/1635.   More details: Dashbaord lists pipelines and favorites. In both cases each pipeline also includes 'latestRun' property that includes complete Run object. Run objects can be very expensive and includes expensive objects such as changeSets and many others. Further, it was validated to be the case going over HAR files submitted by users on this ticket and others.  Favorites can be expensive too, specially it was resulting in to expensive computation and fact that we autofavorite and need all favorites so that we can show in pipeline/branch/activities pages - had more involved fixes. This is fixed as well, see PR https://github.com/jenkinsci/blueocean-plugin/pull/1638.   Both PRs are merged to master. If you can, please give it a try. By the end of this week or early next week we are going to release 1.5-beta-1 and that should have these fixes as well.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49630) Unable to view configuration of some projects after upgrade to 2.107

2018-02-19 Thread ralph.go...@dslextreme.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ralph Goers edited a comment on  JENKINS-49630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to view configuration of some projects after upgrade to 2.107   
 

  
 
 
 
 

 
 Digging further we see that select.js updateListBox is calling hudson-behavior.js findFollowingTR which is returning undefined, causing the subsequent code to fail.   !image-2018-02-19-12- 03 06 - 57 02 - 775 174 .png!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49630) Unable to view configuration of some projects after upgrade to 2.107

2018-02-19 Thread ralph.go...@dslextreme.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ralph Goers commented on  JENKINS-49630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to view configuration of some projects after upgrade to 2.107   
 

  
 
 
 
 

 
 Digging further we see that select.js updateListBox is calling hudson-behavior.js findFollowingTR which is returning undefined, causing the subsequent code to fail.     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49630) Unable to view configuration of some projects after upgrade to 2.107

2018-02-19 Thread ralph.go...@dslextreme.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ralph Goers updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49630  
 
 
  Unable to view configuration of some projects after upgrade to 2.107   
 

  
 
 
 
 

 
Change By: 
 Ralph Goers  
 
 
Attachment: 
 image-2018-02-19-12-03-57-775.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49632) MavenLinkerPublisher - missing classifier and secondary artifacts

2018-02-19 Thread dant...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 dan tran updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49632  
 
 
  MavenLinkerPublisher - missing classifier and secondary artifacts   
 

  
 
 
 
 

 
Change By: 
 dan tran  
 
 
Summary: 
 MavenLinkerPublisher - missing classifier and secondary  artifact  artifacts  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49632) MavenLinkerPublisher - missing classifier and secondary artifact

2018-02-19 Thread dant...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 dan tran created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49632  
 
 
  MavenLinkerPublisher - missing classifier and secondary artifact   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Alvaro Lobato  
 
 
Components: 
 pipeline-maven-plugin  
 
 
Created: 
 2018-02-19 18:56  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 dan tran  
 

  
 
 
 
 

 
 Currently, "Deployed Artifact" only shows primary artifacts.  Those deployed by attach mechanism are missing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-46638) Null pointer exception saving a parameterized freestyle job with no parameters defined

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kseniia Nenasheva commented on  JENKINS-46638  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Null pointer exception saving a parameterized freestyle job with no parameters defined   
 

  
 
 
 
 

 
 PR #3300  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-46638) Null pointer exception saving a parameterized freestyle job with no parameters defined

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kseniia Nenasheva updated  JENKINS-46638  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46638  
 
 
  Null pointer exception saving a parameterized freestyle job with no parameters defined   
 

  
 
 
 
 

 
Change By: 
 Kseniia Nenasheva  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49630) Unable to view configuration of some projects after upgrade to 2.107

2018-02-19 Thread ralph.go...@dslextreme.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ralph Goers commented on  JENKINS-49630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to view configuration of some projects after upgrade to 2.107   
 

  
 
 
 
 

 
 We were on 2.76. I am not sure to tell you the versions of all the plugins we were using.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49630) Unable to view configuration of some projects after upgrade to 2.107

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to view configuration of some projects after upgrade to 2.107   
 

  
 
 
 
 

 
 Which version have been using before the upgrade BTW?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49630) Unable to view configuration of some projects after upgrade to 2.107

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49630  
 
 
  Unable to view configuration of some projects after upgrade to 2.107   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 regression  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49625) Config pages of Maven jobs do no load

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49625  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Config pages of Maven jobs do no load   
 

  
 
 
 
 

 
 Looks similar to JENKINS-49630  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49630) Unable to view configuration of some projects after upgrade to 2.107

2018-02-19 Thread ralph.go...@dslextreme.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ralph Goers commented on  JENKINS-49630  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to view configuration of some projects after upgrade to 2.107   
 

  
 
 
 
 

 
 In stepping through the code where the error is occurring I can see it is going through an HTMLCollection that contains a set of div.credentials-select-control objects. I am having some trouble getting any deeper.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions

2018-02-19 Thread timothy.mcna...@build.com (JIRA)

Title: Message Title

Tim McNally commented on JENKINS-49543

Re: Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions

Then you did not properly configuring logging.
I did, but I did not know that what I was looking for was during start up.

it is advisable to install the support-core plugin
Thanks that is a handy plugin. I have it installed now. I have downgraded our Tomcat version to get you the information requested. I attached the logs from the jenkins.security.ClassFilterImpl recorder. If you need a different log, please let me know soon as I will need to put our server back on Tomcat 8.5.28. Here is the line that seems relevant from the log:

2018-02-19 18:09:58.169+ [id=25] FINE jenkins.security.ClassFilterImpl: jar:file:/srv/tomcat/tomcat_app/webapps/jenkins/WEB-INF/lib/ssh-cli-auth-1.4.jar!/ is not recognized; rejecting

As far as running Jenkins on the embedded Jetty server, is there any information about migrating from Tomcat to the embedded server? We ran our server using Tomcat as that was what was convenient when we setup our server ~3 years ago, but obviously are interested in running our Jenkins instance in the most supported way possible. Thank you for your assistance on this issue.

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-49625) Config pages of Maven jobs do no load

2018-02-19 Thread christoph.dr...@innogames.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Dreis edited a comment on  JENKINS-49625  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Config pages of Maven jobs do no load   
 

  
 
 
 
 

 
 We're actually seeing a similar behavior as JENKINS-49630 Yet, this seems to be unrelated to Bitbucket, but to a normal git setup.{color:#22}descriptorByName/hudson.plugins.git.UserRemoteConfig/fillCredentialsIdItems{color}\{code}updateListBox (select.js:4)(anonymous) (select.js:79)h (hudson-behavior.js:1304)refillOnChange (hudson-behavior.js:1319)(anonymous) (select.js:77)(anonymous) (behavior.js:111)(anonymous) (behavior.js:107)applySubtree (behavior.js:93)(anonymous) (select.js:269)setTimeout (async)(anonymous) (select.js:263)\{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions

2018-02-19 Thread timothy.mcna...@build.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim McNally updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49543  
 
 
  Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl on Old Apache TomCat 8.x versions   
 

  
 
 
 
 

 
Change By: 
 Tim McNally  
 
 
Attachment: 
 jenkins.security.ClassFilterImpl.zip  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49625) Config pages of Maven jobs do no load

2018-02-19 Thread christoph.dr...@innogames.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Dreis commented on  JENKINS-49625  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Config pages of Maven jobs do no load   
 

  
 
 
 
 

 
 We're actually seeing a similar behavior as JENKINS-49630  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-46638) Null pointer exception saving a parameterized freestyle job with no parameters defined

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kseniia Nenasheva assigned an issue to Kseniia Nenasheva  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46638  
 
 
  Null pointer exception saving a parameterized freestyle job with no parameters defined   
 

  
 
 
 
 

 
Change By: 
 Kseniia Nenasheva  
 
 
Assignee: 
 Kseniia Nenasheva  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-46638) Null pointer exception saving a parameterized freestyle job with no parameters defined