Am I doing something wrong here? I *constantly* get failures with 
ci.jenkins.io typically with agents not working when I expect them to. Not 
build failures with my plugin but infra issues before the plugin even gets 
built. Typically out of memory issues when the build doesn't even start. At 
the time of writing there are ~320 jobs waiting to be built and most of the 
agents marked as offline. I've seen that number a lot higher in the past. I 
honestly don't know whether this is a common issue or not. Typically I end 
up waiting either days for a Windows agent or in this most recent failure I 
can't even connect to a windows agent so the Linux part of the build 
doesn't even start and the whole build is marked as a failure.

My Jenkinsfile looks like this:

buildPlugin(useAci: true)

I only added useAci after finding out in a similar manner that my builds 
were failing with infra issues without it.

I thought the recommendation was to add a buildPlugin() statement in a 
Jenkinsfile in your plugin's root directory. I therefore assumed that what 
actually builds the plugin is stable most of the time. Have I got the wrong 
end of the stick? Should I be using something else in my Jenkinsfile? I 
can't be the only plugin dev to face these issues which leads me to believe 
I must be doing something wrong or thinking about this in the wrong way. Do 
I just happen to be building my plugin at the wrong time of the week?

I know I can always proceed to with my PRs and builds by ignoring the 
result of the CI build but then..... what's the point of the recommendation 
to add buildPlugin() 
<https://jenkins.io/doc/developer/publishing/continuous-integration/>?

Yours massively frustrated

Mez

-- 
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/9914283d-cc5a-40ff-8a0d-ce5a4eca2a6d%40googlegroups.com.

Reply via email to