[Builds] Remove elements unnecessary with the new version-bump workflow #2387
Conversation
HannesWell
force-pushed
the
remove-unnecessary-build-elements
branch
from
c45aafc
to
e8d34a8
Compare
|
As thenew workflow is not yet setup on this repo, this one can not be pushed, right? |
This repository is not really the problem since the removed elements are (hardly) used here, but we should await until it's active in all other (active) SDK repositories. And while JDT should only be a matter of committer time, Equinox and SWT seem to need more adjustments and might take longer. |
HannesWell
force-pushed
the
remove-unnecessary-build-elements
branch
2 times, most recently
from
96dce5e
to
19abb15
Compare
With the new reusable workflow for automated version increments in pull-requests it is not necessary anymore to bump versions in advance during release preparation. This now happens automatically as part of the PR verification and that step can therefore be removed.
HannesWell
force-pushed
the
remove-unnecessary-build-elements
branch
from
19abb15
to
8476eab
Compare
|
Landing this part in. |
To add some context, why this is important now:
With this being submitted, Equinox and SWT still don't get the version-bumps on first change in the dev-cycle, but at least changing the parent-pom version should be possible now. |
|
For Equinox and SWT the following PRs could now be created, after renaming the existing |
With the new reusable workflow for automated version increments in pull-requests, introduced with #2352, it is not necessary anymore to bump versions in advance during release preparation or the enable bumping if the property 'compare-version-with-baselines.skip' is set to false. Everything now happens automatically and these elements can therefore be removed.
Removing these elements avoids partly duplicated configuration and generally reduced the amount of configuration.