Santiago Chialvo
opened 2 years ago
-
Fixing issue info will be cached in
<onedev data dir>/projects/<project id>/info/commit. Just stop OneDev, delete this folder, and start OneDev. This folder will be recreated then. -
Previous Value Current Value Open
Closed
-
Thanks! We'll try it. Non-related question please, I wanted to ask... If I change a job's name on the YML, for example:
What will happen with the listed issues when we make a new build under this job? Will it remember all previous issue listing and continue as if nothing happened, or will consider the rename as new completely different job, so it will start listing from scratch?
Santiago.
-
Fixed issues will no longer be available for the first run after job rename, and things will back to normal for second and subsequent runs.
-
Thank you!
| Type |
Question
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Watchers (2)
Hi Robin,
We have a recent case where some issues were improperly added to the 'Fixed issues' list after creating a build, after we checked the was a regex under 'Commit Message Fix Patterns' that was putting issues in our 'Resolving' state, then passed through other custom states we have but most important that they ended in 'Fixed issues' build list as I said before. So, what I did was remove this regex because we just use the other one that comes by default (considering keywords resolved, resolving, etc.), when I did that, the list of 'Fixed issues' properly excluded those issues initially included by the regex. However, I see that in the issue itself, I can still see the build listed under 'Fixing Builds' and even the commit (considering the old regex) under 'Fixing Commits'. I think the issue stills out of sync with regards of this regex status change... my question is, is there a way to correct this in any way? I've used the 'Run Integrity Check' option but it doesn't help. Thanks.
Santiago.