Streamline lifecycle events exposed
See original GitHub issueWe 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 cachesonSaveCache
,onPostSaveCache
: for the same reason, those events actually happen before saving cachesonPackage
,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?
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top 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 >
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
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 elseonPreBuild
- Before build commands are executedonBuild
- Build commands are executedonPostBuild
- after build commands are executedonPreDeploy
- before deployment finishes and site is live (waiting on buildbot)onPostDeploy
- After deployment finishes and site is live (waiting on buildbot)onSuccess
- Runs on build successonError
- Runs on build erroronEnd
- Runs on build error or successThe 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
oronPreBuild
Done in #712.