Failure: Asset Validation Workflow about jam

[sophiewigmore]

I am open to removing this entirely. It has never passed and I'm in agreement at this point that it's not super valuable. If you want to take a stab at fixing it and having it run before releasing, I'd support that too, but enough time has gone into trying to fix this that I'm fine to abandon as well.

[fg-j]

@sophiewigmore is this failure residual from before your fix?

[sophiewigmore]

@fg-j yea, I forgot to close this out. We'll see if the fix worked on the next release 🙇🏻‍♀️

[github-actions]

Another failure occurred: https://github.com/paketo-buildpacks/jam/actions/runs/3290525582

[robdimsdale]

@paketo-buildpacks/tooling-maintainers this looks like an issue with the script that validates the jam version. It failed on multiple runs so I don't think it's a flake:

Run chmod +x "$GITHUB_WORKSPACE/jam"
chmod: changing permissions of '/home/runner/work/jam/jam/jam': Operation not permitted
Error: Process completed with exit code 1.

[github-actions]

Another failure occurred: https://github.com/paketo-buildpacks/jam/actions/runs/3290525582

[robdimsdale]

Interesting. It looks like this job has never passed since it was introduced in jam v1.2.0.

Given it runs after the release is created, I don't think it's particularly valuable. At best it can tell us that we just shipped a broken version of jam.

In practice, I don't think we've ever seen a release of jam where the version was incorrect, so I would advocate removing this job entirely.

If we want this job to exist, I think it should come before we release, not after.

@paketo-buildpacks/tooling-maintainers I'm happy to take a pass at this, but I'd like feedback on whether we want to fix the job (and move it pre-release) or remove it entirely.

[robdimsdale]

I'd rather just remove it. We've not any issues in the past with this feature, so I have high confidence in it continuing to work without this type of validation.

I'll open a PR to remove it.