During the last two releases I had the problem that as soon as I put the new version numbers in drupal-org.make the Gitlab build process fails to build a debian package until I also create the releases on D.o.

CommentFileSizeAuthor
#2 switch_from_tar-2912760-2.patch1.93 KBhelmo
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

helmo created an issue. See original summary.

helmo’s picture

helmo CreditAttribution: helmo at Initfour websolutions for Aegir Cooperative commented
FileSize
switch_from_tar-2912760-2.patch1.93 KB
Jon Pugh’s picture

Jon Pugh
he/him
Primary language English
Location New Windsor NY
CreditAttribution: Jon Pugh at OpenDevShop Inc (CLOSED) commented

I think perhaps we can avoid changing the makefile to use git by creating a second makefile that has this, and make the CI builds use that instead.

I recently did this with devshop so that devmaster profile can be copied from a folder (needed for forks and pull requests) instead of checked out. https://github.com/opendevshop/devshop/blob/1.x/RoboFile.php#L144

helmo’s picture

helmo CreditAttribution: helmo at Initfour websolutions for Aegir Cooperative commented
Related issues: +#2910758: [meta] 3.13 release (bugfix/patches)

What CI is testing then is the new Debian packages which should be promoted to the stable channel.

I'd like to keep CI as close to a normal install as possible. And having another file with version numbers in them to maintain is an extra thing to go wrong.

  • helmo committed 09337c0 on 7.x-3.x 
    Issue #2912760 by helmo: Switch from tar packages to git tags in drupal-...
helmo’s picture

helmo CreditAttribution: helmo at Initfour websolutions for Aegir Cooperative commented
Status: Active » Fixed

First in the 1.13 release.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.