You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Members of the Gazebo core team currently need to push files to S3 during the release process for Gazebo packages (including sdformat) using personal S3 credentials. The upload is handled using the release.py script. Moving this process into a centralized automation system will support growing the Gazebo core team without requiring the granting of S3 bucket access to more individuals and remove the need for existing personal credentials.
Implementation:
Spawn a generation job in Jenkins from release.py, which will create the source tarball and push it to S3 and/or GitHub Releases, it could potentially also create the Debian source package and trigger the release upload for the source package only. Then on success, trigger the numerous parameterized debbuilder jobs. The release.py job could either block until the “source release” job is complete or just exit once it is triggered and rely on Jenkins to notify the releaser that their triggered “source builder” or one of the subsequently triggered debbuilder jobs failed.
Members of the Gazebo core team currently need to push files to S3 during the release process for Gazebo packages (including sdformat) using personal S3 credentials. The upload is handled using the
release.py
script. Moving this process into a centralized automation system will support growing the Gazebo core team without requiring the granting of S3 bucket access to more individuals and remove the need for existing personal credentials.Implementation:
Spawn a generation job in Jenkins from release.py, which will create the source tarball and push it to S3 and/or GitHub Releases, it could potentially also create the Debian source package and trigger the release upload for the source package only. Then on success, trigger the numerous parameterized debbuilder jobs. The release.py job could either block until the “source release” job is complete or just exit once it is triggered and rely on Jenkins to notify the releaser that their triggered “source builder” or one of the subsequently triggered debbuilder jobs failed.
Roadmap:
The text was updated successfully, but these errors were encountered: