-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customize build steps in release.yml
and ci-build.yml
#519
Labels
feature
Product feature
Comments
This was referenced Jan 24, 2024
kaklakariada
added a commit
that referenced
this issue
Mar 27, 2024
kaklakariada
added a commit
that referenced
this issue
Mar 27, 2024
kaklakariada
added a commit
that referenced
this issue
Mar 27, 2024
kaklakariada
added a commit
that referenced
this issue
Mar 28, 2024
kaklakariada
added a commit
that referenced
this issue
Apr 2, 2024
kaklakariada
added a commit
that referenced
this issue
Apr 2, 2024
kaklakariada
added a commit
that referenced
this issue
Apr 3, 2024
kaklakariada
added a commit
that referenced
this issue
Apr 3, 2024
kaklakariada
added a commit
that referenced
this issue
Apr 3, 2024
kaklakariada
added a commit
that referenced
this issue
Apr 3, 2024
This was referenced Apr 3, 2024
kaklakariada
added a commit
that referenced
this issue
Apr 5, 2024
Co-authored-by: Christoph Kuhnke <[email protected]>
kaklakariada
added a commit
that referenced
this issue
Apr 5, 2024
kaklakariada
added a commit
that referenced
this issue
Apr 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Goal: Custom preparation / build / cleanup steps
Some projects need custom preparation / build / cleanup steps like installing additional tools (Go, node, ...), writing test config files, passing secrets as env variables to the build step or deleting resources afterwards.
Implementation
Add optional configuration options to
.project-keeper.yml
:run: mvn verify
by defaultenv
if presentEach option can have the following properties for a custom build step using GH action syntax (see GH documentation):
name:
optional readable nameuses:
optional GH action (-> e.g. allow installing other tools)with:
optional map of args for a GH actionrun:
multiline shell scriptshell:
optional shell type (bash, powershell, ...)env:
list of environment variables. This allows specifying GH secrets or matrix build variablesif:
allow running for specific versions/OS/always()Option questions
Out of scope:
mvn javadoc:javadoc
instead ofmvn package
The text was updated successfully, but these errors were encountered: