Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-44000

awsIdentity and withAWS uses master and not the slave. version pipeline-aws-plugin - 2.12

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Won't Fix
    • pipeline-aws-plugin
    • None
    • pipeline-aws-plugin - 2.12

    Description

      awsIdentity and withAWS uses master and not the slave.

      See details here.

      https://gist.github.com/ajohnstone/7e6179e24509bceff4361fd82ca2c3a6

       

      master instance is ecs-instance-bootstrap/i-c02c1c28 and the executing node is actually i-0c388429a809ca1c0 with arn:aws:sts::49<REDACTED>63:assumed-role/jenkins-instance-role/i-0c388429a809ca1c0

      Attachments

        Activity

          ctennis Caleb Tennis added a comment -

          No problem, thanks for the plugin contribution!

          ctennis Caleb Tennis added a comment - No problem, thanks for the plugin contribution!
          caseteroconamor Ruben Sancho Ramos added a comment - - edited

          Hello I have the same issue, actually for me it's working fine on Declarative Pipeline, but on Scripted Pipeline I have the same problem described above. On both pipelines I define the "node" (SP) / "agent" (DP) directive pointing to the same ECS Cloud Slave template, but I don't get the same result.

          On Scripted Pipeline, all the other commands are executed on the slave as expected, only the ones provided by this plugin are executed on the master.

          I'm using Jenkins 2.100 and Pipeline: AWS Steps v1.20

          caseteroconamor Ruben Sancho Ramos added a comment - - edited Hello I have the same issue, actually for me it's working fine on Declarative Pipeline, but on Scripted Pipeline I have the same problem described above. On both pipelines I define the "node" (SP) / "agent" (DP) directive pointing to the same ECS Cloud Slave template, but I don't get the same result. On Scripted Pipeline, all the other commands are executed on the slave as expected, only the ones provided by this plugin are executed on the master. I'm using Jenkins 2.100 and Pipeline: AWS Steps v1.20

          I contacted Cloudbees/Jenkins and the described behavior is expected. Plugins should use the master for this kind of interaction.

          hoegertn Thorsten Hoeger added a comment - I contacted Cloudbees/Jenkins and the described behavior is expected. Plugins should use the master for this kind of interaction.

          mmmm OK but how comes that it works well with Declarative Pipeline? shouldn't it be consistent?

          caseteroconamor Ruben Sancho Ramos added a comment - mmmm OK but how comes that it works well with Declarative Pipeline? shouldn't it be consistent?

          That is a very good question but I am afraid I cannot answer it. To be honest documentation for plugin developers is very bad concerning slaves.

          hoegertn Thorsten Hoeger added a comment - That is a very good question but I am afraid I cannot answer it. To be honest documentation for plugin developers is very bad concerning slaves.

          People

            hoegertn Thorsten Hoeger
            ajohnstone Andrew Johnstone
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: