Jesse Glick
Jesse Glick
If you can figure out how to set that up, it would be great. Or something like https://github.com/jenkinsci/maven-hpi-plugin/pull/66. Or use Launchable to run some tests which seem important (not that...
I think there is a plugin that lets you do that. It cannot however _trigger_ a build when labels change.
In a similar vein, CloudBees CI PCT runs roughly corresponding to `jenkinsci/jenkins@master` caught prior to today’s weekly release: https://github.com/jenkinsci/forensics-api-plugin/pull/572 (Tried to confirm with `local-test.sh` but was unable to build `bom`...
Beware that @Vlatombe found some issues affecting the `kubernetes` plugin on AKS relating (as I recall) to scalability issues with the API server.
> I remember it to be when using non default jnlp container in pod agents. My recollection is that it affected all agents, not just using `container`, and the problem...
> rule out (or point at) the Kubernetes plugin by trying a BOM build using Azure VMs Fine enough if that is straightforward to do, but the most direct diagnosis...
> compile the plugin :exclamation: Whatever this was doing, it sounds like it needs to be rewritten. Nothing should need to be compiled. Take the `*.hpi` from the UC, look...
If that works, it sounds like a good hotfix for this symptom. The fundamental mistake is the attempt to use a deployed POM to build sources, which is not what...
> What are they for? Resolving dependencies from Maven builds. > relying on sources rather than binaries is inherently fragile Not sure if this is the cause of https://github.com/jenkins-infra/backend-extension-indexer/issues/97, but...