Skip to content

Finalize CI/CD Pipeline - #2897

Closed
24-Kwek-44 wants to merge 23 commits into
google:mainfrom
24-Kwek-44:feature/ci-pipeline
Closed

Finalize CI/CD Pipeline#2897
24-Kwek-44 wants to merge 23 commits into
google:mainfrom
24-Kwek-44:feature/ci-pipeline

Conversation

@24-Kwek-44

Copy link
Copy Markdown

Purpose

Description

Checklist

  • New code follows the Google Java Style Guide
    This is automatically checked by mvn verify, but can also be checked on its own using mvn spotless:check.
    Style violations can be fixed using mvn spotless:apply; this can be done in a separate commit to verify that it did not cause undesired changes.
  • If necessary, new public API validates arguments, for example rejects null
  • New public API has Javadoc
    • Javadoc uses @since $next-version$
      ($next-version$ is a special placeholder which is automatically replaced during release)
  • If necessary, new unit tests have been added
    • Assertions in unit tests use Truth, see existing tests
    • No JUnit 3 features are used (such as extending class TestCase)
    • If this pull request fixes a bug, a new test was added for a situation which failed previously and is now fixed
  • mvn clean verify javadoc:jar passes without errors

24-Kwek-44 and others added 23 commits August 21, 2025 20:59
…sfully. Meaningful code: added GsonVersion as a version displaying feature (and the respective unit test too)
Done build automation with added Gson versioning feature
Configure unit test and code coverage test with report
Add Dockerfile for deployment automation
@google-cla

google-cla Bot commented Sep 4, 2025

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Comment on lines +7 to +24
runs-on: ubuntu-latest
steps:
- name: Checkout repository code
uses: actions/checkout@v3
- name: Set up JDK 11
uses: actions/setup-java@v3
with:
java-version: '11'
distribution: 'temurin'
- name: Build project with Maven
run: mvn -B verify --file pom.xml
- name: Upload build artifact
uses: actions/upload-artifact@v4
with:
name: gson-jar
path: gson/target/gson-*.jar

test:

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
Comment on lines +25 to +43
needs: build
runs-on: ubuntu-latest
steps:
- name: Checkout repository code
uses: actions/checkout@v3
- name: Set up JDK 11
uses: actions/setup-java@v3
with:
java-version: '11'
distribution: 'temurin'
- name: Run unit tests with Maven
run: mvn -B verify
- name: Upload test reports
uses: actions/upload-artifact@v4
with:
name: test-reports
path: gson/target/surefire-reports/

deploy:

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
Comment on lines +44 to +57
needs: test
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v3

- name: Download build artifact
uses: actions/download-artifact@v4
with:
name: gson-jar
path: gson/target/

- name: Build Docker image
run: docker build -t gson-app .

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
@24-Kwek-44 24-Kwek-44 closed this Sep 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants