[JIRA] (JENKINS-51537) How do we display jenkins errors in the pull request using stash notifier class in Jenkins file

2018-05-24 Thread rameishyed...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 vsv updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51537  
 
 
  How do we display jenkins errors in the pull request using stash notifier class in Jenkins file   
 

  
 
 
 
 

 
Change By: 
 vsv  
 
 
Environment: 
 jdk 1.8. 0_45 , jenkins version - 2.112  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51189) Job DSL fails to create new job

2018-05-24 Thread tomasno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tomas Norre Mikkelsen commented on  JENKINS-51189  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job DSL fails to create new job   
 

  
 
 
 
 

 
 To be fair, it's not a problem on all my instances, with same setup, so tend to think it's something not plugin related.  If I'm adjusting the Job Configuration by hand, I can save the config.xml.. So honestly I'm a little lost on what the problem can be.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51537) How do we display jenkins errors in the pull request using stash notifier class in Jenkins file

2018-05-24 Thread rameishyed...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramesh Kumar Yedla created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51537  
 
 
  How do we display jenkins errors in the pull request using stash notifier class in Jenkins file   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 stashnotifier-plugin  
 
 
Created: 
 2018-05-25 04:42  
 
 
Environment: 
 jdk 1.8.0_45, jenkins version - 2.112  
 
 
Labels: 
 jenkins plugin api  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ramesh Kumar Yedla  
 

  
 
 
 
 

 
 I am trying to use stash api call but not able to use it in Jenkinsfile integrating with it. Could you please suggest  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

[JIRA] (JENKINS-45614) Activity tab is really slow

2018-05-24 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy commented on  JENKINS-45614  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Activity tab is really slow   
 

  
 
 
 
 

 
 After more tests/search/experimentation/discussions/coffee/beers : 
 
Loading runs in parallel will be done (but optional with a feature flag to activate it) 
remove the testSummary field to avoid heavy calculation on first activity screen 
add an extra rest call in runDetails page to get the testSummary data 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51363) Pipeline support

2018-05-24 Thread zsy19980...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Share Cheng updated  JENKINS-51363  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51363  
 
 
  Pipeline support   
 

  
 
 
 
 

 
Change By: 
 Share Cheng  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51536) Blue Ocean link on Pipeline Multibranch branch page redirects to wrong page

2018-05-24 Thread dam...@addepar.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Damien Jiang created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51536  
 
 
  Blue Ocean link on Pipeline Multibranch branch page redirects to wrong page   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Denis Saponenko  
 
 
Components: 
 blueocean-plugin, pipeline-multibranch-defaults-plugin  
 
 
Created: 
 2018-05-24 23:35  
 
 
Environment: 
 Blue Ocean 1.5.0, Jenkins core 2.107.3, Pipeline 2.5, Pipeline: Multibranch 2.18  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Damien Jiang  
 

  
 
 
 
 

 
 On the branch page (/job/JOBNAME/job/BRANCHNAME/), clicking the "Blue Ocean" link redirects to the JOBNAME's page in Blue Ocean, rather than the BRANCHNAME's page. This makes navigating to the branch's page rather annoying. A side-effect of this is that when viewing a job in Blue Ocean that's downstream of a multibranch job, clicking the "upstream job" link doesn't send you to the build that you wanted, or even the branch that you wanted, but rather to the page for the whole job.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[JIRA] (JENKINS-51183) Create a demo Integration testing flow for Artifact Manager S3

2018-05-24 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51183  
 
 
  Create a demo Integration testing flow for Artifact Manager S3   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Summary: 
 Create  an  a  demo Integration testing flow for Artifact Manager S3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51183) Create an demo Integration testing flow for Artifact Manager S3

2018-05-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51183  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Create an demo Integration testing flow for Artifact Manager S3   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/model/bom/ComponentReference.java custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/model/bom/Reference.java http://jenkins-ci.org/commit/custom-war-packager/5ab8700c1c0ae31e08b1f9bb08721a87d8b8bb78 Log: JENKINS-51183 - Support Directory references in BOM  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51535) Warning in logs when Artifact Manager S3 is enabled && misconfigured but the build has not artifacts

2018-05-24 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51535  
 
 
  Warning in logs when Artifact Manager S3 is enabled && misconfigured but the build has not artifacts   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 When the build has artifacts defined but fails to deploy them, all further attempts to open the build lead to a stacktrace in logs. Probably the plugin should ignore builds where it knows that there was no artifacts downloaded to S3   {code:java}May 25, 2018 12:42:30 AM hudson.model.Run getArtifactsUpToWARNING: nulljava.io.IOException: Unable to get credentials from environment at io.jenkins.plugins.artifact_manager_s3.S3BlobStore.getCredentialsSupplier(S3BlobStore.java:124) at io.jenkins.plugins.artifact_manager_s3.S3BlobStore.getContext(S3BlobStore.java:110) at io.jenkins.plugins.artifact_manager_jclouds.JCloudsVirtualFile.getContext(JCloudsVirtualFile.java:99) at io.jenkins.plugins.artifact_manager_jclouds.JCloudsVirtualFile.listStorageMetadata(JCloudsVirtualFile.java:192) at io.jenkins.plugins.artifact_manager_jclouds.JCloudsVirtualFile.run(JCloudsVirtualFile.java:366) at hudson.model.Run.getArtifactsUpTo(Run.java:1098) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at 

[JIRA] (JENKINS-51535) Warning in logs when Artifact Manager S3 is enabled && misconfigured but the build has not artifacts

2018-05-24 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51535  
 
 
  Warning in logs when Artifact Manager S3 is enabled && misconfigured but the build has not artifacts   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Priority: 
 Minor Trivial  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51535) Warning in logs when Artifact Manager S3 is enabled && misconfigured but the build has not artifacts

2018-05-24 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51535  
 
 
  Warning in logs when Artifact Manager S3 is enabled && misconfigured but the build has not artifacts   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 artifact-manager-s3-plugin  
 
 
Created: 
 2018-05-24 22:45  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 

 

May 25, 2018 12:42:30 AM hudson.model.Run getArtifactsUpTo
WARNING: null
java.io.IOException: Unable to get credentials from environment
	at io.jenkins.plugins.artifact_manager_s3.S3BlobStore.getCredentialsSupplier(S3BlobStore.java:124)
	at io.jenkins.plugins.artifact_manager_s3.S3BlobStore.getContext(S3BlobStore.java:110)
	at io.jenkins.plugins.artifact_manager_jclouds.JCloudsVirtualFile.getContext(JCloudsVirtualFile.java:99)
	at io.jenkins.plugins.artifact_manager_jclouds.JCloudsVirtualFile.listStorageMetadata(JCloudsVirtualFile.java:192)
	at io.jenkins.plugins.artifact_manager_jclouds.JCloudsVirtualFile.run(JCloudsVirtualFile.java:366)
	at hudson.model.Run.getArtifactsUpTo(Run.java:1098)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
	at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
	at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
	at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
	at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
	at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
	at 

[JIRA] (JENKINS-51511) Build job serialization is failing on 2.107.3 LTS causing loss of data.

2018-05-24 Thread joe.nunnel...@socrata.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joe Nunnelley commented on  JENKINS-51511  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build job serialization is failing on 2.107.3 LTS causing loss of data.   
 

  
 
 
 
 

 
 additionally I'm stuck on the github pull request builder 1.35 as any plugin version greater than that is hitting the following bug (including 1.40).  https://github.com/jenkinsci/ghprb-plugin/issues/377.  Unfortunately, the 1.40 plugin is the one with the JEP-200 bug fix so we are not able to use it until the rate limit issue is resolved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-46379) withEnv mess with Job parameter (not case sensitive)

2018-05-24 Thread matt...@beechwoods.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Gabeler-Lee commented on  JENKINS-46379  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: withEnv mess with Job parameter (not case sensitive)   
 

  
 
 
 
 

 
 This drove me utterly insane working on my pipeline until I figured out what was symptomatically going on and came across this bug. Is there anything I can do to help move forwards addressing this issue?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51526) When "Delete root device on instance termination" is set, AMI's root device settings are ignored

2018-05-24 Thread daniel_atal...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Atallah commented on  JENKINS-51526  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When "Delete root device on instance termination" is set, AMI's root device settings are ignored   
 

  
 
 
 
 

 
 I created https://github.com/jenkinsci/ec2-plugin/pull/281 to fix this issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40562) Health metric setting is lost

2018-05-24 Thread annemoro...@alum.mit.edu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 AnneTheAgile commented on  JENKINS-40562  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Health metric setting is lost   
 

  
 
 
 
 

 
 Jenkins 2.100 same behavior; config is lost. I'm not sure what it is supposed to do.  I wish I could edit the "View" characteristics for the multibranch. For example, I cannot see which is the latest aborted / cancelled build.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51485) Warnings Plugin MSBuildParser does not handle hyphen or underscore in category

2018-05-24 Thread johnmc...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 John Case commented on  JENKINS-51485  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warnings Plugin MSBuildParser does not handle hyphen or underscore in category   
 

  
 
 
 
 

 
 Ulli Hafner This was auto assigned to you.  If you aren't the right person to do this can you please pass it off to somebody else?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51521) Git parameter does not show branch list in case deleteDir() is present in pipeline

2018-05-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git parameter does not show branch list in case deleteDir() is present in pipeline   
 

  
 
 
 
 

 
 Code changed in jenkins User: Boguslaw Klimas Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java http://jenkins-ci.org/commit/git-parameter-plugin/534a2fc768b45d9b03514718824f8e48aacd0490 Log: Merge pull request #65 from jenkinsci/feature/JENKINS-51521 JENKINS-51521: Default value for sortMode Compare: https://github.com/jenkinsci/git-parameter-plugin/compare/2369bfe8e101...534a2fc768b4 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51534) Git Publisher fails with NPE when trying to push a tag

2018-05-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-51534  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Publisher fails with NPE when trying to push a tag   
 

  
 
 
 
 

 
 Please provide more details of the job definition which is being used to create the tag and push it.  For example, answers to the following questions are needed:# What are the steps to reproduce the problem?# What job type (Freestyle, Pipeline, Multi-branch Pipeline, Matrix, ...)?# What is the git source server and what protocol is being used (ssh or https)?# What is the credential type used for the git publisher (private key or username/password)? Based on the stack trace and [this line|https://github.com/jenkinsci/git-plugin/blob/a7264a2c84a935b6444032c50820d34521d55f43/src/main/java/hudson/plugins/git/GitPublisher.java#L192] in the plugin source code, I'd guess that the project name is set to null.  That is quite unexpected since a project name is seen by users.  I don't know how a user would react to a null or empty project name,.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51521) Git parameter does not show branch list in case deleteDir() is present in pipeline

2018-05-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git parameter does not show branch list in case deleteDir() is present in pipeline   
 

  
 
 
 
 

 
 Code changed in jenkins User: klimas7 Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java http://jenkins-ci.org/commit/git-parameter-plugin/0c75bbfca2c894c7ccabefe528090b3813f15987 Log: JENKINS-51521: Default value for sortMode  *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51521) Git parameter does not show branch list in case deleteDir() is present in pipeline

2018-05-24 Thread klim...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas commented on  JENKINS-51521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git parameter does not show branch list in case deleteDir() is present in pipeline   
 

  
 
 
 
 

 
 Hi, If you useing the Snippet Generator, you should receive the complet the parameter definition, where all required field are initialization. 

 

properties([
parameters([
[
$class: 'GitParameterDefinition', 
branch: '', 
branchFilter: '.*', 
defaultValue: '', 
description: '', 
name: 'BRANCH', 
quickFilterEnabled: false, 
selectedValue: 'NONE', 
sortMode: 'NONE', 
tagFilter: '*', 
type: 'PT_BRANCH'
]
])
])
 

 Regardless, I will introduce the appropriate change. Regards Boguslaw  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51521) Git parameter does not show branch list in case deleteDir() is present in pipeline

2018-05-24 Thread klim...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas started work on  JENKINS-51521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Boguslaw Klimas  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51534) Git Publisher fails with NPE when trying to push a tag

2018-05-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-51534  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Publisher fails with NPE when trying to push a tag   
 

  
 
 
 
 

 
 Please provide more details of the job definition which is being used to create the tag and push it. For example, answers to the following questions are needed: 
 
What are the steps to reproduce the problem? 
What job type (Freestyle, Pipeline, Multi-branch Pipeline, Matrix, ...)? 
What is the git source server and what protocol is being used (ssh or https)? 
What is the credential type used for the git publisher (private key or username/password)? 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51534) Git Publisher fails with NPE when trying to push a tag

2018-05-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51534  
 
 
  Git Publisher fails with NPE when trying to push a tag   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-44849) Changeset for first run of generated job is empty

2018-05-24 Thread wayne.warre...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wayne Warren edited a comment on  JENKINS-44849  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Changeset for first run of generated job is empty   
 

  
 
 
 
 

 
 This is a pretty serious problem that significantly impairs the functionality of the `changeset` directive in declarative pipeline. I would go as far as to say that the `changeset` directive is worthless because of its counter intuitive and inconsistent behavior. It's led myself and a teammate to make several meaningless changes to our `changeset` usages to see if that would make the job run the conditional stages; of course whenever we made such changes within a PR the next build would actually run so we mistakenly thought we had fixed something , even though in reality all we had done was satisfy the condition under which Jenkins would actually acknowledge that changes are present in the PR as described in this ticket . Since I absolutely know some other poor fool is going to encounter this problem, this is the workaround I've come up with:{code:java}+  _expression_ {+    sh(returnStatus: true, script: 'git diff  origin/master --name-only | grep "^auth.*" > /dev/null') == 0+  }{code}   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-44849) Changeset for first run of generated job is empty

2018-05-24 Thread wayne.warre...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wayne Warren commented on  JENKINS-44849  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Changeset for first run of generated job is empty   
 

  
 
 
 
 

 
 This is a pretty serious problem that significantly impairs the functionality of the `changeset` directive in declarative pipeline. I would go as far as to say that the `changeset` directive is worthless because of its counter intuitive and inconsistent behavior. It's led myself and a teammate to make several meaningless changes to our `changeset` usages to see if that would make the job run the conditional stages; of course whenever we made such changes within a PR the next build would actually run so we mistakenly thought we had fixed something.   Since I absolutely know some other poor fool is going to encounter this problem, this is the workaround I've come up with: 

 

+  _expression_ {
+    sh(returnStatus: true, script: 'git diff  origin/master --name-only | grep "^auth.*" > /dev/null') == 0
+  } 

    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51534) Git Publisher fails with NPE when trying to push a tag

2018-05-24 Thread gunnar.schu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gunnar Schulze created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51534  
 
 
  Git Publisher fails with NPE when trying to push a tag   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2018-05-24 20:40  
 
 
Environment: 
 Jenkins 2.124  Git plugin 3.9.0  Release plugin 2.10.1  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Gunnar Schulze  
 

  
 
 
 
 

 
 When trying to use the Git Publisher to push a tag after a successful release build, the build fails with the following exception: java.lang.NullPointerException at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:192) at hudson.plugins.release.ReleaseWrapper.executeBuildSteps(ReleaseWrapper.java:417) at hudson.plugins.release.ReleaseWrapper.access$300(ReleaseWrapper.java:102) at hudson.plugins.release.ReleaseWrapper$4.tearDown(ReleaseWrapper.java:364) at hudson.model.Build$BuildExecution.doRun(Build.java:174) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1794) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)  
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-50597) Verify behavior of timeouts, interrupts, and network disconnections in S3 storage

2018-05-24 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-50597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Verify behavior of timeouts, interrupts, and network disconnections in S3 storage   
 

  
 
 
 
 

 
 Jesse Glick If you apply it at the stream level, it lets you distinguish between error cases and cases where something is slow because you're simply transferring a lot of data. Much less prone to false failures and it doesn't require user tweaking to avoid failing builds / API calls. Also pretty easy to implement!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51532) Plot plugin extreme memory leak with matrix jobs

2018-05-24 Thread cameron...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cameron updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51532  
 
 
  Plot plugin extreme memory leak with matrix jobs   
 

  
 
 
 
 

 
Change By: 
 Cameron  
 

  
 
 
 
 

 
 After a day or two, our Jenkins master becomes very unresponsive, taking 100% CPU of all available cores. The response time drops to tens of seconds, or sometimes even minutes to load a single page.Investigation with VisualVM shows much garbage collection taking place, with the heap nearly maxed out (at 1GB use of 1.25GB max). Looking at a heap snapshot, I discovered that the majority of memory is taken up by String[] objects, containing 5-tuples of Strings (referencing char[] arrays in turn). There are over a million of these small string arrays, each having contents similar to {{["35300", "Size", "709", "1526866800302", ""]}}.Tracing the references of the objects reveals that they are held by the {{rawPlotData}} of MatrixPlotPublisher objects. {{rawPlotData}} is itself an array; a single sample object in our snapshot contains 106710 string arrays like the one above.The most likely plot  we have  that's causing this  is a CSVSeries plot tracking the size of ~7000 generated files  (per matrix build) .  That's still several orders of magnitude less than the number of objects being built internally.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   

[JIRA] (JENKINS-51532) Plot plugin extreme memory leak with matrix jobs

2018-05-24 Thread cameron...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cameron updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51532  
 
 
  Plot plugin extreme memory leak with matrix jobs   
 

  
 
 
 
 

 
Change By: 
 Cameron  
 

  
 
 
 
 

 
 After a day or two, our Jenkins master becomes very unresponsive, taking 100% CPU of all available cores. The response time drops to tens of seconds, or sometimes even minutes to load a single page.Investigation with VisualVM shows much garbage collection taking place, with the heap nearly maxed out (at 1GB use of 1.25GB max). Looking at a heap snapshot, I discovered that the majority of memory is taken up by String[] objects, containing 5-tuples of Strings (referencing char[] arrays in turn). There are over a million of these small string arrays, each having contents similar to {{["35300", "Size", "709", "1526866800302", ""]}}.Tracing the references of the objects reveals that they are held by the {{rawPlotData}} of MatrixPlotPublisher objects. {{rawPlotData}} is itself an array; a single sample object in our snapshot contains 106710 string arrays like the one above. The most likely plot we have is a CSVSeries plot tracking the size of ~7000 generated files.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

 

[JIRA] (JENKINS-51533) Blue Ocean Archive tab not showing all artifacts

2018-05-24 Thread blondieou...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephanie Oubre created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51533  
 
 
  Blue Ocean Archive tab not showing all artifacts   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2018-05-24 19:59  
 
 
Environment: 
 awt.toolkit sun.awt.X11.XToolkit  executable-war /usr/lib/jenkins/jenkins.war  file.encoding UTF-8  file.encoding.pkg sun.io  file.separator /  hudson.TcpSlaveAgentListener.hostName jnkmas01-mgr01test-dfw.alchemy-ops.com  java.awt.graphicsenv sun.awt.X11GraphicsEnvironment  java.awt.headless true  java.awt.printerjob sun.print.PSPrinterJob  java.class.path /usr/lib/jenkins/jenkins.war  java.class.version 52.0  java.endorsed.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.el6_9.x86_64/jre/lib/endorsed  java.ext.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.el6_9.x86_64/jre/lib/ext:/usr/java/packages/lib/ext  java.home /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.151-1.b12.el6_9.x86_64/jre  java.io.tmpdir /tmp  java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib  java.runtime.name OpenJDK Runtime Environment  java.runtime.version 1.8.0_151-b12  java.specification.name Java Platform API Specification  java.specification.vendor Oracle Corporation  java.specification.version 1.8  java.vendor Oracle Corporation  java.vendor.url http://java.oracle.com/  java.vendor.url.bug http://bugreport.sun.com/bugreport/  java.version 1.8.0_151  java.vm.info mixed mode  java.vm.name OpenJDK 64-Bit Server VM  java.vm.specification.name Java Virtual Machine Specification  java.vm.specification.vendor Oracle Corporation  java.vm.specification.version 1.8  java.vm.vendor Oracle Corporation  java.vm.version 25.151-b12  jenkins.install.runSetupWizard false  JENKINS_HOME /var/lib/jenkins  jetty.git.hash 82b8fb23f757335bb3329d540ce37a2a2615f0a8  jna.loaded true  jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib/vmware-tools/lib64/libvmGuestLibJava.so:/usr/lib/vmware-tools/lib32/libvmGuestLibJava.so:/usr/lib/vmware-tools/lib64/libvmGuestLib.so:/usr/lib/vmware-tools/lib32/libvmGuestLib.so:/usr/lib64/qt-3.3/lib:/usr/lib64/atlas:/usr/lib64/mysql:/usr/lib/vmware-tools/lib64/libDeployPkg.so:/usr/lib/vmware-tools/lib32/libDeployPkg.so  jnidispatch.path /tmp/jna--1712433994/jna4804258446320816445.tmp  line.separator  mail.smtp.sendpartial true  mail.smtps.sendpartial true  org.apache.commons.jelly.tags.fmt.timeZone America/Chicago  os.arch amd64  os.name Linux  os.version 2.6.32-696.18.7.el6.x86_64  path.separator :  sun.arch.data.model 64  sun.boot.class.path 

[JIRA] (JENKINS-51511) Build job serialization is failing on 2.107.3 LTS causing loss of data.

2018-05-24 Thread joe.nunnel...@socrata.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joe Nunnelley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51511  
 
 
  Build job serialization is failing on 2.107.3 LTS causing loss of data.   
 

  
 
 
 
 

 
Change By: 
 Joe Nunnelley  
 
 
Labels: 
 2.0  JEP-200  build jenkins regression user-experience  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-16705) Native support for settings-security.xml (i. e. encrypted passwords)

2018-05-24 Thread jgang...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jae Gangemi commented on  JENKINS-16705  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Native support for settings-security.xml (i. e. encrypted passwords)   
 

  
 
 
 
 

 
 is there any movement on this issue? i would like to see the ability for the plugin to just drop a security-settings.xml file in place w/ the encrypted master password supplied from the credentials plugin. the plugin could drop the file directly in the .m2 directory or the location can be passed to maven using {{-Dsettings.security}} as described here: https://stackoverflow.com/questions/23782409/specify-custom-location-of-maven-security-settings-xml-file  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51502) Lightweight checkout fails on Build Replica

2018-05-24 Thread aliprince20112...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ali prince updated  JENKINS-51502  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51502  
 
 
  Lightweight checkout fails on Build Replica   
 

  
 
 
 
 

 
Change By: 
 ali prince  
 
 
Status: 
 In  Review  Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-16705) Native support for settings-security.xml (i. e. encrypted passwords)

2018-05-24 Thread jgang...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jae Gangemi edited a comment on  JENKINS-16705  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Native support for settings-security.xml (i. e. encrypted passwords)   
 

  
 
 
 
 

 
 is there any movement on this issue? i would like to see the ability for the plugin to just drop a {{security-settings.xml}} file in place w/ the encrypted master password supplied from the credentials plugin.the plugin could drop the file directly in the {{.m2}} directory or the location can be passed to maven using  \ { \ { {{ -Dsettings.security}} }}  as described here: [ https://stackoverflow.com/questions/23782409/specify-custom-location-of-maven-security-settings-xml-file ]  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51502) Lightweight checkout fails on Build Replica

2018-05-24 Thread aliprince20112...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ali prince stopped work on  JENKINS-51502  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 ali prince  
 
 
Resolution: 
 Won't Fix  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51502) Lightweight checkout fails on Build Replica

2018-05-24 Thread aliprince20112...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ali prince updated  JENKINS-51502  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51502  
 
 
  Lightweight checkout fails on Build Replica   
 

  
 
 
 
 

 
Change By: 
 ali prince  
 
 
Status: 
 Closed In Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51532) Plot plugin extreme memory leak with matrix jobs

2018-05-24 Thread cameron...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cameron created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51532  
 
 
  Plot plugin extreme memory leak with matrix jobs   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Veaceslav Gaidarji  
 
 
Components: 
 plot-plugin  
 
 
Created: 
 2018-05-24 19:47  
 
 
Environment: 
 Jenkins 2.107.2 + Plot plugin 2.04; master running on openjdk-1.8.0/linux.  
 
 
Labels: 
 plugins memory-leak  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Cameron  
 

  
 
 
 
 

 
 After a day or two, our Jenkins master becomes very unresponsive, taking 100% CPU of all available cores. The response time drops to tens of seconds, or sometimes even minutes to load a single page. Investigation with VisualVM shows much garbage collection taking place, with the heap nearly maxed out (at 1GB use of 1.25GB max). Looking at a heap snapshot, I discovered that the majority of memory is taken up by String[] objects, containing 5-tuples of Strings (referencing char[] arrays in turn). There are over a million of these small string arrays, each having contents similar to ["35300", "Size", "709", "1526866800302", ""]. Tracing the references of the objects reveals that they are held by the rawPlotData of MatrixPlotPublisher objects. rawPlotData is itself an array; a single sample object in our snapshot contains 106710 string arrays like the one above.  
 

  
 
 
 
 

 

[JIRA] (JENKINS-51326) JEP-200 long data type rejected after upgrade to 2.107.3

2018-05-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-51326  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JEP-200 long data type rejected after upgrade to 2.107.3   
 

  
 
 
 
 

 
 Looking for class="long" is probably a red herring. Judging by the stack trace, I suspect that there is some object with an enum-valued field, which is reading a config.xml with crazy content that would not have worked (perhaps some plugin incompatibly refactored the type of a persistent field) but would normally just be sending something to OldDataMonitor. Still not really sure how this becomes a long specifically. Is the error reproducible? Then forget about custom core patches and just bisect $JENKINS_HOME until you identify the jobs/**/config.xml responsible, and attach it here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51531) Duplicate Code number of elements in table

2018-05-24 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51531  
 
 
  Duplicate Code number of elements in table   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Ulli Hafner  
 
 
Components: 
 analysis-core-plugin  
 
 
Created: 
 2018-05-24 19:17  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ulli Hafner  
 

  
 
 
 
 

 
 How many items should be shown in the table if A is duplicated in B and C:  
 
1 
3 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
 

[JIRA] (JENKINS-51373) Define a plan of what can be achieved by May 23

2018-05-24 Thread knure...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 J Knurek commented on  JENKINS-51373  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Define a plan of what can be achieved by May 23   
 

  
 
 
 
 

 
 based on the notes from yesterday's meeting, I would think that this ticket should be closed, and a new one created for the next weeks' goals?   and/or maybe we should review from this what has been accomplished? at the very least, it'd be nice to see the next weeks goals defined out  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51530) Mulibranch pipeline job and mercurialSCMSource traits request

2018-05-24 Thread lilfoxs...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nickolas Fox updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51530  
 
 
  Mulibranch pipeline job and mercurialSCMSource traits request   
 

  
 
 
 
 

 
Change By: 
 Nickolas Fox  
 

  
 
 
 
 

 
 Without passing trait (behaviour) installation for multibranch pipeline using mercurial there's no chance to run jobs (probably due to hg-cache requirement or something like this).I discovered {code}mercurialInstallationSCMSourceTrait{code} in jenkins job reference manual but this node I can not apply to the following configuration:{code}multibranchPipelineJob('ci-per-branch'){displayName('CI')description('Continuous Integration Tests')triggers {periodic(10)}branchSources {branchSource {source {mercurialSCMSource {id "ci-per-branch-id"credentialsId " bsw access - bm- bot -id "source "https:// hg.iponweb.net repolocation / bidswitch/ui-ci/ "// here should be installation option to make it work}}}}orphanedItemStrategy {discardOldItems {numToKeep(0)daysToKeep(0)}}}{code}Unfortunately I have not find how to configure it by another ways.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
  

[JIRA] (JENKINS-50597) Verify behavior of timeouts, interrupts, and network disconnections in S3 storage

2018-05-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-50597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Verify behavior of timeouts, interrupts, and network disconnections in S3 storage   
 

  
 
 
 
 

 
 Probably most easily handled by just applying a timeout to the entire network operation, all the way from hostname resolution to receiving a status code and reading the response body.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51530) Mulibranch pipeline job and mercurialSCMSource traits request

2018-05-24 Thread lilfoxs...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nickolas Fox created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51530  
 
 
  Mulibranch pipeline job and mercurialSCMSource traits request   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Daniel Spilker  
 
 
Attachments: 
 2018-05-24_22-06-33.png, 2018-05-24_22-06-56.png  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2018-05-24 19:14  
 
 
Environment: 
 jenkins: 2.107.3  job-dsl: 1.69  mercurial-plugin: 2.3  
 
 
Labels: 
 mercurial  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Nickolas Fox  
 

  
 
 
 
 

 
 Without passing trait (behaviour) installation for multibranch pipeline using mercurial there's no chance to run jobs (probably due to hg-cache requirement or something like this). I discovered  

 
mercurialInstallationSCMSourceTrait 

  in jenkins job reference manual but this node I can not apply to the following configuration: 

 

multibranchPipelineJob('ci-per-branch'){
displayName('CI')
description('Continuous Integration Tests')
triggers {

[JIRA] (JENKINS-50597) Verify behavior of timeouts, interrupts, and network disconnections in S3 storage

2018-05-24 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-50597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Verify behavior of timeouts, interrupts, and network disconnections in S3 storage   
 

  
 
 
 
 

 
 Jesse Glick You also need to be mindful of streams going silent in the middle too – not all critical network failures will result in a 4xx being returned or an IOException. A generalized Stream wrapper that catches if a single read/write operation blocks for a prolonged period without new content might be helpful for that (then you throw a new IOException subtype).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50597) Verify behavior of timeouts, interrupts, and network disconnections in S3 storage

2018-05-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-50597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Verify behavior of timeouts, interrupts, and network disconnections in S3 storage   
 

  
 
 
 
 

 
 A review of the recommendations as well as the error list confirms that we should retry on 5xx but not 4xx errors, which seems like generally good advice not limited to S3. Of course there can be other network errors that precede even receiving an HTTP response code.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36543) Boolean input parameter ignores default value of false

2018-05-24 Thread bc...@ncsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brandon Chew reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I've recently created a pipeline job using a Boolean Parameter and have noticed that this issue is still happening.  I'm using Pipeline Stage View plugin 2.9.  Did this get reverted somehow in 2.9?  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36543  
 
 
  Boolean input parameter ignores default value of false   
 

  
 
 
 
 

 
Change By: 
 Brandon Chew  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-51476) Git parameter plugin is not retrieving revision number

2018-05-24 Thread klim...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas started work on  JENKINS-51476  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Boguslaw Klimas  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51476) Git parameter plugin is not retrieving revision number

2018-05-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51476  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git parameter plugin is not retrieving revision number   
 

  
 
 
 
 

 
 Code changed in jenkins User: Boguslaw Klimas Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/RevisionInfoFactory.java src/test/java/net/uaznia/lukanus/hudson/plugins/gitparameter/RevisionInfoFactoryTest.java http://jenkins-ci.org/commit/git-parameter-plugin/2369bfe8e101c3129e3c61966c5e721054f4a91f Log: Merge pull request #64 from jenkinsci/bugfix/JENKINS-51476 Bugfix/jenkins 51476 Compare: https://github.com/jenkinsci/git-parameter-plugin/compare/ee650d9b5dbc...2369bfe8e101 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51476) Git parameter plugin is not retrieving revision number

2018-05-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51476  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git parameter plugin is not retrieving revision number   
 

  
 
 
 
 

 
 Code changed in jenkins User: klimas7 Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/RevisionInfoFactory.java http://jenkins-ci.org/commit/git-parameter-plugin/d840a835fd28c77b3e8b7b7e4430b98df77fdbb9 Log: JENKINS-51476: JGit retrieving revision number, fix zone  *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50597) Verify behavior of timeouts, interrupts, and network disconnections in S3 storage

2018-05-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-50597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Verify behavior of timeouts, interrupts, and network disconnections in S3 storage   
 

  
 
 
 
 

 
 (FTR this fork is newer, but requires a newer version of Guava than Jenkins bundles.)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50597) Verify behavior of timeouts, interrupts, and network disconnections in S3 storage

2018-05-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-50597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Verify behavior of timeouts, interrupts, and network disconnections in S3 storage   
 

  
 
 
 
 

 
 Carlos Sanchez points me to guava-retrying which looks like a convenient way of implementing exponential backoff, if perhaps overkill. The official documentation for S3 appears to be here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51529) Use a single jenkinsfile across multiple git repos for pull requests?

2018-05-24 Thread ceast...@us.ibm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 carl eastman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51529  
 
 
  Use a single jenkinsfile across multiple git repos for pull requests?   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2018-05-24 17:59  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 carl eastman  
 

  
 
 
 
 

 
 We have a single jenkins file that we use for building and deploying across 50 different git repos. With blueocean how can we do the same thing for pull requests? Instead of having to keep 50 copies of the same jenkinsfile in sync across 50 git repos.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

  

[JIRA] (JENKINS-47505) Pipeline fails after upgrade to latest stable versions

2018-05-24 Thread cgil...@meditech.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chad Gilman commented on  JENKINS-47505  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline fails after upgrade to latest stable versions   
 

  
 
 
 
 

 
 We've started experiencing this problem after upgrading Jenkins from 2.73.2 to 2.107.3. The list of our active plugins is attached.   

 

May 24, 2018 1:15:00 PM WARNING hudson.XmlFile replaceIfNotAtTopLevel
JENKINS-45892: reference to org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject@5a040cf8[atat_pythonlibs/development] being saved from unexpected /var/lib/jenkins/jobs/atat_pythonlibs/jobs/development/indexing/indexing.xml
java.lang.IllegalStateException
	at hudson.XmlFile.replaceIfNotAtTopLevel(XmlFile.java:222)
	at hudson.model.AbstractItem.writeReplace(AbstractItem.java:492)
	at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:89)
	at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:141)
	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)
	at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)
	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)
	at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265)
	at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)
	at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224)
	at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138)
	at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209)
	at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150)
	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)
	at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)
	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)
	at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265)
	at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)
	at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224)
	at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138)
	at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209)
	at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150)
	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)
	at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)
	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)
	at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265)
	at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)
	at 

[JIRA] (JENKINS-47505) Pipeline fails after upgrade to latest stable versions

2018-05-24 Thread cgil...@meditech.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chad Gilman edited a comment on  JENKINS-47505  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline fails after upgrade to latest stable versions   
 

  
 
 
 
 

 
 We've started experiencing this problem after upgrading Jenkins from 2.73.2 to 2.107.3.    The list of our active plugins  is attached : [^active . txt]  {code:java}May 24, 2018 1:15:00 PM WARNING hudson.XmlFile replaceIfNotAtTopLevelJENKINS-45892: reference to org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject@5a040cf8[atat_pythonlibs/development] being saved from unexpected /var/lib/jenkins/jobs/atat_pythonlibs/jobs/development/indexing/indexing.xmljava.lang.IllegalStateException at hudson.XmlFile.replaceIfNotAtTopLevel(XmlFile.java:222) at hudson.model.AbstractItem.writeReplace(AbstractItem.java:492) at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:89) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:141) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at 

[JIRA] (JENKINS-47505) Pipeline fails after upgrade to latest stable versions

2018-05-24 Thread cgil...@meditech.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chad Gilman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47505  
 
 
  Pipeline fails after upgrade to latest stable versions   
 

  
 
 
 
 

 
Change By: 
 Chad Gilman  
 
 
Attachment: 
 active.txt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50597) Verify behavior of timeouts, interrupts, and network disconnections in S3 storage

2018-05-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-50597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Verify behavior of timeouts, interrupts, and network disconnections in S3 storage   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/io/jenkins/plugins/artifact_manager_jclouds/JCloudsArtifactManager.java src/test/java/io/jenkins/plugins/artifact_manager_jclouds/MockApiMetadata.java src/test/java/io/jenkins/plugins/artifact_manager_jclouds/MockApiMetadataTest.java src/test/java/io/jenkins/plugins/artifact_manager_jclouds/MockBlobStore.java src/test/java/io/jenkins/plugins/artifact_manager_jclouds/MockBlobStoreTest.java src/test/java/io/jenkins/plugins/artifact_manager_jclouds/NetworkTest.java http://jenkins-ci.org/commit/artifact-manager-s3-plugin/cb859635d11ca7c3a2822ee6608588bb3e9b1159 Log: Merge pull request #33 from jenkinsci/jclouds-mock JENKINS-50597 Introduce mocking framework and start to resolve network reliability issues Compare: https://github.com/jenkinsci/artifact-manager-s3-plugin/compare/30c5cfba...cb859635d11c *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49934) Add editor ATH coverage for editing and reordering of individual steps in a pipeline

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49934  
 
 
  Add editor ATH coverage for editing and reordering of individual steps in a pipeline   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Summary: 
 Add editor ATH coverage for  editing and  reordering of  individual  steps in a pipeline  
 

  
 
 
 
 

 
 *Summary:* * Reordering of steps within a stage, as described in [JENKINS-38323|https://issues.jenkins-ci.org/browse/JENKINS-38323] (a.k.a. "Drag and Drop"), is a useful new feature in the Pipeline editor.  * It makes sense to add some single-step editing as part of the same test.  ATH tests which verify this functionality would be a welcome improvement to editor test coverage.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-49578) "delete bundle" is not a big red button

2018-05-24 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier commented on  JENKINS-49578  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "delete bundle" is not a big red button   
 

  
 
 
 
 

 
 James Nord I created PR-145 to track this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49578) "delete bundle" is not a big red button

2018-05-24 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier started work on  JENKINS-49578  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Adrien Lecharpentier  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51260) global environment variables are not expanded (interpolated) in pipelines

2018-05-24 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-51260  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: global environment variables are not expanded (interpolated) in pipelines   
 

  
 
 
 
 

 
 It impacts the environment resolution anyway IIRC  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50828) Investigate automated test for BO log behavior

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50828  
 
 
  Investigate automated test for BO log behavior   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50829) Automated test for stopping running jobs in Blue Ocean

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50829  
 
 
  Automated test for stopping running jobs in Blue Ocean   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50826) Investigate automated test for navigating into Blue Ocean from Classic

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50826  
 
 
  Investigate automated test for navigating into Blue Ocean from Classic   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50827) ATH for exit to Classic flows from various places in the BO UI

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50827  
 
 
  ATH for exit to Classic flows from various places in the BO UI   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50825) Add editor ATH coverage for deleting stages from a pipeline

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50825  
 
 
  Add editor ATH coverage for deleting stages from a pipeline   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-pipeline-editor-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50779) De-flake BitbucketServerTest#testCreationNoJenkinsfile

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50779  
 
 
  De-flake BitbucketServerTest#testCreationNoJenkinsfile   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50604) Modify existing Bitbucket ATH test to perform end to end create flow

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50604  
 
 
  Modify existing Bitbucket ATH test to perform end to end create flow   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50572) Pipeline create flow fails when done against a blank repo on Bitbucket Server

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50572  
 
 
  Pipeline create flow fails when done against a blank repo on Bitbucket Server   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-pipeline-editor-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49930) Add editor ATH coverage for setting and changing environment variables

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49930  
 
 
  Add editor ATH coverage for setting and changing environment variables   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-pipeline-editor-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49932) Add editor ATH coverage for changing an existing stage in a Jenkinsfile

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49932  
 
 
  Add editor ATH coverage for changing an existing stage in a Jenkinsfile   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-pipeline-editor-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49934) Add editor ATH coverage for reordering of steps in a pipeline

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49934  
 
 
  Add editor ATH coverage for reordering of steps in a pipeline   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-pipeline-editor-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49927) Add editor ATH coverage for editing an already-existing Jenkinsfile

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49927  
 
 
  Add editor ATH coverage for editing an already-existing Jenkinsfile   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-pipeline-editor-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49928) Add editor ATH coverage for changing agent settings in a Jenkinsfile

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49928  
 
 
  Add editor ATH coverage for changing agent settings in a Jenkinsfile   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-pipeline-editor-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-48521) ATH test(s) for links embedded in Branches tab

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48521  
 
 
  ATH test(s) for links embedded in Branches tab   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-48496) Add a way to click blank parts of a row in ATH tests which test the Activity tab

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48496  
 
 
  Add a way to click blank parts of a row in ATH tests which test the Activity tab   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51528) Allow specifying Windows VM OS disk size

2018-05-24 Thread mbac...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Bacchi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51528  
 
 
  Allow specifying Windows VM OS disk size   
 

  
 
 
 
 

 
Change By: 
 Matt Bacchi  
 

  
 
 
 
 

 
 In Azure the default size for OS disks is [30 GB for Linux|https://docs.microsoft.com/en-us/azure/virtual-machines/linux/expand-disks] and [127 GB for Windows|https://docs.microsoft.com/en-us/azure/virtual-machines/windows/expand-os-disk].I would like the ability to increase the requested size of the OS disk in the Azure VM Agents Plugin directly. Another option is to use [deployment templates|https://docs.microsoft.com/en-us/azure/virtual-machines/windows/download-template] to [specify the OS disk size|https://docs.microsoft.com/en-us/azure/virtual-machines/windows/download-template]. I have already open an issue in Jira for this request, but I think both  jenkins  JENKINS -51527 and this current request may be useful.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-51527) Allow using downloaded Azure deployment templates

2018-05-24 Thread mbac...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Bacchi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51527  
 
 
  Allow using downloaded Azure deployment templates   
 

  
 
 
 
 

 
Change By: 
 Matt Bacchi  
 

  
 
 
 
 

 
 Azure allows you to download a template for a running VM and deploy it [using the command line|https://docs.microsoft.com/en-us/azure/virtual-machines/windows/download-template]This is useful if you want to modify the template and deploy slightly different values. For example you cannot deploy a Windows VM with an OS disk greater than 126GB, in order to do so you must add something like this to the template and deploy via the command line([described here|https://docs.microsoft.com/en-us/azure/virtual-machines/windows/using-managed-disks-template-deployments#managed-disks-template-formatting]):{code:java}  "dataDisks": [  {  "diskSizeGB": 500,  "lun": 0,  "createOption": "Empty"  }  ]{code}I would like to increase the OS disk size on my VMs managed by the Azure VM Agents Plugin and this is the only way I can see to do it for the time being, unless you add a feature to the plugin to set the OS disk size (I am planning to open a feature request or improvement issue for this request as well.  Edit: JENKINS-51528 added. )   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
   

[JIRA] (JENKINS-48252) ATH for Blue Ocean Pull Requests tab

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48252  
 
 
  ATH for Blue Ocean Pull Requests tab   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-48293) Improvements to GitCreationTest#testSSHPrivateRepostory so we can remove @Ignore

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48293  
 
 
  Improvements to GitCreationTest#testSSHPrivateRepostory so we can remove @Ignore   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-48378) Add stability / consistency to ParallelNavigationTest.java

2018-05-24 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48378  
 
 
  Add stability / consistency to ParallelNavigationTest.java   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Component/s: 
 blueocean-acceptance-test  
 
 
Component/s: 
 blueocean-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51402) Presigned url has the wrong region when running from a different one

2018-05-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-51402  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Presigned url has the wrong region when running from a different one   
 

  
 
 
 
 

 
 Code changed in jenkins User: Ivan Fernandez Calvo Path: README.md src/main/java/io/jenkins/plugins/artifact_manager_s3/S3BlobStore.java http://jenkins-ci.org/commit/artifact-manager-s3-plugin/30c5cfbad0ff4e421f7e19db6ca13d6bbfcf Log: JENKINS-51402 Presigned url has the wrong region (#29) Presigned url has the wrong region when running from a different one  *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/  Functionality will be removed from GitHub.com on January 31st, 2019.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51511) Build job serialization is failing on 2.107.3 LTS causing loss of data.

2018-05-24 Thread joe.nunnel...@socrata.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joe Nunnelley commented on  JENKINS-51511  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build job serialization is failing on 2.107.3 LTS causing loss of data.   
 

  
 
 
 
 

 
 I have tried to exempt the classes reported in the stack and restarted jenkins. it was not effective but perhaps my syntax was incorrect. -Dhudson.remoting.ClassFilter=org.kohsuke.github.GHPullRequestCommitDetail,org.jenkinsci.plugins.ghprb.GhprbCause,hudson.model.CauseAction,hudson.model.Queue$WaitingItem,hudson.model.Actionable,hudson.model.Queue$State,hudson.model.Cause$UpstreamCause,hudson.model.FreeStyleBuild          
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27070) Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration"

2018-05-24 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-27070  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration"
 

  
 
 
 
 

 
 Abubakar Mohammed no technical reason, especially for this specific / small change. It's just that the plugin has no active owner :-/  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51528) Allow specifying Windows VM OS disk size

2018-05-24 Thread mbac...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Bacchi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51528  
 
 
  Allow specifying Windows VM OS disk size   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Azure DevOps  
 
 
Components: 
 azure-vm-agents-plugin  
 
 
Created: 
 2018-05-24 15:54  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Matt Bacchi  
 

  
 
 
 
 

 
 In Azure the default size for OS disks is 30 GB for Linux and 127 GB for Windows. I would like the ability to increase the requested size of the OS disk in the Azure VM Agents Plugin directly. Another option is to use deployment templates to specify the OS disk size. I have already open an issue in Jira for this request, but I think both jenkins-51527 and this current request may be useful.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  

[JIRA] (JENKINS-51527) Allow using downloaded Azure deployment templates

2018-05-24 Thread mbac...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Bacchi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51527  
 
 
  Allow using downloaded Azure deployment templates   
 

  
 
 
 
 

 
Change By: 
 Matt Bacchi  
 

  
 
 
 
 

 
 Azure allows you to download a template for a running VM and deploy it [using the command line| [ https://docs.microsoft.com/en-us/azure/virtual-machines/windows/download-template |https://docs.microsoft.com/en-us/azure/virtual-machines/windows/download-template) ] ] This is useful if you want to modify the template and deploy slightly different values. For example you cannot deploy a Windows VM with an OS disk greater than 126GB, in order to do so you must add something like this to the template and deploy via the command line([described here|https://docs.microsoft.com/en-us/azure/virtual-machines/windows/using-managed-disks-template-deployments#managed-disks-template-formatting]):{code:java}  "dataDisks": [  {  "diskSizeGB": 500,  "lun": 0,  "createOption": "Empty"  }  ]{code}I would like to increase the OS disk size on my VMs managed by the Azure VM Agents Plugin and this is the only way I can see to do it for the time being, unless you add a feature to the plugin to set the OS disk size (I am planning to open a feature request or improvement issue for this request as well.)   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
 

[JIRA] (JENKINS-51527) Allow using downloaded Azure deployment templates

2018-05-24 Thread mbac...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Bacchi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51527  
 
 
  Allow using downloaded Azure deployment templates   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Azure DevOps  
 
 
Components: 
 azure-vm-agents-plugin  
 
 
Created: 
 2018-05-24 15:41  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Matt Bacchi  
 

  
 
 
 
 

 
 Azure allows you to download a template for a running VM and deploy it [using the command line|https://docs.microsoft.com/en-us/azure/virtual-machines/windows/download-template] This is useful if you want to modify the template and deploy slightly different values. For example you cannot deploy a Windows VM with an OS disk greater than 126GB, in order to do so you must add something like this to the template and deploy via the command line(described here): 

 

  "dataDisks": [
  {
  "diskSizeGB": 500,
  "lun": 0,
  "createOption": "Empty"
  }
  ]
 

 I would like to increase the OS disk size on my VMs managed by the Azure VM Agents Plugin and this is the only way I can see to do it for the time being, unless you add a feature to the plugin to set the OS disk size (I am planning to open a feature request or improvement issue for this request as well.)    
 

  
 
 
 
 

 
 
 
  

[JIRA] (JENKINS-51512) Git parameter plugin does not work with Windows agent

2018-05-24 Thread gunjan.mirchand...@rbccm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gunjan Mirchandani updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51512  
 
 
  Git parameter plugin does not work with Windows agent   
 

  
 
 
 
 

 
Change By: 
 Gunjan Mirchandani  
 
 
Attachment: 
 Error.PNG  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27070) Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration"

2018-05-24 Thread abubakar....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Abubakar Mohammed commented on  JENKINS-27070  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration"
 

  
 
 
 
 

 
 Thank you  Arnaud Héritier for your reply Just want to know that is there any technical reason behind not releasing this snapshot version?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51526) When "Delete root device on instance termination" is set, AMI's root device settings are ignored

2018-05-24 Thread daniel_atal...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Atallah created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51526  
 
 
  When "Delete root device on instance termination" is set, AMI's root device settings are ignored   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Francis Upton  
 
 
Components: 
 ec2-plugin  
 
 
Created: 
 2018-05-24 15:28  
 
 
Environment: 
 Jenkins 2.107.3, ec2-plugin 1.39  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Daniel Atallah  
 

  
 
 
 
 

 
 When the "Delete root device on instance termination" checkbox is used, the AMI's root block device is only partially copied, resulting in the loss of any non-default settings. One example of the impact is that even if the AMI's root device type should be gp2 (SSD) the type of EBS volume is "standard" (magnetic storage).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 

[JIRA] (JENKINS-51260) global environment variables are not expanded (interpolated) in pipelines

2018-05-24 Thread sorin.sbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sorin Sbarnea commented on  JENKINS-51260  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: global environment variables are not expanded (interpolated) in pipelines   
 

  
 
 
 
 

 
 Yes, EnvInject plugin is installed but we are not using it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50597) Verify behavior of timeouts, interrupts, and network disconnections in S3 storage

2018-05-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-50597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Verify behavior of timeouts, interrupts, and network disconnections in S3 storage   
 

  
 
 
 
 

 
 Carlos Sanchez notes that there are some expected and documented failure modes for S3 such as for rate limiting which certainly require handling. For now, should suffice to bake in some sort of basic exponential backoff strategy with a (long) ultimate timeout; can always introduce a tunable systemwide parameter later as more services are developed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50597) Verify behavior of timeouts, interrupts, and network disconnections in S3 storage

2018-05-24 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez edited a comment on  JENKINS-50597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Verify behavior of timeouts, interrupts, and network disconnections in S3 storage   
 

  
 
 
 
 

 
 I'll add that we need to make sure calls to AWS APIs are retried with backoff given my previous experience > bq.  If an API request exceeds the API request rate for its category, the request returns the RequestLimitExceeded error code. To prevent this error, ensure that your application doesn't retry API requests at a high rate. You can do this by using care when polling and by using exponential backoff retries.https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-50597) Verify behavior of timeouts, interrupts, and network disconnections in S3 storage

2018-05-24 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez edited a comment on  JENKINS-50597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Verify behavior of timeouts, interrupts, and network disconnections in S3 storage   
 

  
 
 
 
 

 
 I'll add that we need to make sure calls to AWS APIs are retried with backoff given my previous experience > If an API request exceeds the API request rate for its category, the request returns the RequestLimitExceeded error code. To prevent this error, ensure that your application doesn't retry API requests at a high rate. You can do this by using care when polling and by using exponential backoff retries.https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51243) Use JiraTestReporter plugin in Jenkins pipeline(Groovy) type of job.

2018-05-24 Thread luta.cata...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Catalin Luta commented on  JENKINS-51243  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Use JiraTestReporter plugin in Jenkins pipeline(Groovy) type of job.   
 

  
 
 
 
 

 
 Aashish Rajguru, manus, as you probably saw, Andrei Tuicu pushed a potential fix to the repo. We don't have time right now to test it thoroughly, but we have put some time aside for the release on the 5th of June. If you have time and know your way around snapshot builds, you can give it a go and test it out. Let us know if you find anything!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35988) Equivalent to polling commit exclusions for branch indexing

2018-05-24 Thread maxime....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Lemanissier edited a comment on  JENKINS-35988  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Equivalent to polling commit exclusions for branch indexing   
 

  
 
 
 
 

 
 I'm having a similar issue using pipeline library.When i merge a change on the master branch of my jenkins pipeline library, all jobs using this library (more than 100...) are  also  all  rebuilt simultaneously, which fills Jenkins queue for hours everytime a change is made on the library. .. This default behavior is probably well intended, as if the pipeline changes, all jobs using should be rebuilt, but when having a lot of jobs, this becomes unpractical/unusable.  I would prefer to wait for the next manual build or SCM change on the project repository (not on the lib one) to trigger a new build. Is there a way to not trigger builds due to changes on the pipeline library?If not, can i use a specific naming convention for the master branch of the pipeline library, and excluding it from polling as shared in previous comment? Will this exclusion also apply on pipeline library?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35988) Equivalent to polling commit exclusions for branch indexing

2018-05-24 Thread maxime....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Lemanissier commented on  JENKINS-35988  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Equivalent to polling commit exclusions for branch indexing   
 

  
 
 
 
 

 
 I'm having a similar issue using pipeline library. When i merge a change on the master branch of my jenkins pipeline library, all jobs using this library (more than 100...) are also rebuilt simultaneously, which fills Jenkins queue for hours everytime a change is made on the library. This default behavior is probably well intended, as if the pipeline changes, all jobs using should be rebuilt, but when having a lot of jobs, this becomes unpractical/unusable. Is there a way to not trigger builds due to changes on the pipeline library? If not, can i use a specific naming convention for the master branch of the pipeline library, and excluding it from polling as shared in previous comment? Will this exclusion also apply on pipeline library?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51521) Git parameter does not show branch list in case deleteDir() is present in pipeline

2018-05-24 Thread mikita_makare...@epam.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikita Makarenka edited a comment on  JENKINS-51521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git parameter does not show branch list in case deleteDir() is present in pipeline   
 

  
 
 
 
 

 
 Looks like I managed to walk around but it still some kind of bug from my point of view: The solution was to explictly specify "sortMode" in "properties" declaration{code:java}node {properties([parameters([[$class: 'GitParameterDefinition',name: 'gitBranch',listSize: '0',type: 'PT_BRANCH',sortMode: 'DESCENDING']])   ])stage ("2") {cleanWs()}stage("First stage") {git (url: git_url,credentialsId: git_cred)}  }{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51521) Git parameter does not show branch list in case deleteDir() is present in pipeline

2018-05-24 Thread mikita_makare...@epam.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikita Makarenka commented on  JENKINS-51521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git parameter does not show branch list in case deleteDir() is present in pipeline   
 

  
 
 
 
 

 
 Looks like I managed to walk around but it still some kind of bug from my point of view: The solution was to explictly specify "sortMode" in "properties" declaration 

 

node {
properties([
parameters([
[
$class: 'GitParameterDefinition',
name: 'gitBranch',
listSize: '0',
type: 'PT_BRANCH',
sortMode: 'DESCENDING'
]
])   
])


stage("First stage") {
git (
url: git_url,
credentialsId: git_cred
)
}
stage ("2") {
cleanWs()
}
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51521) Git parameter does not show branch list in case deleteDir() is present in pipeline

2018-05-24 Thread mikita_makare...@epam.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikita Makarenka edited a comment on  JENKINS-51521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git parameter does not show branch list in case deleteDir() is present in pipeline   
 

  
 
 
 
 

 
 Looks like I managed to walk around but it still some kind of bug from my point of view:The solution was to explictly specify "sortMode" in "properties" declaration{code:java}node {properties([parameters([[$class: 'GitParameterDefinition',name: 'gitBranch',listSize: '0',type: 'PT_BRANCH',sortMode: 'DESCENDING']])   ]) stage ("2") {  cleanWs()} stage("First stage") {git (url: git_url,credentialsId: git_cred)} stage ("2") {  cleanWs() } } {code}   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51111) Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab

2018-05-24 Thread roger.woo...@outlook.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roger Wooley commented on  JENKINS-5  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab   
 

  
 
 
 
 

 
 It only happens for the most recently ran job. If I perform the same steps on an older job it I can see the tests.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


  1   2   >