question-mark
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.

Streamline lifecycle events exposed

See original GitHub issue

We currently document and expose the following events that are not 100% implemented yet:

  • onPreGetCache, onGetCache: caching happens in the buildbot right now, so those events actually happen after restoring caches
  • onSaveCache, onPostSaveCache: for the same reason, those events actually happen before saving caches
  • onPackage, onPostPackage: I am not sure what those events do. We documented them as “Package & optimize artifacts”. At the moment, those are performed right after build, before any buildbot optimization.
  • onPreInstall, onInstall: installations happen in the buildbot right now, so those events actually happen after install

Since those events are not really implemented yet, shouldn’t we only expose them and document them once they are implemented?

@DavidWells @tzmanics @verythorough

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
DavidWellscommented, Jan 17, 2020

In an effort to simplify things we should clean up the events.

We can always introduce new events later

Here is the list

  • onInit - Runs before anything else
  • onPreBuild - Before build commands are executed
  • onBuild - Build commands are executed
  • onPostBuild - after build commands are executed
  • TBD onPreDeploy - before deployment finishes and site is live (waiting on buildbot)
  • ~TBD onDeploy - Deployment happens (waiting on buildbot)~
  • TBD onPostDeploy - After deployment finishes and site is live (waiting on buildbot)
  • onSuccess - Runs on build success
  • onError - Runs on build error
  • onEnd - Runs on build error or success

The cache, install, & function stuff can be introduced later as we finalize those primitives & how they interact with the flow. So for now, fold function packaging into onBuild or onPreBuild

0reactions
ehmickycommented, Jan 20, 2020

Done in #712.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Handling Lifecycles with Lifecycle-Aware Components
The lifecycle events that are dispatched from the framework and the Lifecycle class. These events map to the callback events in activities and ......
Read more >
Building a lifecycle event - Product Documentation | ServiceNow
Lifecycle events enable you to automate the fulfillment of HR cases such as new hire onboarding.
Read more >
4 Steps to Streamline How You Track Your Event Sponsorships
In a four-step process, you can streamline the sponsorship purchases into your event, utilize all the advantages of events including the ...
Read more >
Secure & Automate JML Lifecycle​ | Authomize.com
Achieve full visibility for every identity across every environment; Tracking progress with intuitive UI. Monitor and Alert on JML Events. Maintain ...
Read more >
How to Harness and Expose the Business Value of Events ...
New events are brought online, new use cases are revealed, or priorities simply shift. Managing the lifecycle of your event API product to ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found