[
https://issues.apache.org/jira/browse/CASSANDRA-15668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-15668:
-------------------------------------------
Description:
On the new ci-cassandra.apache.org infrastructure agents are siloed to projects.
The declarative pipeline in the 2.2, 3.0, 3.11, and trunk branches do not
restrict the builds to agents with the 'cassandra' label. Because these agents
will not run jobs that don't specify this label, the pipeline task only ever
runs on unlabelled agents, of which there are very few (and likely shouldn't
exist, existing only from for now because of misconfigurations).
Example of the failure to run the pipeline tasks is
{noformat}
[Pipeline] Start of Pipeline
[Pipeline] node
Still waiting to schedule task
'cassandra10' is reserved for jobs with matching label expression;
'cassandra11' is reserved for jobs with matching label expression;
'cassandra12' is reserved for jobs with matching label expression;
'cassandra13' is reserved for jobs with matching label expression;
'cassandra14' is reserved for jobs with matching label expression;
'cassandra15' is reserved for jobs with matching label expression;
'cassandra16' is reserved for jobs with matching label expression; 'cassandra1'
is reserved for jobs with matching label expression; 'cassandra2' is reserved
for jobs with matching label expression; 'cassandra3' is reserved for jobs with
matching label expression; 'cassandra4' is reserved for jobs with matching
label expression; 'cassandra5' is reserved for jobs with matching label
expression; 'cassandra6' is reserved for jobs with matching label expression;
'cassandra7' is reserved for jobs with matching label expression; 'cassandra8'
is reserved for jobs with matching label expression; 'cassandra9' is reserved
for jobs with matching label expression
{noformat}
Along with this change, we can improve the name of the
{{*-test-jvm-dtest-forking}} stages.
was:
On the new ci-cassandra.apache.org infrastructure agents are siloed to projects.
The declarative pipeline in the 2.2, 3.0, 3.11, and trunk branches do not
restrict the builds to agents with the 'cassandra' label. Because these agents
will not run jobs that don't specify this label, the pipeline task only ever
runs on unlabelled agents, of which there are very few (and likely shouldn't
exist because of misconfiguration).
Example of the failure to run the pipeline tasks is
{noformat}
[Pipeline] Start of Pipeline
[Pipeline] node
Still waiting to schedule task
'cassandra10' is reserved for jobs with matching label expression;
'cassandra11' is reserved for jobs with matching label expression;
'cassandra12' is reserved for jobs with matching label expression;
'cassandra13' is reserved for jobs with matching label expression;
'cassandra14' is reserved for jobs with matching label expression;
'cassandra15' is reserved for jobs with matching label expression;
'cassandra16' is reserved for jobs with matching label expression; 'cassandra1'
is reserved for jobs with matching label expression; 'cassandra2' is reserved
for jobs with matching label expression; 'cassandra3' is reserved for jobs with
matching label expression; 'cassandra4' is reserved for jobs with matching
label expression; 'cassandra5' is reserved for jobs with matching label
expression; 'cassandra6' is reserved for jobs with matching label expression;
'cassandra7' is reserved for jobs with matching label expression; 'cassandra8'
is reserved for jobs with matching label expression; 'cassandra9' is reserved
for jobs with matching label expression
{noformat}
Along with this change, we can improve the name of the
{{*-test-jvm-dtest-forking}} stages.
> Jenkins 'Cassandra' label applied to the declarative pipeline
> --------------------------------------------------------------
>
> Key: CASSANDRA-15668
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15668
> Project: Cassandra
> Issue Type: Task
> Components: Build, Test/unit
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0-alpha
>
>
> On the new ci-cassandra.apache.org infrastructure agents are siloed to
> projects.
> The declarative pipeline in the 2.2, 3.0, 3.11, and trunk branches do not
> restrict the builds to agents with the 'cassandra' label. Because these
> agents will not run jobs that don't specify this label, the pipeline task
> only ever runs on unlabelled agents, of which there are very few (and likely
> shouldn't exist, existing only from for now because of misconfigurations).
> Example of the failure to run the pipeline tasks is
> {noformat}
> [Pipeline] Start of Pipeline
> [Pipeline] node
> Still waiting to schedule task
> 'cassandra10' is reserved for jobs with matching label expression;
> 'cassandra11' is reserved for jobs with matching label expression;
> 'cassandra12' is reserved for jobs with matching label expression;
> 'cassandra13' is reserved for jobs with matching label expression;
> 'cassandra14' is reserved for jobs with matching label expression;
> 'cassandra15' is reserved for jobs with matching label expression;
> 'cassandra16' is reserved for jobs with matching label expression;
> 'cassandra1' is reserved for jobs with matching label expression;
> 'cassandra2' is reserved for jobs with matching label expression;
> 'cassandra3' is reserved for jobs with matching label expression;
> 'cassandra4' is reserved for jobs with matching label expression;
> 'cassandra5' is reserved for jobs with matching label expression;
> 'cassandra6' is reserved for jobs with matching label expression;
> 'cassandra7' is reserved for jobs with matching label expression;
> 'cassandra8' is reserved for jobs with matching label expression;
> 'cassandra9' is reserved for jobs with matching label expression
> {noformat}
> Along with this change, we can improve the name of the
> {{*-test-jvm-dtest-forking}} stages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
