[hibernate-dev] Keeping CI from being confusing.
steve at hibernate.org
Sat Dec 16 11:44:19 EST 2017
For the main ORM job I see someone changed the label to "AWS&&Slave", which
is obviously different from the "Slave" label you recommended. Basically
at this point I am completely lost as to what to use for these labels.
Since I did not add this "AWS&&Slave" I am going to leave it alone. For
the other ORM jobs, I do see many have the "OS1" label. I can fix those to
"Slave". But I have to ask... if "Slave" is the more appropriate value for
the vast majority of builds, can't that just be the default? What if we
leave off the label? As you say, labels are supposed to indicate that the
job "requires such capabilities" as in the capabilities implied by that
label. But if a job has no such requirement, why is it a requirement to
add any label?
On Tue, Dec 12, 2017 at 6:31 AM Sanne Grinovero <sanne at hibernate.org> wrote:
> I see many jobs are still explicitly configured to request a build on
> slaves tagged as "OS1".
> Please get rid of that: we have no longer any slave running on OS1,
> some of the new slaves use the "OS1" label to allow a smooth migration
> - but it's a lie and it's been a long time since we removed OS1.
> I will need to eventually cleanup such things, as it's getting messy
> and confusing.
> Labels are expected to be used to tag specific slaves to have specific
> capabilities, so that some jobs can flag they require such
> Typically the only label you need is "Slave" as we don't want most
> jobs to run on the master node.
> An example of a valid label is "HANA" for the job running integration
> tests on the HANA database; for obvious reasons this job needs to be
> run on the only slave actually having HANA running.
> While at it, if you installed any Jenkins plugin which you no longer
> need please remove it.
> General reminder: there's no dedicated team to keep CI or
> infrastructure running efficiently, we're all responsible so try to
> dedicate it some 20 minutes every month making sure your jobs are
> still necessary and configurations are up to date.
> For more extensive operations ask Davide or myself and we'll see to help.
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
More information about the hibernate-dev