[JIRA] (JENKINS-29893) Allow exclusions for git clean

2019-10-30 Thread eub.kansa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josiah Eubank commented on  JENKINS-29893  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow exclusions for git clean   
 

  
 
 
 
 

 
 +1 for the script/pipeline maintenance of modifying everywhere that uses 'checkout scm'  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164471.1439300117000.5410.1572448980358%40Atlassian.JIRA.


[JIRA] (JENKINS-57157) Global Tools fail to update automatic installs

2019-04-23 Thread eub.kansa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josiah Eubank created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57157  
 
 
  Global Tools fail to update automatic installs   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Sonar Team  
 
 
Components: 
 sonar, workflow-basic-steps-plugin  
 
 
Created: 
 2019-04-23 14:55  
 
 
Environment: 
 Jenkins 2.173, Pipeline Basic Steps 2.15, Sonarqube Scanner for Jenkins 2.8.1  
 
 
Labels: 
 tools sonarqube update pipeline automatic-install  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Josiah Eubank  
 

  
 
 
 
 

 
 When a tool is upgraded versions or the automatic installer is changed, Jenkins does not update the tool installed on the build agent.  For example, the Sonarqube plugin installs its scanner as a Global Tool with an automatic installer from maven (populated dropdown).  If you change versions, the new version does not overwrite the previous version on the build agent. Current workaround is to manually delete the tools directory from every build agent when upgrading any tools. Expected behavior: either install the tool to a version specific directory based on the source (zip file name, maven version, etc) or overwrite the generic directory with whichever version is specified in Global Tool Configuration (either upgrade or downgrade)  
 

  
 
 
 
 

 
   

[JIRA] (JENKINS-55789) Document expected bug 23212 - idle timeout overrides boot

2019-01-25 Thread eub.kansa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josiah Eubank created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55789  
 
 
  Document expected bug 23212 - idle timeout overrides boot
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 vsphere-cloud-plugin  
 
 
Created: 
 2019-01-26 00:40  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Josiah Eubank  
 

  
 
 
 
 

 
 This 2014 comment is still applicable "Was able to reproduce the described behavior using JNLP connection with a long post-boot delay and a short idle time to disconnect. The two features are colliding. Solutions: decrease post-boot delay to bare minimum needed, use non-JNLP slave agent connection, or increase the idle time to disconnect."   However, I cannot find this documented anywhere and it should be on the plugin page – or fixed.  Idle timeout should not start counting down until after the connect is complete.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
   

[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13

2018-11-19 Thread eub.kansa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josiah Eubank commented on  JENKINS-54331  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13   
 

  
 
 
 
 

 
 Fixed in 2.2.14 https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/150  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54401) NPE when parsing scm git revision date on PR branches

2018-11-19 Thread eub.kansa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josiah Eubank commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NPE when parsing scm git revision date on PR branches   
 

  
 
 
 
 

 
 Not yet listed on update site: http://updates.jenkins-ci.org/current/update-center.json  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-54401) NPE when parsing scm git revision date on PR branches

2018-11-13 Thread eub.kansa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josiah Eubank commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NPE when parsing scm git revision date on PR branches   
 

  
 
 
 
 

 
 Is there an update on releasing this fix?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines

2018-10-30 Thread eub.kansa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josiah Eubank commented on  JENKINS-34256  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Preparing Jenkins For Shutdown Hangs Running Pipelines   
 

  
 
 
 
 

 
 Also experiencing this new since around 2.140 in all pipeline jobs.  These jobs are on lowest durability setting.   Previously had no issue holding the queue by "preparing for shutdown" and the currently running jobs would finish.  Now have to force Jenkins to restart to get rid of the jobs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-791) slave log should include timestamp

2018-08-30 Thread eub.kansa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josiah Eubank commented on  JENKINS-791  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: slave log should include timestamp   
 

  
 
 
 
 

 
 Has this regressed or purposely removed?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-25845) Node startup log should contain a timestamp

2018-08-30 Thread eub.kansa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josiah Eubank commented on  JENKINS-25845  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Node startup log should contain a timestamp   
 

  
 
 
 
 

 
 Is this specific to a plugin or for all Nodes? Using vsphere plugin to reboot/revert nodes and the node logs do not have timestamps.  Attempting to determine if this ticket has regressed or it does not apply to the current lack of timestamps.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-28907) option to treat merge commiters as regular commiters

2018-04-24 Thread eub.kansa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josiah Eubank commented on  JENKINS-28907  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: option to treat merge commiters as regular commiters   
 

  
 
 
 
 

 
 The line in question is now https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L972  
 

  
 
 
 
 

 
 
 

 
 
 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.