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

Run each Jenkins build flavor on its own machine #303

Closed
BetsyMcPhail opened this issue Sep 16, 2024 · 3 comments
Closed

Run each Jenkins build flavor on its own machine #303

BetsyMcPhail opened this issue Sep 16, 2024 · 3 comments

Comments

@BetsyMcPhail
Copy link
Contributor

In #300, all but 2 jobs were removed from Jenkins because they also existed in GHA. In this issue, the task is to update the Jenkinsfile so that the remaining two jobs (drake_bazel_external and drake_cmake_external), each run on their own node. This way we can ensure that the setup scripts and results remain independent.

Follow up to #61

@BetsyMcPhail BetsyMcPhail self-assigned this Sep 16, 2024
@jwnimmer-tri jwnimmer-tri changed the title Run each Jenkins build flavor on its on machine Run each Jenkins build flavor on its own machine Oct 29, 2024
@BetsyMcPhail
Copy link
Contributor Author

BetsyMcPhail commented Nov 13, 2024

As part of #322 each job runs on a fresh instance. However, there is still a single Jenkinsfile that should be split up, see #309.

@jwnimmer-tri
Copy link
Contributor

A single Jenkinsfile is all we want / need. The "self-contained examples" goal does not encompass showing users how to configure Jenkins -- only GHA.

@BetsyMcPhail
Copy link
Contributor Author

Great, then I think we can call this one complete?

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

No branches or pull requests

2 participants