Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Jenkinsfile docker stage requires an agent but agent is none #790

Closed
kavilla opened this issue Oct 22, 2021 · 3 comments · Fixed by #791
Closed

[Bug]: Jenkinsfile docker stage requires an agent but agent is none #790

kavilla opened this issue Oct 22, 2021 · 3 comments · Fixed by #791
Labels
bug Something isn't working

Comments

@kavilla
Copy link
Member

kavilla commented Oct 22, 2021

Describe the bug

The detect Docker image + args to use for the build stage for the OpenSearch and OpenSearch Dashboards Jenkinsfile throws this error:

Required context class hudson.FilePath is missing Perhaps you forgot to surround the code with a step that provides this, such as: node
--
Error signal | Attempted to execute a step that  requires a node context while ‘agent none’ was specified. Be sure to  specify your own ‘node { ... }’ blocks when using ‘agent none’.

The agent is none for the pipeline so each stage would have to define there on agent if they are doing work.

To reproduce

Run https://github.com/opensearch-project/opensearch-build/blob/main/jenkins/opensearch-dashboards/Jenkinsfile through Jenkins and see error.

Expected behavior

For it to build.

Screenshots

No response

Host / Environment

No response

Additional context

Should we just throw

agent {
      docker {
          label 'Jenkins-Agent-al2-x64-c54xlarge-Docker-Host'
          image 'opensearchstaging/ci-runner:centos7-x64-arm64-jdk14-node10.24.1-cypress6.9.1-20211005'
          alwaysPull true
      }
}

into that stage? Or just create an agent that can does the work of pulling that value from the manifest.yaml file.

Relevant log output

No response

@kavilla kavilla added bug Something isn't working untriaged Issues that have not yet been triaged labels Oct 22, 2021
@reta
Copy link
Contributor

reta commented Oct 22, 2021

@kavilla @dblock looking into this

@kavilla
Copy link
Member Author

kavilla commented Oct 22, 2021

@reta, I believe @peternied is working on a solution for now as well.

@reta
Copy link
Contributor

reta commented Oct 22, 2021

Oops, thanks @kavilla , definitely leaving it to @peternied , thank you

@kavilla kavilla removed the untriaged Issues that have not yet been triaged label Oct 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants