You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a pipeline I have at my employer's GitLab, the documentation step hung indefinitely, or at least during 2h. By forcing the pipeline to use the version 2.2.6 I was able to run it again.
I wonder if it is possible to document this in the changelog (readme?), since it does not seem to be a frequent issue.
The text was updated successfully, but these errors were encountered:
Rather than documenting this I would prefer to find the bug and resolve it. Are you able to reproduce this consistently? Which diagramming tools are you using?
It's a legacy component we're building a hotfix for, so I'm not entirely aware of all the tools involved. However, I do know hpp2plantum is used towards generating PlantUML diagrams.
It's something that could be observed consistently on the one project (I would have to run others to see whether I can replicate it there as well). Even when I ran it for older Commits, it got to the same step and froze until the pipeline timed out (2h)
asciidoctor -v -r asciidoctor-diagram -r asciidoctor-pdf -b pdf not-my-projects-name.adoc
On a pipeline I have at my employer's GitLab, the documentation step hung indefinitely, or at least during 2h. By forcing the pipeline to use the version 2.2.6 I was able to run it again.
I wonder if it is possible to document this in the changelog (readme?), since it does not seem to be a frequent issue.
The text was updated successfully, but these errors were encountered: