Problem/Motivation

It would be nice if MR's made for this project spun up a Tugboat Preview environment and created some default boards so that it is easier to QA merge requests submitted for the project.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#4 tugboat-instance.png53.27 KBswirt

Issue fork burndown-3605184

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

swirt created an issue. See original summary.

swirt opened merge request !29

jeremylichtman’s picture

jeremylichtman commented

Hi @swirt, one of the principals of this project is no external dependencies (other that Drupal itself). IMHO, it would be better to have a separate module called burndown_tugboat that adds this functionality in.

swirt’s picture

swirt
he/him
Primary language English
commented
StatusFileSize
new tugboat-instance.png53.27 KB

A separate module would not / could add this. This is for previews, for this module, within the issue on Drupal.org.
This does not add a dependency to this module. It simply provides a config.yml that the tugboat runner on drupal.org looks for. If it finds it, it tries to spin up site using the merge request.

tugboat preview created for the MR in this issue

This is the same thing that core issues use now.
More information here

It truly makes maintaining a module much easier.

swirt’s picture

swirt
he/him
Primary language English
commented

This is attempting to create the preview for this MR, but tugboat on d.o is having a bad day. I raised the problem with the tugboat team here.

swirt’s picture

swirt
he/him
Primary language English
commented

The MR should have just been the tugboat config.yml. However the existing drush commands accepted no options and relied only on interactive io. This made it impossible to use them "as is" to generate some sample boards. So I added some logic to support drush options with io interaction as a backup.

swirt’s picture

swirt
he/him
Primary language English
commented
Status: Active » Needs work

Changing the status so that this waits until the failure to build is resolved.

jeremylichtman’s picture

jeremylichtman commented

I'll merge once things are working okay.

swirt’s picture

swirt
he/him
Primary language English
commented
Status: Needs work » Needs review

This is now working. @ambermatz from Tugboat got me straightened out. Crediting @ambermatz for the assist in Drupal Slack.

If you click the link that says "View live preview" it will take you to a temporary drupal site with Burndown installed and the drush commands ran to build some sample projects and tasks.
u: admin
p: admin

These instances only live for I think 10 days.

swirt’s picture

swirt
he/him
Primary language English
commented

No need to tag a release for this one as there is nothing that impacts anyone here for using the module.

jeremylichtman’s picture

jeremylichtman commented

Reviewed and merged.

jeremylichtman’s picture

jeremylichtman commented
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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