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

Do not warn when triggered job is a success #375

Merged
merged 5 commits into from
May 7, 2024

Conversation

hashar
Copy link
Contributor

@hashar hashar commented Apr 10, 2024

I keep having log messages such as:

WARNING: [hudson.plugins.parameterizedtrigger.TriggerBuilder perform]
Attempting to use the result of unfinished build #1234

The message was introduced in #161 by 06d8f19 but in #148 / 02ee6ea, mapBuildResult() was made to return null by default (eg on SUCCESS).

The resut is the warning is always triggered when the triggered build succeeds.

Fixes https://phabricator.wikimedia.org/T336782

Testing done

Submitter checklist

Preview Give feedback

I keep having log messages such as:

  WARNING: [hudson.plugins.parameterizedtrigger.TriggerBuilder perform]
  Attempting to use the result of unfinished build <name of job> #1234

The message was introduced in jenkinsci#161 by 06d8f19 but in jenkinsci#148 / 02ee6ea,
mapBuildResult() was made to return `null` by default (eg on SUCCESS).

The resut is the warning is always triggered when the triggered build
succeeds.

Fixes https://phabricator.wikimedia.org/T336782
@hashar hashar requested a review from a team as a code owner April 10, 2024 12:43
@MarkEWaite MarkEWaite enabled auto-merge (squash) May 6, 2024 01:06
@MarkEWaite MarkEWaite added the bug label May 6, 2024
@MarkEWaite MarkEWaite disabled auto-merge May 6, 2024 01:07
@MarkEWaite
Copy link
Contributor

MarkEWaite commented May 6, 2024

This pull request is a good reason to release a new version of the plugin, though I would like to complete the evaluation of the upgrade of the optional dependency on promoted builds plugin before this is released. The optional dependency is being evaluated in pull requests:

My preference is to update to the older version of promoted builds so that the fewest users are forced to update to a newer version of promoted builds, but the dependency version is still modernized to a popular release that is only 20 months old instead of 29 months old.

@MarkEWaite
Copy link
Contributor

Tests pass in plugin BOM draft pull request when the optional dependency on promoted builds plugin is updated to the same new value in both the git plugin and the parameterized trigger plugin. That means we'll need a release of git plugin and a release of parameterized trigger plugin in the same plugin BOM release.

This pull request will be the catalyst for the automated release of the parameterized trigger plugin.

@hashar
Copy link
Contributor Author

hashar commented May 7, 2024

Do you need me to rebase the pull request?

@MarkEWaite
Copy link
Contributor

Thanks for asking, but no need to rebase. It will be squash merged

@MarkEWaite MarkEWaite merged commit f6fff3e into jenkinsci:master May 7, 2024
14 checks passed
@hashar
Copy link
Contributor Author

hashar commented May 13, 2024

Thank you for the release. I have confirmed the warnings are gone!

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

Successfully merging this pull request may close these issues.

3 participants