[JIRA] (JENKINS-56122) Not able to run UFT Scripts in UFT 14.50 via Jenkins

2019-02-17 Thread sakthiisaibharathi.samundeesw...@bnymellon.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sakthi Isai Bharathi Samundeeswari commented on  JENKINS-56122  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to run UFT Scripts in UFT 14.50 via Jenkins   
 

  
 
 
 
 

 
 Anda Sorina Laakso Ok. let me know.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56018) ATH Docker image should not be using Module patches starting from 2.163

2019-02-17 Thread manuelramonleonjime...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramon Leon commented on  JENKINS-56018  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ATH Docker image should not be using Module patches starting from 2.163   
 

  
 
 
 
 

 
 You're right, the image is not there, on Docker Hub (https://hub.docker.com/r/jenkins/ath/tags). The tag is created correctly on GH. No idea why, sorry.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56122) Not able to run UFT Scripts in UFT 14.50 via Jenkins

2019-02-17 Thread sakthiisaibharathi.samundeesw...@bnymellon.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sakthi Isai Bharathi Samundeeswari commented on  JENKINS-56122  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to run UFT Scripts in UFT 14.50 via Jenkins   
 

  
 
 
 
 

 
 Anda Sorina Laakso  
 
I have installed Tomcat in one of server. I pushed jenkins.war into tomcat webapps. 
Now, installed the microfocus plugin to run scripts. 
Now, i am executing the scripts from file system and ALM. 
I am getting the above message in console. 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56116) Commit messages are broken in the build details - changes

2019-02-17 Thread tasho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arseniy Tashoyan updated  JENKINS-56116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56116  
 
 
  Commit messages are broken in the build details - changes   
 

  
 
 
 
 

 
Change By: 
 Arseniy Tashoyan  
 
 
Resolution: 
 Cannot Reproduce  
 
 
Status: 
 Fixed but Unreleased Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56116) Commit messages are broken in the build details - changes

2019-02-17 Thread tasho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arseniy Tashoyan commented on  JENKINS-56116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Commit messages are broken in the build details - changes   
 

  
 
 
 
 

 
 I was able to narrow down the search. This problem occurs: 
 
both for Maven and Freestyle jobs 
configured to run on a specific slave 
 Here is the configuration of this slave: 

 

 cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.10 (Santiago)

 git --version
git version 1.7.1
 

 I tried to cleanup that slave, but of no avail: 
 
disconnect the node 
kill processes of user jenkins 
remove all files and directories belonging to user jenkins 
connect the node back 
      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56122) Not able to run UFT Scripts in UFT 14.50 via Jenkins

2019-02-17 Thread anda-sorina.laa...@microfocus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anda Sorina Laakso commented on  JENKINS-56122  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to run UFT Scripts in UFT 14.50 via Jenkins   
 

  
 
 
 
 

 
 Waiting for my colleague to come also from a meeting and we can schedule the call.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56122) Not able to run UFT Scripts in UFT 14.50 via Jenkins

2019-02-17 Thread anda-sorina.laa...@microfocus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anda Sorina Laakso commented on  JENKINS-56122  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to run UFT Scripts in UFT 14.50 via Jenkins   
 

  
 
 
 
 

 
 Can you give more details on what kind of script are you trying to run? Can you also tell us how the connection is done to the machine you are using?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56122) Not able to run UFT Scripts in UFT 14.50 via Jenkins

2019-02-17 Thread sakthiisaibharathi.samundeesw...@bnymellon.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sakthi Isai Bharathi Samundeeswari commented on  JENKINS-56122  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to run UFT Scripts in UFT 14.50 via Jenkins   
 

  
 
 
 
 

 
 Anda Sorina Laakso Yes.  Can you please look into now. We can schedule a call.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56122) Not able to run UFT Scripts in UFT 14.50 via Jenkins

2019-02-17 Thread anda-sorina.laa...@microfocus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anda Sorina Laakso commented on  JENKINS-56122  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to run UFT Scripts in UFT 14.50 via Jenkins   
 

  
 
 
 
 

 
 That is the entire message you get in the Jenkins console?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56122) Not able to run UFT Scripts in UFT 14.50 via Jenkins

2019-02-17 Thread sakthiisaibharathi.samundeesw...@bnymellon.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sakthi Isai Bharathi Samundeeswari commented on  JENKINS-56122  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to run UFT Scripts in UFT 14.50 via Jenkins   
 

  
 
 
 
 

 
 Anda Sorina Laakso I am not getting any response. Can you treat this as High Priority ticket  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56176) GIT_REVISION macro replaced with GIT_COMMIT but without support for length

2019-02-17 Thread ij...@yahoo.com.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Davis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56176  
 
 
  GIT_REVISION macro replaced with GIT_COMMIT but without support for length   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2019-02-18 07:22  
 
 
Environment: 
 Jenkins = 2.150.2  Git plugin = 4.0.0-rc  Build Name Setter = 1.6.9  Token Macro = 2.5  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Ian Davis  
 

  
 
 
 
 

 
 Support for GIT_REVISION macro appears to be replaced by GIT_COMMIT however the replacement does not support the length parameter.  Consequently "Build Name Setter" plugin is unable to set build names based on only the first few chars the the SHA so build names are massive.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 

[JIRA] (JENKINS-56018) ATH Docker image should not be using Module patches starting from 2.163

2019-02-17 Thread ogon...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža commented on  JENKINS-56018  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ATH Docker image should not be using Module patches starting from 2.163   
 

  
 
 
 
 

 
 Hmm, I am not seeing the image released: https://hub.docker.com/r/jenkins/ath/tags. Does anyone have an idea why?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56175) Submodule with space in git URL won't update

2019-02-17 Thread shanexper...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 shan shan updated  JENKINS-56175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56175  
 
 
  Submodule with space in git URL won't update   
 

  
 
 
 
 

 
Change By: 
 shan shan  
 
 
Status: 
 In  Review  Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56175) Submodule with space in git URL won't update

2019-02-17 Thread shanexper...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 shan shan updated  JENKINS-56175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56175  
 
 
  Submodule with space in git URL won't update   
 

  
 
 
 
 

 
Change By: 
 shan shan  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins

2019-02-17 Thread plros...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Roskin commented on  JENKINS-55945  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Got IllegalStateException while restart Jenkins
 

  
 
 
 
 

 
 I got this when I loaded a locally compiled version of the Stash pull request builder plugin and selected the "Restart Jenkins" checkbox. I saw that message. I reloaded the page after a few seconds, Jenkins is working normally. Jenkins 2.164 in Docker.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56154) PTC Integrity --Refusing to marshal org.apache.commons.logging.impl.SLF4JLocationAwareLog for security reasons;

2019-02-17 Thread caihaoh...@163.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cai Hao updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56154  
 
 
  PTC Integrity --Refusing to marshal org.apache.commons.logging.impl.SLF4JLocationAwareLog for security reasons;   
 

  
 
 
 
 

 
Change By: 
 Cai Hao  
 

  
 
 
 
 

 
 When I configure the job and set  *  Post-build Actions *  to  *  Integrity - CM Checkpoint * , and save, then it throw the error follow, What should I do to solve this problem?ava.lang.UnsupportedOperationException: Refusing to marshal org.apache.commons.logging.impl.SLF4JLocationAwareLog for security reasons; see  [  https://jenkins.io/redirect/class-filter/ ]  at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) 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)Caused: java.lang.RuntimeException: Failed to serialize hudson.scm.IntegrityCheckpointAction#logger for class hudson.scm.IntegrityCheckpointAction at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) 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.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at hudson.util.DescribableList$ConverterImpl.marshal(DescribableList.java:269) 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)Caused: java.lang.RuntimeException: Failed to serialize hudson.model.Project#publishers for class hudson.model.FreeStyleProject at hudson.util.RobustReflectionConverter$2.writeField(RobustReflect

[JIRA] (JENKINS-56154) PTC Integrity --Refusing to marshal org.apache.commons.logging.impl.SLF4JLocationAwareLog for security reasons;

2019-02-17 Thread caihaoh...@163.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cai Hao updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56154  
 
 
  PTC Integrity --Refusing to marshal org.apache.commons.logging.impl.SLF4JLocationAwareLog for security reasons;   
 

  
 
 
 
 

 
Change By: 
 Cai Hao  
 
 
Labels: 
 Integrity JEP-200  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56173) Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined

2019-02-17 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref commented on  JENKINS-56173  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/jenkins/pull/3903  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56152) Improve dependency errors message

2019-02-17 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref started work on  JENKINS-56152  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56173) Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined

2019-02-17 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref started work on  JENKINS-56173  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56152) Improve dependency errors message

2019-02-17 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref assigned an issue to Josh Soref  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56152  
 
 
  Improve dependency errors message   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Assignee: 
 Josh Soref  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56152) Improve dependency errors message

2019-02-17 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref commented on  JENKINS-56152  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve dependency errors message   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/jenkins/pull/3903  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56175) Submodule with space in git URL won't update

2019-02-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56175  
 
 
  Submodule with space in git URL won't update   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 When a git submodule repository name includes a space character, the git plugin versions through git plugin 4.0.0-rc ignore the submodule.Problem was found by the plugin pom 3.36 extension which includes a space character in the temporary directories created by the Jenkins test harness.For example, I defined a repository {{ssh:// hasphrase@ home.markwaite.net :45022 / \ ~/git/bare/bugs/without-space.git}} which includes a submodule from {{ssh:// hasphrase@ home.markwaite.net :45022 / \ ~/git/bare/bugs/with space.git}}.    I can clone the {{without-space}} repository from the command line and can update the submodule.  When I perform the same operation from a Jenkins job, the repository is cloned, but the submodule is not detected and never updates.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56175) Submodule with space in git URL won't update

2019-02-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite started work on  JENKINS-56175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56175) Submodule with space in git URL won't update

2019-02-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56175  
 
 
  Submodule with space in git URL won't update   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2019-02-18 04:29  
 
 
Environment: 
 Git client plugin 3.0.0-rc (and all previous versions)  Git plugin 4.0.0-rc (and all previous versions)  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Mark Waite  
 

  
 
 
 
 

 
 When a git submodule repository name includes a space character, the git plugin versions through git plugin 4.0.0-rc ignore the submodule. Problem was found by the plugin pom 3.36 extension which includes a space character in the temporary directories created by the Jenkins test harness. For example, I defined a repository ssh://hasphr...@home.markwaite.net:45022//git/bare/bugs/without-space.git which includes a submodule from ssh://hasphr...@home.markwaite.net:45022//git/bare/bugs/with space.git.  I can clone the without-space repository from the command line and can update the submodule. When I perform the same operation from a Jenkins job, the repository is cloned, but the submodule is not detected and never updates.  
 

  
 
 
 
 

 
 
 

 
 
 

[JIRA] (JENKINS-56174) AmazonWebServicesCredentialsBinding within withEnv does not respect proxy settings

2019-02-17 Thread behran...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Behrang Saeedzadeh created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56174  
 
 
  AmazonWebServicesCredentialsBinding within withEnv does not respect proxy settings   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Nicolas De Loof  
 
 
Components: 
 aws-credentials-plugin  
 
 
Created: 
 2019-02-18 04:04  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Behrang Saeedzadeh  
 

  
 
 
 
 

 
 While this code succeeds to connect to STS and assume a new role: 

 

withEnv(['AWS_ACCESS_KEY_ID=', 'AWS_SECRET_ACCESS_KEY=', 'HTTP_PROXY=http://example:', 'HTTPS_PROXY=http://example:', 'NO_PROXY=some,domain,names']) {
sh 'aws sts assume-role --role-arn arn:aws:iam::...:role/RoleName --role-session-name "SessionName"'
}
 

 This code fails: 

 

withEnv(['AWS_ACCESS_KEY_ID=', 'AWS_SECRET_ACCESS_KEY=', 'HTTP_PROXY=http://example:', 'HTTPS_PROXY=http://example:', 'NO_PROXY=some,domain,names']) {
withCredentials([[
$class: 'AmazonWebServicesCredentialsBinding',
credentialsId: 'SomeId',
accessKeyVariable: 'AWS_ACCESS_KEY_ID',
secretKeyVariable: 'AWS_SECRET_ACCESS_KEY'
]]) {
echo "Test"
}
}
 

 With this error: 

 

hudson.remoting.ProxyException: java.net.SocketTimeoutException: connect timed out
	at java.net.PlainSock

[JIRA] (JENKINS-56173) Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined

2019-02-17 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref commented on  JENKINS-56173  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined   
 

  
 
 
 
 

 
 Fwiw, the message is incorrect, the credentials plugin isn't installed at all. It's available in /pluginManager/available. Since I've managed to trigger this w/ two installs, it's apparently quite possible. One fix for the message would be to change disabled to missing the other approach would be to try to distinguish between disabled and not-installed plugins. I'm leading towards just using missing which covers both categories.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56173) Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined

2019-02-17 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref commented on  JENKINS-56173  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined   
 

  
 
 
 
 

 
 w/ my fix, this is what I get:    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56173) Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined

2019-02-17 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56173  
 
 
  Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Attachment: 
 image-2019-02-17-21-21-30-116.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56173) Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined

2019-02-17 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56173  
 
 
  Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-02-18 02:08  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Josh Soref  
 

  
 
 
 
 

 
 I don't have many plugins installed/enabled. When I visit /pluginManager/installed, if I hover over Config File Provider Plugin, I get an exception: 

 

 _table.js:233 Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined
at populateEnableDisableInfo (_table.js:233)
at _table.js:379
populateEnableDisableInfo @ _table.js:233
(anonymous) @ _table.js:379
setTimeout (async)
(anonymous) @ _table.js:376
responder @ prototype.js:5656 

 This happens w/ Jenkins ver. 2.161 as well as trunk (albeit w/ my custom stuff).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[JIRA] (JENKINS-56173) Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined

2019-02-17 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref assigned an issue to Josh Soref  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56173  
 
 
  Uncaught TypeError: Cannot read property 'jenkinsPluginMetadata' of undefined   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Assignee: 
 Josh Soref  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56077) New Stapler routing rules result in the URL "/descriptorByName/com.microsoft.azure.vmagent.AzureVMAgentTemplate/fillAvailabilityTypeItems" no longer being allowed.

2019-02-17 Thread jie...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jie Shen commented on  JENKINS-56077  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New Stapler routing rules result in the URL "/descriptorByName/com.microsoft.azure.vmagent.AzureVMAgentTemplate/fillAvailabilityTypeItems" no longer being allowed.   
 

  
 
 
 
 

 
 I will remove this warning here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56154) PTC Integrity --Refusing to marshal org.apache.commons.logging.impl.SLF4JLocationAwareLog for security reasons;

2019-02-17 Thread caihaoh...@163.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cai Hao commented on  JENKINS-56154  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PTC Integrity --Refusing to marshal org.apache.commons.logging.impl.SLF4JLocationAwareLog for security reasons;   
 

  
 
 
 
 

 
 Oleg Nenashev Thanks for the reply.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54954) 401 response requesting Quality Gate status

2019-02-17 Thread miles_ma...@trimble.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Miles Mason commented on  JENKINS-54954  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 401 response requesting Quality Gate status   
 

  
 
 
 
 

 
 Rafael Ramos - Yes, you're right, I needed to add permissions for "Administer Quality Gates" so the Jenkins user could get the status...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56164) Hockeyapp: upload always fails raising ConnectionClosedException

2019-02-17 Thread mez.pah...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56164  
 
 
  Hockeyapp: upload always fails raising ConnectionClosedException   
 

  
 
 
 
 

 
Change By: 
 Mez Pahlan  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56164) Hockeyapp: upload always fails raising ConnectionClosedException

2019-02-17 Thread mez.pah...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56164  
 
 
  Hockeyapp: upload always fails raising ConnectionClosedException   
 

  
 
 
 
 

 
Change By: 
 Mez Pahlan  
 
 
Priority: 
 Major Trivial  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56164) Hockeyapp: upload always fails raising ConnectionClosedException

2019-02-17 Thread mez.pah...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan commented on  JENKINS-56164  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Hockeyapp: upload always fails raising ConnectionClosedException   
 

  
 
 
 
 

 
 Glad you got to the bottom of it.  The Wiki should be editable I am unaware of any restrictions apart from the fact that you need to be logged in. I'd welcome a pull request to improve documentation if you want to contribute one. If not I'll see about adding something in there myself when I've got some time.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55013) support for App Center

2019-02-17 Thread mez.pah...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mez Pahlan commented on  JENKINS-55013  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: support for App Center   
 

  
 
 
 
 

 
 Just a quick update. I am working on this. No ETA at the moment, but work had commenced.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56158) package v. 2.150.3 is absent

2019-02-17 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56158  
 
 
  package v. 2.150.3 is absent   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56009) Log audit events for user credentials

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56009  
 
 
  Log audit events for user credentials   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Assignee: 
 David Olorundare  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55694) Log audit events for user property changes

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55694  
 
 
  Log audit events for user property changes   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Assignee: 
 David Olorundare  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56172) Fix audit-log configuration output file issue

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56172  
 
 
  Fix audit-log configuration output file issue   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 audit-log-plugin  
 
 
Created: 
 2019-02-17 21:21  
 
 
Labels: 
 audit-logging  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 David Olorundare  
 

  
 
 
 
 

 
 Discussed in the Gitter Outreachy chats- https://gitter.im/jenkinsci/outreachy?at=5c45cbe3cb47ec30007b3ed1 The current log4j.xml configuration-output file causes infinite loops in the property interpolation of system variables used. Thereby resulting in no creation of audit logs when Jenkins is manually run from the command-line and operated from its UI.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 

[JIRA] (JENKINS-56167) Remove trilead-ssh2 dependency from hudson.cli.PrivateKeyProvider

2019-02-17 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo started work on  JENKINS-56167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56167) Remove trilead-ssh2 dependency from hudson.cli.PrivateKeyProvider

2019-02-17 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo updated  JENKINS-56167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56167  
 
 
  Remove trilead-ssh2 dependency from hudson.cli.PrivateKeyProvider   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54958) Subversion changelog corrupted by parallel checkout with stacktrace at the end of the pipeline

2019-02-17 Thread a...@schrell.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Schrell edited a comment on  JENKINS-54958  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Subversion changelog corrupted by parallel checkout with stacktrace at the end of the pipeline   
 

  
 
 
 
 

 
 Same here. Can anyone point me to the source where the changelog file  name  ( with number) is created? Looks like a synchronization is needed. I looked into the source but I could not find it.Andreas   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54958) Subversion changelog corrupted by parallel checkout with stacktrace at the end of the pipeline

2019-02-17 Thread a...@schrell.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Schrell commented on  JENKINS-54958  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Subversion changelog corrupted by parallel checkout with stacktrace at the end of the pipeline   
 

  
 
 
 
 

 
 Same here. Can anyone point me to the source where the changelog file (number) is created? Looks like a synchronization is needed. I looked into the source but I could not find it. Andreas    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56171) blue ocean pipeline cache misleading, at least needs a mechanism to clear

2019-02-17 Thread mlandma...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 boris ivan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56171  
 
 
  blue ocean pipeline cache misleading, at least needs a mechanism to clear   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2019-02-17 18:02  
 
 
Priority: 
  Major  
 
 
Reporter: 
 boris ivan  
 

  
 
 
 
 

 
 I'm actively working on a pipeline. Occasionally I will delete or move a stage, in the effort to working on this pipeline (using declarative). When I run the pipeline again, I see various stages that I've already deleted. Sometimes they even go green and move on to the next stage. In all cases, when the pipeline finishes, the correct view is painted, and the ghost stages disappear. But this is a real problem. Our pipelines take hours to run - it's not a quick couple of seconds in which the incorrect graph is drawn. I've seen debate across various JIRAs in which the developers mentioned they aren't planning on removing the cache because some users might like it. I disagree, but you can't please everyone. However, given that using the cache shows blatantly incorrect visualizations, a fix needs to be provided. I think it should always work and if that means not using the cache at all I'd be happy, but to appease everyone, maybe you can provide an optional way to clear the cache before the next run, to appease the group of us who need the visualization to not be wrong.  
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-56170) Update ApiTokenProperty use of SecurityListener

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare assigned an issue to David Olorundare  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56170  
 
 
  Update ApiTokenProperty use of SecurityListener   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Assignee: 
 David Olorundare  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56008) Update HudsonPrivateSecurityRealm.Details use of SecurityListener

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare updated  JENKINS-56008  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56008  
 
 
  Update HudsonPrivateSecurityRealm.Details use of SecurityListener   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56005) Add user property change listener method to SecurityListener

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare updated  JENKINS-56005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56005  
 
 
  Add user property change listener method to SecurityListener   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56008) Update HudsonPrivateSecurityRealm.Details use of SecurityListener

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare started work on  JENKINS-56008  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56005) Add user property change listener method to SecurityListener

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare started work on  JENKINS-56005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55667) Configure "Job Configuration History" plugin with "Configuration as Code"

2019-02-17 Thread deweya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Dewey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55667  
 
 
  Configure "Job Configuration History" plugin with "Configuration as Code"   
 

  
 
 
 
 

 
Change By: 
 Austin Dewey  
 
 
Comment: 
 I tried giving this a shot but it looks like the parent needs updated to at least 3.0 for configuration-as-code to be compatible. A lot of things break (mostly test failures) when jumping to this version. Are there any plans to upgrade the parent pom to version 3.0 or higher soon?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56136) Update Log4j version to 2.11.2

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare started work on  JENKINS-56136  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56005) Add user property change listener method to SecurityListener

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare stopped work on  JENKINS-56005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56009) Log audit events for user credentials

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare assigned an issue to David Olorundare  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56009  
 
 
  Log audit events for user credentials   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Assignee: 
 David Olorundare  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56008) Update HudsonPrivateSecurityRealm.Details use of SecurityListener

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare stopped work on  JENKINS-56008  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55694) Log audit events for user property changes

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare assigned an issue to David Olorundare  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55694  
 
 
  Log audit events for user property changes   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Assignee: 
 David Olorundare  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56136) Update Log4j version to 2.11.2

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare stopped work on  JENKINS-56136  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 David Olorundare  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56170) Update ApiTokenProperty use of SecurityListener

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56170  
 
 
  Update ApiTokenProperty use of SecurityListener   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 audit-log-plugin  
 
 
Created: 
 2019-02-17 15:58  
 
 
Labels: 
 audit-logging  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 David Olorundare  
 

  
 
 
 
 

 
 Update the methods within the ApiTokenProperty class; to make use of the user-property-change listener method of the SecurityListener class. The class has methods which handle api-token creations and deletions made from the Jenkins UI in a user's configuration page. 
 
To perform this update will require modifying the ApiTokenProperty class within the jenkins-core hudson/security package. 
Unit tests for the updated ApiTokenProperty class method should be implemented, to verify its correctness, and should be added to the preexisting Jenkins unit tests for the ApiTokenProperty class. 
 The SecurityListener class method related to listening for user-property-change events was added in JENKINS-56005  
 

  
 
 
 
 

 
 
 

  

[JIRA] (JENKINS-56008) Update HudsonPrivateSecurityRealm.Details use of SecurityListener

2019-02-17 Thread davi...@ieee.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Olorundare updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56008  
 
 
  Update HudsonPrivateSecurityRealm.Details use of SecurityListener   
 

  
 
 
 
 

 
Change By: 
 David Olorundare  
 

  
 
 
 
 

 
  Related to JENKINS-55694 Update the newInstance() method within the Details class of HudsonPrivateSecurityRealm; to make use of the user-property-change listener method of the SecurityListener class. The Details class specifically handles the update of user-password changes made from the Jenkins UI in a user's configuration page. * To perform this update will require modifying the HudsonPrivateSecurityRealm.Details class within the jenkins-core hudson/security package. * Unit tests for the updated HudsonPrivateSecurityRealm.Details class method should be implemented, to verify its correctness, and should be added to the preexisting Jenkins unit tests for the HudsonPrivateSecurityRealm.Details class.The SecurityListener class method related to listening for user-property-change events was added in  -- JENKINS-56005  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55667) Configure "Job Configuration History" plugin with "Configuration as Code"

2019-02-17 Thread deweya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Dewey commented on  JENKINS-55667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configure "Job Configuration History" plugin with "Configuration as Code"   
 

  
 
 
 
 

 
 I tried giving this a shot but it looks like the parent needs updated to at least 3.0 for configuration-as-code to be compatible. A lot of things break (mostly test failures) when jumping to this version. Are there any plans to upgrade the parent pom to version 3.0 or higher soon?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55667) Configure "Job Configuration History" plugin with "Configuration as Code"

2019-02-17 Thread deweya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Dewey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55667  
 
 
  Configure "Job Configuration History" plugin with "Configuration as Code"   
 

  
 
 
 
 

 
Change By: 
 Austin Dewey  
 

  
 
 
 
 

 
 The Job Config History plugin contains several fields that should be able to be configured with "Configuration as Code". These fields are normally configured under "Manage Jenkins". The fields can be viewed at [https://plugins.jenkins.io/jobConfigHistory] under "Interdependencies with other Plugins". I tried giving this a shot but it looks like the parent needs updated to at least 3.0 for configuration-as-code to be compatible, which is likely its own story in and of itself.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55667) Configure "Job Configuration History" plugin with "Configuration as Code"

2019-02-17 Thread deweya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Dewey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55667  
 
 
  Configure "Job Configuration History" plugin with "Configuration as Code"   
 

  
 
 
 
 

 
Change By: 
 Austin Dewey  
 

  
 
 
 
 

 
 The Job Config History plugin contains several fields that should be able to be configured with "Configuration as Code". These fields are normally configured under "Manage Jenkins". The fields can be viewed at [https://plugins.jenkins.io/jobConfigHistory] under "Interdependencies with other Plugins".   I tried giving this a shot but it looks like the parent needs updated to at least 3.0 for configuration-as-code to be compatible, which is likely its own story in and of itself.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55667) Configure "Job Configuration History" plugin with "Configuration as Code"

2019-02-17 Thread deweya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Dewey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55667  
 
 
  Configure "Job Configuration History" plugin with "Configuration as Code"   
 

  
 
 
 
 

 
Change By: 
 Austin Dewey  
 

  
 
 
 
 

 
 The Job Config History plugin contains several fields that should be able to be configured with "Configuration as Code". These fields are normally configured under "Manage Jenkins". The fields can be viewed at [https://plugins.jenkins.io/jobConfigHistory] under "Interdependencies with other Plugins".  I tried giving this a shot but it looks like the parent needs updated to at least 3.0 for configuration-as-code to be compatible, which is likely its own story in and of itself.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55667) Configure "Job Configuration History" plugin with "Configuration as Code"

2019-02-17 Thread deweya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Dewey assigned an issue to Stefan Brausch  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55667  
 
 
  Configure "Job Configuration History" plugin with "Configuration as Code"   
 

  
 
 
 
 

 
Change By: 
 Austin Dewey  
 
 
Assignee: 
 Austin Dewey Stefan Brausch  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55667) Configure "Job Configuration History" plugin with "Configuration as Code"

2019-02-17 Thread deweya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Dewey stopped work on  JENKINS-55667  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Austin Dewey  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread inbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Inbar Hachmon commented on  JENKINS-56169  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
 True, thank you   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated  JENKINS-56169  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56169  
 
 
  Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Resolution: 
 Not A Defect  
 
 
Status: 
 Fixed but Unreleased Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated  JENKINS-56169  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56169  
 
 
  Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Status: 
 Reopened Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-56169  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
 This makes a legitimate feature request though  (unless filed elsewhere already).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread inbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Inbar Hachmon updated  JENKINS-56169  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56169  
 
 
  Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
Change By: 
 Inbar Hachmon  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread inbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Inbar Hachmon commented on  JENKINS-56169  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
 I see.  Thank you for the quick reply!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56169  
 
 
  Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Issue Type: 
 Bug New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-56169  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
 This is currently unsupported.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56150) git plugin with repo that has empty .gitmodules file NPE during submodule update

2019-02-17 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56150  
 
 
  git plugin with repo that has empty .gitmodules file NPE during submodule update   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 If a git repository happens to have an empty .gitmodules file, then the git client plugin will assume that the repository has submodules. Then, when the submodule Update code is run, it will crash with what appeared to be a Null Pointer exception.(my jenkins instance is having other issues, which prevent me from extracting the exceptions stack trace at the moment, but once I have it, I will update the bug.). {noformat}java.lang.NullPointerExceptionat hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:133)at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1256)at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748){noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
  

[JIRA] (JENKINS-55978) SSHD Module does not apply Apache Mina idle timeout properly

2019-02-17 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-55978  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSHD Module does not apply Apache Mina idle timeout properly   
 

  
 
 
 
 

 
 Réda Housni Alaoui it has not been backported to 2.150.3, but it will be automatically included into the new LTS baseline - 2.164.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55978) SSHD Module does not apply Apache Mina idle timeout properly

2019-02-17 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55978  
 
 
  SSHD Module does not apply Apache Mina idle timeout properly   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 lts-candidate  sshd  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread inbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Inbar Hachmon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56169  
 
 
  Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
Change By: 
 Inbar Hachmon  
 

  
 
 
 
 

 
 I'm opening this issue in response to the issue:[https://issues.jenkins-ci.org/browse/JENKINS-30317]I understand Daniel Beck's answer, but it still doesn't solve a major issue: how am I supposed to send a file parameter when triggering a build remotely (by an HTTP post request)?When using "/build", I don't get the locatin's url in the response header.when using "/buildWithParameter", I can't send a file parameter.Issue 30317 is from 2015. How is the problem with sending a file parameter when triggering remotely (by an HTTP POST request)  is  still unsolved? 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55978) SSHD Module does not apply Apache Mina idle timeout properly

2019-02-17 Thread alaoui....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Réda Housni Alaoui commented on  JENKINS-55978  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SSHD Module does not apply Apache Mina idle timeout properly   
 

  
 
 
 
 

 
 Hi Oleg, Can this be backported to LTS? I added the lts-candidate to the labels.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55978) SSHD Module does not apply Apache Mina idle timeout properly

2019-02-17 Thread alaoui....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Réda Housni Alaoui updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55978  
 
 
  SSHD Module does not apply Apache Mina idle timeout properly   
 

  
 
 
 
 

 
Change By: 
 Réda Housni Alaoui  
 
 
Labels: 
 lts-candidate sshd  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread inbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Inbar Hachmon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56169  
 
 
  Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
Change By: 
 Inbar Hachmon  
 

  
 
 
 
 

 
 I'm opening this issue in response to the issue:[https://issues.jenkins-ci.org/browse/JENKINS-30317]I understand Daniel  Becker  Beck 's answer, but it still doesn't solve a major issue: how am I supposed to send a file parameter when triggering a build remotely (by an HTTP post request)?When using "/build", I don't get the locatin's url in the response header.when using "/buildWithParameter", I can't send a file parameter.Issue 30317 is from 2015. How is the problem with sending a file parameter when triggering remotely (by an HTTP POST request) is still unsolved?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread inbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Inbar Hachmon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56169  
 
 
  Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
Change By: 
 Inbar Hachmon  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread inbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Inbar Hachmon updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56169  
 
 
  Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
Change By: 
 Inbar Hachmon  
 

  
 
 
 
 

 
 I'm opening this issue in response to the issue:[https://issues.jenkins-ci.org/browse/JENKINS-30317]I understand Daniel Becker's answer, but it still doesn't solve a major issue: how am I supposed to send a file parameter when triggering a build remotely (by an HTTP post request)?When using "/build", I don't get the locatin's url in the response header.when using "/buildWithParameter", I can't send a file parameter.Issue 30317 is from 2015. How is the problem with sending a file parameter when triggering remotely  (by an HTTP POST request)  is still unsolved?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56018) ATH Docker image should not be using Module patches starting from 2.163

2019-02-17 Thread manuelramonleonjime...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramon Leon commented on  JENKINS-56018  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ATH Docker image should not be using Module patches starting from 2.163   
 

  
 
 
 
 

 
 Thank you, we can safely close this task.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56018) ATH Docker image should not be using Module patches starting from 2.163

2019-02-17 Thread manuelramonleonjime...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramon Leon updated  JENKINS-56018  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56018  
 
 
  ATH Docker image should not be using Module patches starting from 2.163   
 

  
 
 
 
 

 
Change By: 
 Ramon Leon  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Done  
 
 
Released As: 
 acceptance-test-harness-1.64  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-56169) Sending a file parameter via remote trigger

2019-02-17 Thread inbar...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Inbar Hachmon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56169  
 
 
  Sending a file parameter via remote trigger   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Beck  
 
 
Components: 
 core  
 
 
Created: 
 2019-02-17 10:16  
 
 
Labels: 
 API build  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Inbar Hachmon  
 

  
 
 
 
 

 
 I'm opening this issue in response to the issue: https://issues.jenkins-ci.org/browse/JENKINS-30317 I understand Daniel Becker's answer, but it still doesn't solve a major issue: how am I supposed to send a file parameter when triggering a build remotely (by an HTTP post request)? When using "/build", I don't get the locatin's url in the response header. when using "/buildWithParameter", I can't send a file parameter. Issue 30317 is from 2015. How is the problem with sending a file parameter when triggering remotely is still unsolved?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  

[JIRA] (JENKINS-31314) Running asynchronous code inside a @NonCPS method should fail cleanly

2019-02-17 Thread yngv...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yngvar Kristiansen commented on  JENKINS-31314  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Running asynchronous code inside a @NonCPS method should fail cleanly   
 

  
 
 
 
 

 
 Any progress on this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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