[JIRA] [logstash-plugin] (JENKINS-29830) Logstash plugin set @timestamp value to line output value

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29830 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Logstash plugin set @timestamp value to line output value  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Rusty Gerard Path: src/main/java/jenkins/plugins/logstash/persistence/AbstractLogstashIndexerDao.java src/test/java/jenkins/plugins/logstash/persistence/AbstractLogstashIndexerDaoTest.java http://jenkins-ci.org/commit/logstash-plugin/2e6899bf5128ef0fd5ef950204cf4c0623915373 Log: Merge pull request #13 from rwtsoftware/JENKINS-29830 
Add Timestamps 
Compare: https://github.com/jenkinsci/logstash-plugin/compare/7b20502a6d5e...2e6899bf5128 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [logstash-plugin] (JENKINS-33633) Change Key values to "_" vs "." as this breaks ES 2.0 and later

2016-03-22 Thread rusty.ger...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rusty Gerard commented on  JENKINS-33633 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change Key values to "_" vs "." as this breaks ES 2.0 and later  
 
 
 
 
 
 
 
 
 
 
The Logstash plugin pushes data to Elasticsearch in JSON format. Are you referring to the "denormalizing" performed by Elasticsearch, or period characters in the JSON keys? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [logstash-plugin] (JENKINS-33635) Enable globally

2016-03-22 Thread rusty.ger...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rusty Gerard commented on  JENKINS-33635 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable globally   
 
 
 
 
 
 
 
 
 
 
This issue should be filed against the Configuration Slicing plugin, not the Logstash plugin. ("Slicing" a property requires updating the slicing plugin to make it aware of the Logstash plugin, not the other way around.) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [maven-plugin] (JENKINS-33738) Builds are failing due to java.lang.NoClassDefFoundError: org/jvnet/hudson/maven3/listeners/MavenProjectInfo

2016-03-22 Thread medea.gugushv...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Medea Gugushvili created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33738 
 
 
 
  Builds are failing due to java.lang.NoClassDefFoundError: org/jvnet/hudson/maven3/listeners/MavenProjectInfo  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 maven-plugin 
 
 
 

Created:
 

 2016/Mar/23 5:10 AM 
 
 
 

Environment:
 

 Jenkins ver. 1.651, jdk1.7.0_51 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Medea Gugushvili 
 
 
 
 
 
 
 
 
 
 
From time to time builds are failing with following reason: 
[pool-1-thread-1 for channel] INFO org.codehaus.mojo.cobertura.CoberturaReportMojo - Cobertura Report generation was successful. [pool-1-thread-1 for channel] INFO org.apache.maven.cli.event.ExecutionEventLogger -  [pool-1-thread-1 for channel] INFO org.apache.maven.cli.event.ExecutionEventLogger - BUILD SUCCESS [pool-1-thread-1 for channel] INFO org.apache.maven.cli.event.ExecutionEventLogger -  [pool-1-thread-1 for channel] INFO org.apache.maven.cli.event.ExecutionEventLogger - Total time: 35:24.283s [pool-1-thread-1 for channel] INFO org.apache.maven.cli.event.ExecutionEventLogger - Finished at: Wed Mar 23 01:04:43 UTC 2016 [pool-1-thread-1 for channel] INFO org.apache.maven.cli.event.ExecutionEventLogger - Final Memory: 31M/580M 

[JIRA] [ws-cleanup-plugin] (JENKINS-33737) Consult additional environments to interpolate workspace delete command

2016-03-22 Thread wberr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wade Berrier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33737 
 
 
 
  Consult additional environments to interpolate workspace delete command  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 vjuranek 
 
 
 

Components:
 

 ws-cleanup-plugin 
 
 
 

Created:
 

 2016/Mar/23 3:07 AM 
 
 
 

Environment:
 

 Workspace cleanup plugin latest (0.28) 
 
 
 

Labels:
 

 plugin windows 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Wade Berrier 
 
 
 
 
 
 
 
 
 
 
The delete command has the option of being interpolated, which is very handy. 
The issue is that it appears only the slave's environment variables are consulted when interpolating variables. This was discovered by trial and error, as seems to be confirmed by looking at the code. 
I would prefer to also consult the jenkins global environment, or the actual process environment. 
My situation is that I have lots of linux nodes, and a few windows nodes. I don't mind specifying variables for the few windows nodes, but it's tedious to specify for all the other nodes as well 

[JIRA] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others

2016-03-22 Thread jswa...@alohaoi.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Swager reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
It's reproducible! 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-11024 
 
 
 
  Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Swager 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others

2016-03-22 Thread jswa...@alohaoi.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Swager commented on  JENKINS-11024 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others  
 
 
 
 
 
 
 
 
 
 
I'm experiencing this problem. Using CloudBees folders and roles/groups with absolutely no permissions for non-authenticated users. 
I can list-job through the folders and see the job. But trying to build it via the cli results in "ERROR: No such job" 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33736) HttpParser Full jetty warn

2016-03-22 Thread ty...@monkeypox.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R. Tyler Croy assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33736 
 
 
 
  HttpParser Full jetty warn  
 
 
 
 
 
 
 
 
 

Change By:
 
 R. Tyler Croy 
 
 
 

Assignee:
 
 R. Tyler Croy 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33736) HttpParser Full jetty warn

2016-03-22 Thread ty...@monkeypox.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R. Tyler Croy moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33736 
 
 
 
  HttpParser Full jetty warn  
 
 
 
 
 
 
 
 
 

Change By:
 
 R. Tyler Croy 
 
 
 

Project:
 
 Infrastructure Jenkins 
 
 
 

Key:
 
 INFRA JENKINS - 614 33736 
 
 
 

Workflow:
 
 classic default workflow JNJira 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 ci 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 

[JIRA] [core] (JENKINS-33358) Groovy and PermGen memory leak

2016-03-22 Thread liuh...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hongkai Liu commented on  JENKINS-33358 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Groovy and PermGen memory leak  
 
 
 
 
 
 
 
 
 
 
Thanks for the work. I will update here. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33358) Groovy and PermGen memory leak

2016-03-22 Thread orc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hao CHEN assigned an issue to Hongkai Liu 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Can you try version 1.1.1 of this plugin, I parsed and cached the groovy script, parse() do save a lot of memory, hoping it could solve your issue. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33358 
 
 
 
  Groovy and PermGen memory leak  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hao CHEN 
 
 
 

Assignee:
 
 Jesse Glick Hongkai Liu 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [git-plugin] (JENKINS-24529) Poll SCM Job Trigger (git) does not wake up VirtualBox on-demand slave nodes

2016-03-22 Thread nabe...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 nabedge watanabe commented on  JENKINS-24529 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Poll SCM Job Trigger (git) does not wake up VirtualBox on-demand slave nodes  
 
 
 
 
 
 
 
 
 
 
I have same issue. After upgrade 1.556 to 1.653, cron polling to github.com on my build job configuration can not trigger the job saying ... 
``` Started on Mar 23, 2016 10:38:00 AM We need to schedule a new build to get a workspace, but deferring 3,693ms in the hope that one will become available soon (all_suitable_nodes_are_offline) Done. Took 0 ms ``` 
If some slave node wake up, that can trigger job correctly. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33735) HTML source SyntaxError: expected expression, got '<' for ""

2016-03-22 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33735 
 
 
 
  HTML source SyntaxError: expected _expression_, got '<' for ""  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rick Liu 
 
 
 

Attachment:
 
 Cov_commit [Coverity] [Jenkins] - Mozilla Firefox_005.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33735) HTML source SyntaxError: expected expression, got '<' for ""

2016-03-22 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33735 
 
 
 
  HTML source SyntaxError: expected _expression_, got '<' for ""  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rick Liu 
 
 
 

Attachment:
 
 jenkins_homepage.html 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33735) HTML source SyntaxError: expected expression, got '<' for ""

2016-03-22 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33735 
 
 
 
  HTML source SyntaxError: expected _expression_, got '<' for ""  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 Dashboard [Jenkins] - Mozilla Firefox_004.png 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Mar/23 1:29 AM 
 
 
 

Environment:
 

 Server:  Ubuntu 14.04 x86_64  Oracle JDK 1.7  Jenkins 1.642.1   Client:  Ubuntu 15.10 x86_64  Firefox 45.0  Firebug 2.0.14 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Rick Liu 
 
 
 
 
 
 
 
 
 
 
For every Jenkins page, if you enable Firebug, it will show "SyntaxError: expected _expression_, got '<'  
 
 
 
 
 
 
 
 
 
 
 
 
   

[JIRA] [core] (JENKINS-33557) Setup wizard shows blank page when Jenkins is behind proxy

2016-03-22 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-33557 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Setup wizard shows blank page when Jenkins is behind proxy  
 
 
 
 
 
 
 
 
 
 
New PR build: https://jenkins.ci.cloudbees.com/job/core/job/jenkins-core/4495/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33659) Address item config page width issues with scrollable tabs / updated UI

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33659 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Address item config page width issues with scrollable tabs / updated UI  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/6a355ae3dfb9a0a764951670aee2546986bc7fbf Log: Merge pull request #2153 from kzantow/

JENKINS-33659
-scrollspy-ux-issues 
[FIX JENKINS-33659] Basic fix for scrollspy width issues 
Compare: https://github.com/jenkinsci/jenkins/compare/8ca7cab46f52...6a355ae3dfb9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33659) Address item config page width issues with scrollable tabs / updated UI

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33659 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Address item config page width issues with scrollable tabs / updated UI  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: kzantow Path: war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/c52117a9bafa2bb4995674561e744aab28437e09 Log: 

JENKINS-33659
 - Basic fix for scrollspy width issues 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33659) Address item config page width issues with scrollable tabs / updated UI

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33659 
 
 
 
  Address item config page width issues with scrollable tabs / updated UI  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33571) Installing "All" plugins in Getting Started dialogue results in a broken Jenkins installation

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33571 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Installing "All" plugins in Getting Started dialogue results in a broken Jenkins installation  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: war/src/main/js/api/plugins.js http://jenkins-ci.org/commit/jenkins/495784745d860f7b3454915b76ae5679dbba95b3 Log: Add Slack Plugin again, 2.0.1 resolved cause for 

JENKINS-33571
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33705) Security token not printed with proper line endings on Windows

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33705 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Security token not printed with proper line endings on Windows  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: core/src/main/java/jenkins/install/SetupWizard.java http://jenkins-ci.org/commit/jenkins/012a92e7de75d10a90afa580badb843a7c5efb0d Log: [FIX JENKINS-33705] Use platform line endings 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33705) Security token not printed with proper line endings on Windows

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33705 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Security token not printed with proper line endings on Windows  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: core/src/main/java/jenkins/install/SetupWizard.java http://jenkins-ci.org/commit/jenkins/3fdd8666b762cc36d3ccca35c3848f911d619d27 Log: Merge pull request #2150 from daniel-beck/

JENKINS-33705
 
[FIX JENKINS-33705] Use platform line endings 
Compare: https://github.com/jenkinsci/jenkins/compare/82d3eb8644ad...3fdd8666b762 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33705) Security token not printed with proper line endings on Windows

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33705 
 
 
 
  Security token not printed with proper line endings on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-14538) Separate "configure tools" page

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-14538 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Separate "configure tools" page  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/Functions.java core/src/main/java/hudson/model/Descriptor.java core/src/main/java/hudson/tools/ToolDescriptor.java core/src/main/java/jenkins/model/GlobalConfiguration.java core/src/main/java/jenkins/model/GlobalConfigurationCategory.java core/src/main/java/jenkins/model/GlobalToolConfiguration.java core/src/main/java/jenkins/mvn/GlobalMavenConfig.java core/src/main/resources/jenkins/management/Messages.properties core/src/main/resources/jenkins/model/GlobalToolConfiguration/index.groovy http://jenkins-ci.org/commit/jenkins/ea5b2a7ef6131e7d04a7114bbe9e7ee8e275651a Log: [FIX JENKINS-14538] Move tool configuration to separate page 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-14538) Separate "configure tools" page

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-14538 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Separate "configure tools" page  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Antonio Muñiz Path: core/src/main/java/hudson/Functions.java core/src/main/java/hudson/model/Descriptor.java core/src/main/java/hudson/model/ManageJenkinsAction.java core/src/main/java/hudson/tools/ToolDescriptor.java core/src/main/java/jenkins/management/ConfigureLink.java core/src/main/java/jenkins/model/GlobalConfiguration.java core/src/main/java/jenkins/model/GlobalConfigurationCategory.java core/src/main/java/jenkins/model/GlobalToolConfiguration.java core/src/main/java/jenkins/mvn/GlobalMavenConfig.java core/src/main/resources/hudson/logging/LogRecorder/sidepanel.jelly core/src/main/resources/hudson/logging/LogRecorderManager/index.jelly core/src/main/resources/hudson/logging/LogRecorderManager/sidepanel.jelly core/src/main/resources/hudson/model/ComputerSet/index.jelly core/src/main/resources/hudson/model/ComputerSet/sidepanel.jelly core/src/main/resources/hudson/model/Label/sidepanel.jelly core/src/main/resources/hudson/model/UpdateCenter/sidepanel.jelly core/src/main/resources/hudson/model/User/sidepanel.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/index.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/sidepanel.jelly core/src/main/resources/jenkins/management/Messages.properties core/src/main/resources/jenkins/model/GlobalToolConfiguration/index.groovy core/src/main/resources/lib/hudson/project/configurable.jelly http://jenkins-ci.org/commit/jenkins/9e667865adaf4d1582c756ade81a7e2547cdc05f Log: Merge branch '

JENKINS-14538
' of github.com:daniel-beck/jenkins into 

JENKINS-14538
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 

[JIRA] [core] (JENKINS-14538) Separate "configure tools" page

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-14538 
 
 
 
  Separate "configure tools" page  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-14538) Separate "configure tools" page

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-14538 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Separate "configure tools" page  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/Functions.java core/src/main/java/hudson/model/Descriptor.java core/src/main/java/hudson/model/ManageJenkinsAction.java core/src/main/java/hudson/tools/ToolDescriptor.java core/src/main/java/jenkins/management/ConfigureLink.java core/src/main/java/jenkins/model/GlobalConfiguration.java core/src/main/java/jenkins/model/GlobalConfigurationCategory.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/java/jenkins/mvn/GlobalMavenConfig.java core/src/main/java/jenkins/tools/GlobalToolConfiguration.java core/src/main/java/jenkins/tools/ToolConfigurationCategory.java core/src/main/resources/hudson/logging/LogRecorder/sidepanel.jelly core/src/main/resources/hudson/logging/LogRecorderManager/index.jelly core/src/main/resources/hudson/logging/LogRecorderManager/sidepanel.jelly core/src/main/resources/hudson/model/ComputerSet/index.jelly core/src/main/resources/hudson/model/ComputerSet/sidepanel.jelly core/src/main/resources/hudson/model/Label/sidepanel.jelly core/src/main/resources/hudson/model/UpdateCenter/sidepanel.jelly core/src/main/resources/hudson/model/User/sidepanel.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/index.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/sidepanel.jelly core/src/main/resources/jenkins/management/Messages.properties core/src/main/resources/jenkins/tools/GlobalToolConfiguration/index.groovy core/src/main/resources/lib/hudson/project/configurable.jelly test/src/test/java/hudson/model/HudsonTest.java test/src/test/java/hudson/tasks/MavenTest.java test/src/test/java/hudson/tools/JDKInstallerTest.java http://jenkins-ci.org/commit/jenkins/82d3eb8644ad1729e6e3444ed8f2d58c1bfee79b Log: Merge pull request #2140 from amuniz/

JENKINS-14538
 
[FIX JENKINS-14538] Move tool configuration to separate page 
Compare: https://github.com/jenkinsci/jenkins/compare/547f304b0b26...82d3eb8644ad 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
  

[JIRA] [core] (JENKINS-14538) Separate "configure tools" page

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-14538 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Separate "configure tools" page  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: Jenkinsfile README.md changelog.html cli/pom.xml core/pom.xml core/src/filter/resources/hudson/model/UpdateCenter/CoreUpdateMonitor/message_pl.properties core/src/main/java/hudson/ClassicPluginStrategy.java core/src/main/java/hudson/EnvVars.java core/src/main/java/hudson/ExtensionFinder.java core/src/main/java/hudson/FilePath.java core/src/main/java/hudson/FileSystemProvisioner.java core/src/main/java/hudson/FileSystemProvisionerDescriptor.java core/src/main/java/hudson/Functions.java core/src/main/java/hudson/Launcher.java core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/ProxyConfiguration.java core/src/main/java/hudson/TcpSlaveAgentListener.java core/src/main/java/hudson/WebAppMain.java core/src/main/java/hudson/cli/AddJobToViewCommand.java core/src/main/java/hudson/cli/BuildCommand.java core/src/main/java/hudson/cli/CLIAction.java core/src/main/java/hudson/cli/CLICommand.java core/src/main/java/hudson/cli/CliProtocol.java core/src/main/java/hudson/cli/CliProtocol2.java core/src/main/java/hudson/cli/ClientAuthenticationCache.java core/src/main/java/hudson/cli/CommandDuringBuild.java core/src/main/java/hudson/cli/ConsoleCommand.java core/src/main/java/hudson/cli/CopyJobCommand.java core/src/main/java/hudson/cli/CreateJobCommand.java core/src/main/java/hudson/cli/CreateNodeCommand.java core/src/main/java/hudson/cli/CreateViewCommand.java core/src/main/java/hudson/cli/DeleteJobCommand.java core/src/main/java/hudson/cli/DeleteNodeCommand.java core/src/main/java/hudson/cli/DeleteViewCommand.java core/src/main/java/hudson/cli/GroovyCommand.java core/src/main/java/hudson/cli/GroovyshCommand.java core/src/main/java/hudson/cli/HelpCommand.java core/src/main/java/hudson/cli/InstallPluginCommand.java core/src/main/java/hudson/cli/InstallToolCommand.java core/src/main/java/hudson/cli/ListJobsCommand.java core/src/main/java/hudson/cli/ListPluginsCommand.java core/src/main/java/hudson/cli/OnlineNodeCommand.java core/src/main/java/hudson/cli/ReloadJobCommand.java core/src/main/java/hudson/cli/RemoveJobFromViewCommand.java core/src/main/java/hudson/cli/SetBuildDisplayNameCommand.java core/src/main/java/hudson/cli/declarative/CLIRegisterer.java core/src/main/java/hudson/cli/handlers/GenericItemOptionHandler.java core/src/main/java/hudson/cli/handlers/NodeOptionHandler.java core/src/main/java/hudson/cli/handlers/ViewOptionHandler.java core/src/main/java/hudson/console/ConsoleLogFilter.java core/src/main/java/hudson/logging/LogRecorder.java core/src/main/java/hudson/model/AbstractBuild.java core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/model/AsyncAperiodicWork.java core/src/main/java/hudson/model/AsyncPeriodicWork.java core/src/main/java/hudson/model/Computer.java core/src/main/java/hudson/model/ComputerSet.java core/src/main/java/hudson/model/Fingerprint.java core/src/main/java/hudson/model/Hudson.java core/src/main/java/hudson/model/Label.java core/src/main/java/hudson/model/LoadStatistics.java core/src/main/java/hudson/model/Node.java core/src/main/java/hudson/model/OverallLoadStatistics.java core/src/main/java/hudson/model/Queue.java core/src/main/java/hudson/model/Result.java core/src/main/java/hudson/model/Run.java core/src/main/java/hudson/model/Slave.java core/src/main/java/hudson/model/TaskListener.java core/src/main/java/hudson/model/View.java core/src/main/java/hudson/model/WorkspaceBrowser.java core/src/main/java/hudson/model/WorkspaceCleanupThread.java core/src/main/java/hudson/node_monitors/AbstractAsyncNodeMonitorDescriptor.java core/src/main/java/hudson/node_monitors/ArchitectureMonitor.java core/src/main/java/hudson/node_monitors/NodeMonitor.java core/src/main/java/hudson/node_monitors/NodeMonitorUpdater.java 

[JIRA] [git-plugin] (JENKINS-15136) Support for "Poll on Master" for git SCM plugin

2016-03-22 Thread jur...@space-marine.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jurgen weber commented on  JENKINS-15136 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support for "Poll on Master" for git SCM plugin  
 
 
 
 
 
 
 
 
 
 
this is not strictly true, you still have an edge case where you may want this. 
https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-FastRemotePolling 
the last polling is turned off for traditional workspace polling depending on what it is polling, if it's just a static branch sure fine, but if you wildcard it then it starts building slaves al lthe time. 
I worked around it by doing http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/ but I feel the feature may still want to be used by some. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [maven-plugin] (JENKINS-20594) Expose parsed maven project version

2016-03-22 Thread scangusk...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott MacDonald edited a comment on  JENKINS-20594 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Expose parsed maven project version  
 
 
 
 
 
 
 
 
 
 {POM_VERSION_MAJOR}.${POM_VERSION_MINOR}.${revision}   is super helpful in CD, especially when using SEMVER which embeds compatibility into the version identifier based on the scope of compatibility of the work.   This allows the pom to contain the software SEMVER version and be a source controlled asset completely specified by the developer making the change (whose knows whether the change is compatible or not) , while allowing   CD to simply add on a unique   increment#  to the existing checked in major.minor  to   indicate a compatible increment   of   the developer specified major.minor compatible SEMVER version checked into the pom.xml.mvn version:set -DnewVersion=${POM_VERSION_MAJOR}.${POM_VERSION_MINOR}.${BUILD_NUMBER}  with the pom be something like 1.0.${revision}  where the major.minor is controlled via checkin by the developer making the compatible or incompatible change,and increment is pulled from CD (like git commit or jenkins build#) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [maven-plugin] (JENKINS-20594) Expose parsed maven project version

2016-03-22 Thread scangusk...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott MacDonald commented on  JENKINS-20594 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Expose parsed maven project version  
 
 
 
 
 
 
 
 
 

 {POM_VERSION_MAJOR}.${POM_VERSION_MINOR}.${revision} is super helpful in CD, especially when using SEMVER which embeds compatibility into the version identifier based on the scope of compatibility of the work. This allows the pom to contain the software SEMVER version and be a source controlled asset completely specified by the developer making the change (whose knows whether the change is compatible or not) , while allowing CD to simply add on a unique increment# to the existing checked in major.minor indicate a compatible increment the developer specified major.minor compatible SEMVER version checked into the pom.xml.  mvn version:set -DnewVersion=${POM_VERSION_MAJOR} 
.$ {POM_VERSION_MINOR} 
.$ {BUILD_NUMBER} 
  
with the pom be something like 1.0.$ {revision} 
 where the major.minor is controlled via checkin by the developer making the compatible or incompatible change,and increment is pulled from CD (like git commit or jenkins build#) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [p4-plugin] (JENKINS-33734) P4 Plugin does not reload UI configuration using the Pipeline Workflow

2016-03-22 Thread cnick...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 C.Nicklaw updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33734 
 
 
 
  P4 Plugin does not reload UI configuration using the Pipeline Workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 C.Nicklaw 
 
 
 

Priority:
 
 Minor Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [p4-plugin] (JENKINS-33734) P4 Plugin does not reload UI configuration using the Pipeline Workflow

2016-03-22 Thread cnick...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 C.Nicklaw created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33734 
 
 
 
  P4 Plugin does not reload UI configuration using the Pipeline Workflow  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Paul Allen 
 
 
 

Attachments:
 

 p4plugin1.png, p4plugin2.png 
 
 
 

Components:
 

 p4-plugin 
 
 
 

Created:
 

 2016/Mar/22 11:29 PM 
 
 
 

Environment:
 

 Jenkins ver. 1.642.3  P4 Plugin ver 1.3.7  Pipeline 1.14  Pipeline: SCM Step 1.14 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 C.Nicklaw 
 
 
 
 
 
 
 
 
 
 
The P4 Plugin does not reload UI configuration within the Pipeline definition SCM section. 
Steps to recreate: 
1. Configure Pipeline 2. Within the Pipeline Definition section select 'Pipeline script from SCM' 3. Select 'Perforce Software' 4. Configure the Plugin 
 
5. Save changes 6. Build Now 
The build triggers correctly, the p4 sync occurs, the script file JenkinsFile is parsed and workflow begins. 
  

[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables

2016-03-22 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-28447 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CpsScmFlowDefinition does not resolve variables  
 
 
 
 
 
 
 
 
 
 
SCM implementations seem to call Run.getEnvironment(TaskListener) so it is possible an implementation of JENKINS-30910 would automatically fix this, but certainly deserves its own integration tests. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [durable-task-plugin] (JENKINS-33456) durable-task 1.8 breaks workflow bat steps

2016-03-22 Thread carpentier...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christophe Carpentier commented on  JENKINS-33456 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: durable-task 1.8 breaks workflow bat steps  
 
 
 
 
 
 
 
 
 
 
I've read this issue history, and man, this doesn't look easy. Might I suggest using START /wait as an alternative to CALL, and use %ERRORLEVEL% to retrieve the result? Source: http://stackoverflow.com/questions/13257571/call-command-vs-start-with-wait-option 
I'd also suggest a kind of unit-test-job that does all kind of calls, start, cmds... and check in which case you manage to get the result; in any case it should not hang. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33246) It is unclear that the items with ** are dependencies during plugin install on 2.0

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33246 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: It is unclear that the items with ** are dependencies during plugin install on 2.0  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/jenkins/install/pluginSetupWizard.properties war/src/main/js/pluginSetupWizardGui.js war/src/main/js/templates/progressPanel.hbs war/src/main/less/pluginSetupWizard.less http://jenkins-ci.org/commit/jenkins/547f304b0b26a3627fe04d023cdad1a63475e5ed Log: Merge pull request #2159 from kzantow/

JENKINS-33246
-show-install-dependency-legend 
[FIX JENKINS-33246] Add a footnote about ** in setup wizard 
Compare: https://github.com/jenkinsci/jenkins/compare/5a9ac399d2f1...547f304b0b26 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33246) It is unclear that the items with ** are dependencies during plugin install on 2.0

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33246 
 
 
 
  It is unclear that the items with ** are dependencies during plugin install on 2.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33246) It is unclear that the items with ** are dependencies during plugin install on 2.0

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33246 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: It is unclear that the items with ** are dependencies during plugin install on 2.0  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: kzantow Path: core/src/main/resources/jenkins/install/pluginSetupWizard.properties war/src/main/js/pluginSetupWizardGui.js war/src/main/js/templates/progressPanel.hbs war/src/main/less/pluginSetupWizard.less http://jenkins-ci.org/commit/jenkins/9fbd7aa5170745f0e724031c4736d8da7a57b55e Log: 

JENKINS-33246
 - add a footnote about required dependencies installing during setup wizard 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [scripttrigger-plugin] (JENKINS-33328) Cannot run trigger script on a slave node

2016-03-22 Thread gregory.boissi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gregory Boissinot resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33328 
 
 
 
  Cannot run trigger script on a slave node  
 
 
 
 
 
 
 
 
 

Change By:
 
 Gregory Boissinot 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [scripttrigger-plugin] (JENKINS-33328) Cannot run trigger script on a slave node

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33328 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot run trigger script on a slave node  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: gboissinot Path: pom.xml http://jenkins-ci.org/commit/scripttrigger-plugin/dd8148845ece3c7a267263800b3d80d22219d4d3 Log: Fix JENKINS-33328 - Cannot run trigger script on a slave node 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [claim-plugin] (JENKINS-33078) The "Claim it" link does not work when apostrophe used in any failure cause

2016-03-22 Thread wo...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 wolfs commented on  JENKINS-33078 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The "Claim it" link does not work when apostrophe used in any failure cause  
 
 
 
 
 
 
 
 
 
 
Paul Hicks: Newlines also cause the same problem 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [scm-sync-configuration-plugin] (JENKINS-33733) SEVERE: Error when retrieving ScmSyncConfig plugin instance => No filtering enabled on current request

2016-03-22 Thread sorin.sbar...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sorin Sbarnea created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33733 
 
 
 
  SEVERE: Error when retrieving ScmSyncConfig plugin instance => No filtering enabled on current request  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Frédéric Camblor 
 
 
 

Components:
 

 scm-sync-configuration-plugin 
 
 
 

Created:
 

 2016/Mar/22 9:24 PM 
 
 
 

Environment:
 

 jenkins-1.654 oracle java 8 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Sorin Sbarnea 
 
 
 
 
 
 
 
 
 
 
Happening when you try to restart Jenkins from GUI, renders Jenkins offline requiring us to restart the service from ssh. 

 

Mar 22, 2016 9:20:05 PM hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter doFilter
SEVERE: Error when retrieving ScmSyncConfig plugin instance => No filtering enabled on current request
java.lang.NullPointerException
	at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.getInstance(ScmSyncConfigurationPlugin.java:321)
	at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:32)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:131)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:125)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
 
   

[JIRA] [claim-plugin] (JENKINS-33078) The "Claim it" link does not work when apostrophe used in any failure cause

2016-03-22 Thread wo...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 wolfs commented on  JENKINS-33078 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The "Claim it" link does not work when apostrophe used in any failure cause  
 
 
 
 
 
 
 
 
 
 
Opened a pull-request to fix the problem: https://github.com/jenkinsci/claim-plugin/pull/20 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [maven-plugin] (JENKINS-24869) POM_VERSION is not resetted

2016-03-22 Thread m...@alludra.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zahir Toufie edited a comment on  JENKINS-24869 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: POM_VERSION is not resetted  
 
 
 
 
 
 
 
 
 
 Experiencing the problem with a similar usecase to Marc Carter. I'm using Jenkins 1.646.I've resorted to adding a shell script to all my build tasks that require the POM_VERSION field; {code} POM_VERSION=`mvn help:evaluate -Dexpression=project.version | sed -n -e '/^\[.*\]/ !{ /^[0-9]/ { p; q } }'` {code}   This bug, get's my vote. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [maven-plugin] (JENKINS-24869) POM_VERSION is not resetted

2016-03-22 Thread m...@alludra.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zahir Toufie commented on  JENKINS-24869 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: POM_VERSION is not resetted  
 
 
 
 
 
 
 
 
 
 
Experiencing the problem with a similar usecase to Marc Carter. I'm using Jenkins 1.646. 
I've resorted to adding a shell script to all my build tasks that require the POM_VERSION field; 
POM_VERSION=`mvn help:evaluate -Dexpression=project.version | sed -n -e '/[.*]/ !{ /[0-9]/  { p; q } 
 }'` 
This bug, get's my vote. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-29326) Workflow sidebar has duplicated Git Build Data links

2016-03-22 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick started work on  JENKINS-29326 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-29326) Workflow sidebar has duplicated Git Build Data links

2016-03-22 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated  JENKINS-29326 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29326 
 
 
 
  Workflow sidebar has duplicated Git Build Data links  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Reopened Open 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ec2-plugin] (JENKINS-32915) Spot instance launched one after another until capacity reached for single task in queue

2016-03-22 Thread deejay.zajac+jenk...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mateusz Zając commented on  JENKINS-32915 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Spot instance launched one after another until capacity reached for single task in queue  
 
 
 
 
 
 
 
 
 
 
Pull request created. 
https://github.com/jenkinsci/ec2-plugin/pull/186 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [job-dsl-plugin] (JENKINS-33081) Multiple Script Execution Order

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33081 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Multiple Script Execution Order  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/src/main/resources/javaposse/jobdsl/plugin/ExecuteDslScripts/help-targets.html http://jenkins-ci.org/commit/job-dsl-plugin/aac03f80f0a271a28dee9caefd3adc315dcd4247 Log: Merge pull request #789 from daspilker/

JENKINS-33081
 


JENKINS-33081
 added documentation about script execution order 
Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/3a2054476087...aac03f80f0a2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [job-dsl-plugin] (JENKINS-33081) Multiple Script Execution Order

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33081 
 
 
 
  Multiple Script Execution Order  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [job-dsl-plugin] (JENKINS-33081) Multiple Script Execution Order

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33081 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Multiple Script Execution Order  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/src/main/resources/javaposse/jobdsl/plugin/ExecuteDslScripts/help-targets.html http://jenkins-ci.org/commit/job-dsl-plugin/7e879ed576efb2acf48d8fcc142e08fe0eda2180 Log: added documentation about script execution order 
[FIXES JENKINS-33081] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [git-parameter-plugin] (JENKINS-33084) Git Parameter plugin should prune stale remote branches

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33084 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git Parameter plugin should prune stale remote branches  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: klimas7 Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java http://jenkins-ci.org/commit/git-parameter-plugin/bb26f5da84453aab2a1a40b7a5f6de9bdc7392b0 Log: JENKINS-33084 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-29326) Workflow sidebar has duplicated Git Build Data links

2016-03-22 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The fix got broken again in 2.4.2. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29326 
 
 
 
  Workflow sidebar has duplicated Git Build Data links  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [seleniumhtmlreport-plugin] (JENKINS-11292) parsing error..when trying to generate selenium report.htmls are being copied

2016-03-22 Thread d...@sisao.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Lorenz edited a comment on  JENKINS-11292 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: parsing error..when trying to generate selenium report.htmls are being copied  
 
 
 
 
 
 
 
 
 
 There is no workaround, the plugin expects  a  html files created by selenium tests. Only these files can be parsed with this plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [seleniumhtmlreport-plugin] (JENKINS-11292) parsing error..when trying to generate selenium report.htmls are being copied

2016-03-22 Thread d...@sisao.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Lorenz edited a comment on  JENKINS-11292 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: parsing error..when trying to generate selenium report.htmls are being copied  
 
 
 
 
 
 
 
 
 
 There is no workaround, the plugin expects  the  a html files created by selenium tests. Only these files can be parsed with this plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [seleniumhtmlreport-plugin] (JENKINS-11292) parsing error..when trying to generate selenium report.htmls are being copied

2016-03-22 Thread d...@sisao.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Lorenz commented on  JENKINS-11292 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: parsing error..when trying to generate selenium report.htmls are being copied  
 
 
 
 
 
 
 
 
 
 
There is no workaround, the plugin expects the a html files created by selenium tests. Only these files can be parsed with this plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-9146) Allow archiving of empty directories to be enabled/disabled

2016-03-22 Thread casey.mcgi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Casey McGinty commented on  JENKINS-9146 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow archiving of empty directories to be enabled/disabled  
 
 
 
 
 
 
 
 
 
 
My build output is 3GB. I really have to zip that to get 1 empty dir? Thanks! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [seleniumhtmlreport-plugin] (JENKINS-33383) report styling denied in Chrome

2016-03-22 Thread d...@sisao.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Lorenz commented on  JENKINS-33383 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: report styling denied in Chrome  
 
 
 
 
 
 
 
 
 
 
In your issue description I can read 'seleniumhq', are you sure that your problem is produced by seleniumhtmlreport plugin? Mabey you could provide a sample test file to reproduce this issue? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [durable-task-plugin] (JENKINS-33456) durable-task 1.8 breaks workflow bat steps

2016-03-22 Thread daniel.weber....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Weber commented on  JENKINS-33456 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: durable-task 1.8 breaks workflow bat steps  
 
 
 
 
 
 
 
 
 
 
We also encountered problems where bat steps dis not finish. It looked like the result.txt file that Jenkins is waiting for was never created although the batch scripts were done. The 2 .bat files and log file existed in the "...@tmp" folder. 
Downgrading durable-tasks to 1.7 helped. 
Running Jenkins 1.625.3 under Windows Server 2008 R2, pipeline plugins versions 1.14. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33728) Illegal state exception if navigating pages during Jenkins 2.0 startup

2016-03-22 Thread kzan...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keith Zantow commented on  JENKINS-33728 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Illegal state exception if navigating pages during Jenkins 2.0 startup  
 
 
 
 
 
 
 
 
 
 
Tom FENNELLY this isn't related to the setup wizard AFAIK, the changed you mentioned were removed anyway, startup is mostly as it was wrt. setup wizard changes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33732) API xml changed format from 1.651 to 1.652

2016-03-22 Thread locopelo...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Astro Ashtar created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33732 
 
 
 
  API xml changed format from 1.651 to 1.652  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Mar/22 8:22 PM 
 
 
 

Environment:
 

 jenkins 1.651 to 1.652+ on a windows server 2008 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Astro Ashtar 
 
 
 
 
 
 
 
 
 
 
Tags format/location has changed from the api/xml when doing a POST to  
Two notable changes for me have been the action/parameter has been removed and the action/cause has been renamed 
https:///job///api/xml 
if this was a freeStyleBuild, then the output would contain a  
// for v1.651 and lower 

 




some parameter name
some parameter values




Started by user astro
astro
astro


// more tags

 

 
// for 1.652 and above 

   

[JIRA] [core] (JENKINS-3227) Empty directories are archived

2016-03-22 Thread casey.mcgi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Casey McGinty edited a comment on  JENKINS-3227 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Empty directories are archived  
 
 
 
 
 
 
 
 
 
 This should have never been  fix  fixed .  Arhiving  Archiving  empty dirs is a  requirements  requirement . If you don't want an empty dir archived, then don't create one or delete it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-3227) Empty directories are archived

2016-03-22 Thread casey.mcgi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Casey McGinty edited a comment on  JENKINS-3227 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Empty directories are archived  
 
 
 
 
 
 
 
 
 
 This should have never been fix. Arhiving empty dirs is a requirements. If you don't want an empty dir archived,  than  then  don't create one  or delete it . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-3227) Empty directories are archived

2016-03-22 Thread casey.mcgi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Casey McGinty commented on  JENKINS-3227 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Empty directories are archived  
 
 
 
 
 
 
 
 
 
 
This should have never been fix. Arhiving empty dirs is a requirements. If you don't want an empty dir archived, than don't create one. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33619) Script definition area rendered over header section

2016-03-22 Thread amu...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Muñiz commented on  JENKINS-33619 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Script definition area rendered over header section  
 
 
 
 
 
 
 
 
 
 
Yes, but there were some changes that make it more difficult to reproduce. Just activate the Snippet Generator and scroll down to see the effect. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-31162) New item categorization and dynamic choice offering

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New item categorization and dynamic choice offering  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: recena Path: src/main/java/hudson/matrix/MatrixProject.java http://jenkins-ci.org/commit/matrix-project-plugin/f675af0bfff201573f99111e7fb601ae9ca9b709 Log: JENKINS-31162 @olivergondza's comment was addressed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-31162) New item categorization and dynamic choice offering

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New item categorization and dynamic choice offering  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: recena Path: src/main/java/hudson/matrix/MatrixProject.java http://jenkins-ci.org/commit/matrix-project-plugin/420f904293600b5ef5183ed24560d02cb106d536 Log: JENKINS-31162 The category idenfifier has been updated 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-31162) New item categorization and dynamic choice offering

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New item categorization and dynamic choice offering  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/hudson/matrix/MatrixProject.java src/main/resources/hudson/matrix/MatrixProject/newJobDetail.jelly src/main/resources/hudson/matrix/MatrixProject/newJobDetail.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_ar.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_da.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_de.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_es.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_et.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_fi.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_fr.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_hi_IN.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_it.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_ja.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_ko.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_nb_NO.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_nl.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_pl.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_pt.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_pt_BR.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_ru.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_sv_SE.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_tr.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_uk.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_zh_CN.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_zh_TW.properties src/main/resources/hudson/matrix/Messages.properties src/main/resources/hudson/matrix/Messages_ar.properties src/main/resources/hudson/matrix/Messages_da.properties src/main/resources/hudson/matrix/Messages_de.properties src/main/resources/hudson/matrix/Messages_es.properties src/main/resources/hudson/matrix/Messages_et.properties src/main/resources/hudson/matrix/Messages_fi.properties src/main/resources/hudson/matrix/Messages_fr.properties src/main/resources/hudson/matrix/Messages_hi_IN.properties src/main/resources/hudson/matrix/Messages_it.properties src/main/resources/hudson/matrix/Messages_ja.properties src/main/resources/hudson/matrix/Messages_ko.properties src/main/resources/hudson/matrix/Messages_nb_NO.properties src/main/resources/hudson/matrix/Messages_nl.properties src/main/resources/hudson/matrix/Messages_pl.properties src/main/resources/hudson/matrix/Messages_pt_BR.properties src/main/resources/hudson/matrix/Messages_ru.properties src/main/resources/hudson/matrix/Messages_sv_SE.properties src/main/resources/hudson/matrix/Messages_tr.properties src/main/resources/hudson/matrix/Messages_uk.properties src/main/resources/hudson/matrix/Messages_zh_CN.properties src/main/resources/hudson/matrix/Messages_zh_TW.properties src/main/webapp/images/48x48/matrixproject.png http://jenkins-ci.org/commit/matrix-project-plugin/79490b45dafad757abe63968103c2106e0ee1f64 Log: Merge pull request #33 from recena/JENKINS-31162 
Support for Item categorization in Jenkins 2 
Compare: https://github.com/jenkinsci/matrix-project-plugin/compare/3628523c9c2d...79490b45dafa 
 
 
 
 
 
 
   

[JIRA] [core] (JENKINS-31162) New item categorization and dynamic choice offering

2016-03-22 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-31162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New item categorization and dynamic choice offering  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: recena Path: src/main/java/hudson/matrix/MatrixProject.java src/main/resources/hudson/matrix/MatrixProject/newJobDetail.jelly src/main/resources/hudson/matrix/MatrixProject/newJobDetail.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_ar.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_da.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_de.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_es.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_et.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_fi.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_fr.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_hi_IN.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_it.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_ja.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_ko.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_nb_NO.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_nl.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_pl.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_pt.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_pt_BR.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_ru.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_sv_SE.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_tr.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_uk.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_zh_CN.properties src/main/resources/hudson/matrix/MatrixProject/newJobDetail_zh_TW.properties src/main/resources/hudson/matrix/Messages.properties src/main/resources/hudson/matrix/Messages_ar.properties src/main/resources/hudson/matrix/Messages_da.properties src/main/resources/hudson/matrix/Messages_de.properties src/main/resources/hudson/matrix/Messages_es.properties src/main/resources/hudson/matrix/Messages_et.properties src/main/resources/hudson/matrix/Messages_fi.properties src/main/resources/hudson/matrix/Messages_fr.properties src/main/resources/hudson/matrix/Messages_hi_IN.properties src/main/resources/hudson/matrix/Messages_it.properties src/main/resources/hudson/matrix/Messages_ja.properties src/main/resources/hudson/matrix/Messages_ko.properties src/main/resources/hudson/matrix/Messages_nb_NO.properties src/main/resources/hudson/matrix/Messages_nl.properties src/main/resources/hudson/matrix/Messages_pl.properties src/main/resources/hudson/matrix/Messages_pt_BR.properties src/main/resources/hudson/matrix/Messages_ru.properties src/main/resources/hudson/matrix/Messages_sv_SE.properties src/main/resources/hudson/matrix/Messages_tr.properties src/main/resources/hudson/matrix/Messages_uk.properties src/main/resources/hudson/matrix/Messages_zh_CN.properties src/main/resources/hudson/matrix/Messages_zh_TW.properties src/main/webapp/images/48x48/matrixproject.png http://jenkins-ci.org/commit/matrix-project-plugin/c36474b9ceabcaa3634aae7e8c8077028a830fa8 Log: JENKINS-31162 Support for Item categorization in Jenkins 2 
 
 
 
 
 
 
 
 
 
 
 
 
   

[JIRA] [core] (JENKINS-33619) Script definition area rendered over header section

2016-03-22 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-33619 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Script definition area rendered over header section  
 
 
 
 
 
 
 
 
 
 
I did not see this today, is it still reproducible? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cloudbees-folder-plugin] (JENKINS-33622) Classic job configuration page shown for Multibranch projects

2016-03-22 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33622 
 
 
 
  Classic job configuration page shown for Multibranch projects  
 
 
 
 
 
 
 
 
 
 
I checked freestyle, standalone Pipeline, and multibranch Pipeline and all seemed as expected—the job types use the new UI, the multibranch used the old UI but still looked fine. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Component/s:
 
 cloudbees-folder-plugin 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 workflow-plugin 
 
 
 

Labels:
 
 2.0  ui workflow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
   

[JIRA] [amazon-ecs-plugin] (JENKINS-33731) iam user is not authorized to perform: ecs:RegisterTaskDefinition on resource: *

2016-03-22 Thread j...@gnshealthcare.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 juyuan cai created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33731 
 
 
 
  iam user is not authorized to perform: ecs:RegisterTaskDefinition on resource: *   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 juyuan cai 
 
 
 

Components:
 

 amazon-ecs-plugin 
 
 
 

Created:
 

 2016/Mar/22 7:29 PM 
 
 
 

Environment:
 

 Jenkins version: 1.642.2, plugin version:1.2 (archives) . I use the docker hub to install Jenkins. 
 
 
 

Labels:
 

 plugin jenkins 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 juyuan cai 
 
 
 
 
 
 
 
 
 
 
I want to add a new cloud and and a new slave template. I use the same iam policy showed in the documentation. And I chose the name of the ECS Cluster to "default". when I created a slave template and click save, it showed the JAVA error " Caused by: com.amazonaws.AmazonServiceException: User: arn:aws:iam::040653710277:user/ecs-jenkinsbot is not authorized to perform: ecs:RegisterTaskDefinition on resource: * (Service: AmazonECS; Status Code: 400; Error Code: AccessDeniedException; Request ID: 8b5a6f59-efa5-11e5-bf1e-5fbd8a5dcc6b)]". After I changed the IAM role, problem solved. However, I just want jenkins to ONLY have permissions to 

[JIRA] [build-pipeline-plugin] (JENKINS-33591) Manual steps broken in Jenkins ver. 1.653

2016-03-22 Thread gius...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Giuseppe Penone commented on  JENKINS-33591 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Manual steps broken in Jenkins ver. 1.653  
 
 
 
 
 
 
 
 
 
 
I restarted the pipe from the beginning but found some problems: 1) the manual step takes the color of the job only if I run it from the pipeline view page and not from the job page 2) when I run the job from the pipeline view page something is wrong because the 'BUILD_USER_ID' key is not set (Set jenkins user build variables from the Build User Vars Plugin) Since I have to run the job from the job page and not from the view to make it work (green) the view page does not take the green color and still has the red from the latest run from the pipeline view page 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [acceptance-test-harness] (JENKINS-33730) ATH needs to be made to work with 2.0

2016-03-22 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33730 
 
 
 
  ATH needs to be made to work with 2.0  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 acceptance-test-harness 
 
 
 

Created:
 

 2016/Mar/22 6:42 PM 
 
 
 

Labels:
 

 2.0 2.0-planned 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Daniel Beck 
 
 
 
 
 
 
 
 
 
 
Acceptance test harness needs to be checked whether it works with the 2.0 targeting changes, and if not, needs to be adapted to work with the 2.0 changes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

[JIRA] [checkmarx-plugin] (JENKINS-33603) SourceControl Type is not supported

2016-03-22 Thread supp...@checkmarx.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Checkmarx Support closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Explanation given 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33603 
 
 
 
  SourceControl Type is not supported  
 
 
 
 
 
 
 
 
 

Change By:
 
 Checkmarx Support 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33729) Jenkins 2.0 cannot restart after massive plugin installation

2016-03-22 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck edited a comment on  JENKINS-33729 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins 2.0 cannot restart after massive plugin installation  
 
 
 
 
 
 
 
 
 
 Possibly  caused  fixed  by https://github.com/jenkinsci/jenkins/commit/a5febd7666fd78542d45428505cc62c067315c43 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [remoting] (JENKINS-5055) server rejected connection: already connected to master

2016-03-22 Thread dmwj...@isomedia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Douglas Wooster edited a comment on  JENKINS-5055 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: server rejected connection: already connected to master  
 
 
 
 
 
 
 
 
 
 We are seeing this issue in Jenkins 1.574, after rebooting the slave machine.Issue is intermittent  - perhaps 1/3 of the time .Slaves are Linux, RHEL 6.4The slave is started from a local /etc/init.d script.Master is also RHEL 6.4 running on Tomcat 7.0.63.JENKINS-28492 was opened last year for the same error message, so I linked the two JIRAs. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.

2016-03-22 Thread dmwj...@isomedia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Douglas Wooster edited a comment on  JENKINS-28492 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection.  
 
 
 
 
 
 
 
 
 
 I am seeing the exact same thing with Jenkins 1.574 , after reboot of the slave .We download the slave.jar from the master before every startup so we know it is current.Both slaves and master are RHEL 6.4 Linux.Slaves are started headless from an init script when the machine is booted.Error occurs about 1/3 of the time.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [checkmarx-plugin] (JENKINS-33603) SourceControl Type is not supported

2016-03-22 Thread elord...@vt.edu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Lordahl commented on  JENKINS-33603 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SourceControl Type is not supported  
 
 
 
 
 
 
 
 
 
 
Good to know. 
While i still think it would be beneficial to bypass zipping & uploading for Source-Control projects, I understand the functionality now. Thank you. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.

2016-03-22 Thread dmwj...@isomedia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Douglas Wooster commented on  JENKINS-28492 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection.  
 
 
 
 
 
 
 
 
 
 
I am seeing the exact same thing with Jenkins 1.574. We download the slave.jar from the master before every startup so we know it is current. Both slaves and master are RHEL 6.4 Linux. Slaves are started headless from an init script when the machine is booted. Error occurs about 1/3 of the time. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33729) Jenkins 2.0 cannot restart after massive plugin installation

2016-03-22 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-33729 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins 2.0 cannot restart after massive plugin installation  
 
 
 
 
 
 
 
 
 
 
Possibly caused by https://github.com/jenkinsci/jenkins/commit/a5febd7666fd78542d45428505cc62c067315c43 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33728) Illegal state exception if navigating pages during Jenkins 2.0 startup

2016-03-22 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom FENNELLY commented on  JENKINS-33728 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Illegal state exception if navigating pages during Jenkins 2.0 startup  
 
 
 
 
 
 
 
 
 
 
Keith Zantow Could this be as a result of the new changes for security setup? I seem to remember there was some behind the scenes changes to the Jenkins instance (I thought we suspected that might cause issues) while the installer is setting up security. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [remoting] (JENKINS-5055) server rejected connection: already connected to master

2016-03-22 Thread dmwj...@isomedia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Douglas Wooster commented on  JENKINS-5055 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: server rejected connection: already connected to master  
 
 
 
 
 
 
 
 
 
 
We are seeing this issue in Jenkins 1.574, after rebooting the slave machine. Issue is intermittent. Slaves are Linux, RHEL 6.4 The slave is started from a local /etc/init.d script. Master is also RHEL 6.4 running on Tomcat 7.0.63. 
JENKINS-28492 was opened last year for the same error message, so I linked the two JIRAs. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33728) Illegal state exception if navigating pages during Jenkins 2.0 startup

2016-03-22 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33728 
 
 
 
  Illegal state exception if navigating pages during Jenkins 2.0 startup  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0  2.0-planned 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33729) Jenkins 2.0 cannot restart after massive plugin installation

2016-03-22 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33729 
 
 
 
  Jenkins 2.0 cannot restart after massive plugin installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0  2.0-planned 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.

2016-03-22 Thread dmwj...@isomedia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Douglas Wooster commented on  JENKINS-28492 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection.  
 
 
 
 
 
 
 
 
 
 
This issue is reporting the same symptoms as 

JENKINS-5055
, which was thought to have been fixed back before the Hudson/Jenkins split, but now has multiple people reporting that the problem is back. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33693) maven builder fails if latest maven on path on windows

2016-03-22 Thread dogf...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 dogfood commented on  JENKINS-33693 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: maven builder fails if latest maven on path on windows  
 
 
 
 
 
 
 
 
 
 
Integrated in  jenkins_main_trunk #4523 [FIXED JENKINS-33693] Do not hardcode .bat extension. (Revision 490adc9d0f4b0ed2c7e3183b18b136c006953824) 
 Result = SUCCESS james nord : 490adc9d0f4b0ed2c7e3183b18b136c006953824 Files :  
 

core/src/main/java/hudson/tasks/Maven.java
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33729) Jenkins 2.0 cannot restart after massive plugin installation

2016-03-22 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33729 
 
 
 
  Jenkins 2.0 cannot restart after massive plugin installation  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Mar/22 5:47 PM 
 
 
 

Labels:
 

 2.0 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
Reproduction steps: 1) Select many plugins for upgrade 2) Update them with "restart after installation option" 
Expected behavior: 
 

Jenkins installs plugins and restarts
 
 
Actual behavior: 
 

Jenkins shuts down the web UI
 

Jenkins does not restart due to "Caused by: java.lang.UnsupportedOperationException at java.util.concurrent.CopyOnWriteArrayList$COWIterator.remove"
 

[JIRA] [safe-restart] (JENKINS-33702) safeRestart fails with Authentication exception

2016-03-22 Thread daniel.m...@gfs.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Mish commented on  JENKINS-33702 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: safeRestart fails with Authentication exception  
 
 
 
 
 
 
 
 
 
 
Upgraded to Major, since it seems that the process gets stuck, never shuts down and requires a kill -9 to restart. This affects all restarts within the application, including the Restart Safely plugin. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33728) Illegal state exception if navigating pages during Jenkins 2.0 startup

2016-03-22 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev edited a comment on  JENKINS-33728 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Illegal state exception if navigating pages during Jenkins 2.0 startup  
 
 
 
 
 
 
 
 
 
 cause: https://github.com/jenkinsci/jenkins/commit/036a8e94ed37cf851f0cafb9cb12c21e3496ed7c  by [~tfennelly]] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-33728) Illegal state exception if navigating pages during Jenkins 2.0 startup

2016-03-22 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33728 
 
 
 
  Illegal state exception if navigating pages during Jenkins 2.0 startup  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Project:
 
 Jenkins  Website 
 
 
 

Key:
 
 WEBSITE JENKINS - 144 33728 
 
 
 

Workflow:
 
 WEBSITE: Software Development Workflow JNJira 
 
 
 

Status:
 
 To Do Open 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 

[JIRA] [safe-restart] (JENKINS-33702) safeRestart fails with Authentication exception

2016-03-22 Thread daniel.m...@gfs.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Mish updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33702 
 
 
 
  safeRestart fails with Authentication exception  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Mish 
 
 
 

Priority:
 
 Minor Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [monitoring-plugin] (JENKINS-31619) java.lang.NoClassDefFoundError: Could not initialize class net.bull.javamelody.I18N

2016-03-22 Thread schristo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Christou commented on  JENKINS-31619 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.NoClassDefFoundError: Could not initialize class net.bull.javamelody.I18N  
 
 
 
 
 
 
 
 
 
 
Tomasz Śniatowski I am wondering if this is caused by the monitoring plugin, and the monitoring jar having the same package path which might confuse the classloader. Potentially fixed by forcing the binaries location: https://github.com/christ66/monitoring-plugin/commit/df81844f763ee416ffe445ad8552d158e62f0db3. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [checkmarx-plugin] (JENKINS-33603) SourceControl Type is not supported

2016-03-22 Thread supp...@checkmarx.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Checkmarx Support commented on  JENKINS-33603 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SourceControl Type is not supported  
 
 
 
 
 
 
 
 
 
 
Eric, 
When initiating the scan from/by Jenkins - the configuration in the web interface of Cx for Source Control will not make any difference as the code will be uploaded from the Jenkins - ignoring the settings in the web interface. Only if you initiate the scan from Cx Web Interface the code will be taken from where it is configured in the web interface.. 
Make sense? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [build-pipeline-plugin] (JENKINS-33591) Manual steps broken in Jenkins ver. 1.653

2016-03-22 Thread gius...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Giuseppe Penone commented on  JENKINS-33591 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Manual steps broken in Jenkins ver. 1.653  
 
 
 
 
 
 
 
 
 
 
Timo Mihaljov thanks for the update, I'll re-run the pipe from the beginning shortly and let you know 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [ant-plugin] (JENKINS-33727) Invoke Ant build step does not work since 1.653

2016-03-22 Thread hugodvr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hugo Reis created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33727 
 
 
 
  Invoke Ant build step does not work since 1.653  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 ant-plugin, core 
 
 
 

Created:
 

 2016/Mar/22 5:03 PM 
 
 
 

Environment:
 

 Jenkins greater than 1.652 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Hugo Reis 
 
 
 
 
 
 
 
 
 
 
IStarting from Jenkins 1.653 with the same plugins versions we noticed that the ant command is created differently and it does not work with our configuration. 
Add build step Invoke Ant with the following values: 
Ant Version: ANT_1.9.4 Targets: -lib D:\ANT_1.9.4\ANT_libs Alpha.i Build File: buildInstallers.xml Properties: iaPath=$ {InstallAnywhereLocation} 
 iaOutputDir=$WORKSPACE iaMergeModulesDir=  
 buildView=$WORKSPACE buildLogsPath=$WORKSPACE installersPath=$WORKSPACE 
1.652 - Command output cmd.exe /C '"D:\ANT_1.9.4\bin\ant.bat -file buildInstallers.xml -DiaOutputDir=D:\JENKINS-WS\Alpha\workspace "-DiaPath=C:\Program Files (x86)\InstallAnywhere 2015" -DbuildLogsPath=D:\JENKINS-WS\Alpha\workspace -DiaMergeModulesDir="" -DbuildView=D:\JENKINS-WS\Alpha\workspace -DinstallersPath=D:\JENKINS-WS\Alpha\workspace -lib 

[JIRA] [job-dsl-plugin] (JENKINS-32785) Deprecate listview -> columns -> lastBuildNode() to generate a new config

2016-03-22 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Will be released in 1.45. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32785 
 
 
 
  Deprecate listview -> columns -> lastBuildNode() to generate a new config  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Spilker 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [security] (JENKINS-31611) Unprivileged user may access plugin uninstall form

2016-03-22 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-31611 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unprivileged user may access plugin uninstall form  
 
 
 
 
 
 
 
 
 
 
Actually there's no way around being able to determine whether a plugin is installed given how Stapler works. If you don't want people to be able to determine which plugins are installed, don't give them read access to your instance. 
Looking into preventing access to this URL. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [packaging] (JENKINS-31814) dpkg error installing jenkins 1.639 on debian platforms

2016-03-22 Thread bl...@covarrubi.as (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Blake Covarrubias edited a comment on  JENKINS-31814 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: dpkg error installing jenkins 1.639 on debian platforms  
 
 
 
 
 
 
 
 
 
 I've been troubleshooting this issue on  a fresh  Ubuntu 14.04  system , and determined the root cause to be incorrect ordering of installation dependencies.APT  attempt  attempts  to install & start Jenkins *before* the installation of openjdk-7-jre-headless. This causes the do_start() function to fail & return a non-zero exit code.My solution is to simply install openjdk-7-jre-headless before Jenkins.apt-get install openjdk-7-jre-headlessapt-get install jenkins 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [packaging] (JENKINS-31814) dpkg error installing jenkins 1.639 on debian platforms

2016-03-22 Thread bl...@covarrubi.as (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Blake Covarrubias commented on  JENKINS-31814 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: dpkg error installing jenkins 1.639 on debian platforms  
 
 
 
 
 
 
 
 
 
 
I've been troubleshooting this issue on Ubuntu 14.04, and determined the root cause to be incorrect ordering of installation dependencies. 
APT attempt to install & start Jenkins before the installation of openjdk-7-jre-headless. This causes the do_start() function to fail & return a non-zero exit code. 
My solution is to simply install openjdk-7-jre-headless before Jenkins. 
apt-get install openjdk-7-jre-headless apt-get install jenkins 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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