-
Notifications
You must be signed in to change notification settings - Fork 64
Update PCT #863
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 PCT #863
Conversation
|
|
According to https://ci.jenkins.io/job/Tools/job/bom/job/PR-863/2/pipeline-console/?selected-node=332 The build is erroring when injected tests fail |
|
Perhaps the injected tests do not add value to PCT? |
Yeah possibly, we already ignore them in bom Line 41 in b9fa01a
I'm reverting the PR affecting us in our fork of PCT anyway jenkinsci/plugin-compat-tester#343 Upgrading should be dealt with separately to fixing the jep-229 issue imo |
|
I manually deployed a SNAPSHOT because the folder is setup to merge with master bringing in changes that cause bom to fail. I tried reverting the PR that caused issues but was having difficulty. this could work in the meantime what do people think? |
|
Whatever works but could you get a link to a commit sha at least of what is in the snapshot? 🤔 Would be nice to finally land a proper PCT fix? |
|
done |
prep.sh
Outdated
| version=0.5.1-rc1066.9cfd30140d30 # TODO https://github.com/jenkinsci/plugin-compat-tester/pull/276 | ||
| pct=$HOME/.m2/repository/org/jenkins-ci/tests/plugins-compat-tester-cli/${version}/plugins-compat-tester-cli-${version}.jar | ||
| [ -f $pct ] || $MVN dependency:get -Dartifact=org.jenkins-ci.tests:plugins-compat-tester-cli:${version}:jar -DremoteRepositories=https://repo.jenkins-ci.org/public/,https://repo.jenkins-ci.org/incrementals/ -Dtransitive=false | ||
| version=0.5.1-SNAPSHOT # TODO https://github.com/jenkinsci/plugin-compat-tester/pull/344 (c9c684eab7e8de91650ad1c96ded6489c42910f1) |
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.
Better to get jenkinsci/plugin-compat-tester#344 to pass tests—by ignoring stuff if necessary.
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.
ha, my last attempt of just reverting the PCT change that affected bom didn't go so well as there were other changes. Unless there's a simpler fix I'd probably just revert every PR in the last year =/.
pr-merge pain -.-, can't build an isolated PR
Not sure if I'll have the time to fix properly.
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.
Ack. PCT needs a lot of work.
|
See #657. Ought to remain in draft until it is picking up an incremental build (if not an actual release). |
| timestamp=0.5.1-20220130.152941-4 | ||
| pct=$HOME/.m2/repository/org/jenkins-ci/tests/plugins-compat-tester-cli/${version}/plugins-compat-tester-cli-${timestamp}.jar | ||
| [ -f $pct ] || $MVN dependency:get -Dartifact=org.jenkins-ci.tests:plugins-compat-tester-cli:${timestamp}:jar -DremoteRepositories=https://repo.jenkins-ci.org/public/,https://repo.jenkins-ci.org/incrementals/ -Dtransitive=false | ||
| version=1152.vafc19b26d5aa # TODO https://github.com/jenkinsci/plugin-compat-tester/pull/345 |
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.
No description provided.