-
Notifications
You must be signed in to change notification settings - Fork 54
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
Bump configuration-as-code from 1.34 to 1.35 #172
Conversation
hack as I can't change the Jenkinsfile, note in this case it wasn't noticed because the Jenkinsfile allows no test results, the pct build is failing but the process doesn't exit with 1 as test_failures are allowed, assuming they are reported on later, but because the build failed there's no actual test failure. Not intending this for merge, just so we can see the failures as we fix them
Currently failing on: ssh-credentials bump has caused:
commented here: |
Just so we can check we got all the required plugins
let's remove the fail fast, while testing? 🤔 |
if i change the Jenkinsfile it will just be ignored, |
if we ask nicely maybe we can get commit access? 🙇 |
Pretty please Jesse 😄 |
Seeing if the ansicolor failure is a flake or consistent |
failed this time on script-security. cc @jglick |
I am reluctant to disable |
Oh, and this is why I don't like the PCT... it's testing a quite unreal setup. |
thanks for taking a look @amuniz, From what I can see it should be managed though, In that bom release it's importing other boms up until latest, |
How is bom-latest being picked up? I don't see it in https://github.com/jenkinsci/bom/blob/bom-4/bom-2.138.x/pom.xml It looks they are picked up backward, but not forward (which seems correct). |
If I run:
I see:
https://github.com/jenkinsci/bom/blob/bom-4/bom-2.138.x/pom.xml#L15 https://github.com/jenkinsci/bom/blob/bom-4/bom-2.150.x/pom.xml#L15 ... |
Ah, ok. Then I have no idea 🤷♂️ |
@jglick any ideas? |
Also @amuniz the bom change in workflow-step-api is unreleased, but even if I checkout the released version I have the same issue, |
Sorry, I have no time to work on this at the moment.
Yes, no one likes it really, but we are sort of stuck with it because nearly all our test coverage presumes a Maven flat |
…into revert-164-revert-161-patch-1
You are busy! Thanks for moving this repo along. |
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 would rather bite the bullet and integrate it, even with Folders plugin suppressed. We can fix it in a follow-up, PCT patch is needed IIUC
cc @jetersen