Closed jordanpadams closed 3 years ago
Unfortunately, when I tried git fetch --prune --unshallow --tags
I get an error:
fatal: --unshallow on a complete repository does not make sense
I'm not sure what this means.
See:
Further research: in my test environment, I do plain git clone
during testing while the checkout action only clones the ref that triggered the workflow.
Pressing on!
Ah I think I found the problem.
In Python I'm filtering for *dev*
but in Maven I copied the same logic over when I should be looking for *SNAPSHOT*
(Also FYI, no need to pipe git tag -l
into grep
since it has filtering capability built-in.)
@nutjob4life this unfortunately doesn't look to be fixed. see latest build of validate.
@nutjob4life unfortunately, it still doesn't look like this has been fixed?
https://github.com/NASA-PDS/validate/releases/tag/1.25.0-SNAPSHOT
@nutjob4life needs to update the docker image with git-lfs
Here's where I think the issue is:
Okay, updated the base image with git-lfs
and re-ran the action on validate. Here's a screenshot of the step now:
Does that look like it fixed it @jordanpadams?
🎉 looks good @nutjob4life. let me see what else I can break...
Describe the bug The SNAPSHOT releases are being recreated for each unstable CI/CD run, but the tags are not being cleaned up. This causes the tags and release assets to get out of sync.
To Reproduce See latest validate snapshot.
It says
@pdsen-ci pdsen-ci released this 6 minutes ago
but then follows with7 commits to master since this release
indicating a new tag was not created with the new releaseProposed Fixes
Java:
Python (haven't tested this with Python, but assuming it has the same issue?):