date:20190524

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57416  
 
 
  [GSoC] Role Strategy Plugin Performance Improvements: Phase 1   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 gsoc-2019  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57653) Extract the JMH framework to standalone lib or to JTH

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57653  
 
 
  Extract the JMH framework to standalone lib or to JTH   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Oliver Gondža  
 
 
Components: 
 jenkins-test-harness, role-strategy-plugin  
 
 
Created: 
 2019-05-24 07:45  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 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

[JIRA] (JENKINS-57654) Propose a Maven profile for JMH in Plugin POM

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57654  
 
 
  Propose a Maven profile for JMH in Plugin POM   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 plugin-pom, role-strategy-plugin  
 
 
Created: 
 2019-05-24 07:46  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199585.1558683987000.10949.1558684020190%40Atlassian.JIRA.
For more options, visit https://groups.g

[JIRA] (JENKINS-57654) Propose a Maven profile for JMH in Plugin POM

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Abhyudaya Sharma  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57654  
 
 
  Propose a Maven profile for JMH in Plugin POM   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev Abhyudaya Sharma  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57654) Propose a Maven profile for JMH in Plugin POM

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57654  
 
 
  Propose a Maven profile for JMH in Plugin POM   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 gsoc-2019  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57653) Extract the JMH framework to standalone lib or to JTH

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Abhyudaya Sharma  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57653  
 
 
  Extract the JMH framework to standalone lib or to JTH   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oliver Gondža Abhyudaya Sharma  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Gheorghiu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54929  
 
 
  Some final output is missing in Jenkins Pipeline when using the Ansible Plugin   
 

  
 
 
 
 

 
Change By: 
 Andrei Gheorghiu  
 
 
Attachment: 
 ansible-plugin-moved-output.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195937.1543444084000.11004.1558684922357%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Gheorghiu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54929  
 
 
  Some final output is missing in Jenkins Pipeline when using the Ansible Plugin   
 

  
 
 
 
 

 
Change By: 
 Andrei Gheorghiu  
 
 
Attachment: 
 ansible-plugin.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195937.1543444084000.10984.1558684922063%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Gheorghiu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54929  
 
 
  Some final output is missing in Jenkins Pipeline when using the Ansible Plugin   
 

  
 
 
 
 

 
Change By: 
 Andrei Gheorghiu  
 
 
Attachment: 
 ansible-plugin-blue-ocean.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195937.1543444084000.10964.1558684921565%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrei Gheorghiu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54929  
 
 
  Some final output is missing in Jenkins Pipeline when using the Ansible Plugin   
 

  
 
 
 
 

 
Change By: 
 Andrei Gheorghiu  
 
 
Comment: 
 I also have the same issue, but only in the standard console, the Blue Ocean UI displays everything properly. Also, this behavior is strictly related to the plugin, as the same command called from Jenkins shell  works as expected.  {quote}Running via ansible plugin[Pipeline] ansiblePlaybook[retry-test] $ ansible-playbook looping-with-parameters.yml -i inventory --extra-vars '\{"commands_list": [ls, pwd, date, whoami]}'PLAY [target] **TASK [Gathering Facts] *ok: [eltf-qemu01]TASK [Run test(s)] *changed: [eltf-qemu01] => (item=ls)changed: [eltf-qemu01] => (item=pwd)changed: [eltf-qemu01] => (item=date)[Pipeline] echoRunning from jenkins shell[Pipeline] sh+ ansible-playbook looping-with-parameters.yml -i inventory --extra-vars \{"commands_list": [ls, pwd, date, whoami]}changed: [eltf-qemu01] => (item=whoami)PLAY RECAP *eltf-qemu01: ok=2changed=1unreachable=0failed=0   PLAY [target] **TASK [Gathering Facts] *ok: [eltf-qemu01]TASK [Run test(s)] *changed: [eltf-qemu01] => (item=ls)changed: [eltf-qemu01] => (item=pwd)changed: [eltf-qemu01] => (item=date)changed: [eltf-qemu01] => (item=whoami)PLAY RECAP *eltf-qemu01: ok=2changed=1unreachable=0failed=0   {quote}!ansible-plugin-blue-ocean.PNG!System info: Ansible Pipeline plugin Version 1.0 Jenkins version 2.150.1 Pipeline version 2.6Blue Ocean 1.10.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57655) Can volumes-from be disabled for docker.image().inside() in a Jenkins pipeline?

2019-05-24 Thread pie...@pietervogelaar.nl (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pieter Vogelaar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57655  
 
 
  Can volumes-from be disabled for docker.image().inside() in a Jenkins pipeline?   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 docker-workflow-plugin  
 
 
Created: 
 2019-05-24 08:04  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Pieter Vogelaar  
 

  
 
 
 
 

 
 The Jenkins docker pipeline provides a very nice docker.image().inside() function. This will result in a docker run command like: 

 

docker run -t -d -u 1000:1000 -w /var/jenkins_home/workspace/my-job --volumes-from 30dfde62097dad7873b0c72da82f70252jefewfr72edb412c2e759303d10 -e  -e  -e  my-image:latest cat
 

 The `--volumes-from` parameter will provide the container with the same volumes as the main Jenkins container. So it will also expose the entire /var/jenkins_home directory.  Sometimes I would like to execute commands in a container and only expose the current job workspace. Is it possible to disable/remove the `--volumes-from` parameter? I can add an extra `v ${WORKSPACE}:/workspace` myself as args, but I can't find a way to disable/remove the `-volumes-from` parameter.   I also posted this on: https://stackoverflow.com/questions/56277847/can-volumes-from-be-disabled-for-docker-image-inside-in-a-jenkins-pipeline

[JIRA] (JENKINS-57655) Can volumes-from be disabled for docker.image().inside() in a Jenkins pipeline?

2019-05-24 Thread pie...@pietervogelaar.nl (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pieter Vogelaar updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57655  
 
 
  Can volumes-from be disabled for docker.image().inside() in a Jenkins pipeline?   
 

  
 
 
 
 

 
Change By: 
 Pieter Vogelaar  
 

  
 
 
 
 

 
 The Jenkins docker pipeline provides a very nice docker.image().inside() function. This will result in a docker run command like:{code:java}docker run -t -d -u 1000:1000 -w /var/jenkins_home/workspace/my-job --volumes-from 30dfde62097dad7873b0c72da82f70252jefewfr72edb412c2e759303d10 -e  -e  -e  my-image:latest cat{code}  The `--volumes-from` parameter will provide the container with the same volumes as the main Jenkins container. So it will also expose the entire /var/jenkins_home directory. Sometimes I would like to execute commands in a container and only expose the current job workspace.Is it possible to disable/remove the `--volumes-from` parameter?I can add an extra ` - v ${WORKSPACE}:/workspace` myself as args, but I can't find a way to disable/remove the `- - volumes-from` parameter. I also posted this on: [https://stackoverflow.com/questions/56277847/can-volumes-from-be-disabled-for-docker-image-inside-in-a-jenkins-pipeline]  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-57607) Can't log in after plugin update

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wadeck Follonier commented on  JENKINS-57607  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't log in after plugin update   
 

  
 
 
 
 

 
 Paul Adams, Neil Sleightholm, Josh Schreuder, A B, Sergio Labres, Björn Olsson, Sergio Labres, S imon, could you provide a bit of log in addition to the existing screenshot? That could be especially useful to detect where the root cause is. Thank you in advance!  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57655) Can volumes-from be disabled for docker.image().inside() in a Jenkins pipeline?

2019-05-24 Thread pie...@pietervogelaar.nl (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pieter Vogelaar updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57655  
 
 
  Can volumes-from be disabled for docker.image().inside() in a Jenkins pipeline?   
 

  
 
 
 
 

 
Change By: 
 Pieter Vogelaar  
 
 
Labels: 
 docker 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199588.1558685044000.11055.1558685340071%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-56447) Git Parameter plugin causes SCM polling to return false negatives

2019-05-24 Thread robin.jans...@zf.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Robin Jansohn commented on  JENKINS-56447  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Parameter plugin causes SCM polling to return false negatives   
 

  
 
 
 
 

 
 I can confirm this (Jenkins 2.164.3, git-parameter-plugin 0.9.10, git-client-plugin 2.7.7, git-plugin 3.10.0, scm-api-plugin 2.4.1). We also use Bitbucket server (v5.14.4). Is this being looked at? With the current state we cannot use Git SCM polling to trigger nightly builds (@midnight). Changes are simply not detected. I looked at the workspace folder and it did not contain the latest changes (no git pull or similar executed). Job type is pipeline and we also use the git parameter to specify the branch (default origin/master). As additional behaviors we have Check out to specific local branch with an empty value activated. Git Polling Log 

 
Started on May 24, 2019, 12:49:00 AM
Using strategy: Default
[poll] Last Built Revision: Revision 8f72cec4daf37c36fd32884b531f6e9ef64bdff9 (refs/remotes/origin/master)
using credential git-ssh-creds
 > /usr/bin/git --version # timeout=10
using GIT_SSH to set credentials SSH key access on Bitbucket server
 > /usr/bin/git ls-remote -h ssh://g...@git.my-company.com:7999/project/repo.git # timeout=10
Found 1 remote heads on ssh://g...@git.my-company.com:7999/project/repo.git
Using strategy: Default
[poll] Last Built Revision: Revision 8f72cec4daf37c36fd32884b531f6e9ef64bdff9 (refs/remotes/origin/master)
using credential git-ssh-creds
 > /usr/bin/git --version # timeout=10
using GIT_SSH to set credentials SSH key access on Bitbucket server
 > /usr/bin/git ls-remote -h ssh://g...@git.my-company.com:7999/project/repo.git # timeout=10
Found 1 remote heads on ssh://g...@git.my-company.com:7999/project/repo.git
Done. Took 0.69 sec
No changes
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-34642) Jenkins 2.0: pinning plugins no longer works

2019-05-24 Thread dirk.heinri...@recommind.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dirk Heinrichs commented on  JENKINS-34642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins 2.0: pinning plugins no longer works   
 

  
 
 
 
 

 
 /me also thinks this was a bad decision. The pinning functionality shouldn't be coupled to bundled plugins. The use case is also quite simple. There's one plugin in we make use of in several hundred jobs, but it once introduced a backwards incompatible change, which prevents us from updating it. Since we cannot pin it anymore, we need to be careful when updating our plugins not to update this single plugin also, since it would break 80% of our jobs when we do so. Pinning it once would really save us a lot of hassle.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57607) Can't log in after plugin update

2019-05-24 Thread n...@x2systems.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Neil Sleightholm commented on  JENKINS-57607  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't log in after plugin update   
 

  
 
 
 
 

 
 Can you let me know the log file name?  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-34642) Jenkins 2.0: pinning plugins no longer works

2019-05-24 Thread dirk.heinri...@recommind.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dirk Heinrichs edited a comment on  JENKINS-34642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins 2.0: pinning plugins no longer works   
 

  
 
 
 
 

 
 /me also thinks this was a bad decision. The pinning functionality shouldn't be coupled to bundled plugins. The use case is also quite simple. There's one plugin  in  we make use of in several hundred jobs, but it once introduced a backwards incompatible change, which prevents us from updating it. Since we cannot pin it anymore, we need to be careful when updating our plugins not to update this single plugin also, since it would break 80% of our jobs when we do so.Pinning it once would really save us a lot of hassle.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-34642) Jenkins 2.0: pinning plugins no longer works

2019-05-24 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-34642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins 2.0: pinning plugins no longer works   
 

  
 
 
 
 

 
 Dirk Heinrichs Pinning did nothing for your use case, except show a label on the UI that you used to mean something different, as it could still be updated. The same thing could be accomplished by adding something like labels to installed plugins without all the baggage that came with pinning.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-34642) Jenkins 2.0: pinning plugins no longer works

2019-05-24 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck edited a comment on  JENKINS-34642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins 2.0: pinning plugins no longer works   
 

  
 
 
 
 

 
 [~dhs] Pinning did _nothing_ for your use case, except show a label on the UI that you used to mean something different, as it could still be updated. The same thing could be accomplished by adding something like labels to installed plugins without all the baggage that came with pinning.  Or editable descriptions.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57607) Can't log in after plugin update

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wadeck Follonier commented on  JENKINS-57607  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't log in after plugin update   
 

  
 
 
 
 

 
 Neil Sleightholm You can follow Logging to retrieve the log file, I hope this will help you!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57607) Can't log in after plugin update

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wadeck Follonier edited a comment on  JENKINS-57607  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't log in after plugin update   
 

  
 
 
 
 

 
 [~nsleigh] You can follow  the information on this page:  [Logging  doc |https://wiki.jenkins.io/display/JENKINS/Logging] to retrieve the log file, I hope this will help you!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57607) Can't log in after plugin update

2019-05-24 Thread kad...@hamburg-applications.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wadeck Follonier edited a comment on  JENKINS-57607  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't log in after plugin update   
 

  
 
 
 
 

 
 [~nsleigh] You can follow the information on this page: [Logging doc|https://wiki.jenkins.io/display/JENKINS/Logging] ,  to retrieve the log file, I hope this will help you!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57656) Run on tag even if no change detected

2019-05-24 Thread jonathan.bouze...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Bouzekri created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57656  
 
 
  Run on tag even if no change detected   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Kirill Merkushev  
 
 
Components: 
 github-plugin  
 
 
Created: 
 2019-05-24 09:48  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jonathan Bouzekri  
 

  
 
 
 
 

 
 When I push a tag, github webhook correctly calls my jenkins hook. However nothing is triggered. The log shows that it receives the tag information however as it is on a commit that was already built, it did not detect any change so the built was not triggered. It would be great to have a behavior to force the build on a tag. My use case is to build a docker image tagged with the tag name automatically.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57639) InfluxDB Plugin Robot Framework "suite_result" data publication fails with org.influxdb.InfluxDBException$FieldTypeConflictException after update to 1.21

2019-05-24 Thread aleksi.sim...@eficode.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksi Simell commented on  JENKINS-57639  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: InfluxDB Plugin Robot Framework "suite_result" data publication fails with org.influxdb.InfluxDBException$FieldTypeConflictException after update to 1.21   
 

  
 
 
 
 

 
 Did you also update Robot Framework plugin? InfluxDB plugin doesn't specify the type of data it writes, it gets its values from Robot Framework plugin. You have already written into the database with floats, so you cannot write integers there, unless you drop measurement suite_result.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-46094) "Checkout over SSH" fails the build since it still uses HTTPS urls

2019-05-24 Thread forbes...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Al Forbes commented on  JENKINS-46094  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Checkout over SSH" fails the build since it still uses HTTPS urls   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/bitbucket-branch-source-plugin/releases I did not find the 2.4.5 release. Are publish and release different things? If someone has time, a 2.4.5 release would be highly appreciated.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57657) SYSTEM user could be used to track changes during initialization process.

2019-05-24 Thread esc...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Emilio Escobar  created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57657  
 
 
  SYSTEM user could be used to track changes during initialization process.   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Emilio Escobar   
 
 
Components: 
 jobconfighistory-plugin  
 
 
Created: 
 2019-05-24 10:09  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Emilio Escobar   
 

  
 
 
 
 

 
 Until InitLevel is not COMPLETED, unknown/anonymous user is used for tracking changes in configuration files as is defined at https://github.com/jenkinsci/jobConfigHistory-plugin/blob/master/src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistorySaveableListener.java#L88-L93 SYSTEM user looks like a better option (as the changes are done by the system at that point).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job

2019-05-24 Thread candidusl...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Shcherbakov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57549  
 
 
  Jenkins job doesn't detect completion of mainframe job   
 

  
 
 
 
 

 
Change By: 
 Alexander Shcherbakov  
 
 
Attachment: 
 zos-connector-restructure-relogon.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199458.1558312268000.11197.1558692660276%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job

2019-05-24 Thread candidusl...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Shcherbakov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57549  
 
 
  Jenkins job doesn't detect completion of mainframe job   
 

  
 
 
 
 

 
Change By: 
 Alexander Shcherbakov  
 
 
Attachment: 
 zos-connector-old-logon-connect.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199458.1558312268000.11195.1558692660239%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job

2019-05-24 Thread candidusl...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Shcherbakov commented on  JENKINS-57549  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins job doesn't detect completion of mainframe job   
 

  
 
 
 
 

 
 copy-pasted old (2.2) logon and connect routines. Kindly retest with them. This looks more and more strange: can it be somehow related to FTP server state?  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57658) Test issue for scrum board

2019-05-24 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57658  
 
 
  Test issue for scrum board   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Parichay Barpanda  
 
 
Components: 
 assembla-merge-request-builder-plugin  
 
 
Created: 
 2019-05-24 10:17  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Parichay Barpanda  
 

  
 
 
 
 

 
 Ignorance is bliss.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-55648) Logging of parallel pipeline job is not recording post stage after failed job

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Kadner commented on  JENKINS-55648  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Logging of parallel pipeline job is not recording post stage after failed job   
 

  
 
 
 
 

 
 New finding: The log recording stop is depending on the load on the jenkins master. Increasing the hardware performance (more CPU power) stabilizes the logging.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55648) Logging of parallel pipeline job is not recording post stage after failed job

2019-05-24 Thread kad...@hamburg-applications.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Kadner updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55648  
 
 
  Logging of parallel pipeline job is not recording post stage after failed job   
 

  
 
 
 
 

 
Change By: 
 Martin Kadner  
 
 
Labels: 
 Pipeline error http  jenkins  logging  master  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55240) Refusing to marshal org.jvnet.hudson.test.TestCrumbIssuer for security reasons

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55240  
 
 
  Refusing to marshal org.jvnet.hudson.test.TestCrumbIssuer for security reasons   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 https://ci.jenkins.io/job/Plugins/job/kubernetes-plugin/job/PR-409/1/testReport/org.csanchez.jenkins.plugins.kubernetes/KubernetesSlaveTest/windows_8___Archive__windows_8testGetPodRetention/Discussion in https://github.com/jenkinsci/kubernetes-plugin/pull/409 {code }java.lang.RuntimeException : java .io.IOException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#clouds for class hudson.model.Hudson }   at hudson.util.PersistedList._onModified(PersistedList.java:183) at hudson.util.PersistedList.add(PersistedList.java:72) at org.csanchez.jenkins.plugins.kubernetes.KubernetesSlaveTest.testGetPodRetention(KubernetesSlaveTest.java:93) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:552) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.lang.Thread.run(Thread.java:748) Caused by: java. io.IOException: java. lang. RuntimeException: Failed to serialize jenkins.model.Jenkins#clouds for class hudson.model.Hudson at hudson.XmlFile.write(XmlFile.java:200) at jenkins.model.Jenkins.save(Jenkins.java:3221) at hudson.util.PersistedList.onModified(PersistedList.java:173) at jenkins.model.Jenkins$CloudList.onModified(Jenkins.java:501) at hudson.util.PersistedList._onModified(PersistedList.java:181) ... 15 moreCaused by: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#clouds for class hudson.model.Hudson at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.c

[JIRA] (JENKINS-55240) Refusing to marshal org.jvnet.hudson.test.TestCrumbIssuer for security reasons

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-55240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Refusing to marshal org.jvnet.hudson.test.TestCrumbIssuer for security reasons   
 

  
 
 
 
 

 
 Removed the confusing description. IIUc the issue is still there, Abhyudaya Sharma has hit it recently in Role Strategy plugin tests. My suggestion would be to whitelist the serialization in the entire JTH library to avoid such issues in the future. We just need to add "Jenkins-ClassFilter-Whitelisted=true" to the manifest (https://jenkins.io/blog/2018/01/13/jep-200/#making-plugins-compatible-with-jenkins-2-102-or-above). WDYT Jesse Glick?    
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57659) jenkins share library Cannot cast object 'true' with class 'java.lang.Boolean'

2019-05-24 Thread 763513...@qq.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 wang xingmin created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57659  
 
 
  jenkins share library Cannot cast object 'true' with class 'java.lang.Boolean'   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 jenkinsfile-runner  
 
 
Created: 
 2019-05-24 10:42  
 
 
Environment: 
 ubunt18  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 wang xingmin  
 

  
 
 
 
 

 
 I use jenkins share library to upload maven jar package to nexus3 , it upload success , but finally  report an error . my upload script : pipeline { stage("publish to nexus") { script { echo "ok" pom = readMavenPom file: "pom.xml" filesByGlob = findFiles(glob: "target/*.${pom.packaging}") artifactPath = filesByGlob[0].path nexusArtifactUploader( nexusVersion: NEXUS_VERSION, protocol: NEXUS_PROTOCOL, nexusUrl: NEXUS_URL, groupId: pom.groupId, version: "${ env.BRANCH_NAME }", repository: NEXUS_REPOSITORY, credentialsId: NEXUS_CREDENTIAL_ID, artifacts: [ [artifactId: pom.artifactId, classifier: "${ env.BUILD_NUMBER }-${GIT_COMMIT_SHORT}",  file: artifactPath, type: pom.packaging],  ] ) } } } the error messages: [Pipeline] // node [Pipeline] End of Pipeline hudson.remoting.ProxyException: org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'true' with class 'java.lang.Boolean' to class 'org.jenkinsci.plugins.pipeline.modeldefinition.model.Root' at org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.continueCastOnSAM(DefaultTypeTransformation.java:405) at org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.continueCastOnNumber(DefaultTypeTransformation.java:319) at org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType(DefaultTypeTransformation.java:232) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.castToType(ScriptBytecodeAdapter.java:603) at org.codehaus.groovy.runtime.ScriptBy

[JIRA] (JENKINS-26213) LI parameter submission is not supported for the class hudson.plugins.validating_string_parameter.ValidatingStringParameterDefinition type.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou commented on  JENKINS-26213  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: LI parameter submission is not supported for the class hudson.plugins.validating_string_parameter.ValidatingStringParameterDefinition type.   
 

  
 
 
 
 

 
 You need a more advanced script for that. You can find an example of such script on the jenkins-rest wiki.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57622) Community Bounding Phase for Cloud features for EWM GSoC 2019

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57622  
 
 
  Community Bounding Phase for Cloud features for EWM GSoC 2019   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 gsoc-2019  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57621) Community Bounding Phase for Cloud features for EWM GSoC 2019

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57621  
 
 
  Community Bounding Phase for Cloud features for EWM GSoC 2019   
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 gsoc-2019  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57623) Update jenkins.io page

Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin d'Anjou updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57623  
 
 
  Update jenkins.io page
 

  
 
 
 
 

 
Change By: 
 Martin d'Anjou  
 
 
Labels: 
 gsoc-2019  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57658) Test issue for scrum board

2019-05-24 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57658  
 
 
  Test issue for scrum board   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Labels: 
 gsoc-2019  
 
 
Sprint: 
 GSoC 2019. Coding Phase 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199591.1558693036000.11297.1558695600084%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57424) Parse JMH benchmark Results

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57424  
 
 
  Parse JMH benchmark Results   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Labels: 
 gsoc-2019  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57423) Introduce JMH benchmarks for Role Strategy Plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57423  
 
 
  Introduce JMH benchmarks for Role Strategy Plugin   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Labels: 
 gsoc-2019  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57425) Implement JMH benchmark in pull request build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57425  
 
 
  Implement JMH benchmark in pull request build   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Labels: 
 gsoc-2019  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-24 Thread ol...@apache.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy updated  JENKINS-57244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Status: 
 In Review 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199007.1556619184000.11309.1558696381273%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel

2019-05-24 Thread ol...@apache.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57244  
 
 
  java.io.NotSerializableException: The calling thread Thread has no associated channel   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Labels: 
 maven-plugin-3.3 regression  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-8244) "Too Many Open files", Git and SSH slave

2019-05-24 Thread karankaushik...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karan Kaushik commented on  JENKINS-8244  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Too Many Open files", Git and SSH slave   
 

  
 
 
 
 

 
 Still facing the issue in Jenkins 2.135, is there someway to fix this problem permanently?  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57421) Profile Role Strategy Plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57421  
 
 
  Profile Role Strategy Plugin   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Sprint: 
 GSoC 2019.  Coding Phase 1  Community Bonding  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57424) Parse JMH benchmark Results

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57424  
 
 
  Parse JMH benchmark Results   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Sprint: 
 GSoC 2019. Coding Phase 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199236.1557740142000.11333.1558697160580%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57423) Introduce JMH benchmarks for Role Strategy Plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57423  
 
 
  Introduce JMH benchmarks for Role Strategy Plugin   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Sprint: 
 GSoC 2019. Coding Phase 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199235.1557740094000.11330.1558697160537%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57653) Extract the JMH framework to standalone lib or to JTH

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57653  
 
 
  Extract the JMH framework to standalone lib or to JTH   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Sprint: 
 GSoC 2019. Coding Phase 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199584.155868394.11342.1558697160704%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57425) Implement JMH benchmark in pull request build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57425  
 
 
  Implement JMH benchmark in pull request build   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Sprint: 
 GSoC 2019. Coding Phase  2  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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199237.1557740286000.11339.1558697160673%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57425) Implement JMH benchmark in pull request build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57425  
 
 
  Implement JMH benchmark in pull request build   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Sprint: 
 GSoC 2019. Coding Phase 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199237.1557740286000.11336.1558697160635%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57654) Propose a Maven profile for JMH in Plugin POM

2019-05-24 Thread bochenski.kuba+jenk...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57654  
 
 
  Propose a Maven profile for JMH in Plugin POM   
 

  
 
 
 
 

 
Change By: 
 Abhyudaya Sharma  
 
 
Sprint: 
 GSoC 2019. Coding Phase 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199585.1558683987000.11345.1558697160819%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost

2019-05-24 Thread svcj...@keitalbame.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nuno Costa commented on  JENKINS-55220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch Pipeline jobs get randomly lost   
 

  
 
 
 
 

 
 This happening to me today. I had this happening a few weeks ago and without any change from our part, it reenabled the branch. We are using bitbucket.org Team. Using jenkins 2.164.2 and nginx, both as containers.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost

2019-05-24 Thread svcj...@keitalbame.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nuno Costa edited a comment on  JENKINS-55220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch Pipeline jobs get randomly lost   
 

  
 
 
 
 

 
 This  is  happening to me today. I had this happening a few weeks ago and without any change from our part, it reenabled the branch.We are using bitbucket.org Team.Using jenkins 2.164.2 and nginx, both as containers.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost

2019-05-24 Thread svcj...@keitalbame.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nuno Costa edited a comment on  JENKINS-55220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch Pipeline jobs get randomly lost   
 

  
 
 
 
 

 
 This is happening to me today , although is not showing any errors .  The Scan log shows that is not detecting jenkinsfile on a specific branch but the file is there. Other branches with jenkinsfile are been shown in the log.  I had this happening a few weeks ago and without any change from our part, it reenabled the branch.We are using bitbucket.org Team.Using jenkins 2.164.2 and nginx, both as containers.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57631) No credentials found for id

2019-05-24 Thread jiaozi362...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 zern king assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57631  
 
 
  No credentials found for id   
 

  
 
 
 
 

 
Change By: 
 zern king  
 
 
Assignee: 
 zern king  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-52697) Logstash plugin: support JCasC

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski updated  JENKINS-52697  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Done  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52697  
 
 
  Logstash plugin: support JCasC   
 

  
 
 
 
 

 
Change By: 
 Jakub Bochenski  
 
 
Status: 
 Fixed but Unreleased Resolved  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git from Amazon

2019-05-24 Thread audrius.meskaus...@meska.info (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Audrius Meskauskas created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57660  
 
 
  Git plugin crash on saving the project on Amazon EC while using git from Amazon   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Attachments: 
 trace.txt  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2019-05-24 12:22  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Audrius Meskauskas  
 

  
 
 
 
 

 
 When using Jenkins inside Amazon EC cloud (and using Amazon Code Commit git provider), the attached stack trace was observed while trying to modify and save the build project settings. The crash is relevant to hudson.plugins.git.GitSCM. The project uses git to fetch the sources. This initially worked, and the project actually even runs the build no problem, but it cannot be modified because of the crash. Strange to see the Git plugin crash on action that itself should not include any interaction with repository.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit

2019-05-24 Thread audrius.meskaus...@meska.info (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Audrius Meskauskas updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57660  
 
 
  Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit   
 

  
 
 
 
 

 
Change By: 
 Audrius Meskauskas  
 
 
Summary: 
 Git plugin crash on saving the project on Amazon EC while using git  from  for  Amazon  Code Commit  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit

2019-05-24 Thread audrius.meskaus...@meska.info (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Audrius Meskauskas updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57660  
 
 
  Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit   
 

  
 
 
 
 

 
Change By: 
 Audrius Meskauskas  
 

  
 
 
 
 

 
 When using Jenkins inside Amazon EC cloud (and using Amazon Code Commit git provider), the attached stack trace was observed while trying to modify and save the build project settings. The crash is relevant to hudson.plugins.git.GitSCM.The project uses git to fetch the sources. This initially worked, and the project actually even runs the build no problem, but it cannot be modified because of the crash. Strange to see the Git plugin crash on action that itself should not include any interaction with repository. Using Jenkins   
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit

2019-05-24 Thread audrius.meskaus...@meska.info (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Audrius Meskauskas updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57660  
 
 
  Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit   
 

  
 
 
 
 

 
Change By: 
 Audrius Meskauskas  
 

  
 
 
 
 

 
 When using Jenkins inside Amazon EC cloud (and using Amazon Code Commit git provider), the attached stack trace was observed while trying to modify and save the build project settings. The crash is relevant to hudson.plugins.git.GitSCM.The project uses git to fetch the sources. This initially worked, and the project actually even runs the build no problem, but it cannot be modified because of the crash. Strange to see the Git plugin crash on action that itself should not include any interaction with repository.Using Jenkins  2.164.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199593.1558700538000.11403.1558700760239%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit

2019-05-24 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57660  
 
 
  Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit

2019-05-24 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-57660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit   
 

  
 
 
 
 

 
 I believe the stack trace message is correct. The refspec is invalid. It needs to be corrected. If the Amazon Code Commit plugin created that refspec, it needs to be changed to provide a correct refspec. If a person entered that refspec, then they need to change the refspec to use a correct value. I agree that this is a bug, since the stack trace is much too ugly a way of showing a failure to the user.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57661) The incrementals-publisher does not provide a reason for some 400 Bad Request errors

2019-05-24 Thread chris+jenk...@chriskilding.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Kilding created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57661  
 
 
  The incrementals-publisher does not provide a reason for some 400 Bad Request errors   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-05-24 12:34  
 
 
Environment: 
 Server: ci.jenkins.io  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Chris Kilding  
 

  
 
 
 
 

 
 When my plugin deploys to Jenkins Incrementals on ci.jenkins.io, sometimes I get a 400 Bad Request response but with no explanation in the body. This means that I (the plugin author) cannot know what has gone wrong. In addition, the deploy step of the plugin build passes, even though an error has occurred. An example build: https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Faws-secrets-manager-credentials-provider-plugin/detail/support%2Fdocumentation/5/pipeline Note: I filed this under ‘core’ because there was no component for ‘community-functions’.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57661) The incrementals-publisher does not provide a reason for some 400 Bad Request errors

2019-05-24 Thread chris+jenk...@chriskilding.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Kilding commented on  JENKINS-57661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The incrementals-publisher does not provide a reason for some 400 Bad Request errors   
 

  
 
 
 
 

 
 Related discussion on the mailing list: https://groups.google.com/forum/m/#!topic/jenkinsci-dev/dpfPf-qyPzQ    
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit

2019-05-24 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-57660  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit   
 

  
 
 
 
 

 
 I believe the stack trace message is correct.  The refspec is invalid.  It needs to be corrected.If the Amazon Code Commit plugin created that refspec, it needs to be changed to provide a correct refspec.If a person entered that refspec, then they need to change the refspec to use a correct value. I  agree that this is a bug, since the stack trace is much too ugly a way of showing a failure to the user. When I use that invalid refspec in the "Advanced" section of the git repository configuration, saving the form shows the following message:{noformat}java.lang.IllegalArgumentException: Invalid wildcards refs/remotes/*/master/* at org.eclipse.jgit.transport.RefSpec.(RefSpec.java:196) at org.eclipse.jgit.transport.RefSpec.(RefSpec.java:226) at org.eclipse.jgit.lib.DefaultTypedConfigGetter.getRefSpecs(DefaultTypedConfigGetter.java:302) at org.eclipse.jgit.lib.Config.getRefSpecs(Config.java:502) at org.eclipse.jgit.transport.RemoteConfig.(RemoteConfig.java:195) at org.eclipse.jgit.transport.RemoteConfig.getAllRemoteConfigs(RemoteConfig.java:124) at hudson.plugins.git.GitSCM$DescriptorImpl.createRepositoryConfigurations(GitSCM.java:1612)Caused: hudson.plugins.git.GitException: Error creating repositories at hudson.plugins.git.GitSCM$DescriptorImpl.createRepositoryConfigurations(GitSCM.java:1614) at hudson.plugins.git.GitSCM.updateFromUserData(GitSCM.java:264) at hudson.plugins.git.GitSCM.(GitSCM.java:214) at jdk.internal.reflect.GeneratedConstructorAccessor213.newInstance(Unknown Source) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:474) at hudson.model.Descriptor.newInstance(Descriptor.java:596){noformat}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57400) Add option to filter warnings

2019-05-24 Thread heiko.th...@hpi.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 sunblack commented on  JENKINS-57400  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add option to filter warnings   
 

  
 
 
 
 

 
 Oh thanks, searched for this in tool option, and not in general settings (event it makes sense how it is). Nevertheless: filter is using absolute path and not relativ paths, so it is more complex with multiple build server.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57402) Let diagrams interact with Details table

2019-05-24 Thread heiko.th...@hpi.de (JIRA)

Title: Message Title

sunblack commented on JENKINS-57402

Re: Let diagrams interact with Details table

In general I prefer a combined view, like it is done by old CppCheck plugin. This shows all warnings in on table, bug highlight rows (green => fixes, red => new, white => not changed). This is a view I really miss here, especially this plugin generates a new warning if only line number changed (e.g. if you have 5 warnings and add or remove a line before these warnings, this plugins shows 5 fixed and 5 new warnings, during old CppCheck plugin count this as not changed). With combined view of all 3 categories (new, fixed, outstanding) it would be much easier to see, which new warnings were only generated because of changed lines. And of course this would allow interacting with the diagrams .

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

[JIRA] (JENKINS-12615) Discard Old Builds does not warn the user when no builds will be discarded

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-12615  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Discard Old Builds does not warn the user when no builds will be discarded   
 

  
 
 
 
 

 
 Jesse Glick  In implementation, I have just added one if condition(type of flag) in LogRotator.java. Whenever value of numToKeep and daysToKeep are not blank, then according to flag(new variable declared) message will be displayed. Currently I have added only if condition and I got error. I have searched regarding this error, but I am not getting it clear. Error is of failure of JUnit tests. But I don't know why it failed. [ERROR] Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 0.006 s <<< FAILURE! - in hudson.cli.PrivateKeyProviderTest [ERROR] loadKeyBroken(hudson.cli.PrivateKeyProviderTest) Time elapsed: 0.001 s <<< ERROR! java.lang.Exception: Unexpected exception, expected but was at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:28) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) Caused by: java.nio.file.NoSuchFileException: C:\Open%20Source\cli\target\test-classes\hudson\cli\openssh-broken at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) at sun.nio.fs.WindowsFileSystemProvider.newByteChannel(WindowsFileSystemProvider.java:230) at java.nio.file.Files.newByteChannel(Files.java:361) at java.nio.file.Files.newByteChannel(Files.java:407) at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384) at java.nio.file.Files.newInputStream(Files.java:152) at hudson.cli.PrivateKeyProvider.readPemFile(PrivateKeyProvider.java:132) at hudson.cli.PrivateKeyProvider.loadKey(PrivateKeyProvider.java:128) at hudson.cli.PrivateKeyProviderTest.loadKeyBroken(PrivateKeyProviderTest.java:102) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statemen

[JIRA] (JENKINS-57581) Jenkins job created by seed job using jobdsl script does't shows JMS message checks on job UI.

2019-05-24 Thread sco...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Hebert commented on  JENKINS-57581  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins job created by seed job using jobdsl script does't shows JMS message checks on job UI.   
 

  
 
 
 
 

 
 So 3 things. 
 
my script is not a pipeline script. it is a DSL script. 
You mis-spelled msgCheck. 
Using your method of configure is not correctly creating the CIBuildTrigger object in that Jenkins complains that it is missing a parameter from a class that CIBuildTrigger inherited. 
   Here is my version of your DSL script that works for me:   

 
import groovy.json.JsonSlurper
def uuid = UUID.randomUUID().toString()

folder('test-job')  {
 description ('folder containing jobs for Rhel-8')
}



job("test-job/job-2") {
	description()
	keepDependencies(false)
  
multiscm {
  git{

remote{
  url("https://gitlab.cee.redhat.com/g11n-qe/Rhel-8.0-Automation.git")
credentials ("demo-creds")
  
   
  }
  branch("*/master")
  }
}
  
 //label('pooja-openqa')

	disabled(false)
	concurrentBuild(false)
	steps {
		shell("""sudo cp -R * /var/lib/openqa/tests/
ls""")
 }
triggers {
ciBuildTrigger {
providerData {
activeMQSubscriberProviderData {
checks {   
  msgCheck { 
  	expectedValue("RHEL-7.7")
field("release-id")   
}
} 
name ("Red Hat UMB")
overrides
{
topic("Consumer.rh-jenkins-ci-plugin."+uuid+".VirtualTopic.distill.compose-moved")
}
selector("mtype =  'compose-moved' AND environment = 'prod' AND service = 'distill'")
}
}
noSquash(true)
}
}
 

}
 

 At this point, I will not be addressing any code changes for this issue. I am closing the ticket.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57581) Jenkins job created by seed job using jobdsl script does't shows JMS message checks on job UI.

2019-05-24 Thread sco...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Hebert updated  JENKINS-57581  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57581  
 
 
  Jenkins job created by seed job using jobdsl script does't shows JMS message checks on job UI.   
 

  
 
 
 
 

 
Change By: 
 Scott Hebert  
 
 
Status: 
 Reopened Fixed but Unreleased  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57662) A blog post about our project workflow

2019-05-24 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57662  
 
 
  A blog post about our project workflow   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Parichay Barpanda  
 
 
Components: 
 gitlab-api-plugin, gitlab-branch-source-plugin  
 
 
Created: 
 2019-05-24 14:02  
 
 
Environment: 
 Ubuntu, Git  
 
 
Labels: 
 gsoc-2019  
 
 
Priority: 
  Trivial  
 
 
Reporter: 
 Parichay Barpanda  
 

  
 
 
 
 

 
 This blog post describes how the workflow of our project will be carried. Talk about how we are using Jira and the git workflow model we are employing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57662) A blog post about our project workflow

2019-05-24 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda assigned an issue to Marky Jackson  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57662  
 
 
  A blog post about our project workflow   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 
 
Assignee: 
 Parichay Barpanda Marky Jackson  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57662) A blog post about our project workflow

2019-05-24 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57662  
 
 
  A blog post about our project workflow   
 

  
 
 
 
 

 
Change By: 
 Parichay Barpanda  
 

  
 
 
 
 

 
 This blog post describes how the workflow of our project will be carried. Talk about how we are using Jira and the git workflow model we are employing.  https://baymac.github.io/2019/05/project-workflow-for-gsoc  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57662) A blog post about our project workflow

2019-05-24 Thread parichay.barpa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda updated  JENKINS-57662  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57662  
 
 
  A blog post about our project workflow   
 

  
 
 
 
 

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

2019-05-24 Thread mahmoud.al-a...@intel.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mahmoud Al-Ashi commented on  JENKINS-44930  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 I believe command "sh" should always return an object with all relevant output (stdout, stderr, exit_code) and at the same time it should also print the output live to the console unless some argument (no_stdout) or so is given. This way you can access all at once. The other problem that I see now is that when "returnStdout" is provided, the output is not printed to the console. I would prefer to print the output to the console live anyway but also get the output to parse it or do something special with 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183003.149756330.11436.1558707241454%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57662) A blog post about our project workflow

2019-05-24 Thread marky.r.jack...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson commented on  JENKINS-57662  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: A blog post about our project workflow   
 

  
 
 
 
 

 
 Parichay Barpanda I agree with this flow and the entire blog post. Let's wait for Rick to also 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199595.1558706565000.11512.1558707360171%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-56890) IOException: "cannot find current thread"

2019-05-24 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-56890  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IOException: "cannot find current thread"   
 

  
 
 
 
 

 
 

I wonder if there could be other problems with running the completion callback in GeneralNonBlockingStepExecution on a separate thread (maybe we need to fix that instead of just making the collection thread safe)
 Long before this API was introduced, steps were sometimes calling StepContext.get from arbitrary threads, whether that happened to be part of callback processing or not. (simple example) It is expected to be thread-safe.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57186) New View href is an absolute URL but other menu items are relative URLs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-57186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New View href is an absolute URL but other menu items are relative URLs   
 

  
 
 
 
 

 
 I tried applying the proposed solution, but few tests failed. So this solution won't work Napoleon BlownApart.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57642) Wrong parameter type and squashing its content when trigger a job

2019-05-24 Thread sco...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Hebert commented on  JENKINS-57642  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Wrong parameter type and squashing its content when trigger a job   
 

  
 
 
 
 

 
 Pavel Janoušek akostadinov We were actually hardcoding the use of StringParameterValue instead of looking at what the job was using for its CI_MESSAGE parameter. I am working on a fix with proper tests for this use case.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57186) New View href is an absolute URL but other menu items are relative URLs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-57186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New View href is an absolute URL but other menu items are relative URLs   
 

  
 
 
 
 

 
 Test Failures :  [INFO] Results: [INFO] [ERROR] Failures: [ERROR] FilePathTest.isDescendant_regularSymlinks:960 [ERROR] FilePathTest.isDescendant_worksEvenInSymbolicWorkspace:1110 [ERROR] UtilTest.resolveSymlinkToFile:570 [ERROR] NewViewLinkTest.getActionsHasPermission:55 expected: but was:<[]/newView> [ERROR] NewViewLinkTest.getActionsNoPermission:68 expected: but was:<[]/newView> [ERROR] VirtualFileTest.forFilePath_isDescendant:277->checkCommonAssertionForIsDescendant:312 [ERROR] VirtualFileTest.forFilePath_listOnlyDescendants_withoutIllegal:366->checkCommonAssertionForList:392 Expected: iterable over [Has name: aa, Has name: ab, Has name: _b] in any order but: No item matches: Has name: _b in [, ] [ERROR] VirtualFileTest.forFile_isDescendant:261->checkCommonAssertionForIsDescendant:312 [ERROR] VirtualFileTest.forFile_listOnlyDescendants_withoutIllegal:351->checkCommonAssertionForList:392 Expected: iterable over [Has name: aa, Has name: ab, Has name: _b] in any order but: No item matches: Has name: _b in [, ] [ERROR] Errors: [ERROR] UtilTest.testIsSymlink_ParentIsSymlink:286 » FileSystem C:\OpenSource\core\tar... [ERROR] AtomicFileWriterTest.symlinkToDirectory:80 » FileSystem C:\OpenSource\core\tar... [ERROR] PathRemoverTest.testForceRemoveFile_ParentIsSymbolicLink:184 » FileSystem C:\O... [ERROR] PathRemoverTest.testForceRemoveFile_SymbolicLink:153 » FileSystem C:\OpenSourc... [ERROR] PathRemoverTest.testForceRemoveRecursive_ContainsSymbolicLinks:373 » FileSystem [ERROR] PathRemoverTest.testForceRemoveRecursive_ParentIsSymbolicLink:411 » FileSystem [INFO] [ERROR] Tests run: 3712, Failures: 9, Errors: 6, Skipped: 28  
 

  
 
 
 
 

 
 
 

 
 
 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 unsubscr

[JIRA] (JENKINS-57663) Do not trigger all branch builds when regenerating a multibranchPipelineJob

2019-05-24 Thread costincarai...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Costin Caraivan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57663  
 
 
  Do not trigger all branch builds when regenerating a multibranchPipelineJob   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2019-05-24 14:33  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Costin Caraivan  
 

  
 
 
 
 

 
 This is a super annoying issue that makes the jobDsl plugin really hard to use in some situations.   When it regenerates a multibranchPipeline job, *all* the branch builds are triggered. Of course, this can mean that *hundreds* of builds are suddenly scheduled. This should, in my opinion, either:   a) never happen b) or only happen when there are actual configuration changes.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57186) New View href is an absolute URL but other menu items are relative URLs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57186  
 
 
  New View href is an absolute URL but other menu items are relative URLs   
 

  
 
 
 
 

 
Change By: 
 Nisarg Shah  
 
 
Comment: 
 I tried applying the proposed solution, but few tests failed. So this solution won't work [~nap].  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57186) New View href is an absolute URL but other menu items are relative URLs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57186  
 
 
  New View href is an absolute URL but other menu items are relative URLs   
 

  
 
 
 
 

 
Change By: 
 Nisarg Shah  
 
 
Comment: 
 Test Failures : [INFO] Results:[INFO][ERROR] Failures:[ERROR] FilePathTest.isDescendant_regularSymlinks:960[ERROR] FilePathTest.isDescendant_worksEvenInSymbolicWorkspace:1110[ERROR] UtilTest.resolveSymlinkToFile:570[ERROR] NewViewLinkTest.getActionsHasPermission:55 expected:<[https://127.0.0.1:8080]/newView> but was:<[]/newView>[ERROR] NewViewLinkTest.getActionsNoPermission:68 expected:<[https://127.0.0.1:8080]/newView> but was:<[]/newView>[ERROR] VirtualFileTest.forFilePath_isDescendant:277->checkCommonAssertionForIsDescendant:312[ERROR] VirtualFileTest.forFilePath_listOnlyDescendants_withoutIllegal:366->checkCommonAssertionForList:392Expected: iterable over [Has name: aa, Has name: ab, Has name: _b] in any order but: No item matches: Has name: _b in [, ][ERROR] VirtualFileTest.forFile_isDescendant:261->checkCommonAssertionForIsDescendant:312[ERROR] VirtualFileTest.forFile_listOnlyDescendants_withoutIllegal:351->checkCommonAssertionForList:392Expected: iterable over [Has name: aa, Has name: ab, Has name: _b] in any order but: No item matches: Has name: _b in [, ][ERROR] Errors:[ERROR] UtilTest.testIsSymlink_ParentIsSymlink:286 » FileSystem C:\OpenSource\core\tar...[ERROR] AtomicFileWriterTest.symlinkToDirectory:80 » FileSystem C:\OpenSource\core\tar...[ERROR] PathRemoverTest.testForceRemoveFile_ParentIsSymbolicLink:184 » FileSystem C:\O...[ERROR] PathRemoverTest.testForceRemoveFile_SymbolicLink:153 » FileSystem C:\OpenSourc...[ERROR] PathRemoverTest.testForceRemoveRecursive_ContainsSymbolicLinks:373 » FileSystem[ERROR] PathRemoverTest.testForceRemoveRecursive_ParentIsSymbolicLink:411 » FileSystem[INFO][ERROR] Tests run: 3712, Failures: 9, Errors: 6, Skipped: 28  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57663) Do not trigger all branch builds when regenerating a multibranchPipelineJob

2019-05-24 Thread costincarai...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Costin Caraivan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57663  
 
 
  Do not trigger all branch builds when regenerating a multibranchPipelineJob   
 

  
 
 
 
 

 
Change By: 
 Costin Caraivan  
 

  
 
 
 
 

 
 This is a super annoying issue that makes the jobDsl plugin really hard to use in some situations. When it regenerates a multibranchPipeline job, * * all* *  the branch builds are triggered. Of course, this can mean that * * hundreds* *  of builds are suddenly scheduled. This should, in my opinion, either: a) never happenb) or only happen when there are actual configuration changes.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-46094) "Checkout over SSH" fails the build since it still uses HTTPS urls

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman commented on  JENKINS-46094  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Checkout over SSH" fails the build since it still uses HTTPS urls   
 

  
 
 
 
 

 
 Al Forbes 2.4.5 of github branch source.  For bitbucket, the fix is in 2.4.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184329.1502287878000.11562.1558709700365%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception

2019-05-24 Thread aaron.k....@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aaron Sua created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57664  
 
 
  On Release of a Version recieve a Null Pointer exception   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 jira-plugin  
 
 
Created: 
 2019-05-24 14:55  
 
 
Environment: 
 Jenkins version 2.164.3  Jira Plugin version 3.07  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Aaron Sua  
 

  
 
 
 
 

 
 After upgrading from Jenkins 2.107 and Jira Plugin 2.5 when executing the Release A Version step in a Jenkins job the output simply states: [JIRA] Marking version  in project  as released. FATAL: Unable to release jira version /: java.lang.NullPointerException Finished: FAILURE  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-57665) Hubotapprove does not exclude build_user from approve/abort

2019-05-24 Thread rashminai...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rashmi Nair created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57665  
 
 
  Hubotapprove does not exclude build_user from approve/abort   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Naresh Rayapati  
 
 
Components: 
 hubot-steps-plugin  
 
 
Created: 
 2019-05-24 15:00  
 
 
Environment: 
 TEST  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Rashmi Nair  
 

  
 
 
 
 

 
 Hi Team,   I am using below code where in hubotApprove command do not have my id in submitter list but still it lets me approve or abort when I trigger this pipeline:   stage ('Request Approval from #devOps on rocket.chat') { steps { wrap([$class: 'BuildUser']) { sh """USER=${BUILD_USER_ID}""" hubotSend site: "forge_trial", message: "Permission requested to delete ${params.project_name} - Other users please approve except $BUILD_USER_ID who has triggered the deletion" hubotApprove site: "forge_trial", message: "Proceed or Abort $BUILD_URL/input/", submitter: "a,b,c,d", tokens: "$BUILD_NUMBER, $JENKINS_URL"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-56775) Parameters are not replaced in the "Stream Codeline" field

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen assigned an issue to Paul Allen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56775  
 
 
  Parameters are not replaced in the "Stream Codeline" field   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Assignee: 
 Paul Allen  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-56775) Parameters are not replaced in the "Stream Codeline" field

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen started work on  JENKINS-56775  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198419.1553681537000.11583.1558713180421%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-49833) getApiJson: (url=...) failed due to Http error #403

2019-05-24 Thread kpshee...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Sheehan commented on  JENKINS-49833  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: getApiJson: (url="" failed due to Http error #403   
 

  
 
 
 
 

 
 I agree with Henryk Paluch, this is Jenkins calling Jenkins which gets 403 because we require authenticated users. Job status is updated so not really sure what this request is doing. We first saw this as a deny on our f/w but once we opened that up we see the 403.  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-56775) Parameters are not replaced in the "Stream Codeline" field

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated  JENKINS-56775  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56775  
 
 
  Parameters are not replaced in the "Stream Codeline" field   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198419.1553681537000.11595.1558713420256%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-56775) Parameters are not replaced in the "Stream Codeline" field

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen commented on  JENKINS-56775  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameters are not replaced in the "Stream Codeline" field   
 

  
 
 
 
 

 
 https://swarm.workshop.perforce.com/changes/25655  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57371) error message when building PR

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated  JENKINS-57371  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57371  
 
 
  error message when building PR   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Status: 
 In Review Closed  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 2.5.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.11600.1558714200375%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-52697) Logstash plugin: support JCasC

2019-05-24 Thread robin.sm...@forgerock.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Robin Smith commented on  JENKINS-52697  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Logstash plugin: support JCasC   
 

  
 
 
 
 

 
 Brilliant - thank you!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-57583) "Ignore target branch" no longer working

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57583  
 
 
  "Ignore target branch" no longer working   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

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

[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call