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.
Named jobs are triggered with __default__ name
See original GitHub issuev2.8.2 (I haven’t upgraded to 3.0+, yet) broke how “triggering” named jobs were saved: the name is ignore and the __default__ one is used.
v2.8.1 and below worked fine.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Jobs - GitLab Documentation
Job names must be 255 characters or fewer. Use unique names for your jobs. If multiple jobs have the same name, only one...
Read more >How to create and trigger build jobs in Jenkins? - Tools QA
Step 4: Give the project name "Setup Build Job" inside the "Projects to Build" textbox. By default, we will select the "Trigger only...
Read more >Workflow syntax for GitHub Actions
When more than one default setting is defined with the same name, GitHub uses the most specific default setting. For example, a default...
Read more >Start-Job (Microsoft.PowerShell.Core)
Specifies a friendly name for the new job. You can use the name to identify the job to other job cmdlets, such as...
Read more >Trigger a named pipeline in gitlab - Stack Overflow
I explicitly don't want to rerun the default pipelines on these triggers. ... TLDR: How do I trigger a job/pipeline by name?
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
(Btw - I added some screenshots and the JSON of the job to my comment above for each version.)
No worries! I was able to rollback to the previous version just fine.
And yes, it sounds like that’s what’is missing from the code.
🎉 This issue has been resolved in version 3.2.2 🎉
The release is available on:
Your semantic-release bot 📦🚀