New branch adjustments

New branch - needed adjustments and things to look out for

POM

In parent POM, adjust Quarkus version, dependencies, build image versions, or other configuration if needed. E.g.:

...
    <groupId>io.quarkus.ts.openshift</groupId>
    <artifactId>parent</artifactId>
...
    <properties>
        ...
        <version.quarkus>1.11.6.Final</version.quarkus>
        ...
    </properties>
...

References:

• pom.xml

Github wokrflows

Pull Request CI - build of Quarkus main

build-master job - no need for that, remove entirely. Alternatively, adjust to build appropriate branch of Quarkus. E.g.:

...
  build-master:
    name: JVM build - Quarkus 1.11
    ...
    steps:
      ...
      - name: Build Quarkus 1.11
        run: git clone https://github.com/quarkusio/quarkus.git && cd quarkus && git checkout 1.11 && mvn -B -s .github/mvn-settings.xml clean install -DskipTests -DskipITs -DskipDocs
      - name: Build with Maven
        run: mvn -fae -V -B clean test -Dquarkus-core-only -Dinclude.serverless
      ...
...

References:

• .github/workflows/ci.yml

OpenShift resources

When referencing a repository, look out for compatibility issues with (un)specified branch. E.g:

...
- apiVersion: build.openshift.io/v1
  kind: BuildConfig
  ...
  spec:
    ...
    source:
      git:
        uri: https://github.com/quarkusio/quarkus-quickstarts
        ref: "1.11"
      ...
    ...
...

References:

• external-applications/quickstart-using-s2i/src/test/resources/quickstart-using-s2i.yaml