Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Fail in build step
See original GitHub issueHi,
Both building from source and using Docker showed an error:
Error: open internal/frontend/frontend_generated.go: no such file or directory
exit status 1
I resolved this issue by creating empty directory /internal/frontend/.
My machine is based on Arch Linux with go 1.14.5 version.
PS, Citadel seems to be best Trello alternative, keep developement!
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
TeamCity On-Premises - Build Failure Conditions - JetBrains
You can instruct TeamCity to mark a build as failed if some of its metrics (for example, code coverage or artifacts size) have...
Read more >In Parametrized Trigger Plugin, what's the difference between ...
When you choose Fail this build step if the triggered build is worse or equal to it will cause the perform method to...
Read more >jenkins job doesn't fail if build step fails · Issue #93 - GitHub
There is something wrong in the jenkins job which means that builds that fail (ie the build step in the job fails) do...
Read more >Keeping a build running after a Step fails - Bitrise
Issue: Every time a Step fails, the entire build fails as well. However, certain Steps aren't crucial to the build so they should...
Read more >Pipeline: Basic Steps - Jenkins
The behavior of the step when an exception is thrown can be configured to print a message, set a build result other than...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve pushed a commit so that the
internal/frontenddirectory gets created if it doesn’t exist (which it doesn’t on a freshly cloned repo) so this should now be fixed!Just for the log, as of 6f33cc5799fb3baf9c42b52dfd8cec764f34d378 I can report that the build step works.