[JIRA] (JENKINS-42445) Ansible plugin: Support hostKeyChecking = true in pipeline dsl

2017-03-02 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot commented on  JENKINS-42445  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ansible plugin: Support hostKeyChecking = true in pipeline dsl   
 

  
 
 
 
 

 
 Thank you for the report. I am going to verify that quickly.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40780) Don't work after 0.6.1

2017-01-03 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in 0.6.2  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40780  
 
 
  Don't work after 0.6.1   
 

  
 
 
 
 

 
Change By: 
 Jean-Christophe Sirot  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40780) Don't work after 0.6.1

2017-01-03 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot commented on  JENKINS-40780  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Don't work after 0.6.1   
 

  
 
 
 
 

 
 Thank you for the bug report. I'm going to check it ASAP  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-34627) It is impossible not to pass an inventory file

2016-12-31 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34627  
 
 
  It is impossible not to pass an inventory file   
 

  
 
 
 
 

 
Change By: 
 Jean-Christophe Sirot  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39611) ansible / ansible-playbook -i option is not supported via a parameter in Jenkins job inside Invoke Ansible build step

2016-12-31 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39611  
 
 
  ansible / ansible-playbook -i option is not supported via a parameter in Jenkins job inside Invoke Ansible build step   
 

  
 
 
 
 

 
Change By: 
 Jean-Christophe Sirot  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38207) Can't use parameters from Mask Passwords Plugin in ansible

2016-12-31 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38207  
 
 
  Can't use parameters from Mask Passwords Plugin in ansible
 

  
 
 
 
 

 
Change By: 
 Jean-Christophe Sirot  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38207) Can't use parameters from Mask Passwords Plugin in ansible

2016-12-31 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot edited a comment on  JENKINS-38207  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't use parameters from Mask Passwords Plugin in ansible
 

  
 
 
 
 

 
 Jenkins and jenkins plugins variables are injected as environment variables inside the ansible process. To access these variables from the playbook you need to use this kind of _expression_{code :yaml }- name: Print debug  debug: msg="KEY - {{ lookup('env','AWS_KEY') }} SECRET - {{ lookup('env','AWS_SECRET') }}"{code}I've updated the documentation to better explain how to use injected variables.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38207) Can't use parameters from Mask Passwords Plugin in ansible

2016-12-31 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot commented on  JENKINS-38207  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't use parameters from Mask Passwords Plugin in ansible
 

  
 
 
 
 

 
 Jenkins and jenkins plugins variables are injected as environment variables inside the ansible process. To access these variables from the playbook you need to use this kind of _expression_ 

 

Unable to find source-code formatter for language: yaml. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml


- name: Print debug
  debug: msg="KEY - {{ lookup('env','AWS_KEY') }} SECRET - {{ lookup('env','AWS_SECRET') }}"
 

 I've updated the documentation to better explain how to use injected variables.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-29284) Build variables are not available during the ansible-playbook execution

2016-12-31 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-29284  
 
 
  Build variables are not available during the ansible-playbook execution   
 

  
 
 
 
 

 
Change By: 
 Jean-Christophe Sirot  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39438) support empty forks (Number of parallel processes) parameter

2016-12-26 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39438  
 
 
  support empty forks (Number of parallel processes) parameter   
 

  
 
 
 
 

 
Change By: 
 Jean-Christophe Sirot  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39438) support empty forks (Number of parallel processes) parameter

2016-12-26 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot commented on  JENKINS-39438  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: support empty forks (Number of parallel processes) parameter   
 

  
 
 
 
 

 
 Fixed in 0.6  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-29284) Build variables are not available during the ansible-playbook execution

2016-12-26 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot commented on  JENKINS-29284  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build variables are not available during the ansible-playbook execution   
 

  
 
 
 
 

 
 Sergey Zhekpisov Can you give me more details on your the failing job configuration  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-29284) Build variables are not available during the ansible-playbook execution

2016-12-26 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot commented on  JENKINS-29284  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build variables are not available during the ansible-playbook execution   
 

  
 
 
 
 

 
 Piotr Minkowski Variables are injected in the process environment. It means you have to use this syntax to use in your template settings.j2: 

 
- build_id: {{ lookup('env','BUILD_ID') }}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39611) ansible / ansible-playbook -i option is not supported via a parameter in Jenkins job inside Invoke Ansible build step

2016-11-11 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot commented on  JENKINS-39611  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ansible / ansible-playbook -i option is not supported via a parameter in Jenkins job inside Invoke Ansible build step   
 

  
 
 
 
 

 
 I reviewed this issue and it does not seems to be a bug but it shows that the field names and documentation have to be improved. The "file path" field when the file radio button is selected accepts a comma separated list of hosts. Note that the host list must not contain spaces (before or after the comma) since the ansible-playbook command seems to consider everything between the commas to be a hostname. Also the "inline content" is used to create an inventory file on the fly and avoid the creation of such a file from a script for instance.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39611) ansible / ansible-playbook -i option is not supported via a parameter in Jenkins job inside Invoke Ansible build step

2016-11-08 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot commented on  JENKINS-39611  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ansible / ansible-playbook -i option is not supported via a parameter in Jenkins job inside Invoke Ansible build step   
 

  
 
 
 
 

 
 Thank you for filling out this ticket. I'm going to review it asap.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-33849) "Authentication failure" when use the "delegate_to" in the task

2016-10-26 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot commented on  JENKINS-33849  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Authentication failure" when use the "delegate_to" in the task   
 

  
 
 
 
 

 
 It seems to be an ansible bug fixed in 2.0.1.0-1 (https://github.com/ansible/ansible/commit/1f5584aa5b9d1142e67fed209bbeea1ca99fc307).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38289) ansiblePlaybook pipeline step does not respect environment

2016-10-26 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in 0.6  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38289  
 
 
  ansiblePlaybook pipeline step does not respect environment   
 

  
 
 
 
 

 
Change By: 
 Jean-Christophe Sirot  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38289) ansiblePlaybook pipeline step does not respect environment

2016-10-10 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot commented on  JENKINS-38289  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ansiblePlaybook pipeline step does not respect environment   
 

  
 
 
 
 

 
 Thank you Thomas Kalmár for your PR. I will review it ASAP.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35372) Cannot delete extra variable once added

2016-07-14 Thread jcsi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean-Christophe Sirot resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed with Jenkins 2.8  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-35372  
 
 
  Cannot delete extra variable once added   
 

  
 
 
 
 

 
Change By: 
 Jean-Christophe Sirot  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] [ansible-plugin] (JENKINS-35372) Cannot delete extra variable once added

2016-06-06 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot commented on  JENKINS-35372 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot delete extra variable once added  
 
 
 
 
 
 
 
 
 
 
Indeed, I just verified it too. After the tests I made today it seems to be broken since 2.0. I will resolve the ticket with a fixed status. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ansible-plugin] (JENKINS-35372) Cannot delete extra variable once added

2016-06-06 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot commented on  JENKINS-35372 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot delete extra variable once added  
 
 
 
 
 
 
 
 
 
 
Thank you for opening this ticket. I also found that bug yesterday. I just verify that It used to work in Jenkins 1.x branch but not in 2.x. I am trying to determine when it stopped working exactly. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ansible-plugin] (JENKINS-34627) It is impossible not to pass an inventory file

2016-05-06 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot commented on  JENKINS-34627 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: It is impossible not to pass an inventory file  
 
 
 
 
 
 
 
 
 
 
Fixed in version 0.5 by leaving empty the inventory field. However an option "do not pass an inventory file" would be better. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ansible-plugin] (JENKINS-34627) It is impossible not to pass an inventory file

2016-05-05 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34627 
 
 
 
  It is impossible not to pass an inventory file  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Jean-Christophe Sirot 
 
 
 

Components:
 

 ansible-plugin 
 
 
 

Created:
 

 2016/May/05 6:37 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Jean-Christophe Sirot 
 
 
 
 
 
 
 
 
 
 
Once selected, it is not possible to unselect the inventory file. But this is not a mandatory parameter to pass to ansible-playbook. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message 

[JIRA] [ansible-plugin] (JENKINS-29284) Build variables are not available during the ansible-playbook execution

2016-05-05 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
fixed in version 0.5 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29284 
 
 
 
  Build variables are not available during the ansible-playbook execution  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jean-Christophe Sirot 
 
 
 

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] [ansible-plugin] (JENKINS-29284) Build variables are not available during the ansible-playbook execution

2016-05-05 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29284 
 
 
 
  Build variables are not available during the ansible-playbook execution  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jean-Christophe Sirot 
 
 
 

Summary:
 
 Build variables are not available during the ansible- palybook playbook  execution 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ansible-plugin] (JENKINS-33787) openstack.py dynamic inventory

2016-05-05 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot commented on  JENKINS-33787 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: openstack.py dynamic inventory  
 
 
 
 
 
 
 
 
 
 
Govindaraj Venkatesan Is the dynamic inventory file openstack.py executable for the jenkins user? If the file does not have the executable flag, ansible tries to read it as a regular inventory. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ansible-plugin] (JENKINS-33787) openstack.py dynamic inventory

2016-05-05 Thread jcsi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Christophe Sirot commented on  JENKINS-33787 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: openstack.py dynamic inventory  
 
 
 
 
 
 
 
 
 
 
Sorry for the late reply. I'm going to investigate your issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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