[JIRA] (JENKINS-14465) Buttons and lists don't work as expected

2012-07-20 Thread pxan...@gmail.com (JIRA)














































Oleksandr Popov
 updated  JENKINS-14465


Buttons and lists don't work as expected
















Hi,

@Adrian: from my side everything you posted (i.e. "For single conditional step, the trigger other jobs step or send files or commands over SSH step is not working fine") is working. Im able to choose servers and writing area appears (see screenshot)

@domi: please see same screenshot thereis _javascript_ exeption when Im adding multiple conditional step. Hope that helps resolve issue





Change By:


Oleksandr Popov
(20/Jul/12 8:34 AM)




Attachment:


_javascript_-error.jpg



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-14465) Buttons and lists don't work as expected

2012-07-19 Thread pxan...@gmail.com (JIRA)














































Oleksandr Popov
 commented on  JENKINS-14465


Buttons and lists don't work as expected















One additional update:
When adding single conditional step it is working fine. For some reason in multiple steps (Ive attached screen shot of it)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-14465) Buttons and lists don't work as expected

2012-07-19 Thread pxan...@gmail.com (JIRA)














































Oleksandr Popov
 updated  JENKINS-14465


Buttons and lists don't work as expected
















Change By:


Oleksandr Popov
(19/Jul/12 1:25 PM)




Attachment:


buttons.jpg



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-14465) Buttons and lists don't work as expected

2012-07-19 Thread pxan...@gmail.com (JIRA)












































  
Oleksandr Popov
 edited a comment on  JENKINS-14465


Buttons and lists don't work as expected
















Also I see that similar things happens with  editing Views: Im unable to delete column by pressing "Delete" button.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-14465) Buttons and lists don't work as expected

2012-07-19 Thread pxan...@gmail.com (JIRA)














































Oleksandr Popov
 commented on  JENKINS-14465


Buttons and lists don't work as expected















Also I see that similar things happans with  editing Views: Im unable to delete column by pressing "Delete" button.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-11817) Allow to add prefix to commit's comment

2012-07-19 Thread pxan...@gmail.com (JIRA)















































Oleksandr Popov
 closed  JENKINS-11817 as Fixed


Allow to add prefix to commit's comment
















Thanks





Change By:


Oleksandr Popov
(19/Jul/12 1:13 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-14465) Buttons and lists don't work as expected

2012-07-19 Thread pxan...@gmail.com (JIRA)














































Oleksandr Popov
 commented on  JENKINS-14465


Buttons and lists don't work as expected















Have the similar issue. Checked in Firefox and IE. Same result. 
Please advice about progress.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-12250) Critical block can not be added into conditional step

2012-03-29 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160949#comment-160949
 ] 

Oleksandr Popov commented on JENKINS-12250:
---

Hello?

> Critical block can not be added into conditional step
> -
>
> Key: JENKINS-12250
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12250
> Project: Jenkins
>  Issue Type: Bug
>  Components: conditional-buildstep, exclusion
> Environment: Jenkins 1.445
> Jenkins Exclusion Plug-in 0.6
> conditional-buildstep 0.2
>Reporter: Oleksandr Popov
>Assignee: Anthony Roux
>Priority: Critical
> Attachments: critical-block.PNG
>
>
> I'm not able to add critical block into conditional step. See screen-shot for 
> details

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-13155) Parameters are not working in EnvInject plugin 1.38

2012-03-21 Thread pxan...@gmail.com (JIRA)

 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Popov closed JENKINS-13155.
-


> Parameters are not working in EnvInject plugin 1.38
> ---
>
> Key: JENKINS-13155
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13155
> Project: Jenkins
>  Issue Type: Bug
>  Components: envinject
> Environment: EnvInject  1.38
> Jenkins 1.455 / 1.456
>Reporter: Oleksandr Popov
>Assignee: gbois
>Priority: Critical
> Attachments: env-inject-issue.png
>
>
> When you specify variables in "Inject environment variables to the build 
> process" / "Properties File Path" section (as it is presented in attached 
> screenshot) it does not resolves those variables:
> 13:45:46  [EnvInject] - Executing scripts and injecting environment variables 
> after the SCM step.
> 13:45:46  [EnvInject] - [ERROR] - The given properties file path 
> '${WORKSPACE}/${Branch}/***/Install/properties/dbschema.property' doesn't 
> exist.
> 13:45:46  [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on 
> injecting env vars as a build wrap: hudson.util.IOException2: remote file 
> operation failed: /*/*/jenkins/workspace/[Job-name] at 
> hudson.remoting.Channel@147ed19:*
> Had to revert to 1.36 version

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-13155) Parameters are not working in EnvInject plugin 1.38

2012-03-21 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160540#comment-160540
 ] 

Oleksandr Popov commented on JENKINS-13155:
---

Thanks it is working now... v. 1.39

> Parameters are not working in EnvInject plugin 1.38
> ---
>
> Key: JENKINS-13155
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13155
> Project: Jenkins
>  Issue Type: Bug
>  Components: envinject
> Environment: EnvInject  1.38
> Jenkins 1.455 / 1.456
>Reporter: Oleksandr Popov
>Assignee: gbois
>Priority: Critical
> Attachments: env-inject-issue.png
>
>
> When you specify variables in "Inject environment variables to the build 
> process" / "Properties File Path" section (as it is presented in attached 
> screenshot) it does not resolves those variables:
> 13:45:46  [EnvInject] - Executing scripts and injecting environment variables 
> after the SCM step.
> 13:45:46  [EnvInject] - [ERROR] - The given properties file path 
> '${WORKSPACE}/${Branch}/***/Install/properties/dbschema.property' doesn't 
> exist.
> 13:45:46  [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on 
> injecting env vars as a build wrap: hudson.util.IOException2: remote file 
> operation failed: /*/*/jenkins/workspace/[Job-name] at 
> hudson.remoting.Channel@147ed19:*
> Had to revert to 1.36 version

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-13155) Parameters are not working in EnvInject plugin 1.38

2012-03-20 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160481#comment-160481
 ] 

Oleksandr Popov commented on JENKINS-13155:
---

Ive both 1.455 and 1.456 - with old 1.36 plugin version it working fine, 
however with 1.38 it is not. Could you please fix this.

Thanks in advance!

> Parameters are not working in EnvInject plugin 1.38
> ---
>
> Key: JENKINS-13155
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13155
> Project: Jenkins
>  Issue Type: Bug
>  Components: envinject
> Environment: EnvInject  1.38
> Jenkins 1.455 / 1.456
>Reporter: Oleksandr Popov
>Assignee: gbois
>Priority: Critical
> Attachments: env-inject-issue.png
>
>
> When you specify variables in "Inject environment variables to the build 
> process" / "Properties File Path" section (as it is presented in attached 
> screenshot) it does not resolves those variables:
> 13:45:46  [EnvInject] - Executing scripts and injecting environment variables 
> after the SCM step.
> 13:45:46  [EnvInject] - [ERROR] - The given properties file path 
> '${WORKSPACE}/${Branch}/***/Install/properties/dbschema.property' doesn't 
> exist.
> 13:45:46  [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on 
> injecting env vars as a build wrap: hudson.util.IOException2: remote file 
> operation failed: /*/*/jenkins/workspace/[Job-name] at 
> hudson.remoting.Channel@147ed19:*
> Had to revert to 1.36 version

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-13155) Parameters are not working in EnvInject plugin 1.38

2012-03-20 Thread pxan...@gmail.com (JIRA)
Oleksandr Popov created JENKINS-13155:
-

 Summary: Parameters are not working in EnvInject plugin 1.38
 Key: JENKINS-13155
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13155
 Project: Jenkins
  Issue Type: Bug
  Components: envinject
 Environment: EnvInject  1.38
Jenkins 1.455 / 1.456
Reporter: Oleksandr Popov
Assignee: gbois
Priority: Critical
 Attachments: env-inject-issue.png

When you specify variables in "Inject environment variables to the build 
process" / "Properties File Path" section (as it is presented in attached 
screenshot) it does not resolves those variables:

13:45:46  [EnvInject] - Executing scripts and injecting environment variables 
after the SCM step.
13:45:46  [EnvInject] - [ERROR] - The given properties file path 
'${WORKSPACE}/${Branch}/***/Install/properties/dbschema.property' doesn't exist.
13:45:46  [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on 
injecting env vars as a build wrap: hudson.util.IOException2: remote file 
operation failed: /*/*/jenkins/workspace/[Job-name] at 
hudson.remoting.Channel@147ed19:*

Had to revert to 1.36 version


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12667) No possibility to specify "Workspace Root Directory" for Slave node

2012-03-15 Thread pxan...@gmail.com (JIRA)

 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Popov reassigned JENKINS-12667:
-

Assignee: Frederik Fromm  (was: Oleksandr Popov)

> No possibility to specify "Workspace Root Directory" for Slave node
> ---
>
> Key: JENKINS-12667
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12667
> Project: Jenkins
>  Issue Type: Bug
>  Components: slave-setup
>Affects Versions: current
> Environment: Jenkins 1.452
>Reporter: Oleksandr Popov
>Assignee: Frederik Fromm
>Priority: Critical
>
> There is no possibility to specify "Workspace Root Directory" for Slave node 
> as it is for Master node.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12250) Critical block can not be added into conditional step

2012-03-14 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160239#comment-160239
 ] 

Oleksandr Popov commented on JENKINS-12250:
---

no it is not working...
Is it normal - I've uploaded .hpi file via Jenkins interface and version of 
Exclusion plugin still 0.6?

> Critical block can not be added into conditional step
> -
>
> Key: JENKINS-12250
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12250
> Project: Jenkins
>  Issue Type: Bug
>  Components: conditional-buildstep, exclusion
> Environment: Jenkins 1.445
> Jenkins Exclusion Plug-in 0.6
> conditional-buildstep 0.2
>Reporter: Oleksandr Popov
>Assignee: Anthony Roux
>Priority: Critical
> Attachments: critical-block.PNG
>
>
> I'm not able to add critical block into conditional step. See screen-shot for 
> details

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12250) Critical block can not be added into conditional step

2012-03-13 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160186#comment-160186
 ] 

Oleksandr Popov commented on JENKINS-12250:
---

Thanks... will check and let you know

> Critical block can not be added into conditional step
> -
>
> Key: JENKINS-12250
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12250
> Project: Jenkins
>  Issue Type: Bug
>  Components: conditional-buildstep, exclusion
> Environment: Jenkins 1.445
> Jenkins Exclusion Plug-in 0.6
> conditional-buildstep 0.2
>Reporter: Oleksandr Popov
>Assignee: Anthony Roux
>Priority: Critical
> Attachments: critical-block.PNG
>
>
> I'm not able to add critical block into conditional step. See screen-shot for 
> details

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12667) No possibility to specify "Workspace Root Directory" for Slave node

2012-03-13 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160184#comment-160184
 ] 

Oleksandr Popov commented on JENKINS-12667:
---

I mean not Jenkins root folder (cause "Remote FS root" parameter is jenkins 
itself root) but workspace directory for each job.
For master server it is possible to specify single directory for all jobs where 
SCM do checkout for all branches. You could find this variable if you go:
Manage Jenkins -> Configure System -> Press "Advanced" buttom in the top of 
configuration screen -> you will see "Workspace Root Directory" property.

Thanks for your assistance in advance!

> No possibility to specify "Workspace Root Directory" for Slave node
> ---
>
> Key: JENKINS-12667
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12667
> Project: Jenkins
>  Issue Type: Bug
>  Components: slave-setup
>Affects Versions: current
> Environment: Jenkins 1.452
>Reporter: Oleksandr Popov
>Assignee: Oleksandr Popov
>Priority: Critical
>
> There is no possibility to specify "Workspace Root Directory" for Slave node 
> as it is for Master node.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12667) No possibility to specify "Workspace Root Directory" for Slave node

2012-03-05 Thread pxan...@gmail.com (JIRA)

 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Popov updated JENKINS-12667:
--

Environment: Jenkins 1.452  (was: Jenkins 1.450)
   Priority: Critical  (was: Major)

> No possibility to specify "Workspace Root Directory" for Slave node
> ---
>
> Key: JENKINS-12667
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12667
> Project: Jenkins
>  Issue Type: Bug
>  Components: slave-setup
>Affects Versions: current
> Environment: Jenkins 1.452
>Reporter: Oleksandr Popov
>Assignee: Kohsuke Kawaguchi
>Priority: Critical
>
> There is no possibility to specify "Workspace Root Directory" for Slave node 
> as it is for Master node.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12113) Maven - java.io.IOException: error=2, No such file or directory if in SVN configuration parameters used in Local module directory section

2012-03-02 Thread pxan...@gmail.com (JIRA)

 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleksandr Popov closed JENKINS-12113.
-


Thanks for you help!

> Maven - java.io.IOException: error=2, No such file or directory if in SVN 
> configuration parameters used in Local module directory section
> -
>
> Key: JENKINS-12113
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12113
> Project: Jenkins
>  Issue Type: Bug
>  Components: core, maven, maven2, parameters, subversion
> Environment: Jenkins 1.448
> Subversion Plugin 1.37
> Maven Integration Plugin 1.448
> Ant 1.1
>Reporter: Oleksandr Popov
>Assignee: kutzi
> Attachments: subversion.hpi, svn_maven_issue_01.PNG, 
> svn_maven_issue_02.PNG
>
>
> Maven is unable to work if in Subversion configuration parameters are used in 
> Local module directory section.
> As you can see in svn_maven_issue_01.PNG Ive specified predefined variable in 
> Local module directory section. And when I run it - Maven failed 
> (svn_maven_issue_02.PNG) with java.io.IOException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12250) Critical block can not be added into conditional step

2012-03-02 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159741#comment-159741
 ] 

Oleksandr Popov commented on JENKINS-12250:
---

Hello? Any update on this issue?

> Critical block can not be added into conditional step
> -
>
> Key: JENKINS-12250
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12250
> Project: Jenkins
>  Issue Type: Bug
>  Components: conditional-buildstep, exclusion
> Environment: Jenkins 1.445
> Jenkins Exclusion Plug-in 0.6
> conditional-buildstep 0.2
>Reporter: Oleksandr Popov
>Assignee: Anthony Roux
>Priority: Critical
> Attachments: critical-block.PNG
>
>
> I'm not able to add critical block into conditional step. See screen-shot for 
> details

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12667) No possibility to specify "Workspace Root Directory" for Slave node

2012-03-02 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159740#comment-159740
 ] 

Oleksandr Popov commented on JENKINS-12667:
---

Any update?

> No possibility to specify "Workspace Root Directory" for Slave node
> ---
>
> Key: JENKINS-12667
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12667
> Project: Jenkins
>  Issue Type: Bug
>  Components: slave-setup
>Affects Versions: current
> Environment: Jenkins 1.450
>Reporter: Oleksandr Popov
>Assignee: Kohsuke Kawaguchi
>
> There is no possibility to specify "Workspace Root Directory" for Slave node 
> as it is for Master node.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12113) Maven - java.io.IOException: error=2, No such file or directory if in SVN configuration parameters used in Local module directory section

2012-02-09 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158804#comment-158804
 ] 

Oleksandr Popov commented on JENKINS-12113:
---

Great news! Hope so ;)

> Maven - java.io.IOException: error=2, No such file or directory if in SVN 
> configuration parameters used in Local module directory section
> -
>
> Key: JENKINS-12113
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12113
> Project: Jenkins
>  Issue Type: Bug
>  Components: core, maven, maven2, parameters, subversion
> Environment: Jenkins 1.448
> Subversion Plugin 1.37
> Maven Integration Plugin 1.448
> Ant 1.1
>Reporter: Oleksandr Popov
>Assignee: kutzi
> Attachments: subversion.hpi, svn_maven_issue_01.PNG, 
> svn_maven_issue_02.PNG
>
>
> Maven is unable to work if in Subversion configuration parameters are used in 
> Local module directory section.
> As you can see in svn_maven_issue_01.PNG Ive specified predefined variable in 
> Local module directory section. And when I run it - Maven failed 
> (svn_maven_issue_02.PNG) with java.io.IOException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12113) Maven - java.io.IOException: error=2, No such file or directory if in SVN configuration parameters used in Local module directory section

2012-02-08 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158726#comment-158726
 ] 

Oleksandr Popov edited comment on JENKINS-12113 at 2/8/12 3:35 PM:
---

Yes! Looks like that fixes the issue...

  was (Author: pxantom):
Yes! Looks like that fixes the issue... I think the similar change needed 
for Ant.
  
> Maven - java.io.IOException: error=2, No such file or directory if in SVN 
> configuration parameters used in Local module directory section
> -
>
> Key: JENKINS-12113
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12113
> Project: Jenkins
>  Issue Type: Bug
>  Components: core, maven, maven2, parameters, subversion
> Environment: Jenkins 1.448
> Subversion Plugin 1.37
> Maven Integration Plugin 1.448
> Ant 1.1
>Reporter: Oleksandr Popov
>Assignee: kutzi
> Attachments: subversion.hpi, svn_maven_issue_01.PNG, 
> svn_maven_issue_02.PNG
>
>
> Maven is unable to work if in Subversion configuration parameters are used in 
> Local module directory section.
> As you can see in svn_maven_issue_01.PNG Ive specified predefined variable in 
> Local module directory section. And when I run it - Maven failed 
> (svn_maven_issue_02.PNG) with java.io.IOException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12113) Maven - java.io.IOException: error=2, No such file or directory if in SVN configuration parameters used in Local module directory section

2012-02-07 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158747#comment-158747
 ] 

Oleksandr Popov commented on JENKINS-12113:
---

One little question: when it will be released?

> Maven - java.io.IOException: error=2, No such file or directory if in SVN 
> configuration parameters used in Local module directory section
> -
>
> Key: JENKINS-12113
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12113
> Project: Jenkins
>  Issue Type: Bug
>  Components: core, maven, maven2, parameters, subversion
> Environment: Jenkins 1.448
> Subversion Plugin 1.37
> Maven Integration Plugin 1.448
> Ant 1.1
>Reporter: Oleksandr Popov
>Assignee: kutzi
> Attachments: subversion.hpi, svn_maven_issue_01.PNG, 
> svn_maven_issue_02.PNG
>
>
> Maven is unable to work if in Subversion configuration parameters are used in 
> Local module directory section.
> As you can see in svn_maven_issue_01.PNG Ive specified predefined variable in 
> Local module directory section. And when I run it - Maven failed 
> (svn_maven_issue_02.PNG) with java.io.IOException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12250) Critical block can not be added into conditional step

2012-02-07 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158728#comment-158728
 ] 

Oleksandr Popov commented on JENKINS-12250:
---

Any update?

> Critical block can not be added into conditional step
> -
>
> Key: JENKINS-12250
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12250
> Project: Jenkins
>  Issue Type: Bug
>  Components: conditional-buildstep, exclusion
> Environment: Jenkins 1.445
> Jenkins Exclusion Plug-in 0.6
> conditional-buildstep 0.2
>Reporter: Oleksandr Popov
>Assignee: Anthony Roux
>Priority: Critical
> Attachments: critical-block.PNG
>
>
> I'm not able to add critical block into conditional step. See screen-shot for 
> details

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12667) No possibility to specify "Workspace Root Directory" for Slave node

2012-02-07 Thread pxan...@gmail.com (JIRA)
Oleksandr Popov created JENKINS-12667:
-

 Summary: No possibility to specify "Workspace Root Directory" for 
Slave node
 Key: JENKINS-12667
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12667
 Project: Jenkins
  Issue Type: Bug
  Components: slave-setup
Affects Versions: current
 Environment: Jenkins 1.450
Reporter: Oleksandr Popov
Assignee: Kohsuke Kawaguchi


There is no possibility to specify "Workspace Root Directory" for Slave node as 
it is for Master node.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12113) Maven - java.io.IOException: error=2, No such file or directory if in SVN configuration parameters used in Local module directory section

2012-02-07 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158726#comment-158726
 ] 

Oleksandr Popov commented on JENKINS-12113:
---

Yes! Looks like that fixes the issue... I think the similar change needed for 
Ant.

> Maven - java.io.IOException: error=2, No such file or directory if in SVN 
> configuration parameters used in Local module directory section
> -
>
> Key: JENKINS-12113
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12113
> Project: Jenkins
>  Issue Type: Bug
>  Components: core, maven, maven2, parameters, subversion
> Environment: Jenkins 1.448
> Subversion Plugin 1.37
> Maven Integration Plugin 1.448
> Ant 1.1
>Reporter: Oleksandr Popov
>Assignee: kutzi
> Attachments: subversion.hpi, svn_maven_issue_01.PNG, 
> svn_maven_issue_02.PNG
>
>
> Maven is unable to work if in Subversion configuration parameters are used in 
> Local module directory section.
> As you can see in svn_maven_issue_01.PNG Ive specified predefined variable in 
> Local module directory section. And when I run it - Maven failed 
> (svn_maven_issue_02.PNG) with java.io.IOException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-12113) Maven - java.io.IOException: error=2, No such file or directory if in SVN configuration parameters used in Local module directory section

2012-02-06 Thread pxan...@gmail.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158648#comment-158648
 ] 

Oleksandr Popov commented on JENKINS-12113:
---

@kutzi - Any updates or estimates?

> Maven - java.io.IOException: error=2, No such file or directory if in SVN 
> configuration parameters used in Local module directory section
> -
>
> Key: JENKINS-12113
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12113
> Project: Jenkins
>  Issue Type: Bug
>  Components: core, maven, parameters, subversion
> Environment: Jenkins 1.448
> Subversion Plugin 1.37
> Maven Integration Plugin 1.448
> Ant 1.1
>Reporter: Oleksandr Popov
>Assignee: kutzi
>Priority: Blocker
> Attachments: svn_maven_issue_01.PNG, svn_maven_issue_02.PNG
>
>
> Maven is unable to work if in Subversion configuration parameters are used in 
> Local module directory section.
> As you can see in svn_maven_issue_01.PNG Ive specified predefined variable in 
> Local module directory section. And when I run it - Maven failed 
> (svn_maven_issue_02.PNG) with java.io.IOException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira