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

[JENKINS-68904] Adress ESLint violations #6794

Merged
merged 5 commits into from
Jul 8, 2022

Conversation

NotMyFault
Copy link
Member

@NotMyFault NotMyFault commented Jul 7, 2022

Addresses the ESLint part of JENKINS-68904
The latest commit simulates a CI failure and will be reverted once demonstrated.

Proposed changelog entries

  • Entry 1: Issue, Human-readable Text
  • ...

Proposed upgrade guidelines

N/A

Submitter checklist

  • (If applicable) Jira issue is well described
  • Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change) and are in the imperative mood. Examples
    • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
  • Appropriate autotests or explanation to why this change has no tests
  • New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadoc, as appropriate.
  • New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO") if applicable.
  • For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@mention

Maintainer checklist

Before the changes are marked as ready-for-merge:

  • There are at least 2 approvals for the pull request and no outstanding requests for change
  • Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
  • Changelog entries in the PR title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood
  • Proper changelog labels are set so that the changelog can be generated automatically
  • If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
  • If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

@NotMyFault NotMyFault added the skip-changelog Should not be shown in the changelog label Jul 7, 2022
@NotMyFault NotMyFault requested a review from a team July 7, 2022 07:05
@NotMyFault
Copy link
Member Author

The failure can be seen on https://ci.jenkins.io/job/Core/job/jenkins/job/PR-6794/2/consoleFull and has been reverted by now.

@NotMyFault NotMyFault requested a review from a team July 7, 2022 15:40
Copy link
Member

@basil basil left a comment

Choose a reason for hiding this comment

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

commit 6b70fc8 is not fully reverted by commit f40fca8. I would prefer that it be fully reverted and that we discuss the topic of enforcement in a separate PR (the fix for JENKINS-68903), since there are multiple ways to implement JENKINS-68903 and the partial revert in f40fca8 implements the solution to JENKINS-68903 that I describe in that bug as "less attractive."

@@ -330,7 +331,7 @@ function checkRowCellOverflows(row) {
// build name (first field) a block element, forcing the details and controls to wrap
// onto the next row (creating a second row).
buildName.classList.add('block');
var wrap = blockWrap(buildDetails, buildControls);
wrap = blockWrap(buildDetails, buildControls);
Copy link
Member

Choose a reason for hiding this comment

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

Ah yes, the intricacies of variable scope in JavaScript… 😄 I don't understand this but I trust you.

Comment on lines +361 to +363
buildBadge = $(buildControls).getElementsBySelector('.build-badge')[0];
if (buildBadge) {
var badgeOverflowParams = getElementOverflowParams(buildBadge);
badgeOverflowParams = getElementOverflowParams(buildBadge);
Copy link
Member

Choose a reason for hiding this comment

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

Ah yes, the intricacies of variable scope in JavaScript… 😄 I don't understand this but I trust you.

@NotMyFault
Copy link
Member Author

The commit has been reverted properly 👍🏻

@basil
Copy link
Member

basil commented Jul 7, 2022

This PR is now ready for merge. We will merge it after approximately 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process. Thanks!

@basil basil added the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Jul 7, 2022
@basil basil merged commit d737a76 into jenkinsci:master Jul 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback skip-changelog Should not be shown in the changelog
Projects
None yet
3 participants