[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [glassfish-dev] JSF Templating -- What is blocking?
|
On 5/5/20 11:59 AM, arjan tijms wrote:
Hi,
Woodstock is one of the projects that uses an embedded
Jenkinsfile instead of the script that most projects are
using.
One could argue whether this is really needed, as the
Jenkinsfile assumes intimate knowledge about (specifically)
the Kubernetes cluster it's running on.
The inline YAML template for the k8s pod is definitely not ideal.
IIRC the only reason for it being there is to implement the shared
local repository.
This can be fixed by registering templates in the Jenkins master and
assigning labels to them.
You can then select which template to use by specifying the label in
the Jenkinsfile like this:
agent {
label "my-template-label"
}
Not sure we have permissions to add templates on the current Jenkins
setup, but if we wanted to go that way I'm sure we can work things
out with the eclipse infra team.
In this case one of the issues is the runAsUser, which
is randomised on OpenShift (the cloud that Eclipse uses). I
can fix the Jenkinsfile, but in addition I think it might be
a good idea to add a "regular" job that uses the default
Eclipse CI Kubernetes and JNLP images as well.
Multibranch pipelines are way better than plain old Jenkins jobs. It
enables the GitHub PR workflow out of the box and thus makes
contributions easy.
IMO this is a must have for every single project with code.
Also, the default template will not have a shared local repository
or have sufficient resource limits.
You may also run into some tests issues (.e.g IIRC CTS won't pass if
sendmail isn't running)
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev