Problem/Motivation

Drupal.org recently opened up gitlab CI to contrib module maintainers

Proposed resolution

This can be done by adding a .gitlab-ci.yml

Remaining tasks

  • ✅ File an issue about this project
  • ❌ Addition/Change/Update/Fix to this project
  • ❌ Testing to ensure no regression
  • ➖ Automated unit/functional testing coverage
  • ➖ Developer Documentation support on feature change/addition
  • ➖ User Guide Documentation support on feature change/addition
  • ➖ UX/UI designer responsibilities
  • ➖ Accessibility and Readability
  • ❌ Code review from 1 Varbase core team member
  • ❌ Full testing and approval
  • ❌ Credit contributors
  • ❌ Review with the product owner
  • ❌ Update Release Notes and Update Helper on new feature change/addition
  • ❌ Release

Varbase update type

  • ✅ No Update
  • ➖ Optional Update
  • ➖ Forced Update
  • ➖ Forced Update if Unchanged

User interface changes

  • N/A

API changes

  • N/A

Data model changes

  • N/A

Release notes snippet

  • N/A
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:

Comments

kalash-j created an issue. See original summary.

kalash-j’s picture

Assigned: kalash-j » Unassigned
Status: Active » Needs review

Pipeline is working fine now
had some issue with composer which are solved now

rajab natshah’s picture

Status: Needs review » Needs work
kalash-j’s picture

Status: Needs work » Needs review

@rajab-natshah did the changes you mentioned in MR.

indranil roy’s picture

Status: Needs review » Needs work
rajab natshah’s picture

Status: Needs work » Closed (outdated)

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.