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

Fix release process by restoring groupId #21

Merged
merged 2 commits into from
Jan 8, 2023

Conversation

MarkEWaite
Copy link
Contributor

Fix the release process by restoring original groupId

  • Return to original plugin groupId
  • Describe untested changes in the README

The plugin groupId was changed in the pom file after the release of 1.10. That change caused the release of 1.11 and 1.12 to fail. The last release available from the Jenkins update center is 1.10.

There have been significant changes in the master branch of the plugin since the release of 1.10. Rather than risk breaking compatibility for existing users of the 1.10 release, I've removed the incorrect change of groupId and accepted that this plugin cannot be released without testing those changes.

I'm not a user of the plugin. I'm not willing to perform that testing. If someone else wants to adopt the plugin, perform the additional testing, and release a new version, this change is a necessary but not sufficient step towards that release.

Compare the current code to the 1.10 tag for the details of the changes made since the 1.10 release.

https://issues.jenkins.io/browse/JENKINS-70301 describes the relationship between this plugin and the WMI Windows Agents plugin. Users that want to remove the WMI Windows Agents plugin will also need to remove this plugin or they will need to wait until jenkinsci/jenkins#7568 is available in Jenkins core 2.386 or newer.

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did

The plugin groupId was changed in the pom file after the release of 1.10.
That change caused the release of 1.11 and 1.12 to fail.  The last
release available from the Jenkins update center is 1.10.

There have been significant changes in the master branch of the plugin
since the release of 1.10.  Rather than risk breaking compatibility for
existing users of the 1.10 release, I've removed the incorrect change of
groupId and accepted that this plugin cannot be released without testing
those changes.

I'm not a user of the plugin.  I'm not willing to perform that testing.
If someone else wants to adopt the plugin, perform the additional testing,
and release a new version, this change is a necessary but not sufficient
step towards that release.

Compare the current code to the 1.10 tag for the details of the changes
made since the 1.10 release.

https://issues.jenkins.io/browse/JENKINS-70301 describes the
relationship between this plugin and the WMI Windows Agents plugin.
Users that want to remove the WMI Windows Agents plugin will
also need to remove this plugin or they will need to wait until
jenkinsci/jenkins#7568 is available in Jenkins
core 2.386 or newer.
If someone adopts this plugin, they need to know that there are many
changes on the master branch that have not been delivered to users and
may surprise users with compatibility issues or other problems.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant