[JIRA] [timestamper-plugin] (JENKINS-30429) Ability to change color of timestamps

2016-02-20 Thread stevengbr...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven G Brown resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I've realised this is already possible by changing the format on the Configure System page. Example: 

 

'"color:blue;">'HH:mm:ss' '
 

 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30429 
 
 
 
  Ability to change color of timestamps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steven G Brown 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 Steven G Brown 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You 

[JIRA] [core] (JENKINS-33060) Session timeout doesn't work at top page even if auto reload is false

2016-02-20 Thread masanori.sa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Masanori Satoh created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33060 
 
 
 
  Session timeout doesn't work at top page even if auto reload is false  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 スクリーンショット 2016-02-19 19.02.55.png 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 21/Feb/16 4:08 AM 
 
 
 

Environment:
 

 safari 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Masanori Satoh 
 
 
 
 
 
 
 
 
 
 
Session timeout doesn't work at top page, even if auto reload is false. I checked my communication from my browser to Jenkins. Attachment is my developer tool's screenshot. A AJAX is communicating to Jenkins when the browser is foreground. Therefore session timeout doesn't work. I set the session timeout below. JENKINS_ARGS="--sessionTimeout=xxx" 
 
 
 
 
 
 
 
 
 
 
   

[JIRA] [credentials-binding-plugin] (JENKINS-24805) Mask credentials in Build Log

2016-02-20 Thread arumugam1...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arumugam Subramanian commented on  JENKINS-24805 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Mask credentials in Build Log  
 
 
 
 
 
 
 
 
 
 
Having same issue. Android gradle commandline doesnt work with mask password or envinject plugin to pass password as build parameter. Any idea would really helpful. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [throttle-concurrent-builds-plugin] (JENKINS-25326) Throttle Concurrent Builds doesn't work when builds are in cloudbees folders

2016-02-20 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-25326 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Throttle Concurrent Builds doesn't work when builds are in cloudbees folders  
 
 
 
 
 
 
 
 
 
 
Created a new pull request: https://github.com/jenkinsci/throttle-concurrent-builds-plugin/pull/37 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [gerrit-trigger-plugin] (JENKINS-33059) Changing Gerrit trigger configuration requires restart of Jenkins

2016-02-20 Thread will.sa...@greenwayhealth.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Will Saxon created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33059 
 
 
 
  Changing Gerrit trigger configuration requires restart of Jenkins  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 rsandell 
 
 
 

Components:
 

 gerrit-trigger-plugin 
 
 
 

Created:
 

 21/Feb/16 1:49 AM 
 
 
 

Environment:
 

 gerrit-trigger 2.18.3, Jenkins 1.642.1 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Will Saxon 
 
 
 
 
 
 
 
 
 
 
I changed the Gerrit hostname and path of the SSH private key and noted successful connection when clicking the 'Test Connection' button. However, after saving the new configuration, jenkins.log started to get spammed (see below). I was able to add a new server entry and remove the old one to work around this. I assume that if I restarted Jenkins the new configuration would have been used. 

Feb 20, 2016 8:42:51 PM com.sonymobile.tools.gerrit.gerritevents.GerritConnection connect SEVERE: Could not connect to Gerrit server! Host:  Port: 22 Feb 20, 2016 8:42:51 PM com.sonymobile.tools.gerrit.gerritevents.GerritConnection connect SEVERE: Proxy: Feb 20, 2016 8:42:51 PM com.sonymobile.tools.gerrit.gerritevents.GerritConnection connect SEVERE: User:  KeyFile:  Feb 20, 2016 8:42:51 PM com.sonymobile.tools.gerrit.gerritevents.GerritConnection connect SEVERE: IOException: com.sonymobile.tools.gerrit.gerritevents.ssh.SshException: com.jcraft.jsch.JSchException: 

[JIRA] [core] (JENKINS-33058) AbstractProject.Pronoun message is not fullly translatable

2016-02-20 Thread damian.publicem...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damian Szczepanik commented on  JENKINS-33058 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: AbstractProject.Pronoun message is not fullly translatable  
 
 
 
 
 
 
 
 
 
 
I can try to make it work and delete those abstract keys but I need to get some advises how and without causing regressions. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33058) AbstractProject.Pronoun message is not fullly translatable

2016-02-20 Thread damian.publicem...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Damian Szczepanik created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33058 
 
 
 
  AbstractProject.Pronoun message is not fullly translatable  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 20/Feb/16 11:42 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Damian Szczepanik 
 
 
 
 
 
 
 
 
 
 
Message ids such as AbstractProject.Pronoun and AbstractItem.Pronoun are used quite often but they don't allow to provide full and correct translations for many cases. Take a look at following example (Poilsh language) 

 
 

 Message 
 

 English 
 

 Polish 
 
 
 

 Delete {0} 
 

 Delete Project 
 
 

[JIRA] [git-client-plugin] (JENKINS-24728) Add ability to specify shallow clone depth

2016-02-20 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-24728 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add ability to specify shallow clone depth  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Nicholas Jasieniecki Path: src/main/java/hudson/plugins/git/extensions/impl/CloneOption.java src/main/resources/hudson/plugins/git/extensions/impl/CloneOption/config.groovy src/main/resources/hudson/plugins/git/extensions/impl/CloneOption/help-depth.html http://jenkins-ci.org/commit/git-plugin/d96318dcb142d378d31678cfcb0a40841760b5b4 Log: JENKINS-24728 Added UI Elements for shallow clone depth 
Use @DataBoundSetter instead of extending the constructor as was done in the original pull request. The DataBoundSetter annotation simplifies the change. 
Original concept by Nicholas Jasieniecki, with changes by Mark Waite. 
Add help to shallow clone depth setting. 
Add shallow and shallow depth to fetch command options. The previous implementation only set depth on the clone arguments, not on the fetch arguments. Without the depth on the fetch arguments, fetch retrieves history additively, rather than retaining the depth at the originally specified value. That caused the history in a repository which is being reused to grow each time new commits are detected and built by the job. This change now keeps the history at the specified depth even with incremental updates of the repository by new commits. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [p4-plugin] (JENKINS-32454) new option to delete perforce client view & workspace on job deletion

2016-02-20 Thread barn...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Barnish commented on  JENKINS-32454 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: new option to delete perforce client view & workspace on job deletion  
 
 
 
 
 
 
 
 
 
 
Thanks for your comments. It sounds like 1.3.7 will work and we will give that a try. 
FYI we were not using a the "custom workspace" option in the job configuration. The option I was referring to is in the global jenkins configuration "Workspace Root Directory" which is hidden under one of the advanced buttons at the top. It allows us to use a separate disk for the workspaces which are very large in comparison to the jenkins global+job configuration files. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [warnings-plugin] (JENKINS-32150) Cannot resolve relative filenames referencing parent directory

2016-02-20 Thread ullrich.haf...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner commented on  JENKINS-32150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot resolve relative filenames referencing parent directory  
 
 
 
 
 
 
 
 
 
 
Thanks for the valuable test case! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [warnings-plugin] (JENKINS-32150) Cannot resolve relative filenames referencing parent directory

2016-02-20 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot resolve relative filenames referencing parent directory  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/ParserResult.java src/test/java/hudson/plugins/analysis/core/ParserResultTest.java http://jenkins-ci.org/commit/analysis-core-plugin/b864544a789d69fbf59e675465b83426336ebace Log: [FIXED JENKINS-32150] Remove leading relative path components to parent directories when finding files in the workspace. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [warnings-plugin] (JENKINS-32150) Cannot resolve relative filenames referencing parent directory

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32150 
 
 
 
  Cannot resolve relative filenames referencing parent directory  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [cmakebuilder-plugin] (JENKINS-29142) look for MSVC 15.x toolchain

2016-02-20 Thread fifteenknots...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Weber commented on  JENKINS-29142 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: look for MSVC 15.x toolchain  
 
 
 
 
 
 
 
 
 
 
A workaround for MSVC is described in Martin Kutny`s blog. In short, it applies the effect of vcvarsall.bat as follows: 
 

Setup environment variables by running vcvarsall.bat,
 

write all environment vars to a file,
 

use the EnvInject Jenkins Plugin to read the file and pass the required variables to the whole build job.
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [email-ext-plugin] (JENKINS-33035) Editable Email Notification Upgrade Breaks Jenkins Boot Up

2016-02-20 Thread slide.o....@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl started work on  JENKINS-33035 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Alex Earl 
 
 
 

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] [jira-plugin] (JENKINS-32560) jira-plugin generating message in the wrong ticket

2016-02-20 Thread david.br...@efi.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Brown  commented on  JENKINS-32560 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: jira-plugin generating message in the wrong ticket  
 
 
 
 
 
 
 
 
 
 
This sounds like the same issue we are facing (using Jenkins version 1.598 and JIRA plugin version 1.38). 
What I've noticed is that the incorrect updates have only the first line of comment, e.g. "SUCCESS: Integrated in DEV-16-2 #455" whereas a legitimate update will include the full changeset description on subsequent lines. 
In my view this issue should have a higher Priority than Minor/Trivial as users are being misled into believing that changes have been included in builds when they have not been. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jira-plugin] (JENKINS-32170) Support CLI parameter submission for JiraIssueParameterDefinition

2016-02-20 Thread radek.anton...@quiddia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Radek Antoniuk updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32170 
 
 
 
  Support CLI parameter submission for JiraIssueParameterDefinition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Radek Antoniuk 
 
 
 

Labels:
 
 confirmed jira-plugin-2.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jira-plugin] (JENKINS-31113) Configurable HTTP timeout parameter for JiraRestService

2016-02-20 Thread radek.anton...@quiddia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Radek Antoniuk updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31113 
 
 
 
  Configurable HTTP timeout parameter for JiraRestService  
 
 
 
 
 
 
 
 
 

Change By:
 
 Radek Antoniuk 
 
 
 

Labels:
 
 jira-plugin-2.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jira-plugin] (JENKINS-32504) Make JiraEnvironmentVariableBuilder compatible with pipeline

2016-02-20 Thread radek.anton...@quiddia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Radek Antoniuk resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32504 
 
 
 
  Make JiraEnvironmentVariableBuilder compatible with pipeline  
 
 
 
 
 
 
 
 
 

Change By:
 
 Radek Antoniuk 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [jira-plugin] (JENKINS-32492) Rename all dropdown labels to include JIRA: prefix

2016-02-20 Thread radek.anton...@quiddia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Radek Antoniuk assigned an issue to Radek Antoniuk 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32492 
 
 
 
  Rename all dropdown labels to include JIRA: prefix  
 
 
 
 
 
 
 
 
 

Change By:
 
 Radek Antoniuk 
 
 
 

Assignee:
 
 Radek Antoniuk 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jira-plugin] (JENKINS-32492) Rename all dropdown labels to include JIRA: prefix

2016-02-20 Thread radek.anton...@quiddia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Radek Antoniuk updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32492 
 
 
 
  Rename all dropdown labels to include JIRA: prefix  
 
 
 
 
 
 
 
 
 

Change By:
 
 Radek Antoniuk 
 
 
 

Labels:
 
 jira-plugin-2.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jira-plugin] (JENKINS-32504) Make JiraEnvironmentVariableBuilder compatible with pipeline

2016-02-20 Thread radek.anton...@quiddia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Radek Antoniuk updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32504 
 
 
 
  Make JiraEnvironmentVariableBuilder compatible with pipeline  
 
 
 
 
 
 
 
 
 

Change By:
 
 Radek Antoniuk 
 
 
 

Labels:
 
 jira-plugin-2.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [active-directory-plugin] (JENKINS-32710) Configure AD Authorization with Groovy

2016-02-20 Thread jsmic...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Mickey resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32710 
 
 
 
  Configure AD Authorization with Groovy  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Mickey 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [active-directory-plugin] (JENKINS-32710) Configure AD Authorization with Groovy

2016-02-20 Thread jsmic...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Mickey closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32710 
 
 
 
  Configure AD Authorization with Groovy  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Mickey 
 
 
 

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] [jira-plugin] (JENKINS-32504) Make JiraEnvironmentVariableBuilder compatible with pipeline

2016-02-20 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32504 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make JiraEnvironmentVariableBuilder compatible with pipeline  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: jzajic Path: COMPATIBILITY.md src/main/java/hudson/plugins/jira/pipeline/IssueSelectorStep.java src/main/resources/hudson/plugins/jira/Messages.properties http://jenkins-ci.org/commit/jira-plugin/1ada0f3e74be6e447cdbe40ef8178d658bb18edc Log: JENKINS-32504 JiraEnvironmentVariableBuilder and pipeline 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] [active-directory-plugin] (JENKINS-32710) Configure AD Authorization with Groovy

2016-02-20 Thread jsmic...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Mickey commented on  JENKINS-32710 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Configure AD Authorization with Groovy  
 
 
 
 
 
 
 
 
 
 
'site' cannot be nill when configured via Groovy.  Here is an answer: 

 

import jenkins.model.*
import hudson.security.*
import hudson.plugins.active_directory.*
   
def instance = Jenkins.getInstance()
String domain = 'my.domain.com'
String site = 'site'
String server = '192.168.1.1'
String bindName = 'acco...@my.domain.com'
String bindPassword = 'password'
adrealm = new ActiveDirectorySecurityRealm(domain, site, bindName, bindPassword, server)
instance.setSecurityRealm(adrealm)
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-environment-plugin] (JENKINS-33057) Please make thye html output of this better readable by adding contrast

2016-02-20 Thread devopsti...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 DevOps Tiger created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33057 
 
 
 
  Please make thye html output of this better readable by adding contrast  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 build-environment-plugin 
 
 
 

Created:
 

 20/Feb/16 2:06 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 DevOps Tiger 
 
 
 
 
 
 
 
 
 
 
currently this plugin outputs black text on a dark gray background. This is very bad because it is extremely hard to read the actual content of the text when the combination of text and background has very low contrast. Please provide some text output with better contrast, like e.g. black on white. Thanks. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
   

[JIRA] [custom-view-tabs-plugin] (JENKINS-30862) "ugly" formatting of view names using "Custom Views TabBar"

2016-02-20 Thread ringra...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alistair Todd closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Changes released in version 1.3 
(skipped a couple of versions due to github hassles that turned out to be due to a corporate firewall but which left me rushing to finish) 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30862 
 
 
 
  "ugly" formatting of view names using "Custom Views TabBar"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alistair Todd 
 
 
 

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] [custom-view-tabs-plugin] (JENKINS-30862) "ugly" formatting of view names using "Custom Views TabBar"

2016-02-20 Thread ringra...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alistair Todd resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Accepted pull request from maosmurf, with thanks. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-30862 
 
 
 
  "ugly" formatting of view names using "Custom Views TabBar"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alistair Todd 
 
 
 

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] [custom-view-tabs-plugin] (JENKINS-30862) "ugly" formatting of view names using "Custom Views TabBar"

2016-02-20 Thread ringra...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alistair Todd commented on  JENKINS-30862 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "ugly" formatting of view names using "Custom Views TabBar"  
 
 
 
 
 
 
 
 
 
 
Thanks for the contribution and sorry it took so long for me to see this and do something with 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] [custom-view-tabs-plugin] (JENKINS-30862) "ugly" formatting of view names using "Custom Views TabBar"

2016-02-20 Thread ringra...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alistair Todd started work on  JENKINS-30862 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Alistair Todd 
 
 
 

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] [publish-over-ssh-plugin] (JENKINS-33056) Please add clean remote option

2016-02-20 Thread goikhb...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lior Goikhburg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33056 
 
 
 
  Please add clean remote option  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 bap 
 
 
 

Components:
 

 publish-over-ssh-plugin 
 
 
 

Created:
 

 20/Feb/16 1:19 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Lior Goikhburg 
 
 
 
 
 
 
 
 
 
 
Like in the Publish over FTP plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [multi-branch-project-plugin] (JENKINS-32255) Multi-branch multi-configuration projects

2016-02-20 Thread alstein...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Steinberg commented on  JENKINS-32255 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Multi-branch multi-configuration projects  
 
 
 
 
 
 
 
 
 
 
I do really need that feature. I can't wait when it is released.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [p4-plugin] (JENKINS-24003) Unable to wipe out workspace

2016-02-20 Thread dant...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 dan tran commented on  JENKINS-24003 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to wipe out workspace  
 
 
 
 
 
 
 
 
 
 
Not sure what happen, I upgraded to 1.3.7, the problem still there, revert back to 1.3.7 snapshot does not help either. I am now back at 1.3.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jira-ext-plugin] (JENKINS-33055) Misleading instructions

2016-02-20 Thread nfo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nikk Folts created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33055 
 
 
 
  Misleading instructions  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Dan Alvizu 
 
 
 

Components:
 

 jira-ext-plugin 
 
 
 

Created:
 

 20/Feb/16 8:31 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Nikk Folts 
 
 
 
 
 
 
 
 
 
 
I tried multiple times to get a custom field to update while following the helper text: 
 
"The name of the field. For custom fields this will have something like customField_12349"
 
However, it turns out (or it would seem), that you have to have the field name all lowercase... (that is the only way I got it to work)... If I capitalized the "F" in Field, I'd get an error: 
 
Filed 'customField_X' does not exist or read-only
 
As soon as I lowercased it all, it worked. The instructions should either specify this, OR, if it is true that the Jira REST API is always lowercase, then the value passed by the user should be lowercased before sending it to Jira. 
 
 
 
 
 
 
 
 
 
 
 
 

[JIRA] [jira-ext-plugin] (JENKINS-33055) Misleading helper text on "Update a Field"

2016-02-20 Thread nfo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nikk Folts updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33055 
 
 
 
  Misleading helper text on "Update a Field"   
 
 
 
 
 
 
 
 
 

Change By:
 
 Nikk Folts 
 
 
 

Summary:
 
 Misleading  instructions  helper text on "Update a Field"   
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jira-ext-plugin] (JENKINS-33054) "Update a Field" does not work with environment variables

2016-02-20 Thread nfo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nikk Folts created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33054 
 
 
 
  "Update a Field" does not work with environment variables  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Dan Alvizu 
 
 
 

Components:
 

 jira-ext-plugin 
 
 
 

Created:
 

 20/Feb/16 8:27 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Nikk Folts 
 
 
 
 
 
 
 
 
 
 
I attempted to update a wiki-markup enabled field in Jira with: 

 

Last Jenkins Build - [$JOB_NAME $BUILD_DISPLAY_NAME|$BUILD_URL]
 

 
But, it placed its value plain text, rather than turning the variables into their actual values... It seems to work just fine for comments, just not "Update a Field" 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 

[JIRA] [jira-ext-plugin] (JENKINS-33054) "Update a Field" does not work with environment variables

2016-02-20 Thread nfo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nikk Folts updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33054 
 
 
 
  "Update a Field" does not work with environment variables  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nikk Folts 
 
 
 

Priority:
 
 Minor Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [multi-branch-project-plugin] (JENKINS-32255) Multi-branch multi-configuration projects

2016-02-20 Thread apet...@taigasystem.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrey Petrov edited a comment on  JENKINS-32255 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Multi-branch multi-configuration projects  
 
 
 
 
 
 
 
 
 
 This feature is very important for us,  whern  when  you must build N branches with  commont  common  settings and each branch build for many OS.  As mentioned above, the best solution would be to  integration with https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Project+Plugin  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [core] (JENKINS-32991) Jenkins 1.596.3 with java 1.6.24 and web logic 10.3.5, version compatibility

2016-02-20 Thread sairam.cs...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sairam ballekari commented on  JENKINS-32991 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins 1.596.3 with java 1.6.24 and web logic 10.3.5, version compatibility  
 
 
 
 
 
 
 
 
 
 
Yeah it is from Jenkins repository only, and it is belongs to Jenkins core..I am struck at this step 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [multi-branch-project-plugin] (JENKINS-32255) Multi-branch multi-configuration projects

2016-02-20 Thread apet...@taigasystem.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrey Petrov commented on  JENKINS-32255 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Multi-branch multi-configuration projects  
 
 
 
 
 
 
 
 
 
 
This feature is very important for us, whern you must build N branches with commont settings and each branch build for many OS. As mentioned above, the best solution would be to integration with https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Project+Plugin  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [core] (JENKINS-32991) Jenkins 1.596.3 with java 1.6.24 and web logic 10.3.5, version compatibility

2016-02-20 Thread r...@orange.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raphael CHAUMIER updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32991 
 
 
 
  Jenkins 1.596.3 with java 1.6.24 and web logic 10.3.5, version compatibility  
 
 
 
 
 
 
 
 
 

Change By:
 
 Raphael CHAUMIER 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 weblogic-deployer-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.