-
Notifications
You must be signed in to change notification settings - Fork 21
New branch adjustments
Josef Smrcka edited this page May 21, 2021
·
1 revision
In parent POM, adjust Quarkus version, dependencies, build image versions, or other configuration if needed. E.g.:
...
<groupId>io.quarkus.qe</groupId>
<artifactId>beefy-scenarios</artifactId>
...
<properties>
...
<quarkus.platform.version>1.11.6.Final</quarkus.platform.version>
<quarkus-plugin.version>1.11.6.Final</quarkus-plugin.version>
...
</properties>
...
005-quarkus-and-maven-profiles/pom.xml
references specific Quarkus version in a profile:
...
<parent>
<groupId>io.quarkus.qe</groupId>
<artifactId>beefy-scenarios</artifactId>
<version>1.0.0-SNAPSHOT</version>
</parent>
<artifactId>005-quarkus-and-maven-profiles</artifactId>
...
<profiles>
<profile>
<id>my-profile</id>
...
<properties>
<quarkus.platform.version>1.11.5.Final</quarkus.platform.version>
<quarkus-plugin.version>1.11.5.Final</quarkus-plugin.version>
</properties>
...
</profile>
</profiles>
</project>
References:
quarkus-main-build
job should not be necessary if the branch uses published Quarkus release. Optionally, the job may be removed:
name: "Pull Request Build"
on:
- pull_request
jobs:
# REMOVE
# quarkus-main-build:
# name: Quarkus Main build
...
linux-build:
name: Linux - PR build
runs-on: ubuntu-latest
# REMOVE
# needs: quarkus-main-build
...
windows-build:
name: Windows - PR build
runs-on: windows-latest
# REMOVE
# needs: quarkus-main-build
...
References:
Triggered only on default branch.
References: