-
Notifications
You must be signed in to change notification settings - Fork 52
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
add configuration-as-code plugin to Bill of Material #78
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Triggers a test failure in git
. Probably something for @MarkEWaite to fix (incompatibility with newer versions of configuration-as-code
?) but TBD. If the failure is triaged and fixed in a separate PR, then we can go ahead with this after excluding that test suite until the other PR is merged and released.
|
||
@Test | ||
public void smokes() { | ||
assertThat(Jenkins.get().getSystemMessage(), is("Hello World")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A bit more interesting to configure some object defined in this plugin, but good enough for now I guess.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is nothing really interesting to configure in JCasC 😆
Though we could use it to smoke test all other plugins 😆
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean, currently this plugin does not define any global settings, but it could. Whether that would make test coverage any more meaningful for BOM updates is another question.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
91d7c3e hmm
@MarkEWaite 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wanna state BOM and PCT is pretty awesome! Kudos 😍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should I remove the test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is fine.
That test failure is fixed in git client plugin 2.8.2. The JCasC plugin updated its test definition and the git client plugin was updated to use the most recent JCasC plugin tests. |
Co-Authored-By: Jesse Glick <[email protected]>
Well that fixed the
|
Same issue. They both need updating of JCasC just as Git did. |
@MRamonLeon are you up for fixing them? 😅 |
Sorry @Casz, I don't have enough bandwidth right now, maybe next week. For ssh-credentials, maybe a security issue has been solved and the log doesn't contain the plain password anymore and the test needs to be fixed:
Please take into account that the |
@MRamonLeon I'll see if I have bandwidth for it 😅 |
Looking into ssh-credentials 😓 |
hah, I just created a branch on that repo, it'll require this to be merged: |
Okay I'll look into the other one @timja so looking into |
I see someone else did my work: jenkinsci/ssh-agents-plugin#147 thanks @fcojfernandez |
@jglick would you prefer dependabot updating the deps or are you okay with me updating the deps in this PR? |
If you have some dependencies related to this change that you see could be updated, by all means update them. |
@MarkEWaite any idea why these fail consistently:
https://ci.jenkins.io/blue/organizations/jenkins/Tools%2Fbom/detail/PR-78/11/tests ? |
@Casz the getAllLogEntries test compares the output of I've disabled the assertion in that test on the development branches (master and stable-2.8) of the git client plugin because the test is checking a deprecated method and is not very useful. However, the released git client plugin 2.8.5 includes that test and now fails due to the recent commits on the master branch. If you need a git client plugin release that includes that change, you can either use git client plugin 3.0.0-beta11 or an incremental build from the master branch. |
🙏 for green |
@jglick not sure the CI is so red 😕❓ |
Sigh, yes, seems like Remoting problems on ci.jenkins.io again. |
I can't even load this CI job =/, it's been loading for +20 mins |
🙏 |
Whoop green, cc @jglick |
This would be great to get merged! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for all downstream changes to make it happen!
cc @jglick @oleg-nenashev hopefully I did this right 😅