On Thu, Aug 29, 2019 at 11:24 AM Oleg Nenashev <[email protected]> wrote:
> Dependabot + pom.xml definition should be our target goal.
Not quite sure what you are proposing here. Some kind of POM profile
to test against newer stuff? I was actually proposing something
completely different (but perhaps complementary): that you would write
something like
@Library('jenkins-infra/pipeline-library@73')
buildPlugin(configurations: buildPlugin.recommendedConfigurations())
which would run on a matrix including, say, 2.176.3 as the high core
version. Dependabot would then suggest incrementing the library
number, which might pull in various changes, including but not limited
to testing against a newer LTS.
> lack of the node step where we can retrieve and process POM.xml
You can
try {
String pom = readTrusted 'pom.xml'
// process…
} catch (x) {
// untrusted PR may have touched POM; see JENKINS-45970
}
outside of a `node` block, if you think you can do something useful with that.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0fRY_nUGEM-oMSi0ny1nok-CL7HR0xC9NWxZkqSXeopA%40mail.gmail.com.
