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

Develop Github Action that uses the CLI #24354

Closed
10 tasks done
Tracked by #24753
wezell opened this issue Mar 13, 2023 · 0 comments
Closed
10 tasks done
Tracked by #24753

Develop Github Action that uses the CLI #24354

wezell opened this issue Mar 13, 2023 · 0 comments

Comments

@wezell
Copy link
Contributor

wezell commented Mar 13, 2023

Parent Issue

CLI Phase 2
#24753

User Story

I am a dotCMS developer and I want to set up a CI/CD pipeline from github using github actions. As a developer, I should be able to commit my files, code changes and fixes into git and see them reflected in my dotCMS environment.

  • If I add a new site, I should see that site created in dotCMS
  • If I commit a new content type, I should see that reflected - same with css, js, VTLs, files and folders, file containers and file templates.
  • If I change a content type, it should be changed in the target environment.
  • If I change a content type, vtl or asset, it should be updated in the target environment as well.

Acceptance Criteria

  • The action will generally be triggered by a workflow that is fired when a new commit/merge happens in a branch

  • The action will be built as a Docker container action (see: https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action)

  • The action's Dockerfile should be stored in the /tools/dotcms-cli/action/

  • The action will take env variables to configure it

    • The target dotCMS env
    • dotCMS API Token, provided as a github secret
    • any cli config flags
    • should destructive actions be taken - whether to support deletes and take destructive actions (folder, content type, file deletions)
  • As we add new features to the CLI, we should also make sure our github action will support them.

Proposed Objective

Technical User Experience

Proposed Priority

Priority 2 - Important

Tasks

Preview Give feedback
  1. QA : Not Needed Team : Scout Type : Task
  2. Merged QA : Approved QA : Passed Internal Release : 24.01.26 Team : Scout Type : Task dotCMS : CLI
  3. Merged QA : Not Needed Team : Scout Type : Task
  4. Merged QA : Not Needed Team : Scout Type : Task
  5. Merged QA : Not Needed Team : Scout Type : Task
  6. Merged QA : Approved QA : Passed Internal Release : 24.01.26 Team : Scout Type : Task dotCMS : CLI
  7. Merged NW Removed Note to QA QA : Approved QA : Passed Internal Release : 24.02.20 Team : Scout Type : Task dotCMS : CLI
  8. Merged QA : Approved QA : Passed Internal Release : 24.01.26 Team : Scout Type : Task dotCMS : CLI
  9. Merged Note to QA QA : Approved QA : Passed Internal Release : 24.02.20 Team : Scout Type : Task dotCMS : CLI
  10. Merged QA : Approved QA : Passed Internal Release: 24.03.11 Team : Scout Type : New Functionality dotCMS : CLI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants