[JIRA] (JENKINS-40805) Workspace not available when a slave is created by the Kubernetes plugin

2017-01-26 Thread olivier.lamb...@smals.be (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lambert commented on  JENKINS-40805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Workspace not available when a slave is created by the Kubernetes plugin   
 

  
 
 
 
 

 
 Raghu Pallikonda We also find this workaround. It works fine  but it's just a workaround ... We think a better solution should be implemented directlry in the core of Jenkins. 1. Check if the "where the project is run" is online 2. IF YES >> display this workspace 3. IF NO >> check if it's available on the master 4. IF YES, display it 5. IF NO, display error message  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-26379) Jenkins - ssh connection exception

2017-01-26 Thread akash.so...@siemens.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Akash Soori commented on  JENKINS-26379  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins - ssh connection exception   
 

  
 
 
 
 

 
 After adding valid Java path in Advanced... section of node configuration, above issue got resolved.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39411) javax.servlet.ServletException on job save after adding quality gates post-build action

2017-01-26 Thread m...@jochen-fuerbacher.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jochen A. Fürbacher commented on  JENKINS-39411  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: javax.servlet.ServletException on job save after adding quality gates post-build action   
 

  
 
 
 
 

 
 Cannot reproduce with Jenkins 2.28 (as well as 2.42) and Quality Gates Plugin 2.5.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41418) Permission denied while accessing workspace

2017-01-26 Thread mkuma...@in.ibm.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manjunath Kumatagi commented on  JENKINS-41418  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Permission denied while accessing workspace   
 

  
 
 
 
 

 
 I copy pasted exact code from above git repo and tried running it,.. Jos is waiting for slave to be up and running to run the job but slave never came up and here what I find in the kubernetes: 

 

[root@ kubernetes]# ./cluster/kubectl.sh get pods
NAMEREADY STATUS  RESTARTS   AGE
kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9   0/3   ContainerCreating   0  5m


[root@ kubernetes]# ./cluster/kubectl.sh describe pod kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9
Name:		kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9
Namespace:	default
Node:		127.0.0.1/127.0.0.1
Start Time:	Fri, 27 Jan 2017 01:47:41 -0500
Labels:		jenkins=slave
		jenkins/mypod=true
Status:		Pending
IP:		
Controllers:	
Containers:
  maven:
Container ID:	
Image:		maven:3.3.9-jdk-8-alpine
Image ID:		
Port:		
Command:
  cat
State:		Waiting
  Reason:		ContainerCreating
Ready:		False
Restart Count:	0
Volume Mounts:
  /etc/shared-secrets from volume-0 (rw)
  /home/jenkins from workspace-volume (rw)
  /var/run/secrets/kubernetes.io/serviceaccount from default-token-jqq8v (ro)
Environment Variables from:	
Environment Variables:
  JENKINS_SECRET:		0c574b20fd8c968fbc2671d550c454c8c15e9cbb4cb810055c9dae547ac428a5
  JENKINS_NAME:		kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9
  JENKINS_LOCATION_URL:	http://:8080/
  JENKINS_URL:		http://:8080
  JENKINS_JNLP_URL:		http://:8080/computer/kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9/slave-agent.jnlp
  HOME:			/home/jenkins
  golang:
Container ID:	
Image:		golang:1.6.3-alpine
Image ID:		
Port:		
Command:
  cat
State:		Waiting
  Reason:		ContainerCreating
Ready:		False
Restart Count:	0
Volume Mounts:
  /etc/shared-secrets from volume-0 (rw)
  /home/jenkins from workspace-volume (rw)
  /var/run/secrets/kubernetes.io/serviceaccount from default-token-jqq8v (ro)
Environment Variables from:	
Environment Variables:
  JENKINS_SECRET:		0c574b20fd8c968fbc2671d550c454c8c15e9cbb4cb810055c9dae547ac428a5
  JENKINS_NAME:		kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9
  JENKINS_LOCATION_URL:	http://:8080/
  JENKINS_URL:		http://:8080
  JENKINS_JNLP_URL:		http://:8080/computer/kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9/slave-agent.jnlp
  HOME:			/home/jenkins
  jnlp:
Container ID:	
Image:		jenkinsci/jnlp-slave:alpine
Image ID:		
Port:		
Args:
  0c574b20fd8c968fbc2671d550c454c8c15e9cbb4cb810055c9dae547ac428a5
  kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9
State:		Waiting
  Reason:		ContainerCreating
Ready:		False
Restart Count:	0
Volume Mounts:
  /etc/shared-secrets from volume-0 (rw)
  /home/jenkins from workspace-volume (rw)
  /var/run/secrets/kubernetes.io/serviceaccount from default-token-jqq8v (ro)
Environment Variables from:	
Environment Variables:
  JENKINS_SECRET:		0c574b20fd8c968fbc2671d550c454c8c15e9cbb4cb810055c9dae547ac428a5
  JENKINS_NAME:		kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9
  JENKINS_LOCATION_URL:	http://:8080/
  JENKINS_URL:		http://:8080
  JENKINS_JNLP_URL:		http://:8080/computer/

[JIRA] (JENKINS-36132) Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed.

2017-01-26 Thread robert.s...@zf.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Smid commented on  JENKINS-36132  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed.   
 

  
 
 
 
 

 
 Sorry, i thought main goal is that main goal is copying source files from workspace to the build folder. Do i have to start another issue? Here is part of log file: src/idr_libthmdl.c:162:1: Info 830: Location cited in prior message src/idr_libthmdl.c:289:1: Info 818: Pointer parameter 'f_struct10ms_p' (line 238) could be declared as pointing to const [MISRA 2012 Rule 8.13, advisory] src\idr_libthmdl.c:238:1: Info 830: Location cited in prior message I use Warnings plugin, pc-lint parser I do not know what tool creates this warnings, i do not have control over building process, it is black box for me, i just triggering omakes and collect results in Jenkins. But the message format looks ok to me  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41504) Jenkins integration in CentOs problem

2017-01-26 Thread mahen...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mahendiran Tha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41504  
 
 
  Jenkins integration in CentOs problem   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Attachments: 
 Jenkins.png  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2017/Jan/27 5:26 AM  
 
 
Environment: 
 Linux (CentOS -7)  
 
 
Labels: 
 jenkins git-plugin  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Mahendiran Tha  
 

  
 
 
 
 

 
 Hi Team, I'm new to Jenkins and i have installed GIT & Jenkins on same machine (Centos) and created sample project in jenkins dashboard. when i input GIT URL for a project i'm facing below error Failed to connect to repository : Error performing command: ls-remote -h git@192.168.10.124:PRODUCT_IMPORT HEAD. Note: I have created a Key without password and its updated in GIT Server. both Jenkins & GIT are available in same server.  
 

  
 
 
 
 

 
 
 

  

[JIRA] (JENKINS-41360) Steps need to be whitelisted and/or grouped

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow updated  JENKINS-41360  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41360  
 
 
  Steps need to be whitelisted and/or grouped   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41360) Steps need to be whitelisted and/or grouped

2017-01-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-41360  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Steps need to be whitelisted and/or grouped   
 

  
 
 
 
 

 
 Code changed in jenkins User: Keith Zantow Path: src/main/js/components/editor/AddStepSelectionSheet.jsx http://jenkins-ci.org/commit/blueocean-pipeline-editor-plugin/f7a05c372bb94ac1ed97f82054155536fc580663 Log: JENKINS-41360 - sort step selections (#21)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41503) JSON Schema issue: mapArgumentValue not accepting null

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41503  
 
 
  JSON Schema issue: mapArgumentValue not accepting null   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 

  
 
 
 
 

 
 Arguments with { isLiteral: true, "value": null } fail schema validation.I think this needs to allow null values: https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-api/src/main/resources/ast-schema.json#L50  or alternately, don't include those args in the JSON during conversion? Not sure if they are necessarily equivalent. Took this valid pipeline:{code}pipeline {agent {docker {image "httpd:2.4.12"args null}}stages {stage("foo") {steps {sh 'cat /usr/local/apache2/conf/extra/httpd-userdir.conf'sh 'echo "The answer is 42"'}}}}{code}which converts to the corresponding JSON, that no longer passes schema validation due to agent docker args null value:{code}{"pipeline": {"agent": {"type": "docker","arguments": [{"key": "image","value": { "isLiteral": true, "value": "httpd:2.4.12"}},{"key": "args","value": { "isLiteral": true, "value": null}}]},"stages": [{"name": "foo","branches": [{ "name": "default", "steps": [ { "name": "sh", "arguments": [ { "key": "script", "value": { "isLiteral": true, "value": "cat /usr/local/apache2/conf/extra/httpd-userdir.conf" } } ] }, { "name": "sh", "arguments": [ { "key": "script", "value": { "isLiteral": true, "value": "echo \"The answer is 42\"" } } ] } ]}]}]}}{code}  
 

  
 
 
 
 

 
 
 
  

[JIRA] (JENKINS-41503) JSON Schema issue: mapArgumentValue not accepting null

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41503  
 
 
  JSON Schema issue: mapArgumentValue not accepting null   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 

  
 
 
 
 

 
 Arguments with  _ { isLiteral: true, "value": null } _  fail schema validation.I think this needs to allow null values: https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-api/src/main/resources/ast-schema.json#L50Took this valid pipeline:{code}pipeline {agent {docker {image "httpd:2.4.12"args null}}stages {stage("foo") {steps {sh 'cat /usr/local/apache2/conf/extra/httpd-userdir.conf'sh 'echo "The answer is 42"'}}}}{code}which converts to the corresponding JSON, that no longer passes schema validation due to agent docker args null value:{code}{"pipeline": {"agent": {"type": "docker","arguments": [{"key": "image","value": { "isLiteral": true, "value": "httpd:2.4.12"}},{"key": "args","value": { "isLiteral": true, "value": null}}]},"stages": [{"name": "foo","branches": [{ "name": "default", "steps": [ { "name": "sh", "arguments": [ { "key": "script", "value": { "isLiteral": true, "value": "cat /usr/local/apache2/conf/extra/httpd-userdir.conf" } } ] }, { "name": "sh", "arguments": [ { "key": "script", "value": { "isLiteral": true, "value": "echo \"The answer is 42\"" } } ] } ]}]}]}}{code}  
 

  
 
 
 
 

 
 
 

 

[JIRA] (JENKINS-41503) JSON Schema issue: mapArgumentValue not accepting null

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41503  
 
 
  JSON Schema issue: mapArgumentValue not accepting null   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 pipeline-model-definition-plugin  
 
 
Created: 
 2017/Jan/27 4:15 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Keith Zantow  
 

  
 
 
 
 

 
 Arguments with _ { isLiteral: true, "value": null } _ fail schema validation. I think this needs to allow null values: https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-api/src/main/resources/ast-schema.json#L50 Took this valid pipeline: 

 

pipeline {
agent {
docker {
image "httpd:2.4.12"
args null
}
}
stages {
stage("foo") {
steps {
sh 'cat /usr/local/apache2/conf/extra/httpd-userdir.conf'
sh 'echo "The answer is 42"'
}
}
}
}
 

 which converts to the corresponding JSON, that no longer passes schema validation due to agent docker args null value: 

 

{
"pipeline": {
"agent": {
"type": "docker",
"arguments": [
{
"key": "image",
"value": {
"isLiteral": true,
"value": "httpd:2.4.12"
}
},
{
"key": "args",
"value": {
"isLiteral": true,
"value": null
}
}
 

[JIRA] (JENKINS-41360) Steps need to be whitelisted and/or grouped

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow updated  JENKINS-41360  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41360  
 
 
  Steps need to be whitelisted and/or grouped   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41360) Steps need to be whitelisted and/or grouped

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow started work on  JENKINS-41360  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Keith Zantow  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41502) Show triggers for jobs if upstream job (with link)

2017-01-26 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41502  
 
 
  Show triggers for jobs if upstream job (with link)   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Screen Shot 2017-01-27 at 2.43.13 pm.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2017/Jan/27 3:44 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Neale  
 

  
 
 
 
 

 
 When a pipeline triggers another pipeline, jenkins knows about this.  This can then be shown in various places as hyperlinks so you can navigate from a downstream job back up stream (see attached screen shot of classic).  A very useful feature.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 

[JIRA] (JENKINS-41360) Steps need to be whitelisted and/or grouped

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow commented on  JENKINS-41360  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Steps need to be whitelisted and/or grouped   
 

  
 
 
 
 

 
 Based on discussion, this is the list we want to have: 
 
Shell Script 
Print Message 
Enforce Time Limit 
Retry The body... 
Sleep 
Windows Bash Script 
Archive The artifacts 
Allocate Node .. then alphabetic.  
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41307) Alternate editor launch button

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41307  
 
 
  Alternate editor launch button   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 
 
Priority: 
 Minor Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41346) Validate and show errors at location

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow updated  JENKINS-41346  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41346  
 
 
  Validate and show errors at location   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41355) Default agent to 'any'

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow updated  JENKINS-41355  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41355  
 
 
  Default agent to 'any'   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41362) Script step to take a text box

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow updated  JENKINS-41362  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41362  
 
 
  Script step to take a text box   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41358) Round tripping missing data

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow updated  JENKINS-41358  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41358  
 
 
  Round tripping missing data   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41356) Need to be able to delete a whole stage

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow updated  JENKINS-41356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41356  
 
 
  Need to be able to delete a whole stage   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41358) Round tripping missing data

2017-01-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-41358  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Round tripping missing data   
 

  
 
 
 
 

 
 Code changed in jenkins User: Keith Zantow Path: package.json pom.xml src/main/js/components/Sheets.jsx src/main/js/components/editor/AgentConfiguration.jsx src/main/js/components/editor/EditorMain.jsx src/main/js/components/editor/EditorPage.jsx src/main/js/components/editor/EditorPipelineGraph.jsx src/main/js/components/editor/EditorStepDetails.jsx src/main/js/components/editor/EditorStepList.jsx src/main/js/components/editor/EnvironmentConfiguration.jsx src/main/js/components/editor/NewPipelineTemplate.json src/main/js/components/editor/ValidationMessageList.jsx src/main/js/components/editor/common.jsx src/main/js/components/editor/steps/GenericStepEditor.jsx src/main/js/components/editor/steps/PipelineScriptStepEditor.jsx src/main/js/components/properties/BooleanPropertyInput.jsx src/main/js/components/properties/DecimalPropertyInput.jsx src/main/js/components/properties/IntegerPropertyInput.jsx src/main/js/components/properties/ListPropertyInput.jsx src/main/js/components/properties/StringPropertyInput.jsx src/main/js/services/PipelineMetadataService.js src/main/js/services/PipelineStore.js src/main/js/services/PipelineSyntaxConverter.js src/main/js/services/PipelineValidator.js src/main/js/services/fetchClassic.js src/main/less/editor.less http://jenkins-ci.org/commit/blueocean-pipeline-editor-plugin/c341fddf36d316b599ec66df68fb7970b1d469a4 Log: Pipeline validation and cleanup (#20) 
 
basic working pipeline validator 
Restyle pipeline 
Handle top-level errors in parallel nodes 
Fix z-index issue, dont include empty args 
Fix default to agent any 
Default new to NewPipelineTemplate 
Editing child steps in container steps 
JENKINS-41358 - stage-level agent not exported 
JENKINS-41356 - Fix stage delete 
JENKINS-41362 - edit 'script' with a textbox 
Usage blurb for load/save dialog 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
  

[JIRA] (JENKINS-41356) Need to be able to delete a whole stage

2017-01-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-41356  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Need to be able to delete a whole stage   
 

  
 
 
 
 

 
 Code changed in jenkins User: Keith Zantow Path: package.json pom.xml src/main/js/components/Sheets.jsx src/main/js/components/editor/AgentConfiguration.jsx src/main/js/components/editor/EditorMain.jsx src/main/js/components/editor/EditorPage.jsx src/main/js/components/editor/EditorPipelineGraph.jsx src/main/js/components/editor/EditorStepDetails.jsx src/main/js/components/editor/EditorStepList.jsx src/main/js/components/editor/EnvironmentConfiguration.jsx src/main/js/components/editor/NewPipelineTemplate.json src/main/js/components/editor/ValidationMessageList.jsx src/main/js/components/editor/common.jsx src/main/js/components/editor/steps/GenericStepEditor.jsx src/main/js/components/editor/steps/PipelineScriptStepEditor.jsx src/main/js/components/properties/BooleanPropertyInput.jsx src/main/js/components/properties/DecimalPropertyInput.jsx src/main/js/components/properties/IntegerPropertyInput.jsx src/main/js/components/properties/ListPropertyInput.jsx src/main/js/components/properties/StringPropertyInput.jsx src/main/js/services/PipelineMetadataService.js src/main/js/services/PipelineStore.js src/main/js/services/PipelineSyntaxConverter.js src/main/js/services/PipelineValidator.js src/main/js/services/fetchClassic.js src/main/less/editor.less http://jenkins-ci.org/commit/blueocean-pipeline-editor-plugin/c341fddf36d316b599ec66df68fb7970b1d469a4 Log: Pipeline validation and cleanup (#20) 
 
basic working pipeline validator 
Restyle pipeline 
Handle top-level errors in parallel nodes 
Fix z-index issue, dont include empty args 
Fix default to agent any 
Default new to NewPipelineTemplate 
Editing child steps in container steps 
JENKINS-41358 - stage-level agent not exported 
JENKINS-41356 - Fix stage delete 
JENKINS-41362 - edit 'script' with a textbox 
Usage blurb for load/save dialog 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
  

[JIRA] (JENKINS-41362) Script step to take a text box

2017-01-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-41362  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Script step to take a text box   
 

  
 
 
 
 

 
 Code changed in jenkins User: Keith Zantow Path: package.json pom.xml src/main/js/components/Sheets.jsx src/main/js/components/editor/AgentConfiguration.jsx src/main/js/components/editor/EditorMain.jsx src/main/js/components/editor/EditorPage.jsx src/main/js/components/editor/EditorPipelineGraph.jsx src/main/js/components/editor/EditorStepDetails.jsx src/main/js/components/editor/EditorStepList.jsx src/main/js/components/editor/EnvironmentConfiguration.jsx src/main/js/components/editor/NewPipelineTemplate.json src/main/js/components/editor/ValidationMessageList.jsx src/main/js/components/editor/common.jsx src/main/js/components/editor/steps/GenericStepEditor.jsx src/main/js/components/editor/steps/PipelineScriptStepEditor.jsx src/main/js/components/properties/BooleanPropertyInput.jsx src/main/js/components/properties/DecimalPropertyInput.jsx src/main/js/components/properties/IntegerPropertyInput.jsx src/main/js/components/properties/ListPropertyInput.jsx src/main/js/components/properties/StringPropertyInput.jsx src/main/js/services/PipelineMetadataService.js src/main/js/services/PipelineStore.js src/main/js/services/PipelineSyntaxConverter.js src/main/js/services/PipelineValidator.js src/main/js/services/fetchClassic.js src/main/less/editor.less http://jenkins-ci.org/commit/blueocean-pipeline-editor-plugin/c341fddf36d316b599ec66df68fb7970b1d469a4 Log: Pipeline validation and cleanup (#20) 
 
basic working pipeline validator 
Restyle pipeline 
Handle top-level errors in parallel nodes 
Fix z-index issue, dont include empty args 
Fix default to agent any 
Default new to NewPipelineTemplate 
Editing child steps in container steps 
JENKINS-41358 - stage-level agent not exported 
JENKINS-41356 - Fix stage delete 
JENKINS-41362 - edit 'script' with a textbox 
Usage blurb for load/save dialog 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
   

[JIRA] (JENKINS-38668) ${CHANGES_SINCE_LAST_SUCCESS} no longer displays "No changes" when there are no new SCM changes

2017-01-26 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-38668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ${CHANGES_SINCE_LAST_SUCCESS} no longer displays "No changes" when there are no new SCM changes   
 

  
 
 
 
 

 
 Please try this HPI https://ci.jenkins.io/job/Plugins/job/token-macro-plugin/job/master/lastSuccessfulBuild/artifact/target/token-macro.hpi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40805) Workspace not available when a slave is created by the Kubernetes plugin

2017-01-26 Thread palli...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raghu Pallikonda commented on  JENKINS-40805  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Workspace not available when a slave is created by the Kubernetes plugin   
 

  
 
 
 
 

 
 Carlos Sanchez Could you please help with this issue, or how we can fix it? Olivier Lambert  Could you please let me know if you were able to solve the issue? We do have a workaround which is not that nice.. Once the build is done, we have to change the 'where the project is run ' to master. Then the workspace is shown.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37610) Sauce Labs Results Publisher throws Exception in Pipeline

2017-01-26 Thread halk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Mogan commented on  JENKINS-37610  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Sauce Labs Results Publisher throws Exception in Pipeline   
 

  
 
 
 
 

 
 Okay, I had time today, so did a bit of refactoring. Should be released tomorrow, monday at the latest. Also got it to not include that extra field, and made a `saucePublisher` shortcut  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41236) SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"

2017-01-26 Thread halk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Mogan commented on  JENKINS-41236  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"   
 

  
 
 
 
 

 
 Okay, I had time today, so did a bit of refactoring. Should be released tomorrow, monday at the latest.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-7151) Disabling build will delete any pending builds

2017-01-26 Thread t...@deepelement.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Todd Morrison commented on  JENKINS-7151  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Disabling build will delete any pending builds   
 

  
 
 
 
 

 
 IMO, disable build should allow existing builds in the queue to complete. Ideally, we could safely 'rolling down' a build (not accepting new in the queue) without damaging existing commitments.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41133) Github Pull Requests showing up under Branches

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-41133  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Pull Requests showing up under Branches   
 

  
 
 
 
 

 
 When JENKINS-41234 is resolved we consider this issue and all the related ones fixed and shipped.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40446) Links broken in GitHub status for matrix projects

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-40446  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Links broken in GitHub status for matrix projects   
 

  
 
 
 
 

 
 Leandro Lucarella what versions of the following plugins do you have installed? 
 
Blue Ocean beta 
BlueOcean Display URL plugin 
Display URL API 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41494) Blue Ocean karaoke mode fails to show steps or follow along

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41494  
 
 
  Blue Ocean karaoke mode fails to show steps or follow along   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 pannonian  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41494) Blue Ocean karaoke mode fails to show steps or follow along

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41494  
 
 
  Blue Ocean karaoke mode fails to show steps or follow along   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41496) Bad pubsub dependency issue

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41496  
 
 
  Bad pubsub dependency issue   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Summary: 
 Uncaught TyperError: Cannot read property _links of undefined Bad pubsub dependency issue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41496) Uncaught TyperError: Cannot read property _links of undefined

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay started work on  JENKINS-41496  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41496) Uncaught TyperError: Cannot read property _links of undefined

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-41496  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Uncaught TyperError: Cannot read property _links of undefined   
 

  
 
 
 
 

 
 This was a result of the Pubsub issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41496) Uncaught TyperError: Cannot read property _links of undefined

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated  JENKINS-41496  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41496  
 
 
  Uncaught TyperError: Cannot read property _links of undefined   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41494) Blue Ocean karaoke mode fails to show steps or follow along

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41494  
 
 
  Blue Ocean karaoke mode fails to show steps or follow along   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Thorsten Scherler  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41496) Uncaught TyperError: Cannot read property _links of undefined

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Vivek Pandey  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41496  
 
 
  Uncaught TyperError: Cannot read property _links of undefined   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Vivek Pandey  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38668) ${CHANGES_SINCE_LAST_SUCCESS} no longer displays "No changes" when there are no new SCM changes

2017-01-26 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-38668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ${CHANGES_SINCE_LAST_SUCCESS} no longer displays "No changes" when there are no new SCM changes   
 

  
 
 
 
 

 
 Code changed in jenkins User: Alex Earl Path: src/test/java/org/jenkinsci/plugins/tokenmacro/impl/ChangesSinceLastSuccessfulBuildMacroTest.java http://jenkins-ci.org/commit/token-macro-plugin/f7b7652e63c7c7a0dbfdde71dd5f75a8d3aeefc0 Log: Fix JENKINS-38668  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37311) "logout" link doesn't work

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-37311  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "logout" link doesn't work   
 

  
 
 
 
 

 
 Related GitHub Oauth bug is fixed, I wonder if this is a quick fix.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38548) Freestyle Job hangs when running on a JNLP Mac OSX agent

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Seems to be an llvm bug https://llvm.org/bugs/show_bug.cgi?id=30764  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38548  
 
 
  Freestyle Job hangs when running on a JNLP Mac OSX agent   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-41488) Pipeline view automatically scrolls down

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow commented on  JENKINS-41488  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline view automatically scrolls down   
 

  
 
 
 
 

 
 James Dumay I don't believe this is a duplicate of JENKINS-38226 - I think what Gustavo Gonnet is asking for is a way to display the executing pipeline of an individual job.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41488) Pipeline view automatically scrolls down

2017-01-26 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41488  
 
 
  Pipeline view automatically scrolls down   
 

  
 
 
 
 

 
Change By: 
 Keith Zantow  
 
 
Resolution: 
 Duplicate  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-34712) "master is offline" preventing Pipeline from executing

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34712  
 
 
  "master is offline" preventing Pipeline from executing   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Labels: 
 pipeline  pipeline-hangs  robustness  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-31484) Flow goes into endless loop in DefaultInvoker.getProperty when accessing field via getter

2017-01-26 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-31484  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Flow goes into endless loop in DefaultInvoker.getProperty when accessing field via getter   
 

  
 
 
 
 

 
 Using .getName() rather than .name is not the issue, since the bug is inside the getter itself. The workaround is to use the more explicit: 

 

String getName() {this.@name}
 

 Similarly for setters: 

 

void setName(String name) {this.@name = name}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-34712) "master is offline" preventing Pipeline from executing

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34712  
 
 
  "master is offline" preventing Pipeline from executing   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 

  
 
 
 
 

 
 Our own Jenkins Pipeline projects seem to be getting stuck in this state of "master is offline" when attempting to run on our clusters which have zero executors assigned to the master node.It's unclear what, past a service restart, will clear this up :(Steps to reproduce:#  Start a pipeline job#  forcing the master to run out of storage# shutdown master, clear up storage# restart master, confirm it's up# observe that it is still marked as offline for a long time. 30+ minutes  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-34712) "master is offline" preventing Pipeline from executing

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34712  
 
 
  "master is offline" preventing Pipeline from executing   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Labels: 
 pipeline  robustness  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-34712) "master is offline" preventing Pipeline from executing

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34712  
 
 
  "master is offline" preventing Pipeline from executing   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 

  
 
 
 
 

 
 Our own Jenkins Pipeline projects seem to be getting stuck in this state of "master is offline" when attempting to run on our clusters which have zero executors assigned to the master node.It's unclear what, past a service restart, will clear this up :( h3. Thread Dump{code}Channel reader thread Steps to reproduce :  trusted-agent-1  "Channel reader thread: trusted-agent-1" Id=87 Group=main WAITING on com.trilead.ssh2.channel.Channel@78493ab5 at java.lang.Object.wait(Native Method) -  waiting on com.trilead.ssh2.channel.Channel@78493ab5 at java.lang.Object.wait(Object.java:503) at com.trilead.ssh2.channel.FifoBuffer.read(FifoBuffer.java:212) at com.trilead.ssh2.channel.Channel$Output.read(Channel.java:127) at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:936) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)Channel reader thread: trusted-agent-2"Channel reader thread: trusted-agent-2" Id=90 Group=main WAITING on com.trilead.ssh2.channel.Channel@67e91886 at java.lang.Object.wait(Native Method) -  waiting on com.trilead.ssh2.channel.Channel@67e91886 at java.lang.Object.wait(Object.java:503) at com.trilead.ssh2.channel.FifoBuffer.read(FifoBuffer.java:212) at com.trilead.ssh2.channel.Channel$Output.read(Channel.java:127) at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:936) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)Computer.threadPoolForRemoting [ # 8]"Computer.threadPoolForRemoting [#8]" Id=132 Group=main TIMED_WAITING on java.util.concurrent.SynchronousQueue$TransferStack@4a44a3c2 

[JIRA] (JENKINS-34712) "master is offline" preventing Pipeline from executing

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34712  
 
 
  "master is offline" preventing Pipeline from executing   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 

  
 
 
 
 

 
 Our own Jenkins Pipeline projects seem to be getting stuck in this state of "master is offline" when attempting to run on our clusters which have zero executors assigned to the master node.It's unclear what, past a service restart, will clear this up :(Steps to reproduce:# forcing the master to run out of storage# shutdown master, clear up storage# restart master, confirm it's up# observe that it is still marked as offline  in CJOC  for a long time. 30+ minutes  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-34712) "master is offline" preventing Pipeline from executing

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34712  
 
 
  "master is offline" preventing Pipeline from executing   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Attachment: 
 threaddump.txt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38021) Accessing unset global variable cause master to hang

2017-01-26 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-38021  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Accessing unset global variable cause master to hang   
 

  
 
 
 
 

 
 I believe this is simply a duplicate of JENKINS-31484 but I want to do some more integration testing first to be sure, and also want to verify that JENKINS-25623 allows the build to be halted even without this particular fix.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-31484) Flow goes into endless loop in DefaultInvoker.getProperty when accessing field via getter

2017-01-26 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-31484  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31484  
 
 
  Flow goes into endless loop in DefaultInvoker.getProperty when accessing field via getter   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35432) Scheduled builds crash after running for more than 8 hours

2017-01-26 Thread adactusla...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Spenser Austin commented on  JENKINS-35432  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Scheduled builds crash after running for more than 8 hours   
 

  
 
 
 
 

 
 This was supposed to be fixed in the Team Explorer Everywhere SDK v14.0.3 Release. This was included in version 5.1.0 of the TFS-plugin.  I'm not sure why this is still happening, unless it wasn't actually fixed in the Team Explorer Anywhere 14.0.3. I'm on plugin version 5.3 and we still get this error occasionally. The only permanent fix would be to get it fixed in the TFS SDK.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38908) Script.main(String[]) vs. Script.main() ArrayIndexOutOfBoundsException

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell updated  JENKINS-38908  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38908  
 
 
  Script.main(String[]) vs. Script.main() ArrayIndexOutOfBoundsException   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 In Review Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38908) Script.main(String[]) vs. Script.main() ArrayIndexOutOfBoundsException

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-38908  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Script.main(String[]) vs. Script.main() ArrayIndexOutOfBoundsException   
 

  
 
 
 
 

 
 Released as script-security-1.24  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38668) ${CHANGES_SINCE_LAST_SUCCESS} no longer displays "No changes" when there are no new SCM changes

2017-01-26 Thread slide.o....@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-38668  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ${CHANGES_SINCE_LAST_SUCCESS} no longer displays "No changes" when there are no new SCM changes   
 

  
 
 
 
 

 
 The internet went down at my house (where my build system is), so it will take me longer than I anticipated to get the version to try.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-26375) Team Foundation Server Plugin (TFS) creates bogus users in 3.0 and later

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell edited a comment on  JENKINS-26375  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Team Foundation Server Plugin (TFS) creates bogus users in 3.0 and later   
 

  
 
 
 
 

 
 Seems like the #73 above was superceded by [#40|https://github.com/jenkinsci/tfs-plugin/pull/140] so I think this is resolved if I understand the maintainer's comments. Seems like this was fixed in tfs-5.3.0, but I'm leaving for maintainer to confirm.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-26375) Team Foundation Server Plugin (TFS) creates bogus users in 3.0 and later

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-26375  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Team Foundation Server Plugin (TFS) creates bogus users in 3.0 and later   
 

  
 
 
 
 

 
 Seems like the #73 above was superceded by #40 so I think this is resolved if I understand the maintainer's comments.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41501) Regression: Activity pagination is broken

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41501  
 
 
  Regression: Activity pagination is broken   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 pagination-is-broken.gif  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2017/Jan/26 10:54 PM  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 Steps to reproduce 
 
Go to https://ci.blueocean.io/blue/organizations/jenkins/blueocean/activity/ 
Scroll to the bottom and click "Show More" 
The whole table will reload, "Show more" is disabled and no more rows will be shown. 
 What you should see Pagination working   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

 

[JIRA] (JENKINS-41501) Regression: Activity pagination is broken

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Ivan Meredith  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41501  
 
 
  Regression: Activity pagination is broken   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Ivan Meredith  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41501) Regression: Activity pagination is broken

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41501  
 
 
  Regression: Activity pagination is broken   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Critical Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41500) Blue Ocean 404 page should set a 404 status code

2017-01-26 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41500  
 
 
  Blue Ocean 404 page should set a 404 status code   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 blueocean-404.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2017/Jan/26 10:45 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 R. Tyler Croy  
 

  
 
 
 
 

 
 An unrelated issue caused an invalid URL to be generated by Blue Ocean (already tracked). When the browser navigates to that invalid URL (e.g. https://ci.jenkins.io/blue/organizations/jenkins/Infra%2Fazure/detail/master/37/pipeline/undefinedruns/4/) the response is a 200 OK with the screenshoted page. The HTTP response code should be 404.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
   

[JIRA] (JENKINS-40447) PublishHTMLStepExecution.run can block CPS thread

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell updated  JENKINS-40447  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released as htmlpublisher-1.12  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40447  
 
 
  PublishHTMLStepExecution.run can block CPS thread   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41499) Regression: show complete log button has shifted to the left

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41499  
 
 
  Regression: show complete log button has shifted to the left   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Thorsten Scherler  
 
 
Attachments: 
 blueocean #621 2017-01-27 09-23-23.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2017/Jan/26 10:36 PM  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 It should be centered.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

[JIRA] (JENKINS-27897) Jenkins is unable to run tests in ALM PC 12

2017-01-26 Thread ajay.sin...@walmart.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ajay Singh commented on  JENKINS-27897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins is unable to run tests in ALM PC 12   
 

  
 
 
 
 

 
 I was also facing the same problem. I just removed all the special characters from below places and it worked fine, please try and confirm if it helps anyone too. Jenkins > Go in your project > Project Name Jenkins > Go in your project > Build > Description Both these places should not have any special characters. After ensuring these updates, above issue fixed for me.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-31484) Flow goes into endless loop in DefaultInvoker.getProperty when accessing field via getter

2017-01-26 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-31484  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31484  
 
 
  Flow goes into endless loop in DefaultInvoker.getProperty when accessing field via getter   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Review  Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41498) P4Groovy not executing operations on the slave

2017-01-26 Thread ssutherl...@ea.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean Sutherland edited a comment on  JENKINS-41498  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: P4Groovy not executing operations on the slave   
 

  
 
 
 
 

 
 One solution is to extend AbstractTask into a new task for P4Groovy, and have the run(), fetch(), and save() methods use that instead. If this is the direction we want to go, I can start a PR pending legal approval on our end (we're still trying to work out the kinks in the process)   Additionally, if changes need to be made to the execution anyway, it might be worth looking into making them into durable tasks.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40995) Deadlock between hudson.model.RunMap and java.util.logging.StreamHandler

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-40995  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock between hudson.model.RunMap and java.util.logging.StreamHandler   
 

  
 
 
 
 

 
 Released in workflow-durable-task-step-2.8  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41498) P4Groovy not executing operations on the slave

2017-01-26 Thread ssutherl...@ea.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean Sutherland commented on  JENKINS-41498  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: P4Groovy not executing operations on the slave   
 

  
 
 
 
 

 
 One solution is to extend AbstractTask into a new task for P4Groovy, and have the run(), fetch(), and save() methods use that instead. Additionally, if changes need to be made to the execution anyway, it might be worth looking into making them into durable tasks.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40284) Fair Queuing strategy levels out to an identical weight for all jobs

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40284  
 
 
  Fair Queuing strategy levels out to an identical weight for all jobs   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41498) P4Groovy not executing operations on the slave

2017-01-26 Thread ssutherl...@ea.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean Sutherland created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41498  
 
 
  P4Groovy not executing operations on the slave   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2017/Jan/26 10:23 PM  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Sean Sutherland  
 

  
 
 
 
 

 
 When executing p4 commands through a P4Groovy object, the commands are run on the master instead of being sent to the slave. The P4Groovy object initialization is wrapped in a MasterToSlaveCallable, but the actual execution is not.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 

[JIRA] (JENKINS-40701) Add warning that Usage Tracking might not be exhaustive and depends on the consumer plugins

2017-01-26 Thread ryan.campb...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell updated  JENKINS-40701  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Released as credentials-2.1.11  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40701  
 
 
  Add warning that Usage Tracking might not be exhaustive and depends on the consumer plugins   
 

  
 
 
 
 

 
Change By: 
 recampbell  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-41186) java.security.spec.InvalidKeySpecException: key spec not recognised

2017-01-26 Thread steven.jo...@computerminds.co.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven Jones commented on  JENKINS-41186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.security.spec.InvalidKeySpecException: key spec not recognised   
 

  
 
 
 
 

 
 Interesting, I also tried using an encrypted rsa key and get the following different exception! 

 
java.lang.IllegalArgumentException: DER length more than 4 bytes: 90
	at shaded.com.google.common.base.Preconditions.checkArgument(Preconditions.java:148)
	at org.jclouds.crypto.ASN1Codec.readLength(ASN1Codec.java:161)
	at org.jclouds.crypto.ASN1Codec.create(ASN1Codec.java:150)
	at org.jclouds.crypto.ASN1Codec.createASN1Sequence(ASN1Codec.java:84)
	at org.jclouds.crypto.ASN1Codec.decodeRSAPrivateKey(ASN1Codec.java:64)
	at org.jclouds.crypto.Pems$DecodeRSAPrivateCrtKeySpec.parseResult(Pems.java:238)
	at org.jclouds.crypto.Pems$DecodeRSAPrivateCrtKeySpec.parseResult(Pems.java:233)
	at org.jclouds.crypto.Pems$PemProcessor.getResult(Pems.java:98)
	at shaded.com.google.common.io.ByteSource$ByteArrayByteSource.read(ByteSource.java:546)
	at org.jclouds.crypto.Pems.fromPem(Pems.java:195)
	at org.jclouds.crypto.Pems.privateKeySpec(Pems.java:214)
	at org.jclouds.crypto.Pems.privateKeySpec(Pems.java:252)
	at org.jclouds.ssh.SshKeys.fingerprintPrivateKey(SshKeys.java:211)
	at org.jclouds.openstack.nova.v2_0.compute.strategy.ApplyNovaTemplateOptionsCreateNodesWithGroupEncodedIntoNameThenAddToSet.execute(ApplyNovaTemplateOptionsCreateNodesWithGroupEncodedIntoNameThenAddToSet.java:128)
	at org.jclouds.compute.internal.BaseComputeService.createNodesInGroup(BaseComputeService.java:217)
	at sun.reflect.GeneratedMethodAccessor551.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:37)
	at com.sun.proxy.$Proxy144.createNodesInGroup(Unknown Source)
	at jenkins.plugins.jclouds.compute.JCloudsSlaveTemplate.get(JCloudsSlaveTemplate.java:595)
	at jenkins.plugins.jclouds.compute.JCloudsSlaveTemplate.provisionSlave(JCloudsSlaveTemplate.java:339)
	at jenkins.plugins.jclouds.compute.JCloudsCloud$2.call(JCloudsCloud.java:373)
	at jenkins.plugins.jclouds.compute.JCloudsCloud$2.call(JCloudsCloud.java:370)
	at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)}}
 

 Which would suggest to me that an incorrectly encoded string or buffer is being passed around?  
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-31484) Flow goes into endless loop in DefaultInvoker.getProperty when accessing field via getter

2017-01-26 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-31484  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31484  
 
 
  Flow goes into endless loop in DefaultInvoker.getProperty when accessing field via getter   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41488) Pipeline view automatically scrolls down

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41488  
 
 
  Pipeline view automatically scrolls down   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-34416) Documentation should clarify distinction between global variable access vs. plain class references

2017-01-26 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34416  
 
 
  Documentation should clarify distinction between global variable access vs. plain class references   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries

2017-01-26 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41497  
 
 
  Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries   
 

  
 
 
 
 

 
 This looks like it's an underlying behavior in Pipeline.  
 

  
 
 
 
 

 
Change By: 
 R. Tyler Croy  
 
 
Summary: 
 Blue Ocean Poll SCM and Timer triggers include  "Changes" for a Pipeline  are from the completely wrong repository  for any/all Shared Libraries  
 
 
Component/s: 
 pipeline  
 
 
Component/s: 
 blueocean-plugin  
 
 
Priority: 
 Major Minor  
 
 
Attachment: 
 classic-changes-view.png  
 

  
 
 
 
 

 
 I noticed this while filing another ticket (JENKINS-41496), but the "Changes" view for the Pipeline run for this project "azure" has the  **  " wrong commits ** "  shown. See the screenshots for more. What basically appears to be happening is that any change to a Shared Library will result in _newly_ triggered Pipelines which have "Poll SCM" configured. Pipelines which configure a timer will also have Changes from the Shared Library listed when it executes again. I 'm  think *listing* the Shared Library commits in "Changes" is acceptable, but *triggering* based on an SCM Poll for a Pipeline is very confusing behavior and IMHO incorrect behavior.As a shared tooling team, I would  not  sure why  expect my Shared Library changes to trigger a bunch of Pipelines for projects depending on them .  
 

  
 
 
 
   

[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated  JENKINS-41425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41425  
 
 
  Refreshing page with / in job name results in 404   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay started work on  JENKINS-41425  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41186) java.security.spec.InvalidKeySpecException: key spec not recognised

2017-01-26 Thread steven.jo...@computerminds.co.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven Jones commented on  JENKINS-41186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.security.spec.InvalidKeySpecException: key spec not recognised   
 

  
 
 
 
 

 
 I've tried creating a ECDSA key, but that generates an exception from another bit of jclouds!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-27897) Jenkins is unable to run tests in ALM PC 12

2017-01-26 Thread ajay.sin...@walmart.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ajay Singh commented on  JENKINS-27897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins is unable to run tests in ALM PC 12   
 

  
 
 
 
 

 
 do we have any fix for this issue yet?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41495) Jenkins Update for plugins URL not working in 2.32.1 version

2017-01-26 Thread sharathi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 sharat sathyanarayan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41495  
 
 
  Jenkins Update for plugins URL not working in 2.32.1 version   
 

  
 
 
 
 

 
Change By: 
 sharat sathyanarayan  
 
 
Summary: 
 Kenkins Jenkins  Update for plugins URL not working in 2.32.1 version  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40990) Jenkins 2.32.1 causes Java 5/6 Maven builds to fail

2017-01-26 Thread andreas.man...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Mandel commented on  JENKINS-40990  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins 2.32.1 causes Java 5/6 Maven builds to fail   
 

  
 
 
 
 

 
 Ok, cause is that with the new remoting} the causing {{UnsupportedClassVersionError is not part of the getCause chain of the caught IOException any more. Need to find out how the cause is reported now through the channel.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41186) java.security.spec.InvalidKeySpecException: key spec not recognised

2017-01-26 Thread steven.jo...@computerminds.co.uk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven Jones commented on  JENKINS-41186  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.security.spec.InvalidKeySpecException: key spec not recognised   
 

  
 
 
 
 

 
 I'm not a Java developer, but, looking at the exception, we're getting it from line 144 of KeyType.java: http://www.atetric.com/atetric/javadoc/net.schmizz/sshj/0.10.0/src-html/net/schmizz/sshj/common/KeyType.html#line.144 Which looks to be dealing with ECDSA keys? So maybe it's picking up the wrong key type or some such?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41497) Blue Ocean "Changes" for a Pipeline are from the completely wrong repository

2017-01-26 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers edited a comment on  JENKINS-41497  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean "Changes" for a Pipeline are from the completely wrong repository   
 

  
 
 
 
 

 
 Could you please paste the JSON response from the REST API call to .../runs/ { $ runId }  ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41497) Blue Ocean "Changes" for a Pipeline are from the completely wrong repository

2017-01-26 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-41497  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean "Changes" for a Pipeline are from the completely wrong repository   
 

  
 
 
 
 

 
 Could you please paste the JSON response from the REST API call to .../runs/ {runId}  ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41496) Uncaught TyperError: Cannot read property _links of undefined

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-41496  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Uncaught TyperError: Cannot read property _links of undefined   
 

  
 
 
 
 

 
 Visiting any page such as https://ci.jenkins.io/blue/pipelines will have these errors in the logs  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41496) Uncaught TyperError: Cannot read property _links of undefined

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41496  
 
 
  Uncaught TyperError: Cannot read property _links of undefined   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Critical Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41497) Blue Ocean "Changes" for a Pipeline are from the completely wrong repository

2017-01-26 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41497  
 
 
  Blue Ocean "Changes" for a Pipeline are from the completely wrong repository   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 blueocean-changes.png, unrelated-repo-changes.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2017/Jan/26 9:49 PM  
 
 
Environment: 
 b19  
 
 
Priority: 
  Major  
 
 
Reporter: 
 R. Tyler Croy  
 

  
 
 
 
 

 
 I noticed this while filing another ticket (JENKINS-41496), but the "Changes" view for the Pipeline run for this project "azure" has the *wrong commits* shown. See the screenshots for more. I'm not sure why.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  

[JIRA] (JENKINS-41496) Uncaught TyperError: Cannot read property _links of undefined

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41496  
 
 
  Uncaught TyperError: Cannot read property _links of undefined   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 pannonian  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41496) Uncaught TyperError: Cannot read property _links of undefined

2017-01-26 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41496  
 
 
  Uncaught TyperError: Cannot read property _links of undefined   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41496) Uncaught TyperError: Cannot read property _links of undefined

2017-01-26 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41496  
 
 
  Uncaught TyperError: Cannot read property _links of undefined   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Selection_057.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2017/Jan/26 9:45 PM  
 
 
Environment: 
 b19  
 
 
Priority: 
  Major  
 
 
Reporter: 
 R. Tyler Croy  
 

  
 
 
 
 

 
 Navigating to any Pipeline run in Blue Ocean spews a few _javascript_ errors. I'm not sure if this affects functionality, I haven't found anything yet that suggests that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

 

[JIRA] (JENKINS-37993) Can't load main dashboard - hudson model view

2017-01-26 Thread cemcken...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Clara Mckenzie commented on  JENKINS-37993  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't load main dashboard - hudson model view   
 

  
 
 
 
 

 
 Disabling Semantic Versioning worked for me  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41494) Blue Ocean karaoke mode fails to show steps or follow along

2017-01-26 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy commented on  JENKINS-41494  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean karaoke mode fails to show steps or follow along   
 

  
 
 
 
 

 
 Scratch that _links error, I think that's a different issue!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41494) Blue Ocean karaoke mode fails to show steps or follow along

2017-01-26 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy commented on  JENKINS-41494  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Blue Ocean karaoke mode fails to show steps or follow along   
 

  
 
 
 
 

 
 I am also seeing the following error after starting a Pipeline and hitting the "Open" toast at the bottom: 

 

blueocean.js:5523 Uncaught (in promise) TypeError: Cannot read property '_links' of undefined(…)updateLatestRun @ blueocean.js:5523executeAction @ blueocean.js:64247res @ blueocean.js:64219(anonymous function) @ blueocean.js:4706Promise.reject (async)tryCatch @ blueocean.js:39904invokeCallback @ blueocean.js:39919(anonymous function) @ blueocean.js:39666flush @ blueocean.js:39615Mutation (async)(anonymous function) @ blueocean.js:39587asap @ blueocean.js:39539(anonymous function) @ blueocean.js:39665then @ blueocean.js:39668
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41495) Kenkins Update for plugins URL not working in 2.32.1 version

2017-01-26 Thread sharathi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 sharat sathyanarayan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41495  
 
 
  Kenkins Update for plugins URL not working in 2.32.1 version   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Update_plugin_Malformed_URL.PNG  
 
 
Components: 
 update-sites-manager-plugin  
 
 
Created: 
 2017/Jan/26 9:38 PM  
 
 
Environment: 
 Corporate Cloud infrastructure, ubuntu, Jenkins ver. 2.32.1  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 sharat sathyanarayan  
 

  
 
 
 
 

 
 Please see the attached image. When I click on check now. It gives the below error. Note: I was doing an upgrade from ver 1.6 to 2.32.1 stable version. I followed the following post to upgrade jenkins http://www.thegeekstuff.com/2016/06/upgrade-jenkins-and-plugins  Stack trace java.net.MalformedURLException: no protocol: ?id=simpleupdatesite&version=2.32.1 at java.net.URL.(URL.java:585) at java.net.URL.(URL.java:482) at java.net.URL.(URL.java:431) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:180) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1619) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInv

[JIRA] (JENKINS-41495) Kenkins Update for plugins URL not working in 2.32.1 version

2017-01-26 Thread sharathi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 sharat sathyanarayan updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41495  
 
 
  Kenkins Update for plugins URL not working in 2.32.1 version   
 

  
 
 
 
 

 
Change By: 
 sharat sathyanarayan  
 

  
 
 
 
 

 
 Please see the attached image.When I click on check now. It gives the below error.Note: I was doing an upgrade from ver 1.6 to 2.32.1 stable version. I followed the following post to upgrade  jenkins  Jenkins. I am unable to proceed further due to unavailability of the latest plugins. Urgent help required. http://www.thegeekstuff.com/2016/06/upgrade-jenkins-and-plugins Stack tracejava.net.MalformedURLException: no protocol: ?id=simpleupdatesite&version=2.32.1 at java.net.URL.(URL.java:585) at java.net.URL.(URL.java:482) at java.net.URL.(URL.java:431) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:180) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1619) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:174) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:49) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:44) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:106) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:44) at hudson.util.PluginServletFilter$1.doFil

[JIRA] (JENKINS-41495) Kenkins Update for plugins URL not working in 2.32.1 version

2017-01-26 Thread sharathi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 sharat sathyanarayan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41495  
 
 
  Kenkins Update for plugins URL not working in 2.32.1 version   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Update_plugin_Malformed_URL.PNG  
 
 
Components: 
 update-sites-manager-plugin  
 
 
Created: 
 2017/Jan/26 9:38 PM  
 
 
Environment: 
 Corporate Cloud infrastructure, ubuntu, Jenkins ver. 2.32.1  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 sharat sathyanarayan  
 

  
 
 
 
 

 
 Please see the attached image. When I click on check now. It gives the below error. Note: I was doing an upgrade from ver 1.6 to 2.32.1 stable version. I followed the following post to upgrade jenkins http://www.thegeekstuff.com/2016/06/upgrade-jenkins-and-plugins  Stack trace java.net.MalformedURLException: no protocol: ?id=simpleupdatesite&version=2.32.1 at java.net.URL.(URL.java:585) at java.net.URL.(URL.java:482) at java.net.URL.(URL.java:431) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:180) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1619) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInv

[JIRA] (JENKINS-36132) Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed.

2017-01-26 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner edited a comment on  JENKINS-36132  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed.   
 

  
 
 
 
 

 
 Robert: Seems that you are using the wrong parser? The log {noformat}src/file.c:111:11: Info : A message.{noformat}from your example is not in MS-Build (same as PC-Lint) message format.  Did you follow the [explanation|https://wiki.jenkins-ci.org/display/JENKINS/PcLint+options].  What tool creates your warnings? Can you wrap an example console log message into a noformat tag (see above)?(BTW: this issue is about Resharper messages ;-))  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and 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   4   5   >