Trigger Builds for each portal when their configuration changes or if package.json updates

Description

We should switch from having a jenkins job for each portal and instead trigger builds for each portal by looking at changes in their configuration folder, if something has been committed since the last build then it should get built. There's an edge case though, if the package.json has been updated, then all portals should get built. (Note - this is for staging)

For production we can stick with manually pushing the portal jobs, but we should consolidate to having a single job that does this. We can feed that job the name of the portal to be built.

Environment

None

Activity

Show:
Fixed
Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Michael Lee

Reporter

Michael Lee

Priority

Major

Development Area

Portals