Back to dev version

[jglick]

ed1f487 was not paired with the expected “back to development version” commit, indicating a botched release.

If you do not want to publish releases manually and deal with local authentication issues and so on, you can also consider automated releases.

[sbobin]

Hi Jesse! Thanks for the fix you propose. Can you clarify? Is it related to my recent question on jenkins-dev about "Cannot publish new plugin release"?

[jglick]

Possibly. maven-release-plugin is fragile in the sense that a failure partway through a release will leave your repository in an invalid state that needs to be manually cleaned up.

[sbobin]

I will try that then. Thanks!

[sbobin]

Hi Jesse!

Unfortunately, it does not seem to fix my build. I have merged your pull request. When I run mvn -e -X release:prepare release:perform, it will create a new tag but not a new release.

Now I have got 3 new tags since the last few weeks my build is broken and I made new attempts, but the build still ends up failing and I have no corresponding release published on the Jenkins page for my plugin: https://plugins.jenkins.io/mathworks-polyspace/releases/.

Can you or somebody from the Jenkins team please help me fix my plugin build?

Note: my Jenkins repo is marked "This branch is 4 commits ahead of, 3 commits behind mathworks/mathworks-polyspace-plugin:master.". I don't know if there is any relation. How to reconcile that?

Thanks!

[jglick]

Can you or somebody from the Jenkins team please help me fix my plugin build?

You can file a helpdesk ticket. Personally I do not plan to help anyone use maven-release-plugin since it is notoriously error-prone, one of the reasons we set up the automated release system.

[sbobin]

Thanks for your quick reply! With the page on automated release system you mention, is there anything else I need to do to fix my repo and get it on a clean state (and file a helpdesk request)? Or can I ignore the current failing build/release and it goes through a completely different workflow? Thanks.

[jglick]

is there anything else I need to do to fix my repo and get it on a clean state

You mean to prepare it for CD? You should start with it incrementalified, which it seems is only partially the case currently since version is hard-coded rather than using revision (compare the against the plugin archetype).

[sbobin]

Ok. Will try that. Thanks!