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

Refactor Jenkins build tests #300

Merged

Conversation

nicolecheetham
Copy link
Collaborator

@nicolecheetham nicolecheetham commented Sep 12, 2024

Cleans up Jenkins build tests workflow making it more clear and concise

Additionally, removes build tests in the Jenkins that already exist as GHA build tests

  • Jeremy could not remember why there was redundancy of build tests in the Jenkinsfile and therefore advised removing the build tests which duplicate the ones in the GHA: drake_bazel_download, drake_catkin_installed, drake_cmake_installed

Issue: #61


This change is Reviewable

Copy link
Collaborator Author

@nicolecheetham nicolecheetham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+@BetsyMcPhail for feature review

Reviewable status: all discussions resolved, LGTM missing from assignee betsymcphail, platform LGTM missing (waiting on @BetsyMcPhail)

Copy link
Contributor

@BetsyMcPhail BetsyMcPhail left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 1 unresolved discussion, LGTM missing from assignee betsymcphail, platform LGTM missing (waiting on @nicolecheetham)


-- commits line 2 at r1:
BTW As this PR is actually making a functional change by removing some tests from Jenkins, it would be good to explicitly mention that here. That would make it clear that they aren't being removed by accident.

Related, the "Continuous Integration" section of README.md needs to be updated to account for these removals.

Copy link
Collaborator Author

@nicolecheetham nicolecheetham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 1 unresolved discussion, LGTM missing from assignee betsymcphail, platform LGTM missing (waiting on @BetsyMcPhail)


-- commits line 2 at r1:

Previously, BetsyMcPhail (Betsy McPhail) wrote…

BTW As this PR is actually making a functional change by removing some tests from Jenkins, it would be good to explicitly mention that here. That would make it clear that they aren't being removed by accident.

Related, the "Continuous Integration" section of README.md needs to be updated to account for these removals.

Thank you for pointing this out. I have updated the description of the PR to mention the functional change as well as the README.md

Copy link
Contributor

@BetsyMcPhail BetsyMcPhail left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewed 2 of 2 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: :shipit: complete! all discussions resolved, platform LGTM from [betsymcphail] (waiting on @nicolecheetham)

Copy link
Collaborator Author

@nicolecheetham nicolecheetham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+@jwnimmer-tri for platform review

Reviewable status: all discussions resolved, LGTM missing from assignee jwnimmer-tri, platform LGTM from [betsymcphail] (waiting on @jwnimmer-tri)

Copy link
Contributor

@jwnimmer-tri jwnimmer-tri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewed 2 of 2 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: 1 unresolved discussion, platform LGTM from [betsymcphail, jwnimmer-tri] (waiting on @nicolecheetham)


-- commits line 2 at r2:
When this merges, we need a much better summary -- either with a force-push to adjust the commit message, or edit it during the squash-and-merge using the web interface.

The verb "refactor" indicates a cleanup with no change in functionality, but here we have two important changes in functionality:

(1) Remove three build flavors from Jenkins because they are redundant with GHA:

  • drake_bazel_download
  • drake_catkin_installed
  • drake_cmake_installed

(2) In the remaining two build flavors in Jenkins, run each on a separate machine, so their setup script and/or results do not contaminate each other.

Copy link
Contributor

@BetsyMcPhail BetsyMcPhail left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 1 unresolved discussion, platform LGTM from [betsymcphail, jwnimmer-tri] (waiting on @jwnimmer-tri)


-- commits line 2 at r2:

Previously, jwnimmer-tri (Jeremy Nimmer) wrote…

When this merges, we need a much better summary -- either with a force-push to adjust the commit message, or edit it during the squash-and-merge using the web interface.

The verb "refactor" indicates a cleanup with no change in functionality, but here we have two important changes in functionality:

(1) Remove three build flavors from Jenkins because they are redundant with GHA:

  • drake_bazel_download
  • drake_catkin_installed
  • drake_cmake_installed

(2) In the remaining two build flavors in Jenkins, run each on a separate machine, so their setup script and/or results do not contaminate each other.

I don't believe 2) was implemented in this PR... I'm not sure if that was intentional or not? Nicole, I'm happy to take the Jenkins refactor (splitting into two jobs) as a follow-up to this PR if you would like.

Copy link
Contributor

@jwnimmer-tri jwnimmer-tri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 1 unresolved discussion, platform LGTM from [betsymcphail, jwnimmer-tri] (waiting on @BetsyMcPhail)


-- commits line 2 at r2:

Previously, BetsyMcPhail (Betsy McPhail) wrote…

I don't believe 2) was implemented in this PR... I'm not sure if that was intentional or not? Nicole, I'm happy to take the Jenkins refactor (splitting into two jobs) as a follow-up to this PR if you would like.

Ah, you're right. I misread the groovy.

In the case it's just (1) as the only functional change.

I would also be OK to mention something like "refactor code to remove layers of confusing indirection" in the commit message, if you like.

Copy link
Collaborator Author

@nicolecheetham nicolecheetham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 1 unresolved discussion, platform LGTM from [betsymcphail, jwnimmer-tri] (waiting on @BetsyMcPhail and @jwnimmer-tri)


-- commits line 2 at r2:

Previously, jwnimmer-tri (Jeremy Nimmer) wrote…

Ah, you're right. I misread the groovy.

In the case it's just (1) as the only functional change.

I would also be OK to mention something like "refactor code to remove layers of confusing indirection" in the commit message, if you like.

Sure. Splitting the two jobs to run on a separate machine can be a follow-up to this PR once this one is merged

And I'll see if I can include both the build refactoring and the removal of the redundant build flavors into a commit message. If not, I can more closely use your suggestion.

Copy link
Contributor

@jwnimmer-tri jwnimmer-tri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed all commit messages.
Reviewable status: 1 unresolved discussion, platform LGTM from [betsymcphail, jwnimmer-tri] (waiting on @BetsyMcPhail)

Copy link
Contributor

@BetsyMcPhail BetsyMcPhail left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 1 unresolved discussion, platform LGTM from [betsymcphail, jwnimmer-tri] (waiting on @nicolecheetham)

Copy link
Contributor

@BetsyMcPhail BetsyMcPhail left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 1 unresolved discussion, platform LGTM from [betsymcphail, jwnimmer-tri] (waiting on @jwnimmer-tri and @nicolecheetham)


-- commits line 2 at r2:

Previously, nicolecheetham (Nicole C.) wrote…

Sure. Splitting the two jobs to run on a separate machine can be a follow-up to this PR once this one is merged

And I'll see if I can include both the build refactoring and the removal of the redundant build flavors into a commit message. If not, I can more closely use your suggestion.

Follow-up issue: #303

Copy link
Contributor

@jwnimmer-tri jwnimmer-tri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed all commit messages.
Reviewable status: :shipit: complete! all discussions resolved, platform LGTM from [betsymcphail, jwnimmer-tri] (waiting on @nicolecheetham)

@jwnimmer-tri jwnimmer-tri merged commit a0e612f into RobotLocomotion:main Sep 17, 2024
6 checks passed
@nicolecheetham nicolecheetham deleted the jenkins_build_refactor branch September 25, 2024 21:06
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

Successfully merging this pull request may close these issues.

3 participants