[JIRA] [slack-plugin] (JENKINS-33832) Slack Notifications not available directly in Job configuration

2016-03-25 Thread vi...@reachvikas.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vikas Kumar updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33832 
 
 
 
  Slack Notifications not available directly in Job configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vikas Kumar 
 
 
 
 
 
 
 
 
 
 Slack Notifications as shown below is not available directly in the Job configuration but it is in *Post-build Actions* !https://wiki.jenkins-ci.org/download/attachments/75893253/Project_Config_1.png!These options are working correctly in *Post-build Actions*  but this is a bit misleading that post-build action specifies something which should not be before build. !2016-03-26_12-56-31.png|thumbnail!   However, plugin v1.8.1 installed on Jenkins 1.625.3 has the expected options as shown in the [https://wiki.jenkins-ci.org/display/JENKINS/Slack+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] [slack-plugin] (JENKINS-33832) Slack Notifications not available directly in Job configuration

2016-03-25 Thread vi...@reachvikas.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vikas Kumar updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33832 
 
 
 
  Slack Notifications not available directly in Job configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vikas Kumar 
 
 
 

Attachment:
 
 2016-03-26_12-56-31.png 
 
 
 
 
 
 
 
 
 
 Slack Notifications as shown below is not available directly in the Job configuration but it is in *Post-build Actions* !https://wiki.jenkins-ci.org/download/attachments/75893253/Project_Config_1.png!These options are working correctly in *Post-build Actions*  but this is a bit misleading that post-build action specifies something which should not be before build. !attachment-name.jpg|thumbnail!   However, plugin v1.8.1 installed on Jenkins 1.625.3 has the expected options as shown in the [https://wiki.jenkins-ci.org/display/JENKINS/Slack+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] [slack-plugin] (JENKINS-33832) Slack Notifications not available directly in Job configuration

2016-03-25 Thread vi...@reachvikas.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vikas Kumar updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33832 
 
 
 
  Slack Notifications not available directly in Job configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vikas Kumar 
 
 
 
 
 
 
 
 
 
 Slack Notifications  as shown below  is not available directly in the Job configuration but it is in  *  Post-build Actions . *  !https://wiki.jenkins-ci.org/download/attachments/75893253/Project_Config_1.png!These options are working correctly  in *Post-build Actions*  but this is a bit misleading that post-build action specifies something which should  not  be before build. !attachment-name.jpg|thumbnail!   However, plugin v1.8.1 installed on Jenkins 1.625.3 has the expected options as shown in the [https://wiki.jenkins-ci.org/display/JENKINS/Slack+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] [slack-plugin] (JENKINS-33832) Slack Notifications not available directly in Job configuration

2016-03-25 Thread vi...@reachvikas.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vikas Kumar updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33832 
 
 
 
  Slack Notifications not available directly in Job configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vikas Kumar 
 
 
 
 
 
 
 
 
 
 Slack Notifications is not available directly in the Job configuration but it is in Post-build Actions. !https://wiki.jenkins-ci.org/download/attachments/75893253/Project_Config_1.png!These options are working correctly but this is a bit misleading that post-build action specifies something which should be before build.However, plugin v1.8.1 installed on Jenkins 1.625.3 has the expected options as shown in the [ https:// wiki .jenkins-ci.org/display/JENKINS/Slack+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] [slack-plugin] (JENKINS-33832) Slack Notifications not available directly in Job configuration

2016-03-25 Thread vi...@reachvikas.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vikas Kumar created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33832 
 
 
 
  Slack Notifications not available directly in Job configuration  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kurt Madel 
 
 
 

Components:
 

 slack-plugin 
 
 
 

Created:
 

 2016/Mar/26 2:01 AM 
 
 
 

Environment:
 

 Jenkins v1.642.3  Slack Notification Plugin v2.0.1 
 
 
 

Labels:
 

 plugin jenkins slack 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Vikas Kumar 
 
 
 
 
 
 
 
 
 
 
Slack Notifications is not available directly in the Job configuration but it is in Post-build Actions.  
 
These options are working correctly but this is a bit misleading that post-build action specifies something which should be before build. 
However, plugin v1.8.1 installed on Jenkins 1.625.3 has the expected options as shown in the [wiki]

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

2016-03-25 Thread alv...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33591 
 
 
 
  Manual steps broken in Jenkins ver. 1.653  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Alvizu 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25 Thread alv...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Merged and released in 1.5.2 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33591 
 
 
 
  Manual steps broken in Jenkins ver. 1.653  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Alvizu 
 
 
 

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] [git-parameter-plugin] (JENKINS-33831) Revision Parameter Type: ArrayIndexOutOfBoundsException

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

 
 
 
 
 
 
 
  Re: Revision Parameter Type: ArrayIndexOutOfBoundsException  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: klimas7 Path: pom.xml src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterValue.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/RevisionInfo.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/RevisionInfoFactory.java http://jenkins-ci.org/commit/git-parameter-plugin/129d4aff456c3b3ce5b3de0ab6b37e12e14ba830 Log: JENKINS-33831 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33831) Revision Parameter Type: ArrayIndexOutOfBoundsException

2016-03-25 Thread klim...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Boguslaw Klimas started work on  JENKINS-33831 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Boguslaw Klimas 
 
 
 

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] [git-parameter-plugin] (JENKINS-33831) Revision Parameter Type: ArrayIndexOutOfBoundsException

2016-03-25 Thread klim...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Boguslaw Klimas created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33831 
 
 
 
  Revision Parameter Type: ArrayIndexOutOfBoundsException  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Boguslaw Klimas 
 
 
 

Components:
 

 git-parameter-plugin 
 
 
 

Created:
 

 2016/Mar/25 11:39 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Boguslaw Klimas 
 
 
 
 
 
 
 
 
 
 
When author revision had negative offset Eg. author Gabor Liptak  1359406662 -0500 
we get exception: 
net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition prettyRevisionInfo SEVERE: Unexpected error  java.lang.ArrayIndexOutOfBoundsException: 1 at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.prettyRevisionInfo(GitParameterDefinition.java:257) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.generateContents(GitParameterDefinition.java:332) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition$DescriptorImpl.doFillValueItems(GitParameterDefinition.java:453) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at

[JIRA] [core] (JENKINS-33830) Hooks to get plugin lifecycle events

2016-03-25 Thread vivek.pan...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vivek Pandey created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33830 
 
 
 
  Hooks to get plugin lifecycle events  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Mar/25 11:27 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Vivek Pandey 
 
 
 
 
 
 
 
 
 
 
Some plugin might like to do interesting things with plugin lifecycle, when a plugin is installed or uninstalled.  
There is InitReactorListener interface but it gets loaded way early during boot time and the InitReactorListener implementations inside plugins never get loaded to receive post-boot plugin lifecycle events.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[JIRA] [core] (JENKINS-33755) Jenkins 2.0 - New Item interface does not print validation messages

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

 
 
 
 
 
 
 
  Re: Jenkins 2.0 - New Item interface does not print validation messages  
 
 
 
 
 
 
 
 
 
 
Possibly same root cause as JENKINS-33774: the validation _javascript_ is apparently inactive on this 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] [job-dsl-plugin] (JENKINS-33829) Support CMake plugin

2016-03-25 Thread victormartinezru...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Victor Martinez started work on  JENKINS-33829 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Victor Martinez 
 
 
 

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] [job-dsl-plugin] (JENKINS-33829) Support CMake plugin

2016-03-25 Thread victormartinezru...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Victor Martinez updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33829 
 
 
 
  Support CMake plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Victor Martinez 
 
 
 
 
 
 
 
 
 
 https://wiki.jenkins-ci.org/display/JENKINS/ MSBuild CMake +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] [job-dsl-plugin] (JENKINS-33829) Support CMake plugin

2016-03-25 Thread victormartinezru...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Victor Martinez created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33829 
 
 
 
  Support CMake plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Victor Martinez 
 
 
 

Components:
 

 job-dsl-plugin 
 
 
 

Created:
 

 2016/Mar/25 11:10 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Victor Martinez 
 
 
 
 
 
 
 
 
 
 
https://wiki.jenkins-ci.org/display/JENKINS/MSBuild+Plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

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

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

 
 
 
 
 
 
 
  Re: Manual steps broken in Jenkins ver. 1.653  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Timo Mihaljov Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java http://jenkins-ci.org/commit/build-pipeline-plugin/d56ff03bf4838c541e68f4cfc06f59ba78d12317 Log: JENKINS-33591 Don't modify CauseAction's causes 
The cause list is immutable as described in the comments of 

JENKINS-33467
. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25 Thread scm_issue_l...@java.net (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-33591 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Manual steps broken in Jenkins ver. 1.653  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Dan Alvizu Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java http://jenkins-ci.org/commit/build-pipeline-plugin/281fe1d7c66eb25a2e27009fe064c5f7836fd2bf Log: Merge pull request #97 from noidi/JENKINS-33591 
Fix JENKINS-33591: Manual steps broken in Jenkins ver. 1.653 
Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/3b4634ec3425...281fe1d7c66e 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33467) CauseAction.causes can become huge

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

 
 
 
 
 
 
 
  Re: CauseAction.causes can become huge  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Timo Mihaljov Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java http://jenkins-ci.org/commit/build-pipeline-plugin/d56ff03bf4838c541e68f4cfc06f59ba78d12317 Log: JENKINS-33591 Don't modify CauseAction's causes 
The cause list is immutable as described in the comments of 

JENKINS-33467
. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [suppress-stack-trace-plugin] (JENKINS-33685) filter stacktrace in all cases

2016-03-25 Thread ifernandezca...@cloudbees.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ivan Fernandez Calvo commented on  JENKINS-33685 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: filter stacktrace in all cases  
 
 
 
 
 
 
 
 
 
 
I changed it to had three options to choice: Users - It suppress stack trace for users, administrators could see the stack trace. Users and administrators -It always suppress stack trace even if the user is administrator. Nobody - It always shows the stack trace. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [clover-plugin] (JENKINS-33610) IOException with Clover 4.6 plugin

2016-03-25 Thread robertx.mie...@intel.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Miesen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33610 
 
 
 
  IOException with Clover 4.6 plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robert Miesen 
 
 
 

Comment:
 
 I can confirm that we are experiencing the same issues after we upgraded the clover plugin to version 4.6.We are running Jenkins 1.642.2 LTS. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33799) Githhub Organization Folder icon is not scaled

2016-03-25 Thread k...@kohsuke.org (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kohsuke Kawaguchi edited a comment on  JENKINS-33799 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Githhub Organization Folder icon is not scaled  
 
 
 
 
 
 
 
 
 
 The problem is because default avatars like [this|https://avatars.githubusercontent.com/u/7169964?v=3= 300 100 ] is not responding to the size specifier parameter 's' unlike explicit avatars like [this|https://avatars2.githubusercontent.com/u/107424?v=3=100] . Both images should be served as 100px by 100px but only the latter is. So the plugin ends up serving a URL to an  tag that's too big.To fix this in a plugin requires us to proxy, resize, and cache avatar images, which also requires up-to-date check. In contrast, we can fix this in the core much easily by just fixing the height and width settings to CSS. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33799) Githhub Organization Folder icon is not scaled

2016-03-25 Thread k...@kohsuke.org (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kohsuke Kawaguchi updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33799 
 
 
 
  Githhub Organization Folder icon is not scaled  
 
 
 
 
 
 
 
 
 
 
The problem is because default avatars like this is not responding to the size specifier parameter 's' unlike explicit avatars like this 
So the plugin ends up serving a URL to an  tag that's too big. 
To fix this in a plugin requires us to proxy, resize, and cache avatar images, which also requires up-to-date check. In contrast, we can fix this in the core much easily by just fixing the height and width settings to CSS. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Kohsuke Kawaguchi 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 github-organization-folder-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

[JIRA] [github-organization-folder-plugin] (JENKINS-33799) Githhub Organization Folder icon is not scaled

2016-03-25 Thread pw...@cloudbees.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Wolf commented on  JENKINS-33799 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Githhub Organization Folder icon is not scaled  
 
 
 
 
 
 
 
 
 
 
This also happens when I connect to a legitimate repo owner in GH. I dont know if it is only default pictures or with custom icons. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-organization-folder-plugin] (JENKINS-33799) Githhub Organization Folder icon is not scaled

2016-03-25 Thread k...@kohsuke.org (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kohsuke Kawaguchi started work on  JENKINS-33799 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Kohsuke Kawaguchi 
 
 
 

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] [core] (JENKINS-33828) Jenkins 2.0 plugins setup wizard - empty suggested

2016-03-25 Thread michal.c.slusarc...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Slusarczyk updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33828 
 
 
 
  Jenkins 2.0 plugins setup wizard - empty suggested   
 
 
 
 
 
 
 
 
 

Change By:
 
 Michal Slusarczyk 
 
 
 
 
 
 
 
 
 
 See screenshot, steps to reproduce:1. Go to 'Select plugins to install' 2. Select 'None'3. Click 'Back'4. Go to 'Install suggested plugins'.Also 'Recommended' in 'Select plugins to install' is not restoring initial state if I uncheck  plugins  manually. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33828) Jenkins 2.0 plugins setup wizard - empty suggested

2016-03-25 Thread michal.c.slusarc...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michal Slusarczyk created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33828 
 
 
 
  Jenkins 2.0 plugins setup wizard - empty suggested   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 Screen Shot 2016-03-25 at 1.07.33 PM.png 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Mar/25 9:17 PM 
 
 
 

Environment:
 

 docker image: jenkinsci/jenkins:2.0-beta-1  browser: Chrome Version 49.0.2623.87 (64-bit), OS X El Capitan 
 
 
 

Labels:
 

 2.0 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Michal Slusarczyk 
 
 
 
 
 
 
 
 
 
 
See screenshot, steps to reproduce: 1. Go to 'Select plugins to install'  2. Select 'None' 3. Click 'Back' 4. Go to 'Install suggested plugins'. 
Also 'Recommended' in 'Select plugins to install' is not

[JIRA] [core] (JENKINS-22008) buildTimeTrend only shows the last 20 builds

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

 
 
 
 
 
 
 
  Re: buildTimeTrend only shows the last 20 builds  
 
 
 
 
 
 
 
 
 
 
See related JENKINS-23244. It is a little complicated since the node build history page shows both a textual table, which is rendered incrementally; and a graphical timeline, which is not rendered incrementally (blocks a handler thread getting data), and which only shows 20 records (if it ever gets that many!) as a partial workaround. 
Even if everything is rendered incrementally (and, in the case of the timeline, also on demand by scrolling), leaving the page open (or scrolling) could impose a burden on the server, though at least there is no risk that some runaway thread will freeze the server indefinitely: you just need to navigate away. Maybe UIs like this could impose some kind of throttling, so that only up to 10 build records per seconds could be loaded in the entire system in response to UI navigation (batch processes could be exempted). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25 Thread alv...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu commented on  JENKINS-33591 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Manual steps broken in Jenkins ver. 1.653  
 
 
 
 
 
 
 
 
 
 
I tested and I see the same behavior in Jenkins 1.646 / build pipeline 1.5.1 and in Jenkins 1.654 / build pipeline with Timo Mihaljov's change, with respect to the Build User Vars Plugin: downstream variables show up if the 'Set Jenkins User Variables' box is checked, and do not if it is not. Parameter / cause information appears to be copied correctly. This is okay to merge from my perspective.  
Giuseppe Penone - If you can document the issue and the expected behavior before this patch, please do so! This looks good from my testing. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33827) Git build chooser only obeys first child of the extensions section

2016-03-25 Thread zmeggy...@skawa.hu (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zalan Meggyesi created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33827 
 
 
 
  Git build chooser only obeys first child of the extensions section  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 

Components:
 

 git-plugin 
 
 
 

Created:
 

 2016/Mar/25 8:22 PM 
 
 
 

Environment:
 

 git-plugin 2.4.4  Jenkins 1.653 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Zalan Meggyesi 
 
 
 
 
 
 
 
 
 
 
This issue was spun out of 

JENKINS-33695
. 
Consider the following snippet from a job config.xml: 

 

"hudson.plugins.git.GitSCM" plugin="git@2.4.4">
	2
	
		
			gitlab
			[URL]
			[CREDENTIAL]
		
	
	
		
			**/master
		
		
			**/bleeding
		
	
	false
	"list"/>
	
		
			"hudson.plugins.git.util.AncestryBuildChooser">
14

			
		
		
			"hudson.plugins.git.util.InverseBuildChooser"/>
		
	

 

 
According to this snippet, there should be two criteria for selecting a commit to build - it should both be less than 14 days old, and it should not be the master or bleeding branch (i.e. the chosen commit would be

[JIRA] [core] (JENKINS-22008) buildTimeTrend only shows the last 20 builds

2016-03-25 Thread jgl...@cloudbees.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-22008 
 
 
 
  buildTimeTrend only shows the last 20 builds  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33805) Integrate upgrade wizard step 0 and InstallUtil/InstallState

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

 
 
 
 
 
 
 
  Re: Integrate upgrade wizard step 0 and InstallUtil/InstallState  
 
 
 
 
 
 
 
 
 
 
Keith Zantow Great idea, not towards 2.0 though. This issue is about investigating whether something can be done for that release to not introduce this redundant and possibly temporary system. If the answer is "no", that's a bit ugly but not the end of the world. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [parameterized-remote-trigger-plugin] (JENKINS-33679) Jenkins 1.653 breaks Parameterized-Remote-Trigger-Plugin

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

 
 
 
 
 
 
 
  Re: Jenkins 1.653 breaks Parameterized-Remote-Trigger-Plugin  
 
 
 
 
 
 
 
 
 
 
To clarify, the upcoming Jenkins release (around Sunday/Monday or so as usual) will not include the faulty version of the component that caused this. There's nothing you can do about it until then other than downgrading to 1.651. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-client-plugin] (JENKINS-33695) Git plugin writing out incorrect settings

2016-03-25 Thread mark.earl.wa...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-33695 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git plugin writing out incorrect settings  
 
 
 
 
 
 
 
 
 
 
That likely means I did some damage at some other point and inadvertently caused a loss of functionality. 
If you can isolate the version number where the behavior changed, that would help the investigation. I'd prefer that come in a separate bug report, since I think it is a different change than this change. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25 Thread alv...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu started work on  JENKINS-33591 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Dan Alvizu 
 
 
 

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] [build-pipeline-plugin] (JENKINS-33591) Manual steps broken in Jenkins ver. 1.653

2016-03-25 Thread alv...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu commented on  JENKINS-33591 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Manual steps broken in Jenkins ver. 1.653  
 
 
 
 
 
 
 
 
 
 
Giuseppe Penone- can you elaborate on issue #1 in your last comment: you have a job you start with 'Build Other Projects (Manual Trigger), and if you click 'Build now' in the job page, the pipeline does not update? If so, that is not a regression, it never worked that way  
I would also like more details on #2 - what do you mean by 'run the job' - starting the pipeline with the 'Run' button in the build pipeline view? Retrigger a build? Trigger the 'build manual' step? And to be clear: this is a regression caused by the fix to JENKINS-33591? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25 Thread alv...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu assigned an issue to Dan Alvizu 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33591 
 
 
 
  Manual steps broken in Jenkins ver. 1.653  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Alvizu 
 
 
 

Assignee:
 
 Dan Alvizu 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33805) Integrate upgrade wizard step 0 and InstallUtil/InstallState

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

 
 
 
 
 
 
 
  Re: Integrate upgrade wizard step 0 and InstallUtil/InstallState  
 
 
 
 
 
 
 
 
 
 
I think we should modify the InstallUtil version to be more of an update log. This could be in JSON format or something similar. We could use that to track all version upgrades, downgrades, and attach timestamps and metadata to each version, so things like this we could fairly easily track and display upgrade wizards at version 2.0, 2.1, etc.. Thoughts Kohsuke Kawaguchi Tom FENNELLY Daniel Beck? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25240) DeadBranchStrategy should avoid deleting projects with active jobs

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

 
 
 
 
 
 
 
  Re: DeadBranchStrategy should avoid deleting projects with active jobs  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/DefaultOrphanedItemStrategy.java src/test/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/be15a91e154cf3bed6a09a8a3252078e586155d3 Log: [FIXED JENKINS-25240] Need to consider even nested jobs for purposes of checking running builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25240) DeadBranchStrategy should avoid deleting projects with active jobs

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

 
 
 
 
 
 
 
  Re: DeadBranchStrategy should avoid deleting projects with active jobs  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/DefaultOrphanedItemStrategy.java src/test/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/3857169b4daf828aedaeb4b0e37baa0fba94e560 Log: Merge pull request #46 from jglick/

JENKINS-25240
-redux 


JENKINS-25240
 Need to consider even nested jobs for purposes of checking running builds 
Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/585f91aa2ac9...3857169b4daf 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25240) DeadBranchStrategy should avoid deleting projects with active jobs

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25240 
 
 
 
  DeadBranchStrategy should avoid deleting projects with active jobs  
 
 
 
 
 
 
 
 
 

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] [git-client-plugin] (JENKINS-33695) Git plugin writing out incorrect settings

2016-03-25 Thread zmeggy...@skawa.hu (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zalan Meggyesi commented on  JENKINS-33695 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git plugin writing out incorrect settings  
 
 
 
 
 
 
 
 
 
 
Strange as it may be, it seems that 2.4.2, despite my prior experience, is consistent with 2.4.4, in that both of them only obey the first child node of the . 
I guess at this point, I should open a new issue with that behavior, as the original problem of writing out a mangled XML was 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] [build-pipeline-plugin] (JENKINS-33686) Build triggered via "Build other projects (manual step)" has no connection to upstream job

2016-03-25 Thread alv...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Thanks for the detailed steps, Angelo Veltens - this is a duplicate of JENKINS-33591, so it will be tracked there. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33686 
 
 
 
  Build triggered via "Build other projects (manual step)" has no connection to upstream job  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Alvizu 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33686) Build triggered via "Build other projects (manual step)" has no connection to upstream job

2016-03-25 Thread alv...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33686 
 
 
 
  Build triggered via "Build other projects (manual step)" has no connection to upstream job  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Alvizu 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33686) Build triggered via "Build other projects (manual step)" has no connection to upstream job

2016-03-25 Thread alv...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu assigned an issue to Dan Alvizu 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33686 
 
 
 
  Build triggered via "Build other projects (manual step)" has no connection to upstream job  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Alvizu 
 
 
 

Assignee:
 
 Dan Alvizu 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-branch-source-plugin] (JENKINS-33815) Validation for GH Organizations and GH User Accounts

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

 
 
 
 
 
 
 
  Re: Validation for GH Organizations and GH User Accounts  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/FolderComputation.java src/test/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/c75b77aefa8898ed51b2c499e55d181f8783874d Log: 

JENKINS-33815
 Fixing FolderComputation to properly handle AbortException. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-branch-source-plugin] (JENKINS-33815) Validation for GH Organizations and GH User Accounts

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

 
 
 
 
 
 
 
  Re: Validation for GH Organizations and GH User Accounts  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/FolderComputation.java src/test/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/585f91aa2ac91db4b1ed7fe7123451e8387b1499 Log: Merge pull request #47 from jglick/AbortException 


JENKINS-33815
 Fixing FolderComputation to properly handle AbortException 
Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/26c075fa833a...585f91aa2ac9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33802) Standardize 'one column layout' definitions

2016-03-25 Thread rec...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-33802 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Standardize 'one column layout' definitions  
 
 
 
 
 
 
 
 
 
 
Daniel Beck I agree though it could be include in the next release of Jenkins 1.x. In this way, we can try 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] [job-dsl-plugin] (JENKINS-33825) Support MSBuild plugin

2016-03-25 Thread victormartinezru...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Victor Martinez commented on  JENKINS-33825 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support MSBuild plugin  
 
 
 
 
 
 
 
 
 
 
 

https://github.com/jenkinsci/job-dsl-plugin/pull/808
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33825) Support MSBuild plugin

2016-03-25 Thread victormartinezru...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Victor Martinez resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33825 
 
 
 
  Support MSBuild plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Victor Martinez 
 
 
 

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] [job-dsl-plugin] (JENKINS-33825) Support MSBuild plugin

2016-03-25 Thread victormartinezru...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Victor Martinez started work on  JENKINS-33825 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Victor Martinez 
 
 
 

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] [core] (JENKINS-33810) Release 2.0 Release Candidate

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33810 
 
 
 
  Release 2.0 Release Candidate  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Epic Name:
 
 Bits in 2.0  Release Candidate  RC Downloads 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33826) Build history text badge display cut off and overlaps other content

2016-03-25 Thread kzan...@cloudbees.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keith Zantow created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33826 
 
 
 
  Build history text badge display cut off and overlaps other content  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Keith Zantow 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Mar/25 6:44 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Keith Zantow 
 
 
 
 
 
 
 
 
 
 
Creating build history badges / labels, for example with the Groovy Postbuild plugin, may result in text overlapping page content or being cut off. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent

[JIRA] [bitbucket-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json

2016-03-25 Thread christian.markus.eichenber...@sbb.ch (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christian Eichenberger commented on  JENKINS-28877 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket Plugin unable to parse Bitbucket webhook response json  
 
 
 
 
 
 
 
 
 
 
I've started support for Bitbucket Server (on-premises version): [1] Current status [2] is tested on a sample project but not more than that. Any feedback and contributions welcome! 
[1] https://github.com/jenkinsci/bitbucket-plugin/compare/master...SchweizerischeBundesbahnen:support-for-bitbucketserver?expand=1  [2] https://github.com/SchweizerischeBundesbahnen/bitbucket-plugin/commit/9ab04242bad1682d18729c71ecf3eb125bdacda5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33825) Support MSBuild plugin

2016-03-25 Thread victormartinezru...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Victor Martinez created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33825 
 
 
 
  Support MSBuild plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Victor Martinez 
 
 
 

Components:
 

 job-dsl-plugin 
 
 
 

Created:
 

 2016/Mar/25 6:29 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Victor Martinez 
 
 
 
 
 
 
 
 
 
 
https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin 
Version 1.X doesn't support projectRulePath as 2.X version does 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was

[JIRA] [job-dsl-plugin] (JENKINS-33825) Support MSBuild plugin

2016-03-25 Thread victormartinezru...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Victor Martinez updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33825 
 
 
 
  Support MSBuild plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Victor Martinez 
 
 
 
 
 
 
 
 
 
 https://wiki.jenkins-ci.org/display/JENKINS/ Log MSBuild + Parser+ Plugin Version 1.X doesn't support projectRulePath as 2.X version does 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33795) Support Log Parser plugin

2016-03-25 Thread victormartinezru...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Victor Martinez resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
https://github.com/jenkinsci/job-dsl-plugin/pull/807 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33795 
 
 
 
  Support Log Parser plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Victor Martinez 
 
 
 

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] [job-dsl-plugin] (JENKINS-33795) Support Log Parser plugin

2016-03-25 Thread victormartinezru...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Victor Martinez started work on  JENKINS-33795 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Victor Martinez 
 
 
 

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] [github-organization-folder-plugin] (JENKINS-33799) Githhub Organization Folder icon is not scaled

2016-03-25 Thread k...@kohsuke.org (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kohsuke Kawaguchi commented on  JENKINS-33799 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Githhub Organization Folder icon is not scaled  
 
 
 
 
 
 
 
 
 
 
I think Daniel meant "this shouldn't have that epic link to JENKINS-33810 because it's not a fix in the core." 
I will operate under the assumption that this still needs to be fixed for RC. And FWIW I think this is a fix that needs to happen in core. But I'll investigate. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33805) Integrate upgrade wizard step 0 and InstallUtil/InstallState

2016-03-25 Thread k...@kohsuke.org (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kohsuke Kawaguchi commented on  JENKINS-33805 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Integrate upgrade wizard step 0 and InstallUtil/InstallState  
 
 
 
 
 
 
 
 
 
 
I left this comment in the original PR but I don't think this is achievable. 
What I think we should do instead is to rename the file that UpgradeWizard is using so that it is marked clearly as local to that one class, as opposed to try to be something more universally useful. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33759) New Item option in folders shows the old UI

2016-03-25 Thread rec...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33759 
 
 
 
  New Item option in folders shows the old UI  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 1. #  Create an empty folder and navigate to it 1. #  Click on "Create Item" in it (link: {{/job/Folder/new}}) 1. #  Check the interfaceExpected behavior: Modern UI is being displayedActual behavior: 2.0 UI is being displayed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS

2016-03-25 Thread vinc...@latombe.net (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vincent Latombe commented on  JENKINS-28955 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins unusable after downgrade from latest weekly release to LTS  
 
 
 
 
 
 
 
 
 
 
Submitted https://github.com/jenkinsci/jenkins/pull/2172 to disable plugins whose dependencies are obsolete, which should allow Jenkins to successfully boot without the faulty plugins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [multiple-scms-plugin] (JENKINS-33824) Multiple SCMs (all git repos) where one repo should not trigger a build still causes a build to be triggered

2016-03-25 Thread brittany.john...@ge.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brittany Johnson created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33824 
 
 
 
  Multiple SCMs (all git repos) where one repo should not trigger a build still causes a build to be triggered  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kevin Bell 
 
 
 

Components:
 

 multiple-scms-plugin 
 
 
 

Created:
 

 2016/Mar/25 5:47 PM 
 
 
 

Environment:
 

 1.621 
 
 
 

Labels:
 

 plugin jenkins git 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Brittany Johnson 
 
 
 
 
 
 
 
 
 
 
I have a job which checks out multiple git repositories. Check ins to repository1 should trigger the build to run. Checkins to repository2 should not trigger the build to run. To convey this, repository2 is configured with "Don't trigger build on commit notifications" and "Polling ignores commits in certain paths" where .* is listed as the excluded path. When a check in is made to repository2, the build is still triggered.

[JIRA] [cloudbees-folder-plugin] (JENKINS-33759) New Item option in folders shows the old UI

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

 
 
 
 
 
 
 
  Re: New Item option in folders shows the old UI  
 
 
 
 
 
 
 
 
 
 
Well the main fix is in the Folders plugin anyway. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [parameterized-remote-trigger-plugin] (JENKINS-33679) Jenkins 1.653 breaks Parameterized-Remote-Trigger-Plugin

2016-03-25 Thread buta.adr...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adi Adrian commented on  JENKINS-33679 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins 1.653 breaks Parameterized-Remote-Trigger-Plugin  
 
 
 
 
 
 
 
 
 
 
Could you please indicate how to fix it by downgrading Stapler. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-branch-source-plugin] (JENKINS-33815) Validation for GH Organizations and GH User Accounts

2016-03-25 Thread rec...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33815 
 
 
 
  Validation for GH Organizations and GH User Accounts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

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] [github-branch-source-plugin] (JENKINS-33815) Validation for GH Organizations and GH User Accounts

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

 
 
 
 
 
 
 
  Re: Validation for GH Organizations and GH User Accounts  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java http://jenkins-ci.org/commit/github-branch-source-plugin/34259081f6bd25981186d83770547de98cef401e Log: Merge pull request #35 from recena/

JENKINS-33815
 
Validation for GH Organizations and GH User Accounts 
Compare: https://github.com/jenkinsci/github-branch-source-plugin/compare/eb2b060810a4...34259081f6bd 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33776) Cannot start from preview rpm

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

 
 
 
 
 
 
 
  Re: Cannot start from preview rpm  
 
 
 
 
 
 
 
 
 
 
FWIW given the popularity of Jetty, I don't think an issue with 3 votes and 10 watchers indicates a widely used feature. 
And we're not really able to back this out anyway anymore, we need the Servlet 3 support. This will need to be addressed in the release notes, hoping someone reads them. 
However, what we need to address in Jenkins is the brokenness of packaging, and, depending on how upgrading those works, whether we need to downgrade from exception to warning being logged in winstone-jetty (so those who have it enabled unnecessarily can still use 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] [github-branch-source-plugin] (JENKINS-33815) Validation for GH Organizations and GH User Accounts

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

 
 
 
 
 
 
 
  Re: Validation for GH Organizations and GH User Accounts  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java http://jenkins-ci.org/commit/github-branch-source-plugin/d1e16ba8a3065f98c38415fdaaef95f3b5131ed0 Log: 

JENKINS-33815
 Validation for GH Organizations and GH User Accounts 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-branch-source-plugin] (JENKINS-33815) Validation for GH Organizations and GH User Accounts

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

 
 
 
 
 
 
 
  Re: Validation for GH Organizations and GH User Accounts  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java http://jenkins-ci.org/commit/github-branch-source-plugin/13dbeef0d3e6173dc8cf29e305829f835c51b781 Log: 

JENKINS-33815
 @jglick's comment was addresed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy

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

 
 
 
 
 
 
 
  Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy  
 
 
 
 
 
 
 
 
 
 
Geoffroy Jabouley Not automatically, as it was only merged into 1.653, and the next LTS line is based on 1.651. But now at least there's a chance. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy

2016-03-25 Thread geoffroy.jabou...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoffroy Jabouley commented on  JENKINS-28289 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy  
 
 
 
 
 
 
 
 
 
 
Hello do you think this fix will make its way to a jenkins 1.X LTS release before jenkins 2.0? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [clover-plugin] (JENKINS-33610) IOException with Clover 4.6 plugin

2016-03-25 Thread robertx.mie...@intel.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Miesen commented on  JENKINS-33610 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: IOException with Clover 4.6 plugin  
 
 
 
 
 
 
 
 
 
 
I can confirm that we are experiencing the same issues after we upgraded the clover plugin to version 4.6. 
We are running Jenkins 1.642.2 LTS. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28955) Jenkins unusable after downgrade from latest weekly release to LTS

2016-03-25 Thread vinc...@latombe.net (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vincent Latombe commented on  JENKINS-28955 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins unusable after downgrade from latest weekly release to LTS  
 
 
 
 
 
 
 
 
 
 
Hit that problem as well. To me the crux of the issue is that plugins dependency checking doesn't verify required versions, it only checks if dependencies are installed. 
Then comes the Extension phase and everything blows up because extensions of all loaded plugins are loaded at the same time and we can't disable faulty plugins anymore. 
I think it would be much safer to just disable plugins for which dependencies are outdated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33805) Integrate upgrade wizard step 0 and InstallUtil/InstallState

2016-03-25 Thread db...@cloudbees.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck assigned an issue to Keith Zantow 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Keith Zantow Could you PTAL whether this can be handled towards 2.0 with reasonable effort? I suspect it might not. 
CC Kohsuke Kawaguchi 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33805 
 
 
 
  Integrate upgrade wizard step 0 and InstallUtil/InstallState  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0 2.0-beta  2.0-planned 
 
 
 

Assignee:
 
 Keith Zantow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33804) 2.0 upgrade wizard banner design should be improved

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33804 
 
 
 
  2.0 upgrade wizard banner design should be improved  
 
 
 
 
 
 
 
 
 
 
Needed towards 2.0 RC otherwise useless given Step 1 follows in 2.1. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0 2.0-beta  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] [winstone-jetty] (JENKINS-33814) Re-release Winstone-Jetty with correct version number

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33814 
 
 
 
  Re-release Winstone-Jetty with correct version number  
 
 
 
 
 
 
 
 
 
 
Not needed towards 2.0, this has been wrong for a looong 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-33804) 2.0 upgrade wizard banner design should be improved

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

 
 
 
 
 
 
 
  Re: 2.0 upgrade wizard banner design should be improved  
 
 
 
 
 
 
 
 
 
 
No. You wrote it doesn't look good, so I filed this issue 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-33800) java.io.FileNotFoundException: /var/jenkins_home/secrets/initialAdminPassword when upgrading from 1.642.2 LTS to 2.0-beta-1

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33800 
 
 
 
  java.io.FileNotFoundException: /var/jenkins_home/secrets/initialAdminPassword when upgrading from 1.642.2 LTS to 2.0-beta-1  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0 2.0-beta  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-33802) Standardize 'one column layout' definitions

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33802 
 
 
 
  Standardize 'one column layout' definitions  
 
 
 
 
 
 
 
 
 
 
This is for post 2.0. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33813) 2.0 Setup wizard: No valid crumb was included in the request

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33813 
 
 
 
  2.0 Setup wizard: No valid crumb was included in the request  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Priority:
 
 Critical Major 
 
 
 

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-33813) 2.0 Setup wizard: No valid crumb was included in the request

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

 
 
 
 
 
 
 
  Re: 2.0 Setup wizard: No valid crumb was included in the request  
 
 
 
 
 
 
 
 
 
 
Suggestion looks good. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-organization-folder-plugin] (JENKINS-33799) Githhub Organization Folder icon is not scaled

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33799 
 
 
 
  Githhub Organization Folder icon is not scaled  
 
 
 
 
 
 
 
 
 
 
Not needed for 2.0 RC. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0-beta  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-33801) New config form "remove" buttons need tooltip with former label

2016-03-25 Thread db...@cloudbees.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck assigned an issue to gus reiber 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
gus reiber Is this straightforward to implement? 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33801 
 
 
 
  New config form "remove" buttons need tooltip with former label  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0 2.0-beta  2.0-planned 
 
 
 

Assignee:
 
 gus reiber 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-organization-folder-plugin] (JENKINS-33797) Github Organization folder creation causes exception with space in job name

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33797 
 
 
 
  Github Organization folder creation causes exception with space in job name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0-beta  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] [cloudbees-folder-plugin] (JENKINS-33759) New Item option in folders shows the old UI

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33759 
 
 
 
  New Item option in folders shows the old UI  
 
 
 
 
 
 
 
 
 
 
RC can happen without this. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0  2.0-planned  ui 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-organization-folder-plugin] (JENKINS-33797) Github Organization folder creation causes exception with space in job name

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33797 
 
 
 
  Github Organization folder creation causes exception with space in job name  
 
 
 
 
 
 
 
 
 
 
RC can happen without this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33765) Configure S3 at folder level

2016-03-25 Thread jgl...@cloudbees.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Won't Do 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Not a Folders issue, and no clear proposal for how this would work. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33765 
 
 
 
  Configure S3 at folder level  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Won't Do 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33762) Configure JDK at folder level

2016-03-25 Thread jgl...@cloudbees.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Won't Do 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Not a Folders issue, and no clear proposal for how this would work. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33762 
 
 
 
  Configure JDK at folder level  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Won't Do 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33764) Configure SSH credentials at folder level

2016-03-25 Thread jgl...@cloudbees.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
You can already do this with folder-scoped credentials. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33764 
 
 
 
  Configure SSH credentials at folder level  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open Resolved 
 
 
 

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-33774) 'Create Item' does not support autocompleting the 'Copy from' field

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

 
 
 
 
 
 
 
  Re: 'Create Item' does not support autocompleting the 'Copy from' field  
 
 
 
 
 
 
 
 
 
 
Generally there is no network traffic from either the job name or copy text fields, so it is not just this which is broken: there is also no checking that the job is not being named, for example, \$. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [branch-api-plugin] (JENKINS-33808) Prove that richer Create Item API works by implementing for GH Org folders.

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33808 
 
 
 
  Prove that richer Create Item API works by implementing for GH Org folders.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Component/s:
 
 core 
 
 
 

Labels:
 
 2.0 2.0-beta  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-33809) Find out what's wrong with the tests on the 2.0 branch requiring so much RAM

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33809 
 
 
 
  Find out what's wrong with the tests on the 2.0 branch requiring so much RAM  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0 2.0-beta  2.0-planned  regression 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [copyartifact-plugin] (JENKINS-33772) Find out what's wrong with Copy Artifact failing to load in 2.0

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33772 
 
 
 
  Find out what's wrong with Copy Artifact failing to load in 2.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0 2.0-beta  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-33803) Review all new API in 2.0 for @Restricted

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33803 
 
 
 
  Review all new API in 2.0 for @Restricted  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0 2.0-beta  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-33770) Setup wizard login trivial to circumvent

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33770 
 
 
 
  Setup wizard login trivial to circumvent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0 2.0-beta  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-33807) Document all new system properties in wiki

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33807 
 
 
 
  Document all new system properties in wiki  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0 2.0-beta  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] [packaging] (JENKINS-33776) Cannot start from preview rpm

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33776 
 
 
 
  Cannot start from preview rpm  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0  2.0-beta 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-33755) Jenkins 2.0 - New Item interface does not print validation messages

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33755 
 
 
 
  Jenkins 2.0 - New Item interface does not print validation messages  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0  2.0-planned  regression ui 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33774) 'Create Item' does not support autocompleting the 'Copy from' field

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33774 
 
 
 
  'Create Item' does not support autocompleting the 'Copy from' field  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 2.0 2.0-beta  2.0-planned  regression 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33802) Standardize 'one column layout' definitions

2016-03-25 Thread rec...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-33802 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Standardize 'one column layout' definitions  
 
 
 
 
 
 
 
 
 
 
Daniel Beck, IMHO does not make sense that versus. PR-2029 is based on  and is designed to support new options easily. And PR-2121 has solved full-width screen ad-hoc becuase it was needed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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   >