Skip to content

Conversation

@JimSuplizio
Copy link
Contributor

When executing mvn gpg:sign-and-deploy-file it always just pulls the latest version of org.apache.maven.plugins:maven-gpg-plugin. On Friday, 03/08/2024, version 3.2.0 was published and it looks like our pipelines started picking this version up yesterday and we're seeing publishing failures trying to publish to the dev feed in release pipelines as well as nightly scheduled runs.

This change will allow us to set the version of org.apache.maven.plugins:maven-gpg-plugin used by the publish commands. Right now, I'm setting it back to 3.1.0 to unblock publishing until I'm able to figure out why 3.2.0 is failing. Unfortunately, the release notes for 3.2.0 are beyond unhelpful.

To test this particular change I'm going to be running the Template pipeline against this refs/merge.

@JimSuplizio JimSuplizio added the EngSys This issue is impacting the engineering system. label Mar 12, 2024
@JimSuplizio JimSuplizio self-assigned this Mar 12, 2024
@JimSuplizio
Copy link
Contributor Author

JimSuplizio commented Mar 12, 2024

I ran the template pipeline against the refs/merge of this PR and changes worked. I'm going to override check enforcer to get these merged in.

Note: The Update Package Version steps are going to fail when running against a refs/merge which is why the override is required.

@JimSuplizio
Copy link
Contributor Author

/check-enforcer override

@JimSuplizio
Copy link
Contributor Author

/check-enforcer evaluate

@JimSuplizio
Copy link
Contributor Author

@microsoft-github-policy-service rerun

1 similar comment
@JimSuplizio
Copy link
Contributor Author

@microsoft-github-policy-service rerun

@JimSuplizio JimSuplizio merged commit 4fb3af1 into Azure:main Mar 12, 2024
@JimSuplizio JimSuplizio deleted the SetGPGPluginVer branch March 14, 2024 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

EngSys This issue is impacting the engineering system.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants