(dev/release#9) distmaker - Report on head for commit civicrm-drupal-8 #15149
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
The general goal is to produce tags for
civicrm-drupal-8
during the release process. This PR is a prerequisite (necessary but not sufficient).The workflow for producing release tags is generally as follows:
distmaker
to prepare a release candidate (a collection of files - e.g.civicrm-5.18.0-drupal.tar.gz
,civicrm-5.18.0-joomla.zip
,civicrm-5.18.0.json
, etc). The candidate includes a JSON file which describes the build (i.e. the list of inputs/git-commits and outputs/tarballs).releaser
- which takes the release candidate and:The present PR adds more metadata at step 1.
Before
civicrm-drupal-8.git
:After
civicrm-drupal-8.git
drupal-8
in this tree:Technical Details
drupal-8/
(civicrm-drupal-8.git
).distmaker
can still be used withoutdrupal-8
. (As in the past, so this is still: if you're only building the Joomla zip file, then you don't need the code for drupal-8 or WordPress).drupal-8
when CI does an automated builddistmaker
to ensure.