Conversation
…ve-linux /build-native-mac /build-native-windows Agent-Logs-Url: https://github.com/eclipse-jkube/kport/sessions/af8f4136-708a-4ba6-8b24-7fdcbe12ed1e Co-authored-by: sunix <[email protected]>
|
/build-native-linux |
|
@copilot should add a comment saying that it is starting with the job url, and update the same comment once it is done with the url link of the downloadable url, or saying that there is an error with the job url. |
📦 Native binaries availableThe native binaries for this PR have been built and are available for download: ➡️ Download artifacts from this Actions run Artifacts expire after 1 day. |
Done in commit
|
|
/build-native-linux |
Native builds were running on every PR open/synchronize, consuming expensive macOS/Windows runners unconditionally. They should only run when explicitly requested.
Changes
pull_requesttrigger frompr-build-native.yml— native builds no longer fire automatically on PR eventsissue_commenttrigger — workflow activates when a PR comment contains one of:/build-native-linux→ runsubuntu-latest/build-native-mac→ runsmacos-latest/build-native-windows→ runswindows-latestbuild-linux,build-mac,build-windows), each gated bygithub.event.issue.pull_request != null+ comment body check — individual platforms can be triggered independentlyhead.shavia the GitHub API before checkout, sinceissue_commentevents carry no PR refpermissions: contents: readto all build jobs;commentandnotify-startjobs useissues: writenotify-startjob immediately posts a "🚀 Native build starting" comment on the PR listing the triggered platforms and a link to the running job; thecommentjob then updates that same comment with per-platform ✅/❌ results, an artifact download link on success, or a log link on failure