[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin

15 views
Skip to first unread message

gojiradam@gmail.com (JIRA)

unread,
Nov 28, 2018, 5:29:03 PM11/28/18
to jenkinsc...@googlegroups.com
Adam Delarosa created an issue
 
Jenkins / Task JENKINS-54929
Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Issue Type: Task Task
Assignee: Jean-Christophe Sirot
Attachments: waX7XcM.png
Components: ansible-plugin, pipeline
Created: 2018-11-28 22:28
Environment: Latest (11.29.18) Jenkins Version 2.153 (2018-11-25)
Latest (11.29.18) Jenkins Ansible Pipeline plugin Version 1.0 (26 March 2018)
Labels: jenkins pipeline ansible playbook ansible-plugin
Priority: Major Major
Reporter: Adam Delarosa

When using the Ansible Plugin with jenkins Pipeline
I can't see the entire log (I could see the entire log if I'll SSH to the server and run the command from the command line).
This issue started about a month ago..

Here is a screenshot of how the output look like now:
https://imgur.com/waX7XcM

Ansible Plugin:
https://jenkins.io/doc/pipeline/steps/ansible/

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

gojiradam@gmail.com (JIRA)

unread,
Nov 28, 2018, 5:52:02 PM11/28/18
to jenkinsc...@googlegroups.com
Adam Delarosa updated an issue
Change By: Adam Delarosa
When using the Ansible Plugin with jenkins Pipeline
I can't see the entire log (I could see the entire log if I'll SSH to the server and run the command from the command line).
This issue started about a month ago..

Here is a screenshot of how the output look like now:
[https://imgur.com/waX7XcM]

Ansible Plugin:
[ https://jenkins.io/doc/pipeline/steps/ansible/ ]

This is the Pipeline code that uses the Ansible Pipeline Plugin:


{code:java}
        stage('running something') {
            steps {
                script {
                    dir('my/path/here') {
                     ansiblePlaybook([
                     inventory   : 'hosts',
                     playbook    : 'main.yml',
                     installation: 'ansible',
                     sudoUser    : null,
                     colorized   : true,
                     extraVars   : [
                     blah   : "${params.blah}",
                     some_var       : "${params.some_var}"
                     ]
                     ])
                    }
                }
            }
        }
{code}

gojiradam@gmail.com (JIRA)

unread,
Nov 28, 2018, 5:55:01 PM11/28/18
to jenkinsc...@googlegroups.com
Adam Delarosa updated an issue
When using the Ansible Plugin with jenkins Pipeline
I can't see the entire log (I could see in the entire log terminal if I'll SSH to the server and run the command from the command line ) .

gojiradam@gmail.com (JIRA)

unread,
Nov 28, 2018, 5:58:01 PM11/28/18
to jenkinsc...@googlegroups.com
Adam Delarosa updated an issue
When using the Ansible Plugin with jenkins Pipeline ,
I can't see the entire log
in on Jenkins PIpeline build output - Some output is missing at the end of the Ansible play.
The output looks fine on a
terminal - if I'll SSH to the server and run the ansible-playbook command from the command line.

*
This issue started about a month ago..


Here is a screenshot of how the output look like now:
[https://imgur.com/waX7XcM]

Ansible Plugin:
[https://jenkins.io/doc/pipeline/steps/ansible/]

This is the Pipeline code that uses the Ansible Pipeline Plugin:
{code:java}
        stage('running something') {
            steps {
                script {
                    dir('my/path/here') {
                     ansiblePlaybook([
                     inventory   : 'hosts',
                     playbook    : 'main.yml',
                     installation: 'ansible',
                     sudoUser    : null,
                     colorized   : true,
                     extraVars   : [
                     blah   : "${params.blah}",
                     some_var       : "${params.some_var}"
                     ]
                     ])
                    }
                }
            }
        }
{code}

bspecht@trustwave.com (JIRA)

unread,
Dec 4, 2018, 12:10:02 PM12/4/18
to jenkinsc...@googlegroups.com
Ben Specht updated an issue
Change By: Ben Specht
Attachment: Screen Shot 2018-12-04 at 11.09.00 AM.png

bspecht@trustwave.com (JIRA)

unread,
Dec 4, 2018, 12:14:02 PM12/4/18
to jenkinsc...@googlegroups.com


Ansible Pipeline plugin Version 1.0

Jenkins version 2.138.3
Pipeline version 2.6

bspecht@trustwave.com (JIRA)

unread,
Dec 14, 2018, 1:23:02 PM12/14/18
to jenkinsc...@googlegroups.com

vivek.pandey@gmail.com (JIRA)

unread,
Dec 18, 2018, 10:12:02 AM12/18/18
to jenkinsc...@googlegroups.com
Vivek Pandey updated an issue
Change By: Vivek Pandey
Labels: ansible ansible-plugin jenkins pipeline pipeline-triaged playbook

andreiebh@gmail.com (JIRA)

unread,
Jan 4, 2019, 9:22:01 AM1/4/19
to jenkinsc...@googlegroups.com

andreiebh@gmail.com (JIRA)

unread,
Jan 4, 2019, 9:25:02 AM1/4/19
to jenkinsc...@googlegroups.com
Andrei Gheorghiu commented on Bug JENKINS-54929
 
Re: Some final output is missing in Jenkins Pipeline when using the Ansible Plugin

I also have the same issue, but only in the standard console, the Blue Ocean UI displays everything properly. Also, this behavior is strictly related to the plugin, as the same command called from Jenkins shell  works as expected. 
Running via ansible plugin[Pipeline] ansiblePlaybook[retry-test] $ ansible-playbook looping-with-parameters.yml -i inventory --extra-vars '{"commands_list": [ls, pwd, date, whoami]}'

PLAY [target] ******************************************************************

TASK [Gathering Facts] *********************************************************
ok: [eltf-qemu01]

TASK [Run test(s)] *************************************************************
changed: [eltf-qemu01] => (item=ls)
changed: [eltf-qemu01] => (item=pwd)
changed: [eltf-qemu01] => (item=date)[Pipeline] echoRunning from jenkins shell[Pipeline] sh+ ansible-playbook looping-with-parameters.yml -i inventory --extra-vars {"commands_list": [ls, pwd, date, whoami]}changed: [eltf-qemu01] => (item=whoami)

PLAY RECAP *********************************************************************
eltf-qemu01 : ok=2 changed=1 unreachable=0 failed=0 PLAY [target] ******************************************************************

TASK [Gathering Facts] *********************************************************ok: [eltf-qemu01]
TASK [Run test(s)] *************************************************************
changed: [eltf-qemu01] => (item=ls)
changed: [eltf-qemu01] => (item=pwd)
changed: [eltf-qemu01] => (item=date)
changed: [eltf-qemu01] => (item=whoami)

PLAY RECAP *********************************************************************
eltf-qemu01 : ok=2 changed=1 unreachable=0 failed=0

System info:
Ansible Pipeline plugin Version 1.0

Jenkins version 2.150.1
Pipeline version 2.6

Blue Ocean 1.10.1

andreiebh@gmail.com (JIRA)

unread,
Jan 4, 2019, 9:28:02 AM1/4/19
to jenkinsc...@googlegroups.com
Andrei Gheorghiu edited a comment on Bug JENKINS-54929
I also have the same issue, but only in the standard console, the Blue Ocean UI displays everything properly. Also, this behavior is strictly related to the plugin, as the same command called from Jenkins shell  works as expected. 

 
{quote}
Running via ansible plugin[Pipeline] ansiblePlaybook[retry-test] $ ansible-playbook looping-with-parameters.yml -i inventory --extra-vars '\{"commands_list": [ls, pwd, date, whoami]}'


PLAY [target] ******************************************************************

TASK [Gathering Facts] *********************************************************
ok: [eltf-qemu01]

TASK [Run test(s)] *************************************************************
changed: [eltf-qemu01] => (item=ls)
changed: [eltf-qemu01] => (item=pwd)
changed: [eltf-qemu01] => (item=date)[Pipeline] echoRunning from jenkins shell[Pipeline] sh+ ansible-playbook looping-with-parameters.yml -i inventory --extra-vars \{"commands_list": [ls, pwd, date, whoami]}changed: [eltf-qemu01] => (item=whoami)

PLAY RECAP *********************************************************************
eltf-qemu01                : ok=2    changed=1    unreachable=0    failed=0   PLAY [target] ******************************************************************

TASK [Gathering Facts] *********************************************************
ok: [eltf-qemu01]

TASK [Run test(s)] *************************************************************
changed: [eltf-qemu01] => (item=ls)
changed: [eltf-qemu01] => (item=pwd)
changed: [eltf-qemu01] => (item=date)
changed: [eltf-qemu01] => (item=whoami)

PLAY RECAP *********************************************************************
eltf-qemu01                : ok=2    changed=1    unreachable=0    failed=0
   
   {quote}

!ansible-plugin-blue-ocean.PNG!


System info:
Ansible Pipeline plugin Version 1.0
Jenkins version 2.150.1
Pipeline version 2.6

Blue Ocean 1.10.1

andreiebh@gmail.com (JIRA)

unread,
Jan 4, 2019, 9:30:02 AM1/4/19
to jenkinsc...@googlegroups.com
Andrei Gheorghiu edited a comment on Bug JENKINS-54929
I also have the same issue, but only in the standard console, the Blue Ocean UI displays everything properly. Also, this behavior is strictly related to the plugin, as the same command called from Jenkins shell  works as expected. 

 
{quote}Running via ansible plugin

[Pipeline] ansiblePlaybook
[retry-test] $ ansible-playbook looping-with-parameters.yml -i inventory --extra-vars ' \ {"commands_list": [ls, pwd, date, whoami]}'

PLAY [target] ******************************************************************

TASK [Gathering Facts] *********************************************************
ok: [eltf-qemu01]

TASK [Run test(s)] *************************************************************
changed: [eltf-qemu01] => (item=ls)
changed: [eltf-qemu01] => (item=pwd)
changed: [eltf-qemu01] => (item=date)

[Pipeline] echoRunning echo
Running
from jenkins shell
[Pipeline] sh
+ ansible-playbook looping-with-parameters.yml -i inventory --extra-vars \ {"commands_list": [ls, pwd, date, whoami]}
changed: [eltf-qemu01] => (item=whoami)

PLAY RECAP *********************************************************************
eltf-qemu01                : ok=2    changed=1    unreachable=0    failed=0
   


   PLAY [target] ******************************************************************

TASK [Gathering Facts] *********************************************************
ok: [eltf-qemu01]

TASK [Run test(s)] *************************************************************
changed: [eltf-qemu01] => (item=ls)
changed: [eltf-qemu01] => (item=pwd)
changed: [eltf-qemu01] => (item=date)
changed: [eltf-qemu01] => (item=whoami)

PLAY RECAP *********************************************************************
eltf-qemu01                : ok=2    changed=1    unreachable=0    failed=0   {quote}

!ansible-plugin-blue-ocean.PNG!

System info:
Ansible Pipeline plugin Version 1.0
Jenkins version 2.150.1
Pipeline version 2.6

Blue Ocean 1.10.1

andreiebh@gmail.com (JIRA)

unread,
Jan 4, 2019, 9:31:03 AM1/4/19
to jenkinsc...@googlegroups.com
Andrei Gheorghiu edited a comment on Bug JENKINS-54929
I also have the same issue, but only in the standard console, the Blue Ocean UI displays everything properly. Also, this behavior is strictly related to the plugin, as the same command called from Jenkins shell  works as expected. 

 
{quote} Running via ansible plugin

[Pipeline] ansiblePlaybook
[retry-test] $ ansible-playbook looping-with-parameters.yml -i inventory --extra-vars ' \ {"commands_list": [ls, pwd, date, whoami]}'

PLAY [target] ******************************************************************

TASK [Gathering Facts] *********************************************************
ok: [eltf-qemu01]

TASK [Run test(s)] *************************************************************
changed: [eltf-qemu01] => (item=ls)
changed: [eltf-qemu01] => (item=pwd)
changed: [eltf-qemu01] => (item=date)

[Pipeline]
echo
Running
echoRunning from jenkins shell
[Pipeline] sh
+ ansible-playbook looping-with-parameters.yml -i inventory --extra-vars \ {"commands_list": [ls, pwd, date, whoami]}
changed: [eltf-qemu01] => (item=whoami)

PLAY RECAP *********************************************************************
eltf-qemu01                : ok=2    changed=1    unreachable=0    failed=0
   


PLAY [target] ******************************************************************

TASK [Gathering Facts] *********************************************************
ok: [eltf-qemu01]

TASK [Run test(s)] *************************************************************
changed: [eltf-qemu01] => (item=ls)
changed: [eltf-qemu01] => (item=pwd)
changed: [eltf-qemu01] => (item=date)
changed: [eltf-qemu01] => (item=whoami)

PLAY RECAP *********************************************************************
eltf-qemu01                : ok=2    changed=1    unreachable=0    failed=0    {quote}
!ansible-plugin-blue-ocean.PNG!

System info:
Ansible Pipeline plugin Version 1.0
Jenkins version 2.150.1
Pipeline version 2.6

Blue Ocean 1.10.1

andreiebh@gmail.com (JIRA)

unread,
Jan 4, 2019, 9:33:02 AM1/4/19
to jenkinsc...@googlegroups.com

andreiebh@gmail.com (JIRA)

unread,
Jan 4, 2019, 9:37:03 AM1/4/19
to jenkinsc...@googlegroups.com

andreiebh@gmail.com (JIRA)

unread,
Jan 4, 2019, 9:40:01 AM1/4/19
to jenkinsc...@googlegroups.com
Andrei Gheorghiu commented on Bug JENKINS-54929
 
Re: Some final output is missing in Jenkins Pipeline when using the Ansible Plugin

Looks like if there is another step after the ansible-playbook call, the missing output gets printed out at some point, but later than it should (please see the two attached images)

If the ansible-playbook is the last step in the pipeline, or if it exits with error, the text is left missing.

gojiradam@gmail.com (JIRA)

unread,
Jan 6, 2019, 2:51:02 AM1/6/19
to jenkinsc...@googlegroups.com

Andrei GheorghiuAndrei Gheorghiu For me, In Blue Ocean, I see the output as bad as at standard output..

ruslan.bondarau@gmail.com (JIRA)

unread,
Jan 6, 2019, 10:31:02 AM1/6/19
to jenkinsc...@googlegroups.com

ruslan.bondarau@gmail.com (JIRA)

unread,
Jan 6, 2019, 10:34:02 AM1/6/19
to jenkinsc...@googlegroups.com

I also have the same issue

Ansible Pipeline plugin Version 1.0
Jenkins version 2.138.2
Pipeline: Declarative 1.3.4

 

bdebotte@libertyglobal.com (JIRA)

unread,
Jan 7, 2019, 7:56:03 AM1/7/19
to jenkinsc...@googlegroups.com

bdebotte@libertyglobal.com (JIRA)

unread,
Jan 7, 2019, 7:56:13 AM1/7/19
to jenkinsc...@googlegroups.com

bdebotte@libertyglobal.com (JIRA)

unread,
Jan 7, 2019, 7:58:02 AM1/7/19
to jenkinsc...@googlegroups.com
Benjamin Debotte commented on Bug JENKINS-54929
 
Re: Some final output is missing in Jenkins Pipeline when using the Ansible Plugin

Same issue here.

 

Ansible plugin 1.0

Ansible 2.5.6

 

Jenkins Blue output:

Local session:

pablogrs@gmail.com (JIRA)

unread,
Jan 30, 2019, 9:31:02 AM1/30/19
to jenkinsc...@googlegroups.com

I am seeing the same, hardcoded Ansible commands shows proper output but the plugin doesn't

h0neyb4dgerdc@gmail.com (JIRA)

unread,
Jan 31, 2019, 5:12:02 AM1/31/19
to jenkinsc...@googlegroups.com

Hello,

We are facing the same issue on our jenkins.

We checked many versions and the bug is visible from the version LTS 2.138.1.

  • 2.138.4 nok
  • 2.138.3 nok
  • 2.138.2 nok
  • 2.138.1 nok
  • 2.121.3 ok

Another interesting fact is that the bug is not present on pipeline ran from the master. It only affects remote executions.

 

This issue may be related to the following fix:

https://github.com/jenkinsci/jenkins/commit/ebd71116c15b97fd3e855a738fbfdef387cd6e3c

I reverted the commit and recompiled the latest version and now I'am able to see the full log (but some logs remain overwritten by the ssh-agent).

I do not know if this FIX JENKINS-52729 is directly involved to our bug. Maybe Jesse Glick could help on that issue.

jglick@cloudbees.com (JIRA)

unread,
Jan 31, 2019, 9:23:02 AM1/31/19
to jenkinsc...@googlegroups.com

Not familiar with this plugin so cannot give details, but in general if you have a Callable (or FileCallable) running on an agent that has been passed a serialized TaskListener, it will need to flush before returning.

jglick@cloudbees.com (JIRA)

unread,
Jan 31, 2019, 9:24:03 AM1/31/19
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
 
Change By: Jesse Glick
Component/s: pipeline
Labels: ansible ansible-plugin jenkins pipeline pipeline-triaged playbook

mosonkonrad@gmail.com (JIRA)

unread,
Apr 9, 2019, 9:54:02 AM4/9/19
to jenkinsc...@googlegroups.com

sven@hergenhahn-web.de (JIRA)

unread,
Apr 25, 2019, 4:00:04 AM4/25/19
to jenkinsc...@googlegroups.com

Mee too. Since usually when a problem occurs, the output at the end is important, I've for now resorted to using ansible-playbook with `sh 'ansible-playbook ...'` in my pipeline and since have no problem with my output

sven@hergenhahn-web.de (JIRA)

unread,
Apr 25, 2019, 4:01:03 AM4/25/19
to jenkinsc...@googlegroups.com
Sven Hergenhahn edited a comment on Bug JENKINS-54929
Mee too. Since usually when a problem occurs, the output at the end is important, I've for now resorted to using ansible-playbook with ` {{ sh 'ansible-playbook ...' ` }}   in my pipeline and since have no problem with my output .

I would prefer to return to the plugin though if possible

pablogrs@gmail.com (JIRA)

unread,
Apr 25, 2019, 4:10:02 AM4/25/19
to jenkinsc...@googlegroups.com

What I did to solve this, instead of manually calling Ansible from the Pipeline I extended the pipeline with a library method which calls Ansible.

Something like:

class Ansible implements IAnsible{    
    def context
    Map arguments    
    def ansiblePlaybook
    def ansibleInventory
    def ansibleExtras
    def ansibleExtraVars    

    Ansible(Map arguments, context){
        this.context = context
        this.arguments = arguments    
    }

    void parseArguments(Map arguments){
        ansiblePlaybook = arguments.get("playbook", '')
        ansibleInventory = arguments.get("inventory", '')
        ansibleExtras = arguments.get("extras", '')
        ansibleExtraVars = arguments.get("extraVars", '')
    }    

    String parseAnsibleExtraVars(Map extras){
        def sb = new StringBuilder()        
        sb.append('\'')
        ansibleExtraVars.each(){ key, value ->
            sb.append(key)
            sb.append('=')
            sb.append(value)
            sb.append(' ')
        }
        sb.append('\'')        
        return sb.toString()
    }    

    void playbookCall(){
      parseArguments(this.arguments)        
      def extraVars = parseAnsibleExtraVars(ansibleExtraVars)        
      context.sh """ export ANSIBLE_FORCE_COLOR=1 \ 
        && ansible-playbook -i ${ansibleInventory} ${ansiblePlaybook} --extra-vars ${extraVars}    ${ansibleExtras} """    
   }
}

And you call it pretty much in the same way from the pipeline, just create a method in vars:

// code placeholder
import com.ansible.Ansible
        def call(Map ansibleParameters){
            def ansibleRunner = new Ansible(ansibleParameters, this)
            ansiColor('xterm') {
                ansibleRunner.playbookCall()
            }
        }

 

 

steven@sclark.me (JIRA)

unread,
Apr 26, 2019, 8:58:03 AM4/26/19
to jenkinsc...@googlegroups.com

I've submitted a PR that addresses this issue at least for me (https://github.com/jenkinsci/ansible-plugin/pull/29).Hopefully someone could accept it and create a bugfix release with it. 

steven@sclark.me (JIRA)

unread,
Apr 26, 2019, 12:47:04 PM4/26/19
to jenkinsc...@googlegroups.com
Steven Clark edited a comment on Bug JENKINS-54929
I've submitted a PR that addresses this issue at least for me ([https://github.com/jenkinsci/ansible-plugin/pull/29]).Hopefully someone could accept it and create a bugfix release with it. 

 

*EDIT:* **Looks like there are a very different cases, the patch in that PR seemed to address at least one, but we are still seeing some trimmed output depending on how Anisble might have died from the looks of things. Will keep on looking into the plugin but for now I've pulled the PR.

steven@sclark.me (JIRA)

unread,
Apr 26, 2019, 12:47:05 PM4/26/19
to jenkinsc...@googlegroups.com
Steven Clark edited a comment on Bug JENKINS-54929
I've submitted a PR that addresses this issue at least for me ([https://github.com/jenkinsci/ansible-plugin/pull/29]).Hopefully someone could accept it and create a bugfix release with it. 

 

*EDIT:* **   Looks like there are a very different cases, the patch in that PR seemed to address at least one, but we are still seeing some trimmed output depending on how Anisble might have died from the looks of things. Will keep on looking into the plugin but for now I've pulled the PR.

steven@sclark.me (JIRA)

unread,
Apr 26, 2019, 12:47:07 PM4/26/19
to jenkinsc...@googlegroups.com
Steven Clark edited a comment on Bug JENKINS-54929
I've submitted a PR that addresses this issue at least for me ([https://github.com/jenkinsci/ansible-plugin/pull/29]).Hopefully someone could accept it and create a bugfix release with it. 

 

*EDIT:* Looks like there are a very few different cases, the patch in that PR seemed to address at least one, but we are still seeing some trimmed output depending on how Anisble Ansible might have died from the looks of things. Will I'll keep on looking into the plugin but for now I've pulled the PR.

anandasattva@gmail.com (JIRA)

unread,
May 23, 2019, 7:51:02 AM5/23/19
to jenkinsc...@googlegroups.com

andreiebh@gmail.com (JIRA)

unread,
May 24, 2019, 4:02:04 AM5/24/19
to jenkinsc...@googlegroups.com

andreiebh@gmail.com (JIRA)

unread,
May 24, 2019, 4:02:05 AM5/24/19
to jenkinsc...@googlegroups.com

andreiebh@gmail.com (JIRA)

unread,
May 24, 2019, 4:02:07 AM5/24/19
to jenkinsc...@googlegroups.com

andreiebh@gmail.com (JIRA)

unread,
May 24, 2019, 4:03:02 AM5/24/19
to jenkinsc...@googlegroups.com
Andrei Gheorghiu updated an issue
Change By: Andrei Gheorghiu
Comment: I also have the same issue, but only in the standard console, the Blue Ocean UI displays everything properly. Also, this behavior is strictly related to the plugin, as the same command called from Jenkins shell  works as expected. 

 
{quote}Running via ansible plugin[Pipeline] ansiblePlaybook[retry-test] $ ansible-playbook looping-with-parameters.yml -i inventory --extra-vars '\{"commands_list": [ls, pwd, date, whoami]}'

PLAY [target] ******************************************************************

TASK [Gathering Facts] *********************************************************
ok: [eltf-qemu01]

TASK [Run test(s)] *************************************************************
changed: [eltf-qemu01] => (item=ls)
changed: [eltf-qemu01] => (item=pwd)
changed: [eltf-qemu01] => (item=date)[Pipeline] echoRunning from jenkins shell[Pipeline] sh+ ansible-playbook looping-with-parameters.yml -i inventory --extra-vars \{"commands_list": [ls, pwd, date, whoami]}changed: [eltf-qemu01] => (item=whoami)

PLAY RECAP *********************************************************************
eltf-qemu01                : ok=2    changed=1    unreachable=0    failed=0   PLAY [target] ******************************************************************

TASK [Gathering Facts] *********************************************************
ok: [eltf-qemu01]

TASK [Run test(s)] *************************************************************
changed: [eltf-qemu01] => (item=ls)
changed: [eltf-qemu01] => (item=pwd)
changed: [eltf-qemu01] => (item=date)
changed: [eltf-qemu01] => (item=whoami)

PLAY RECAP *********************************************************************
eltf-qemu01                : ok=2    changed=1    unreachable=0    failed=0   {quote}
!ansible-plugin-blue-ocean.PNG!

System info:

Ansible Pipeline plugin Version 1.0
Jenkins version 2.150.1
Pipeline version 2.6

Blue Ocean 1.10.1

steven@sclark.me (JIRA)

unread,
Jun 2, 2019, 3:10:02 PM6/2/19
to jenkinsc...@googlegroups.com
Steven Clark commented on Bug JENKINS-54929
 
Re: Some final output is missing in Jenkins Pipeline when using the Ansible Plugin

So we've been running with the latest PR (https://github.com/jenkinsci/ansible-plugin/pull/30) I created for the past two weeks and this new version of the PR seems to solve the issue.

 

Is it possible to get the maintainer to look through the PR to get a new release of the plugin?

 

eyalg1972@gmail.com (JIRA)

unread,
Sep 4, 2019, 1:10:02 AM9/4/19
to jenkinsc...@googlegroups.com

I wanted to use the plugin, but our deployments need to run some commands on Websphere, and in case of failures the plugin does not show the error log, so I needed to move to sh as well.

 

Waiting for the new release.

Reply all
Reply to author
Forward
0 new messages