Repository navigation
Travis release jobs fail on second pass #882
Copy link
Copy link
Closed
Labels
type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
Activity
- addedtype: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
on Sep 21, 2015 It would be great to run our after hook only after all tests pass, since technically, we don't know if our code is good until they do. I found something a week or so ago that could help. Do you remember the link by chance?
I think it was https://github.com/alrra/travis-after-all ?
Fixed by #893
- added a commit that references this issue
on Nov 10, 2022 - added a commit that references this issue
on Jul 23, 2025 - added a commit that references this issue
on Jan 28, 2026 - added a commit that references this issue
on Feb 17, 2026 - added 2 commits that reference this issue
on Feb 24, 2026 - added a commit that references this issue
on Mar 18, 2026 - added 2 commits that reference this issue
on Mar 23, 2026 - added a commit that references this issue
on Mar 27, 2026 - added a commit that references this issue
on May 5, 2026
Metadata
Metadata
Assignees
Labels
type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Now that we're supporting multiple node versions via CI, we need to update our release scripts. When and if the second pass finishes (0.12), it will fail at creating a new folder for the documentation JSON, because it already exists from the previous pass (4.x).