Update buildenv for stable version and dependencies#25
Conversation
Signed-off-by: Sachin <32639496+sachintu47@users.noreply.github.com>
…ase' Signed-off-by: Sachin <32639496+sachintu47@users.noreply.github.com>
sachintu47
requested review from
IgorTodorovskiIBM and
MikeFultonDev
as code owners
|
augment review |
🤖 Augment PR SummarySummary: Updates build metadata to treat this port as a STABLE build pinned to zoslib v4.0.1 and adds a repository_dispatch trigger for automated version bumps. 🤖 Was this summary useful? React with 👍 or 👎 |
![augmentcode[bot]](https://avatars.githubusercontent.com/in/1027498?s=60&v=4){kind=small}
| # enable manual trigger of version updates | ||
| workflow_dispatch: | ||
| # trigger on upstream repository tag events | ||
| repository_dispatch: |
There was a problem hiding this comment.
Adding a repository_dispatch trigger means anyone able to fire that dispatch can run this workflow with contents: write and the BUMP_TOKEN secret; please make sure the sender/payload is validated so this can’t be abused.
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
| doGenerateSubmoduleConfigurations: false, | ||
| extensions: [], | ||
| userRemoteConfigs: [[url: "https://github.com/zopencommunity/zoslibport.git"]]]) | ||
| // Poll changes from upstream |
There was a problem hiding this comment.
Removing the upstream checkout means the Jenkins “Poll” stage will no longer detect changes/releases in zopencommunity/zoslib; please confirm there’s an alternate trigger path for rebuilding when upstream updates.
Severity: low
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
1 participant
No description provided.