search

bitrise-steplib / steps-generate-changelog

MIT License
2 stars 7 forks source link

Generate-changelog step generates empty CHANGELOG.md #20

Open insiderser opened 2 years ago

insiderser commented 2 years ago

Troubleshooting

Useful information

Issue description

Sometimes generate-changelog step generates an empty changelog even though there have been some commits between the current and the previous tags. The git-commit-changelog step running immediatelly after generate-changelog is able to find changelog.

Restarting failed builds doesn't help.

Bitrise info

Config:
- NewVersion: 1.1.18.3
- ChangelogPath: /bitrise/deploy/CHANGELOG.md
- WorkDir: /bitrise/src
Changelog:

The changelog content is available in the BITRISE_CHANGELOG environment variable

Steps to reproduce

Haven't found any solid way of reproducing the issue.

  1. Create a release branch from develop, merge into master.
  2. Tag master, which will trigger release deployment -> Deployment sometimes fails due to empty changelog.
  3. Merge the same release branch into develop -> Sometimes empty changelog as well.

We run generate-changelog step on every push to develop as well, and it has never failed after merging ordinary feature/fix branches into develop. It fails when there are release branches and merges into master only.

Roland-Bak commented 2 years ago

Hello @insiderser 👋

Can you let me know if the issue is still persistent? In case it is, I'll take this up with the developers and see what can be done to get to the bottom of this 🙂

oleksandr-bezushko-axon commented 2 years ago

@Roland-Bak Thanks for looking into this issue.

Yes, the issue was still present as of Jan 6th. It was more frequent on that day. I can share a more recent build URL with you if needed.

@insiderser is my another account. Sorry for messing this up.

bitrise-coresteps-bot commented 2 years ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

insiderser commented 2 years ago

Still important to me