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

Update analysis-model and warnings-ng on ci.j #3051

Closed
NotMyFault opened this issue Jul 12, 2022 · 5 comments
Closed

Update analysis-model and warnings-ng on ci.j #3051

NotMyFault opened this issue Jul 12, 2022 · 5 comments

Comments

@NotMyFault
Copy link
Member

Service(s)

ci.jenkins.io

Summary

Hey,

could we update analysis-model-api to 10.13.0 and warnings-ng to 9.14.0 on ci.j please?
I added support for Stylelint as linter and I'm looking forward to use this functionality for core builds on ci.j

Thanks in advance!

Reproduction steps

No response

@NotMyFault NotMyFault added the triage Incoming issues that need review label Jul 12, 2022
@lemeurherve
Copy link
Member

lemeurherve commented Jul 12, 2022

These plugins will be updated soon, it just needs the time to be catched up in automated pull requests like this one.
We usually review and merge these kind of PRs the day they're opened, closing this issue, let us know if it's really urgent.

@NotMyFault
Copy link
Member Author

NotMyFault commented Jul 12, 2022

Not urgent for sure, but dduportal let me know yesterday, that not all installed plugins and versions are managed by that, hence the issue raised.

@lemeurherve
Copy link
Member

lemeurherve commented Jul 12, 2022

I discussed with @dduportal, I shouldn't have closed this issue indeed my first message is completely wrong, sorry.

Plugins on ci.jenkins.io are manually managed, let me take care of it.

@lemeurherve lemeurherve reopened this Jul 12, 2022
@lemeurherve lemeurherve self-assigned this Jul 12, 2022
@lemeurherve lemeurherve removed the triage Incoming issues that need review label Jul 12, 2022
@dduportal
Copy link
Contributor

My aploogies to both of you: I did not share enough information so it mislead Herve.

But this issue is legit, and now knowledge had been shared with Herve so we can handle this request.
Thanks for reproting @NotMyFault and sorry for the delay!

@lemeurherve
Copy link
Member

Updates OK:
image
image

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

3 participants