-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Build] Deploy RelEng scripts in master branch build #2645
[Build] Deploy RelEng scripts in master branch build #2645
Conversation
cbf34c1
to
2cad6c8
Compare
Verified that this works by replaying the verification build and modified it to deploy to: Will delete that entire folder again, together with the https://ci.eclipse.org/releng/job/Publish_shell_scripts_for_releng_jobs/ Jenkins job, once this is submitted. |
I have now added a 'staging' mechanism to minimize downtime, but I have to test this better. |
d76e6a6
to
8f88aef
Compare
With the latest adjustments and after some more testing I think this is now ready. In general I would be nice to just start the deployment if something has changed, e.g. by uploading the commit-id of the current commit too and then running git diff before uploading, but I assume that's not worth the effort? |
Please get this one in and checks can be following commits. |
8f88aef
to
c9dab73
Compare
This ensures that releng scripts are always updated on the download-server as soon as they change in the git repository. Furthermore this avoids the need for the separate Jenkins job to deploy the scripts.
c9dab73
to
71f49a8
Compare
Yes. I just had it almost completely running quickly after my last message. So we have it with check now already. :) Submitting now, as the verification build does not test this. To bootstrap the |
After unanticipated build failures on the initial run on master I figured out that the disposal location
Deleting |
This ensures that releng scripts are always updated on the download-server as soon as they change in the git repository. Furthermore this avoids the need for the separate Jenkins job to deploy the scripts, thus making
https://ci.eclipse.org/releng/job/Publish_shell_scripts_for_releng_jobs/ obsolete (can be deleted once this is submitted).