Migrate to the reusable GHA#75
Conversation
346f3cc to
898fcea
Compare
| run: | | ||
| mvn clean verify --batch-mode --file pom.xml | ||
|
|
||
| owasp-dependency-check: |
There was a problem hiding this comment.
There's no point in running this:
- The content package has no dependencies
- The content package has no code
Consequently, it's not the kind of thing OWASP can detect, etc.
There was a problem hiding this comment.
OTOH, why wouldn't we change the rest of the workflow to use the default build workflow?
There was a problem hiding this comment.
@ibacher problem is that the reusable build-backend-module workflow is written specifically for backend OMOD modules, and this repo is a content package.
ex:
There was a problem hiding this comment.
Well, that is a workflow called "build-backend-module" not "build-maven-project", so I guess I', fine with that. Maybe we can factor out something less module-specific for content packages, etc.?
|
@ibacher I decided to leave the build job as it is and only move the release job to use our common GHA. |
2 participants
No description provided.