Okay, that makes sense.
Jobs have been picked up, just required quite some hours to run everything.
this morning I noticed some failed with the following message:
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 54: Invalid option type "timestamps". Valid option types:
[authorizationMatrix, buildDiscarder, catchError, checkoutToSubdirectory,
datadog, disableConcurrentBuilds, disableResume, durabilityHint,
newContainerPerStage, overrideIndexTriggers, parallelsAlwaysFailFast,
preserveStashes, quietPeriod, rateLimitBuilds, retry, script,
skipDefaultCheckout, skipStagesAfterUnstable, throttle, throttleJobProperty,
timeout, waitUntil, warnError, withChecks, withContext, withCredentials,
withEnv, wrap, ws] @ line 54, column 9. timestamps() ^ WorkflowScript: 56:
Invalid option type "ansiColor". Valid option types: [authorizationMatrix,
buildDiscarder, catchError, checkoutToSubdirectory, datadog,
disableConcurrentBuilds, disableResume, durabilityHint, newContainerPerStage,
overrideIndexTriggers, parallelsAlwaysFailFast, preserveStashes, quietPeriod,
rateLimitBuilds, retry, script, skipDefaultCheckout, skipStagesAfterUnstable,
throttle, throttleJobProperty, timeout, waitUntil, warnError, withChecks,
withContext, withCredentials, withEnv, wrap, ws] @ line 56, column 9.
ansiColor('xterm') ^ 2 errors at
org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
at
org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085)
at
org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603)
at
org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581)
at
org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558)
at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at
groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at
groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at
groovy.lang.GroovyShell.parse(GroovyShell.java:700) at
org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:142)
at
org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127)
at
org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:571)
at
org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:523)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:337) at
hudson.model.ResourceController.execute(ResourceController.java:97) at
hudson.model.Executor.run(Executor.java:429) Finished: FAILURE
I've looked into our Jenkins scripts and and can't find these options. So I
assume these are some globally defined scripts that needs to be repaired.
thanks,
Robert
On 15-7-2021 11:18:34, Gavin McDonald <gmcdon...@apache.org> wrote:
Hi
On Thu, Jul 15, 2021 at 11:08 AM Robert Scholte
wrote:
> In case you haven't noticed: all Windows nodes are offline.
>
>
Yeah they are 'leased' nodes shared between all ci-* controllers and come
online
when in use.
Robert
> On 15-7-2021 10:29:31, Robert Scholte wrote:
> Our scripts use the labels ubuntu and Windows to distinguish the OS.
> Is it safe to add ubuntu to the maven nodes?
>
> thanks,
> Robert
> On 15-7-2021 10:06:37, Gavin McDonald wrote:
> Thanks All,
>
> Jobs have been migrated.
>
> Please test and report any issues ASAP to INFRA jira.
>
> https://ci-maven.apache.org/
>
>
>
> On 2021/07/08 21:37:43, Arnaud Héritier wrote:
> > Hi Gavin
> >
> > Let’s go. I cannot test more than the authentication today but I can
> assist
> > more later this month after my vacations.
> >
> > What is important is to move the shared libraries used by our jobs (I do
> > not remember how they were configured).
> >
> > We will see if we need / have to find some sponsors to setup some
> > additional build nodes.
> >
> > Thanks for your help.
> >
> > Le jeu. 8 juil. 2021 à 23:06, Enrico Olivelli a
> > écrit :
> >
> > > Il giorno gio 8 lug 2021 alle ore 20:06 Gavin McDonald
> > > gmcdon...@apache.org>
> > > ha scritto:
> > >
> > > > Hi All,
> > > >
> > > > With no more interest in this subject, and no willing testers, I'll
> be
> > > > going ahead tomorrow and move all Maven jobs to ci-maven.apache.org.
> > > >
> > >
> > > I have tested that I am able to login to ci-maven with my LDAP
> credentials
> > >
> > > Thanks
> > > Enrico
> > >
> > >
> > > >
> > > > Feel free to check after the move and create INFRA jira ticket(s) for
> > > > anything that breaks as a result.
> > > >
> > > > Gav...
> > > >
> > > > On 2021/06/30 18:23:54, Gavin McDonald wrote:
> > > > > Hi Michael,
> > > > >
> > > > > On 2021/06/30 18:12:12, Michael Osipov wrote:
> > > > > > Am 2021-06-30 um 20:03 schrieb Gavin McDonald:
> > > > > > > Hi Maven folks.
> > > > > > >
> > > > > > > Infra has decided to separate off the Maven build jobs from
> > > > > > > ci-builds.apache.org over to its very own Jenkins Controller
> and
> > > > Agents.
> > > > > > >
> > > > > > > This means that Maven now has a dedicated Jenkins environment
> for
> > > > itself.
> > > > > > > It
> > > > > > > also means that no other projects build jobs can build on the
> Maven
> > > > nodes;
> > > > > > > and
> > > > > > > then Maven jobs will no longer be able to build on the
> ci-builds
> > > > jobs.
> > > > > > >
> > > > > > > Your new Controller is set up as https://ci-maven.apache.org
> and
> > > > all Maven
> > > > > > > Committers
> > > > > > > can login via LDAP and create jobs.
> > > > > > >
> > > > > > > At the time of writing, there is one node/agent attached but I
> am
> > > > building
> > > > > > > 4 more - all
> > > > > > > Ubuntu 20.04 and based in our Azure account.
> > > > > >
> > > > > > Well, just Ubuntu? We actually need at least three different
> > > operating
> > > > > > systems to detect subtile bugs which I have found over time.
> > > > > > Since this is on an Azure can you rather add at least one
> Windows and
> > > > > > FreeBSD node to it? 4x Ubuntu won't really help.
> > > > >
> > > > > You are getting exactly as you have been using on ci-builds.a.o
> (and
> > > > builds.a.o) before that.
> > > > > There is no FreeBSD on any of our CI nor has there been for many
> years,
> > > > we do not support
> > > > > it.
> > > > >
> > > > > As for Windows nodes, you still have access to the same Windows
> nodes
> > > as
> > > > you always have, they are what are called floating agents available
> for
> > > > lease by all Jenkins Controllers, so your access and availability to
> the
> > > > Windows nodes will not change. We have 6 Windoes nodes currently and
> plan
> > > > to add some more soon.
> > > > >
> > > > > If anyone were to donate any nodes to attach to ci-maven then we'd
> be
> > > > happy to help add them on, including FreeBSD donated nodes, only
> > > difference
> > > > being that Infra would not manage them nor install any software on
> them,
> > > > which would be up to the donator(s).
> > > > >
> > > > > HTH
> > > > >
> > > > > >
> > > > > > Michael
> > > > > >
> > > > > >
> ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > >
> > > >
> > >
> > --
> > Arnaud Héritier
> > Twitter/Skype : aheritier
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
--
*Gavin McDonald*
Systems Administrator
ASF Infrastructure Team
