Closed jonahgraham closed 7 months ago
@jonahgraham
FYI, one approach I was considering was some type of job that checks timestamps on some regular and fairly short schedule and when it determines that the simrel staging repo is newer than expected, would kick off the EPP staging job. It's just a really rough idea though and I did not have enough time this month to investigate that.
In the old days (when we had triggering) because EPP takes so long that most EPP builds during release weeks fail because until the simrel repo gets quiet overnight the EPP build was running while the simrel repo was changing contents. That is why I thought just a once a day build is a good idea.
I like your idea of looking for a marker to know whether to run the build. If Simrel added a file (e.g. buildnumber.txt) to https://download.eclipse.org/staging/2024-06 I could read that every 5(?) minutes and skip the build if it hadn't changed. I would store that same number in https://download.eclipse.org/technology/epp/staging/ somewhere as the comparison point.
There is a plug-in that would work: https://plugins.jenkins.io/urltrigger/ - it could be set to watch https://download.eclipse.org/staging/2024-06/content.jar
I'll raise an issue with helpdesk to ask if that can be installed.
That would be nice if we didn't need to brew our own solution!
The provides a workaround for the lack of triggering from SimRel -> EPP, see https://github.com/eclipse-packaging/packages/issues/122