Skip to content
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

feat: added Maven java 17 pack #914

Merged
merged 47 commits into from
Oct 12, 2021

Conversation

babadofar
Copy link
Contributor

No description provided.

babadofar and others added 30 commits August 6, 2021 23:22
…882e286db9d

chore(deps): upgrade Mentor-Medier/jx3-pipeline-catalog to version 3.2.182
Java 11 update task link to Mentor-medier from jenkins-x
…44bdc8bcbce3

chore(deps): upgrade Mentor-Medier/jx3-pipeline-catalog to version 3.2.182
…-ea3701e274bb

chore(deps): upgrade Mentor-Medier/jx3-pipeline-catalog to version 3.2.188
setting Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn in MAVEN_OPTS to disable logging downloaded libraries
Adding option to use maven batch mode
…a49ecfc40db3

chore(deps): upgrade Mentor-Medier/jx3-pipeline-catalog to version 3.2.188
@jenkins-x-bot
Copy link
Contributor

Hi @babadofar. Thanks for your PR.

I'm waiting for a jenkins-x or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

@babadofar
Copy link
Contributor Author

babadofar commented Oct 1, 2021

One thing worth noting here is the addition of build step build-mvn-install to the release pipeline. Keeping the existing build-mvn-deploy as the default, so people can opt in and change their builds in case they don't need to publish jars for all projects. To save resources and the environment 🌳 solves #913

@ankitm123
Copy link
Member

/ok-to-test

@ankitm123
Copy link
Member

/lgtm

@jenkins-x-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ankitm123
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rawlingsj rawlingsj merged commit 22ec70a into jenkins-x:master Oct 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants