Skip to content
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

Replace tarball generation in release.py by a Jenkins job #990

Closed
18 of 20 tasks
j-rivero opened this issue Aug 14, 2023 · 2 comments
Closed
18 of 20 tasks

Replace tarball generation in release.py by a Jenkins job #990

j-rivero opened this issue Aug 14, 2023 · 2 comments
Assignees

Comments

@j-rivero
Copy link
Contributor

j-rivero commented Aug 14, 2023

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:

@j-rivero j-rivero self-assigned this Aug 28, 2023
@scpeters
Copy link
Contributor

#1020 is kind of related

@j-rivero
Copy link
Contributor Author

All merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants