[JIRA] (JENKINS-49720) NVM wrapper hard-coded path

[p.no...@dhl.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Novak commented on  JENKINS-49720  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NVM wrapper hard-coded path   
 

  
 
 
 
 

 
 Thank you very much, I appreciate 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-49787) Jenkins.createProjectFromXml() formats xml differently than AbstractItem.save()

[aaandra...@yahoo.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Petres Andras created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49787  
 
 
  Jenkins.createProjectFromXml() formats xml differently than AbstractItem.save()   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Spilker  
 
 
Attachments: 
 diff.png  
 
 
Components: 
 core, job-dsl-plugin, jobconfighistory-plugin  
 
 
Created: 
 2018-02-28 07:36  
 
 
Environment: 
 Jenkins 2.106  job-dsl-plugin 1.68  jobConfigHistory plugin 2.18  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Petres Andras  
 

  
 
 
 
 

 
 Hello, We generate our jobs using job-dsl plugin and we want to track custom changes to jobs using job-config-history plugin which compares job xml. Note that job-dsl-plugin relies on Jenkins.createProjectFromXml() to generate job xml. We noticed that after a generated job is saved (via the web UI) or a build is started, the job xml is rewritten via AbstractItem.save() adding a change to job config history. The differences are (see image attached): 
 
XML version 1.1 in file generated by save versus version 1.0 (introduced in Jenkins 2.105) 
different indentation 
different order of tags 
 Is there a way to assure that job xml formatting is independent of the way of creation?  
 

  
 
 

[JIRA] (JENKINS-48798) Error when using HP ALM Quality in a Post Build step

[ka...@hpe.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yafim Kazak assigned an issue to Roy Lu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48798  
 
 
  Error when using HP ALM Quality in a Post Build step   
 

  
 
 
 
 

 
Change By: 
 Yafim Kazak  
 
 
Assignee: 
 Ofir Shaked Roy Lu  
 

  
 
 
 
 

 
 
 

 
 
 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-47464) Prettier autoformating

[jmcdon...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh McDonald edited a comment on  JENKINS-47464  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prettier autoformating   
 

  
 
 
 
 

 
 PR to adjust documentation  https://github.com/jenkinsci/blueocean-plugin/pull/1679  
 

  
 
 
 
 

 
 
 

 
 
 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-47464) Prettier autoformating

[jmcdon...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh McDonald commented on  JENKINS-47464  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prettier autoformating   
 

  
 
 
 
 

 
 PR to adjust documentation  
 

  
 
 
 
 

 
 
 

 
 
 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-41922) "Minimum instances" support

[vscjenk...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Azure DevOps resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in 0.4.8 (pool retention strategy).  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41922  
 
 
  "Minimum instances" support   
 

  
 
 
 
 

 
Change By: 
 Azure DevOps  
 
 
Status: 
 Open 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-49576) Failure creating provisioned agent after successful provisioning

[vscjenk...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Azure DevOps assigned an issue to Chenyang Liu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49576  
 
 
  Failure creating provisioned agent after successful provisioning
 

  
 
 
 
 

 
Change By: 
 Azure DevOps  
 
 
Assignee: 
 Azure DevOps Chenyang Liu  
 

  
 
 
 
 

 
 
 

 
 
 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-49473) Unable to delete Azure VM Agent from Jenkins after having deleted agent directly on Azure

[vscjenk...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Azure DevOps assigned an issue to Chenyang Liu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49473  
 
 
  Unable to delete Azure VM Agent from Jenkins after having deleted agent directly on Azure   
 

  
 
 
 
 

 
Change By: 
 Azure DevOps  
 
 
Assignee: 
 Azure DevOps Chenyang Liu  
 

  
 
 
 
 

 
 
 

 
 
 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-49345) FTP Upload failed Azure Germany

[vscjenk...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Azure DevOps assigned an issue to Dayang Shen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49345  
 
 
  FTP Upload failed Azure Germany   
 

  
 
 
 
 

 
Change By: 
 Azure DevOps  
 
 
Assignee: 
 Azure DevOps Dayang Shen  
 

  
 
 
 
 

 
 
 

 
 
 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-48253) Empty list of existing Storage Account Names

[vscjenk...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Azure DevOps assigned an issue to Chenyang Liu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48253  
 
 
  Empty list of existing Storage Account Names   
 

  
 
 
 
 

 
Change By: 
 Azure DevOps  
 
 
Assignee: 
 Azure DevOps Chenyang Liu  
 

  
 
 
 
 

 
 
 

 
 
 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-32568) Add custom-data to Azure slave deployment

[vscjenk...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Azure DevOps assigned an issue to Chenyang Liu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32568  
 
 
  Add custom-data to Azure slave deployment   
 

  
 
 
 
 

 
Change By: 
 Azure DevOps  
 
 
Assignee: 
 Azure DevOps Chenyang Liu  
 

  
 
 
 
 

 
 
 

 
 
 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-30014) Builds hang, Jenkins still browseable

[vscjenk...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Azure DevOps assigned an issue to Chenyang Liu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-30014  
 
 
  Builds hang, Jenkins still browseable   
 

  
 
 
 
 

 
Change By: 
 Azure DevOps  
 
 
Assignee: 
 Azure DevOps Chenyang Liu  
 

  
 
 
 
 

 
 
 

 
 
 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-41569) Pipeline hangs waiting for resume on an agent which never was

[vscjenk...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Azure DevOps assigned an issue to Chenyang Liu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41569  
 
 
  Pipeline hangs waiting for resume on an agent which never was   
 

  
 
 
 
 

 
Change By: 
 Azure DevOps  
 
 
Assignee: 
 Azure DevOps Chenyang Liu  
 

  
 
 
 
 

 
 
 

 
 
 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-40635) Add Availability Set configuration to Azure slave plugin

[vscjenk...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Azure DevOps assigned an issue to Chenyang Liu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40635  
 
 
  Add Availability Set configuration to Azure slave plugin   
 

  
 
 
 
 

 
Change By: 
 Azure DevOps  
 
 
Assignee: 
 Azure DevOps Chenyang Liu  
 

  
 
 
 
 

 
 
 

 
 
 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-41381) Allow for passing of secrets to startup scripts

[vscjenk...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Azure DevOps assigned an issue to Chenyang Liu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41381  
 
 
  Allow for passing of secrets to startup scripts   
 

  
 
 
 
 

 
Change By: 
 Azure DevOps  
 
 
Assignee: 
 Azure DevOps Chenyang Liu  
 

  
 
 
 
 

 
 
 

 
 
 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-47306) 'Create First Admin user' page not handling missing values.

[kzan...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow commented on  JENKINS-47306  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 'Create First Admin user' page not handling missing values.   
 

  
 
 
 
 

 
 I don't think this is a duplicate. At one point there was handling for this stuff, it was just delegating to the main Jenkins registration screen, but at least it showed errors and didn't let you proceed until they were fixed. Clearly something has changed since then, maybe in handling of posting back those pages, which might indeed be directly related to JENKINS-48352  
 

  
 
 
 
 

 
 
 

 
 
 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-41805) Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace.

[hiten.prajapati...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hiten Prajapati commented on  JENKINS-41805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace.   
 

  
 
 
 
 

 
 please Help me this is still problem me cos we have many jobs with many branches in project that's make my ssd full.   
 

  
 
 
 
 

 
 
 

 
 
 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-49742) Multi-line string seems to be broken when triggered from the pipeline.

[oleksandrkushc...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleksandr Kushchak commented on  JENKINS-49742  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multi-line string seems to be broken when triggered from the pipeline.   
 

  
 
 
 
 

 
 Oleg Nenashev I have not tried doing this before, so I can't comment on the 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-49742) Multi-line string seems to be broken when triggered from the pipeline.

[oleksandrkushc...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleksandr Kushchak edited a comment on  JENKINS-49742  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multi-line string seems to be broken when triggered from the pipeline.   
 

  
 
 
 
 

 
 [~oleg_nenashev] I  have 've  not tried doing this before, so I can't comment on the 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-16738) Pressing "Test Configuration" pops up message "failed to evaluate. Invalid Argument" message box

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-16738  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pressing "Test Configuration" pops up message "failed to evaluate. Invalid Argument" message box   
 

  
 
 
 
 

 
 Can you provide a screenshot of this issue?  
 

  
 
 
 
 

 
 
 

 
 
 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-49786) Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up

[zi...@heavysoft.ru (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Anton Zimin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49786  
 
 
  Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up   
 

  
 
 
 
 

 
Change By: 
 Anton Zimin  
 

  
 
 
 
 

 
 Jenkins 2.89.3Git client plugin 2.7.1Git plugin 3.8.0Pipeline 2.5Create pipeline from SCM, use *wrong* as local branch name.!2018-02-28_1145.png!Jenkinsfile:{code:java}pipeline {agent anystages {stage ('SCM') {steps {script {echo '1'bat script: 'git remote -v'bat script: 'git branch'checkout([$class: 'GitSCM', branches: [[name: 'develop']], extensions: [[$class: 'LocalBranch', localBranch: 'expected']], //extensions: [[$class: 'LocalBranch', localBranch: 'expected'], [$class: 'WipeWorkspace']], userRemoteConfigs: [[url: 'ssh://gitblit.example.com/anton/jenkins-project.git', credentialsId: 'jenkins-ssh-credential']]])echo '2'bat script: 'git remote -v'bat script: 'git branch'}}}}}{code}*First build (Log1.txt)*Branches after Jenkinsfile checkout:{code}* wrong{code}Branches after project repo checkout:{code}* expected  wrong{code}An unexpected branch *wrong* exists in the list.*Second build (Log2.txt)*Branches after Jenkinsfile checkout:{code}  expected* wrong{code}An unexpected branch *expected* exists in the list.Branches after project repo checkout:{code}* expected  wrong{code}An unexpected branch *wrong* exists in the list.*Build with WipeWorkspace extension (LogWipe.txt)*Branches after Jenkinsfile checkout:{code}* wrong{code}{code}* expected{code}Everything is good, but I don't need to clone the repository every time. PruneStaleBranch extension does not help (I guess it deletes only tracked branches). 1. Why does Jenkins use my workspace to checkout Jenkisfile? I expect it to use a temp dir, like libLoader does.2. Why does it mix branches for unrelated repositories? Does it manually change .git/ content somehow?Similar issue: JENKINS-30619  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
 

[JIRA] (JENKINS-49786) Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up

[zi...@heavysoft.ru (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Anton Zimin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49786  
 
 
  Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up   
 

  
 
 
 
 

 
Change By: 
 Anton Zimin  
 

  
 
 
 
 

 
 Jenkins 2.89.3Git client plugin 2.7.1Git plugin 3.8.0Pipeline 2.5Create pipeline from SCM, use *wrong* as local branch name.!2018-02-28_1145.png!Jenkinsfile:{code:java}pipeline {agent anystages {stage ('SCM') {steps {script {echo '1'bat script: 'git remote -v'bat script: 'git branch'checkout([$class: 'GitSCM', branches: [[name: 'develop']], extensions: [[$class: 'LocalBranch', localBranch: 'expected']], //extensions: [[$class: 'LocalBranch', localBranch: 'expected'], [$class: 'WipeWorkspace']], userRemoteConfigs: [[url: 'ssh://gitblit.example.com/anton/jenkins-project.git', credentialsId: 'jenkins-ssh-credential']]])echo '2'bat script: 'git remote -v'bat script: 'git branch'}}}}}{code}*First build (Log1.txt)*Branches after Jenkinsfile checkout:{code}* wrong{code}Branches after project repo checkout:{code}* expected  wrong{code}An unexpected branch *wrong* exists in the list.*Second build (Log2.txt)*Branches after Jenkinsfile checkout:{code}  expected* wrong{code}An unexpected branch *expected* exists in the list.Branches after project repo checkout:{code}* expected  wrong{code}An unexpected branch *wrong* exists in the list.*Build with WipeWorkspace extension (LogWipe.txt)*Branches after Jenkinsfile checkout:{code}* wrong{code}{code}* expected{code}Everything is good, but I don't need to clone the repository every time.1. Why does Jenkins use my workspace to checkout Jenkisfile? I expect it to use a temp dir, like libLoader does.2. Why does it mix branches for unrelated repositories? Does it manually change .git/ content somehow? Similar issue: JENKINS-30619  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

 

[JIRA] (JENKINS-49786) Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up

[zi...@heavysoft.ru (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Anton Zimin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49786  
 
 
  Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up   
 

  
 
 
 
 

 
Change By: 
 Anton Zimin  
 
 
Attachment: 
 Log1.txt  
 
 
Attachment: 
 Log2.txt  
 
 
Attachment: 
 LogWipe.txt  
 

  
 
 
 
 

 
 
 

 
 
 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-49786) Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up

[zi...@heavysoft.ru (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Anton Zimin created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49786  
 
 
  Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Attachments: 
 2018-02-28_1145.png  
 
 
Components: 
 git-client-plugin, pipeline  
 
 
Created: 
 2018-02-28 05:06  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Anton Zimin  
 

  
 
 
 
 

 
 Jenkins 2.89.3 Git client plugin 2.7.1 Git plugin 3.8.0 Pipeline 2.5 
 Create pipeline from SCM, use wrong as local branch name.  Jenkinsfile: 

 


pipeline {
agent any

stages {
stage ('SCM') {
steps {
script {
echo '1'
bat script: 'git remote -v'
bat script: 'git branch'

checkout([$class: 'GitSCM', branches: [[name: 'develop']],
extensions: [[$class: 'LocalBranch', localBranch: 'expected']],
//extensions: [[$class: 'LocalBranch', localBranch: 'expected'], [$class: 'WipeWorkspace']],
userRemoteConfigs: [[url: 'ssh://gitblit.example.com/anton/jenkins-project.git',
credentialsId: 'jenkins-ssh-credential']]])

echo '2'
bat script: 'git remote -v'
bat script: 'git branch'
}
}
}
}
} 

 First build (Log1.txt) Branches after Jenkinsfile checkout: 
 

[JIRA] (JENKINS-16240) Problem with NOT_BUILT build result

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-16240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Problem with NOT_BUILT build result   
 

  
 
 
 
 

 
 I just took over these plugins recently, I am going through issues and looking. I'll review this and see if its something I can debug soon.  
 

  
 
 
 
 

 
 
 

 
 
 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-10674) Publish over CIFS performance is slow

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-10674  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Publish over CIFS performance is slow   
 

  
 
 
 
 

 
 Have you tried the latest version that allows you to set a buffer size? Please try changing the default buffer size to something larger and see if that increases performance.  
 

  
 
 
 
 

 
 
 

 
 
 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-7892) Support TestCase attribute patch.

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl resolved as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-7892  
 
 
  Support TestCase attribute patch.   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 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-49785) Add param for export changelog filename.

[zxj...@126.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 suren pi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49785  
 
 
  Add param for export changelog filename.   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 suren pi  
 
 
Components: 
 workflow-scm-step-plugin  
 
 
Created: 
 2018-02-28 04:44  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 suren pi  
 

  
 
 
 
 

 
 We want get the file of changelog (e.g. changelog0.xml changelog1.xml), then fetch useful infomation. But the filename is increased. So We can add a param for export the file nam, I suggest.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

[JIRA] (JENKINS-49768) GITEA Organization Job. Could not fetch branches from source when we use Gitea SSH built-in server

[olec...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksandr Gamoskin assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49768  
 
 
  GITEA Organization Job. Could not fetch branches from source when we use Gitea SSH built-in server   
 

  
 
 
 
 

 
Change By: 
 Aleksandr Gamoskin  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 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-49782) Pretested Integration Plugin failed to clean all ready branches merged

[vw...@toronto.ca (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Weng updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49782  
 
 
  Pretested Integration Plugin failed to clean all ready branches merged   
 

  
 
 
 
 

 
Change By: 
 Victor Weng  
 

  
 
 
 
 

 
 Sometimes developer pushed to another ready/ branch by typo, resulted in remote with 2 ready branches rooted from the same local branch. The pretested plugin does merge them, as following:```*21:08:13*  > git show-ref --tags -d # timeout=10*21:08:13* [PREINT]  Pretested Integration Plugin v3.0.0 (9fd14)*21:08:13* [PREINT] Checking out integration branch master:*21:08:13*  > git config core.sparsecheckout # timeout=10*21:08:13*  > git checkout -f origin/master*21:08:13*  > git branch -a -v --no-abbrev # timeout=10*21:08:13*  > git checkout -b master origin/master*21:08:13* [PREINT] Branch commit count: 2*21:08:13* [PREINT] Skip FF as there are several commits*21:08:13* [PREINT] Preparing to merge changes in commit 01cf8ca58f9afaed607c3214551f60ca1a5c828e on development branch origin/ready/vweng1 to integration branch master*21:08:13* Seen branch in repository origin/master*21:08:13* Seen branch in repository origin/ready/vw1*21:08:13* Seen branch in repository origin/ready/vweng1*21:08:13* Seen branch in repository origin/release*21:08:13* Seen branch in repository origin/vic*21:08:13* Seen branch in repository origin/vweng*21:08:13* Seen 6 remote branches*21:08:13* [PREINT] Collecting commit messages on development branch origin/ready/vweng1*21:08:13* [PREINT] Done collecting commit messages*21:08:13* [PREINT] Collecting author of last commit on development branch*21:08:13* [PREINT] Done collecting last commit author: Victor  Weng  < Victor.Weng  @ toronto  . ca xxx > 1519783628 -0500*21:08:13* [PREINT] Starting accumulated merge (no-ff) - without commit:*21:08:13*  > git merge --no-commit -m Accumulated commit of the following from branch 'origin/ready/vweng1':*21:08:13* *21:08:13* commit 01cf8ca58f9afaed607c3214551f60ca1a5c828e*21:08:13* Author: Victor  Weng  < Victor.Weng  @ toronto  . ca xxx >*21:08:13* Date:   Tue Feb 27 21:07:08 2018 -0500*21:08:13* *21:08:13* test*21:08:13* *21:08:13* *21:08:13* commit d75c103d0d3a41fae8a37182c1e19530e576d3a2*21:08:13* Author: Victor  Weng  < Victor.Weng  @ toronto  . ca xxx >*21:08:13* Date:   Tue Feb 27 21:04:39 2018 -0500*21:08:13* *21:08:13* update*21:08:13* *21:08:13* *21:08:13*  --no-ff 01cf8ca58f9afaed607c3214551f60ca1a5c828e # timeout=10*21:08:13* [PREINT] Merge was successful*21:08:13* [PREINT] Starting to commit accumulated merge changes:*21:08:13*  > git commit -F /var/jenkins_home/workspace/c3_template@tmp/gitcommit7900359076344737293.txt # timeout=10*21:08:13* [PREINT] Commit of accumulated merge done*21:08:13* [PREINT] Commit was successful*21:08:13*  > git rev-parse HEAD^\{commit} # timeout=10*21:08:13* Seen branch in repository origin/master*21:08:13* Seen branch in repository origin/ready/vw1*21:08:13* Seen branch in repository origin/ready/vweng1*21:08:13* Seen branch in repository origin/release*21:08:13* Seen branch in repository 

[JIRA] (JENKINS-49782) Pretested Integration Plugin failed to clean all ready branches merged

[vw...@toronto.ca (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Weng updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49782  
 
 
  Pretested Integration Plugin failed to clean all ready branches merged   
 

  
 
 
 
 

 
Change By: 
 Victor Weng  
 
 
Summary: 
 Pretested Integration Plugin  3.0  failed to  process more than 1  clean all  ready branches  merged  
 
 
Priority: 
 Critical Minor  
 

  
 
 
 
 

 
 When there are more than 1 Sometimes developer pushed to another   ready / branch by typo, resulted in remote with 2 ready  branches  waiting to be integrated  rooted from the same local branch. The pretested plugin does merge them ,  e  as following:```*21:08:13*  > git show-ref --tags -d # timeout=10*21:08:13* [PREINT]  Pretested Integration Plugin v3 . g 0 . 0 (9fd14)*21:08:13* [PREINT] Checking out integration branch master:*21:08:13*  > git config core.sparsecheckout # timeout=10*21:08:13*  > git checkout -f origin/master*21:08:13*  > git branch -a -v --no-abbrev # timeout=10*21:08:13*  > git checkout -b master origin/master*21:08:13* [PREINT] Branch commit count: 2*21:08:13* [PREINT] Skip FF as there are several commits*21:08:13* [PREINT] Preparing to merge changes in commit 01cf8ca58f9afaed607c3214551f60ca1a5c828e on development branch origin/  ready/ vweng1 to integration branch master*21:08:13* Seen branch in repository origin/master*21:08:13* Seen branch in repository origin/ready/ vw1  and *21:08:13* Seen branch in repository origin/  ready/ vw2 both checked into github waiting vweng1*21:08:13* Seen branch in repository origin/release*21:08:13* Seen branch in repository origin/vic*21:08:13* Seen branch in repository origin/vweng*21:08:13* Seen 6 remote branches*21:08:13* [PREINT] Collecting commit messages on development branch origin/ready/vweng1*21:08:13* [PREINT] Done collecting commit messages*21:08:13* [PREINT] Collecting author of last commit on development branch*21:08:13* [PREINT] Done collecting last commit author: Victor Weng  1519783628 -0500*21:08:13* [PREINT] Starting accumulated merge (no-ff) - without commit:*21:08:13*  > git merge --no-commit -m Accumulated commit of the following from branch 'origin/ready/vweng1':*21:08:13* *21:08:13* commit 01cf8ca58f9afaed607c3214551f60ca1a5c828e*21:08:13* Author: Victor Weng *21:08:13* Date:   Tue Feb 27 21:07:08 2018 -0500*21:08:13* *21:08:13* test*21:08:13* *21:08:13* *21:08:13* commit d75c103d0d3a41fae8a37182c1e19530e576d3a2*21:08:13* Author: Victor Weng *21:08:13* Date:   Tue Feb 27 21:04:39 2018 -0500*21:08:13* *21:08:13* update*21:08:13* *21:08:13* *21:08:13*  --no-ff 01cf8ca58f9afaed607c3214551f60ca1a5c828e # timeout=10*21:08:13* 

[JIRA] (JENKINS-49784) Can not select Docker Swarm in Cloud

[luckyhk....@samsung.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hokwang Lee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49784  
 
 
  Can not select Docker Swarm in Cloud   
 

  
 
 
 
 

 
Change By: 
 Hokwang Lee  
 

  
 
 
 
 

 
 Recently I am looking forward to using better docker swarm plugin.I really hope this plugin provide awesome features to users. Anyway, I 've seen this plugin and installed.But I can not select Docker Swarm in Cloud section.  And also I request very basic example using this plugin,from how to set docker swarm (some docker service commands)to install and set this plugin.and use for build (the first step of CI/CD).    
 

  
 
 
 
 

 
 
 

 
 
 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-49784) Can not select docker swarm in Cloud

[luckyhk....@samsung.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hokwang Lee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49784  
 
 
  Can not select docker swarm in Cloud   
 

  
 
 
 
 

 
Change By: 
 Hokwang Lee  
 
 
Summary: 
 can Can  not select docker swarm  in Cloud  
 

  
 
 
 
 

 
 
 

 
 
 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-49784) Can not select Docker Swarm in Cloud

[luckyhk....@samsung.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hokwang Lee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49784  
 
 
  Can not select Docker Swarm in Cloud   
 

  
 
 
 
 

 
Change By: 
 Hokwang Lee  
 
 
Summary: 
 Can not select  docker swarm  Docker Swarm  in Cloud  
 

  
 
 
 
 

 
 
 

 
 
 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-49784) can not select docker swarm

[luckyhk....@samsung.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hokwang Lee created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49784  
 
 
  can not select docker swarm   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 surya gaddipati  
 
 
Components: 
 docker-swarm-plugin  
 
 
Created: 
 2018-02-28 04:20  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Hokwang Lee  
 

  
 
 
 
 

 
 Recently I am looking forward to using better docker swarm plugin. I really hope this plugin provide awesome features to users.   Anyway, I 've seen this plugin and installed. But I can not select Docker Swarm in Cloud section.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message 

[JIRA] (JENKINS-49783) get current changelog.xml file when checkout code with svn

[fanjin2...@126.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 fan jin created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49783  
 
 
  get current changelog.xml file when checkout code with svn
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 fan jin  
 
 
Components: 
 subversion-plugin  
 
 
Created: 
 2018-02-28 03:42  
 
 
Environment: 
 Jenkins ver. 2.19.3  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 fan jin  
 

  
 
 
 
 

 
 I know it will generate several changelog.xml when I create several checkout step for svn build and only build once 。So I want get the current chanlgelog.xml .For example ,I checkout A,B,C project from svn in one build .A generete changelog0.xml ,B  generete changelog1.xml.C generete changelog2.xml ,I want have a variable to identify chanlelog0.xml,because I need use the variable later.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
  

[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step

[jmcdon...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh McDonald commented on  JENKINS-38339  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: UI for downstream jobs launched with 'build' step   
 

  
 
 
 
 

 
 UI changes PR: https://github.com/jenkinsci/blueocean-plugin/pull/1675  
 

  
 
 
 
 

 
 
 

 
 
 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-49756) InvocationTargetException when connecting to Bitbucket server with an empty repo

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49756  
 
 
  InvocationTargetException when connecting to Bitbucket server with an empty repo   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Sprint: 
 Blue Ocean 1.5 - 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-49756) InvocationTargetException when connecting to Bitbucket server with an empty repo

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated  JENKINS-49756  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49756  
 
 
  InvocationTargetException when connecting to Bitbucket server with an empty repo   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
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-49756) InvocationTargetException when connecting to Bitbucket server with an empty repo

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey started work on  JENKINS-49756  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
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-49756) InvocationTargetException when connecting to Bitbucket server with an empty repo

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-49756  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: InvocationTargetException when connecting to Bitbucket server with an empty repo   
 

  
 
 
 
 

 
 Missed this error in the log: 

 

Caused by: com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input
 at [Source: UNKNOWN; line: 1, column: 0]
	at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:270)
	at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:3854)
	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3799)
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2931)
	at io.jenkins.blueocean.blueocean_bitbucket_pipeline.server.BitbucketServerApi.getDefaultBranch(BitbucketServerApi.java:290)
 

 Looks like for empty repo we are expecting HTTP status 404 but getting 204 when we call default branch API. This change happened in BB server 5.6.0, https://jira.atlassian.com/browse/BSERV-10313. PR opened: https://github.com/jenkinsci/blueocean-plugin/pull/1678.  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-49756) InvocationTargetException when connecting to Bitbucket server with an empty repo

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey assigned an issue to Vivek Pandey  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49756  
 
 
  InvocationTargetException when connecting to Bitbucket server with an empty repo   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Assignee: 
 Vivek Pandey  
 

  
 
 
 
 

 
 
 

 
 
 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-42197) Job import plugin refreshes the page after clicking on "Query" button

[john.wa...@northwestern.edu (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 John Walsh commented on  JENKINS-42197  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job import plugin refreshes the page after clicking on "Query" button   
 

  
 
 
 
 

 
 Same issue...  
 

  
 
 
 
 

 
 
 

 
 
 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-49746) Regex returns more matches than it should if errors are close together

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-49746  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regex returns more matches than it should if errors are close together   
 

  
 
 
 
 

 
 Do you have any test data I could test on this with?  
 

  
 
 
 
 

 
 
 

 
 
 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-49782) Pretested Integration Plugin 3.0 failed to process more than 1 ready branches

[vw...@toronto.ca (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Weng created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49782  
 
 
  Pretested Integration Plugin 3.0 failed to process more than 1 ready branches   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Praqma Support  
 
 
Components: 
 pretested-integration-plugin  
 
 
Created: 
 2018-02-28 02:36  
 
 
Environment: 
 Jenkins 2.89.4, Pretested plugin 3.0.0  
 
 
Labels: 
 plugin jenkins pretested  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Victor Weng  
 

  
 
 
 
 

 
 When there are more than 1 ready branches waiting to be integrated, e.g. ready/vw1 and ready/vw2 both checked into github waiting to be merged, the new 3.0 pretested plugin only merges 1 and leaves the other un-merged. And upon the next poll, it will start to merge the others but with an error as following: 21:13:13 [PREINT] Starting accumulated merge (no-ff) - without commit:21:13:13 > git merge --no-commit -m Accumulated commit of the following from branch 'origin/ready/vw1':21:13:13 21:13:13 --no-ff d75c103d0d3a41fae8a37182c1e19530e576d3a2 # timeout=10*21:13:13* [PREINT] Merge was successful*21:13:13* [PREINT] Starting to commit accumulated merge changes:21:13:13 [PREINT] [PREINT] - setUp() - NothingToDoException - Nothing to do. The reason is: No MERGE_MSG found in .git, there was nothing to merge The result is developer would have to commit some new changes again to the not-yet-merged ready branch. This wasn't happening in 2.x and is way too annoying to defeat the purpose of having pretested workflow.  
 

  
 
   

[JIRA] (JENKINS-49781) Please provide a means for securely providing credentials for Kubernetes deployments.

[menx...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Menghua Xiao commented on  JENKINS-49781  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Please provide a means for securely providing credentials for Kubernetes deployments.   
 

  
 
 
 
 

 
 I see the point. Currently the credentials are exposed in the kubernetesDeploy call if we are using Pipeline. It would be better the kubeconfig related things are stored in the Jenkins credentials store. They are less likely to be changed from deployments to deployments. The pipeline just reference them through the credentials ID. I will start implement this.  
 

  
 
 
 
 

 
 
 

 
 
 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-49756) InvocationTargetException when connecting to Bitbucket server with an empty repo

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-49756  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: InvocationTargetException when connecting to Bitbucket server with an empty repo   
 

  
 
 
 
 

 
 Karl Shultz followed your steps with BB server 5.2.0 and it worked fine with brand new empty repo. I suspect it might be a later version of BB server with something in response that blueocean BB server code is not handling properly. Let us know what version of BB server you see this issue.   
 

  
 
 
 
 

 
 
 

 
 
 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-47487) Current build status condition always shown as success

[henry_...@agilent.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Henry Lee commented on  JENKINS-47487  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Current build status condition always shown as success   
 

  
 
 
 
 

 
 Yes, this is a problem for me too. Jenkins version 2.73.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-49763) Duration time is incorrect in a parallel pipeline step.

[zxj...@126.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 suren pi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49763  
 
 
  Duration time is incorrect in a parallel pipeline step.   
 

  
 
 
 
 

 
Change By: 
 suren pi  
 

  
 
 
 
 

 
 I got a negative number from pipeline workflow api, that is a  during  duration  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-49763) Duration time is incorrect in a parallel pipeline step.

[zxj...@126.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 suren pi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49763  
 
 
  Duration time is incorrect in a parallel pipeline step.   
 

  
 
 
 
 

 
Change By: 
 suren pi  
 
 
Summary: 
 During Duration  time is incorrect in a parallel pipeline step.  
 

  
 
 
 
 

 
 
 

 
 
 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-49773) Pipeline plugin sh script returned exit code -2 from time to time

[279245...@qq.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 yang guilei updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49773  
 
 
  Pipeline plugin sh script returned exit code -2 from time to time   
 

  
 
 
 
 

 
Change By: 
 yang guilei  
 
 
Environment: 
 kubernetes1.8.4 jenkins 2.32.3(fabric8/jenkins-docker)  jenkins kubernetes plugin 1.3.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-49756) InvocationTargetException when connecting to Bitbucket server with an empty repo

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-49756  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: InvocationTargetException when connecting to Bitbucket server with an empty repo   
 

  
 
 
 
 

 
 Karl Shultz what version of bb server it is? Does it also happen with Bb cloud? Don’t think anything changed in this last of the code though.   
 

  
 
 
 
 

 
 
 

 
 
 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-49763) During time is incorrect in a parallel pipeline step.

[zxj...@126.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 suren pi commented on  JENKINS-49763  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: During time is incorrect in a parallel pipeline step.   
 

  
 
 
 
 

 
 So, you can see durationMillis is negative. Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 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-49763) During time is incorrect in a parallel pipeline step.

[zxj...@126.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 suren pi edited a comment on  JENKINS-49763  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: During time is incorrect in a parallel pipeline step.   
 

  
 
 
 
 

 
 Ok, I will put some log info tomorrow Here is api output text . {code:java}{"_links":{"self":{"href":"/jenkins/job/common/lastBuild/wfapi/describe"}},"id":"201","name":"#201","status":"IN_PROGRESS","startTimeMillis":1519782004606,"endTimeMillis":1519782006142,"durationMillis":1536,"queueDurationMillis":5,"pauseDurationMillis":0,"stages":[{"_links":{"self":{"href":"/jenkins/job/common/lastBuild/execution/node/12/wfapi/describe"}},"id":"12","name":"2","execNode":"","status":"SUCCESS","startTimeMillis":1519782004715,"durationMillis":-13,"pauseDurationMillis":-13},{"_links":{"self":{"href":"/jenkins/job/common/lastBuild/execution/node/10/wfapi/describe"}},"id":"10","name":"1","execNode":"","status":"IN_PROGRESS","startTimeMillis":1519782004702,"durationMillis":1439,"pauseDurationMillis":0}]}{code}RestApi url is : http://localhost:8080/jenkins/job/common/lastBuild/wfapi/describeHere is pipeline script:{code:java}node {parallel 'test': {stage('1') {sleep 60}}, 'deply': {stage('2') {sleep 60}}}{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-49442) Builds hanging on htmlpublisher

[rich...@byh2o.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Bywater assigned an issue to Tomas Bjerre  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49442  
 
 
  Builds hanging on htmlpublisher   
 

  
 
 
 
 

 
Change By: 
 Richard Bywater  
 
 
Component/s: 
 violations-plugin  
 
 
Component/s: 
 htmlpublisher-plugin  
 
 
Assignee: 
 Richard Bywater Tomas Bjerre  
 

  
 
 
 
 

 
 
 

 
 
 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-49442) Builds hanging on htmlpublisher

[rich...@byh2o.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Bywater commented on  JENKINS-49442  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Builds hanging on htmlpublisher   
 

  
 
 
 
 

 
 Taking a look at the thread dump, I'd say its more likely that this is being caused by the Violations plugin as its the only publisher running in the thread dump. I notice that the plugin doesn't appear to be supported anymore and the plugin page https://plugins.jenkins.io/violations seems to suggest using the Warnings plugin instead?  
 

  
 
 
 
 

 
 
 

 
 
 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-49761) SSL Error in Github API connection

[naa...@randomvariable.co.uk (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Naadir Jeewa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49761  
 
 
  SSL Error in Github API connection   
 

  
 
 
 
 

 
Change By: 
 Naadir Jeewa  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

 
 
 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-49761) SSL Error in Github API connection

[naa...@randomvariable.co.uk (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Naadir Jeewa started work on  JENKINS-49761  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Naadir Jeewa  
 
 
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-49761) SSL Error in Github API connection

[naa...@randomvariable.co.uk (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Naadir Jeewa commented on  JENKINS-49761  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSL Error in Github API connection   
 

  
 
 
 
 

 
 This PR should fix this https://github.com/kohsuke/github-api/pull/420  
 

  
 
 
 
 

 
 
 

 
 
 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-32980) Make it easier to use JNLP slaves with self-signed TLS certificates on Jenkins

[aa...@splatteredbits.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aaron Jensen commented on  JENKINS-32980  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make it easier to use JNLP slaves with self-signed TLS certificates on Jenkins   
 

  
 
 
 
 

 
 This doesn't work for me, either. It's unclear from the docs what I'm supposed to pass. The public key? Private key? (I've tried both.) Path to a file?  
 

  
 
 
 
 

 
 
 

 
 
 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-43995) Individual Pipeline steps and stages/blocks should have Result statuses

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43995  
 
 
  Individual Pipeline steps and stages/blocks should have Result statuses   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 

  
 
 
 
 

 
 *Problem* Currently, the only status we have for an individual {{FlowNode}} (be it representing an atomic {{Step}} or a block) is whether it has an {{ErrorAction}}. Blue Ocean would like to be able to visualize other {{Result}} types (such as {{UNSTABLE}} and {{ABORTED}}) distinctly, as well as to be able to have all steps/blocks get marked as {{UNSTABLE}} or {{ABORTED}} if only one step/block actually is unstable or was aborted.  *Approach*We want to have a shared understanding of how the status system should work before we attempt a long refactor of the Pipeline status system. The first goal is to build a throwaway simulator that we can use to describe a Pipeline, the status of its steps and what the resulting stage, parallel and pipeline status should be. This is used to develop a set of scenarios that will be used to define the specification for the refactor. Before moving onto the real changes there must be consensus among the team that this is the desired behaviour.
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

[JIRA] (JENKINS-49781) Please provide a means for securely providing credentials for Kubernetes deployments.

[tonyfl...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tony Flint updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49781  
 
 
  Please provide a means for securely providing credentials for Kubernetes deployments.   
 

  
 
 
 
 

 
Change By: 
 Tony Flint  
 

  
 
 
 
 

 
 I would like a way to provide the kubernetesDeploy method with credentials that are stored in Jenkins' credentials store. Right now, I am using the SSH credentials type, which requires that I manually lay down a kubeconfig file somewhere that contains sensitive information. {{ This is what I'm imagining: }}   { quote}\ { \{  kubernetesDeploy( credentialsType: 'Text', textCredentials: [ serverUrl: '', certificateAuthorityData: '', clientCertificateData: '', clientKeyData: '', ],   }} \  { \ {kubernetesCredentials: [    }}  \ { \ {     clientCertificateCredentialsId: '',   }}  \ { \ {     clientKeyCredentialsId: '',   }}  \ { \ {     serverUrl: '',   }}  \ { \ {     certificateAuthorityData: ''   }}  \ { \ { ]    }} {quote} Am I missing something? Is there a way to achieve this now, that I'm missing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

[JIRA] (JENKINS-49781) Please provide a means for securely providing credentials for Kubernetes deployments.

[tonyfl...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tony Flint updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49781  
 
 
  Please provide a means for securely providing credentials for Kubernetes deployments.   
 

  
 
 
 
 

 
Change By: 
 Tony Flint  
 

  
 
 
 
 

 
 I would like a way to provide the kubernetesDeploy method with credentials that are stored in Jenkins' credentials store. Right now, I am using the SSH credentials type, which requires that I manually lay down a kubeconfig file somewhere that contains sensitive information.{{This is what I'm imagining:}}{{ kubernetesDeploy( credentialsType: 'Text', textCredentials: [ serverUrl: '', certificateAuthorityData: '', clientCertificateData: '', clientKeyData: '', ], }}{{ kubernetesCredentials: [ }}{{    clientCertificateCredentialsId: '', }}{{    clientKeyCredentialsId: '', }}{{    serverUrl: '', }}{{    certificateAuthorityData: '' }}{{]  }}Am I missing something? Is there a way to achieve this now, that I'm missing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are 

[JIRA] (JENKINS-32599) JENKINS_HOME/users/config.xml Results in Nameless User

[db...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck assigned an issue to Daniel Beck  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32599  
 
 
  JENKINS_HOME/users/config.xml Results in Nameless User   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Assignee: 
 Daniel Beck  
 

  
 
 
 
 

 
 
 

 
 
 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-49781) Please provide a means for securely providing credentials for Kubernetes deployments.

[tonyfl...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tony Flint updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49781  
 
 
  Please provide a means for securely providing credentials for Kubernetes deployments.   
 

  
 
 
 
 

 
Change By: 
 Tony Flint  
 

  
 
 
 
 

 
 I would like a way to provide the kubernetesDeploy method with credentials that are stored in Jenkins' credentials store. Right now, I am using the SSH credentials type, which requires that I manually lay down a kubeconfig file somewhere that contains sensitive information.This is what I'm imagining:  { quote}\ { \{  kubernetesDeploy( credentialsType: 'Text', textCredentials: [ serverUrl: '', certificateAuthorityData: '', clientCertificateData: '', clientKeyData: '', ],}} \ { \ {kubernetesCredentials: [ }}  \ { \ {     clientCertificateCredentialsId: '',}}  \ { \ {     clientKeyCredentialsId: '',}}  \ { \ {     serverUrl: '',}}  \ { \ {     certificateAuthorityData: ''}}  \ { \ { ]}} {quote} Am I missing something? Is there a way to achieve this now, that I'm missing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

 

[JIRA] (JENKINS-32599) JENKINS_HOME/users/config.xml Results in Nameless User

[db...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck started work on  JENKINS-32599  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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-32599) JENKINS_HOME/users/config.xml Results in Nameless User

[db...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated  JENKINS-32599  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32599  
 
 
  JENKINS_HOME/users/config.xml Results in Nameless User   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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-49781) Please provide a means for securely providing credentials for Kubernetes deployments.

[tonyfl...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tony Flint updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49781  
 
 
  Please provide a means for securely providing credentials for Kubernetes deployments.   
 

  
 
 
 
 

 
Change By: 
 Tony Flint  
 

  
 
 
 
 

 
 I would like a way to provide the kubernetesDeploy method with credentials that are stored in Jenkins' credentials store. Right now, I am using the SSH credentials type, which requires that I manually lay down a kubeconfig file somewhere that contains sensitive information.This is what I'm imagining: ```  {{ kubernetesDeploy( credentialsType: 'Text', textCredentials: [ serverUrl: '', certificateAuthorityData: '', clientCertificateData: '', clientKeyData: '', ],  }}{{ kubernetesCredentials: [}}{{     clientCertificateCredentialsId: '', }}  {{     clientKeyCredentialsId: '', }}  {{     serverUrl: '', }}  {{     certificateAuthorityData: '' }}  {{ ] }}  ```   Am I missing something? Is there a way to achieve this now, that I'm missing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received 

[JIRA] (JENKINS-49781) Please provide a means for securely providing credentials for Kubernetes deployments.

[tonyfl...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tony Flint created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49781  
 
 
  Please provide a means for securely providing credentials for Kubernetes deployments.   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Menghua Xiao  
 
 
Components: 
 kubernetes-cd-plugin  
 
 
Created: 
 2018-02-27 23:55  
 
 
Environment: 
 Jenkins 2.109 with kubernetes-cd-plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Tony Flint  
 

  
 
 
 
 

 
 I would like a way to provide the kubernetesDeploy method with credentials that are stored in Jenkins' credentials store. Right now, I am using the SSH credentials type, which requires that I manually lay down a kubeconfig file somewhere that contains sensitive information. This is what I'm imagining: ``` kubernetesDeploy( credentialsType: 'Text', textCredentials: [ serverUrl: '', certificateAuthorityData: '', clientCertificateData: '', clientKeyData: '', ], kubernetesCredentials: [      clientCertificateCredentialsId: '',     clientKeyCredentialsId: '',     serverUrl: '',     certificateAuthorityData: '' ] ``` Am I missing something? Is there a way to achieve this now, that I'm missing.  
 

  
 
 
 
 

 
 
 

 
 
 

[JIRA] (JENKINS-47464) Prettier autoformating

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47464  
 
 
  Prettier autoformating   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Issue Type: 
 Improvement Task  
 

  
 
 
 
 

 
 
 

 
 
 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-47985) EC2 Plugin doesn't store AMITypeData in config.xml

[thai...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Thai Pham commented on  JENKINS-47985  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 Plugin doesn't store AMITypeData in config.xml   
 

  
 
 
 
 

 
 When will this fix be released?  
 

  
 
 
 
 

 
 
 

 
 
 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-49754) Streams other than StdOut getting returned when using returnStdOut on PowerShell Step

[ja...@kauppi.la (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jared Kauppila commented on  JENKINS-49754  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Streams other than StdOut getting returned when using returnStdOut on PowerShell Step   
 

  
 
 
 
 

 
 This seems to get the job done unless I'm missing something: 

 

// script.ps1
$VerbosePreference = "Continue"

Write-Host "This is written to host"
Write-Output "This is written to Success output"
Write-Error "This is an error"
Write-Warning "This is a warning message"
Write-Verbose "This is verbose output"
Write-Debug "This is a debug message"
 

 With the following on the wrapper: 

 

$allOtherStreams = $($stdOut = & C:\temp\script.ps1) 2>&1 3>&1 4>&1 5>&1 6>&1

Write-Output "Standard Out:" $stdOut
Write-Output "All other streams:" $allOtherStreams
 

 Returns the following output: 

 

Standard Out:
This is written to Success output
All other streams:
This is written to host
C:\temp\script.ps1 : This is an error
At line:1 char:32
+ $allOtherStreams = $($stdOut = & C:\temp\script.ps1) 2>&1 3>&1 4>&1 5 ...
+
+ CategoryInfo  : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,script.ps1
 
WARNING: This is a warning message
VERBOSE: This is verbose output
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This 

[JIRA] (JENKINS-42201) Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.

[db...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 It's not really clear what this is about.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42201  
 
 
  Next-Build-Number-Plugin: Running set-next-build-number command does not respect authorize-project and project security settings.   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
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 

[JIRA] (JENKINS-49754) Streams other than StdOut getting returned when using returnStdOut on PowerShell Step

[gab...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Loewen commented on  JENKINS-49754  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Streams other than StdOut getting returned when using returnStdOut on PowerShell Step   
 

  
 
 
 
 

 
 There are a couple things that can be done.  
 
I can revert the change that wraps user scripts, but this will introduce a bug that strips out all stream designations from the output.  If you look at the non-pipeline PowerShell build step you'll see that they also create a wrapper script, and the behavior is the same.  The only difference is that there is obviously no returnStdout option, which is why the issue is now getting exposed in pipeline. 
I can intercept output right before it is written to the output file (which is what is read when you use returnStdout) to check for stream designations, and if the pattern match succeeds then just I can easily pass the input through to the console log file. That check can be as easy as a simple regex: 

 

$keywordMatch = $Input -match "^(VERBOSE|WARNING|DEBUG):(.*)$" 

 But, this would cause a side effect of misinterpreting regular console output as special streams. For instance: 

 

Write-Host "VERBOSE: This is actually not a verbose stream"
 

 Normally this would be sent to stdout, but now it would incorrectly be treated as a special stream. 
 Both of these introduce a side effect. Sam Van Oort, Andrew Bayer, James Nord, do any of you have a preference for this issue? Thanks, Gabriel     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 

[JIRA] (JENKINS-49754) Streams other than StdOut getting returned when using returnStdOut on PowerShell Step

[gab...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Loewen edited a comment on  JENKINS-49754  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Streams other than StdOut getting returned when using returnStdOut on PowerShell Step   
 

  
 
 
 
 

 
 There are a couple things that can be done.  # I can revert the change that wraps user scripts, but this will introduce a bug that strips out all stream designations from the output.  If you look at the non-pipeline PowerShell build step you'll see that they also create a wrapper script, and the behavior is the same.  The only difference is that there is obviously no returnStdout option, which is why the issue is now getting exposed in pipeline. # I can intercept output right before it is written to the output file (which is what is read when you use returnStdout) to check for stream designations, and if the pattern match succeeds then  just  I can easily pass the input through to the console log file. That check can be as easy as a simple regex:{code:java}$keywordMatch = $Input -match "^(VERBOSE|WARNING|DEBUG):(.*)$"{code}But, this would cause a side effect of misinterpreting regular console output as special streams. For instance:{code:java}Write-Host "VERBOSE: This is actually not a verbose stream"{code}Normally this would be sent to stdout, but now it would incorrectly be treated as a special stream.{color:#33}Both of these introduce a side effect.{color}[~svanoort], [~abayer], [~teilo], do any of you have a preference for this issue?Thanks,Gabriel    
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-49745) Too many CrumbFilter log entries per second

[db...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-49745  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Too many CrumbFilter log entries per second   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/dashboard-view-plugin/blob/392aaa7c4631a459ce7af801a66ee0fdd09cab08/src/main/resources/hudson/plugins/view/dashboard/stats/StatSlaves/statslaves.jelly#L32...L47 seems to be overly simplistic.  
 

  
 
 
 
 

 
 
 

 
 
 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-49745) Too many CrumbFilter log entries per second

[db...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-49745  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Too many CrumbFilter log entries per second   
 

  
 
 
 
 

 
 I consider this to be a bug in Dashboard View Plugin that seems to provide these URLs and doesn't seem to handle 403 well (https://github.com/jenkinsci/dashboard-view-plugin/blob/392aaa7c4631a459ce7af801a66ee0fdd09cab08/src/main/java/hudson/plugins/view/dashboard/stats/StatSlaves.java).  
 

  
 
 
 
 

 
 
 

 
 
 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-49745) Too many CrumbFilter log entries per second

[db...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49745  
 
 
  Too many CrumbFilter log entries per second   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Component/s: 
 dashboard-view-plugin  
 
 
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-49761) SSL Error in Github API connection

[jcrotty_alp...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Crotty commented on  JENKINS-49761  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSL Error in Github API connection   
 

  
 
 
 
 

 
 Exact same issue has been happing since Feb. 22, 2018 on our Jenkins install for all Github Pull Requests. We tried the solution here but no luck. This has our test builds totally dead in the water.  
 

  
 
 
 
 

 
 
 

 
 
 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-49752) Hudson returned status code -1

[klim...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas commented on  JENKINS-49752  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Hudson returned status code -1   
 

  
 
 
 
 

 
 Hi, I installed Jenkins on my windows (windows 7) and created very simple job. Details on screenshots.  Jenkins is installed as windows services. If you will create job which no have build parameter, only have SCM definition it work fine? Which plugin version you have: git-parameter and git-client? You are sure that your configuration is correct: git setup, permissions, services permissions etc. please look on this site https://plugins.jenkins.io/git and section Jenkins, GIT plugin and Windows Regards Bogusław   

 

Started by user Admin
Building in workspace C:\Program Files (x86)\Jenkins\workspace\test
 > git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git.exe config remote.origin.url https://github.com/jenkinsci/git-parameter-plugin.git # timeout=10
Fetching upstream changes from https://github.com/jenkinsci/git-parameter-plugin.git
 > git.exe --version # timeout=10
using GIT_ASKPASS to set credentials 
 > git.exe fetch --tags --progress https://github.com/jenkinsci/git-parameter-plugin.git +refs/heads/*:refs/remotes/origin/*
 > git.exe rev-parse "refs/remotes/origin/master^{commit}" # timeout=10
 > git.exe rev-parse "refs/remotes/origin/origin/master^{commit}" # timeout=10
Checking out Revision 65266404f0772bee46b871e62d379625a4b36848 (refs/remotes/origin/master)
 > git.exe config core.sparsecheckout # timeout=10
 > git.exe checkout -f 65266404f0772bee46b871e62d379625a4b36848
Commit message: "Merge pull request #59 from ntwerdochlib/JENKINS-49727-optional-list-size"
First time build. Skipping changelog.
Finished: SUCCESS
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-49620) Anchore report exception

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty assigned an issue to Swathi Gangisetty  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49620  
 
 
  Anchore report exception   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Assignee: 
 Daniel Nurmi Swathi Gangisetty  
 

  
 
 
 
 

 
 
 

 
 
 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

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty updated  JENKINS-49620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Zoltan Medovarszky, the issue is fixed in anchore plugin version 1.0.14. Reports generated by previous plugin versions should be viewable with plugin version 1.0.14. Please give it a try and let us know if you see any errors  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49620  
 
 
  Anchore report exception   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 In Review 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 

[JIRA] (JENKINS-49752) Hudson returned status code -1

[klim...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49752  
 
 
  Hudson returned status code -1   
 

  
 
 
 
 

 
Change By: 
 Boguslaw Klimas  
 
 
Attachment: 
 image-2018-02-27-23-07-43-260.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-49752) Hudson returned status code -1

[klim...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49752  
 
 
  Hudson returned status code -1   
 

  
 
 
 
 

 
Change By: 
 Boguslaw Klimas  
 
 
Attachment: 
 image-2018-02-27-23-06-40-531.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

[swa...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty updated  JENKINS-49620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49620  
 
 
  Anchore report exception   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
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-49774) NPE in Autofavorite plugin

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Vivek Pandey  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49774  
 
 
  NPE in Autofavorite plugin   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 James Dumay Vivek Pandey  
 

  
 
 
 
 

 
 
 

 
 
 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-49774) NPE in Autofavorite plugin

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49774  
 
 
  NPE in Autofavorite plugin   
 

  
 
 
 
 

 
 Vivek Pandey this one looks reasonably serious - perhaps the code needs to be more defensive for null user properties?  
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 Blue Ocean 1.5 - 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-49780) Sidebar-links plugins kills "restrict to" option in GUI build configure

[mtdegu...@geisigner.edu (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael DeGuzis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49780  
 
 
  Sidebar-links plugins kills "restrict to" option in GUI build configure   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2018-02-27-16-48-34-098.png, image-2018-02-27-16-49-20-867.png  
 
 
Components: 
 sidebar-link-plugin  
 
 
Created: 
 2018-02-27 21:50  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael DeGuzis  
 

  
 
 
 
 

 
 Before installing sidebar links, this option is available (our prod instance)  After installing sidebar-links,this option is removed:    It appears sidebar links trounces that option.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

[JIRA] (JENKINS-49754) Streams other than StdOut getting returned when using returnStdOut on PowerShell Step

[ja...@kauppi.la (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jared Kauppila edited a comment on  JENKINS-49754  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Streams other than StdOut getting returned when using returnStdOut on PowerShell Step   
 

  
 
 
 
 

 
 [~gabloe] It is, yeah. When the Powershell step was initially introduced, we were able to write out those additional verbose/debug streams to the console output which gave visibility into the execution of the scripts while only capturing stdout which could actually be utilized elsewhere (we were writing out JSON which we then parsed from the stdout returned).   Where it stands now, we'd have to decide on either having visibility into the execution by actually writing out those additional streams to the console or on utilizing the output of the script.  
 

  
 
 
 
 

 
 
 

 
 
 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-49754) Streams other than StdOut getting returned when using returnStdOut on PowerShell Step

[ja...@kauppi.la (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jared Kauppila commented on  JENKINS-49754  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Streams other than StdOut getting returned when using returnStdOut on PowerShell Step   
 

  
 
 
 
 

 
 Gabriel Loewen It is, yeah. When the Powershell step was initially introduced, we were able to write out those additional verbose/debug streams to the console output which gave visibility into the execution of the scripts while only capturing stdout which could actually be utilized elsewhere (we were writing out JSON which we then parsed from the stdout returned).   
 

  
 
 
 
 

 
 
 

 
 
 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-49747) java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)

[t...@unchi.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Pierce commented on  JENKINS-49747  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.FileNotFoundException: /tmp/saml-jenkins-keystore-5345145658381646927.jks (No such file or directory)   
 

  
 
 
 
 

 
 Possibly related to JENKINS-49532?  
 

  
 
 
 
 

 
 
 

 
 
 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-48352) Buttons disabled on "Create first admin user" screen

[bpelt...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bruce Peltzer commented on  JENKINS-48352  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Buttons disabled on "Create first admin user" screen   
 

  
 
 
 
 

 
 I chose a very basic install, going only with the recommended plugins. I wasn't using any proxy. Everything seemed to progress pretty quickly, until I tried to create the first user. Then it just hung. There wasn't anything particularly odd about the install up to that point. Incidentally, after using the admin account and creating a new account manually from within Jenkins, everything has been working fine.  
 

  
 
 
 
 

 
 
 

 
 
 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-49754) Streams other than StdOut getting returned when using returnStdOut on PowerShell Step

[gab...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Loewen commented on  JENKINS-49754  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Streams other than StdOut getting returned when using returnStdOut on PowerShell Step   
 

  
 
 
 
 

 
 Jared Kauppila I think this is a side effect caused by the bugfixes that just came in 1.18.  What is happening is that when PowerShell scripts are executed and the output is piped to the log files used by Jenkins for console and error output the stream designations are lost.  What I mean is that if you run the following script: 

 

// script.ps1
$VerbosePreference = "Continue"
Write-Output "Hello"
Write-Verbose "World"
 

 ps> & script.ps1 *> result.txt You'll see the following output: 

 
Hello
World
 

 Whereas what you'd expect to see is: 

 
Hello
VERBOSE: World 

 The fix for this was to wrap up the execution of this in another script. 

 

// wrapper.ps1
& script.ps1
 

 ps> & wrapper.ps1 *> result.txt Which produces the result as you would expect, including the stream designation.  The side effect of this is that essentially all streams get merged into stdout except for the stderr, which of course is separate. Is this issue a major blocker for you? Thanks, Gabriel    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 

[JIRA] (JENKINS-41856) Cannot initialize beans with named parameters and the default constructor

[laur...@tourreau.fr (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Laurent TOURREAU closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41856  
 
 
  Cannot initialize beans with named parameters and the default constructor   
 

  
 
 
 
 

 
Change By: 
 Laurent TOURREAU  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 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-49622) Support Stride

[tyler.v...@wnco.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tyler Veal commented on  JENKINS-49622  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support Stride   
 

  
 
 
 
 

 
 For reference, there is a "Suggestion" entry for Stride here: https://jira.atlassian.com/browse/STRIDE-1973  
 

  
 
 
 
 

 
 
 

 
 
 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-27306) unclassified new org.codehaus.groovy.runtime.GStringImpl java.lang.String java.lang.String[]

[witokondo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Javier Delgado commented on  JENKINS-27306  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: unclassified new org.codehaus.groovy.runtime.GStringImpl java.lang.String java.lang.String[]   
 

  
 
 
 
 

 
 The fact of using a lazy evaluation (at the initial use case) was due first variable not being initialized on its definition, but at a later stage.  My hacky fix, it someone needs it, was to reimplemtent the GStringImpl.toString method (creating a string from the GString strings and values) and providing that reimplementation on a NonCPS method  
 

  
 
 
 
 

 
 
 

 
 
 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-49742) Multi-line string seems to be broken when triggered from the pipeline.

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-49742  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multi-line string seems to be broken when triggered from the pipeline.   
 

  
 
 
 
 

 
 maybe a regression  Oleksandr Kushchak is it a new issue or have you seen it before?  
 

  
 
 
 
 

 
 
 

 
 
 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-49742) Multi-line string seems to be broken when triggered from the pipeline.

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49742  
 
 
  Multi-line string seems to be broken when triggered from the pipeline.   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 ui ux  
 

  
 
 
 
 

 
 
 

 
 
 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-47181) Rework Remoting Protocol roundtrip tests

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 It has been fixed few month ago  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47181  
 
 
  Rework Remoting Protocol roundtrip tests   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In Progress 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-48352) Buttons disabled on "Create first admin user" screen

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-48352  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Buttons disabled on "Create first admin user" screen   
 

  
 
 
 
 

 
 Also sounds similar to JENKINS-47306 Keith Zantow, maybe you could take repro steps from 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.