date:20200410

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vy Donhu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61872  
 
 
  Install Jenkins 2.222.1 on Windows Server 2016 (by Adminstrator user) error   
 

  
 
 
 
 

 
Change By: 
 Vy Donhu  
 

  
 
 
 
 

 
 Install Jenkins on Windows Server 2016 Data Center. Use Apache Tomcat 9.0.35 , JDK 1.8u241, Jenkins WAR files.     I download and used this file [http://mirror.serverion.com/jenkins/war-stable/2.222.1/jenkins.war]     . The error I seen in Apache Tomcat console, mainly cause by error delete file permission. I changed file permission to Allow all (edit, delete, ect.) by Administrator user.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61872) Install Jenkins 2.222.1 on Windows Server 2016 (by Adminstrator user) error

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vy Donhu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61872  
 
 
  Install Jenkins 2.222.1 on Windows Server 2016 (by Adminstrator user) error   
 

  
 
 
 
 

 
Change By: 
 Vy Donhu  
 

  
 
 
 
 

 
 Install Jenkins on Windows Server 2016 Data Center. Use Apache Tomcat 9.0.35 , JDK 1.8u241, Jenkins WAR files. I download and used this file [http://mirror.serverion.com/jenkins/war-stable/2.222.1/jenkins.war] The error I seen in Apache Tomcat console, mainly cause by error delete file permission.  I changed file permission to Allow all (edit, delete, ect.) by Administrator user.     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205737.1586571182000.9321.1586571420063%40Atlassian.JIRA.

[JIRA] (JENKINS-61872) Install Jenkins 2.222.1 on Windows Server 2016 (by Adminstrator user) error

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vy Donhu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61872  
 
 
  Install Jenkins 2.222.1 on Windows Server 2016 (by Adminstrator user) error   
 

  
 
 
 
 

 
Change By: 
 Vy Donhu  
 

  
 
 
 
 

 
 Install Jenkins on Windows Server 2016 Data Center. Use Apache Tomcat 9.0.35 , JDK 1.8u241, Jenkins WAR files.  I download and used this file [http://mirror.serverion.com/jenkins/war-stable/2.222.1/jenkins.war]   The error I seen in Apache Tomcat console, mainly cause by error delete file permission.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205737.1586571182000.9320.1586571360064%40Atlassian.JIRA.

[JIRA] (JENKINS-61872) Install Jenkins 2.222.1 on Windows Server 2016 (by Adminstrator user) error

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vy Donhu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61872  
 
 
  Install Jenkins 2.222.1 on Windows Server 2016 (by Adminstrator user) error   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 error_windows_server.png, fail.png, jenkins.log.txt  
 
 
Components: 
 deploy-plugin  
 
 
Created: 
 2020-04-11 02:13  
 
 
Environment: 
 Windows Server 2016 Data center, JDK 1.8u241  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Vy Donhu  
 

  
 
 
 
 

 
 Install Jenkins on Windows Server 2016 Data Center. Use Apache Tomcat 9.0.35 , JDK 1.8u241, Jenkins WAR files.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-53261) Blue ocean should handle non-encoded URLs for jobs in folders

2020-04-10 Thread euclid...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Euclid Sun edited a comment on  JENKINS-53261  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue ocean should handle non-encoded URLs for jobs in folders   
 

  
 
 
 
 

 
 A workaround is to create links that are appended with a / forcing the browser to not encode anything in the URL and read it as-is with no replacements. If we could have urls from the plugin show up automatically appended with / this would solve a large amount of issues so long as no one tries to post a link from the dashboard without the /However it is still a workaround  from just being able to read a fix would be reading  the folder names and reserving blue/organizations/jenkinsdetail\d+/pipelineas reserve words so that the labels for folders can be read in correctly regardless if they are replaced  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.193336.1535399409000.9315.1586569740343%40Atlassian.JIRA.

[JIRA] (JENKINS-53261) Blue ocean should handle non-encoded URLs for jobs in folders

2020-04-10 Thread euclid...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Euclid Sun edited a comment on  JENKINS-53261  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue ocean should handle non-encoded URLs for jobs in folders   
 

  
 
 
 
 

 
 A  way around  workaround  is to create links that are appended with a / forcing the browser to not encode anything in the URL and read it as-is with no replacements. If we could have urls from the plugin show up automatically appended with / this would solve a large amount of issues so long as no one tries to post a link from the dashboard without the /However it is still a workaround from just being able to read the folder names and reserving blue/organizations/jenkinsdetail\d+/pipelineas reserve words so that the labels for folders can be read in correctly regardless if they are replaced  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.193336.1535399409000.9313.1586569740316%40Atlassian.JIRA.

[JIRA] (JENKINS-53261) Blue ocean should handle non-encoded URLs for jobs in folders

2020-04-10 Thread euclid...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Euclid Sun commented on  JENKINS-53261  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue ocean should handle non-encoded URLs for jobs in folders   
 

  
 
 
 
 

 
 A way around is to create links that are appended with a / forcing the browser to not encode anything in the URL and read it as-is with no replacements. If we could have urls from the plugin show up automatically appended with / this would solve a large amount of issues so long as no one tries to post a link from the dashboard without the / However it is still a workaround from just being able to read the folder names and reserving  blue/organizations/jenkins detail \d+/pipeline as reserve words so that the labels for folders can be read in correctly regardless if they are replaced  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.193336.1535399409000.9305.1586569680190%40Atlassian.JIRA.

[JIRA] (JENKINS-36089) Pipeline support for Promoted Builds Plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36089  
 
 
  Pipeline support for Promoted Builds Plugin   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 gsoc-2019-project-idea gsoc2019-artifact-promotion-in-pipeline pipeline  roadmap  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.172050.1466438354000.9152.1586556484343%40Atlassian.JIRA.

[JIRA] (JENKINS-61184) Jira Trigger Plugin Issue

2020-04-10 Thread rlinu...@networkconfig.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Usama Tariq commented on  JENKINS-61184  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jira Trigger Plugin Issue   
 

  
 
 
 
 

 
 Wisen Tanasa or @Jenkins Support, Please let me know the procedure ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.204728.1582314984000.9150.1586554680191%40Atlassian.JIRA.

[JIRA] (JENKINS-61184) Jira Trigger Plugin Issue

2020-04-10 Thread rlinu...@networkconfig.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Usama Tariq assigned an issue to Usama Tariq  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61184  
 
 
  Jira Trigger Plugin Issue   
 

  
 
 
 
 

 
Change By: 
 Usama Tariq  
 
 
Assignee: 
 Usama Tariq  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.204728.1582314984000.9146.1586554560206%40Atlassian.JIRA.

[JIRA] (JENKINS-56699) Provide formatter for messages that contain newlines

2020-04-10 Thread benjamin.c.cr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Benjamin Cross commented on  JENKINS-56699  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Provide formatter for messages that contain newlines   
 

  
 
 
 
 

 
 Ulli Hafner I made a PR [#438|https://github.com/jenkinsci/warnings-ng-plugin/pull/438] with what I think you are looking for. Let me know if you have any suggestions or changes.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.198337.1553335794000.9140.1586552220336%40Atlassian.JIRA.

[JIRA] (JENKINS-56699) Provide formatter for messages that contain newlines

2020-04-10 Thread benjamin.c.cr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Benjamin Cross edited a comment on  JENKINS-56699  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Provide formatter for messages that contain newlines   
 

  
 
 
 
 

 
 [~drulli] I made a PR [ # 438|[https://github.com/jenkinsci/warnings-ng-plugin/pull/438]] with what I think you are looking for. Let me know if you have any suggestions or changes.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.198337.1553335794000.9142.1586552220386%40Atlassian.JIRA.

[JIRA] (JENKINS-42816) Slave to Agent renaming leftovers

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42816  
 
 
  Slave to Agent renaming leftovers   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 Just "slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation. We need  to  keep  clean it up. This EPIC keeps  a track of missing  renamings  renaming  when  I  we  occasionally notice them .Renaming scope includes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * 3rd-party blogposts * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Any other code: local variables, class fields, etc. * etc.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-42816) Slave to Agent renaming leftovers

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42816  
 
 
  Slave to Agent renaming leftovers   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 fosdem2019 hacktoberfest jenkins2.0  newbie-friendly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.179816.148960121.9122.1586552040760%40Atlassian.JIRA.

[JIRA] (JENKINS-42816) Slave to Agent renaming leftovers

2020-04-10 Thread shubham.aggar...@devfactory.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42816  
 
 
  Slave to Agent renaming leftovers   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 fosdem2019 hacktoberfest  help-wanted  jenkins2.0 newbie-friendly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.179816.148960121.9128.1586552040853%40Atlassian.JIRA.

[JIRA] (JENKINS-61799) New Windows Installer redirects to browser after uninstalling Jenkins

2020-04-10 Thread slide.o....@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-61799  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New Windows Installer redirects to browser after uninstalling Jenkins   
 

  
 
 
 
 

 
 See https://github.com/jenkinsci/packaging/pull/158  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205643.1585913087000.9114.1586550240139%40Atlassian.JIRA.

[JIRA] (JENKINS-51352) Windows slave not getting connected

Title: Message Title


 
 
 
 

 
 
 

 
   
 Shubham Aggarwal commented on  JENKINS-51352  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows slave not getting connected   
 

  
 
 
 
 

 
 Looks like it still isn't released. After a lot of trial-and-error, I ended up here and this workaround worked for me.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.190698.1526438065000.9108.1586548140209%40Atlassian.JIRA.

[JIRA] (JENKINS-40456) First time builds are not reporting to Bitbucket

2020-04-10 Thread joseph.solomo...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Solomon commented on  JENKINS-40456  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: First time builds are not reporting to Bitbucket   
 

  
 
 
 
 

 
 Why do we need to fetch previous build scm values here https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/blob/df373d0ae3ac32a5337c1c002505dee0c85ff5b0/src/main/java/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusHelper.java#L142? Couldn't we replace this line with  

 

Map scm_map = new LinkedHashMap<>();
for (WorkflowRun.SCMCheckout co : build.checkouts(null)) {
scm_map.put(co.scm.getKey(), co.scm);
}
Collectionextends SCM> scms = scm_map.values()
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.177126.1481749849000.9091.1586546280555%40Atlassian.JIRA.

[JIRA] (JENKINS-61799) New Windows Installer redirects to browser after uninstalling Jenkins

2020-04-10 Thread sladynnune...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sladyn Nunes commented on  JENKINS-61799  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New Windows Installer redirects to browser after uninstalling Jenkins   
 

  
 
 
 
 

 
 No issues  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205643.1585913087000.9088.1586544420156%40Atlassian.JIRA.

[JIRA] (JENKINS-61871) Prune stale tags does not prune stale tags in my docker test

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco updated  JENKINS-61871  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61871  
 
 
  Prune stale tags does not prune stale tags in my docker test   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205736.1586541813000.9083.1586544360312%40Atlassian.JIRA.

[JIRA] (JENKINS-61869) Prune tags during fetch shown incorrectly in pipeline syntax generator

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco updated  JENKINS-61869  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61869  
 
 
  Prune tags during fetch shown incorrectly in pipeline syntax generator   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205734.1586535653000.9085.1586544360340%40Atlassian.JIRA.

[JIRA] (JENKINS-61870) Git plugin UI transition for shallow clone needs more changes

2020-04-10 Thread timjaco...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Jacomb commented on  JENKINS-61870  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin UI transition for shallow clone needs more changes   
 

  
 
 
 
 

 
 Yes I’ll sort it  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205735.1586539743000.9081.1586544300314%40Atlassian.JIRA.

[JIRA] (JENKINS-61870) Git plugin UI transition for shallow clone needs more changes

2020-04-10 Thread timjaco...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Jacomb assigned an issue to Tim Jacomb  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61870  
 
 
  Git plugin UI transition for shallow clone needs more changes   
 

  
 
 
 
 

 
Change By: 
 Tim Jacomb  
 
 
Assignee: 
 Tim Jacomb  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205735.1586539743000.9079.1586544300286%40Atlassian.JIRA.

[JIRA] (JENKINS-61675) Neuxs platform plugin fail to connect nexus3

2020-04-10 Thread jyo...@sonatype.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Justin Young commented on  JENKINS-61675  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Neuxs platform plugin fail to connect nexus3   
 

  
 
 
 
 

 
 Hi Hokwang Lee, If you are a Nexus Repository Pro customer please open a ticket on https://support.sonatype.com/hc/en-us.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205411.158511410.9077.1586543700191%40Atlassian.JIRA.

[JIRA] (JENKINS-61871) Prune stale tags does not prune stale tags in my docker test

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco started work on  JENKINS-61871  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205736.1586541813000.9074.1586542980188%40Atlassian.JIRA.

[JIRA] (JENKINS-61871) Prune stale tags does not prune stale tags in my docker test

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61871  
 
 
  Prune stale tags does not prune stale tags in my docker test   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 I have a [JENKINS-40529 branch|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-40529] in my [jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/] that contains a [script|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-40529/remove-all-stale-tags-and-push-one] that creates a new commit, tags the new commit with a unique tag name, and then deletes all other tag names locally and remotely which might have preceded that tag name.That sequence of steps causes the remote repository to typically have only one tag for content on this branch.  The preceding tags placed on that branch are deleted.When I run a Freestyle project, I see that the tags accumulate in the workspace of the freestyle project as the job detects new changes and runs.  That is the expected behavior without the "prune stale tags" extension.When I add the "prune stale tags" extension on that job, I was expecting the tags to be removed from the workspace each time new changes are fetched into the repository.  Unfortunately, with my [docker image|https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins] (using CLI git 2.17) and with several of my agents (one using CLI git 2.26), the stale tags are not removed from the workspace when new changes are fetched into the workspace.  Refer to the [config.xml file of my freestyle job|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-40529-prune-stale-tags/config.xml] for details. That branch of the jenkins-bugs repository also includes a Jenkinsfile which is showing the same behavior.  I'm using [git plugin 4.3.0 pre-release|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/plugins/git.jpi] and [git client plugin 3.3.0 pre-release|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/plugins/git-client.jpi].  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-61871) Prune stale tags does not prune stale tags in my docker test

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Nikolas Falco  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61871  
 
 
  Prune stale tags does not prune stale tags in my docker test   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite Nikolas Falco  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205736.1586541813000.9070.1586541840417%40Atlassian.JIRA.

[JIRA] (JENKINS-61871) Prune stale tags does not prune stale tags in my docker test

Title: Message Title

Mark Waite created an issue

Jenkins / JENKINS-61871

Prune stale tags does not prune stale tags in my docker test

Issue Type:
Bug

Assignee:
Mark Waite

Components:
git-plugin

Created:
2020-04-10 18:03

Environment:
The lts-with-plugins branch of my docker-lfs repository

Priority:
Minor

Reporter:
Mark Waite

I have a JENKINS-40529 branch in my jenkins-bugs repository that contains a script that creates a new commit, tags the new commit with a unique tag name, and then deletes all other tag names locally and remotely which might have preceded that tag name. That sequence of steps causes the remote repository to typically have only one tag for content on this branch. The preceding tags placed on that branch are deleted. When I run a Freestyle project, I see that the tags accumulate in the workspace of the freestyle project as the job detects new changes and runs. That is the expected behavior without the "prune stale tags" extension. When I add the "prune stale tags" extension on that job, I was expecting the tags to be removed from the workspace each time new changes are fetched into the repository. Unfortunately, with my docker image (using CLI git 2.17) and with several of my agents (one using CLI git 2.26), the stale tags are not removed from the workspace when new changes are fetched into the workspace. Refer to the config.xml file of my freestyle job for details.

[JIRA] (JENKINS-61799) New Windows Installer redirects to browser after uninstalling Jenkins

2020-04-10 Thread slide.o....@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-61799  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New Windows Installer redirects to browser after uninstalling Jenkins   
 

  
 
 
 
 

 
 Sladyn Nunes I appreciate you wanting to jump in on this, but I think it might be best to wait until it is in a released state. It's still in development.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205643.1585913087000.9066.1586541360291%40Atlassian.JIRA.

[JIRA] (JENKINS-61799) New Windows Installer redirects to browser after uninstalling Jenkins

2020-04-10 Thread slide.o....@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl assigned an issue to Alex Earl  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61799  
 
 
  New Windows Installer redirects to browser after uninstalling Jenkins   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Assignee: 
 Alex Earl  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205643.1585913087000.9064.1586541360268%40Atlassian.JIRA.

[JIRA] (JENKINS-61869) Prune tags during fetch shown incorrectly in pipeline syntax generator

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-61869  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prune tags during fetch shown incorrectly in pipeline syntax generator   
 

  
 
 
 
 

 
 Thanks for investigating Nikolas Falco!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205734.1586535653000.9061.1586540640167%40Atlassian.JIRA.

[JIRA] (JENKINS-61869) Prune tags during fetch shown incorrectly in pipeline syntax generator

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco commented on  JENKINS-61869  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prune tags during fetch shown incorrectly in pipeline syntax generator   
 

  
 
 
 
 

 
 A getter method is missing to make the pipeline sysntax works correctly.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205734.1586535653000.9059.1586540460182%40Atlassian.JIRA.

[JIRA] (JENKINS-61869) Prune tags during fetch shown incorrectly in pipeline syntax generator

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco started work on  JENKINS-61869  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205734.1586535653000.9057.1586540220194%40Atlassian.JIRA.

[JIRA] (JENKINS-61870) Git plugin UI transition for shallow clone needs more changes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61870  
 
 
  Git plugin UI transition for shallow clone needs more changes   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205735.1586539743000.9055.1586539980062%40Atlassian.JIRA.

[JIRA] (JENKINS-61870) Git plugin UI transition for shallow clone needs more changes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-61870  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin UI transition for shallow clone needs more changes   
 

  
 
 
 
 

 
 Josh Soref or Tim Jacomb are either of you available to investigate this one?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205735.1586539743000.9054.1586539860055%40Atlassian.JIRA.

[JIRA] (JENKINS-61870) Git plugin UI transition for shallow clone needs more changes

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61870  
 
 
  Git plugin UI transition for shallow clone needs more changes   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Attachments: 
 clone-behaviors-before.png, clone-behaviors-latest.png, freestyle-not-selected.png, freestyle-selected.png  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2020-04-10 17:29  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Mark Waite  
 

  
 
 
 
 

 
 Josh Soref and Tim Jacomb provided a pull request to make the git plugin better fit with upcoming user interface changes. Unfortunately, the shallow clone depth setting is much less clear than it was before. Previously, the shallow clone depth setting was included in the clone options as:With the changes that are merged for inclusion in git plugin 4.3.0, it looks like this:We need to find a way to label the shallow clone depth field. It should probably look something like this when not selected (example from freestyle job configuration page):and might look something like this when selected:   I'm also open to other recommendations for appearance. I'm especially open to pull requests proposing to improve it.

[JIRA] (JENKINS-61799) New Windows Installer redirects to browser after uninstalling Jenkins

2020-04-10 Thread sladynnune...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sladyn Nunes commented on  JENKINS-61799  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New Windows Installer redirects to browser after uninstalling Jenkins   
 

  
 
 
 
 

 
 Oleg Nenashev I could give this a try and fix it CC Alex Earl Is the code for the installer still in a pull request ?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205643.1585913087000.9052.1586539080168%40Atlassian.JIRA.

[JIRA] (JENKINS-40529) Prune tags on fetch

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco updated  JENKINS-40529  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40529  
 
 
  Prune tags on fetch   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.177211.1482077235000.9044.1586536800613%40Atlassian.JIRA.

[JIRA] (JENKINS-61869) Prune tags during fetch shown incorrectly in pipeline syntax generator

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Nikolas Falco  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61869  
 
 
  Prune tags during fetch shown incorrectly in pipeline syntax generator   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite Nikolas Falco  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205734.1586535653000.9042.1586535720116%40Atlassian.JIRA.

[JIRA] (JENKINS-61869) Prune tags during fetch shown incorrectly in pipeline syntax generator

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61869  
 
 
  Prune tags during fetch shown incorrectly in pipeline syntax generator   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2020-04-10 16:20  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Mark Waite  
 

  
 
 
 
 

 
 JENKINS-40529 added support to optionally prune tags during the fetch operation. Unfortunately, the trait that has been added does not render correctly in the pipeline syntax generator. It is shown as: 

 
checkout([$class: 'GitSCM', branches: [[name: '*/master']], 
extensions: [], 
gitTool: 'Default', 
submoduleCfg: [], 
userRemoteConfigs: [[]]])
 

 Other extensions are correctly rendered like this: 

 
checkout([$class: 'GitSCM', branches: [[name: '*/master']], 
extensions: [[$class: 'PruneStaleBranch']], 
gitTool: 'Default', submoduleCfg: [], 
userRemoteConfigs: [[]]])
 

 Note that the $class: PruneStaleBranch is shown as an extension instead of ''

[JIRA] (JENKINS-61868) BuildMaster plugin - Cannot create first build of release for application

2020-04-10 Thread jstarb...@scisolutions.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon Starbird created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61868  
 
 
  BuildMaster plugin - Cannot create first build of release for application   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Andrew Sumner  
 
 
Components: 
 inedo-buildmaster-plugin  
 
 
Created: 
 2020-04-10 15:49  
 
 
Environment: 
 Jenkins 2.222.1  BuildMaster Plugin 3.1.0  BuildMaster 6.1.26  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jon Starbird  
 

  
 
 
 
 

 
 Started a new Release in BuildMaster for application. Have the BuildMaster Release Parameter field setup for the app. In job, have Create Build step. When ran, select the app, release, then try to run.  hit error -  

 

FATAL: Null value not allowed as an environment variable: BUILDMASTER_LATEST_BUILD_NUMBER
java.lang.IllegalArgumentException: Null value not allowed as an environment variable: BUILDMASTER_LATEST_BUILD_NUMBER
	at hudson.EnvVars.put(EnvVars.java:379)
	at com.inedo.buildmaster.jenkins.BuildMasterReleaseParameterValue.buildEnvironment(BuildMasterReleaseParameterValue.java:71)
	at org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:88)
	at org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:153)
	at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironmentWithoutJobPropertyObject(EnvInjectListener.java:233)
	at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:49)
	at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:542)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:462)
	at hudson.model.Run.execute(Run.java:1856)
	at

[JIRA] (JENKINS-61863) Nullpointer in http-request-plugin

2020-04-10 Thread janario.olive...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Janario Oliveira updated  JENKINS-61863  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61863  
 
 
  Nullpointer in http-request-plugin   
 

  
 
 
 
 

 
Change By: 
 Janario Oliveira  
 
 
Status: 
 Fixed but Unreleased Resolved  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205727.158651131.9037.1586533320996%40Atlassian.JIRA.

[JIRA] (JENKINS-61863) Nullpointer in http-request-plugin

2020-04-10 Thread janario.olive...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Janario Oliveira updated  JENKINS-61863  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61863  
 
 
  Nullpointer in http-request-plugin   
 

  
 
 
 
 

 
Change By: 
 Janario Oliveira  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Fixed but Unreleased Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205727.158651131.9033.1586533320684%40Atlassian.JIRA.

[JIRA] (JENKINS-61863) Nullpointer in http-request-plugin

2020-04-10 Thread janario.olive...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Janario Oliveira updated  JENKINS-61863  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61863  
 
 
  Nullpointer in http-request-plugin   
 

  
 
 
 
 

 
Change By: 
 Janario Oliveira  
 
 
Status: 
 Reopened Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205727.158651131.9035.1586533320884%40Atlassian.JIRA.

[JIRA] (JENKINS-61863) Nullpointer in http-request-plugin

2020-04-10 Thread janario.olive...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Janario Oliveira updated  JENKINS-61863  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Thanks for the report There were some backward compatibility problems Version 1.8.26 will be available soon, please give it a try https://github.com/jenkinsci/http-request-plugin/commit/72894e2723fe4a20e1691b449a664b77e813e55f  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-61863  
 
 
  Nullpointer in http-request-plugin   
 

  
 
 
 
 

 
Change By: 
 Janario Oliveira  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Basil Crow updated  JENKINS-61843  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in jenkinsci/timestamper-plugin#59.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-61843  
 
 
  Timestamp missing for trailing lines in view as plain text mode.   
 

  
 
 
 
 

 
Change By: 
 Basil Crow  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-61863) Nullpointer in http-request-plugin

2020-04-10 Thread janario.olive...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Janario Oliveira stopped work on  JENKINS-61863  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Janario Oliveira  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205727.158651131.9025.1586532900310%40Atlassian.JIRA.

[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Basil Crow commented on  JENKINS-61843  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Timestamp missing for trailing lines in view as plain text mode.   
 

  
 
 
 
 

 
 No problem. Thank you for reporting the issue and confirming that it has been resolved! I will merge the PR and release 1.11.3 shortly. I had actually linked to the .hpi from the words "this incremental build" in my preceding comment, but missing that is completely understandable since the CSS styling on this page doesn't make hyperlinks very obvious.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205703.1586369761000.9027.1586532900339%40Atlassian.JIRA.

[JIRA] (JENKINS-61863) Nullpointer in http-request-plugin

2020-04-10 Thread janario.olive...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Janario Oliveira started work on  JENKINS-61863  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Janario Oliveira  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205727.158651131.9023.1586532780220%40Atlassian.JIRA.

[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.

Title: Message Title


 
 
 
 

 
 
 

 
   
 John Rocha edited a comment on  JENKINS-61843  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Timestamp missing for trailing lines in view as plain text mode.   
 

  
 
 
 
 

 
 Thank you for your patience and tutelage. I installed the incremental plugin. !installed.png .png ! And I can confirm that I know observe the expected timestamps. Thank you.Also, for my own education. How did you navigate from the #59 plugin link to the HPI link? I suspect that could be useful for me to learn/know for the future.Thanks again!Cheers.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205703.1586369761000.9021.1586532720360%40Atlassian.JIRA.

[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.

Title: Message Title


 
 
 
 

 
 
 

 
   
 John Rocha commented on  JENKINS-61843  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Timestamp missing for trailing lines in view as plain text mode.   
 

  
 
 
 
 

 
 Thank you for your patience and tutelage. I installed the incremental plugin.   And I can confirm that I know observe the expected timestamps. Thank you. Also, for my own education. How did you navigate from the #59 plugin link to the HPI link? I suspect that could be useful for me to learn/know for the future. Thanks again! Cheers.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205703.1586369761000.9019.1586532660097%40Atlassian.JIRA.

[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.

Title: Message Title


 
 
 
 

 
 
 

 
   
 John Rocha updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61843  
 
 
  Timestamp missing for trailing lines in view as plain text mode.   
 

  
 
 
 
 

 
Change By: 
 John Rocha  
 
 
Attachment: 
 installed.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205703.1586369761000.9017.1586532600231%40Atlassian.JIRA.

[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Basil Crow commented on  JENKINS-61843  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Timestamp missing for trailing lines in view as plain text mode.   
 

  
 
 
 
 

 
 Here is the incremental build .hpi: https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/timestamper/1.11.3-SNAPSHOT/timestamper-1.11.3-20200410.050219-1.hpi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205703.1586369761000.9015.1586531880120%40Atlassian.JIRA.

[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.

Title: Message Title


 
 
 
 

 
 
 

 
   
 John Rocha commented on  JENKINS-61843  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Timestamp missing for trailing lines in view as plain text mode.   
 

  
 
 
 
 

 
 Thank you for the instructions on uploading a plugin .hpi file. Next question. How do I get the timestamper .hpi file? You shared a link for jenkinsci/timestamper-plugin#59. What are the steps I do not to download a .hpi file from the link? I don't see any obvious way to do that from the link shared.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205703.1586369761000.9013.1586531580161%40Atlassian.JIRA.

[JIRA] (JENKINS-52310) Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support

2020-04-10 Thread jenk...@gavinmogan.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Mogan commented on  JENKINS-52310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support
 

  
 
 
 
 

 
 I did finish the fixes to make the tests run in java11, everything else seemed like it already worked. I don't remember if the ATH runs though. I think its safe to close.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.192093.1530522315000.9008.1586531040271%40Atlassian.JIRA.

[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Basil Crow commented on  JENKINS-61843  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Timestamp missing for trailing lines in view as plain text mode.   
 

  
 
 
 
 

 
 

How do I install your changes in order to test?
 See these instructions.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205703.1586369761000.9006.1586530080140%40Atlassian.JIRA.

[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.

Title: Message Title


 
 
 
 

 
 
 

 
   
 John Rocha commented on  JENKINS-61843  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Timestamp missing for trailing lines in view as plain text mode.   
 

  
 
 
 
 

 
 Hello Basil Crow, how do i "try the incremental build"? I looked at Jenkins and I don't see an update for the timestamper plugin, so I'm guessing this hasn't been released yet. How do I install your changes in order to test? Thank you.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205703.1586369761000.9004.1586529540215%40Atlassian.JIRA.

[JIRA] (JENKINS-61861) Jenkins Job is Triggering twice for a single Commit

Title: Message Title

Mark Waite commented on JENKINS-61861

Re: Jenkins Job is Triggering twice for a single Commit

No, Anvesh Ramaswamy, I cannot help you with any steps to proceed to resolve the issue. I requested 5 items and you provided far less than 1 of the items I requested. I help Jenkins users on my personal time. When you fail to provide all the information I request, it tells me that you're really not committed to receiving my help. Since you're running a Jenkins version that is many years old and a git plugin that is many years old, you should expect to do significant work of your own before I or anyone else will be willing to assist. The information you provide in the issue report needs to be sufficiently detailed that it persuades me that you are investing enough of your time to justify that I should invest some of my time. You've not shown that. I will not engage in a long series of questions and answers about the issue unless you persuade me that the issue is very interesting to me. If you decide that it is not worth enough of your time to provide that information, then let's agree that we'll close this issue as "cannot reproduce".

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

--
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.205725.1586498472000.9002.1586528220150%40Atlassian.JIRA.

[JIRA] (JENKINS-61867) Calendar Plugin should have options to show/hide polling

2020-04-10 Thread roland.asm...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roland Asmann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61867  
 
 
  Calendar Plugin should have options to show/hide polling   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Sven Schoenung  
 
 
Components: 
 calendar-view-plugin  
 
 
Created: 
 2020-04-10 13:24  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roland Asmann  
 

  
 
 
 
 

 
 I installed this plugin as a Jenkins Admin to get an idea of how much is going on on our Jenkins and am generally pretty happy with the result. However, since not all our users have the possibility/haven't had time to switch to a different way of CI Builds, we have literally hundreds of jobs that are polling every <= 5 minutes, which makes the Calendar-View absolutely unreadable. I would love to see a some options added to configure something like this. Maybe I can then create 2 Views: 1 for actual planned Builds and 1 for all the polling – the latter would be useful to figure out if polling becomes less when my users start transitioning to GIT and Push-Hooks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-28942) Allow plugins to declare that they do not use certain implied dependencies

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-28942  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow plugins to declare that they do not use certain implied dependencies   
 

  
 
 
 
 

 
 Jesse Glick is was in the EPIC for Java 11 support, likely because of the JAXB API plugin. I just moved it out of the epic  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.163400.1434531203000.8998.1586523420292%40Atlassian.JIRA.

[JIRA] (JENKINS-51805) Java 11 GA in Weekly Releases

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Java 11 support was delivered in LTS in Mar 2019: https://jenkins.io/blog/2019/03/11/let-s-celebrate-java-11-support/. I will close this EPIC, forgot to do it last year  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51805  
 
 
  Java 11 GA in Weekly Releases   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-28942) Allow plugins to declare that they do not use certain implied dependencies

2020-04-10 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-28942  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow plugins to declare that they do not use certain implied dependencies   
 

  
 
 
 
 

 
 This issue has nothing to do with Java versions. Maybe you are referring to JENKINS-55681?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.163400.1434531203000.8972.1586520900234%40Atlassian.JIRA.

[JIRA] (JENKINS-52310) Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-52310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support
 

  
 
 
 
 

 
 Gavin Mogan not sure it has been ever finished, but BlueOcean runs well with Java 11. Should we just close it?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.192093.1530522315000.8965.1586520840271%40Atlassian.JIRA.

[JIRA] (JENKINS-52284) Java 11: Support in LTS

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-52284  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52284  
 
 
  Java 11: Support in LTS   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Fixed but Unreleased Resolved  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.192059.1530292467000.8956.1586520781010%40Atlassian.JIRA.

[JIRA] (JENKINS-52284) Java 11: Support in LTS

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-52284  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Java 11 support was released in March 2019: https://jenkins.io/blog/2019/03/11/let-s-celebrate-java-11-support/ . The only remaining follow-up there was removing Java from the Windows installer which we will ship separately  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52284  
 
 
  Java 11: Support in LTS   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from

[JIRA] (JENKINS-28942) Allow plugins to declare that they do not use certain implied dependencies

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-28942  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow plugins to declare that they do not use certain implied dependencies   
 

  
 
 
 
 

 
 No longer relevant for Java 11 GA  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.163400.1434531203000.8945.1586520600271%40Atlassian.JIRA.

[JIRA] (JENKINS-61865) Windows Support Update

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61865  
 
 
  Windows Support Update   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 Currently Jenkins has no documented Windows Support policy. It would be great to get it fixed, and to deprecate/remove de-facto support for old platform versions: * There is explicit documentation for Windows support policy in Jenkins and its installer components. This policy is discussed and approved within the Jenkins Developer mailing list and Platform SIG. Suggested policy: ** All installers and service wrappers require Windows 7 / Windows Server 2012 or above (and .NET framework 4.0+). They also require 64bit platforms. Support for other platforms are provided via manual jenkins.war management ** Jenkins master runtime requires Windows 7 / Windows Server 2012 or above. It may work on older versions, but we do not guarantee compatibility ** Jenkins agent runtime requires Windows 7 / Windows Server 2012 or above. It may work on older versions, but we do not guarantee compatibility ** Jenkins master and agent Docker images are not required to provide images for the supported platforms. They can move ahead as maintainers  perefer  prefer  ** Custom Jenkins packaging may have different requirements (Jenkinsfile Runner, WARs built by Custom WAR Packager) * Downstream components (WinSW and WinP) include explicit system requirements * Jenkins core components are updated to follow  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[JIRA] (JENKINS-61866) Pipeline fails to detect failed powershell step

2020-04-10 Thread adm.malax+jenk...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sergey Dedik created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61866  
 
 
  Pipeline fails to detect failed powershell step   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core, pipeline  
 
 
Created: 
 2020-04-10 11:38  
 
 
Environment: 
 Jenkins version 2.222.1  Pipeline plugin version 2.6  Pipeline: Nodes and Processes plugin version 2.35  
 
 
Labels: 
 jenkins pipeline powershell failure  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Sergey Dedik  
 

  
 
 
 
 

 
 Consider following scripted pipeline: 

 

 node ('windows') {
stage ("stage 1") {
powershell '''
& C:\\Temp\\test.ps1
'''
}

stage ("stage 2") {
echo "stage 2"
}
} 

 Contents of the test.ps1 is following: 

 

param ($param1)

$ErrorActionPreference = "Stop"
Set-StrictMode -Version Latest

Write-Host $undefVar 

 The script is specifically designed to fail on trying to access undefined variable. This scenario is working correctly, Jenkins detects that PowerShell script returned something other than 0 exit code and fails

[JIRA] (JENKINS-61865) Windows Support Update

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61865  
 
 
  Windows Support Update   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 Currently Jenkins has no documented Windows Support policy. It would be great to get it fixed, and to deprecate/remove de-facto support for old platform versions: * There is explicit documentation for Windows support policy in Jenkins and its installer components. This policy is discussed and approved within the Jenkins Developer mailing list and Platform SIG. Suggested  changes  policy : ** All installers and service wrappers require Windows 7 / Windows Server 2012 or above (and .NET framework 4.0+). They also require 64bit platforms. Support for other platforms are provided via manual jenkins.war management ** Jenkins master runtime requires Windows 7 / Windows Server 2012 or above. It may work on older versions, but we do not guarantee compatibility ** Jenkins agent runtime requires Windows 7 / Windows Server 2012 or above. It may work on older versions, but we do not guarantee compatibility * * Jenkins master and agent Docker images are not required to provide images for the supported platforms. They can move ahead as maintainers perefer ** Custom Jenkins packaging may have different requirements (Jenkinsfile Runner, WARs built by Custom WAR Packager) *  Downstream components (WinSW and WinP) include explicit system requirements * Jenkins core components are updated to follow  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[JIRA] (JENKINS-61865) Windows Support Update

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61865  
 
 
  Windows Support Update   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Kohsuke Kawaguchi Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205729.1586518484000.8940.1586518560245%40Atlassian.JIRA.

[JIRA] (JENKINS-61863) Nullpointer in http-request-plugin

2020-04-10 Thread deja....@gmx.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tino Desjardins updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61863  
 
 
  Nullpointer in http-request-plugin   
 

  
 
 
 
 

 
Change By: 
 Tino Desjardins  
 

  
 
 
 
 

 
 When upgrading http-request-plugin from 1.8.24 to 1.8.25 the following Nullpointer occures:ERROR: Build step failed with exceptionjava.lang.NullPointerException at jenkins.plugins.http_request.HttpRequestExecution.from(HttpRequestExecution.java:121) at jenkins.plugins.http_request.HttpRequest.perform(HttpRequest.java:392) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1856) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428)Build step 'HTTP Request' marked build as failure Seems this is then the case if  there  the params "content-type" an "accept" in  *  Header * -section is not set.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[JIRA] (JENKINS-61865) Windows Support Update

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61865  
 
 
  Windows Support Update   
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 core, packaging, windows-slave-installer-module, windows-slaves-plugin  
 
 
Created: 
 2020-04-10 11:34  
 
 
Labels: 
 roadmap platform-sig  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 Currently Jenkins has no documented Windows Support policy. It would be great to get it fixed, and to deprecate/remove de-facto support for old platform versions: 
 
There is explicit documentation for Windows support policy in Jenkins and its installer components. This policy is discussed and approved within the Jenkins Developer mailing list and Platform SIG. Suggested changes: 
 
All installers and service wrappers require Windows 7 / Windows Server 2012 or above (and .NET framework 4.0+). They also require 64bit platforms. Support for other platforms are provided via manual jenkins.war management 
Jenkins master runtime requires Windows 7 / Windows Server 2012 or above. It may work on older versions, but we do not guarantee compatibility 
Jenkins agent runtime requires Windows 7 / Windows Server 2012 or above. It may work on older versions, but we do not guarantee compatibility 
  
Downstream components (WinSW and WinP) include explicit system

[JIRA] (JENKINS-61862) Consider removing the use of WinSW.NET2.exe

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-61862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Consider removing the use of WinSW.NET2.exe   
 

  
 
 
 
 

 
 I agree this is something required. I will create a new EPIC for Windows Support updates and add this ticket there  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205726.1586506269000.8934.1586517960113%40Atlassian.JIRA.

[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.

2020-04-10 Thread phani.nagar...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Phaneendra Nagaruru commented on  JENKINS-61854  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Test Ldap Settings" button stopped functioning.   
 

  
 
 
 
 

 
 I'm also facing the same issue while configuring Jenkins with LDAP. Using Jenkins 2.230.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205717.1586439894000.8930.1586517480158%40Atlassian.JIRA.

[JIRA] (JENKINS-61864) Support multiple values for IssueFieldUpdateStep

2020-04-10 Thread roman.blach...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Blachman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61864  
 
 
  Support multiple values for IssueFieldUpdateStep   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 jira-plugin  
 
 
Created: 
 2020-04-10 10:58  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roman Blachman  
 

  
 
 
 
 

 
 It looks like the current Jira IssueFieldUpdateStep operation doesn't support multiple values, which is very useful when using custom label fields in Jira which can be searchable.   I have created something that we use internally and I'm wondering how can this become part of the mainline release. https://github.com/romanblachman/jira-plugin/commit/0cc4bbbed74335a2d194e54fede86224dd3b8aae  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-61861) Jenkins Job is Triggering twice for a single Commit

Title: Message Title


 
 
 
 

 
 
 

 
   
 Anvesh Ramaswamy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61861  
 
 
  Jenkins Job is Triggering twice for a single Commit
 

  
 
 
 
 

 
Change By: 
 Anvesh Ramaswamy  
 
 
Attachment: 
 Screenshot 2020-04-10 at 4.15.23 PM.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205725.1586498472000.8919.1586515920220%40Atlassian.JIRA.

[JIRA] (JENKINS-61861) Jenkins Job is Triggering twice for a single Commit

2020-04-10 Thread bochenski.kuba+jenk...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Anvesh Ramaswamy commented on  JENKINS-61861  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Job is Triggering twice for a single Commit
 

  
 
 
 
 

 
 Hi Mark,    We are using Jenkins Version 1.609.3, and please find the git plugin versions info in attached screen shot. Can you help me with the steps to proceed to resolve that issue    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205725.1586498472000.8918.1586515920207%40Atlassian.JIRA.

[JIRA] (JENKINS-61860) Jenkins pipeline terraform for azure using azure service principle

2020-04-10 Thread xuzha...@microsoft.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 xu zhang edited a comment on  JENKINS-61860  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins pipeline terraform for azure using azure service principle
 

  
 
 
 
 

 
 [~mmreddy1582] Can Looks like  you  provide more detailed information?  How do you use  trying to log in to the Azure CLI using  service principle  credentials in pipeline ,  and  then run  terraform  script, you can omit the sensitive things  scripts .  Terraform-provider-azurerm does not support service principle login. They only support    Reproducible steps are very helpful for me to follow up this issue authenticating using the Azure CLI as a regular user .     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205724.1586492521000.8916.1586513280182%40Atlassian.JIRA.

[JIRA] (JENKINS-61853) Broken links to pull requests

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski commented on  JENKINS-61853  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Broken links to pull requests   
 

  
 
 
 
 

 
 This works for me with plugin version 1.17 and formatter 1.8 on Jenkins ver. 2.204.5 Without a way to reproduce there isn't much I can do to help. Maybe you are actually using a different markup formatter?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205716.158643871.8913.1586512920119%40Atlassian.JIRA.

[JIRA] (JENKINS-61860) Jenkins pipeline terraform for azure using azure service principle

2020-04-10 Thread xuzha...@microsoft.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 xu zhang commented on  JENKINS-61860  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins pipeline terraform for azure using azure service principle
 

  
 
 
 
 

 
 muragaiah muthirevula Can you provide more detailed information?  How do you use service principle credentials in pipeline and terraform script, you can omit the sensitive things.  Reproducible steps are very helpful for me to follow up this issue.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205724.1586492521000.8911.1586512140237%40Atlassian.JIRA.

[JIRA] (JENKINS-61863) Nullpointer in http-request-plugin

2020-04-10 Thread deja....@gmx.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tino Desjardins updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61863  
 
 
  Nullpointer in http-request-plugin   
 

  
 
 
 
 

 
Change By: 
 Tino Desjardins  
 
 
Summary: 
 Nullpointer  in http-request-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205727.158651131.8908.1586511420141%40Atlassian.JIRA.

[JIRA] (JENKINS-61863) Nullpointer

2020-04-10 Thread deja....@gmx.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tino Desjardins created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61863  
 
 
  Nullpointer   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Janario Oliveira  
 
 
Components: 
 http-request-plugin  
 
 
Created: 
 2020-04-10 09:35  
 
 
Environment: 
 Jenkins ver.: 2.222.1  http-request-plugin: 1.8.25  
 
 
Labels: 
 plugin jenkins exception  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Tino Desjardins  
 

  
 
 
 
 

 
 When upgrading http-request-plugin from 1.8.24 to 1.8.25 the following Nullpointer occures: ERROR: Build step failed with exception java.lang.NullPointerException at jenkins.plugins.http_request.HttpRequestExecution.from(HttpRequestExecution.java:121) at jenkins.plugins.http_request.HttpRequest.perform(HttpRequest.java:392) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1856) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428) Build step 'HTTP Request' marked build as failure   Seems this is then the case if there the params "content-type" an "accept" in Header-section is not set.

[JIRA] (JENKINS-61862) Consider removing the use of WinSW.NET2.exe

2020-04-10 Thread li...@outlook.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Next Turn assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61862  
 
 
  Consider removing the use of WinSW.NET2.exe   
 

  
 
 
 
 

 
Change By: 
 Next Turn  
 
 
Assignee: 
 Emilio  Escobar  Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205726.1586506269000.8904.1586506380201%40Atlassian.JIRA.

[JIRA] (JENKINS-61862) Consider removing the use of WinSW.NET2.exe

2020-04-10 Thread li...@outlook.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Next Turn created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61862  
 
 
  Consider removing the use of WinSW.NET2.exe   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Emilio Escobar   
 
 
Attachments: 
 image-2020-04-10-16-09-40-287.png  
 
 
Components: 
 core, windows-slave-installer-module, windows-slaves-plugin  
 
 
Created: 
 2020-04-10 08:11  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Next Turn  
 

  
 
 
 
 

 
 The use of .exe.config file in Windows Slave Installer Module has prevented WinSW from running on machines without .NET FX 4+ installed since 2013. No one has reported that this is a problem in the past years. Instead, there are only issues regarding using .NET FX 2.0 executables on newer platforms.https://github.com/jenkinsci/windows-slave-installer-module/blob/windows-slave-installer-1.12/src/main/resources/org/jenkinsci/modules/windows_slave_installer/jenkins-slave.exe.config https://github.com/winsw/winsw/issues/399 JENKINS-60005 JENKINS-31564 JENKINS-21484 Therefore, I propose the following actions: 
 
Safely switch to the .NET FX 4.0 executable in Windows Slave Installer Module. 
Re-investigate the need to use .NET FX 2.0 executables in Jenkins master and slaves.

[JIRA] (JENKINS-61861) Jenkins Job is Triggering twice for a single Commit

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-61861  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Job is Triggering twice for a single Commit
 

  
 
 
 
 

 
 A job being started twice for the same commit might be an indication that the repository is using both notifyCommit and web hooks. It might be an indication that the repository is being polled in less time than the build requires to complete.  Please provide precise steps that will allow others to duplicate the problem you're reporting. Precise steps include: 
 
Type of Jenkins job with the config.xml of the job 
Type of SCM system used and whether the repository is public or private 
Type of status notification system configured for the repository (web hooks, notifyCommit, polling, etc.) 
Contents of a Jenkins support bundle from the support core plugin so that plugin versions are noted and Jenkins configuration is provided 
Numbered list of steps the user performs which will show the problem on a newly installed Jenkins installation 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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-61861) Jenkins Job is Triggering twice for a single Commit

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-61861  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Job is Triggering twice for a single Commit
 

  
 
 
 
 

 
 A job being started twice for the same commit might be an indication that the repository is using both notifyCommit and web hooks.  It might be an indication that the repository is being polled in less time than the build requires to complete.  Please provide precise steps that will allow others to duplicate the problem you're reporting.  Precise steps include:* Type of Jenkins job with the config.xml of the job* Type of SCM system used and whether the repository is public or private* Type of status notification system configured for the repository (web hooks, notifyCommit, polling, etc.)* Contents of a Jenkins support bundle from the support core plugin so that plugin versions are noted and Jenkins configuration is provided* Numbered list of steps the user performs which will show the problem on a newly installed Jenkins  installation  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205725.1586498472000.8899.1586505960352%40Atlassian.JIRA.

[JIRA] (JENKINS-61861) Jenkins Job is Triggering twice for a single Commit

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61861  
 
 
  Jenkins Job is Triggering twice for a single Commit
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205725.1586498472000.8895.1586505540142%40Atlassian.JIRA.

[JIRA] (JENKINS-60801) Variable changes are shared between matrix (parallel) stages.

2020-04-10 Thread prakash.gandhi...@outlook.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 prakash raj assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60801  
 
 
  Variable changes are shared between matrix (parallel) stages.   
 

  
 
 
 
 

 
Change By: 
 prakash raj  
 
 
Assignee: 
 prakash raj  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.204130.1579197922000.8893.1586501640125%40Atlassian.JIRA.

[JIRA] (JENKINS-60801) Variable changes are shared between matrix (parallel) stages.

2020-04-10 Thread prakash.gandhi...@outlook.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 prakash raj assigned an issue to prakash raj  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60801  
 
 
  Variable changes are shared between matrix (parallel) stages.   
 

  
 
 
 
 

 
Change By: 
 prakash raj  
 
 
Assignee: 
 prakash raj  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.204130.1579197922000.8891.1586501580179%40Atlassian.JIRA.

[JIRA] (JENKINS-61853) Broken links to pull requests

2020-04-10 Thread mkochanow...@pzu.pl (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michał Kochanowicz commented on  JENKINS-61853  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Broken links to pull requests   
 

  
 
 
 
 

 
 I have downgraded "OWASP Markup Formatter" to 1.8 and see no improvement. Maybe there is something else causing this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205716.158643871.8889.1586499120116%40Atlassian.JIRA.

[JIRA] (JENKINS-61861) Jenkins Job is Triggering twice for a single Commit

Title: Message Title


 
 
 
 

 
 
 

 
   
 Anvesh Ramaswamy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61861  
 
 
  Jenkins Job is Triggering twice for a single Commit
 

  
 
 
 
 

 
Change By: 
 Anvesh Ramaswamy  
 
 
Attachment: 
 Screenshot 2020-04-09 at 6.53.39 PM.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205725.1586498472000.8887.1586498520426%40Atlassian.JIRA.

[JIRA] (JENKINS-61861) Jenkins Job is Triggering twice for a single Commit