[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-02 Thread dcher...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmitry Chernivetsky commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
 Nikolas Falco In our case the PR is not from a forked repo.  
 

  
 
 
 
 

 
 
 

 
 
 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-37334) Getting error when i click on the Manage Jenkins --> Configure system

2018-11-02 Thread usha....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 USHA N commented on  JENKINS-37334  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Getting error when i click on the Manage Jenkins --> Configure system
 

  
 
 
 
 

 
 Kindly update on the status of this issue.. I am facing problem in learning things..  
 

  
 
 
 
 

 
 
 

 
 
 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-54380) Private repository authentication

2018-11-02 Thread tisc...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marcos Vallim updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54380  
 
 
  Private repository authentication   
 

  
 
 
 
 

 
Change By: 
 Marcos Vallim  
 
 
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-54432) Cannot use Gerrit as anonymous multi-branch source

2018-11-02 Thread lucamilane...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 lucamilanesio resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54432  
 
 
  Cannot use Gerrit as anonymous multi-branch source
 

  
 
 
 
 

 
Change By: 
 lucamilanesio  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 gerrit-code-review-0.3.2  
 

  
 
 
 
 

 
 
 

 
 
 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-54432) Cannot use Gerrit as anonymous multi-branch source

2018-11-02 Thread lucamilane...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 lucamilanesio started work on  JENKINS-54432  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 lucamilanesio  
 
 
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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3

2018-11-02 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy edited a comment on  JENKINS-54131  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Failed to parse changelog" in JIRA plugin 3.0.3   
 

  
 
 
 
 

 
 [~milkyman] good to hear!! well I made some fixes and need to cut a release early next week.threadExecutorNumber with value 1 is definitely too low if you have multiple jobs using this JiraSite.My bad I think it was a mistake to make this option configurable so easily people will put wrong valuesI need to fix  user  help for this value   
 

  
 
 
 
 

 
 
 

 
 
 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-54432) Cannot use Gerrit as anonymous multi-branch source

2018-11-02 Thread lucamilane...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 lucamilanesio created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54432  
 
 
  Cannot use Gerrit as anonymous multi-branch source
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 lucamilanesio  
 
 
Components: 
 gerrit-code-review-plugin  
 
 
Created: 
 2018-11-03 00:48  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 lucamilanesio  
 

  
 
 
 
 

 
 Since v0.3, the multi-branch pipeline fails when the SCM URL is not associated to any credentials. It was working fine until v0.2.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3

2018-11-02 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy commented on  JENKINS-54131  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Failed to parse changelog" in JIRA plugin 3.0.3   
 

  
 
 
 
 

 
 Horst Krause good to hear!! well I made some fixes and need to cut a release early next week. threadExecutorNumber with value 1 is definitely too low if you have multiple jobs using this JiraSite. My bad I think it was a mistake to make this option configurable so easily people will put wrong values I need to fix help for this value    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-02 Thread nfalc...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
 I will work for a fix at most this monday. Thanks to had shared the job configuration. Just a question, all of you have this issue on pr that does not come from forked repo right?  
 

  
 
 
 
 

 
 
 

 
 
 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-44079) Sharable Libraries class loader "Grabs" to different class loader

2018-11-02 Thread iponoma...@mail.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Ponomarev edited a comment on  JENKINS-44079  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sharable Libraries class loader "Grabs" to different class loader   
 

  
 
 
 
 

 
 Another example:{code:groovy}@Grab('org.asciidoctor:asciidoctorj:1.5. 6 8.1 ')import org.asciidoctor.Asciidoctor{code}AsciiDoctorJ has transitive dependency from{noformat}org.jruby:jruby-complete:9.1.17.0{noformat}However, when I do {code:groovy}import org.jruby.Rubyecho Ruby.globalRuntime.evalScriptlet("JRUBY_VERSION").toString(){code}I see 1.7.3 (no idea where it came from).And this is why I cannot use asciidoctorj:1.5.6 (I get`java.lang.NoSuchMethodError: org.jruby.RubyModule.getMethodLocation()Lorg/jruby/RubyModule;` during initialization: indeed, no such method in JRuby 1.7.3)  
 

  
 
 
 
 

 
 
 

 
 
 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-44079) Sharable Libraries class loader "Grabs" to different class loader

2018-11-02 Thread iponoma...@mail.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Ponomarev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44079  
 
 
  Sharable Libraries class loader "Grabs" to different class loader   
 

  
 
 
 
 

 
Change By: 
 Ivan Ponomarev  
 
 
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-44079) Sharable Libraries class loader "Grabs" to different class loader

2018-11-02 Thread iponoma...@mail.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Ponomarev commented on  JENKINS-44079  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sharable Libraries class loader "Grabs" to different class loader   
 

  
 
 
 
 

 
 Another example: 

 

@Grab('org.asciidoctor:asciidoctorj:1.5.6')
import org.asciidoctor.Asciidoctor
 

 AsciiDoctorJ has transitive dependency from 

 
org.jruby:jruby-complete:9.1.17.0
 

 However, when I do  

 

import org.jruby.Ruby
echo Ruby.globalRuntime.evalScriptlet("JRUBY_VERSION").toString()
 

 I see 1.7.3 (no idea where it came from). And this is why I cannot use asciidoctorj:1.5.6 (I get `java.lang.NoSuchMethodError: org.jruby.RubyModule.getMethodLocation()Lorg/jruby/RubyModule;` during initialization: indeed, no such method in JRuby 1.7.3)  
 

  
 
 
 
 

 
 
 

 
 
 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-54431) Error with Java 11 and jacoco-plugin 3.0.3

2018-11-02 Thread stz.randh...@extaccount.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dirk D. created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54431  
 
 
  Error with Java 11 and jacoco-plugin 3.0.3   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ognjen Bubalo  
 
 
Components: 
 jacoco-plugin  
 
 
Created: 
 2018-11-02 21:59  
 
 
Environment: 
 Jenkins 2.1.49  Jacococ 3.0.3  Java 11  
 
 
Labels: 
 java11 jacoco gradle  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Dirk D.  
 

  
 
 
 
 

 
 Task :test FAILED Exception in thread "main" java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513) at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525) Caused by: java.lang.RuntimeException: Class java/lang/UnknownError could not be instrumented. at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:140) at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:101) at org.jacoco.agent.rt.internal_c13123e.PreMain.createRuntime(PreMain.java:55) at org.jacoco.agent.rt.internal_c13123e.PreMain.premain(PreMain.java:47) ... 6 more Caused by: java.lang.NoSuchFieldException: $jacocoAccess at 

[JIRA] (JENKINS-54354) Jenkins Window slave can not fetch from bitbucket

2018-11-02 Thread xavier.fust...@clarivate.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Xavier Fustero commented on  JENKINS-54354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Window slave can not fetch from bitbucket   
 

  
 
 
 
 

 
 If anyone has the same problem try using jgit instead. Without changing anything on the Windows slave it worked.   
 

  
 
 
 
 

 
 
 

 
 
 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-53741) java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-53741  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable   
 

  
 
 
 
 

 
 Priyabrata Dhal I am not sure what is your question to me about. Could you please clarifhy?  
 

  
 
 
 
 

 
 
 

 
 
 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-54427) support other containers

2018-11-02 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-54427  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: support other containers   
 

  
 
 
 
 

 
 Or we could improve the kubernetes plugin to use a different launch method, say based on the WebSocket underlying kubectl exec, rather than using the JNLP connector. Then there is no need for the jenkinsfile-runner container to expose any ports at all. At any rate, James Strachan should understand that in the currently working versions of this, it does not look like the example given in the issue description. Rather, no sh steps may be run in the jenkinsfile-runner container (we set the numExecutors: 0 to emphasize this), and to do any work you use the podTemplate step which launches a separate pod, inside of which you may use node with a label to select the container for the slave.jar, and then container to actually use the desired container. The resulting Pipeline script is rather cumbersome, and the scheduling is inefficient, which is why I would like to deprecate this whole system and introduce an alternative direct-launch step akin to dockerNode in docker-plugin but creating a single-container pod instead.  
 

  
 
 
 
 

 
 
 

 
 
 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-38305) Remove --tty from docker exec

2018-11-02 Thread keith.derr...@lge.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Derrick commented on  JENKINS-38305  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove --tty from docker exec   
 

  
 
 
 
 

 
 The best solution would be to provide an option (per job) to disable provision of --tty  
 

  
 
 
 
 

 
 
 

 
 
 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-38305) Remove --tty from docker exec

2018-11-02 Thread keith.derr...@lge.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Derrick commented on  JENKINS-38305  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove --tty from docker exec   
 

  
 
 
 
 

 
 Any action on this?  Supplying --tty makes it impossible to run repo inside a containerized job.  
 

  
 
 
 
 

 
 
 

 
 
 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-44930) Allow sh to return exit status, stdout and stderr all at once

2018-11-02 Thread fnas...@redhat.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fernando Nasser edited a comment on  JENKINS-44930  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow sh to return exit status, stdout and stderr all at once   
 

  
 
 
 
 

 
 Simple solution, create a returnStderr: trueAs the empty String (i.e., nothing in stderr) would mean false, it would indicate "no errors"If it is not empty, one not only knows it failed but also knows WHY it failed.  {code:java} String status = sh(returnStderr: true, script: "git merge --no-edit $branches > merge_output.txt")  if (status) {  currentBuild.result = 'FAILED'    def output = readFile('merge_output.txt').trim()  slackSend channel: SLACK_CHANNEL, message: "<${env.JOB_URL}|${env.JOB_NAME}> ran into an error merging the PR branches into the ${TARGET_BRANCH} branch:\n```\n${output}\n```\n<${env.BUILD_URL}/console|See the full output>", color: 'warning', tokenCredentialId: 'slack-token'    error status  }sh 'rm merge_output.txt' {code}  
 

  
 
 
 
 

 
 
 

 
 
 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-44930) Allow sh to return exit status, stdout and stderr all at once

2018-11-02 Thread fnas...@redhat.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fernando Nasser commented on  JENKINS-44930  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow sh to return exit status, stdout and stderr all at once   
 

  
 
 
 
 

 
 Simple solution, create a returnStderr: true As the empty String (i.e., nothing in stderr) would mean false, it would indicate "no errors" If it is not empty, one not only knows it failed but also knows WHY it failed.   String status = sh(returnStderr: true, script: "git merge --no-edit $branches > merge_output.txt")if (status) { currentBuild.result = 'FAILED' def output = readFile('merge_output.txt').trim() slackSend channel: SLACK_CHANNEL, message: "<${env.JOB_URL}|${env.JOB_NAME}> ran into an error merging the PR branches into the ${TARGET_BRANCH} branch:\n```\n${output}\n```\n<${env.BUILD_URL}/console|See the full output>", color: 'warning', tokenCredentialId: 'slack-token' error status} sh 'rm merge_output.txt'  
 

  
 
 
 
 

 
 
 

 
 
 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-48850) Random java.io.IOException: Unexpected termination of the channel

2018-11-02 Thread jthomp...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-48850  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Random java.io.IOException: Unexpected termination of the channel   
 

  
 
 
 
 

 
 Andrew Marlow, a lot of people have good success keeping channels alive over many builds or long builds. Certainly there are also a number of cases where people have reliability problems for a wide variety of reasons. Sometimes they're able to stabilize or strengthen their environment and these problems disappear. Most of the times they don't provide enough information for anyone who isn't local to diagnose anything. There isn't much reason to keep multiple, duplicate tickets open that all lack information or continued response. With your acknowledged network unreliability, you may also want to give the remoting-kafka-plugin a try. I'd suggest running a test build environment or trying it with a few jobs. One of the reasons for creating the new plugin was a hope for improved reliability. Your unreliable network may be a good test case for that. My network is pretty reliable so I can't reproduce any of these reports or give a good workout to the remoting-kafka-plugin.  
 

  
 
 
 
 

 
 
 

 
 
 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-54399) Configuration page no longer loads

2018-11-02 Thread crai...@tataryn.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Tataryn commented on  JENKINS-54399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configuration page no longer loads   
 

  
 
 
 
 

 
 Updating to Config File Provider Plugin 3.4.1 fixed this for me as well.  
 

  
 
 
 
 

 
 
 

 
 
 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-48850) Random java.io.IOException: Unexpected termination of the channel

2018-11-02 Thread jthomp...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-48850  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Random java.io.IOException: Unexpected termination of the channel   
 

  
 
 
 
 

 
 Federico Naum, I've noticed a number of different comments or cases that suggest there might be more connection problems with more parallel builds. It would be nice to be able to pin that down to something but so far I've seen nothing indicating the source. I'm really interested in hearing your results with the remoting-kafka-plugin. It reuses many of the capabilities and concepts of the primary Remoting module but routes the communication over Kafka channels instead of over Jenkins Remoting specific ones. It's clear there are some reliability issues with the standard channels. The logic around disconnects, reconnects, and retries is not as strong as it needs to be. I doubt it's worth putting a lot of energy into strengthening the existing channel implementations, unless we can isolate specific situations. The remoting-kafka-plugin or something else similar seems a lot more promising for these reliability efforts. It would be great to more results from the remoting-kafka-plugin and see how it holds up in these production environments. If we could see it makes noticeable improvements in a number of these cases that would give confidence for shifting efforts that way.  
 

  
 
 
 
 

 
 
 

 
 
 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-47882) Unable to connect MongoDB with MONGODB-CR authentication

2018-11-02 Thread timjaco...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Jacomb edited a comment on  JENKINS-47882  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect MongoDB with MONGODB-CR authentication
 

  
 
 
 
 

 
 Branch here that can be tested out:https://github.com/jenkinsci/build-failure-analyzer-plugin/compare/master...timja:upgrade-minimal-changesAs far as I can tell it works,I'm currently working on test failures WIP PR:https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/89  
 

  
 
 
 
 

 
 
 

 
 
 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-54430) Build Job Changes render incorrectly, transforming Jira issue URLs into text instead of links

2018-11-02 Thread migor...@aol.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aaron Sylvia created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54430  
 
 
  Build Job Changes render incorrectly, transforming Jira issue URLs into text instead of links   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 redsolo  
 
 
Attachments: 
 image-2018-11-02-14-48-47-254.png  
 
 
Components: 
 tfs-plugin  
 
 
Created: 
 2018-11-02 18:49  
 
 
Environment: 
 Jenkins 2.89.4  TFS Plug-In 5.133.0  Jira Plugin 2.5  
 
 
Labels: 
 jira tfs-plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Aaron Sylvia  
 

  
 
 
 
 

 
 Jira sends urls as HTML DOM node strings:  https://github.com/jenkinsci/jira-plugin/blob/master/src/main/java/hudson/plugins/jira/JiraChangeLogAnnotator.java lines 116-121. The TFS Plug-In filters the HTML special characters and escapes them:  https://github.com/jenkinsci/tfs-plugin/blob/master/tfs/src/main/java/hudson/plugins/tfs/ChangeSetWriter.java within the escapeForXml method. The links appear as text instead of links:     
 

  
 
 
 
 

 
 
 
  

[JIRA] (JENKINS-47882) Unable to connect MongoDB with MONGODB-CR authentication

2018-11-02 Thread timjaco...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Jacomb commented on  JENKINS-47882  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect MongoDB with MONGODB-CR authentication
 

  
 
 
 
 

 
 Branch here that can be tested out: https://github.com/jenkinsci/build-failure-analyzer-plugin/compare/master...timja:upgrade-minimal-changes As far as I can tell it works, I'm currently working on test failures  
 

  
 
 
 
 

 
 
 

 
 
 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-47882) Unable to connect MongoDB with MONGODB-CR authentication

2018-11-02 Thread timjaco...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Jacomb assigned an issue to Tim Jacomb  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47882  
 
 
  Unable to connect MongoDB with MONGODB-CR authentication
 

  
 
 
 
 

 
Change By: 
 Tim Jacomb  
 
 
Assignee: 
 Tomas Westling Tim Jacomb  
 

  
 
 
 
 

 
 
 

 
 
 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-47882) Unable to connect MongoDB with MONGODB-CR authentication

2018-11-02 Thread timjaco...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Jacomb started work on  JENKINS-47882  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Tim Jacomb  
 
 
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-54429) Replay feature should not store non-stored password parameter

2018-11-02 Thread billmor...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bill Moritz created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54429  
 
 
  Replay feature should not store non-stored password parameter   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2018-11-02 17:55  
 
 
Labels: 
 security replay  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Bill Moritz  
 

  
 
 
 
 

 
 The replay feature allows the replay of jobs with nonStoredPassword parameters. This means it must be storing the values somewhere.  I would expect the parameter to not be stored and have that parameter field available during the job replay editor screen.   CloudBees Jenkins Enterprise 2.138.1.2-rolling Pipeline plugin 2.59  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
   

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

2018-11-02 Thread dant...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 dan tran assigned an issue to Joseph Petersen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54331  
 
 
  Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13   
 

  
 
 
 
 

 
Change By: 
 dan tran  
 
 
Assignee: 
 Joseph Petersen  
 

  
 
 
 
 

 
 
 

 
 
 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-30211) Installation error: Could not initialize class com.sun.jna.Pointer

2018-11-02 Thread chin.bi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 chin ho commented on  JENKINS-30211  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Installation error: Could not initialize class com.sun.jna.Pointer   
 

  
 
 
 
 

 
 I had the same issue and I was able to fix it by running jenkins like this (in elevated CMD window): java "-Djna.nosys=true" -jar jenkins.war then Jenkins was able to install as a service. Also I added that system property to the jenkins.xml file like this: -Xrs -Xmx1536m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -Djna.nosys=true -jar "%BASE%\jenkins.war" --httpPort=8080 --webroot="%BASE%\war"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-02 Thread dcher...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmitry Chernivetsky edited a comment on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
 I can confirm this bug.All PR branches are failing to build.Environment:Bitbucket server  v4.12.0Latest jenkins with latest plugins, Bitbucket branch source plugin  [ 2.2.14 |https://gcp-nonprod-jenkins01.it.jetblue.com/pluginManager/plugin/cloudbees-bitbucket-branch-source/thirdPartyLicenses] Multibranch pipeline is autocreated from Bitbucket team/project. Nothing really special about configuration. Screenshot attached.!image-2018-11-02-00-43-19-214.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-54412) Testng Plugin should have capability to save the reports in

2018-11-02 Thread ratsa...@adobe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rati Saxena commented on  JENKINS-54412  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Testng Plugin should have capability to save the reports in
 

  
 
 
 
 

 
 Nalin Makar any update/suggestion 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.


[JIRA] (JENKINS-54275) (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old

2018-11-02 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-54275  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old   
 

  
 
 
 
 

 
 No worries, if I have to test it to guess the problem and remember the solution, it means that it is not well manage, I added the exception to the troubleshooting guide, now it will redirect to the logout page configured, if there is not logout page configured redirect you to a logout page that advise to contact to the admin to check the log error and point him to the troubleshooting guide.  
 

  
 
 
 
 

 
 
 

 
 
 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-54275) (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old

2018-11-02 Thread t...@belodetek.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anton Belodedenko commented on  JENKINS-54275  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old   
 

  
 
 
 
 

 
 OK, we've set Maximum Authentication Lifetime: 1209600 and it's working now with Google Apps. Thanks for your help! Probably could have worked this out myself   
 

  
 
 
 
 

 
 
 

 
 
 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-53741) java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable

2018-11-02 Thread priyabrata.d...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Priyabrata Dhal commented on  JENKINS-53741  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.ClassCastException: java.lang.Integer cannot be cast to hudson.model.Describable   
 

  
 
 
 
 

 
 Hi Sashikant,   Did this issue resolved?I have also got similar issues in my jenkins upgradation from 2.75 to 2.138.2. Could you please help me the steps if you resolved this.   Hi Oleg,   Can you please let me know if any compatibility issues in plugins?   Regards, Priyab  
 

  
 
 
 
 

 
 
 

 
 
 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-54427) support other containers

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54427  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: support other containers   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/remoting/pull/286  is probably a prerequisite  
 

  
 
 
 
 

 
 
 

 
 
 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-54027) ID analysis is already used by another action

2018-11-02 Thread brian.murr...@intel.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-54027  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ID analysis is already used by another action   
 

  
 
 
 
 

 
 I think I am confusing myself.  From https://updates.jenkins.io/experimental/update-center.json, I see: 

 
"warnings": {
"buildDate": "Oct 31, 2018",
"dependencies": [
{
"name": "warnings-ng",
"optional": false,
"version": "1.0.0-beta1"
},
{
"name": "maven-plugin",
"optional": false,
"version": "3.1.2"
},
{
"name": "workflow-job",
"optional": false,
"version": "2.16"
},
{
"name": "workflow-step-api",
"optional": false,
"version": "2.13"
},
{
"name": "antisamy-markup-formatter",
"optional": false,
"version": "1.5"
},
{
"name": "dashboard-view",
"optional": true,
"version": "2.9.11"
},
{
"name": "git",
"optional": true,
"version": "3.9.1"
},
{
"name": "matrix-project",
"optional": true,
"version": "1.13"
},
{
"name": "structs",
"optional": false,
"version": "1.10"
},
{
"name": "token-macro",
"optional": true,
"version": "2.5"
},
{
"name": "analysis-core",
"optional": false,
"version": "1.95"
}
],
"developers": [
{
"developerId": "hafner"
}
],
"excerpt": "(This version is experimental and may change in backward-incompatible ways)The Warnings plug-in reached end-of-life. All functionality has been integrated into the Warnings Next Generation Plugin.",
"gav": "org.jvnet.hudson.plugins:warnings:5.0.0-beta4",
"labels": [
"maven",
"report"
],
"name": "warnings",
"previousTimestamp": "2018-10-03T21:35:03.00Z",
"previousVersion": "5.0.0-beta3",
"releaseTimestamp": "2018-10-31T13:38:32.00Z",
"requiredCore": "2.89.1",
"scm": "https://github.com/jenkinsci/warnings-plugin",
"sha1": "uIwuyadciRiIez4KJO2ezNDmzMM=",
"sha256": "vRkifo4osQv/CBBpl2GmOEGcRfnBp0Rk5/T7i46l3JM=",
"title": "Warnings",
"url": "http://updates.jenkins-ci.org/download/plugins/warnings/5.0.0-beta4/warnings.hpi",
"version": "5.0.0-beta4",
"wiki": "https://plugins.jenkins.io/warnings"
},
"warnings-ng": {
"buildDate": "Nov 02, 2018",
"dependencies": [
{
"name": "workflow-job",
"optional": false,
"version": "2.16"
},
{
"name": "workflow-step-api",
"optional": false,
"version": "2.13"
},
{
"name": "analysis-model-api",
"optional": false,
"version": "1.0.0-beta10"
},
{
"name": "antisamy-markup-formatter",
"optional": false,
"version": "1.5"
},
{
"name": "git",
"optional": true,
"version": "3.9.1"
},
{
"name": "matrix-project",
"optional": true,
"version": "1.13"
},
{
"name": "structs",
"optional": false,
"version": "1.10"
},
{
"name": "token-macro",
"optional": true,
"version": "2.5"
}
],
"developers": [
{
"developerId": "hafner"
}
],
"excerpt": "(This version is experimental and may change in backward-incompatible ways)This plugin collects compiler warnings or issues reported by static analysis tools and visualizes the results. It has built-in support for numerous static analysis tools (including several compilers), see the list of supported report formats.",
"gav": "io.jenkins.plugins:warnings-ng:1.0.0-beta3",
"labels": [],
"name": "warnings-ng",
"previousTimestamp": "2018-11-01T12:11:10.00Z",
"previousVersion": "1.0.0-beta2",
"releaseTimestamp": "2018-11-02T00:27:36.00Z",
"requiredCore": "2.89.1",
"scm": "https://github.com/jenkinsci/warnings-ng-plugin",
"sha1": "Pt0LsnQYmt3zRpOvB9lSaxFl3Xk=",
"sha256": "fITQ2cYE+0m6JzdBDRQ311qfNGjodB5HbjILiXgxPz4=",
"title": "Warnings Next Generation",
"url": "http://updates.jenkins-ci.org/download/plugins/warnings-ng/1.0.0-beta3/warnings-ng.hpi",
"version": "1.0.0-beta3",
"wiki": "https://plugins.jenkins.io/warnings-ng"
},
 
   

[JIRA] (JENKINS-54027) ID analysis is already used by another action

2018-11-02 Thread brian.murr...@intel.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54027  
 
 
  ID analysis is already used by another action   
 

  
 
 
 
 

 
Change By: 
 Brian J Murrell  
 
 
Attachment: 
 Screenshot from 2018-11-02 10-54-43.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-54428) ECS plugin fails if task definition ARN is used

2018-11-02 Thread stef...@conversocial.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefano Pogliani updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54428  
 
 
  ECS plugin fails if task definition ARN is used
 

  
 
 
 
 

 
Change By: 
 Stefano Pogliani  
 
 
Priority: 
 Blocker 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-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free

2018-11-02 Thread benoit.gue...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 benoit guerin commented on  JENKINS-54305  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free   
 

  
 
 
 
 

 
 Thanks Devin Nusbaum will try   
 

  
 
 
 
 

 
 
 

 
 
 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-54428) ECS plugin fails if task definition ARN is used

2018-11-02 Thread stef...@conversocial.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefano Pogliani created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54428  
 
 
  ECS plugin fails if task definition ARN is used
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jan Roehrich  
 
 
Components: 
 amazon-ecs-plugin  
 
 
Created: 
 2018-11-02 14:50  
 
 
Environment: 
 Docker Jenkins LTS 2.138.2 with Amazon ECS Plugin 1.17  The ECS cloud is configured to use a Task Definition ARN and not to create the task definition for us  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Stefano Pogliani  
 

  
 
 
 
 

 
 After upgrading the Amazon ECS plugin from 1.16 to 1.17 all ECS slaves fail to start with the exception below: 

 
Nov 02, 2018 1:55:28 PM hudson.slaves.NodeProvisioner$2 run
WARNING: Unexpected exception encountered while provisioning agent ECS Slave ecs-agent
java.lang.NullPointerException
at com.cloudbees.jenkins.plugins.amazonecs.ECSService.runEcsTask(ECSService.java:303)
at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:278)
at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:227)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
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)
 

 

[JIRA] (JENKINS-54355) ClassNotFound: java.sql.Date in JDK 11

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54355  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ClassNotFound: java.sql.Date in JDK 11   
 

  
 
 
 
 

 
 And http://java9.wtf/class-loading/ ...  
 

  
 
 
 
 

 
 
 

 
 
 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-54426) Jenkinsfile Runner fails on Java 11

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54426  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkinsfile Runner fails on Java 11   
 

  
 
 
 
 

 
 So, see http://java9.wtf/class-loading/   
 

  
 
 
 
 

 
 
 

 
 
 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-10986) Symlinks in a shelved project are archived as directories on Unix platforms

2018-11-02 Thread valentin.bara...@netcracker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Baranov commented on  JENKINS-10986  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Symlinks in a shelved project are archived as directories on Unix platforms   
 

  
 
 
 
 

 
 Hi guys. When can we expect this fix to be released? We extremely need it  
 

  
 
 
 
 

 
 
 

 
 
 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-54426) Jenkinsfile Runner fails on Java 11

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54426  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkinsfile Runner fails on Java 11   
 

  
 
 
 
 

 
 Likely it's caused by https://bugs.openjdk.java.net/browse/JDK-8161269  
 

  
 
 
 
 

 
 
 

 
 
 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-54355) ClassNotFound: java.sql.Date in JDK 11

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54355  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ClassNotFound: java.sql.Date in JDK 11   
 

  
 
 
 
 

 
 FTR https://bugs.openjdk.java.net/browse/JDK-8161269    
 

  
 
 
 
 

 
 
 

 
 
 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-54426) Jenkinsfile Runner fails on Java 11

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54426  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkinsfile Runner fails on Java 11   
 

  
 
 
 
 

 
 Same as JENKINS-54355 ?  
 

  
 
 
 
 

 
 
 

 
 
 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-54427) support other containers

2018-11-02 Thread james.strac...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Strachan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54427  
 
 
  support other containers   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 jenkinsfile-runner  
 
 
Created: 
 2018-11-02 14:23  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Strachan  
 

  
 
 
 
 

 
 When using jenkinsfile-runner inside Kubernetes such as with Prow/Knative Build in Jenkins X it would be awesome to be able to replicate the kubernetes-plugin style execution of commands in sidecars all from within the exact same pod. e.g.   

 

sh "echo this runs in the same container as the jenkinsfile runner"
container("selenium") {
   sh "echo this runs in the selenium container"
}  

 When using pure knative build steps this stuff all works already; but its not yet supported in a Jenkinsfile. I understand that the jenkinsfile runner is just 1 container that runs & isn't gonna be able to grok the sidecar containers - but thats fine - we can configure that stuff outside of the jenkisnfile + jenksinfile-runner - but it'd be nice to be able to execute commands in sidecar containers (e.g. via the shell command: 

 

kubectl exec -it $HOSTNAME -c selenium -- echo "this runs in the selenium continaer"  

      
 

  
 
 
 

[JIRA] (JENKINS-54426) Jenkinsfile Runner fails on Java 11

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54426  
 
 
  Jenkinsfile Runner fails on Java 11   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 java11  
 

  
 
 
 
 

 
 
 

 
 
 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-54426) Jenkinsfile Runner fails on Java 11

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54426  
 
 
  Jenkinsfile Runner fails on Java 11   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 jenkinsfile-runner  
 
 
Created: 
 2018-11-02 14:22  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 

 

java.lang.NoClassDefFoundError: java.sql.Date at org.apache.commons.beanutils.ConvertUtilsBean.class$(ConvertUtilsBean.java:157) at org.apache.commons.beanutils.ConvertUtilsBean.registerOther(ConvertUtilsBean.java:708) at org.apache.commons.beanutils.ConvertUtilsBean.deregister(ConvertUtilsBean.java:580) at org.apache.commons.beanutils.ConvertUtilsBean.(ConvertUtilsBean.java:164) at org.kohsuke.stapler.Stapler.(Stapler.java:1065) at hudson.model.Node$Mode.(Node.java:597) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.base/java.lang.Class.getEnumConstantsShared(Class.java:3554) at java.base/java.lang.Class.getEnumConstants(Class.java:3530) at jenkins.model.Jenkins.(Jenkins.java:5191) at hudson.ExtensionList.lookup(ExtensionList.java:432) at hudson.model.User.clear(User.java:717) at io.jenkins.jenkinsfile.runner.JenkinsRule.before(JenkinsRule.java:251) at io.jenkins.jenkinsfile.runner.JenkinsfileRunnerRule.before(JenkinsfileRunnerRule.java:76) at io.jenkins.jenkinsfile.runner.JenkinsfileRunnerRule$1.evaluate(JenkinsfileRunnerRule.java:113) at io.jenkins.jenkinsfile.runner.App.run(App.java:32) at io.jenkins.jenkinsfile.runner.bootstrap.Bootstrap.run(Bootstrap.java:166) at 

[JIRA] (JENKINS-54424) Jenkinsfile Runner: Stop using Jenkins Test Harness dependency

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated  JENKINS-54424  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54424  
 
 
  Jenkinsfile Runner: Stop using Jenkins Test Harness dependency   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
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-54275) (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old

2018-11-02 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-54275  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old   
 

  
 
 
 
 

 
 I am working on a way to report this in the UI on a way that points to a solution.  In your case, you have to set the Maximum Authentication Lifetime to 14 days as you have configured in your Idp, if not, the token is still valid and Jenkins do not accept it because is configured to do not. Maximum Authentication Lifetime: 1209600  
 

  
 
 
 
 

 
 
 

 
 
 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-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free

2018-11-02 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-54305  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free   
 

  
 
 
 
 

 
 
 
Here I am a little bit lost ... For the crawler, can I open a PR on it ? It is Jenkins own INFRA, not (directly) used by jenkins installations. And about weird distribution policies, what is the problem ? If we fix the plugin to supports JDK 11, it is ok or not ?
 Yep, the crawler runs on Jenkins Infra, and it publishes this file, which is then downloaded by Jenkins instances which use it to know what JDK versions are available and what their download URLs are. I think you should be fine to open a PR against the crawler, although you would likely need to synchronize it with a PR to https://github.com/jenkinsci/jdk-tool-plugin, and depending on the changes required you might need to publish a new file instead of the old one so compatibility with old instances is not broken (for example if you switch to AdoptOpenJDK).  
 

  
 
 
 
 

 
 
 

 
 
 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-54425) "update plugin to a version created with a newer harness" warnings in the default STDOUT

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54425  
 
 
  "update plugin to a version created with a newer harness" warnings in the default STDOUT   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 jenkinsfile-runner  
 
 
Created: 
 2018-11-02 13:57  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 Example: 

 

docker run --rm -v /Users/nenashev/Documents/jenkins/tools/jenkinsfile-runner/demo/cwp/Jenkinsfile:/workspace/Jenkinsfile \
	jenkins-experimental/jenkinsfile-runner-demo
   2.731 [id=27]	WARNING	hudson.ClassicPluginStrategy#createClassJarFromWebInfClasses: Created /usr/share/jenkins/ref/plugins/authentication-tokens/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
   2.792 [id=27]	WARNING	hudson.ClassicPluginStrategy#createClassJarFromWebInfClasses: Created /usr/share/jenkins/ref/plugins/icon-shim/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
   2.957 [id=24]	WARNING	hudson.ClassicPluginStrategy#createClassJarFromWebInfClasses: Created /usr/share/jenkins/ref/plugins/git-server/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
Started
Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] stage
 

 These warnings are OK for the build-time, but they should not be displayed in the production runs IMO  
 

  
 
 
 
 


[JIRA] (JENKINS-54424) Jenkinsfile Runner: Stop using Jenkins Test Harness dependency

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev started work on  JENKINS-54424  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
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-54424) Jenkinsfile Runner: Stop using Jenkins Test Harness dependency

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54424  
 
 
  Jenkinsfile Runner: Stop using Jenkins Test Harness dependency   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 jenkinsfile-runner  
 
 
Created: 
 2018-11-02 13:54  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 Jenkins Test Harness is not a production-ready codebase. It must not be used in Jenkins X Serverless and in other use-cases for Jenkinsfile Runner  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira 

[JIRA] (JENKINS-54415) jep-200 issue w/ matrix reloaded plugin

2018-11-02 Thread m...@praqma.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mads Nielsen commented on  JENKINS-54415  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jep-200 issue w/ matrix reloaded plugin   
 

  
 
 
 
 

 
 I have started work on this on the branch JENKINS-54415. The only thing that is serialized in that class is the AbstractBuild which we do not need to serialize.  https://github.com/jenkinsci/matrix-reloaded-plugin/tree/JENKINS-54415 But yes...this plugin probably could use a new maintainer  
 

  
 
 
 
 

 
 
 

 
 
 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-52463) Each SonarQube parser should skip files of other SonarQube parsers

2018-11-02 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated  JENKINS-52463  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52463  
 
 
  Each SonarQube parser should skip files of other SonarQube parsers   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-54409) It doesn;t like my password

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54409  
 
 
  It doesn;t like my password   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 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-54409) It doesn;t like my password

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54409  
 
 
  It doesn;t like my password   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 core  
 
 
Component/s: 
 _unsorted  
 

  
 
 
 
 

 
 
 

 
 
 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-54409) It doesn;t like my password

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54409  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: It doesn;t like my password   
 

  
 
 
 
 

 
 I assume it is related to the core according to the stacktrace  
 

  
 
 
 
 

 
 
 

 
 
 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-54405) New Relic Deployment Notifier Plugin fails to notify New Relic of Deployment

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54405  
 
 
  New Relic Deployment Notifier Plugin fails to notify New Relic of Deployment   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 newrelic-deployment-notifier-plugin  
 
 
Component/s: 
 _unsorted  
 

  
 
 
 
 

 
 
 

 
 
 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-54405) New Relic Deployment Notifier Plugin fails to notify New Relic of Deployment

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54405  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New Relic Deployment Notifier Plugin fails to notify New Relic of Deployment   
 

  
 
 
 
 

 
 Due to whatever reason, there was no component in JIRA  
 

  
 
 
 
 

 
 
 

 
 
 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-54405) New Relic Deployment Notifier Plugin fails to notify New Relic of Deployment

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Mads Mohr Christensen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54405  
 
 
  New Relic Deployment Notifier Plugin fails to notify New Relic of Deployment   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev Mads Mohr Christensen  
 

  
 
 
 
 

 
 
 

 
 
 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-47631) Plugin cannot access SV project on Jenkins slave

2018-11-02 Thread gunjapraveenku...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Praveen Gunja updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47631  
 
 
  Plugin cannot access SV project on Jenkins slave   
 

  
 
 
 
 

 
Change By: 
 Praveen Gunja  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

 
 
 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3

2018-11-02 Thread milky...@web.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Horst Krause commented on  JENKINS-54131  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Failed to parse changelog" in JIRA plugin 3.0.3   
 

  
 
 
 
 

 
 I had already threadExecutorNumber with value 1 in the config value. This did not work. I stopped jenkins and changed this to the proposed 10. This did not work too. But perhaps your hint about the readTimeout helped. It was set to 0 in the config. I changed it to 30 and now everything seems to work.  
 

  
 
 
 
 

 
 
 

 
 
 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-47631) Plugin cannot access SV project on Jenkins slave

2018-11-02 Thread gunjapraveenku...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Praveen Gunja edited a comment on  JENKINS-47631  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plugin cannot access SV project on Jenkins slave   
 

  
 
 
 
 

 
 *+version of the plugin+*5.5 Micro Focus Application Automation Tools with HPSV 4.10 Similar issue here , if not please let me know , i can log a new issue.*Export step - Exporting of a virtual asset in both archive(.vproja) and non archive formats(.vproj and datamodels in one folder) is not working.**+Steps to reproduce:+*Configure master and slave model of jenkinsEnsure on the slave the jenkins service user is having the proper rights to create the folderconfigure jenkins to execute the svexportstep on the slave node(here the master is on linux env and the slave is of windows)check if the export of the asset is done to the workspace of the job in the slave or any other folder as it is configured!image-2018-11-02-14-20-46-786.png!+*Expected:*+ virtual asset should be exported from the cenrtal server of HPSV to the slaves workspace/any given folder in the slave +*Actual:*+Please see below errornote: SVN checkout is to workspace is okay(including folders) so we do not think it is access related on the slave. !image-2018-11-02-14-20-32-052.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-47631) Plugin cannot access SV project on Jenkins slave

2018-11-02 Thread gunjapraveenku...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Praveen Gunja commented on  JENKINS-47631  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plugin cannot access SV project on Jenkins slave   
 

  
 
 
 
 

 
 Similar issue here , if not please let me know , i can log a new issue. Export step - Exporting of a virtual asset in both archive(.vproja) and non archive formats(.vproj and datamodels in one folder) is not working. Steps to reproduce: Configure master and slave model of jenkins Ensure on the slave the jenkins service user is having the proper rights to create the folder configure jenkins to execute the svexportstep on the slave node (here the master is on linux env and the slave is of windows) check if the export of the asset is done to the workspace of the job in the slave or any other folder as it is configured  Expected: virtual asset should be exported from the cenrtal server of HPSV to the slaves workspace/any given folder in the slave   Actual: Please see below error note: SVN checkout is to workspace is okay(including folders) so we do not think it is access related on the slave.     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-02 Thread aavind...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Avindra Goolcharan commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
 Confirmed that downgrading "Bitbucket Branch Source" to 2.2.13 fixes it.   2.2.14 is the broken revision   
 

  
 
 
 
 

 
 
 

 
 
 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-47631) Plugin cannot access SV project on Jenkins slave

2018-11-02 Thread gunjapraveenku...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Praveen Gunja updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47631  
 
 
  Plugin cannot access SV project on Jenkins slave   
 

  
 
 
 
 

 
Change By: 
 Praveen Gunja  
 
 
Attachment: 
 image-2018-11-02-14-20-32-052.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-47631) Plugin cannot access SV project on Jenkins slave

2018-11-02 Thread gunjapraveenku...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Praveen Gunja updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47631  
 
 
  Plugin cannot access SV project on Jenkins slave   
 

  
 
 
 
 

 
Change By: 
 Praveen Gunja  
 
 
Attachment: 
 image-2018-11-02-14-20-46-786.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-54275) (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old

2018-11-02 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-54275  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old   
 

  
 
 
 
 

 
 Finally, I replicated the issue, I am taking a look, with a SAML token valid for 14 days, a session of 60 seconds and an authentication lifetime of 5 min, I have to wait more than 10 min to see the issue   
 

  
 
 
 
 

 
 
 

 
 
 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-54415) jep-200 issue w/ matrix reloaded plugin

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


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54415  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jep-200 issue w/ matrix reloaded plugin   
 

  
 
 
 
 

 
 Fyi Ewelina Wilkosz. Not sure Praqma still maintains it  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-02 Thread aavind...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Avindra Goolcharan commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
 In the same boat. Are there any workarounds? Some of our builds seem to be working...  
 

  
 
 
 
 

 
 
 

 
 
 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-54423) Masked passwords are not masked in 'Pipeline Steps'

2018-11-02 Thread mksmelni...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maksim Melnikov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54423  
 
 
  Masked passwords are not masked in 'Pipeline Steps'   
 

  
 
 
 
 

 
Change By: 
 Maksim Melnikov  
 

  
 
 
 
 

 
 Hey. I use mask-password-plugin in my pipeline to hide user input password for svn checkout:{code:java}String password = userInput['svnPassword'] wrap([$class: 'MaskPasswordsBuildWrapper', varPasswordPairs: [[password: password, var: 'pass']]]) {    sh "svn checkout --username $user --password $password $url $projectDir" }{code}Console output is okay, there is a masked password: {code:java}// svn checkout --username someuser --password  https://svn.site/some-repo project {code} But I see the full shell command in 'Pipeline Steps' Menu with password entered. See attach.I do not know any other way to get password from input and hide it.  
 

  
 
 
 
 

 
 
 

 
 
 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-54423) Masked passwords are not masked in 'Pipeline Steps'

2018-11-02 Thread mksmelni...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maksim Melnikov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54423  
 
 
  Masked passwords are not masked in 'Pipeline Steps'   
 

  
 
 
 
 

 
Change By: 
 Maksim Melnikov  
 

  
 
 
 
 

 
 Hey. I use mask-password-plugin in my pipeline to hide user input password for svn checkout:{code:java}String password = userInput['svnPassword'] wrap([$class: 'MaskPasswordsBuildWrapper', varPasswordPairs: [[password: password, var: 'pass']]]) {    sh "svn checkout --username $user --password $password $url $projectDir" }{code}Console output is okay, there is a masked password:{code:java} //  svn checkout --username someuser --password  https://svn.site/some-repo project{code}But I see the full shell command in 'Pipeline Steps' Menu with password entered. See attach.I do not know any other way to get password from input and hide it.  
 

  
 
 
 
 

 
 
 

 
 
 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-54423) Masked passwords are not masked in 'Pipeline Steps'

2018-11-02 Thread mksmelni...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maksim Melnikov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54423  
 
 
  Masked passwords are not masked in 'Pipeline Steps'   
 

  
 
 
 
 

 
Change By: 
 Maksim Melnikov  
 

  
 
 
 
 

 
 Hey. I use mask-password-plugin in my pipeline to hide user input password for svn checkout:{code:java}String password = userInput['svnPassword'] wrap([$class: 'MaskPasswordsBuildWrapper', varPasswordPairs: [[password: password, var: 'pass']]]) {    sh "svn checkout --username $user --password $password $url $projectDir" }{code}Console output is okay, there is  a  masked password :svn checkout --username someuser --password  https://svn . site/some-repo project  But I see the full shell command in 'Pipeline Steps' Menu with password entered. See attach.I do not know any other way to get password from input and hide it.  
 

  
 
 
 
 

 
 
 

 
 
 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-54333) Projects are triggered twice by "build with parameters"

2018-11-02 Thread martin.moess...@coop.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Mössner commented on  JENKINS-54333  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Projects are triggered twice by "build with parameters"   
 

  
 
 
 
 

 
 Yes, the steps are correct.  
 

  
 
 
 
 

 
 
 

 
 
 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-54423) Masked passwords are not masked in 'Pipeline Steps'

2018-11-02 Thread mksmelni...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maksim Melnikov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54423  
 
 
  Masked passwords are not masked in 'Pipeline Steps'   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Screenshot from 2018-11-02 15-55-24.png  
 
 
Components: 
 mask-passwords-plugin  
 
 
Created: 
 2018-11-02 12:56  
 
 
Environment: 
 Jenkins ver. 2.97, Mask Password Plugin ver. 2.12.0  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Maksim Melnikov  
 

  
 
 
 
 

 
 Hey. I use mask-password-plugin in my pipeline to hide user input password for svn checkout: 

 

String password = userInput['svnPassword']
 wrap([$class: 'MaskPasswordsBuildWrapper', varPasswordPairs: [[password: password, var: 'pass']]]) {
    sh "svn checkout --username $user --password $password $url $projectDir"
 } 

 Console output is okay, there is masked password. But I see the full shell command in 'Pipeline Steps' Menu with password entered. See attach. I do not know any other way to get password from input and hide it.  
 

  
 
 
 
 


[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-02 Thread frank...@outlook.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank G commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
 we are also facing the same problem and had to revert the Bitbucket branch source plugin to version 2.4.0  
 

  
 
 
 
 

 
 
 

 
 
 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-54411) Configure page show Oops page (/configure)

2018-11-02 Thread d...@fortysix.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dominik Bartholdi resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54411  
 
 
  Configure page show Oops page (/configure)   
 

  
 
 
 
 

 
Change By: 
 Dominik Bartholdi  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-54422) Ability to specify custom message per Action

2018-11-02 Thread bartek1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bartosz Jędrzejewski created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54422  
 
 
  Ability to specify custom message per Action   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Martin Reinhardt  
 
 
Attachments: 
 rocketchat_jenking.png  
 
 
Components: 
 rocket-chat-notifier-plugin  
 
 
Created: 
 2018-11-02 11:56  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Bartosz Jędrzejewski  
 

  
 
 
 
 

 
 Right now there is only one Custom message that we can specify. It's on final message. It would be nice to have something like it was in HipChat plugin. Ability to specify what is said on build start, per Build Status messages etc. I attached the example from HipChat plugin.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 

[JIRA] (JENKINS-54401) java.lang.NullPointerException when parsing target revision date

2018-11-02 Thread peter.katzm...@edag.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Katzmann commented on  JENKINS-54401  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NullPointerException when parsing target revision date   
 

  
 
 
 
 

 
 I can confirm the Problem on PR's too 

 

java.lang.NullPointerException
	at com.fasterxml.jackson.databind.util.ISO8601Utils.parseInt(ISO8601Utils.java:329)
	at com.fasterxml.jackson.databind.util.ISO8601Utils.parse(ISO8601Utils.java:161)
	at com.fasterxml.jackson.databind.util.ISO8601DateFormat.parse(ISO8601DateFormat.java:52)
	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketGitSCMRevision.(BitbucketGitSCMRevision.java:60)
	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:843)
	at jenkins.scm.api.SCMSource.fetch(SCMSource.java:583)
	at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:288)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:429)
Finished: FAILURE
 

  
 

  
 
 
 
 

 
 
 

 
 
 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-54411) Configure page show Oops page (/configure)

2018-11-02 Thread iskoro...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Isko commented on  JENKINS-54411  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configure page show Oops page (/configure)   
 

  
 
 
 
 

 
 Fixed in PR 56 Fix released with version 3.4.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-54419) Re-release 3.13

2018-11-02 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-54419  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Re-release 3.13   
 

  
 
 
 
 

 
 

 
Fri Nov 02 11:33:51 UTC 2018 [daniel-beck-admin/x] [DELETED] releases:org/jenkins-ci/plugins/performance/3??.13/performance-3??.13-javadoc.jar
Fri Nov 02 11:33:51 UTC 2018 [daniel-beck-admin/x] [DELETED] releases:org/jenkins-ci/plugins/performance/3??.13/performance-3??.13-sources.jar
Fri Nov 02 11:33:51 UTC 2018 [daniel-beck-admin/x] [DELETED] releases:org/jenkins-ci/plugins/performance/3??.13/performance-3??.13.hpi
Fri Nov 02 11:33:51 UTC 2018 [daniel-beck-admin/x] [DELETED] releases:org/jenkins-ci/plugins/performance/3??.13/performance-3??.13.jar
Fri Nov 02 11:33:51 UTC 2018 [daniel-beck-admin/x] [DELETED] releases:org/jenkins-ci/plugins/performance/3??.13/performance-3??.13.pom
Fri Nov 02 11:33:51 UTC 2018 [daniel-beck-admin/x] [CREATED] releases/org/jenkins-ci/plugins/performance/maven-metadata.xml
 

 I expect https://updates.jenkins.io/download/plugins/performance to be available within the next hour or so.  
 

  
 
 
 
 

 
 
 

 
 
 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-54421) Configure page show Oops page after Installation of Artifactory Plugin

2018-11-02 Thread iskoro...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Isko commented on  JENKINS-54421  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configure page show Oops page after Installation of Artifactory Plugin   
 

  
 
 
 
 

 
 Fixed in PR 56 in version 3.4.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-54419) Re-release 3.13

2018-11-02 Thread artem.fedo...@blazemeter.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov commented on  JENKINS-54419  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Re-release 3.13   
 

  
 
 
 
 

 
 sounds good for me  
 

  
 
 
 
 

 
 
 

 
 
 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-54419) Re-release 3.13

2018-11-02 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-54419  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Re-release 3.13   
 

  
 
 
 
 

 
 Of course.  
 

  
 
 
 
 

 
 
 

 
 
 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-54383) consider adding bitbucket-oauth and github-oauth to Evergreen

2018-11-02 Thread d...@fortysix.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dominik Bartholdi commented on  JENKINS-54383  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: consider adding bitbucket-oauth and github-oauth to Evergreen   
 

  
 
 
 
 

 
 Baptiste Mathus that really sounds like a good way for me - I'll be more than happy to do this in some kind of supporting this special flavor.  For what its worth it: I currently have to move away from DEV@cloud anyway and everything I'm doing with my own instance on AWS is in the mind to be replaced by a provided solution at one day (e.g. evergreen) - this also means that I do nothing by hand anymore, everything is done with JCasC and job-dsl exclusively. So I should be able to start my seed job on any env and have the exact setup I need to do all my stuff.   
 

  
 
 
 
 

 
 
 

 
 
 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-54419) Re-release 3.13

2018-11-02 Thread artem.fedo...@blazemeter.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov commented on  JENKINS-54419  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Re-release 3.13   
 

  
 
 
 
 

 
 Daniel Beck Will you remove only broken release? Will you save  this https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/performance/3.13/performance-3.13.hpi  release?  
 

  
 
 
 
 

 
 
 

 
 
 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-54419) Re-release 3.13

2018-11-02 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-54419  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Re-release 3.13   
 

  
 
 
 
 

 
 Looks like the mere presence of the broken release in the history results in the dir listing not being created. Artem Fedorov Please let me know if you do not want me to delete the broken release from the Maven repo, otherwise I'll do that tomorrow or so.  
 

  
 
 
 
 

 
 
 

 
 
 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-54354) Jenkins Window slave can not fetch from bitbucket

2018-11-02 Thread xavier.fust...@clarivate.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Xavier Fustero edited a comment on  JENKINS-54354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Window slave can not fetch from bitbucket   
 

  
 
 
 
 

 
 I have checked the swarm process and it runs under SYSTEM user in windows. This user refers toC:\Windows\System32\config\systemprofile\I have created the .ssh directory under above dir and copied the private key. I go to Jenkins job and remove Git from *Source Code Management* and add creating "Execute Windows Batch command" in in Build section. I put the following command there:git clone ssh://git@ git XXX . clarivate.io/ls-editorial/ls-jpharm-gui-qa-tests-acceptance. gitThis worked and cloned the repo under my worksapce D:\workspaces\SYS-TEST successfullyHowever, when using the Source Code Management I get the error from the description. Mark, I reopen it to see if you can take a look again and explain why it works one way but not the other way.Thanks  
 

  
 
 
 
 

 
 
 

 
 
 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-54354) Jenkins Window slave can not fetch from bitbucket

2018-11-02 Thread xavier.fust...@clarivate.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Xavier Fustero updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54354  
 
 
  Jenkins Window slave can not fetch from bitbucket   
 

  
 
 
 
 

 
Change By: 
 Xavier Fustero  
 

  
 
 
 
 

 
 I have a Jenkins Master running on a linux box. Several jobs clone repos from Bitbucket but I have a Windows slave which fails with the following error:{noformat}Building remotely on slavewin-WIN-9G6KGDM45N7-7b265e7f (swarm slavewin) in workspace D:\workspace\SYS-TEST > C:\Program Files\Git\bin\git.exe rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > C:\Program Files\Git\bin\git.exe config remote.origin.url ssh://git@ git XXX . clarivate.io/ls-editorial/ls-jpharm-gui-qa-tests-acceptance. git # timeout=10Fetching upstream changes from ssh://git@git. clarivate XXX . io/ls-editorial/ls-jpharm-gui-qa-tests-acceptance. git > C:\Program Files\Git\bin\git.exe --version # timeout=10using GIT_SSH to set credentials rsa / deploy keys > C:\Program Files\Git\bin\git.exe fetch --tags --progress ssh://git@ git XXX . clarivate.io/ls-editorial/ls-jpharm-gui-qa-tests-acceptance. git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from ssh://git@ git XXX . clarivate.io/ls-editorial/ls-jpharm-gui-qa-tests-acceptance. git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:888) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1155) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1819) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: hudson.plugins.git.GitException: Command "C:\Program Files\Git\bin\git.exe fetch --tags --progress ssh://git@ git XXX . clarivate.io/ls-editorial/ls-jpharm-gui-qa-tests-acceptance. git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: /c: /c: Is a directoryfatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists.{noformat}  The job is configured passing the credential.On the Windows side I have installed git-bash:{noformat} $ git --versiongit version 2.19.1.windows.1{noformat}and set these environment variables:{noformat}GIT_SSH=C:\Program Files\Git\usr\bin\ssh.exePath=blablabla:C:\Program Files\Git\cmd{noformat}If I add the private key in users home/.ssh and type git commands to clone, fetch,etc on the Windows it works. However, when launching the Jenkins job from Master UI it return above error. From Jenkins Master I have this:{noformat}-bash-4.2$ git --versiongit version 2.18.0and 

[JIRA] (JENKINS-54354) Jenkins Window slave can not fetch from bitbucket

2018-11-02 Thread xavier.fust...@clarivate.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Xavier Fustero edited a comment on  JENKINS-54354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Window slave can not fetch from bitbucket   
 

  
 
 
 
 

 
 Hi [~markewaite], thanks for looking at it. I looked for an answer to the mailing list first but I couldn't find an answer. Similar problems but different.  I have removed the GIT_SSH from Windows but getting the same error. I set it as I saw the Jenkins Job said:{noformat} Fetching upstream changes from ssh://git@ git XXX . clarivate.io/ls-editorial/ls-jpharm-gui-qa-tests-acceptance. git > C:\Program Files\Git\bin\git.exe --version # timeout=10 using GIT_SSH to set credentials rsa / deploy keys{noformat}and probably I read someone suggesting to set it in Windows to that value.I see you close it but just wanted to note I am using Jenkins 2.138.2 in case someone else is reading it.  
 

  
 
 
 
 

 
 
 

 
 
 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-54419) Re-release 3.13

2018-11-02 Thread artem.fedo...@blazemeter.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54419  
 
 
  Re-release 3.13   
 

  
 
 
 
 

 
Change By: 
 Artem Fedorov  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number

2018-11-02 Thread artem.fedo...@blazemeter.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov commented on  JENKINS-54181  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance Plugin - Performance report displayed incorrect when compare Reports with Build number   
 

  
 
 
 
 

 
 https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/performance/3.13/performance-3.13.hpi  
 

  
 
 
 
 

 
 
 

 
 
 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-54419) Re-release 3.13

2018-11-02 Thread artem.fedo...@blazemeter.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov commented on  JENKINS-54419  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Re-release 3.13   
 

  
 
 
 
 

 
 Done.  https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/performance/3.13/performance-3.13.hpi  
 

  
 
 
 
 

 
 
 

 
 
 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-54419) Re-release 3.13

2018-11-02 Thread artem.fedo...@blazemeter.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov assigned an issue to Artem Fedorov  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54419  
 
 
  Re-release 3.13   
 

  
 
 
 
 

 
Change By: 
 Artem Fedorov  
 
 
Assignee: 
 Andrey Pokhilko Artem Fedorov  
 

  
 
 
 
 

 
 
 

 
 
 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-54399) Configuration page no longer loads

2018-11-02 Thread benoit.gue...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 benoit guerin commented on  JENKINS-54399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configuration page no longer loads   
 

  
 
 
 
 

 
 Fixed confirmed in 3.4.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.


  1   2   >