Skip to content

Jenkins service GitHub webhook and script problems

Summary

We are looking to use your Jenkins instance for signing our applications, and you have kindly installed the GitHub WebHook plugin for us at: https://ci.eclipse.org/esmf.

However, we've encountered a limitation with this plugin—it does not support using curl to push/trigger builds with parameters, as detailed in this issue: https://issues.jenkins.io/browse/JENKINS-24291.

To work around this, we considered creating a branch during the GitHub Actions to store the data we intended to send, and then extracting and using this data in the Jenkinsfile.

Unfortunately, it appears we do not have the necessary permissions to use scripts such as readFile to implement this solution, as evident from our attempt here: https://ci.eclipse.org/esmf/job/SIGN_AME_BACKEND_WINDOWS/18/console.

Could you please assist us in enabling these capabilities, or suggest an alternative approach that would comply with your system's permissions and policies?

Steps to reproduce

Look here https://ci.eclipse.org/esmf/job/SIGN_AME_BACKEND_WINDOWS/18/console and https://github.com/eclipse-esmf/esmf-aspect-model-editor-backend/pull/73

What is the expected correct behavior?

We have access to this script and maybe also others.

Relevant logs and/or screenshots

Look here https://ci.eclipse.org/esmf/job/SIGN_AME_BACKEND_WINDOWS/18/console

Priority

  • Urgent
  • High
  • Medium
  • Low

Severity

  • Blocker
  • Major
  • Normal
  • Low

Impact

Its blocking our signing of binaries.

Edited by Michele Santoro