libelektra: release pipeline fails

        Start 191: testscr_check_shellcheck

226/264 Test #191: testscr_check_shellcheck 
......................***Failed    0.06 sec


ELEKTRA SCRIPTS SHELLCHECK TEST


awk: cmd. line:1: fatal: cannot open file 
`benchmarks/changetracking.c' for reading: No such file or directory

https://build.libelektra.org/blue/organizations/jenkins/libelektra-release/detail/libelektra-release/193/pipeline

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 66 (66 by maintainers)

Most upvoted comments

Great, let us see if the master build goes through, which will update the website.

Let us close this, as release pipeline succeeded!

AFAIK, this file was created automatically, should I also change the content and adapt it to contain the correct description?

Yes, please.

this file should also contain everything from the 0.10.0 version, right?

No, it should be empty, as it is for the next release.

what should the contents of this file be?

A template for future releases (the next after next). It shouldn’t contain a specific version prefix.

  • the tag was not created (can easily be manually done if all the other things are fixed but should fixed in release pipeline nevertheless)

Not sure how it is done now, but the tags were never automatically pushed. For the 0.9 series you had to download the git bundle from the jenkins artifacts and push the tag manually. (Intentionally, as a last verification step)

Well, that’s what I asked in the beginning in a PR were I made changes. I asked if I need to change the files again….

Ok, seems like there was a misunderstanding. At least following files still need fixes:

  • doc/todo/NEWS.md
  • doc/news/_preparation_next_release.md
  • doc/news/2023-05-22_0.10.0.md (should also be renamed to 05-23 as the release happens today)

But other than that it looks really good¹, so only the last few steps.

¹ The link check as described in doc/todo/release.md worked and kdb --version of the debs print 0.10.0. I didn’t test the rpms, though.

I love your responsiveness and I am waiting for a PR 🚀