Request Jenkins Instance for ESMF

Summary

Our users need a signed exe installer for the esmf-aspect-model-editor and esmf-aspect-model-editor-backend.

Therefore we need a Jenkins instance to sign them.

Reference to this Issue: #3529 (closed)

added IT-prioritylow IT-severitylow ~24521 statetodo team:releng labels

assigned to @pstankie

added statewip label and removed statetodo label

The Eclipse Semantic Modeling Framework (ESMF) JIPP on Jiro is available here now:

=> https://ci.eclipse.org/esmf

PLEASE NOTE:

• Publishing to download.eclipse.org requires access via SCP. Please see https://wiki.eclipse.org/Jenkins#How_do_I_deploy_artifacts_to_download.eclipse.org.3F for more info.

• To simplify setting up jobs on our cluster-based infra, we provide a pod template that can also be used with freestyle jobs. The pod template has the label "centos-7" which can be specified in the job configuration under "Restrict where this project can be run". The image contains more commonly used dependencies than the default “basic” pod template.

• You can find more info about Jenkins here: https://wiki.eclipse.org/Jenkins

Please let us know if you need any additional plug-ins.

A GitHub bot (ID: eclipse-esmf-bot) credentials have been added to the esmf JIPP.

The recommended way to set up a job that builds pull requests is to use a Multibranch Pipeline job (a Jenkinsfile in your repo is required):

1. New item > Multibranch Pipeline
2. Branch Sources > Add source > GitHub
3. Select credentials "GitHub bot (username/token)"
4. Add the repository URL
5. Configure behaviors
6. Save

By default, all branches and PRs will be scanned and dedicated build jobs will be created automatically (if a Jenkinsfile is found).

Please, reopen if more action is needed.

closed

removed statewip label

reopened

@michelu89 we noticed that no CI jobs have been created in the last 3 months. Are you still intending to utilize the ESMF CI instance, or should we remove it?

added Awaiting Feedback label

changed due date to January 15, 2024

If we don't hear back from the project before January 15, 2024, we will retire the ESMF Jenkins instance.

/cc @bbossx8a @chrisvolk @thomashenn

Hi, we are currently in the process of implementing this.

Hi @pstankie / @fgurr, I have looked into the matter, and we would like to manually trigger the webhook from GitHub using GitHub Actions: GitHub Jenkins Plugin - Manual Mode.

To achieve this, we need to create an API token that allows us to call the webhook from GitHub using a CURL command. Here's an example:

curl -X POST https://ci.eclipse.org/esmf/job/Sign-Native-Image/github-webhook/ \ -H "Authorization: token ${{ secrets.JENKINS_API_TOKEN }}" \ -H "Content-Type: application/json" \ -d '{"event_type": "trigger_jenkins"}

An API token can be generated through the configuration settings. I have also found a helpful video explaining the process: YouTube Video on Jenkins API Token.

Our objective is:

After the executable is created, a GitHub Action will call the Jenkins hook. This hook, in turn, is configured in the JENKINSFILE to download the ".exe" file, sign it, and then upload it to the Assets Release directory on GitHub.

removed due date January 15, 2024

closed

mentioned in issue #4258

marked this issue as related to #4597 (closed)