Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

META: Development of build-env:create-project command #7

Closed
13 of 22 tasks
greg-1-anderson opened this issue Mar 11, 2017 · 1 comment
Closed
13 of 22 tasks

META: Development of build-env:create-project command #7

greg-1-anderson opened this issue Mar 11, 2017 · 1 comment

Comments

@greg-1-anderson
Copy link
Member

greg-1-anderson commented Mar 11, 2017

The build-env:create-project command is under development. Backwards compatibility is not guaranteed for future changes to this command until version 1.3.0 is tagged.

Initial requirements:

  • Create a GitHub project from a template
  • Create a Pantheon site
  • Configure Circle CI to test the GitHub project on the Pantheon site on each PR
  • Has functional tests that creates GitHub/Pantheon/Circle projects and confirms that the configured Circle tests pass
  • Tears down test projects once tests complete
  • Has "plugable" site-install strategy when creating new sites
  • Detect whether site supports multidev, and degrade to dev-only testing if it does not.

Later changes:

  • Refactor commandfile implementation into multiple classes (requires Terminus 1.1.1)
  • Repository providers other than GitHub
    • Bitbucket
    • Gitlab
  • CI services other than Circle
    • Travis
    • Jenkins
    • Gitlab
  • More testing improvements
    • Keep last set of sites for inspection after tests; tear down old test projects at beginning of next test
    • Add flags to teardown ("obliterate") command to force deletion / ignore errors
    • Add a scenario that creates a pull request on the test repository and confirms that a multidev environment is created, and that the change is tested

For discussion on permutation testing, see #5.

@ataylorme
Copy link
Contributor

Cleaning up old issues. The command itself exists. If the other items need to be tracked please open a new issue for each and add to the 2.0 milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants