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

Change the way of using the releasepy credentials #538

Merged
merged 3 commits into from
Nov 28, 2024

Conversation

j-rivero
Copy link
Contributor

Together with gazebo-tooling/release-tools#1201

Replace the usage of a single token by per user generated Jenkins API tokens followed the configuration model used in ros_buildfarm.

release_instructions.md Outdated Show resolved Hide resolved
Co-authored-by: Steve Peters <[email protected]>
Signed-off-by: Jose Luis Rivero <[email protected]>
j-rivero added a commit to gazebo-tooling/release-tools that referenced this pull request Nov 28, 2024
…API tokens (#1201)

Commit changes:

* Remove the existing token 
* Change the authentication model to use per-user Jekins API tokens: 41d75d8
* Implement --auth for release.py
* Use --auth from releasepy in nightly/releasepy jobs
* Add osrfbuild permission to call -debbuilder and brew_release
* Include basic python metadata files

* Corresponding developers documentation update: gazebosim/docs#538

Signed-off-by: Jose Luis Rivero <[email protected]>
@j-rivero j-rivero merged commit d2d9898 into master Nov 28, 2024
5 checks passed
@j-rivero j-rivero deleted the jrivero/new_auth_releasepy branch November 28, 2024 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants