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

Split Release Job to Publish Job for Documents Publications only #339

Open
hollowaykeanho opened this issue Jun 15, 2024 · 1 comment
Open
Assignees
Labels
New Feature Case is about developing a new feature/aspect. NON-Backward Compatible Solution is NOT backward compatible.

Comments

@hollowaykeanho
Copy link
Member

Description

There are times where the documents are the only thing to be released and not the packages themselves. Hence, it's best to split into 2 Jobs:

  1. Release - for the products' release.
  2. Publish - for only the document release.

Expected Behavior

Release Job and Publish Job are separated where the latter is executed after the former.

Current Behavior

Release Job handles both works and it's hard to update documents without manually deleting pkg/ directory.

Associated Data Files

No response

@hollowaykeanho hollowaykeanho added the New Feature Case is about developing a new feature/aspect. label Jun 15, 2024
@hollowaykeanho hollowaykeanho self-assigned this Jun 15, 2024
@github-project-automation github-project-automation bot moved this to Buckets in AutomataCI Jun 15, 2024
@hollowaykeanho hollowaykeanho moved this from Buckets to v3.0.0 in AutomataCI Jun 15, 2024
@hollowaykeanho hollowaykeanho added the NON-Backward Compatible Solution is NOT backward compatible. label Jun 17, 2024
@hollowaykeanho
Copy link
Member Author

definitely not backward compatible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Feature Case is about developing a new feature/aspect. NON-Backward Compatible Solution is NOT backward compatible.
Projects
Status: v3.0.0
Development

No branches or pull requests

1 participant