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.

Sign up for GitHub

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

Jump to bottom

Update submodules action is failing #9

Closed
djperrefort opened this issue May 31, 2024 · 2 comments
Closed

Update submodules action is failing #9

djperrefort opened this issue May 31, 2024 · 2 comments
Assignees
@djperrefort

Comments

@djperrefort
Copy link
Member

The GitOps CI for updating submodules is failing. The error indicates the checkout tag is empty. This indicates the tag value isn't being set properly somewhere along the CI pipeline.

Error message: Input "tag" cannot be empty

Example workflow: https://github.com/pitt-crc/keystone-docs/actions/runs/9272628855
@djperrefort djperrefort self-assigned this May 31, 2024
djperrefort added a commit to Better-HPC/keystone-api that referenced this issue May 31, 2024
@djperrefort
Adds missing needs dependency to publish job on release
738cd0b 
This should address Better-HPC/keystone-docs#9.

The `publish.with.version` value relies on `needs.version.outputs.version` but the `version` job is missing from the `needs` list.
@djperrefort djperrefort mentioned this issue May 31, 2024
Merged
djperrefort added a commit to Better-HPC/keystone-api that referenced this issue Jun 3, 2024
@djperrefort
Adds missing needs dependency to publish job on release (#313)
a223701 
This should address Better-HPC/keystone-docs#9.

The `publish.with.version` value relies on `needs.version.outputs.version` but the `version` job is missing from the `needs` list.
@djperrefort djperrefort mentioned this issue Jun 8, 2024
Merged
@djperrefort
Copy link
Member Author

The GitOps Trigger workflow is now passing, but it's publishing the wrong version of the documentation. The Update Submodules job updates the repo by pushing a commit to main that updates the appropriate submodules to the necessary VCS pointer. However, the Publish job does not pull this new commit. Instead, it pulls the previous one.

@djperrefort
Copy link
Member Author

Similar issue for reference: actions/checkout#461

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@djperrefort djperrefort

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@djperrefort