[JIRA] (JENKINS-53181) Jacoco adapter does not work if Jacoco plugin is installed too

2018-08-21 Thread baradari.ra...@googlemail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramin Baradari created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53181  
 
 
  Jacoco adapter does not work if Jacoco plugin is installed too   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Share Cheng  
 
 
Components: 
 code-coverage-api-plugin  
 
 
Created: 
 2018-08-22 05:50  
 
 
Environment: 
 Jenkins Version: 2.138  JRE Version: 1.8.0_131-b11  OS: Linux 64bit  Container: Wildfly 10.0   Installed plugins:  * ace-editor 1.1 true  * analysis-core 1.95 true  * ant 1.8 true  * antisamy-markup-formatter 1.5 true  * apache-httpcomponents-client-4-api 4.5.5-3.0 true  * authentication-tokens 1.3 true  * bouncycastle-api 2.16.3 true  * branch-api 2.0.20 true  * build-monitor-plugin 1.12+build.201805070054 true  * build-timeout 1.19 true  * buildtriggerbadge 2.9 true  * categorized-view 1.10 true  * checkstyle 3.50 true  * cloudbees-folder 6.5.1 true  * cobertura 1.12.1 true  * code-coverage-api 1.0.0 true  * command-launcher 1.2 true  * credentials 2.1.18 true  * credentials-binding 1.16 true  * dashboard-view 2.9.11 true  * description-setter 1.10 true  * disk-usage 0.28 true  * display-url-api 2.2.0 true  * docker-commons 1.13 true  * docker-workflow 1.17 true  * doclinks 0.6.1 true  * dry 2.50 true  * durable-task 1.25 true  * email-ext 2.63 true  * envinject 2.1.6 true  * envinject-api 1.5 true  * extended-choice-parameter 0.76 true  * extensible-choice-parameter 1.6.0 true  * external-monitor-job 1.7 true  * favorite 2.3.2 true  * findbugs 4.72 true  * git 3.9.1 true  * git-client 2.7.3 true  * git-parameter 0.9.4 true  * git-server 1.7 true  * gradle 1.29 true  * groovy 2.0 true  * handlebars 1.1.1 true  * handy-uri-templates-2-api 2.1.6-1.0 true  * htmlpublisher 1.16 true  * icon-shim 2.0.3 true  * jackson2-api 2.8.11.3 true  * jacoco 2.2.1 true  * javadoc 1.4 true  * jdk-tool 1.1 true  * jenkins-design-language 1.8.2 true  * jira 3.0.0 true  * jobConfigHistory 2.18 true  * jquery 1.12.4-0 true  * jquery-detached 1.2.1 true  * jsch 0.1.54.2 true  * junit 1.24 true  * ldap 1.20 true  * mailer 1.21 true  * mapdb-api 1.0.9.0 true  * matrix-auth 2.3 true  * matrix-project 1.13 true  * maven-plugin 3.1.2 true  * metrics 4.0.2.2 true  * momentjs 1.1.1 true  * nodenamecolumn 1.2 true  * pam-auth 1.3 true  * permissive-script-security 0.3 true  * pipeline-build-step 2.7 true  * pipeline-graph-analysis 1.7 true  * pipeline-input-step 2.8 true  * pipeline-milestone-step 1.3.1 true  * pipeline-model-api 1.3.1 true  * pipeline-model-declarative-agent 1.1.1 true  * pipeline-model-definition 1.3.1 true  * pipeline-model-extensions 1.3.1 true  * pipeline-rest-api 2.10 true  * pipeline-stage-step 2.3 true  * pipeline-stage-tags-metadata 1.3.1 true  * 

[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunit-version is a String

2018-08-21 Thread nfalc...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 The nunit version must be a valid version because in XSLT there are logics on how construct the classname and name of test case. Depending on the version some attributes or xml elements are not present. Please fill a bug to the tools to declare against which version of NUnit is compatible.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53165  
 
 
  Conversion Exception for NUnit2 XML Format when nunit-version is a String   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53180) [Octane UFT integration] Enforce discovery job is running on the master and not on slave

2018-08-21 Thread radislav.berkov...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Radi Berkovich created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53180  
 
 
  [Octane UFT integration] Enforce discovery job is running on the master and not on slave   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Radi Berkovich  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2018-08-22 05:17  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Radi Berkovich  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 Possibly the container is so hosed that just trying to fork sleep 3 from the controller process fails.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53179) Direct link to tests page in Blue Ocean

2018-08-21 Thread pfor...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Vasilevich created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53179  
 
 
  Direct link to tests page in Blue Ocean   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Ivan Meredith  
 
 
Components: 
 blueocean-display-url-plugin, display-url-api-plugin  
 
 
Created: 
 2018-08-22 02:27  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Pavel Vasilevich  
 

  
 
 
 
 

 
 We are using environment variables provided by Blue Ocean Display URL plugin: RUN_CHANGES_DISPLAY_URL=https:///job///display/redirect?page=changes RUN_DISPLAY_URL=https:///job///display/redirect However, when tests are failed we want to see direct link to "Tests" page in our notifications. I've tried to append ?page=tests to RUN_DISPLAY_URL, but it doesn't work. Looks like this is not supported internally.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

[JIRA] (JENKINS-53175) Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined

2018-08-21 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy edited a comment on  JENKINS-53175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined   
 

  
 
 
 
 

 
 404 for blueTestSummary should be fixed (see branch bug/JENKINS-53175 [https://github.com/jenkinsci/blueocean-plugin/tree/bug/JENKINS-53175] )but as investigated by [~nicu] there might an other 404  (sometimes)  for url such:{code:java}http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/temp3/runs/63/ {code} Did you get this 404 as well?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53175) Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined

2018-08-21 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy commented on  JENKINS-53175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined   
 

  
 
 
 
 

 
 404 for blueTestSummary should be fixed (see branch bug/JENKINS-53175 https://github.com/jenkinsci/blueocean-plugin/tree/bug/JENKINS-53175 ) but as investigated by Nicolae Pascu there might an other 404 for url such: 

 

http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/temp3/runs/63/  

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (TEST-124) Identify Mentor and update in webstie

2018-08-21 Thread siva.bankapa...@googlemail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Siva Bankapalli created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 test /  TEST-124  
 
 
  Identify Mentor and update in webstie   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Siva Bankapalli  
 
 
Components: 
 foo  
 
 
Created: 
 2018-08-22 02:05  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Siva Bankapalli  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-19754) Jenkins/EnvInject incorrectly sets ${WORKSPACE} on slave node

2018-08-21 Thread barn...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Barnish commented on  JENKINS-19754  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins/EnvInject incorrectly sets ${WORKSPACE} on slave node   
 

  
 
 
 
 

 
 We are still seeing this issue with jenkins 2.138 and envinject 2.16, although the workaround suggested above still seems to work. Does anyone know how to fix it properly?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53175) Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined

2018-08-21 Thread ol...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy assigned an issue to Olivier Lamy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53175  
 
 
  Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined   
 

  
 
 
 
 

 
Change By: 
 Olivier Lamy  
 
 
Assignee: 
 Olivier Lamy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-50800) workspace/* are not cleaned on SCM change.

2018-08-21 Thread mh...@tivo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Hall commented on  JENKINS-50800  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: workspace/* are not cleaned on SCM change.   
 

  
 
 
 
 

 
 Just so you know, any person with 'job change' permissions, and a jenkins server with config files stored in .git in $JENKINS_HOME, that user can effectively destroy/DOS the jenkins instance. Maybe someone will do something with this bug, because it's kind of dangerous.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53178) Unable to download artifacts

2018-08-21 Thread revanth.alampa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 revanth alampally created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53178  
 
 
  Unable to download artifacts   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Eyal Ben Moshe  
 
 
Components: 
 artifactory-plugin  
 
 
Created: 
 2018-08-21 22:39  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 revanth alampally  
 

  
 
 
 
 

 
 I am trying to do a simple download of a tar.gz  from a repository in our artifactory. I am using the following in our Jenkinsfile to test the spec. def downloadSpec = """{ "files": [ { "pattern": "${ARTIFACTORY_URI}/${ARTIFACTORY_PKGS_REPO}/${ARTIFACTORY_APPCENTER_HOME}/charts/${APPCENTER_VERSION}/appcenter-${APPCENTER_VERSION}.tgz", "target": "${OUTPUT_DIR}/", "flat": true } ] }""" server.download(downloadSpec) I do not see any error on running the Jenkinsfile but nothing gets downloaded in the target dir. The output even says " Downloading artifacts using pattern: "generated_url" " When I click on generated_url the tar.gz gets downloaded.  I don't think I am missing anything. Let me know if I am doing something wrong here.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed

2018-08-21 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref commented on  JENKINS-49546  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed   
 

  
 
 
 
 

 
 Fwiw, the two warnings in are addressed by JENKINS-50457  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52509) WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.PluginImpl$1

2018-08-21 Thread mobrock...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rouke Broersma commented on  JENKINS-52509  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.PluginImpl$1   
 

  
 
 
 
 

 
 The first thing I would recommend is if the selenium hub is reachable on the configured url and port, as on first glance it seems to me like the port you are using is simply not accessible from the location at which you run the tests.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2

2018-08-21 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated  JENKINS-52946  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52946  
 
 
  Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Status: 
 Fixed but Unreleased Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2

2018-08-21 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated  JENKINS-52946  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 https://github.com/jenkinsci/envinject-plugin/pull/131  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52946  
 
 
  Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2

2018-08-21 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52946  
 
 
  Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Status: 
 Reopened Resolved  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52947) Attempt to (de-)serialize anonymous class com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerParameters$ParameterMode$1

2018-08-21 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref commented on  JENKINS-52947  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Attempt to (de-)serialize anonymous class com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerParameters$ParameterMode$1   
 

  
 
 
 
 

 
 Jesse Glick?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52947) Attempt to (de-)serialize anonymous class com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerParameters$ParameterMode$1

2018-08-21 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref commented on  JENKINS-52947  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Attempt to (de-)serialize anonymous class com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerParameters$ParameterMode$1   
 

  
 
 
 
 

 
 I suspect this is complaining about: https://github.com/jenkinsci/gerrit-trigger-plugin/blob/1ecb59ced215ccc36c97f42eaa35fb6fcdac8146/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerParameters.java#L624 specifically: https://github.com/jenkinsci/gerrit-trigger-plugin/blob/1ecb59ced215ccc36c97f42eaa35fb6fcdac8146/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerParameters.java#L628 and https://github.com/jenkinsci/gerrit-trigger-plugin/blob/1ecb59ced215ccc36c97f42eaa35fb6fcdac8146/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerParameters.java#L640 probably via: https://github.com/jenkinsci/gerrit-trigger-plugin/blob/a3bf98d1d4342900137a2739f3a7333ecf710898/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java#L213-L216  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread mich...@stieler.it (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Cornel commented on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 Almost. So as far as I understand Kubernetes simply "translates" the resource limit configuration and applies it when starting the Docker containers. I am pretty sure that I saw an IOException Out of memory with Gradle stacktrace during one of the builds. Thus, Docker is probably not killing the process but just prevents it to allocate more memory. I would expect the Gradle JVM to exit with non-zero exit code and the agent to recognize this and immediately mark the build as failed. I don't know if it does or what happens to the agent JVM and so on, though.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52509) WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.PluginImpl$1

2018-08-21 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref commented on  JENKINS-52509  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.PluginImpl$1   
 

  
 
 
 
 

 
 Fwiw, the warning and the error aren't related. I've tried to fix some instances of the warning. You're welcome to have bugs for both (personally, if I were you, I'd be more interested in the error than the warning...). From an IT/Ops perspective, I'd hope there's more logging to report: the url/host/port/ip that was failing... (and if not, I'd want it added...)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52948) Attempt to (de-)serialize anonymous class in gitclient

2018-08-21 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52948  
 
 
  Attempt to (de-)serialize anonymous class in gitclient   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-50457) Attempt to (de-)serialize anonymous class

2018-08-21 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref updated  JENKINS-50457  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50457  
 
 
  Attempt to (de-)serialize anonymous class   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-50457) Attempt to (de-)serialize anonymous class

2018-08-21 Thread jsoref+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Soref assigned an issue to Josh Soref  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50457  
 
 
  Attempt to (de-)serialize anonymous class   
 

  
 
 
 
 

 
Change By: 
 Josh Soref  
 
 
Assignee: 
 Josh Soref  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53164) Rebrand from Essentials to Evergreen the "essentials jenkins plugin"

2018-08-21 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53164  
 
 
  Rebrand from Essentials to Evergreen the "essentials jenkins plugin"   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 

  
 
 
 
 

 
 {{Essentials Jenkins plugin}} => * rename the plugin display name* change the artifactId (we generally do not do this, but I think in this case we should because it's 1) still early stage and 2) nobody is ever supposed to install this plugin manually anyway * rename the repo* rename the JIRA component  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 Michael Cornel that is useful information indeed. If I understand correctly, some out of memory condition is resulting in something (Kubernetes? Docker? the Linux kernel?) deciding to just kill off processes such as the wrapper script. Is the agent JVM also being killed? Whatever the case, Jenkins is then behaving appropriately in marking the sh step as a failure (the -1 pseudo exit code represents the fact that the actual exit code of the process is unknown and something fundamental went wrong), but is not clearly explaining the real problem.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53164) Rebrand from Essentials to Evergreen the "essentials jenkins plugin"

2018-08-21 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus started work on  JENKINS-53164  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53147) Rebrand from Essentials to Evergreen

2018-08-21 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus started work on  JENKINS-53147  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53128) Chinese Localization

2018-08-21 Thread fifteenknots...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Weber edited a comment on  JENKINS-53128  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Chinese Localization   
 

  
 
 
 
 

 
 Thank you for helping out with the translation!I10n for the plugin comes in commit [i10n| [ https://github.com/jenkinsci/cmakebuilder-plugin/commit/06acf166a80a1c9d2191b019a29528cf0ff3cf08]. The file {{messages.properties}} contains any String that comes from java code. Feel free to complain, if the file lacks documentation that suits your needs (e.g. which string shows up where and when).Please report here, if you need more text/items to be internationalized.I would prefer to delay merge permission grant until after the first pull request.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves

2018-08-21 Thread adam.broussea...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Brousseau commented on  JENKINS-24824  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Asynchronous cleanup not removing renamed workspace directories on slaves   
 

  
 
 
 
 

 
 We also have this issue but only on Windows slaves (connected through Cygwin SSH).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-46972) Exiting the "Create your first Pipeline" flow to go to Classic produces a 404

2018-08-21 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46972  
 
 
  Exiting the "Create your first Pipeline" flow to go to Classic produces a 404   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Labels: 
 cb-triaged testing-notes-reviewed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-50116) Last changes history becomes empty after Jenkins restart

2018-08-21 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-50116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Last changes history becomes empty after Jenkins restart   
 

  
 
 
 
 

 
 The project action looks like it should be created in a https://javadoc.jenkins.io/jenkins/model/TransientActionFactory.html for the appropriate job type (AbstractProject) rather than stored with the job. It could be attached to any project, and getIcon overloaded to only show when one of the newest N builds has an Action attached. This would be more efficient than always traversing all builds.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53175) Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined

2018-08-21 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53175  
 
 
  Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 

  
 
 
 
 

 
 *Summary*Intermittently, when running a simple Declarative Pipeline, a stage which I know to have steps in it will be shown as having no steps. The browser console reports two errors in quick succession when this takes place.*Frequency* Maybe 1 out Probably 50%  of  every 3 attempts  the time .*Steps to recreate*1. Create a new, empty repository in an SCM you already have set up for use with Blue Ocean. In my case this is a Bitbucket server.2. Go through the Blue Ocean create flow, specifying the project and repo.3. Create a new Pipeline using the Pipeline Editor. This doesn't need to be anything fancy - mine looks exactly like this:{code:none}pipeline {  agent any  stages {stage('I won a hat last year') {  steps {echo 'I have not won another since, though.'sh 'cat /var/log/jenkins/jenkins.log.1'  }}  }}{code}4. Run the pipeline several times, and look for the "live" pipeline view to report that the stage doesn't have any steps in it, as seen in this screenshot: !image-2018-08-21-14-11-03-061.png|thumbnail! 5. This is when the  error has occurred. The browser console will show the following:{code:none}There has been an error while trying to get the run data. TypeError: newArray.slice is not a functionat LogConsole.componentWillReceiveProps (jenkins-js-extension.js:93380)at ReactCompositeComponentWrapper.updateComponent (jenkins-design-language.js:49436)at ReactCompositeComponentWrapper.receiveComponent (jenkins-design-language.js:49369)at Object.receiveComponent (jenkins-design-language.js:55499)at ReactCompositeComponentWrapper._updateRenderedComponent (jenkins-design-language.js:49576)at ReactCompositeComponentWrapper._performComponentUpdate (jenkins-design-language.js:49546)at ReactCompositeComponentWrapper.updateComponent (jenkins-design-language.js:49467)at ReactCompositeComponentWrapper.receiveComponent (jenkins-design-language.js:49369)at Object.receiveComponent (jenkins-design-language.js:55499)at Object.updateChildren (jenkins-design-language.js:48731)at ReactDOMComponent._reconcilerUpdateChildren (jenkins-design-language.js:54357)at ReactDOMComponent._updateChildren (jenkins-design-language.js:54456)at ReactDOMComponent.updateChildren (jenkins-design-language.js:54443)at ReactDOMComponent._updateDOMChildren (jenkins-design-language.js:50747)at ReactDOMComponent.updateComponent (jenkins-design-language.js:50565)at ReactDOMComponent.receiveComponent (jenkins-design-language.js:50527)at Object.receiveComponent (jenkins-design-language.js:55499)at Object.updateChildren (jenkins-design-language.js:48731)at ReactDOMComponent._reconcilerUpdateChildren (jenkins-design-language.js:54357)at ReactDOMComponent._updateChildren (jenkins-design-language.js:54456)at ReactDOMComponent.updateChildren 

[JIRA] (JENKINS-53175) Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined

2018-08-21 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz commented on  JENKINS-53175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined   
 

  
 
 
 
 

 
 I'd like to bump the severity of this up. It's more easily found than I first thought, and when you do hit it, the screen going non-responsive is pretty severe.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53128) Chinese Localization

2018-08-21 Thread fifteenknots...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Weber commented on  JENKINS-53128  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Chinese Localization   
 

  
 
 
 
 

 
 Thank you for helping out with the translation! I10n for the plugin comes in commit [i10n|https://github.com/jenkinsci/cmakebuilder-plugin/commit/06acf166a80a1c9d2191b019a29528cf0ff3cf08. The file messages.properties contains any String that comes from java code. Feel free to complain, if the file lacks documentation that suits your needs (e.g. which string shows up where and when). Please report here, if you need more text/items to be internationalized. I would prefer to delay merge permission grant until after the first pull request.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53175) Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined

2018-08-21 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53175  
 
 
  Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread mich...@stieler.it (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Cornel edited a comment on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 Ok, it took me a while to actually reproduce this error message.I have to: * Start Gradle manually, so in my case {{sh('./gradlew -d --no-daemon clean bootJar')}} – it does not occur if I start the Gradle build using the Artifactory Jenkins plugin * Configure the Kubernetes build slave with a memory limit of {{512Mi}} which seems to be not enough and results in a (silent) out of memory problemSo it appears that durable  tasks -task  is not actually aborting the build but correctly detects that the process is not running any more. Maybe the error message could give a hint that the most probable reason for the log file not being touched is that the wrapper script has actually died?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread mich...@stieler.it (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Cornel edited a comment on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 Ok, it took me a while to actually reproduce this error message.I have to: * Start Gradle manually, so in my case  {{ sh('./gradlew -d --no-daemon clean bootJar') }}  – it does not occur if I start the Gradle build using the Artifactory Jenkins plugin * Configure the Kubernetes build slave with a memory limit of  {{  512Mi }}  which seems to be not enough and results in a (silent) out of memory problemSo it appears that durable tasks is not actually aborting the build but correctly detects that the process is not running any more. Maybe the error message could give a hint that the most probable reason for the log file not being touched is that the wrapper script has actually died?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53171) Clients not properly receiving a delta [empty] update level

2018-08-21 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy commented on  JENKINS-53171  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Clients not properly receiving a delta [empty] update level   
 

  
 
 
 
 

 
 I should add, the behavior of the update service is correct  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread mich...@stieler.it (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Cornel commented on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 Ok, it took me a while to actually reproduce this error message. I have to: 
 
Start Gradle manually, so in my case sh('./gradlew -d --no-daemon clean bootJar') – it does not occur if I start the Gradle build using the Artifactory Jenkins plugin 
Configure the Kubernetes build slave with a memory limit of 512Mi which seems to be not enough and results in a (silent) out of memory problem 
 So it appears that durable tasks is not actually aborting the build but correctly detects that the process is not running any more. Maybe the error message could give a hint that the most probable reason for the log file not being touched is that the wrapper script has actually died?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-16944) Use div instead of tables for the layout of the dashboard

2018-08-21 Thread tobias.gruetzmac...@inform-software.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tobias Gruetzmacher assigned an issue to Tobias Gruetzmacher  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-16944  
 
 
  Use div instead of tables for the layout of the dashboard   
 

  
 
 
 
 

 
Change By: 
 Tobias Gruetzmacher  
 
 
Assignee: 
 Marco Ambu Tobias Gruetzmacher  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53176) How to safely rotate master.key and hudson.util.Secret?

2018-08-21 Thread block....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon B created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53176  
 
 
  How to safely rotate master.key and hudson.util.Secret?   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Stephen Connolly  
 
 
Components: 
 credentials-plugin  
 
 
Created: 
 2018-08-21 19:34  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jon B  
 

  
 
 
 
 

 
 I previously checked in my entire Jenkins configuration into git for backup purposes. These days, I snapshot EBS volumes for backup. In the interests of security, I would like to rotate the sensitive files in the Jenkins configuration in order to help keep things secure. Those files appear to be: 
 
secrets/hudson.util.Secret 
secrets/master.key 
 Can someone please advise me as to how I can safely rotate those keys while also keeping my Jenkins server running smoothly?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[JIRA] (JENKINS-23582) Cant create new jobs after install

2018-08-21 Thread tobias.gruetzmac...@inform-software.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tobias Gruetzmacher closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 There isn't enough information to reproduce this issue. If this is still a problem, please describe the issue in more detail (and its relation to the dashboard-view-plugin) and reopen.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-23582  
 
 
  Cant create new jobs after install   
 

  
 
 
 
 

 
Change By: 
 Tobias Gruetzmacher  
 
 
Status: 
 In Progress Closed  
 
 
Assignee: 
 Peter Hayes  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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

[JIRA] (JENKINS-16944) Use div instead of tables for the layout of the dashboard

2018-08-21 Thread tobias.gruetzmac...@inform-software.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tobias Gruetzmacher stopped work on  JENKINS-16944  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Tobias Gruetzmacher  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53074) Upgrade bouncycastle-api-plugin to current dependency

2018-08-21 Thread jthomp...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53074  
 
 
  Upgrade bouncycastle-api-plugin to current dependency   
 

  
 
 
 
 

 
Change By: 
 Jeff Thompson  
 
 
Released As: 
 Released in bouncycastle-api 2.17.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53074) Upgrade bouncycastle-api-plugin to current dependency

2018-08-21 Thread jthomp...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53074  
 
 
  Upgrade bouncycastle-api-plugin to current dependency   
 

  
 
 
 
 

 
Change By: 
 Jeff Thompson  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53074) Upgrade bouncycastle-api-plugin to current dependency

2018-08-21 Thread jthomp...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-53074  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Upgrade bouncycastle-api-plugin to current dependency   
 

  
 
 
 
 

 
 Released in bouncycastle-api 2.17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 Craig Rodrigues that logger is unlikely to be helpful in this case. Really there is no Java logging that is very pertinent to this issue (a -1 return status which vanishes iff HEARTBEAT_CHECK_INTERVAL is increased)—all the meaningful messages are already sent to the build log as of PR 57. Root cause diagnosis would involve using an interactive shell to somehow figure out why jenkins-log.txt is not getting touched at least every three seconds. (More often when there is active log output from the user process.) Possibly it is getting touched, but the agent JVM in BourneShellScript.exitStatus is not seeing the right timestamp, or is somehow misinterpreting what it sees; or perhaps one of the two controller sh processes (the one usually inside sleep 3) has been killed by something (such as was claimed in JENKINS-50892).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48300  
 
 
  Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 durable-task PR 81 at least increases the grace period, pending some determination of root cause by users seeing this issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Reopened In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53171) Clients not properly receiving a delta [empty] update level

2018-08-21 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy commented on  JENKINS-53171  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Clients not properly receiving a delta [empty] update level   
 

  
 
 
 
 

 
 It looks like the versions table is completely empty. So the client is not sending the right information along there. Woops!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues commented on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 Michael Cornel Can you add a new logger to your Jenkins system by navigating to Manage Jenkins -> System Log, and creating a new logger org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep set to ALL . Then re-run your pipeline looking for debugging messages to highlight where the problem might be? That logger is defined here: https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java#L71  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53175) Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined

2018-08-21 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz commented on  JENKINS-53175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined   
 

  
 
 
 
 

 
 While the browser is not responding, it's still possible to check things out in the dev console. Mostly there's nothing going on when I click around, but occasionally, I'll see the following 404: 

 

blueocean-core-js.js:54767 GET http://172.18.40.95:8080/blue/rest/organizations/jenkins/pipelines/jenkins-42995/branches/master/runs/14/blueTestSummary/ 404 (Not Found)
 

  Another har file has been attached for that one now as well. Might be a separate issue, that's unclear.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53175) Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined

2018-08-21 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53175  
 
 
  Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Attachment: 
 blueTestSummary.har  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 I do not believe this is related to JENKINS-37575.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52313) Storing binary file in shared library resources folder

2018-08-21 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum edited a comment on  JENKINS-52313  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Storing binary file in shared library resources folder   
 

  
 
 
 
 

 
 [~quas] The problem is that {{UTF-8}} is a variable length encoding so any byte  starting with a 1  whose highest bit is set  will not round-trip correctly. You might be able to use a fixed-length encoding like {{Windows-1252}} in your most recent snippet to get things working, but {{libraryResource}} currently doesn't take an encoding parameter so you would have to change your system default to use that as a workaround. It seems better to explicitly support this use case.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53175) Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined

2018-08-21 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz commented on  JENKINS-53175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined   
 

  
 
 
 
 

 
 Got it. Har file is here. Of note - when I hit this problem, the X icon at top left (to close the Run Details page) is inop. The only way to get the screen to respond again is via a full page refresh.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53175) Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined

2018-08-21 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53175  
 
 
  Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Attachment: 
 har-file.har  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Jesse Glick  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48300  
 
 
  Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Sam Van Oort Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Do not attempt to call System.setProperty from within a sandboxed script. Whitelisting this would constitute a possibly severe vulnerability. The default value for the check interval should likely be higher. Still, presence of this issue suggests that there is something wrong with the agent’s filesystem, or that control processes are being killed. Not sure why this marked fixed. PR 57 merely added better logging; it did not change the behavior otherwise.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48300  
 
 
  Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you 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-48300) Pipeline shell step aborts prematurely with ERROR: script returned exit code -1

2018-08-21 Thread mich...@stieler.it (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Cornel commented on  JENKINS-48300  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline shell step aborts prematurely with ERROR: script returned exit code -1   
 

  
 
 
 
 

 
 I seem to have the same problem with durable-task 1.25. Trying to build an (empty) Spring boot app using Artifactory Maven plugin on a Kuberenetes slave, the build script was aborted with a link to this issue. After setting the property in the pipeline script, (which fixed it), I noticed that there is a rather long time between two log statements:   17:36:55.137 [DEBUG] [org.gradle.initialization.DefaultGradlePropertiesLoader] Found system project properties: [] >> Without the increased timeout, the pipeline was aborted here before the next log entry 17:36:57.323 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationExecutor] Build operation 'Apply script settings.gradle to settings 'ci-test'' started   I am not using NFS but of course the build slave is a virtual machine which will be a little slower.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53018) Windows slave service does not connect via JNLP4

2018-08-21 Thread jthomp...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-53018  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows slave service does not connect via JNLP4   
 

  
 
 
 
 

 
 I have an agent successfully running on a Windows 10 machine using JNLP4. I followed much the same procedure as described, except that I didn't start by having any JNLP2 enabled. I don't know how that would make a difference. I believe many other people are successfully running JNLP4. I suspect there is an environmental or configuration issue. I recommend checking the configuration carefully. Make sure versions are up to date. It would require much more details on exactly how this problem occurs to make any progress with it. And an indication of how there is a defect.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52413) My First Test

2018-08-21 Thread imoutsat...@msn.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos updated  JENKINS-52413  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52413  
 
 
  My First Test   
 

  
 
 
 
 

 
Change By: 
 Ioannis Moutsatsos  
 
 
Status: 
 Fixed but Unreleased Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-49894) Active Choices Reactive Reference Parameter triggering the groovy script twice

2018-08-21 Thread imoutsat...@msn.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos commented on  JENKINS-49894  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active Choices Reactive Reference Parameter triggering the groovy script twice   
 

  
 
 
 
 

 
 What version of AC are you working with. Can you please, report if this issue is present in the most recent AC plugin v2.1. Thank you.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53045) Plugin trips FARGATE rate limit.

2018-08-21 Thread ddum...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dan Dumont commented on  JENKINS-53045  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plugin trips FARGATE rate limit.   
 

  
 
 
 
 

 
 The default rate-limit is 1/sec  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-51296) Project renaming is not propagated to Active Choices projectName

2018-08-21 Thread imoutsat...@msn.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos commented on  JENKINS-51296  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Project renaming is not propagated to Active Choices projectName   
 

  
 
 
 
 

 
 Testing today. Thanks Bruno P. Kinoshita!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-51501) Parameterized Trigger Plugin Dynamic downstream projects fails "array out of bounds"

2018-08-21 Thread imoutsat...@msn.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos edited a comment on  JENKINS-51501  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Trigger Plugin Dynamic downstream projects fails "array out of bounds"   
 

  
 
 
 
 

 
 Is it an issue with AC or with the parametrized build plugin . ?  Replace the AC with a String parameter ,  and test by passing in the same string as it is generated by the AC script.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-51501) Parameterized Trigger Plugin Dynamic downstream projects fails "array out of bounds"

2018-08-21 Thread imoutsat...@msn.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos commented on  JENKINS-51501  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Trigger Plugin Dynamic downstream projects fails "array out of bounds"   
 

  
 
 
 
 

 
 Is it an issue with AC or with the parametrized build plugin. Replace the AC with a String parameter and test by passing in the same string as it is generated by the AC script.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53175) Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined

2018-08-21 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53175  
 
 
  Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined   
 

  
 
 
 
 

 
 If I can find a reliable way to recreate this, I'll grab a .har file and attach it.  
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Labels: 
 cb-triaged  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53175) Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined

2018-08-21 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53175  
 
 
  Intermittent: Unhandled Rejection: "TypeError: Cannot read property '_links' of undefined   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2018-08-21-14-11-03-061.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2018-08-21 18:17  
 
 
Environment: 
 Jenkins:  Core: 2.136  Blue Ocean 1.8.2  All other plugins at experimental update center levels   
 
 
Priority: 
  Major  
 
 
Reporter: 
 Karl Shultz  
 

  
 
 
 
 

 
 Summary Intermittently, when running a simple Declarative Pipeline, a stage which I know to have steps in it will be shown as having no steps. The browser console reports two errors in quick succession when this takes place. Frequency Maybe 1 out of every 3 attempts. Steps to recreate 1. Create a new, empty repository in an SCM you already have set up for use with Blue Ocean. In my case this is a Bitbucket server. 2. Go through the Blue Ocean create flow, specifying the project and repo. 3. Create a new Pipeline using the Pipeline Editor. This doesn't need to be anything fancy - mine looks exactly like this: 

 

pipeline {
  agent any
  stages {
stage('I won a hat last year') {
  steps {
echo 'I have not won another since, though.'
sh 'cat /var/log/jenkins/jenkins.log.1'
  }
}
  }
}
 

 4. Run the 

[JIRA] (JENKINS-52413) My First Test

2018-08-21 Thread imoutsat...@msn.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos updated  JENKINS-52413  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Someone is doing live tests on JIRA!  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52413  
 
 
  My First Test   
 

  
 
 
 
 

 
Change By: 
 Ioannis Moutsatsos  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Won't Do  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52644) Active choice plugin - does not run jql query of jira plugin

2018-08-21 Thread imoutsat...@msn.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos commented on  JENKINS-52644  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active choice plugin - does not run jql query of jira plugin
 

  
 
 
 
 

 
 Please, insure that you are returning a string array as it is required for most Active choices, or formatted HTML if you are using AC Reactive Reference parameter  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52313) Storing binary file in shared library resources folder

2018-08-21 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum updated  JENKINS-52313  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Support for Base64 encoding has been added to Pipeline: Shared Groovy Libraries 2.10 and Pipeline: Basic Steps 2.8.1 (or 2.10 if you are on Jenkins 2.121).  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52313  
 
 
  Storing binary file in shared library resources folder   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 workflow-cps-global-lib 2.10, workflow-basic-steps 2.8.1, workflow-basic-steps 2.10  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
You received this message because you 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-53174) Improve documentation

2018-08-21 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo updated  JENKINS-53174  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53174  
 
 
  Improve documentation   
 

  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53174) Improve documentation

2018-08-21 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53174  
 
 
  Improve documentation   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Ivan Fernandez Calvo  
 
 
Components: 
 ssh-slaves-plugin  
 
 
Created: 
 2018-08-21 18:02  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ivan Fernandez Calvo  
 

  
 
 
 
 

 
 Create configuration guide and changelog on the GitHub repo  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
  

[JIRA] (JENKINS-53174) Improve documentation

2018-08-21 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo started work on  JENKINS-53174  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ivan Fernandez Calvo  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52419) Blue Ocean Test Results have no duration

2018-08-21 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Marking as fixed, as described above. The fix PR is 1794.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52419  
 
 
  Blue Ocean Test Results have no duration   
 

  
 
 
 
 

 
Change By: 
 Karl Shultz  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52419) Blue Ocean Test Results have no duration

2018-08-21 Thread kshu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Shultz commented on  JENKINS-52419  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean Test Results have no duration   
 

  
 
 
 
 

 
 Hi inbar rose, Jason Charrier, and Felix Geisendörfer - Craig Rodrigues recently submitted a PR for exactly this issue, and that PR has been merged to master. Felix was on the right track with the milliseconds thing. I imagine that the next release of Blue Ocean will pick this up, so I'm going to mark this bug report as Resolved/Fixed, as well as referencing JENKINS-52944. Thanks for reporting it!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-51707) Failure - java.net.SocketException: Connection reset

2018-08-21 Thread coolteyg...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cooltey Feng edited a comment on  JENKINS-51707  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failure - java.net.SocketException: Connection reset   
 

  
 
 
 
 

 
 [~gront] Yes, I've tried  to  add couple proxy but it still  does  not  works  work .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-51707) Failure - java.net.SocketException: Connection reset

2018-08-21 Thread coolteyg...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cooltey Feng commented on  JENKINS-51707  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failure - java.net.SocketException: Connection reset   
 

  
 
 
 
 

 
 Daniel Gront Yes, I've tried add couple proxy but it still not works.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52825) Blue Ocean - Need to see executors

2018-08-21 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues commented on  JENKINS-52825  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean - Need to see executors   
 

  
 
 
 
 

 
 Even though the UI is not perfect, even if it was merged as-is into the blueocean-dashboard and improved iteratively over time, that would be an improvement, and one more reason why I can use Blue Ocean as my "daily driver" and not have to shift back to the Classic UI.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53173) Allow Jenkins job to continue in case XCode Plugin is running tests and a test fails

2018-08-21 Thread mikel...@aol.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 MICHAEL LUPO updated  JENKINS-53173  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This feature indeed exists. It's under the "Advanced" settings. Sorry for the SPAM.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53173  
 
 
  Allow Jenkins job to continue in case XCode Plugin is running tests and a test fails   
 

  
 
 
 
 

 
Change By: 
 MICHAEL LUPO  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Won't Do  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-53173) Allow Jenkins job to continue in case XCODE Plugin is running tests and a test fails

2018-08-21 Thread mikel...@aol.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 MICHAEL LUPO created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53173  
 
 
  Allow Jenkins job to continue in case XCODE Plugin is running tests and a test fails   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 xcode-plugin  
 
 
Created: 
 2018-08-21 16:52  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 MICHAEL LUPO  
 

  
 
 
 
 

 
 There is no option to NOT abort the job when a test case fails and that test run was started via the XCode plugin.  This could be a benefit to some.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

[JIRA] (JENKINS-53173) Allow Jenkins job to continue in case XCode Plugin is running tests and a test fails

2018-08-21 Thread mikel...@aol.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 MICHAEL LUPO updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53173  
 
 
  Allow Jenkins job to continue in case XCode Plugin is running tests and a test fails   
 

  
 
 
 
 

 
Change By: 
 MICHAEL LUPO  
 
 
Summary: 
 Allow Jenkins job to continue in case  XCODE  XCode  Plugin is running tests and a test fails  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-26432) Allow shelving of Pipeline

2018-08-21 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-26432  
 
 
  Allow shelving of Pipeline   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Issue Type: 
 Bug New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-7923) Shelving a project which own a shared "Workspace" will cause Hudson to fail until restarted

2018-08-21 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-7923  
 
 
  Shelving a project which own a shared "Workspace" will cause Hudson to fail until restarted   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-7923) Shelving a project which own a shared "Workspace" will cause Hudson to fail until restarted

2018-08-21 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz commented on  JENKINS-7923  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Shelving a project which own a shared "Workspace" will cause Hudson to fail until restarted   
 

  
 
 
 
 

 
 efe4pj: Given all the changes made since Hudson-1.379  and the shelve plugin 0.3, I'll close this issue, please reopen if you reproduce on the latest (2.1) version of the plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-7923) Shelving a project which own a shared "Workspace" will cause Hudson to fail until restarted

2018-08-21 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz assigned an issue to Pierre Beitz  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-7923  
 
 
  Shelving a project which own a shared "Workspace" will cause Hudson to fail until restarted   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Assignee: 
 ashlux Pierre Beitz  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-17272) Shelve project requires an executor on the master

2018-08-21 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-17272  
 
 
  Shelve project requires an executor on the master   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-17272) Shelve project requires an executor on the master

2018-08-21 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz commented on  JENKINS-17272  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Shelve project requires an executor on the master   
 

  
 
 
 
 

 
 Manivannan Selvaraj the shelving will take place on the master, using a flyweight executor (ie not using a standard executor).   Leo Sager: as the shelving/unshelving is using flyweight executors now, I'll close this issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-18043) Shelve project - shelved project list empty

2018-08-21 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-18043  
 
 
  Shelve project - shelved project list empty   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-18043) Shelve project - shelved project list empty

2018-08-21 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz commented on  JENKINS-18043  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Shelve project - shelved project list empty   
 

  
 
 
 
 

 
 This bug report is very old, it shows an error in parsing, the parser was changed since then so I'll close the issue, Jan Seidel please reopen if you reproduce on the latest version of the plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52825) Blue Ocean - Need to see executors

2018-08-21 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues commented on  JENKINS-52825  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean - Need to see executors   
 

  
 
 
 
 

 
 I was able to run this plugin via mvn hpi:run The UI could be improved a bit, but it does work in terms of providing a view of executors inside Blue Ocean.   It would be nice of this plugin could be enhanced and merged into the blueocean-dashboard.   That would eliminate the need to switch back to the classic UI to view the status of executors.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-18043) Shelve project - shelved project list empty

2018-08-21 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz assigned an issue to Pierre Beitz  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-18043  
 
 
  Shelve project - shelved project list empty   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Assignee: 
 ashlux Pierre Beitz  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52825) Blue Ocean - Need to see executors

2018-08-21 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues commented on  JENKINS-52825  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean - Need to see executors   
 

  
 
 
 
 

 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-23983) "shelve project" does not work for inheritance projects

2018-08-21 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-23983  
 
 
  "shelve project" does not work for inheritance projects   
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Issue Type: 
 Bug New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-52825) Blue Ocean - Need to see executors

2018-08-21 Thread rodr...@freebsd.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Rodrigues updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52825  
 
 
  Blue Ocean - Need to see executors   
 

  
 
 
 
 

 
Change By: 
 Craig Rodrigues  
 
 
Attachment: 
 Screen Shot 2018-08-21 at 8.21.47 AM.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-29903) Permission issue on

2018-08-21 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-29903  
 
 
  Permission issue on
 

  
 
 
 
 

 
Change By: 
 Pierre Beitz  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-29903) Permission issue on

2018-08-21 Thread pibe...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre Beitz commented on  JENKINS-29903  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Permission issue on
 

  
 
 
 
 

 
 Looks like a duplicate of JENKINS-10544. Fixes made for shelve plugin version 2.1 should  solve this. Closing, please reopen if you have a test case on this version.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


  1   2   3   >